HTTP/1.1 New Application Failed

Question

i just moved from my old host to Godaddy, which seems to be a worst web host with no support.

i moved my asp website (written in classic asp) to the new godaddy windows hosting. but when i run the site i get the below error

HTTP/1.1 New Application Failed

this site worked perfectly with my previous host.

below is what i have in my web.config file

<?xml version="1.0"?>
<configuration>
    <system.webServer>
        <httpErrors errorMode="Detailed" />
        <asp scriptErrorSentToBrowser="true"/>
    </system.webServer>
    <system.web>
        <customErrors mode="Off"/>
        <compilation debug="true"/>
    </system.web>
</configuration>

can someone tell me why am i getting that error and how can i fix it?

any help will be appreciated.

Maybe this will help - [Run Classic ASP pages with IIS7](http://piyush-chawhan.blogspot.co.uk/2011/06/run-classic-asp-pages-with-iis7.html) suggestion is the `
` should be `
` in the `%systemroot%\System32\inetsrv\applicationHost.config` config file which if you're on shared hosting I doubt you'll have access to. Sounds like GoDaddy might not be supporting Classic ASP by default. — user692942, Aug 15 '14 at 14:36
Actually came across this recently myself, it occurs after renaming a website. The fix is to stop and start the associated Application Pool so it is aware of the website name change, until you do you will get this error. — user692942, Mar 24 '17 at 12:41

score 24 · Accepted Answer · edited Feb 28 '19 at 18:30

24

I had the same issue moving a website from one hosting account (classic windows) to another (plesk), both on GoDaddy. After much headache troubleshooting, I managed to fix it by removing the whole <asp> tag from the web.config file;

    <!-- <asp scriptErrorSentToBrowser="true"/> -->

IIS 8 (only option in plesk) does not support this option altogether and configuring detailed error messaging is done differently using:

    <httpErrors errorMode="Detailed" existingResponse="PassThrough" />

You can find further instructions on this GoDaddy support page

edited Feb 28 '19 at 18:30

Kebab Programmer

1,213
2
21
36

answered Feb 03 '15 at 06:29

Canica

2,650
3
18
34

Before using this suggestion, consider recycling the application pool or restart iis service as described in the other answer and see if the problem goes away. – Salman A Apr 18 '23 at 07:27

score 11 · Answer 2 · answered May 10 '16 at 07:42

11

I just encountered the same error this morning after renaming some Websites in IIS. A restart of IIS got my sites up and running again in seconds. Presumably the .config files are read on startup and 'likely' the cause of this error for me.

answered May 10 '16 at 07:42

Richard Hetherington

181
2
4

Worked for me too. – BoffinBrain Sep 01 '17 at 10:37
Thank you so much. I had changed the names of my sites to their actual domain.com, and that is what did it. But the strange thing is only one site was not affected by this change? Go figure. Thank you so much. – CodingEE Apr 18 '20 at 10:49
To add a brick on the wall, just had the same problem, and restarting the Application Pool is enough – iguypouf Jun 19 '20 at 14:25
2

Easy enough to replicate in IIS (tested in 8.5 anyway). Create a website, view the default page (or set one up). Rename the site (under the 'Sites' tree-view) in Internet Information Service (IIS) Manager, and try to browse the site again (right click on site > Manage Website > Browse). If you followed steps like that at any stage, you might have received: **HTTP/1.1 New Application Failed**. The answer: ```Restart IIS```. Or as @iguypouf suggests STOP the associated Application Pool, and START it again (may involve: Error 0x80070425 prompt, click OK, Start again) or revert rename. – Jonno Aug 06 '21 at 08:57

HTTP/1.1 New Application Failed

2 Answers2

Linked