• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1899
  • Last Modified:

Error coming while deploying MVC3 app on IIS7.5 windows7 : HTTP Error 404.0 - Not Found,Error Code 0x80070002


I am trying to deploy my mvc3 application on local IIS7.5 on windows7 but i am getting error i tried to deploy the brande new mvc app but that also getting same error and error is

Error Summary
HTTP Error 404.0 - Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Detailed Error Information


IIS Web Core





Error Code


Requested URL


Physical Path


Logon Method


Logon User


Most likely causes:•The directory or file specified does not exist on the Web server.
•The URL contains a typographical error.
•A custom filter or module, such as URLScan, restricts access to the file.

Things you can try:•Create the content on the Web server.
•Review the browser URL.
•Create a tracing rule to track failed requests for this HTTP status code and see which module is calling SetStatus. For more information about creating a tracing rule for failed requests, click here.

Links and More Information This error means that the file or directory does not exist on the server. Create the file or directory and try the request again.
View more information »
  • 2
2 Solutions
1. Try adding the following to your web config:

    <modules runAllManagedModulesForAllRequests="true" />

if this does'nt solve your issue, try the below

The code relays on the auto-start functionality that is available only in IIS 7.5. Try to discover the issue with the help of the Failed Request Tracing feature in IIS, and then modify the global.asax.cs file so that the application will be properly initialized, regardless of how/when it is loaded.

The class defined in global.asax.cs file (MvcApplication) implements IProcessHostPreloadClient to take advantage of the IIS 7.5 auto-start functionality. Therefore, move all of the code that is in Application_Start to the Preload method. In order to support cases where the auto-start functionality isn't used, call Preload from ApplicationStart. To ensure Preload only gets called once, use a static Boolean field that is checked to determine if the Preload method was previously executed.
farjack1Author Commented:
I fixed the problem, Answer is:

If issue in deployment then run utility
“C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i”



Make sure
applicationHost.Config  make sure overrideModeDefault = ‘Allow’

<section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Allow" />

Make sure app have permission like
farjack1Author Commented:
Expert gave me some idea

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now