Deploy asp.net mvc beta to iis 6 causing 404's

Question

I'm struggling to get around the 404 errors from asp.net mvc beta when deploying on IIS 6. I had this working in one of the previews by mapping .mvc in IIS but this no longer works. I've read Omar's post and several others on the web and tried their solutions but no luck so far.

The home page opens without a problem on IIS 6 but others 404 and the site runs well on IIS 7.

Has anybody deployed asp.net mvc beta to IIS 6 with success? If so, what adjustments did you need to make to the code and/or IIS settings to get it to work?

For S&G's... check your wildcard mapping. Is that little checkbox "Check that File Exists" checked? I hate that little bastard. — user1228
– user1228, Commented Oct 27, 2008 at 14:52

Majid Basirati · Accepted Answer · 2019-01-12 05:39:09Z

26

I found a solution to my problem from Steve Sanderson's blog (Thanks Steve):

Use a wildcard mapping for aspnet_isapi.dll. This tells IIS 6 to process all requests using ASP.NET, so routing is always invoked, and there’s no problem. It’s dead easy to set up:

open IIS manager (run -> inetmgr -> OK)
right-click your app, go to Properties
then Home Directory tab, then click Configuration.
Under Wildcard application maps, click Insert (not Add, which is confusingly just above)
then enter C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll for “Executable”, and uncheck Verify that file exists.

edited Jan 12, 2019 at 5:39

Majid Basirati

2,9053 gold badges28 silver badges47 bronze badges

answered Oct 27, 2008 at 15:36

Guy

67.7k101 gold badges268 silver badges333 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Chris Van Opstal Over a year ago

Perfect! This solved my problem after an hour and a half of banging my head against a wall.

pauldunlop Over a year ago

Great fix. Saved me A LOT of time. Thanks

TheHolyTerrah Over a year ago

What a pain that was! In the immortal words of Napoleon Dynamite: "Flippin' Sweet!"

TweeZz · Accepted Answer · 2011-01-04 15:07:02Z

5

I can't seem to write comments yet. So I'll write a new answer.

There are a few similar questions going around on stackoverflow. I'm using MVC 3. I know the question was MVC 2 related. But since this is the first stackoverflow post I bumped in to, I think it's worth mentioning that:

when you use MVC 3, you need to add a new extension mapping with the executable of the .NET 4 framework (C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll)

<edit>I just found out that I even don't need to set up the extension mapping. </edit>

It still didn't work for me then :) I still had to 'Allow' ASP.NET v4.0.30319 in the Web Service Extensions section in IIS:
- open IIS
- click on the server node
- open the Web Service Extensions section
- select the ASP.NET v4.0....
- right click --> Allow Good to go!

answered Jan 4, 2011 at 15:07

TweeZz

4,9695 gold badges42 silver badges53 bronze badges

1 Comment

IronicMuffin Over a year ago

Thank you, that Web Service Extensions helped me out. Why would it default to Prohibited on a fresh install??

Community · Accepted Answer · 2020-06-20 09:12:55Z

1

Url rewriting can help you to solve the problem. I've implemented solution allowing to deploy MVC application at any IIS version even when virtual hosting is used. http://www.codeproject.com/KB/aspnet/iis-aspnet-url-rewriting.aspx

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Nov 24, 2009 at 6:22

Alex Ilyin

1,3041 gold badge12 silver badges22 bronze badges

Collectives™ on Stack Overflow

Deploy asp.net mvc beta to iis 6 causing 404's

3 Answers 3

3 Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

3 Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related