Hi:

I can't make the IIS for Windows 2003 return detailed errors for debugging.

I've set the Config >> Debug for debugging on the server and selected send detailed error messages to the client. I also went into DComCnfg and set the IUSER account to launch and run, umm what was it? I can't remember, system services?

Anyway, no matter what I do that stupid server will NOT display any page with ANY problem on it and WILL NOT tell me what it's problem is.

How can I make it display the page anyway (would be real nice) and/or return me an error I can use?

__________________
http://www.softlinksys.com
Professional Software Developer since 1994.

Is the problem only with .asp pages, or do you get the same problem for a .htm as well?

Hmm, I have to say ASP.
I'm not looking for client side errors.
I'm looking for errors that the ASP script caused on the server side.
Also, if I could find a way to get it to do it, I'd love it if it'd display the page up to the point where it has the problem.

Sure, just trying to work out where the problem is, have you enabled asp pages (you can do this in the "web service extensions" node of the iis manager tree)?

Oh, I'm thinking I wasn't clear.
Most of my ASP pages work fine.
WHEN there's a problem with a page, the server won't return the errors, it just says 'cannot display the page . . . " I think it's a 504? error? Just a generic message. I need the details. That is, the page and the line of code that crashed.

Has your browser been set to return friendly error messages?
In IE this would be in tools -> internet options -> advanced -> show friendly http error messages

Yes. I should probably mention that I've been writing ASP applications for about 10 years.
Also, one of the servers that I'm having a problem with used to return the errors for me.
My client got a new network engineer, who reconfigured the server. Now it won't return errors and the network engineer doesn't know why or how to fix it.

The answer to the previous question should be no.

Which error are you getting (I don't think IIS has a 504 error)?

I don't think you understand the problem.
I can produce the error by causing ANY SERVER SIDE SCRIPT PROBLEM

The problem is that it WON'T RETURN AN ERROR that gives me the page and line or any indication as to the cause of the problem.

It's not specific to one problem. In this case (shown below) I intentionally called a database with an incorrect path just so I could produce the error.
Having fixed the database path, the page displays normally.

Again, my problem is:
"I can't make the IIS for Windows 2003 return detailed errors for debugging."

-----------
The page cannot be displayed
There is a problem with the page you are looking for, and it cannot be displayed.
--------------------------------------------------------------------------------

Please try the following:

Contact the Web site administrator to inform them that this error has occured for this URL address.
HTTP Error 500 - Internal server error.
Internet Information Services (IIS)

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search for the words HTTP and 500.
Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Web Site Administration, and About Custom Error Messages.
In the IIS Software Development Kit (SDK) or at the MSDN Online Library, search for topics titled Debugging ASP Scripts, Debugging Components, and Debugging ISAPI Extensions and Filters.
-----------------------------------------------

Yes, I saw you other post. IMO I think your problem should remain here as there is a history - EG:
others will ask about friendly error etc which has already been covered.

Anyhow
I was not aware of a 504 error either, it seems:
504 = Gateway timeout. Are you using CGI or the like? If so remove this code and run the page, still a 504?

You answered yes to the question "Has your browser been set to return friendly error messages?" As Chris said your answer should be no. Make sure this box is not checked.

I have used IIS 6.0 a fair bit. There is no setting that need to be swithched on to allow errors, this I know. Network admins should stay away from IIS. He doesnt know what he done, thats a worry.

Wind is your friend
Matt