Setup encountered a problem while validating the state of Active Directory: Could not find any Domain Controller in domain
I am trying to install Exchange 2007. I believe that I have followed all of the prerequisites and other items that are necessary to install it. However, I keep getting the error below. I am sure that I am doing something wrong so I would greatly appreciate it if someone would let me know if they have run into this error and what they did to fix it. I have gone through all of the TechNet articles and other items that are available online here. Thank you in advance for your help. Summary: 3 item(s). 0 succeeded, 3 failed. Elapsed time: 00:00:10 Hub Transport Role PrerequisitesFailed Error:Setup encountered a problem while validating the state of Active Directory:Could not find any Domain Controller in domain URN.LOC. Elapsed Time: 00:00:05 Client Access Role PrerequisitesFailed Error:Setup encountered a problem while validating the state of Active Directory:Could not find any Domain Controller in domain URN.LOC. Elapsed Time: 00:00:02 Mailbox Role PrerequisitesFailed Error:Setup encountered a problem while validating the state of Active Directory: Could not find any Domain Controller in domain URN.LOC. Elapsed Time: 00:00:02
February 27th, 2007 12:17am
This is most definitely a DNS related issue. Check to see that your exchange server dns is pointing to your domain dns servers, if it is run nslookup queries for domain.local, dc.domain.local, gc.domain.local, dc, gc and make sure you get authoritative responses for them. If you dont then start troubleshooting your DNS, once you got that working fine, so will Exchange 2007 Setup.
February 27th, 2007 8:31am
Make sure your wins settings are not conflicting
March 2nd, 2007 4:11am
Did you ever find out why this was not installing? I am getting the same error. Thanks, Angi
March 11th, 2007 12:03am
Same problem here on a vanilla W2k3 R2 64 test server as DC all created using server manager's install roles procedure. Can't see anything wrong with DNS setup and nor can DCDIAG. An Event ID 2152 gets created in the Application Event log(not friendly since there's no message decoderesource installedat this point). Here are the infill strings: The following information is part of the event: ExSetup.exe, 3772, 1753, Error 6d9 from HrGetServersForRole. Here is the message decode from Events and Error Message Centre with the above strings substituted: Process ExSetup.exe (PID=3772). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall. This suggests the problem is actually RPC, not DNSrelated. I also found this in theknown issues section of this article: http://support.microsoft.com/KB/555854. Same error, look at the suggested cause. 2. The following error may appear in the event log: Event Type: Error Event Source: MSExchange ADAccess Event Category: Devices Event ID: 2152 Description: The description for Event ID ( 2152 ) in Source ( MSExchange ADAccess ) cannot be found.The local computer may not have the necessary registry information or message DLL files to display messagesfrom a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ExSetupUI.exe; 4912; 1753; Error 6d9 from HrGetServersForRole This error may occur due network adapter binding error issue or/anddisable File and Print Sharing on the network adapter.Still digging, would be nice if someone at MS couldprovide a pointeronthis. There are now four treads on here all pointing to the same problem. Have run all the usual RPC endpoint mapper tests and none of them fail.
March 28th, 2007 2:01am
Reported on Usenet that this problem can be due to corrupt user profile. Solution is to create new admin user, logon using that, delete original admin's profile, reboot machine and logon using original admin's account (which creates new profile). Worked in at least one case. Didn't work for me. Reinstall from scratch being careful to install the absolute minimum needed for Exchange worked fine. Suspect this problem may be due to COM permissions causing RPC to fail. Needs looking into by MS, there's more to this thana problem somewhere between the keyboard and the chair.
March 30th, 2007 12:50pm
I encountered the 2152 event, and was befuddled. I was able to solve the problem, however before I go into detail, i should describe my configuration; because my solution may or may not be relevant to you.I have two identical servers, Windows 2003 R2 x64 SP1. The first server is Forest Root and Domain controller, holding the Global Catalog. The second server is also Domain Controller and also holds a copy of the Global Catalog, for failover redundancy. A relatively simple setup. Both servers are identical hardware, purchased at same time, same device drivers, security patches, roles installed etc...I attempted to install Exchange 2007 on the second server, the one holding the duplicate copy of the Global Catalog, and got the error you described . My thinking was this, installing Exchange involves updating the Active Directory Schema, to inlcude Exchange specific changes and additions to the AD Objects. Since my forest structure is a simple one, the first Domain Controller, is the Schema Master, perhaps I can only update the AD Schema on the Schema Master?So I tried installing the first server, and hooray the instll routine runs through with no errors. It may be that you do not wish to install Exchange on the Schema Master, there is a Technet Article which describes running ADPREP from the command line, to update the Schema manually prior to installing Exchange.Hope this helps
April 19th, 2007 1:27pm
But I only have one server in a test rig - it has all AD roles and is running DNS, it's even simpler than yours!. This error is caused by RPC failure. The solution is to delete the administrator's profile and reboot the machine per the solution given in other threads. You got lucky because the admin's local profile on your first server had not been corrupted like the one on the second. Schema updatesin general do not (and should not) have to be run physically on the box holding the Schema Master role, that would be ridiculous in most big IT departments. It is important to note that the machine must be rebooted before logging back on with the affected administrator account - merely logging on using a different account, deleting the affected admin account's profile then logging off and back on as the affected admin (thus creating a new profile) without firstrebooting does not clear the problem. Thisall appears to besecurity and probably .NET framework related. It is worth noting that all non .NET framework related tools and utilities continue to operate normally, anything based on .NET that does LDAP queries in a user context seems to fail. Since a successful install I occassionally get a similar problem. When logged on as administrator, the Exchange Management console will complain of LDAP failurestrying to find the exchange server (which is all running quite happily on the same box). Logging on as another account with the same security and rights works fine. The solution to this is the same, delete the affected admin account's profile and reboot the server. IMHO this is most definitely a bug (or over zealous security quirk) that needs investigation and fixing in SP1.
April 19th, 2007 4:30pm
There is a problem here with user profile lossing the permissions for console and shell access it happened to me when i was messing in outlook 07 on my profile and connecting in outlook to other users accounts.... I then couldn't get into console and shell... and I have had to setup another user and admin exchange as that user.. c'mon MS whats the issue here and how do we fix it.
April 25th, 2007 2:34am
Yep, I agree. The bit that worries me is that in order to clear this condition by deleting the affected admin's profile, you have to reboot the machine - just logging off and back on does not work. That makesme wonder what the hell is going on here security wise. Is some .NETassembly using the security context of whatever user happened to be logged on when it first needed to load, which it thencontinues to useafter the user haslogged off? That would be breaking every rule in the book and then some!
April 25th, 2007 4:13am
Well, guys... me having the same trouble... Had to try the suggested solution, but didn't work.I logged on with a domain user with admin rights, deleted the domain\administrator profile, rebooted the server and re-logged on with domain administrator. NOTHING changed, I still get stuck...Is everybody having the "gc" DNS entry? Where should it be found and how does it have to be set up?My Domain Controller *is* actually a GC server (it has the flag when viewing it from AD Sites & Services), but no DNS records I can see...Need help!Thanks in advance...
June 14th, 2007 4:28pm
I have exch 2007 ssc setup (64 bit) and am trying to configure loadgen (latest version). However it's failing to create users and before I even get to inputting number of users the following is being logged in application event log: Process ExSetup.exe (PID=3772). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall. My loadgen client is on the network switch as the dcs and exchange servers. No problems with DNS. Have run dcdiag and netdiag in verbose mode, all tests being passed. Network has been checked, no errors. Have already tried the deleting the profile which is mentioned in some posts, doesn't work. any ideas pls ?
June 14th, 2007 10:54pm
Can you describe your rig a little more -how many DC's, where are they, where's the DNS andhow does this relate to theserver you're trying to install on.
June 26th, 2007 5:44pm
OK, I have one DC (hostname SERVER), on which resides my DNS Service too. I then added my *new* server (on which I'd like to install Exchange 2007), joined it to the domain and used dcpromo to promote it to be a "seconday" DC. Everything resides in one and only LAN (Class C). If you need more infos, just ask... Thanks so far...
June 28th, 2007 12:13pm
I have duplicated this issue. Exchange works but I can not use Exchange system manager.
August 9th, 2007 11:45pm
Doesrecreating the Admin profile change anything? Also, where did you get the setup disks from? I am hearing rumours that downloaded from MSDN may not be the same as retail/other sources. I must stress these are just rumours, I have absolutely no confirmation of that. I am still of the opinion that this is .NET 2 framework related. Seems to me there is something amiss with the framework that causes it to report RPC failure when there is none as far as non .NET code is concerned. I also doubt this is confined to Exchange. If I had the time I'd go chase it down myself butI am not a free Microsoft help desk. It is up to Microsoft to sort this out,there are enough peoplereporting the problemin a lot of detail. Until that happens, as a consultant I have no choice but to advise clients that Exchange 2007 is notproduction quality and unsupported. When I see setup programs and bits of the installed productwriting entries into event logs for which there is obviously no decode resource I can only suggest somebody at Microsoft buys in bigger chairs for Steve Balmer to throw around.Logging misleading .NET generic error codesfrom exception handling deep down in the code really is the stuff of college labs, not production code. Guys, whichever professor at wherever ran your modules on structured exception handling needs to spend some time in the real world - preferably in an implementation and deployment role or behind a help desk. It's one thing to have a bug somewhere, that's life. It's quite another not to respond to multiple reports of it over a long period of time on a Microsoft forum like this.
August 10th, 2007 2:53am
This weird problem can occur at any moments. I've try a lot of things to try to isolate it. At first I thougth it was an hotfixes problem, after a rollback, nothing was corrected. After I thougth that was related to sharepoint, but uninstalling it don't solve it. I've places a call to Microsoft, but I'm using the 32 bits version and there's no support for that version. I've not tried already the solution to delete and recreate the admin profile, hopefully I'm using VM ware, because it would be very long to reinstall Exchange at every try. It seams to be related only to the management part, because email can be delivered so the Exchange server can talks sucessfuly to AD. The supposition of an RPC call on .net problem is a good idea in the investigation.
August 15th, 2007 8:49pm
I've tried to create another user and add it to the Exchange admin groups, open a session with this user and MAGIC ! that works... I waste almost 3 days on that stupid problem.
August 15th, 2007 11:10pm
same problem here, mine cropped up after installing outlook 2007.
August 28th, 2007 12:52am
Have you solve it ? If you want to, you just have to delete the current user profile and reboot the server, then log back on with the user. This problem occurs because you probably connect to another user's mailbox.
August 28th, 2007 8:11pm
No solution yet. I am able to create another account and use it to run EMC. I don't really want to delete the profile from the account that is having the problem. I did connect to another mailbox with the account that does not work. I don't understand why connecting to another mailbox would cause the problem?
August 28th, 2007 11:55pm
I encountered this exact same issue and tried deleting the Administrator profile, rebooting, but still the same problem. I solved it by disjoining the machinefrom the domain and re-joining it. After my reboot, I logged in as Administrator and it passed all the tests! My environment is a simple Windows 2003 native domain, and the machine I'm installing Exchange 2007 on is a member server (not Domain Controller). I'm also using (testing) the 32-bit version of Exchange 2007, not the 64-bit production version. Hope this helps! --Eric
November 1st, 2007 10:58pm
My situation was this:Domain Controller - Windows 2003Exch 2007 majority node cluster w/Windows 2008 on both nodes.The mailbox role installation on the active node ran fine.I received the "Setup encountered a problem while validating the state of Active Directory" when trying to install on the passive node.I have NO idea why, but I had to disable IPv6 (which I'm not using anyway) and that resolved the issue. What I mean by disable is just deselect it from the properties of the Network Connection.I've seen numerous posts now related to Windows 2008 where either enabling or disabling IPv6 fixes stuff, even if it you're not using it.Hope this helps others.SK
September 24th, 2008 6:47pm
i installed dns and wins services in that server. now setup started without error
October 3rd, 2008 3:30pm
Seems people are still running into this problem. It is caused bystored username/passwords (probably from browser sessions) that cause .NET's RPC interfaces to fail and has nothing to do with DNS. Here is how to fix it without deleting admin profiles etc. 1. Click Start, click Run, type "control keymgr.dll" , and the click OK. 2. Delete any entry that matches the names of the Exchange serversor domain controllers in your organization. If in doubtclear all entries present.
October 3rd, 2008 3:53pm
Code Snippet Seems people arestill running into this problem. It is caused bystoredusername/passwords (probably from browser sessions) that cause .NET'sRPC interfaces to fail and has nothing to do with DNS. Here is how tofix it without deleting admin profiles etc. 1. Click Start, click Run, type "control keymgr.dll" , and the click OK. 2. Delete any entry that matches the names of the Exchange serversor domain controllers in your organization. If in doubtclear all entries present.great, that worked for me, thanx alot.It was the only sollution
October 22nd, 2008 5:44pm
This may not work for everyone but I am installing on windows 2008 and I ran into this issue. I completely closed out the install and went to the cd and right clicked the setup file and ran as administrator. Seemed to work post this trial.Good luck.Matt
January 12th, 2009 11:13pm
Wout de Zeeuw said:This may not work for everyone but I am installing on windows 2008 and I ran into this issue. I completely closed out the install and went to the cd and right clicked the setup file and ran as administrator. Seemed to work post this trial.Good luck.Matt zomg... Matt, you are a genius. I was running into this same problem and found none of the other posts helped clear this up. The weirdest part was that sometimes the installer seemed like it would work, then randomly would drop AD connection... I have a feeling there is something in this domain which was causing confusion within the installer. (Pre win2k naming which is still being used on the network... lulz)... Anyway, I did a run-as using the same account I was on, but with the FQDN of the domain as the prefix and bingo... works like a charm. thanks a lot. I would not have even thought to try this. Only half of my weekend wasted in this case... :)
February 9th, 2009 9:12am
Right-clicking Setup and running it as the Administrator fixed things for me. Thank you. :-)
February 20th, 2009 1:55am
I had the exact same problem with the exchange install and I uninstalled all of the exchange components through add remove programs then I ran the active directory prep switches on the exchangeserver. /preparelegacyexchangepermissions /prepareschema and last /preparedomain This fixed my problem and the reinstall went successfully.Good luck
February 20th, 2009 8:17pm
I had Exact same error installing EX2007 SP1on a test single DC lab.I resolved mine by removing the entry in the hosts file for the DC. Although the entry was correct and all seemed fine, the install finally got passed the error.
December 4th, 2009 5:44pm
Even i had an exact issue in test environment, removing the host entry as suggested resolved it. Thanks
July 22nd, 2010 3:34pm
Same issue for me on Exchange 2007 SP1 x64 test domain on a single server lab setup, when tring to install SP2 or SP3. Remove entry from host file worked. I did have to run ipconfig /flushdns after saving host file before running SP3 setup again.
July 25th, 2010 3:44am
Hi, I have two domains domain.com and child.domain.com. I have a functioning exchange 2007 enviroment in domain.com and this is also where the schema master resides. I am trying to prepare the child domain for a exchange 2007 install and I keep getting an error message that follows Performing Microsoft Exchange Server Prerequisite Check Organization Checks ......................... FAILED Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain icec and site Default-First-Site-Name, and wait for replication to complete. I have used setup.com /prepareAD, /PrepareAllDomains, /PrepareSchema, /Preparedomain, /PrepareLegacyPermisions. My Root Domain Controller is windows 2008 r2 server Child domain controller windows 2003 32bit Please suggest me any solution.. Thanks Crew.
August 19th, 2010 8:38pm
I have fixed my issue by enabling DNS zone transfers.
November 6th, 2010 7:03am
Just as an additional confirmation, I was having this exact same issue and I simply ran the setup as an administrator from the disc and it went ahead without a hitch. I've done at least six installs of Exchange 2010 and this is the first time I ran into this particular issue....
December 7th, 2010 9:06pm
Hi John, I had this issue trying to install SP3 in Exchange 2007. I've got Exchange 2007 and the DC in the same box (I know it's not recommended but this is a lab server). I solved this issue after updating the server's NIC with a DNS to access to the internet. This server only had one DNS server pointed to itself (127.0.0.1). The SP3 installation access to the Internet to find any update...
May 20th, 2011 11:50am