Link to home
Start Free TrialLog in
Avatar of Danstr1
Danstr1

asked on

MSExchangeAL Event ID: 8250 w/ new domain controller

I recently added a new domain controller to my windows2000 & 2003 mixed network. I'm running Exchange 2003 SP2 on a Windows 2003 member server. After transferring all the FSMO's, I dcpromo'd and demoted the previous domain controller to a member server ( I do have more than one GC). The Exchange related services on my Exchange Server keep freezing and I'm forced to reboot the machine. The machine will run for a few hours until the the Exchange services quit on their own and will not allow me to restart. The error message below repeats itself while this takes place.

Source: MSExchangeAL
Category: Service Control
Event ID: 8250

The Win32 API call 'DsGetDCNameW' returned error code (0x54b) The specified domain either does not exist or could not be contacted. The service could not be initialized. Make sure that the operating system was installed propery.

I've attempted to change the domain controller specified in the reciepient update services and was unable to do so. It currently has my old domain controller listed. When I try to browse to the new it's not finding my domain. I have a single domain network.

Any help is greatly appreciated! Thanks! - Dan
ASKER CERTIFIED SOLUTION
Avatar of Vahik
Vahik

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Danstr1
Danstr1

ASKER

I was making matters too complicated and it ended up being a simple DNS configuration issue. Once this was resolved, the error went away and the server began running normally. I still wasn't able to update the recipient update services so I proceeded to follow the steps from the link Vahik posted above. This did the trick! Thanks!
I know this solution is old, but could you repost the link...the one in the solution above doesn't work.  We are having this problem as described. Thanks.