Solved

MSExchangeAL Event ID: 8250 w/ new domain controller

Posted on 2006-07-12
3
5,452 Views
Last Modified: 2008-08-28
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
0
Comment
Question by:Danstr1
3 Comments
 
LVL 26

Accepted Solution

by:
Vahik earned 500 total points
ID: 17095921
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
 

Author Comment

by:Danstr1
ID: 17103639
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
 

Expert Comment

by:kfaller
ID: 33824806
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

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question