Searching...
Thursday, 12 March 2015

How to resolve Error “0x80004005” in Exchange Server 2010

While working on Exchange 2010, it may happen that by mistake you remove those log files which have not been written to the database associated to it,this can create several serious issues. In such situations it may be possible that while trying to mount the database, you may face this error: "Failed to mount database" or "Mailbox Database’ couldn't mount the database that you specified".

Dirty System Shutdown state is another reason for this error generation. Due to Dirty Shutdown state user may lose useful Log files which could further lead to database corruption.In those situations, itmay become practically unmanageable for you to access exchange database files, unluckily you may suffer serious data loss .In order to regain access to your important data, it is necessary for you to figure out the main cause of this problem and to resolve it by using the correct method. Here some of the symptoms, causes, and some most used resolution methods are discussed below:

Symptoms of this Error:

If you are working on Microsoft Exchange Server 2010,you may face this error when trying to mount a mailbox database or a public folder database to Exchange:

Failed to mount 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).

Cause of this Error:
  1. Dirty Shutdown
  2.  Removal of log files, which has not been committed to the database yet.
  3.  Corrupt Database
When you have a corrupt database or incomplete logs you may face this type of error. In those situations these are some basic resolution steps user should follow before going for recovery of database or log files.

Check and Repair the database:

As corrupt database could be a reason for this error as well, so firstly you need to check the database and take it out of dirty shutdown state.

To repair database, run the following:

eseutil /p

"C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"

Check and Repair the database logs:

Then Re-run the database check and if all goes well; you should see this somewhere in the output: State: Clean Shutdown

After that,you can try mounting the database. If it mounts, you are good to go, if it doesn't you have to check the logs:

Check and Repair the database logs:

After repairing database if still your problem persists, then you need to check Database Log files,Check the exchange logs (don't forget to specify E00 - the starting sequence for the logs)
eseutil /ml

"C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E00"

There will be a list of logs and depending on their state, you may get an error. If problem is not with log files,then you need to move further to resolve this error.

Resolving this Error:
  • Run Setup /PrepareAD
  • Add the Exchange Servers group to the "Manage auditing and security log" policy
  • Use a professional software
Method 1: Run Setup /PrepareAD :

You need to run Setup /PrepareAD command from Exchange Server's CD to prepare the Active Directory service for Exchange Server 2010.This command restores Exchange Server configuration in Active Directories. Find the steps below which you need to follow:

Exchange Server 2010

  1. Start Exchange Server 2010 Help.
  2. Click the Contents tab, Go to Deployment-> New Installation-> Preparing to Deploy Exchange 2010, and then click How to Prepare Active Directory and Domains.
Method 2: Add the Exchange Servers group to the "Manage auditing and security log" policy using Domain Controller

So as to add Exchange Servers group to the Manage auditing and security log policy, follow these steps:
  1. Log on to domain controller by using an account which have administrative rights.
  2. Click Start->Administrative Tools-> Domain Controller Security Policy.
  3. In the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in, expand Local Policies, and then click User Rights Assignment, In the right pane, double-click Manage auditing and security log.
  4. In the Manage auditing and security log Properties dialog box, click Add User or Group and in the User and group names box, type DomainNameExchange Servers, and then click OK two times.
  5. Exit the Default Domain Controller Security Settings MMC snap-in, and then wait for this security setting to propagate across the domain controllers in the domain.
  6. Restart the Microsoft Exchange Information Store service
Method 3:Use a Third Party Tool

If your problem is still not getting resolved by following the solutions given above, then it would be better for you to try professional Exchange Recovery Software like - Stellar Phoenix Mailbox Exchange Recovery, which easily restores the completely inaccessible mailboxes from exchange database successfully without causing any data loss. This tool has powerful scanning algorithm that recovers accidentally deleted mailboxes as well. A lot can be done with this Exchange Recovery Tool.


0 comments:

Post a Comment