0x800706BA

The RPC server is unavailable

Last reviewed 2026-07-18 by the Just Software engineering team · also seen as 800706ba, RPC_S_SERVER_UNAVAILABLE, the rpc server is unavailable

What it means

0x800706BA wraps Win32 error 1722, RPC_S_SERVER_UNAVAILABLE. In PKI contexts it means the client (a domain member, an NDES server, or a management console) attempted an RPC/DCOM connection to the certification authority and could not establish it. It is a transport failure — the request never reached the CA's application logic.

Common causes

  1. Active Directory Certificate Services (CertSvc) stopped on the CA server.

  2. Firewalls blocking TCP 135 (RPC endpoint mapper) and/or the dynamic RPC port range between client and CA.

  3. DNS pointing at the wrong host, or the CA host renamed/retired while its AD enrollment objects remain.

  4. The CA server is up but overloaded or mid-reboot during patching windows.

How to fix it

  1. Reproduce cheaply from the failing host: certutil -ping <CAHostName>\<CACommonName> — success rules out transport and points you at permissions instead.

  2. On the CA: Get-Service certsvc must be Running; start it and check the Application log if it will not stay up.

  3. Verify firewall rules allow TCP 135 plus the dynamic RPC range (default 49152-65535) from clients/NDES to the CA.

  4. Check DNS: nslookup the CA host from the client and confirm it resolves to the current server, not a stale record.

An unhandled error has occurred. Reload 🗙