A new installation of Exchange Server 2007 may fail to mount the initial Mailbox Database.  The server will display a “mapiexceptioncallfailed ec=-2147467259” error, and the following events may be seen in the Application event log.

Log Name:      Application
Source:        MSExchangeIS
Date:          5/23/2010 1:39:28 PM
Event ID:      9518
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EXCH07.domain.local
Error 0x80004005 starting Storage Group /DC=local/DC=domain/CN=Configuration/
CN=Services/CN=Microsoft Exchange/CN=Exchange Organization/CN=Administrative
 Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/
CN=EXCH07/CN=InformationStore/CN=First Storage Group on the Microsoft
 Exchange Information Store. MDB failed to start.

The problem may also occur for any other mailbox databases that are created, giving the same 2147467259 error.

The error code 2147467259 can indicate Active Directory problems are the cause of the database failing to mount.

Newly created mailbox databases can fail to mount due to Active Directory replication delays. If the database still will not mount after you have waited for the Active Directory replication interval to lapse, open an elevated command prompt and run the following command from the Exchange Server 2007 source file location:

C:SrcExchange2007>setup /preparedomain

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

No server roles will be installed

Performing Microsoft Exchange Server Prerequisite Check

    Organization Checks              ......................... COMPLETED

Configuring Microsoft Exchange Server

    Prepare Domain Progress          ......................... COMPLETED

The Microsoft Exchange Server setup operation completed successfully.

The mailbox database should now mount successfully without error.

About the Author

Paul Cunningham

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com.


  1. Jeffrey Carden

    Spot on! Thank you for posting this. The scenario and fix were identical to mine and your fix worked like a charm!


Leave a Reply