Are you facing some sort of problem while trying to access MS Exchange database folder? Such problem can occur if there are some problems with the configuration in Exchange Server settings. You should try to address the settings. If the problem is not resolved, then there is a quite prominent possibility that the EDB (Exchange Database) database file is damaged, which can happen due to various reasons including virus infections, database header corruption, transaction log file corruption, etc. In such cases, appropriate methods should be used to recover corrupt EDB file. If these methods are insufficient, then the use of a third-party EDB recovery software to perform EDB recovery is a must.
Let us discuss a scenario in which you are unable to mount the mailbox database in MS Exchange Server 2010. In such case, the following error message is displayed:
“Failed to mount database 'Mailbox Database'
Mailbox Database
Error:
Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2-ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005,ec=-2147467259).”
In addition, the following report is logged in the Application event log:
“Event ID 9518
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: date
Time: time
User: N/A
Computer: ServerName
Description: Error 0x80004005 starting Storage Group /DC=com/DC=example/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=335A1087-5131-4D45-BE3E-3C6C7F76F5EC/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=ServerName/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
MDB failed to start.”
Cause:
There could be the following reasons for such erroneous situation:
A) The 'DomainName\Exchange Servers' group is not assigned the 'Manage auditing and security log' user right.
B) The EDB database file is damaged.
Resolution:
To overcome the problem, you can perform either of the following methods:
A) Run Setup /PrepareAD: You should run the 'Setup /PrepareAD' command using the Exchange Server CD. This command restores the original configuration settings of Exchange Server.
B) Add the Exchange Servers group to the "Manage auditing and security log" policy: To do this, you should perform the following steps:
i) Click Start | Administrative Tools | Domain Controller Security Policy.
ii) Click 'User Rights Assignment' in the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in.
iii) Double-click 'Manage auditing and security log'.
iv) Click 'Add User or Group' in the 'Manage auditing and security log Properties' dialog box.
v) Enter 'DomainName\Exchange Servers' in the 'User and groups names' box.
vi) Click OK two times.
vii) Quit Default Domain Controller Security Settings MMC snap-in.
viii) Restart the Microsoft Exchange Information Store service.
If the problem is persisting, then a third-party EDB recovery software is to be used to recover corrupt EDB file. Such EDB recovery tools use fast and sophisticated scanning algorithms to recover EDB file without causing any damage to the original EDB file.
The EDB recovery tool that most of the recovery experts recommend is Stellar Phoenix Exchange Server recovery, which recovers corrupt EDB file created for MS Exchange Server.
Let us discuss a scenario in which you are unable to mount the mailbox database in MS Exchange Server 2010. In such case, the following error message is displayed:
“Failed to mount database 'Mailbox Database'
Mailbox Database
Error:
Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2-ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005,ec=-2147467259).”
In addition, the following report is logged in the Application event log:
“Event ID 9518
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: date
Time: time
User: N/A
Computer: ServerName
Description: Error 0x80004005 starting Storage Group /DC=com/DC=example/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=335A1087-5131-4D45-BE3E-3C6C7F76F5EC/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=ServerName/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
MDB failed to start.”
Cause:
There could be the following reasons for such erroneous situation:
A) The 'DomainName\Exchange Servers' group is not assigned the 'Manage auditing and security log' user right.
B) The EDB database file is damaged.
Resolution:
To overcome the problem, you can perform either of the following methods:
A) Run Setup /PrepareAD: You should run the 'Setup /PrepareAD' command using the Exchange Server CD. This command restores the original configuration settings of Exchange Server.
B) Add the Exchange Servers group to the "Manage auditing and security log" policy: To do this, you should perform the following steps:
i) Click Start | Administrative Tools | Domain Controller Security Policy.
ii) Click 'User Rights Assignment' in the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in.
iii) Double-click 'Manage auditing and security log'.
iv) Click 'Add User or Group' in the 'Manage auditing and security log Properties' dialog box.
v) Enter 'DomainName\Exchange Servers' in the 'User and groups names' box.
vi) Click OK two times.
vii) Quit Default Domain Controller Security Settings MMC snap-in.
viii) Restart the Microsoft Exchange Information Store service.
If the problem is persisting, then a third-party EDB recovery software is to be used to recover corrupt EDB file. Such EDB recovery tools use fast and sophisticated scanning algorithms to recover EDB file without causing any damage to the original EDB file.
The EDB recovery tool that most of the recovery experts recommend is Stellar Phoenix Exchange Server recovery, which recovers corrupt EDB file created for MS Exchange Server.
No comments:
Post a Comment