Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an Asp.NET MVC WebApi application that works perfectly in development environment does nothing but return 404 errors when deployed to testing server.

  • Application is Framework 4.5
  • dotNET Framework 4.5 is installed on the server
  • Framework 4.5 installation has been confirmed in the registry using regedit
  • Ran "aspnet_regiis -i"
  • Using an application pool configured for .NET Framework v4.0.30319
  • Pipeline mode is 'Integrated'
  • Identity is 'Network Service'
  • 'ASP.Net_4.0_32bit' 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll'
  • 'ASP.Net_4.0_64bit' 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_filter.dll'

Thank you in advance for any insight on getting this working. Jim

share|improve this question

closed as too broad by Greg Askew, Ward, MadHatter, mdpc, HBruijn Nov 10 '15 at 16:21

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

Is the correct version of ASP.NET MVC also installed on the server? – Chris McKeown Aug 20 '13 at 21:04
First thing with any IIS 404s is to get the sub-status from the http logs. They should point you in the right direction. – Peter Hahndorf Aug 31 '13 at 7:17

I know this is an old question but I came upon it looking for something else.

If you experience this issue use Fiddler to trace out the request. There is sometimes the possibility that it really is a 404 error because you are expecting a different URL path.

For example...Say I have an application called CatPurchaser. I deploy it to a server and then later call on a built in API. I expect to be able to call "/WebAPI/Cat/123". But instead of that, I actually should have called "CatPurchaser/WebAPI/Cat/123" because it is a virtual application on my IIS server.

Hopefully that makes sense.

Fiddler Link:

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.