Fail creating databases for Exchange 2010
We are not able to create new databases in Exchange 2010. The error returned as below:
Active Directory operation failed on “server”. This error is not retriable. Additional information: The name reference is invalid.
This may be caused by replication latency between Active Directory domain controllers.
I have reading through the message forums and this issue may be a result of two things:
1. It could be related to latency in AD replication. This may result a slow link or replication interval may be too high.
2. Configuration of domain controller and the Exchange 2010 preferred Global catalog are different.
Question: If we have two DC, both DC have global catalog. How can we ensure the global catalog are same? Any tools/command to synchronize both Global catalog for both DC?
Anyone who face same problem likes me and have solutions, kindly advise!
Thank You!
September 9th, 2011 4:59pm
I have seen this also if you have AD GPO's that are too tight or convoluted. Create a OU with no GPO's assigned, and block inheritance of GPO's for that OU and do a test install.:P Advice offered, If you need more help it is advised to seek the council and advice of paid professionals. The answer is always 42, or reboot.
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2011 5:20pm
Trobleshoot the AD Replication issues, before doing that set the Confgiguration DC and GC server using Set-AdserverSetting cmdlet.
Set-AdserverSettings -ConfigurationDomainController “Servername” -PreferredGlobalCatalog “ServerName” -SetPreferredDomainControllers “Servername”
Where the “ServerName” is would be the name of your Domain Controller, either the FQDN or the Netbios name will do. It is recommended to setup the Configuration Domain Controllers and the Preferred Global Catalog on the same server.
For more information:
Troubleshooting Active Directory Replication Problems
Set-AdServerSettings Cmdlet.
For Exchange 2010 queries use
Exchange 2010 forum.
Thanks.
September 9th, 2011 6:16pm
Hello,
for Exchange 2010 problems please use:
http://social.technet.microsoft.com/Forums/en-US/category/exchange2010,exchangeserver/
Hopefully you do NOT run Exchange on the DC, which is NOT recommended, even not from Microsoft for multiple reasons.
If you think that you have AD problems please upload the following files:
ipconfig /all >c:\ipconfig.txt [from each DC/DNS Server]
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)]
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)
As the output will become large, DON'T post them into the thread, please use Windows Sky Drive (skydrive.live.com) [with open access!] and add the link from it here. Also the /e in dcdiag scans the complete forest, so better run it on COB.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2011 2:29pm
Hi Meinolf,
Thanks for the feedback. I thought this is related to AD issues, thats why I posted at this forum.
I have two DC, the Exchange 2010 was running on different servers.
I have tested when I shutdown the AD1(which is also DC), I'm able to create database. Thus, I guest it should be related to the AD problem.
I have upload the txt file for running ipconfig, dcdiag & repadmin. I'm not able to run the command "dnslint" as this is only for window 2003. My servers was running on Window 2008 R2.
Can you please take a look for the files I have uploaded at skydrive.live.com?
https://skydrive.live.com/redir.aspx?cid=da9eb4a805a415ef&resid=DA9EB4A805A415EF!111
Please advice!
Thanks!
September 12th, 2011 6:36am
Hello,
the major problem is that the DC is multihomed which is NOT recommended configuration and result in multiple problems as you see now.
External access should be granted with the router and not the DC so please reconfigure the DC to use ONLY the private ip settings and also do NOT use the ISPs DNS server on the NIC.
http://support.microsoft.com/kb/157025
http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx
Also do NOT use the other domain DNS as Forwarder, only external DNS servers should be used here.
The DNS configuration problems also result in the problem that msg-ad2 has DNS errors in dcdiag.
Please upload also the ipconfig /all from the second DC.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2011 12:27pm
Thanks Meinolf,
I have updated my DNS, I have re-run the command for my both ad.
You can get the link as below:
https://skydrive.live.com/redir.aspx?cid=da9eb4a805a415ef&resid=DA9EB4A805A415EF!111
Thank you!
September 12th, 2011 1:20pm
Hi,
There are many failures regarding network connectivity and DNS server in DCDiag log files. According to the IPConfig log files, you still using multihomed
network with Oracle VM Virtual Ethernet Adapter and Oracle VM Virtual Ethernet Adapter #2.
As Meinolf Weber mentioned, multihomed network is not recommended. Network adapters on the multihomed domain controllers are registering both the inside
and outside Internet Protocol (IP) addresses with the DNS server. DNS name resolution lookup requests return records in a "round robin" fashion, alternating the internal and external IP addresses. Replication operations require multiple lookup requests of
SRV records. In this case, half of the DNS lookup requests return an IP address that cannot be contacted, and the replication operation fails.
For more information, please refer to the following Microsoft KB articles:
Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294
Name resolution and connectivity issues occur on Windows 2000 domain controllers that have the Routing and Remote Access service and DNS installed
http://support.microsoft.com/kb/830063
Delay in NetBIOS connections from a multi-homed computer
http://support.microsoft.com/kb/166159
Regards,
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2011 4:16pm
Hello,
DNS is still mutlihomed on both DCs. NO CHANGE
Forwarders are still using domain DNS servers. NO CHANGE
What about the firewall settings, are the ports enabled according to:
http://technet.microsoft.com/en-us/library/dd772723(WS.10).aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
September 12th, 2011 11:00pm
Hi,
We have re-install our NIC driver and re-configure the DNS IP for both NIC. The multihome problem seems to be solved.
We have re-run the command dcdiag and the result return as below:
https://skydrive.live.com/redir.aspx?cid=da9eb4a805a415ef&resid=DA9EB4A805A415EF!111
We have go back to mailstore server and try to add new databases, the error message return:
Couldn't mount the database that you specified. Specified database: db2; Error code: An Active Manager operation failed. Error: The database action failed.
Error: An error occurred while trying to select a database copy for possible activation. Error: The database 'db2' was not mounted because errors occurred either
while validating database copies for possible activation, or while attempting to activate another copy.
An Active Manager operation failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database.
We have set the preferred AD server in EMS using command:
Set-ADServerSettings –PreferredServer <DC FQDN>
And we have do the following:
1. Open EMC and right-click on "Organization Configuration". Choose "Modify Configuration Domain Controller".
2. Specify the domain and the DC.
3. Open EMC and right-click on "Recipient Configuration". Choose "Modify Recipient Scope".
4. Specify the global catalog server. Make sure it is the same as the chosen DC.
We have done this step, but when creating new database we still receive the error message.
Please advice!
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2011 12:20pm
Hello,
for listed errors 0x6ba see:
http://msmvps.com/blogs/mweber/archive/2011/02/07/possible-error-messages-on-windows-server-2008-and-windows-server-2008-r2-domain-controllers.aspx
Please upload the unedited ipconfig /all also from BOTH machines, it seems you now use the public ip addresses instead the private ones on MSG-AD2.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
September 13th, 2011 10:57pm
Hi Meinolf,
Thanks for the update. We have enable the RPC from the firewall for both server. I have attached the IPCONFIG for both DC.
https://skydrive.live.com/redir.aspx?cid=da9eb4a805a415ef&resid=DA9EB4A805A415EF!111
We are using DC's public IP instead of external DNS. You can get our config file from the link above.
Free Windows Admin Tool Kit Click here and download it now
September 14th, 2011 5:56am
Hi,
Anybody have encounter the same problem like us?
Please advice or comment.
Thanks!
September 15th, 2011 6:25am
We have resolve the issues by create new DC and transfer all FSMO from DC2 to DC1. We have re-install our mailstore server. Problem resolved.
Thanks everyone for valuable advice!
Free Windows Admin Tool Kit Click here and download it now
October 12th, 2011 10:12pm


