Error 58 Replication
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of
Replsum Error 58
this site About Us Learn more about Stack Overflow the company Business Learn repadmin error 58 more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _
Active Directory Replication Error 58
Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody experienced the following operational errors trying to retrieve replication information 1722 can answer The best answers are voted up and rise to the top Repadmin gives operational error 58 up vote 3 down vote favorite While testing some remote DC's, "repadmin /replsummary" ended with an error of Experienced the following operational errors trying to retrieve replication information: 58 - mydc1.mydomain.com 58 - mydc2.mydomain.com Information for "Source DSA" for mydc1 and mydc2 both show up with experienced the following operational errors trying to retrieve replication information 8341 0 fails/errors; the information is lacking under Destination DSA. This domain controller I ran the command on (remotedc1) can see mydc1 and mydc2. Pinging from remotedc1 to mydc2 and mydc1 shows an average time of 43ms... What causes this kind of error? active-directory replication share|improve this question asked Feb 5 '13 at 19:58 Bart Silverstrim 28.7k94979 I know you guys were offline for quite a while. Any chance that your DCs in NYC were offline long enough to hit the 180 day tombstone lifetime? –MDMarra Feb 5 '13 at 20:06 Other DC's in another location can see mydc1 and mydc2 without error... –Bart Silverstrim Feb 5 '13 at 20:08 We've had internal networks up before the 180 days also :-) –Bart Silverstrim Feb 5 '13 at 20:09 Ok, that's good at least. What happens when you try and force a sync with repadmin /syncall /APed? Any interesting feedback? –MDMarra Feb 5 '13 at 20:10 1 OK, PETE, I GET IT! NO TOMBSTONES :) –MDMarra Feb 5 '13 at 20:13 | show 2 more comments 1 Answer 1 active oldest votes up v
repadmin error 58 Need help with repadmin error 58 4K Views Last Post 04 December 2012 CKaiser posted this 03 December 2012 Greetings. Need some help with replication. I haven't done large-scale stuff in a while, so I'm rusty on this...
Experienced The Following Operational Errors Trying To Retrieve Replication Information 1326
Got around a dozen sites. Not all connected to each other by IP, but all experienced the following operational errors trying to retrieve replication information 55 connected to 2 of the sites (hub/spoke with the hubs connected). Just brought a new location online. Connectivity is a Cisco VPN, other
Repadmin Error 1722
sites are Watchguard VPN. Spun up a DC, no issues with DCPromo, DNS working. We changed replication. Was previously single site link and had chosen a poorly connected site as the hub. Chose two hubs, set up site links http://serverfault.com/questions/475774/repadmin-gives-operational-error-58 between each site and the two hubs, set costing to favor one hub. After about 4 hours, replication has calmed down but I am still seeing problems. When I run repadmin /replsummary, I get error 58 on 6 of the DCs. Notable is that there is no direct IP connectivity from this site to these DCs. I show recent replication traffic as per this run on TBS-DC1: C:\Windows\system32>repadmin /replsummary Replication Summary Start Time: 2012-12-03 14:47:36 Beginning data http://www.activedir.org/thread/need-help-with-repadmin-error-58/ collection for replication summary, this may take awhile: .............. Source DSA largest delta fails/total %% error AD2 56m:03s 0 / 5 0 CONSERVER 10m:58s 0 / 5 0 CPARK-DC1 11m:03s 0 / 5 0 DISNEY-DC2 10m:58s 0 / 5 0 MSN-DC1 10m:58s 0 / 5 0 MTV-DC1 10m:59s 0 / 5 0 PLAYA-DC1 10m:58s 0 / 5 0 SEARISE1 10m:04s 0 / 20 0 TBS-DC1 11m:03s 0 / 5 0 THEPOINTE-DC1 11m:03s 0 / 5 0 WR-DC1 10m:58s 0 / 5 0 Destination DSA largest delta fails/total %% error AD2 02m:16s 0 / 5 0 DISNEY-DC2 06m:41s 0 / 5 0 SEARISE1 55m:58s 0 / 50 0 TBS-DC1 11m:07s 0 / 5 0 THEPOINTE-DC1 11m:23s 0 / 5 0 Experienced the following operational errors trying to retrieve replication information: 58 - MSN-DC1.[domainname] 58 - CONSERVER. [domainname] 58 - CPark-DC1. [domainname] 58 - WR-DC1. [domainname] 58 - MTV-DC1. [domainname] 58 - Playa-DC1. [domainname] If I run an NSLookup for ldap.tcp.dc.msdcs.[domainname], it comes back with the names of all those DCs included. All those DCs are currently in use and I can connect to them. Question is, should I ignore the 58 errors because there's no direct connectivity? Can I safely assume that if replication goes from, for example, TBS-DC1 to Searise1 and from Searise1 to Playa-DC1, all replication will be OK? Or is there another problem I need to troubl
58 while executing command - repadmin /replsum /bysrc /bydest After running command " repadmin /replsum /bysrc /bydest" to check replication status in one of the domain I encountered error code - 58 and the https://citruspk.wordpress.com/2012/11/29/active-directory-replication/ actual output as follows: Experienced the following operational errors trying to retrieve replication information: 58 - FQDN name of Domain Controller. I have tried to search for this error code on numerous https://community.spiceworks.com/topic/596809-can-t-find-cause-for-ldap-error-81-server-down-win32-err-58 sites but could not get much information. I executed below command in order to understand why this error is occurring. net helpmsg 58 Output as below: It merely says that server cannot perform error 58 the requested operation which in this case is running command - repadmin /replsum /bysrc /bydest. This error went away without performing any troubleshooting steps on next day but it does occur on some of the domain controllers but goes away next day. I haven't found any solution to this problem except that I found this has been experienced by some other users and it has been discussed experienced the following widely on Windows Server Forums ( here & here). 2. Commands to execute when replication reports shows errors. I will list out some of the commands which can be executed to deep dive more on the issue and of course resolve the issue of replication. a. Verify Domain Controllers Are in Sync repadmin /showchanges
Follow 5147 Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS New Server and Network Brand new Windows 2008 Standard DNS Server and Gigabit Network powered by Cisco. 2003=>2012 Domain Migration Migrate 2003 VMWare domain up to a 2012 Hyper-V domain. All SQL, Exchange and File Servers will be based on Windows Standard 2012 Server Hyper-V VMs. 74-409 Study Cluster Needed to create a lab cluster environment for my 74-409 exam studies. Updated: 4/5/2014 TECHNOLOGY IN THIS DISCUSSION Microsoft Windows Server Microsoft Windows Server 2003 Join the Community! Creating your account only takes a few minutes. Join Now I'm having a hard time trying to identify the issue... So far I've ran following tests without any errors, on both the PDC and a second DC, which both give the "LDAP error 81 (Server Down) Win32 Err 58" error after running "repadmin /showrepl /all /verbos": repadmin /replsum dcdiag /test:dns /s: /DnsBasic dcdiag /v /c /d /e /s: repadmin /syncall repadmin /showrepl * also used the AD Replication Status Tool - no errors detected. Reply Subscribe 13 Replies Thai Pepper OP britv8 Oct 3, 2014 at 1:00 UTC OS version? any old dcs in the repladmin? 0 Sonora OP Joseph9297 Oct 3, 2014 at 2:12 UTC oh, yea... sorry. I posted two separate questions about these DCs and forgot to mention OS version on this one. 7 DCs, all running windows server 2003, the PDC is STANDARD R2,SP2, others are STANDARD or ENTERPRISE, R1 SP2. When you say old dcs... if my comment above doesn't answer that question and you are referring to physical age, yes. I do have one physical box that has been around for 11 years. The others are all virtual - I do not know their actual "age". The PDC has only been in service a few years. 0 Thai Pepper OP Helpful Post britv8 Oct 4, 2014 at 8:55 UTC Old DCs - I mean dcs that no longer exist in real life, but exist in AD (e.g. under NTDS settings for servers in sites and services) This gives you a bit of an idea of what I mean. http://blogs.technet.com/b/askds/archive/2010/01/27/dcdiag-advertising-test-with-error-81.aspx Example in this one was a DC that was turned off, but not properly demoted, and another DC was built