| Previous | Next |
| ERROR_NOT_SUPPORTED_ON_SBS | ERROR_HOST_DOWN |
ERROR_SERVER_SHUTDOWN_IN_PROGRESS
The server is in its shutdown sequence.
ERROR_SERVER_SHUTDOWN_IN_PROGRESS is Win32 error 1255 (0x4E7). The server has entered a lifecycle state in which new operations are rejected while active work, services, or storage are being drained. This is distinct from a server that is merely unreachable: the shutdown state can be known and intentionally reported.
Expected behavior during shutdown
- new sessions and long-running jobs should be refused
- in-flight work may finish, cancel, or be checkpointed according to policy
- service discovery can still resolve the server while application endpoints close
- clients may observe a mixture of successful and rejected calls during draining
- restarts and cluster failovers can move the service to another node
Telemetry to preserve
Record the server identity, shutdown initiator when available, announced deadline, operation type, request ID, whether the request had started, and any alternate endpoint. Correlate 1255 with service-control, cluster, update, and system shutdown events. A client log containing only “server unavailable” loses the important fact that the rejection was deliberate.
Diagnostic sequence
Determine whether the shutdown is planned, caused by maintenance, or triggered by a failure. Check the server’s System and service logs and verify whether a restart or failover is expected. On a remote client, do not infer that the machine is powered off solely from 1255; it may still be completing cleanup.
Inspect server code for the order of state transitions. The service should publish “draining” before destroying shared resources and should not accept requests after dependencies begin teardown. If 1255 persists after restart, stale load-balancer health or a cached endpoint may be directing clients to an old instance.
Retry and recovery
Read-only idempotent requests can be retried after bounded backoff or against a healthy replica. Writes require knowledge of whether the server accepted them before shutdown. Use request identifiers or status queries to avoid duplicating a change after reconnection. User interfaces should explain maintenance or restart rather than continuously prompting for credentials.
Difference from related shutdown codes
ERROR_SHUTDOWN_IN_PROGRESS is a general system shutdown status. ERROR_SHUTDOWN_IS_SCHEDULED indicates a shutdown has been scheduled but may not have begun. Error 1255 specifically identifies the server machine as already shutting down.
Example
A file-processing server begins an update restart and stops accepting uploads. A client receives 1255 before sending any bytes, waits for service discovery to advertise the replacement node, and submits there. Retrying immediately against the draining node would only add load and delay shutdown.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: Service Control Handler Function
- Microsoft: Shutting Down
- Microsoft: InitiateSystemShutdownExW function
Looking for a different code? Search another status or error code.