HTTP/1.1 New Application Failed ASP IIS

Question

I am trying to move a website from one server to another server but pointing to the same external database server. The error appeared was:

HTTP/1.1 New Application Failed

It was working in the previous server, and only in certain pages are working.

ASP is installed on the server role and tried edit the applicationHost.config to section name=”asp” overrideModeDefault=”Allow” but they didn't solve the issue. The application is the Default Web Site at the root directory in c:\inetpub\wwwroot\

Here's in web.config:

<system.webServer> 
  <defaultDocument> 
  <files> <clear /> 
   <add value="index.html" /> 
   <add value="Default.htm" /> 
   <add value="Default.asp" /> 
   <add value="index.htm" /> 
   <add value="iisstart.htm" /> 
   <add value="default.aspx" /> 
   <add value="index.php" /> 
  </files> 
  </defaultDocument> 
  <httpErrors errorMode="DetailedLocalOnly" /> 
</system.webServer>

Thank you.

I would temporarily remove the whole <asp> node from your web.config or even remove the whole web.config to see whether that makes a difference. — Peter Hahndorf
@PeterHahndorf tried but still. here's in web.config: <system.webServer> <defaultDocument> <files> <clear /> <add value="index.html" /> <add value="Default.htm" /> <add value="Default.asp" /> <add value="index.htm" /> <add value="iisstart.htm" /> <add value="default.aspx" /> <add value="index.php" /> </files> </defaultDocument> <httpErrors errorMode="DetailedLocalOnly" /> </system.webServer> — Amalina Aziz
I would check C:\Windows\System32\inetsrv\config\applicationHost.config for any <asp... nodes. By default there should only be one <cache> node. Also check the Windows application eventlog. — Peter Hahndorf
@PeterHahndorf there's only one node: <cache diskTemplateCacheDirectory="%SystemDrive%\inetpub\temp\ASP Compiled Templates" />. What should i check in the event log? — Amalina Aziz
@PeterHahndorf so i enabled error reporting and found that it is because the parent path disabled by default. Enabled it and it works! Thank you thank youuuu :D — Amalina Aziz

Peter Hahndorf Peter Hahndorf · Accepted Answer · 2016-08-25T11:28:34

The error:

HTTP/1.1 New Application Failed

can have multiple cases, but usually it occurs when the classic asp engine can not start due to some (mis-)configuration settings on IIS.

Often the <system.webServer><asp> in the site's web.config causes this error if Feature Delegation has not been changed to Read/Write on the server level.

To investigate this further make sure you send the proper ASP error message to the brower Send Errors To Browser under ASP-Debugging Properties

If you have IIS Management Scripts and Tools installed (which you should to manage IIS with PowerShell) you can use:

Set-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST' -location 'Default Web Site' -filter "system.webServer/asp" -name "scriptErrorSentToBrowser" -value "True"

If you still use IE disable Show Friendly http error messages

Also enable detailed error messages for the site:

Set-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST/Default Web Site'  -filter "system.webServer/httpErrors" -name "errorMode" -value "Detailed"

you should see a more specific ASP error, if this case it was a

ASP 0131 Disallowed Parent Path

Adjust settings or code to fix the problem.

When done, change the error settings back to the more secure defaults unless you are on your own dev machine.

HTTP/1.1 New Application Failed ASP IIS

2 Answers