Read time 4 minutes
Typically, when corruption issues arise in Microsoft Exchange Server 2000 and 2003, one of the affected components is the Information Store. The Information Store comprises the following database files:
Priv1.edb houses in-process database files and stores non-SMTP messages, while the Priv1.stm file contains Simple Mail Transfer Protocol (SMTP) mail messages, encompassing both in-process emails and those stored on the server. On the other hand, Pub1.edb database files constitute the public folder store for non-SMTP formatted data, while Pub1.stm contains public folders that store SMTP formatted information.
Corruption typically involves one or both of the .EDB files, which are associated with Exchange Server 2000 and 2003 databases. In the majority of instances, either the Priv1.edb file or the Pub1.edb file, both situated within the Program Files\Exchsrvr\Mdbdata folder, becomes corrupted.
When the Information Store becomes corrupted, users may experience the following symptoms:
When attempting to mount the database using Exchange System Manager, you might encounter the following error message:
A critical internal processing error has arisen. We recommend attempting a resolution by initiating a restart of either the Exchange System Manager, the Microsoft Exchange Information Store service, or both in tandem.
Description: The MAPI call to openmsgstore encountered an error, indicating possible network issues or maintenance on the MSE server computer.
In case an upgrade is done, the database files may be located in the C:\Exchsrvr\Mdbdata folder. If the databases have been optimized, database may be located on another drive.
To bring Pub1.edb file back into a consistent state:
Please select “Yes” to initiate the repair process when the utility indicates that it is scanning for database integrity. Once the repair procedure is finished, the program will present the following message:
Execute the following command to repair pub.edb file:
After executing the previous commands, you will receive a report that provides a summary of the total number of warnings, errors, and fixes detected. Continue with the 8th step repeatedly until no warnings, errors, or fixes remain in the report.
If following the aforementioned steps fails to restore your data to a consistent state and your information remains inaccessible, you should consider repairing the priv.edb and pub.edb files using Kernel for Exchange Server software. This software is highly efficient and yields excellent results in Exchange Recovery. It is specifically designed to mend .edb files and and recover multiple mailboxes from them. The EDB to PST converter included in the software allows you to save the recovered mailboxes as both PST and EDB files, ensuring a comprehensive data recovery solution.