Web API Odata Tutorial Sample fails with HTTP Error 403.14 even after applying correction

Question

The sample builds without errors, but it does not execute, it crashes with HHTP 403.14.

The recommended solution of enabling directory browsing was applied, but the sample continues crashing.

On another note, the instructions on the error listing mentioning the command :

Things you can try:

• If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists.
• Enable directory browsing.
  1. Go to the IIS Express install directory.
  2. Run appcmd set config /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the server level.
  3. Run appcmd set config ["SITE_NAME"] /section:system.webServer/directoryBrowse /enabled:true to enable directory browsing at the site level.
• Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.

contain the wrong syntax or are outdated. Syntax error is received when you apply this, enabled:true, for example , does not exist in the current syntax.

The solution that was used was listed under Microsoft's support:

Method 1

<script type="text/javascript">loadTOCNode(2, 'resolution'); </script>To resolve this problem, follow these steps:

1. Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
2. In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify.
3. In Features view, double-click Directory Browsing.
4. In the Actions pane, click Enable.

but, this does not solve the problem.

Does anybody know the fix?

Answer 1

This looks like an IIS configuration issue, so I will have to defer you to the http://www.iis.net website for help with IIS configuration or probably the ASP.NET WebAPI forum: http://forums.asp.net/1246.aspx/1?Web+API

However, you can enable "Failed Request tracing" on your IIS machine to check where in the pipeline the request is failing. See this link on how to enable the Failed Request tracing, the steps are a third down in the page: http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis

Thanks,

Prashant.

---

@prashantphadke || Windows Store Developer Solutions #WSDevSol || Want more solutions? See our blog, Windows Store & Phone Developer Solutions

Answer 2

Prashant,

Thanks for your reply, however, after watching the Pluralsight video on Web API, it looks like that this is a known error in Web API samples and that you need to navigate to a non default location by placing the name of the Web API page in the address bar with a "/" in front of it if you do not want to receive the error.

This does not change the fact that the information on the HTTP 403.14 error page is still incorrect in the syntax and now it is also out of date and confusing to most people who are learning Web API.

Thanks,

Ricardo

Answer 3

Hi Ricardo,

Can you re-post your IIS/ASP.NET or WebAPI question on the appropriate forum to get better help on this issue? This is unfortunately not the right place for this question.

Thanks,

Prashant.

---

@prashantphadke || Windows Store Developer Solutions #WSDevSol || Want more solutions? See our blog, Windows Store & Phone Developer Solutions

Answer 4

Prashant,

Which is the right Forum?

Thanks,

Ricardo

Answer 5

Hi Ricardo,

The ASP.NET Web API forum is: http://forums.asp.net/1246.aspx/1?ASP+NET+Web+API

The IIS forum is: http://forums.iis.net/

Thanks,

Prashant.

---

@prashantphadke || Windows Store Developer Solutions #WSDevSol || Want more solutions? See our blog, Windows Store & Phone Developer Solutions