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
Danstr1Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VahikCommented:
http://exchange.mvps.org/E2K3/modify%20rus%20dc.htm

this is an easy fix....but u may have other problems on ur network.....u need to do a lota testing...like
test to see who are the current FSMO holders
clean up active directory...
check DNS for the old GC and DC and make sure the new ones are listed....
run NETDIAG and DCDIAG and see if any problems show....
maybe run forestprep and domainprep again from exchange CD....

But befroe u do anything...remember if nothing is broken do not try to fix it.....
take care and good luck..
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Danstr1Author Commented:
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!
0
kfallerCommented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.