Oh, sorry !*&@!#^!@ No, 'friendly error messages' is set to NO. <thunk>

The '504' error was my error. I posted the actual message in detail above.

Who would normally be responsible for maintaining IIS configurations?
Also, he's not a network 'Admin', he's an MCSE and is a consultant.

Actually, there is a setting:
Properties >> Home Directory >> Configuration >> Debugging
'Enable ASP Server Side Script debugging' must be checked and it is;
'Send detailed ASP error messages to client' must be checked and it is.

So far nothing works. It won't return valid errors.

Seems you missed this question:
;;;504 = Gateway timeout. Are you using CGI or the like? If so remove this code and run the page, still a 504?

;;;The '504' error was my error. I posted the actual message in detail above
I can see details for a 500 above, not a 504.

;;Who would normally be responsible for maintaining IIS configurations?
default web site and its content (other sites) would be the developer in my environment.

About those settings, these are on by default. notice I said "that need to be switched on"

Anyhow - I guess you missed the question in my post that had the most to do with solving your problem.


Wind is your friend
Matt

If the error shown is a 500...
Have the custom error mappings been altered for 500;100?
Is the file c:\windows\help\iishelp\common\500-100.asp present on the server?

It's NOT a 504 error and I'm not using cgi.
I posted the error that I'm getting, above.
You are correct, the settings are set as the default but at this point one may not know if they have been changed.

I checked the mappings. For the 500;100 it's set to 'Default'. The description is 'Internal Server Error.' Also, the file is present in the c:\windows\help\iishelp\common folder.

I should probably add that at one point I changed the mapping for the 500;100 to the ASP file you mentioned. When I ran it, it showed the ASP code instead of executing it.

OK, I guess that was because it was a file mapping and not a url.

Try creating a new virtual directory under your site, copying the 500-100.asp file into it and setting the custom 500;100 error to type url mapped to the file in the virtual directory e.g. /[your virtual directory]/500-100.asp

OK, I've created a virtual directory 'Errors' and pointed it directly at the c:\windows\help\iishelp\common folder.
I remapped the 500 error to a URL which is '/Errors/500-100.asp'.

I need to mention that somehow Exchange Server and a whole bunch of other crap is using the IIS for something. There's this list of 'Child Nodes' that override the setting. I selected 'public' as the only child node that will be reset to use it.

Right now the IIS is hung up. This is the second time it's done that. I can't reset it because I don't have permissions to the IISAdmin service.

I'll let you know what happens once this network engineer resets it.

Chris Scott:

I *FINALLY* got that silly server to give me detailed error messages.

Part of the problem was that the new IT team set the MDM service to run which was kicking the MS Script Debugger on every time an error occured. That locked the IIS up.
We shut that off and it stopped locking up.

Then I took your suggestion to create a virtual directory which I called 'Errors' and I mapped the 500 error to a URL to that directory & the 500-100.asp file.

It worked!
The server is returning detailed error messages now like it should.

Thanks for your help:o) !!

I just ran into the same problem. As a default, Microsoft locked down everything. We had enabled ASP pages, but some of my pages still blew up. After more researching we realize it was due to our "relative references" (ex: ../image1.jpeg). For security reasons they don't prefer you using relative paths. The solution, either modify the references to that virtual/absolute path. Or what we did, was to find an option to allow "relative path". I forgot where this option is...but it's in the IIS settings. After this, everything worked