Howdy All,
This is a common problem I see lots of people running into since GoDaddy upgraded from IIS 6 to IIS 7. The below story is a similar situation that I had while trying to work on a Classic ASP web site hosted at GoDaddy. I have included the answer/fix below.
Original Story: I am with godaddy for webhosting right now. The have me using IIS7.
When I run my ASP page I get the error :
Error 500 :There is a problem with the resource you are looking for,
and it cannot be displayed.
Basically, there is an error in my code, however, it doesn’t tell me
the line number the error was found on. After searching the web I
found out how to turn on the more detailed error reporting… but you
have to do it on the webserver. I don’t have access to the webserver.
After spending allot of time chatting with godaddy, they claim I can
turn this on in the web.config file. I know this can be turn on for
ASP.NET in the web.config file… but as far as I know, not classic
asp.
OK…. Here is the web.config file I use that gives you the old school error handling data:
Step 1. Open a text document.
Step 2. Insert this code:
<configuration>
<system.webServer>
<httpErrors errorMode=”Detailed” />
<asp scriptErrorSentToBrowser=”true”/>
</system.webServer>
</configuration>
Step 3. Save the file as Web.Config
Step 4. Upload the Web.Config file to your host web directory.
I hope this helps people avoid the few hours I was on the phone with GoDaddy technical support. 
Please let me know if this helps anyone out.
Hi, thanks for the advice about enabling detailed classic ASP errors in IIS7. I tried your solution but now when I go to the page with the error all I get is:
HTTP/1.1 New Application Failed
Any ideas?
Not sure, you may want to paste your code into this thread and see if anyone has any ideas.
HTTP 500.100 – Internal Server Error – ASP error
Internet Information Services
Technical Information (for support personnel)
* Error Type:
Microsoft VBScript runtime (0x800A01A8)
Object required: ‘Application(…)’
/weekly/include/auth_lib.asp, line 372
* Browser Type:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 (.NET CLR 3.5.30729)
* Page:
POST 18 bytes to /weekly/godaddy_error_handling_test.asp
* POST Data:
Continue2=Continue
* Time:
Tuesday, April 27, 2010, 1:26:42 PM
* More information:
Microsoft Support
I have 100 domains on Godaddy and i can say that this company is very reputable..;`
Not sure, you may want to paste your code into this thread and see if anyone has any ideas.
OK I just reviewed the analytics/traffic for this article. This article gets about 50 visits per day for people searching for web.config error handling. However, hardly anyone takes the time to comment and/or interject their experiences to help others.
So please let us know your findings and/or solutions to this type of problem by commenting to this post.
Thanks, Admin – Ryan_SEO_Jennings
Still getting the same problem. Probably going to just cancel my hosting account with GoDaddy and setup a PHP/Apache setup out of my home. Sad.
I tried this. Didn’t get any change in my page results. It still tells me nothing more than “Error 500″.
Off to find some other solution.
Thanks anyhow.
Hello,
thanks to your solution, I was able to eliminate the ambiguous error messages and reveal the source of the issue. This trick has been most helpful and plan to use it in future developments.
Thanks,
Godaddy has great prices on .info domains but their private domain service is so damn expensive,`’
My web.Config file works on GoDaddy and shows detailed error messages:
Uploaded to the root directory in my hosting account.
Perform following steps, it will 100% resolve it
1. Open IIS Manager
2. Select your Site
3. In Icon Pane, select Error Pages having 404 icon.
4. Double Click it and you will find 401, 403 and blah blah errors
5. Now look at the right side of your screen, you will find Edit Feature Setting under Action Panel.
6. Click it
7. Select Detailed Errors
8. That’s all.. enjoy the errors
Regards,
Paresh