This object monitors Remote Procedure Call (RPC) registration and creates a Critical alert if it detects that DFS Replication was unable to start an RPC listener. It does so by looking for the presence of DFS Replication Event 1208.
An unhealthy state of this monitor indicates that DFS Replication couldn’t start an RPC listener and the DFS Replication service is stopped. The RPC listener is needed to communicate with replication partners. This can occur for the following reasons:
The server doesn’t have enough available memory.
The Remote Procedure Call (RPC) service is stopped.
Restart the DFS Replication service
To restart the DFS Replication service from the Operations console, do the following:
1. Click Stop DFS Replication Service.
2. Click Start DFS Replication Service.
To restart the service remotely by using the sc command, open a command prompt window and then do the following:
1.To stop the service, type the following command, where <servername> is the Universal Naming Convention (UNC) path to the remote server:
sc <servername> stop dfsr
2.To confirm that the service is in the STOPPED state, type the following command:
sc <servername> query dfsr
3.To restart the service, type the following command:
sc <servername> start dfsr
Note: To restart a service, you must be a member of the local Administrators group on the affected server. You can also restart services using the Services snap-in, the Windows PowerShell Start-Service and Stop-Service cmdlets, or command-line tools such as net stop and net start.
This monitor automatically resets to a healthy state when the issue is resolved.
To confirm that the service is in the STARTED state from the Operations console, click Query DFS Replication Service Status.
To confirm that the service is in the STARTED state remotely by using the sc command, open a command prompt window and then type the following command:
Note: To query the service state, you must be a member of the local Administrators group on the affected server.