0x800705B4

Timeout talking to the SCEP endpoint

Last reviewed 2026-07-18 by the Just Software engineering team · also seen as 800705b4, ERROR_TIMEOUT

What it means

0x800705B4 wraps Win32 error 1460 (ERROR_TIMEOUT) — "This operation returned because the timeout period expired." The device sent its SCEP request (or tried to) and gave up waiting for a response. The endpoint is reachable enough to connect, but too slow to answer — or something between device and server is holding the request.

Common causes

  1. NDES/SCEP server overloaded, or its issuing CA responding slowly, so requests exceed the client timeout.

  2. The CA performs slow revocation or directory lookups server-side before issuing.

  3. A proxy or TLS-inspection appliance holds or re-queues the SCEP POST.

  4. Large enrolment waves (new deployment ring, mass renewal) hitting a single NDES server at once.

How to fix it

  1. Time a manual request: measure how long the SCEP URL takes to answer from the same network. Multi-second responses point at server-side processing, not the client.

  2. Check CPU, memory and IIS queue length on the NDES server during failure windows; scale up or add a second NDES server behind a load balancer if it is saturated.

  3. On the CA, confirm it responds quickly to certutil -ping from the NDES server; slow CA responses cascade into client timeouts.

  4. Stagger large assignments (deployment rings) so renewals do not stampede the endpoint.

An unhandled error has occurred. Reload 🗙