Exchange Server is a popular e-mail communication server. These days, almost all big organizations are implementing it as their main mail server. When any problem occurs in Exchange Server, it logs the troubled event IDs in the application log along with their system diagnosis. In general, the reason behind most of the error messages, is the corruption of Exchange Server database and this corruption leads to the inaccessibility of Exchange Server database. Well, data loss can be overcome, if you have the latest backup of your data. However, if backup is not available, then you need to go for a third party Exchange Server recovery software.
In respect of the above issue, let us consider a practical case. Suppose, your Microsoft Exchange 2003 server has got locked for no reason. And, when you rebooted the Server, you failed to start that up. On viewing the application event log, you saw the following event IDs on the screen:
“Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Error Log file is corrupt starting Storage Group
/DC=local/DC=cr/CN=Configuration/CN=Services/CN=Microsoft
Exchange/CN=CityRealtyMail/CN=Administrative Groups/CN=First Administrative
Group/CN=Servers/CN=CRC2K3/CN=InformationStore/CN=First Storage Group on the
Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.
Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 6/7/2005
Time: 6:07:09 PM
User: N/A
Computer: CRC2K3
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is down for
maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Information Store (448) First Storage Group: Database recovery/restore
failed with unexpected error -501.”
And, when an attempt was made to mount the public folder, an error message written as below appeared on the screen:
“The database files in this store are corrupted”
Reason: The primary cause, which is responsible for the occurrence of above error message is the corruption of the Exchange Server database. Corruption occurs because of unexpected system shutdown, operating system failure, human error, application malfunction etc.
How to solve ? : In order to solve the above problem you need to apply soft repair method first. Follow the following steps to perform the soft repair process:
1) Run the following commands to check the consistency of database:
eseutil /mh ..\mdbdata\priv.edb > mypriv.txt
eseutil /mh ..\mdbdatapub.edb > mypub.txt
2) If any of the databases are found to be inconsistent, use the following commands to carry out the soft repair solution:
eseutil /r /ispriv
eseutil /r /ispub
3) Now use the steps listed in the MS KB article:
"How to recover from information store corruption"
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q272570
But sometimes, execution of 'ESEUTIL' utility results data loss in Exchange Server. For good results, it is better to opt for a third party Exchange Server Recovery tool. These tools have been developed to overcome the problems that occur because of corrupt Exchange Server database. It is the best alternative, when you need to perform EDB recovery for getting your lost email objects back.
Stellar Phoenix Mailbox Exchange Recovery is a self-explanatory tool that is used to perform quite efficiently. The Exchange Server recovery tool restores all your seemingly lost e-mail objects, such as contacts, attachments, e-mails, appointments, tasks, journal, events and more. The application restores the RTF and HTML messages in their original format and shows compatibility with Windows 7, Vista, Server 2003, XP and 2000. Visit Tool http://exchange.stellarservertools.com/
In respect of the above issue, let us consider a practical case. Suppose, your Microsoft Exchange 2003 server has got locked for no reason. And, when you rebooted the Server, you failed to start that up. On viewing the application event log, you saw the following event IDs on the screen:
“Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Error Log file is corrupt starting Storage Group
/DC=local/DC=cr/CN=Configuration/CN=Services/CN=Microsoft
Exchange/CN=CityRealtyMail/CN=Administrative Groups/CN=First Administrative
Group/CN=Servers/CN=CRC2K3/CN=InformationStore/CN=First Storage Group on the
Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.
Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 6/7/2005
Time: 6:07:09 PM
User: N/A
Computer: CRC2K3
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is down for
maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Information Store (448) First Storage Group: Database recovery/restore
failed with unexpected error -501.”
And, when an attempt was made to mount the public folder, an error message written as below appeared on the screen:
“The database files in this store are corrupted”
Reason: The primary cause, which is responsible for the occurrence of above error message is the corruption of the Exchange Server database. Corruption occurs because of unexpected system shutdown, operating system failure, human error, application malfunction etc.
How to solve ? : In order to solve the above problem you need to apply soft repair method first. Follow the following steps to perform the soft repair process:
1) Run the following commands to check the consistency of database:
eseutil /mh ..\mdbdata\priv.edb > mypriv.txt
eseutil /mh ..\mdbdatapub.edb > mypub.txt
2) If any of the databases are found to be inconsistent, use the following commands to carry out the soft repair solution:
eseutil /r /ispriv
eseutil /r /ispub
3) Now use the steps listed in the MS KB article:
"How to recover from information store corruption"
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q272570
But sometimes, execution of 'ESEUTIL' utility results data loss in Exchange Server. For good results, it is better to opt for a third party Exchange Server Recovery tool. These tools have been developed to overcome the problems that occur because of corrupt Exchange Server database. It is the best alternative, when you need to perform EDB recovery for getting your lost email objects back.
Stellar Phoenix Mailbox Exchange Recovery is a self-explanatory tool that is used to perform quite efficiently. The Exchange Server recovery tool restores all your seemingly lost e-mail objects, such as contacts, attachments, e-mails, appointments, tasks, journal, events and more. The application restores the RTF and HTML messages in their original format and shows compatibility with Windows 7, Vista, Server 2003, XP and 2000. Visit Tool http://exchange.stellarservertools.com/
