Error 800706BE "The RPC Server is unavailable" occurs when creating a recovery point with Veritas System Recovery

Problem

Error 800706BE "The RPC Server is unavailable" occurs when creating a recovery point with Veritas System Recovery (VSR)

Solution

Error 800706BA is a standard Windows error with many causes. It most often refers to Microsoft COM Internet Services (CIS) on the Distributed Component Object Model (DCOM) client call RPC_S_SERVER_UNAVAILABLE; the RPC server is unavailable (Windows Event ID 1722). It occurs when a RPC query times out and error 800706BA is the result. The following steps have been shown to resolve this issue:

Retry the Recovery Point backup job after a period of time has elapsed

The error can occur when the VSR system is under high CPU or memory usage by other services or applications. Wait until those applications finish and attempt the backup. For best practice guidelines on performing recovery point creation please refer to VSR User's Guide section "Best practices for backing up your data".

Verify Distributed Component Object Model (DCOM) settings

1. Click Start >  Run.
2. In the Open box, type DCOMCNFG.EXE, and then click OK
3. Expand Component services.
4. Expand computers.
5. Right click the local computer and choose Properties
6. Select the Enable Distributed COM on this computer check box; if not already selected.
7. From the Default Authentication Level, select Connect.
8. From the Default Impersonation, select Identify.

Restart RPC service

Make sure that the remote procedure call (RPC) services are started on the VSR system.
1.      Click Start > Run.
2.      In the Open box, type services.msc, and then click OK
3.      Do the following:
   A·      Make sure the Remote Procedure Call (RPC) Service is started and set to start automatically
      a.      Right click on Remote Procedure Call (RPC)
      b.      Click Properties
      c.      Select Automatic for the Startup Type field
      d.      Click START (if not started) for Service status.
      e.      Click  OK
   B·      Make sure the Remote Procedure Call (RPC) Locator service is started and set to start automatically
      a.      Right click on Remote Procedure Call (RPC) Locator
      b.      Click Properties
      c.      Select Automatic for the Startup Type field
      d.      Click START (if not started) for Service status.
      e.      Click  OK

Stop Anti-Virus Services and disk monitoring tools (e.g. OpenView, Insight Manager)

Applications that make continuous read and writes to the drive VSR is attempting to backup and or if these applications establish a security level lock to the drive at the time VSR is attempting to create its snapshot imaging during the recovery point imaging process could generate this error. Take precautions when disabling security software when using  VSR to create a backup.  

Prior to next schedule backup by VSR, at the next schedule down time of the system, perform a complete shutdown of the system.

Reboot target server 


Verify DNS settings when backing up to a network share location

VSR will report this error occurs when DNS servers are not configured properly when backing up to a network share. Possible network connectivity issue usually DNS is not set properly. If the above suggestions do not correct this error, perform the following steps:

1·      Verify that address for the configured preferred DNS server on VSR client system on the client is valid and reachable.

2·      Use NSLOOKUP and IPCONFIG /ALL to displayed DNS Server settings.  Check the TCP/IP configuration for a local incorrect DNS Server settings. Local settings will overwrite settings from the DHCP Server. By deleting the local DNS setting and switching to auto configuration DNS server settings should be corrected.

3·      Check if the storage and client systems have DNS entries. If not make sure dynamic updates are enabled on the DNS server and schedule a restart of the netlogon server on each DC.

4·      Check for symptoms where new Global Domain Users cannot not be added to a Local Group in Computer Management -> Local Users and Groups -> Groups. Correct this by configuring the network adapters to point to the correct DNS servers on the network.  Verify that the VSR client is pointing to the DNS server on same domain as the share.

5·      Make sure the authoritative time server is set correctly.

6·      Verify that the VSR client system can ping the storage system by fully qualified domain name if not from a command prompt use the ipconfig /flushdns and /registerdns and try again.

7·      Make sure that if the VSR client system has multiple adapters, the adapter that resolves to the storage location is listed first in the adapter binding order in the Advanced settings of Network and Dial-up Connections. Otherwise, DNS resolver may use the DNS server for the adapter listed first that may not resolve to the storage location correctly.