LDAP Error 81
-
Monday, August 29, 2011 12:56 PM
Our environment has a root and several child domains running W2K8 SP2. For 1.5 days a server was down that has a replication partner for the same child domain in a difference site. After network services were restored, I ran KCC * from the root. All were successful except the down child domain. There I get the error: '[d:\longhorn\ds\ds\src\util\repadmin\repldap.c, 1415] LDAP error 81 (Server Down) Win32 Err 58.'
All of the servers are online now. Would I still need to perform a metadata clean up? Or, will AD clean itself? If I need to clean up AD I am not certain of the steps involved with the clean up.
Thanks, Jesse
All Replies
-
Monday, August 29, 2011 1:10 PM
Hello,
if a DC was down for that short period of time you shouldn't have any problem after reconnection, it should automatically start replicating. Before doing anything like metadata cleanup please upload the following files, so we can get an overview:
ipconfig /all >c:\ipconfig.txt [from each DC/DNS Server]
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)]
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)
As the output will become large, DON'T post them into the thread, please use Windows Sky Drive (skydrive.live.com) [with open access!] and add the link from it here. Also the /e in dcdiag scans the complete forest, so better run it on COB.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked As Answer by Bruce-LiuModerator Wednesday, September 07, 2011 7:36 AM
- Unmarked As Answer by jwmms Wednesday, September 07, 2011 7:10 PM
-
Monday, August 29, 2011 1:19 PM
Hi,
you have to do a metadata cleanup ONLY when you want to remove a failed DomainController which can´t be removed with a regular demotion of the DC.
When I unterstand your post correctly, then your DC was only down for a short period of time.
Please check your replication status
- use dcdiag /v /c /d /e
- repadmin /replsummary *
- repadmin /showrepl *
Look for errors in the results and please post errors when you find some.
Martin
- Marked As Answer by Bruce-LiuModerator Wednesday, September 07, 2011 7:36 AM
- Unmarked As Answer by jwmms Wednesday, September 07, 2011 7:10 PM
-
Tuesday, August 30, 2011 5:35 AMModerator
Metadata cleanup is performed to remove the DC & its references from the domain when either DC is crashed or permanently offline, which doesn't look to be the case from your post. Since, DC was down for 1.5 days, reconnecting should make it work as this is not the big deal.
Make sure proper DNS is specified in child domain DC & all the DC related (DNS/FRS/KDC/Netlogon)services are working.
http://technet.microsoft.com/en-us/library/cc756688%28WS.10%29.aspx
http://support.microsoft.com/kb/887430
How many DC's are there in the child domain? Could you post relevant error message from the event log.
I have outlined the metadata cleanup explanation & steps, but until DC is crashed or permanently offline metadata cleanup is not required.
Metadata Cleanup of a Domain controller
http://awinish.wordpress.com/2011/05/08/metadata-cleanup-of-a-domain-controller/
Regards
Awinish Vishwakarma
MY BLOG: http://awinish.wordpress.com
This posting is provided AS-IS with no warranties/guarantees and confers no rights.
- Marked As Answer by Bruce-LiuModerator Wednesday, September 07, 2011 7:36 AM
-
Wednesday, September 07, 2011 7:03 PM
My apology for the delay. Here is the requested link:
https://skydrive.live.com/redir.aspx?cid=2bf0e0f323e2d734&resid=2BF0E0F323E2D734!350
Thanks, Jesse
-
Tuesday, April 10, 2012 2:57 PM
hello
i have a same problem, could you help me?

