IIS6: Detailed errors to the client

Hi!

We've recently migrated a IIS4 site to a machine running Win2003 and IIS6 using the IIS6.0 Migration Tool. When running IIS4 we got detailed error messages sent to the client, stating error, file name, line number, etc. This does not happen on the IIS6 server, even though the AspScriptErrorSentToBrowser property is set to TRUE.

I've tested with a very simple ASP file that attempts to do Server.CreateObject on a non-existing object. The client just displays a standard error 500 message while the detailed error is being logged to the IIS log file. What am I doing wrong?


Regards,

Jonas Berling

Is this the same client. The client has the option of showing friendly http error messages, which we recommend turning off when encountering errors.

Thank you. I hope this information is helpful.

Tim Coffey [MSFT]

This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft Corporation. All rights reserved.
--------------------
| Thread-Topic: IIS6: Detailed errors to the client
| thread-index: AcODZcbL2BcE6BVTTiaZYVpCqVII/g==
| X-Tomcat-NG: microsoft.public.inetserver.iis
| From: "=?Utf-8?B?Sm9CZQ==?=" <anonymous DeleteThis @discussions.microsoft.com>
| Subject: IIS6: Detailed errors to the client
| Date: Thu, 25 Sep 2003 06:06:04 -0700
| Lines: 10
| Message-ID: <BBE46F4D-73B7-44B9-BEDA-06983EAAE83F DeleteThis @microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.inetserver.iis
| NNTP-Posting-Host: TK2MSFTCMTY1 10.40.1.180
| Path: cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:277083
| X-Tomcat-NG: microsoft.public.inetserver.iis
|
| Hi!



We've recently migrated a IIS4 site to a machine running Win2003 and IIS6 using the IIS6.0 Migration Tool. When running IIS4 we got detailed error
messages sent to the client, stating error, file name, line number, etc. This does not happen on the IIS6 server, even though the
AspScriptErrorSentToBrowser property is set to TRUE.



I've tested with a very simple ASP file that attempts to do Server.CreateObject on a non-existing object. The client just displays a standard error 500
message while the detailed error is being logged to the IIS log file. What am I doing wrong?





Regards,



Jonas Berling
|