Services not starting - 2007 SP1 on 2008 DC
We have set up a single 2008 server test machine. Run DCPromo on it. It is in it's own domain and the only server. We then installed 2007 SP1 on it, however the setup failed as one of the services wouldn't start. Basically the Exchange Transport service is stuck in "Starting". If i kill it, it will just try and restart. In Event log I have this error: (2114) Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1764). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. And also this "informative" message: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1764). Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: orinoco.2008test.local CDG 1 0 0 1 0 0 0 0 0 Out-of-site: To me, it looks like it is having trouble working out where something in AD is or similar... the "reachability" is showing as 0? Having done some googling, I've checked the server is in the two exchange groups (it was, and is). DNS is also configured correctly as far as I can tell, although the _msdcs subtree is seperate to the main domain one (I've seen this a lot though, and I assume it's not a problem? On our current 2000 server based infrastructure it's within the domain tree). Looking at some other posts and articles, I have tried setting all services to manual and starting them after the server has been up for 15 mins. The ADTopology starts eventually (after a good minute or two) but the Transport one won't and I have the same errors. I have also checked group membership etc, put the server into the Domain Admins group as someone suggested, and also allowed it the permission on the group policy object for "Manage Auditing and Security Log", but still no joy! I've also created my subnet in AD Sites and Services (even though this is the only server - in fact, the only machine full stop!) in this test domain. Is this part of the problem? Is Exchange not designed to sit on a DC now? (and how would this effect future versions of SBS for those that go down that route?)Any pointers appreciated!James
October 2nd, 2007 1:53pm

Does DCDIAG.EXE report any AD Problems?
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2007 3:40pm

The only two weird bits are below. Everything else passes. (Note the machine has changed name as I rebuilt it since the original logs were taken but have exactly the same problem!)I have statically configured the IPV4 address- do I need to do similar with the IP6 one? Or just turn that off? Replication doesn't surprise me too much as it's the only server, but hey-ho...ThanksTesting server: Default-First-Site-Name\2008TEST Starting test: Connectivity Warning during resolution of hostname 2008TEST.test2008.local through IPv6 stack. *** Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. If there are problems accessing this directory server then you may need to check that this server is correctly registered with DNS. ......................... 2008TEST passed test Connectivity Starting test: FrsEvent The event log File Replication Service on server 2008TEST.test2008.local could not be queried, error 0x3a9f "Win32 Error 15007" ......................... 2008TEST failed test FrsEvent Starting test: SysVolCheck
October 2nd, 2007 4:46pm

You have DNS configured on the DC and the DC IP Settings point to itself for primary DNS server? I have only tested with Windows 2008 RC0
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2007 4:54pm

Yes, DNS is set to 127.0.0.1 and the DNS is running. Reran DCDiag with the /TestNS switch, and get these warnings: DC: 2008TEST.test2008.local Domain: test2008.local TEST: Basic (Basc) Warning: The AAAA record for this DC was not found TEST: Records registration (RReg) Network Adapter [00000007] Realtek RTL8139/810x Family Fast Ethernet NIC: Warning: Missing AAAA record at DNS server 192.168.8.6: 2008TEST.test2008.local Warning: Missing AAAA record at DNS server 192.168.8.6: gc._msdcs.test2008.local Warning: Record Registrations not found in some network adapters 2008TEST PASS WARN PASS PASS PASS WARN n/a ......................... test2008.local passed test DNS
October 2nd, 2007 4:58pm

Do you have more than one NIC? If so please disable the one you are not using. Deli
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2007 6:22pm

Yes, but that's already done... Thanks!
October 2nd, 2007 6:56pm

Are you sure you did a Setup /PrepareDomain Exchange doen't seem to be able to contact the AD You might even try to run the ExBPA (Exchange Best Practice Analyser) Find this utility in the Toolbox in the Exchage Management Console Deli
Free Windows Admin Tool Kit Click here and download it now
October 3rd, 2007 1:34am

Did you ever get this figured out? I'm having the exact same problem with the transport service stuck in the starting state on a new exchange 07 sp1 install on 2008 server.
November 15th, 2007 4:50pm

I am not sure if the solution to my problem -> http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2364090&SiteID=17 applies to this situation but if you have run out of ideas it would be worth checking out. Basically, there is a problem with the executables in Rollup 4 and above and how their code signatures are verified by the .Net Framework at boot time. This doesn't sound exactly like your problem but you may want to investigate that avenue. Cheers.
Free Windows Admin Tool Kit Click here and download it now
November 16th, 2007 8:29am

I did run into the same problem. Finally I traced it down to the fact that I have disabled IPv6 on the adapter. This seems to prevent the correct tolology resolution. Re-enabling IPv6 on the adapter resolved the problem. Regards, Christian
November 16th, 2007 5:34pm

Christian, Worked for me, Thanks..
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2008 4:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics