Asp.net mvc 4 on iis6: "The page cannot be found"

Question

I am having trouble getting ASP.Net MVC 4 running on IIS 6.

First, i got "Directory listing denied" and that already solved after I setup extensionless urls based on Phil Haack's blog post: ASP.NET MVC on IIS 6 Walkthrough.

Now, I'm getting "The page cannot be found" 404 page.

It's a simple ASP.Net Web Api project in MVC 4 beta.

Sounds like a routing problem. What URL are you trying to request? — mgnoonan, Mar 23 '12 at 23:52
I don't think so. it works on my laptop (Windows 7 - IIS7). but when I upload to Windows Server (IIS6), doesn't work on any url. — Anwar Chandra, Mar 24 '12 at 08:04

score 44 · Accepted Answer · answered Mar 25 '12 at 10:42

44

Under application configuration, I insert wildcard extension mapping to:

c:\windows\microsoft.net\framework\v4.0.30319\aspnet_isapi.dll

But I forgot to un-check on Verify that file exists checkbox.

answered Mar 25 '12 at 10:42

Anwar Chandra

8,538
9
45
61

3

I really hate that checkbox – NickSuperb Dec 10 '12 at 18:06
Wow... something so insignificant as a little checkbox causes the entire MVC site to burn in flames. Go figure. – brazilianldsjaguar Apr 19 '13 at 19:52
@AnwarChandra, I have followed option 1, 2 & 3 from this blog "http://blog.stevensanderson.com/2008/07/04/options-for-deploying-aspnet-mvc-to-iis-6/" so far but nothing works! – DOM May 09 '13 at 10:08
@DOM you should post your own question on SO with more details. – Anwar Chandra May 12 '13 at 10:03
This Q&A would be a lot better if it contained the info from the link in the comments here and also the link in the original question, as neither of those links are valid now. Dang, probably some good answers there... guess I'll keep looking. – eselk Dec 04 '13 at 03:57

score 3 · Answer 2 · answered Aug 16 '13 at 06:52

3

I fixed this problem using these steps:

Open IIS Console
Select “Web Service Extensions
Select “ASP.NET v4.0.30319”
Click Allow

answered Aug 16 '13 at 06:52

Igor Krupitsky

787
6
9

score 0 · Answer 3 · answered Oct 21 '14 at 19:34

Most of the time the usual configuration worked for me (wildcard map, uncheck verify...) but it stopped working recently on one Windows 2003 server. I discovered that the previous "Publish..." was done with "precompile" option, which resulted in the App_global.asax.dll and .compiled files in /bin. They were later deleted by mistake during some incremental manual deployment and the Web Api routes were no longer being registered.

I copied the old bin/App_global.* files to server and it worked again.

I also found that to achieve the same effect you can delete the /PrecompiledApp.config file and make sure the /global.asax exists

Asp.net mvc 4 on iis6: "The page cannot be found"

3 Answers3