FIX: EventLogEntry Class May Cause Leaks in Thread Local Storage and Event ID 4199 Event Log Entries

This article has been archived. It is offered "as is" and will no longer be updated.
When you gain access to the EventLogEntry class in the System.Diagnostics namespace, a leak in Thread Local Storage (TLS) may occur. This leak causes Event ID 4199 event entries in the Application event log. The event description appears similar to the following:

Event Type:      ErrorEvent Source:    COM+Event Category:  ExecutiveEvent ID:        4199Date:            4/11/2003Time:            11:42:07 AMUser:            N/AComputer:        <Computer Name>Description:The COM+ Services DLL (comsvcs.dll) was unable to load because allocation of thread local storage failed. Process Name: ReadEventLog.exeError Code = 0x80070008 : Not enough storage is available to process this command.COM+ Services Internals Information:File: .\comsvcs.cpp, Line: 289

A combination of two problems causes this issue:
  • The EventLogEntry class incorrectly loads the event log entry message file DLL as an executable module instead of as a data file.
  • A TLS index leak occurs when loadlibrary is called against the DLL (Comsvcs.dll, in this case). This Comsvcs.dll leak occurs only on computers running Microsoft Windows 2000. A fix for this problem is available in COM+ Rollup 27.

    Note Other DLLs may also experience the same TLS index leak behavior (the small computer system interface (SCSI) device driver for Tivoli Storage Manager (Adsmscsi.sys) is a known file that experiences this behavior). When a different DLL experiences this problem, the same 4199 event log entry appears. However, the entry has a different Event Source and Description.
The following hotfix is for the System.Diagnostics.EventLogEntry class in the .NET Framework.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework Service Pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) 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   ------------------------------------------------------------------------   23-Jan-2003  03:24  1.0.3705.396  1,171,456  System.dll   23-Jan-2003  03:24  1.0.3705.396    311,296  System.runtime.remoting.dll   23-Jan-2003  03:24  1.0.3705.396    503,808
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 812280 - Last Review: 10/26/2013 10:32:00 - Revision: 2.0

Microsoft .NET Framework 1.0

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbnetframe100sp2fix kbnetframe100presp3fix kberrmsg kbfix kbbug KB812280