You Receive HTTP 500 Error Messages After You Bring an MCMS Server Online (814775)
The information in this article applies to:
- Microsoft Content Management Server 2002
For a Microsoft Content Management Server 2001
version of this article, see
814526. SYMPTOMSBecause of the way Microsoft Content Management Server (MCMS) retrieves resources from its SQL
database, you may receive HTTP 500 error messages in the browser. You may also notice that IIS starts to log errors in the event log, or you may see memory use increase when you view Performance Monitor memory counters. CAUSEThis behavior may occur if the threads that the MCMS process creates are not
cleaned up from memory correctly so that "orphaned" threads occur. As the number of orphaned threads increases in memory, less and less
memory is available for new process threads. Eventually all available
memory is consumed, and IIS starts to return HTTP 500 error messages.RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for Microsoft Content Management Server 2002. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
906142 How to obtain the latest Content Management Server 2002 service pack
Hotfix information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
--------------------------------------------------------------
18-Feb-2003 00:58 5.0.1592.0 138,752 Aesecurityservice.exe
10-Dec-2002 21:52 4.0.1381.4 65,600 Cmsupdate.exe
18-Feb-2003 01:54 1,673 Update.inf
Note Because of file dependencies, this update requires Microsoft Content
Management Server 2002.
MORE INFORMATIONYou
may be able to resolve the problem temporarily by resetting the Internet Information
Services (IIS) by using either the IISRESET command or by using NET STOP IISADMIN. However,
the problem eventually recurs because memory is gradually consumed
again.STATUSMicrosoft has confirmed that this Is a problem In the Microsoft products that are listed In the "Applies To" section.
This problem was corrected in Content Management Server 2002 Service Pack 1.
Modification Type: | Major | Last Reviewed: | 12/7/2005 |
---|
Keywords: | kbContentMgtServ2002sp1fix kbHotfixServer kbQFE kbfix kbbug KB814775 |
---|
|