Article ID: 260912 - Last Review: October 26, 2006 - Revision: 4.2 XADM: Exchange Server Categorization Count Displays 4294967296 in Performance MonitorThis article was previously published under Q260912 SYMPTOMS
Microsoft Windows NT Performance Monitor may display a value of 4294967296 when you view the Categorization Count counter for the MSExchangeIS Private or MSExchangeIS Public objects. When you restart the information store, this count starts at a value of 0.
CAUSE
This issue can occur if the information store allows this counter to become negative. Performance Monitor displays the value 4294967296 for negative numbers (the hexadecimal equivalent to 0x100000000). The value for the Categorization Count counter should reflect the total number of categorization tables in the private and public information stores, and this count should be preserved when you restart the information store. Preservation of this number is not being handled properly.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
191914
(http://support.microsoft.com/kb/191914/EN-US/
)
XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the Microsoft
Download Center:
x86:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
Collapse this image ![]() Alpha: Collapse this image ![]() 119591
(http://support.microsoft.com/kb/119591/EN-US/
)
How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.
| Article Translations
|

Back to the top

