Updating partition details error

Posted by / 06-Oct-2017 00:50

We've tried adjusting the various timeouts but that just made the server run slightly longer before dying.

On the second server, when the problem occurs requests take a long time and when they are done all you see is the service unavailable page.

On SINGAPOREDC, the Rpc is listening on TCP port 135. It appears to have all of its DNS records in place.

It is open in the firewall, and querying the port returns that it is listening. Performing a dcdiag /test:replications on SINGAPOREDC shows errors 1256 (The remote system is not available) and 1722 (The RPC server is unavailable) replicating from the central DC to the branch DC. Performing repadmin /replsummary also shows error 1722, with 4 fails out of 5 attempts. Forcing a replication via Sites & Services sometimes throws an error saying it can't communicate with the server.

Performing dcdiag /test:dns /v /e on SINGAPOREDC gives many errors, as shown below.

Note that while it fails communicating with some domain controllers, it passes for others.

updating partition details error-6updating partition details error-60updating partition details error-23

One of my branch domain controllers, SINGAPOREDC is not replicating with its replication partner in our data center, CENTRALDC-02.

One thought on “updating partition details error”