The Framework.log file size exceeds the value that is set for the Log File Max Size subkey entry when you use WMI on a Windows Server 2003-based computer (891011)


The information in this article applies to:

  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, 64-Bit Enterprise Edition
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When you use Windows Management Instrumentation (WMI) and configure WMI to log events on a Microsoft Windows Server 2003-based computer, the size of the WMI Log file, FrameWork.log, may continue to increase even after the FrameWork.log file has exceeded the Log File Max Size subkey entry.

Note By default, the value of the Log File Max Size subkey is set to 64 kilobytes (KB).

CAUSE

This problem occurs when the Windows Server 2003 Network Service account does not have Delete permissions on the %Systemroot%\System32\Wbem\Logs folder.

RESOLUTION

Hotfix information

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 Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix 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.

IA-64 version of Windows Server 2003

   Date         Time   Version            Size    File name      Platform
   ----------------------------------------------------------------------
   10-Dec-2004  19:40  5.2.3790.241      612,864  Wbemcomn.dll   IA-64
   10-Dec-2004  19:40  5.2.3790.241    1,724,416  Wbemcore.dll   IA-64


x86 version of Windows Server 2003

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   10-Dec-2004  19:40  5.2.3790.241      216,576  Wbemcomn.dll     
   10-Dec-2004  19:40  5.2.3790.241      467,968  Wbemcore.dll

MORE INFORMATION

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

You can configure the WMI error log by changing the registry:
  • The destination folder for all log files is set by the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\LoggingDirectory
  • The maximum file size is set by the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Log File Max Size
The following registry subkey determines how the Windows Driver Model (WDM) provider logs errors: HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging

The logging entry uses the following values:
  • 0: Turns off logging
  • 1: Logs errors only
  • 2: Starts verbose logging
When a log file reaches the value set for the Log File Max Size subkey entry, the log file is backed up to Log_file_name.lo_ and a new log file starts collecting entries. The only exception is the Framework.log file. The Framework.log file may continue to increase even after the file exceeds the value set for the Log File Max Size subkey entry.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbQFE kbHotfixServer kbBug kbfix kbWinServ2003preSP1fix KB891011
©2004 Microsoft Corporation. All rights reserved.