LDAP errors and more in event log after installing Exchange 2003

[willz75]

Hi

I have been trialling Windows 2003 Server with Exchange 2003. After installing Exchange 2003 the server takes a long time to shutdown... anywhere between 10-15mins. Checking the event log I get the following errors relating to Exchange:

LDAP Bind was unsuccessful on directory <server.domain> for distinguished name ''. Directory returned error:[0x34] Unavailable. Event ID 8026 - LDAP Operations.

Then I also get:

Process MAD.EXE (PID=480). All Domain Controller Servers in use are not responding:
<server.domain> Event ID 2102 - Topology.

Can someone please point me in the right direction to solving this?

Thanks
Willz75

 

[peterpark]

I find E2k3 to be fairly easy to install compared to E2K. Try uninstalling completely the E2k3 including deleting the Exchangesvr folder, then reinstall. Did you do a setup /forestprep at your global catalog server, and setup /domainprep on your desired first E2k3 server before running setup? Are ther any existing ADCs in your site? you need to either upgrade these or delete them if no exisitng Ex 5.5 server are around.

 

[willz75]

Hi

forestprep and domainprep were both done on the same server, its the only machine in the domain/AD.

I'll try uninstalling Exchange 2003...

Thanks

 

[xmsre]

Check your ADC config.

John
MOSMWNMTK

 

[robbo007]

Hello,

I have the same problem but my Exchange server 2003 is a standalone server connected to the domain. I have another server that is my DC and GC.

I ran the forest prep etc all from the exchange 2003 standalone server and installed Exchange Server that way. I get the error:

LDAP Bind was unsuccessful on directory SERVIDORFS.fsegura.esp for distinguished name ''. Directory returned error:[0x52] Local Error. DC=fsegura,DC=esp

For more information, click

http://www.microsoft.com/contentredirect.asp.

Should I have run the forest prep etc from my DC? Or does it not matter what server you run it from as the other server has access to the domain?

Any info would be appreciated. I am still in the testing stages of this rollout but I need to put the Exchange server live very soon and this error worries me.

Thanks,

Rob

 

[willz75]

I have managed to workaround this problem by stopping all Exchange services prior to rebooting. This has cut the shutdown time to 1-2 mins and no longer reports errors. It has to do with the fact AD services have shutdown before Exchange is aware and hence it tries to poll AD/Domain controller services and timesout.

 

[PuzzledUNIX]

Make sure that you are running adprep /domainprep and adprep/ forestprep on Domain Controller which carries Global Catalog first and rund dcdiag.exe to test connection configuration as well.

I can go on forever, but go to microsoft webcasts and find one for Feb 18 2003 on upgrading Win2000 to .Net servers and you will find all you need without going through this battle.

Regards,