CODEWITHSUNDEEP
asp-classic
LiveEn
LiveEn

Reputation: 3253

HTTP/1.1 New Application Failed

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.

Upvotes: 12

Views: 19834

Answers (3)

RAIMUNDOS54
RAIMUNDOS54

Reputation: 1

You have to be allowed to use the tag.

This configuration is found on the IIS applicationHost.config file:

%windir%\system32\inetsrv\config\applicationhost.config

Open your editor as administrator and set the value below to Allow instead of Deny. This section might be in the beginning of the file.

<configuration>
  <configSections>
    <sectionGroup name="system.webServer">
      <secion name="asp" overrideModeDefault="Deny" />
      (...)
      </section>
    </sectionGroup>
  <configSection>
<configuration>

If you don't have access to the applicationHost.config file, ask the support at GoDaddy or the administrator wherever it is to do this for you.

Upvotes: 0

Canica
Canica

Reputation: 2738

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

Upvotes: 24

Richard Hetherington
Richard Hetherington

Reputation: 301

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.

Upvotes: 12

Related Questions