8457 The destination server is currently rejecting replication requests.
One of my DC's has been offline for a few days, and after rerconnecting to the network, will not replicate with the other DC's on the domain.
I have run repadmin /showreps and I get and error:
"Can't retrieve message string 8456 (0x2108), error 1815"
The Directory Service Event Viewer displays an EventID: 1925
Description:
The attempt to establish a replication link for the following writable directory partition failed.
Additional Data
Error value:
8457 The destination server is currently rejecting replication requests.
I am pretty sure that this has occurred becuase of the offline time. Can any expert help me get this DC to successfully replicate again without having to do something drastic, like dcpromo.
Jim
I have run repadmin /showreps and I get and error:
"Can't retrieve message string 8456 (0x2108), error 1815"
The Directory Service Event Viewer displays an EventID: 1925
Description:
The attempt to establish a replication link for the following writable directory partition failed.
Additional Data
Error value:
8457 The destination server is currently rejecting replication requests.
I am pretty sure that this has occurred becuase of the offline time. Can any expert help me get this DC to successfully replicate again without having to do something drastic, like dcpromo.
Jim
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This worked for me!
Thanks You Jim for the post!
Karl
Thanks You Jim for the post!
Karl
Same worked for me. Good solution. Thanks for posting back.
Thanks a lot Jim, this helped me a lot
this fixed my issues as well, thanks!
Worked for me I just had one more step that I needed to go through. Under the active directory sites and services I had to goto all tasks -> check replication topology and that stopped the errors and allowed replications to start flowing again.
Worked great. Thank you for your help.
hi there !
sadly, it didn't make it for me.
my secondary DC stayed at rejecting the replication.
i found though that the "replicate now" function from sites & services didn't work, but when forcing the replication from my primary DC in a CLI on the secondary one, it worked.
i booted the primary DC in restore mode and made an authoritative restore from the existing database (no backup involved). It update the USN and then, the replication occured again.
just in case of someone might need this...
bye
sadly, it didn't make it for me.
my secondary DC stayed at rejecting the replication.
i found though that the "replicate now" function from sites & services didn't work, but when forcing the replication from my primary DC in a CLI on the secondary one, it worked.
i booted the primary DC in restore mode and made an authoritative restore from the existing database (no backup involved). It update the USN and then, the replication occured again.
just in case of someone might need this...
bye
You are the man thanks
that is really solve the problem