Event ID 9519 "Error 0x80004005" is logged in the Application log when you try to mount a database in Exchange Server 2010 or in Exchange Server 2007

You experience the following symptoms on a computer that is running Microsoft Exchange Server 2010 or Microsoft Exchange Server 2007:

• If you try to mount a mailbox database or if you try to mount a public folder database, you experience the following symptoms:
  • You receive an error message that resembles the following:
    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).
  • The following events are logged in the Application log:
    
    Event ID 9519

    Event Type: Error
    Event Source: MSExchangeIS
    Event Category: General
    Event ID: 9519
    Date: date
    Time: time
    User: N/A
    Computer: ServerName
    Description: Error 0x80004005 starting database "First Storage Group\Mailbox Database" on the Microsoft Exchange Information Store.
    For more information, click http://www.microsoft.com/contentredirect.asp.
    
    Data: 0000: 46 61 69 6c 65 64 20 74 Failed t
    0008: 6f 20 63 6f 6e 66 69 67 o config
    0010: 75 72 65 20 4d 44 42 00 ure MDB.

    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.

• When you try to log on to the computer, Windows stops responding (hangs) at the "Applying computer settings" part of the logon process.

This problem may occur if the DomainName\Exchange Servers group is not assigned the Manage auditing and security log user right.

To resolve this problem, use one of the following methods:

Method 1: Run Setup /PrepareAD

Run the Setup /PrepareAD command from the Exchange Server CD to prepare the Active Directory directory service for Exchange Server 2010 or Exchange Server 2007. This command restores the Exchange Servere configuration in Active Directory. For more information about how to prepare Active Directory, see the "How to Prepare Active Directory and Domains" topic in Exchange Server Help. To view this Help topic, follow these steps for the appropriate program.

Exchange Server 2010

1. Start Exchange Server 2010 Help.
2. Click the Contents tab, expand Deployment, expand New Installation, expand Preparing to Deploy Exchange 2010, and then click How to Prepare Active Directory and Domains.

Exchange Server 2007

1. Start Exchange Server 2007 Help.
2. Click the Contents tab, expand Deployment, expand New Installation, expand Preparing to Deploy Exchange 2007, 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

To add the Exchange Servers group to the Manage auditing and security log policy, follow these steps:

1. Log on to a domain controller by using an account that has administrative rights.
2. Click Start, point to Administrative Tools, and then click 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.
4. In the right pane, double-click Manage auditing and security log.
5. In the Manage auditing and security log Properties dialog box, click Add User or Group.
6. In the User and group names box, type DomainName\Exchange Servers, and then click OK two times.
7. 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.
8. Restart the Microsoft Exchange Information Store service.