Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Exchange 2007 was outdated and hence posing a problem. As an Exchange Administrator, you own the responsibility of Exchange setup, resolution of problems and also Exchange migration. Installation steps for Exchange 2013 differ from Exchange 2007, however, once started; the installation of Exchange 2013 server is relatively easy but the next process of mounting a new mailbox database on the server proved to be futile effort. The most common error encountered by Administrators is “Mailbox role Failed” and following message displays on screen:
“Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
Error message is listed in detail in the box below:
DBNAME Failed Error: Couldn’t mount the database that you specified. Specified database: DBNAME; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233) . [Database: DBNAME, Server: SERVERNAME.DOMAIN.COM]. An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233) . [ Database: DBNAME, Server: SERVERNAME.DOMAIN.COM] An Active Manager operation failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233) . [ Server: SERVERNAME.DOMAIN.COM]
How the problem arises?
The process of mounting the database has changed for Exchange 2010 and Exchange 2013. Earlier versions like Exchange 2007 consisted of “The Information Store” process was solely responsible for creating New Mailbox Databases and performing “mount and dismount” operations.
The evolution to Exchange 2010 and higher witnessed a new entity “Active Manager Process”. Every server whether standalone or a member of DAG (Database availability Group) have an Active Manager Process. Active Manager Process is assigned the role of creation of mailbox databases and perform mount/dismount operations. Active Manager works with Information store to execute these requests. This process runs within the Exchange Replication Service.
Note: Exchange 2007 and earlier versions used Information store Process for creation and mount/dismount.
The process of creation of new mailbox database entry is as follows: When Administrators create a new mailbox database, it also creates an entry in the Database Configuration Container within the Active directory and this replicates to all domain controllers. The issue arises when a new mailbox database is created and mounted immediately.
What causes this issue?
Exchange Administrators issues a mount command which is immediately referred to the Active Manager Process on the server.
In case of DAG, the issued command route is as follows:
This issue can be resolved after waiting for some time but how long an Exchange Administrator has to wait is not specified. Waiting time is dependent upon the amount of time Domain controllers take to replicate the database object.
Following steps are performed at Exchange level: [PS] C:\>Mount-Database Test [PS] C:\>Get-MailboxDatabase Test -Status | fl name,*mounted* Name : Test MountedOnServer: MBX-1.domain.com Mounted : True
And same problem persists even after using the ECP utility.
Verification Steps performed on Exchange server to verify that the process is flawless:
Verify Global server catalog settings on Exchange server. Verification steps are as follows:
To resolve the error, used the following PowerShell command:
1. Set-ADServerSettings –PreferredServer
But the problem persisted and the message failed to budge.
2. Posted the problem on forum and following resolution method was suggested:
a. Check that you are able to mount blank database
b. Run Eseutil/mh to check the consistency of old database and that you are not getting dirty shutdown error.
But even after running the PowerShell and Eseutil commands, the problem persists. We are not aware of the time-lag for database mount.
It is better to turn to a third-party software which is equipped to create new mailboxes and migrate the database from old server to new machine. Software data recovery tool enables Exchange Administrators to mount the database thus keeping the tensions at bay.
One such software is Stellar Phoenix Mailbox Exchange Recovery that helps you to resolve “failed to mount database” related error and come out of the complex situation with ease. With this tool, you can easily mount mailboxes databases to the new server.
Since the data is to be migrated from old Exchange 2007 version to latest 2013 version, you should sanitize the data on the old server.
Steps to repair corrupt Exchange Database File on Old server:
“Mailbox role failed” error is displayed when mailbox is corrupt and fails to mount database. Error can be rectified with Eseutil Hard Recovery. If these utilities are not performing up-to-the-mark, opt for recovery tools which help resolve the problem and enable easy database mount. Amongst the numerous options, Stellar Phoenix Mailbox Exchange Recovery is one of the enduring selection which resolves the issue: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”