Tuesday, January 5, 2010

Error creating a new mailbox database on exchange 2010 in a multiple domain environment

When you try to create a new mailbox database on Exchange 2010 in a multiple domain environment, the database is created but you may get the following error when trying to mount it:

Failed to mount database

'<test>'.
<test>
Failed
Error:
Couldn't mount the database that you specified. Specified database:
<test>; 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: <test>, Server:
<Servername>].
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: <test>, Server:
<Servername>
An Active Manager operation failed. Error: Operation failed with message:
MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f,
ec=-2147221233)
[Server: <servername>]
MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f,
ec=-2147221233)

The following event is logged in the Application log:

Log Name: Application
Source: MSExchange Configuration Cmdlet - Remote Management
Date: 9/17/2009 12:26:00 PM
Event ID: 4
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: <servername>
Description: (PID 8136, Thread 2652) Task New-MailboxDatabase writing error when processing record of index 0. Error: Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on <domain controller>. This error is not retriable. Additional information: The name reference is invalid.
This may be caused by replication latency between Active Directory domain controllers.

According to Microsoft support site (http://support.microsoft.com/kb/977960/EN-US) , the problem occurs when the value of the ConfigurationDomainController parameter and the value of the PreferredGlobalCatalog parameter are different. Their solution is to run the following cmdlet:

Set-ADServerSettings –PreferredServer <DC FQDN>

We encountered this problem with one of our clients and the solution provided by Microsoft did not work. What we did was to mount the database specifying the domain controller that writes the configuration change to Active Directory. The cmdlet is:

Mount-Database -Identity <database> -DomainController <DC FQDN>

4 comments:

  1. Excellent, worked for me!

    -D.

    ReplyDelete
  2. thanks, this helped getting the store mounted. Exchange 2010 is buggy out of the box.

    We also reference techieshelp

    http://www.techieshelp.com/you-cannot-mount-a-new-exchange-server-2010-mailbox-database/

    ReplyDelete
  3. It's the right configuration. You can edit it depending on the function.

    ReplyDelete
  4. Thanks Paul for the tips. I had similar problem in my Exchange 2010 server. After reading many threads on forum ( one of them is : http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/66c440e9-1dbc-474b-a737-26d86555ab02) and other helpful articles, I could not solve my problem and last I purchase Stellar Phoenix Exchange recovery software which successfully resolved my problem. I came to know from the technical team of Stellar data recovery that this problem can also be occurred due to corrupt mailboxes.

    I would advised to all who are suffering from such kind of problems can call to Microsoft PSS or use a commercial Exchange recovery software.

    ReplyDelete