The dsproxy is a component that does lookups for MAPI clients against AD. The System Attendant can't start because dsproxy can't connect to (although it apparently found what it thought was) a GC. Back in the good old/bad old days, this was usually because the GC role was added to a domain controller and it either messed up somewhere along the replication, or replication of the GC partition completed and the domain controller was never rebooted afterward. There can also be perf issues if the DC/GC chosen is the PDC Emulator. I'd start with: 1. Reboot the 2003 DC/GC that exchange knows about. 2. Wait for it to come back up. 3. Wait 15 minutes and check the application log for event ID 2080 4. Make sure that in the 2080 Exchange recognizes both DC/GCs as GCs. 5. Restart the 2008 GC and wait for it to come back up 6. Check and make sure both are Identified as GCs in the 2080 after 15 minutes. 7. You may want to exclude the PDC emulator, that is chosen by defalt as long as exchange understands the 2008 DC/GC is up and it finds it (see http://support.microsoft.com/kb/298879) 8. restart the exchange services.

Our exchange server 2007 hung, rebooted the server and now the msexchangesa will not start. I ran nslookup the server, everything looks good. Ran Best Practices Health check, everything looks good except for System Attendant not running. Exchange is running on member server windows 2003 r2 sp3. I can ping the dns server and the dns server can ping the exchange server. We only have one exchange server. The errors seem to be two. dsproxy error 2060 and then msexchangesa 1005. I know it points to dns, but cannot find the problem. I do have another DC/GC running on windows server 2008, however the only one showing up on modify domain controller is my windows 2003 DC/GC. I added my windows 2008 dns to the internal/external dns, however, SA will still not start.

Could you post the complete error along with the Hex Codes you getting. You can mask the server namesJasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:Exchange 2010 | Exchange 2007 | MCTS:OCS 2007 | Exchange 2010 | Exchange 2007 | MCSA:Messaging | Security | MCSE:Messaging | Security

The dsproxy is a component that does lookups for MAPI clients against AD. The System Attendant can't start because dsproxy can't connect to (although it apparently found what it thought was) a GC. Back in the good old/bad old days, this was usually because the GC role was added to a domain controller and it either messed up somewhere along the replication, or replication of the GC partition completed and the domain controller was never rebooted afterward. There can also be perf issues if the DC/GC chosen is the PDC Emulator. I'd start with: 1. Reboot the 2003 DC/GC that exchange knows about. 2. Wait for it to come back up. 3. Wait 15 minutes and check the application log for event ID 2080 4. Make sure that in the 2080 Exchange recognizes both DC/GCs as GCs. 5. Restart the 2008 GC and wait for it to come back up 6. Check and make sure both are Identified as GCs in the 2080 after 15 minutes. 7. You may want to exclude the PDC emulator, that is chosen by defalt as long as exchange understands the 2008 DC/GC is up and it finds it (see http://support.microsoft.com/kb/298879) 8. restart the exchange services.