Microsoft KB Archive/891011

= 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 =

Article ID: 891011

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise x64 Edition

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify 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 \System32\Wbem\Logs folder.



Hotfix information
Note This hotfix resolves the problem only on a computer on which a clean installation of Windows Server 2003 with Service Pack 1 was performed. This hotfix does not resolve the problem on a computer on which Windows Server 2003 Service Pack 1 was applied to the original release version of Windows Server 2003.

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

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

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 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 item in Control Panel.

Windows Server 2003, 32-bit versions
  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

Windows Server 2003, Itanium-based versions
  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



MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry 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:


 * The maximum file size is set by the following registry subkey:

The following registry subkey determines how the Windows Driver Model (WDM) provider logs errors:

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 to collect 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 &quot;Applies to&quot; section.



MORE INFORMATION
For more information about the terms that are used to describe software updates, 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

Keywords: kbqfe kbhotfixserver kbbug kbfix kbwinserv2003presp1fix KB891011

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.