Solved

MSExchangeAL Event ID: 8250 w/ new domain controller

Posted on 2006-07-12
3
5,411 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
Comment Utility
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
Comment Utility
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
Comment Utility
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

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a Distribution Group 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 >>…
This video discusses moving either the default database or any database to a new volume.

763 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now