Article ID: 168571
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q168571
SYMPTOMS
Although you create a log file using the Windows NT Performance Monitor utility, the maximum size that the log file can grow to is 2,147,483,648 bytes. When the size of a Performance Monitor log reaches this 2.1 gigabyte (GB) limitation, the file size counter begins to count down backwards placing a negative sign in front of the number of bytes. Also, the log file is corrupted after it reaches that point.
CAUSE
The Windows NT Performance Monitor utility is not designed to collect more than 2.1 GB of data in a log file.
RESOLUTION
For a more concise log file containing only certain counters that you specify, use a utility in the "Windows NT 4.0 Resource Kit" called Performance Data Logger.
In Windows 2000, the Performance Monitor has a 1 GB limitation and stops adding information to the log file when it reaches the limit.
For additional information about the log file limit in Windows 2000, click the article number below to view the article in the Microsoft Knowledge Base:
256929 Windows 2000 System Monitor Logs Have a 1-GB Limit
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0.
Additional query words: perfmon prodnt
Keywords: kbbug KB168571
