thanks for heads up.

Recently GoDaddy moved my site to a new server with updated software. The new server and applications broke a few features, and have forced me to do a total review and unit test to discover what got broken. My Dev site is total toast, and forced me to do most of maintenance on the live site (shy). Today, when time permits, I am going to try to revive the Dev site.

>So if everything is ok now you should switch back to
>debug="false"
>to prevent giving too much error information that can be used with harmful intentions.
>
>Bruno
>
>>I received a reply from the support team of GoDaddy. They placed a Web.Config file (with my permission) into the root folder of my web site. This resolved the issue. I am providing a image of the Web.Config as an attachment.
>>
>>>In your Web.config
>>>put the element:
>>>
>>>->configuration
>>> ...
>>> ->system.web
>>> ->compilation
>>> debug="true"
>>> ...
>>>(close tags)
>>>
>>>Note: I tried to insert in < PRE> < / PRE> the XML syntax but doesn't show.
>>>
>>>HTH
>>>Bruno
>>>
>>>
>>>>Morning,
>>>>
>>>>How can I get real error information like the ASP file name, Line Number, error message as o what went wrong. My web site host recently updated their system, and since then if an error occurs it return a "500 (internal Server) error" page. I have contacted GoDaddy, but they have not been much help. I am looking for a way to trap the error and display the details of the error. "ON ERROR" should be the answer but I can not get it to trap the error before the server throws the Error 500. I am assuming it has something to do with the parsing and/or compiling of the vbscript / javascript code in the ASP page.
>>>>
>>>>Any suggestion is welcome.
>>>>
>>>>Greg