LDAP Bind unsuccessful on directory error shutting down Exchange 2003
Our Exchang eserver is up and running BUT i am having an issue with it going down every so often with this error and I have to restart the server. Over night it actually started operating again itself. EVENT ID: 8026 Event Type: Error Event Source: MSExchangeAL Event Category: LADP Operations Description: LADP Bind was unseccusful on Directory <Fully qualified Domain Name of windows domain controler> for distinguished name" Directory returned error [0x51] Server Down. I tried to follow what microsoft suggested but nothing has changed. This was a NEW clean Exchange install. Thank you for your time.
September 6th, 2006 11:45pm

This typically is because RUS is pointing at an invalid server. Have you verified thatthe DC is valid inESM under Recipient Update Services?
Free Windows Admin Tool Kit Click here and download it now
September 7th, 2006 5:07pm

I am having the same issue - and since exchange server is down - ESM does not work - how can I check to make sure RUS is pointing to the right place?
January 31st, 2007 7:31pm

You can flow this KB http://support.microsoft.com/kb/272552/en-usresolution this issue
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2007 4:44am

appreciate the prompt posting. Unfortunately, the article applies to a server upon which dcpromo has been run. This is a small business server what has never been demoted - running on original installation confirmation. However, I was able to get the exchange system manager to run breifly after restarting the server. This morning exchange would crash everytime about 2-5 minutes after boot up. While having access to the system manager I went into the recipient update service settings and asked it to "rebuild". After rebooting a couple of times, the errors stopped occuring (previously about 1 every 2 seconds) in the event log and everything seemed to get stable again. Not sure the rebuild is what did it but it appears to be working OK now.
February 1st, 2007 8:12am

This look like you forget reboot Domain Controller after you configure DC to GC role. When you configure DC to GC role,the event log will remind you reboot to take effect.
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2007 6:09am

Did you ever resolve this matter? I am having the same problem.
October 31st, 2007 4:10pm

Got the same problem. How can we resolve this issue?
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2007 12:16am

This fixed my issue. I demoted a DC, but the RUS was still pointed to it. Thanks for the info!!
December 3rd, 2007 9:49pm

I had this issue after i install VMware exchange 2007 SCC Cluster and Server 2008 domain controller.http://www.infotechguyz.com/exchange2007/exchange2007scc.htmlweird, i just demoted the server 2008 domiain contoller..ahhh!!
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2008 9:36pm

Did any body reslove this matter so far. I am also having the same problem. When restart the exchange 2003 it works fine, but after few days Itcombe back withthe same errormessage. Thanks - BJ
August 2nd, 2008 10:47pm

Go to Control Panel > Network Connections > Advanced > Connections and move the network interface that has access to your global catalog servers to the top of the list. No reboot or service restart is necessary hope that helps Pedro Pereira
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2008 1:52pm

Thank you Jammy, this solved my issue. My warnings are gone and the network is humming along.Torentine
August 28th, 2008 1:51am

I had the same problem with one of my exchange servers and tried several different solutions. Pedro's post is correct and is the proper configuration when there multiple network interfaces on a single server. However, in my situation the network interface was listed first. By moving it down the list and clicking OK and then to the top of the list and clicking OK solved the LDAP Bind issue. Thank you for bringing this up Pedro.
Free Windows Admin Tool Kit Click here and download it now
October 7th, 2008 6:26pm

in my case i had a same problem. my organization have a 1 DC and 5 ADC. exchange server is pointing toward failed ADC. i have change the location of recipitant update server to working DC. now there is no more error log.
September 25th, 2011 12:01pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics