views:

1675

answers:

6

I'm trying to run an ASP.NET MVC 2 web application under IIS on Windows 7, but I get a 403.14 error. Here are the steps to reproduce:

  1. Open Visual Studio 2010
  2. Create a new ASP.NET MVC 2 project called MvcApplication1
  3. Shift+F5 to run the app. You should see http://localhost:{random_port}/ and the page will render correctly.
  4. Click on MvcApplication1, and select "Properties". Go to the "Web" section.
  5. Select "Use Local IIS Web server" and create a virtual directory.
  6. Save.
  7. Shift+F5 to run the app. You should see http://localhost/MvcApplication1/ and an IIS error HTTP Error 403.14 - Forbidden The Web server is configured to not list the contents of this directory..

It's clear that for whatever reason, ASP.NET routing is not working correctly.

Things I've already thought of and tried:

  • Verified that all IIS features are enabled in "Turn Windows features on or off".
  • Verified that the default website is configured to use .NET 4.0
  • Reassigned ASP.NET v4 scripmaps via aspnet_regiis -i in the v4.0.30319 directory.

Here's the most amazing part - this is on a just-built machine. New copy of Windows 7 x64 Ultimate, clean install of Visual Studio 2010 Premium, no other websites and no other work performed.

Anything else I can try?

Setting Visual Studio to use local IIS web server

A: 

I've always used the custom server setting in VS 2008, which still allows me to debug with no problems. Not sure if it works any differently in 2010

Daniel Schaffer
+11  A: 

Ok, this is resolved for me, by doing the following:

Running aspnet_regiis -i in the 32-bit directory c:\Windows\Microsoft.NET\Framework\v4.0.30319.

At this point, I don't understand why 64-bit mode isn't working, but I'm now unblocked. Hopefully this helps anyone else who is having this issue.

Portman
I hope it helps me too ... I will try your way now
jalchr
This was driving me crazy, how frustrating... fixed now. Cheers
Rohan West
You should accept your own answer since this is the solution. By the way, thanks a lot! This saved me a lot of time.
Alex
Thanks a bunch, this was driving me crazy!
mynameiscoffey
+5  A: 

Hi Portman. I had exactly the same issue, so thanks for your help.

However... did you try running the aspnet_regiis -i command in the Visual Studio 64 bit command prompt (with admin privileges)? When I did that it fixed it for the 64-bit mode.

To clarify, I right clicked on Visual Studio x64 Win64 Command Prompt (2010) and chose Run as Administrator. Then I went here:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319

And did this: aspnet_regiis -i

And now it works perfectly.

Dommer
Worked great, thanks!
BigJoe714
+3  A: 

Also ensure that you configuration file has the following line otherwise the routing will not work.

<system.webServer>
  <modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
Rohan West
A: 

thanks it worked fine @dommer

Blottt
Glad I could help!
Dommer
A: 

OMG I cant belive it actually drove you crazy! if you go to inetmgr, click on the web site you are working in, you will see right in the middle of the inetmgr, an option with a name called 'Directory Browsing', go to it and click on enable on the right hand side. It is as simple as that.

PrincessP