IIS Hangs When the Custom Error 500-100 Is Mapped Incorrectly (247605)


The information in this article applies to:

  • Microsoft Windows 2000 Server
This article was previously published under Q247605

SYMPTOMS

When you create two applications in Internet Information Services (IIS) 5.0, both with the same physical path, and map a custom error 500-100 for the first application to the URL of the second, IIS stops responding (hangs) during requests by the first application.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows 2000 Server.

MORE INFORMATION

This problem occurs under the following set of conditions:

  1. There must be a preprocessor (not a runtime or compilation) error in the error page.
  2. The error page must exist in an application with the custom error pointing to itself.
  3. The user must be invoking the error page explicitly.
Modification Type:MajorLast Reviewed:10/9/2002
Keywords:kbbug KB247605
©2002 Microsoft Corporation. All rights reserved.