REPADMIN /replicate Error
Hi Guys,
I have a big problem when I say big I mean it started small and know it's big.
About 3 weeks Ago we had a Hardware Failure in our Main Server, and we had to rebuild the server which has taken us untill today. When we restarted the server and attempted a AD Replication we kepts gettings errors. We then used repadmin /replicate DC-01
DC-02 DC=DOMAIN,DC=INTERNAL
We then got the following responce back
DsReplicaSync() failed with status 8457 (0x2109):
The destination server is currently rejecting replication requests.
So we ran the comands to enable Inbound and outbound Replication and then got thiss error
DsReplicaSync() failed with status 8451 (0x2103):
The replication operation encountered a database error.
We are know completely lost on where or what to do next. We're trying to Replicate from a Windows Server 2003 R2 to Windows Server 2008 R2.
DC-01 = Win 2K8R2
DC-02 = Win 2K3R2
Can anyone give me some help on fixing this, or is there no hope? We know it was a long time to have a server down but it took ages to get the right parts. Any help would be greatly welcome.
DC-01 was re-soted to recover all of out GPO's and User Data that was lots. We recoved it using Windows Server Backup.
I think that all the info that you should need.
Thank you in advanced for your help and for just even reading this post.
TPark IT Technician
May 26th, 2011 3:37pm
Hi,
According to the symptom you described, this issue mostly can be caused by one of the following factors:
l
The inbound and outbound replications are disabled.
l
The DC is experiencing USN rollback.
I would like to suggest you run the following commands to enable inbound and outbound replications:
repadmin /options <DC NAME> -disable_inbound_repl
repadmin /options <DC NAME> -disable_outbound_repl
Note: please replace <DC NAME> with the real DC name.
If it does not work, please refer to the “Software and methodologies that cause USN rollbacks” section of the following article to check
if you restored the DC with an unsupported method.
How to detect and recover from a USN rollback in Windows Server 2003
http://support.microsoft.com/kb/875495
If the DC encounters USN rollback, you should see the events 2095 or 2103 in Event Viewer. You may not see the events if the contents of the log has
wrapped or been cleared. In this case, please identify the issue by using the
repadmin /showutdvec command. For the detail information, please refer to the “Detecting a USN rollback on a domain controller that is running Windows Server 2003” of the article above.
For further troubleshooting information, please also refer to the following Microsoft KB article:
How to troubleshoot Active Directory operations that fail with error 8456 or 8457: "The source | destination server is currently rejecting replication
requests"
http://support.microsoft.com/kb/2023007
Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 11:29pm
Hello,
as this sounds that you have reinstalled a new server with the old name from the crashed one, have you run metadata cleanup BEFORE to remove all old entries from the broken machine?
If was not done and the new installed machine is using the old name then please remove it complete, run metadata cleanup and reinstall the server again.
http://msmvps.com/blogs/mweber/archive/2010/05/16/active-directory-metadata-cleanup.aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
May 27th, 2011 11:41am


