The source server is currently rejecting replication requests.

We are running few servers at office with about 10 users connected. Since past few days it is giving me an error message saying “The source server is currently rejecting replication requests.” We also have a secondary DC crash just after I restored the data from image backup. When I tried to replicate directory I received the following error message:

Quote:

---

Source: Default-First-Site-Name\PrimaryServer
******* 35 CONSECUTIVE FAILURES since 2007-05-31 15:47:35
Last error: 8456 (0x2108):
The source server is currently rejecting replication requests.

---

Can anyone please tell me how can I fix this error message?

Sorry of for the incomplete post. I forgot to mention this. I'm also receiving the folllowing error:

C:\Program Files\Support Tools>repadmin /showvector /latency DNname
Caching GUIDs.
...
DsReplicaGetInfo() failed with status 8453 (0x2105):
Replication access was denied.

Probably there would have been some problem during Restore process.
Restoring DCs from imaging ISN'T a supported method of AD restoration. So just click this URL

http://support.microsoft.com/kb/885875

I had a similar issue on a Windows 2003 server which also doubled as an Exchange server - I used Acronis to move the O/S from old failing hardware to new hardware and in doing so broke replication. When trying to replicate I got the error: "The source server is currently rejecting replication requests" I also got the same error when trying to run dcpromo.

dcpromo /forceremoval was not an option for me since it would orphan my Exchange server. I could have moved all mailboxes then forced demotion but chose to call microsoft support hoping there was a trick to fix this issue since the server was now in good physical shape and all services were functioning however because the GUID changed AD picked up on the Acronis Image I preformed and assumed a USN rollback scenario.

Microsoft support did have a solution for me and ran the following commands which then allowed my server to replicate data again.

Please keep in mind this worked for me because all i had done was change my server hardware via Acronis (like Ghost) and did not have any other issues beyond replication.

enabling in bound replication - ran at command prompt of orphaned domain controller

repadmin /options servername - disable_inbound_repl
=========================================
enabling outbound replication

repadmin /options servername - disable_outbound_repl
======================================

I had the same issue. Enabling replications as mentioned here helped me to resolve it.

http://technet.microsoft.com/en-us/l...8WS.10%29.aspx


Thanks a lot