15

I have deployed an MVC 4 web-site to a Windows 2008 R2 server with IIS 7.5. .NET 4.5 is installed on the server.

The site works fine locally. All routing works fine. However, when I put it on the server, nothing works. I have confirmed that the DNS/binding is working by putting a static text file in the site and this works.

Here's a few things I've tried:

I have tried/confirmed:

Am I missing something? My next act of desperation is to install the full ASP.NET MVC 4 stack including Visual Studio Express, SQL Express, etc. just to see if it works. Which I really don't want to do. This is a production server!

Update: I should add that the same site works on en equivalent configuration in-house, on a staging server.

Program.X
  • 7,250
  • 12
  • 49
  • 83

1 Answers1

19

I had this same issue. There's a hotfix you should try: http://support.microsoft.com/kb/980368 It fixed the issue for me.

David Hollowell - MSFT
  • 1,065
  • 2
  • 9
  • 18
  • Wow. How did you find that. Thanks, sorted! – Program.X Sep 21 '12 at 14:29
  • I found your post and this hotfix while searching this very issue. Figured I'd share my answer, since I tried all the same things you did, and this was very frustrating. – David Hollowell - MSFT Sep 22 '12 at 15:26
  • 2
    it's worth noting this hotfix is rolled into SP1 for Server 2008 R2. Also, if after applying that hotfix, other things might start to break (i.e. a custom module that does extensionless routing).. If so, look at http://support.microsoft.com/kb/2522807 – jons911 Jan 24 '13 at 01:27
  • 1
    Related http://stackoverflow.com/questions/12495346/asp-net-4-5-mvc-4-not-working-on-windows-server-2008-iis-7 – chrisortman Feb 14 '13 at 00:52
  • That hotfix no longer seems to be available. Does anyone know where I can get it? – Paul Taylor Mar 13 '13 at 15:17
  • We have had that error on a single developer machine and searched that damn problem for about 8 hours! Then the hotfix fixed the problem within seconds :) Thanks! – Pascal Mathys Mar 21 '13 at 22:53
  • 1
    FYI, this hot fix is rolled up in server 2008 r2 sp1. – Eric Brown - Cal Dec 15 '14 at 20:09