WebApi Application: Error 404.0, Handler StaticFile

12,849

Microsoft should definitely put a version at "ASP.NET" Feature in the installer.

WHen you install ASP.NET feature on Windows 2008, this enables ASP.NET 3.5, while I require ASP.NET 4.

So after having installed .NET Framework v4, I would go forward and register ASP.NET 4 with IIS:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319> .\aspnet_regiis.exe -i 

Source:

https://alexanderzeitler.com/articles/HTTP-Error-4040---Not-Found-(MapRequestHandler--StaticFile)-when-deploying-WCF-Web-API-on-IIS-7x/

Share:
12,849
Alexander
Author by

Alexander

There are two hard things in computer science: cache invalidation, naming things, and off-by-one errors.

Updated on July 26, 2022

Comments

  • Alexander
    Alexander almost 2 years

    I just tried to deploy a WebApi application on a Windows 2008R2 with IIS 7.0, with IIS Manager untouched until now.

    The App runs on our dev server (same Win and IIS version) without hassle. On the deployment server,

    • .NET Framework 4.5 is installed,
    • ASP.NET Feature is installed and
    • Windows authentication is installed

    When I call an URL that should map to ASP.NET, the error is

          HTTP Error 404.0
    
           Module IIS Web Code
     Notification MapRequestHandler
          Handler StaticFile
       Error code 0x80070002
    Requested URL http://localhost:80/myapp/api/GetUserConfig
    Physical Path C:\inetpub\wwwroot\myapp\api\GetUserConfig
     Logon Method Negotiate
       Logon User ADDOMAIN\Administrator
    

    Handler StaticFile seems important - as far as I can tell, the cause is that ASP.NET does not correctly handle the URL. Where can I start searching for the actual root of this problem?

    I should add that multiple other deployments, all in Windows 2012 environments, were successful.