Unmountability of a Private Information Store (priv.edb and priv.stm files) primarily occurs when it is corrupted. One of the main reasons for it corruption is improper upgradation from Microsoft Exchange Server 5.5 to 2000. A major hazard that users encounter after improper upgradation is a series of Event Ids, which make the data saved in the private Information Store become inaccessible. In such situations, an effective way to access Private Information Store data is by using an updated backup. However, there are numerous circumstances in which the user has either not created any backup or his backup gets corrupted. To surmount such situations, you need to use an advanced third-party
Exchange Recovery software that can repair the database.
As a practical instance, you migrate your Exchange Server 5.5 database to Exchange 2000. However, after the migration process is complete and you attempt to access the database, you encounter the below series of Event ids:
“ErrorID: 9519 Error 0xfffff9bb starting database "First
Storage Group\Private Information Store (SERVIDOR3)" on
the Microsoft Exchange Information Store.
Failed to configure MDB.
ErrorID: 1127 Error 0xfffff9bb configuring the
database "First Storage Group\Private Information Store
(SERVIDOR3)".
)ErrorID: 1187 Database "First Storage Group\Private
Information Store (SERVIDOR3)" could not be upgraded to
version 3.2. Error 0xfffff9bb.
Error ID: 9545
ailbox /OúCILITY/OUúSNET/CN=RECIPIENTS/CN=CLIENTES
could not be found in the Active Directory during upgrade.
It has been issued GUID b035eb8b-de9a-47c6-b1f5-
309b01fcd514 and is currently disconnected.
You will need to reconnect the mailbox before allowing
the user to log on.
Error ID: 9175 The MAPI call 'OpenMsgStore' failed with
the following error:
The attempt to log on to the Microsoft Exchange Server
computer has failed.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0512-00000000”
Post the occurrence of above event ids, the data saved in the Exchange Server Database becomes inaccessible.
Resolution:
The above event ids can be resolved by repairing the corrupted Exchange Server database. To effectively do so, you will need to run ESEUTIL/P command.
While in many situations, your database gets repaired using the above utility. However, if it doesn't then you need to opt for an Exchange Server Recovery software. An Exchange Recovery software comprehensively repairs corrupt/damaged Exchange Server database in just three simple steps.
Microsoft Exchange Recovery Tool is a powerful utility that repairs Exchange Server databases with ease. The repaired database is stored in a PST (Personal Storage) file format. The read-only Microsoft Exchange Recovery software is compatible with Exchange Server 5.5, 2000, 2003, and 2007.
