Hi

So is mail101 and mail102 running exchange 2013 and AP104 running exchange 2007?

The error says it cannot query active directory, are all your services started and can you actually ping your dc from all your exchange servers?

Hello 

this seems to be an issue with your DC replication. Check replications status.

Hi,

First, please make sure you can ping DC from Exchange 2013 server.

And please make sure the Microsoft Exchange Replication service on server "MAIL101.us.rootdomain.rootdomain" is running.

Besides, please use the Test-ReplicationHealth cmdlet to check the result.

Best regards,
Belinda

Sorry let me clarify some of the config a little more.

MAIL101 - Exch 2013
MAIL102 - Exch 2013

AP104 - Witness (strictly a witness nothing else on this machine)

EDGE01 - Exch 2007 Edge
CAS01 - Exch 2007 Hub/CAS load balancer for CAS02/03
CAS02 - Exch 2007 Hub/CAS
CAS03 - Exch 2007 Hub/CAS
MBOX01 - Exch 2007 Mail cluster
MBOX02 - Exch 2007 Mail cluster node
MBOX03 - Exch 2007 Mail cluster node

RDC01, RDC02, RDC03 - all 2008 R2 root domain controllers for rootdomain.rootdomain
DC01, DC02, DC03, DC04 - all 2008 R2 domain controllers for us.rootdomain.rootdomain

All DCs are Global Catalogs.

I can ping all DCs and root DCs fromboth MAIL101 and 102

The Exchange Replication service is running on both MAIL101 and 102.

DC03 is in the same site as the MAIL101/102 servers so I'll run all replication tests from here.
DCDIAG comes back with all tests passed.
repadmin /replsum comes back with 0 fails and no errors largest delta for any intersite communication is 13min.

When I run Test-ReplicationHealth -Identity MAIL101 and also 102 they both come back as everything passed.  No errors.

Hi,

There are multiple DCs in your environment, I recommend you try to set the preferred Active Directory server using the following command to check the result.

Set-ADServerSettings PreferredServer <DC FQDN>

If you are running Exchange 2013 CU1 or later, you may be presented with a warning message after adding a new mailbox database.

"Warning: Please restart the Microsoft Exchange Information Store service on server E15MB1 after adding new mailbox databases."

Since everything else works well, you can ignore this warning.

Best regards,
Belinda

Hi

It can happen on this situation that the creation of the DB hasn't replicated by the time the command completes.  You will probably find if you wait a couple of minutes the database will respond to a mount request.

Steve

@Belinda

So I tried that with every DC, 01-04, some are in the same site, some aren't.  I ran the replication test every time I set the preferred DC.  All passed for both MAIL101 and MAIL102.

I also tried to set the preferred to a DC that I would consider the primary DC for the us. domain and then tried the DB creation/mount again, the same error occurred.

One thing I noticed when running Get-ADServerSettings I did notice that ConfigurationDomainController and PreferredGlobalCatalog columns are both empty.

@Steve

Yeah I've never had any issues actually mounting the database after a creation after restarting the information store.  Seems to have no real issue in the end.  I'm just concerned that this error is being caused by some underlying issue since I've not seen a lot about it anywhere else.

I had the same issue.  

As previously mentioned by someone this is most likely AD replication related.

The script I'm using is from Msft "CreateMBDatabaseCopies.ps1" which was generated by the storage server role requirements calculator.  In the script is accounted for AD replication and had a loop to hold off on creating any additional database copies for 5 minutes and then check again to see if DC1 and DC2 are "in sync" before proceeding.