Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/254576

From BetaArchive Wiki
Knowledge Base

XADM: The Isinteg Utility Reports ecCorruptData-MAPI_E_CORRUPT_DATA

Article ID: 254576

Article Last Modified on 10/26/2006


  • Microsoft Exchange Server 5.5 Standard Edition

This article was previously published under Q254576


If you run the isinteg -pri -test alltests -verbose command, the results may indicate corruption in the information store. The output is similar to the following:

Starting test 1 of 20, 'Search Folder Links'
Finished Search Folder Links. Time: 0h:3m:46s, number of errors = 1
Test returned ecCorruptData-MAPI_E_CORRUPT_DATA

However, when you use the -fix switch to attempt to fix this issue, the corruption remains in the information store. The summary output of the Isinteg utility does not show that any fixes have been made.


This issue can occur if the Isinteg utility encounters a folder that does not have a folder ID (FID).


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:

191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack

The following files are available for download from the Microsoft Download Center:

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.

Keywords: kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB254576