Hi All,
Solved the problem I think.
This from the IIS 6 help file. As it was a new web site I
had to create an asp error processing file (actually I
copied 500-100.asp to a new virtual directory and then
mapped a custom error to it). I bit of fiddle but there we
are. Hoppefully I won't be doing anymore classic ASP sites.
Here is the extract from IIS help.....
"Enabling ASP Error Processing
By default, the default Web site and all of its
applications transfer the processing of Active Server
Pages (ASP) errors to the 500-100.asp file. However, any
new Web site that you create, or its applications,
transfers the processing of 500-100 errors to the default,
and not to a custom error file. If you want to develop
additional error processing for .asp files, you can do so
by either mapping the 500-100 error to the 500-100.asp
file or by creating an error-processing .asp file of your
own."
Cheers
Mark
-----Original Message-----
Hi All,
I'm having a frustrating time trying to debug an ASP (not
ASP.NET) app on my W2003 dev server running II6.
I continually get a HTTP 500 error message despite
configuring IIS 6 to enable ASP debugging and to send
detailed error message to the client.
Any ideas anyone?
Cheers
Mark
.
