Microsoft small business knowledge base

Article ID: 260912 - Last Review: October 20, 2013 - Revision: 4.2

Hotfix Download Available
View and request hotfix downloads
This article was previously published under Q260912
This article has been archived. It is offered "as is" and will no longer be updated.


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.


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.


To 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  ( ) XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download Q248838engi.exe now (
Collapse this imageExpand this image
Download Q248838enga.exe now (
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591  ( ) 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.


Microsoft 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.

  • Microsoft Exchange Server 5.5 Standard Edition
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB260912
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support