| Previous | Next |
| STATUS_DISK_FULL | STATUS_SERVER_NOT_DISABLED |
STATUS_SERVER_DISABLED
Do not confuse a disabled allocator with a UUID collision
STATUS_SERVER_DISABLED names the GUID allocation server in the Windows NTSTATUS catalog. The status describes allocator service state, not malformed GUID text and not a duplicate identifier. A request reached a path that expected the allocation service to be enabled.
The terminology is legacy. Modern Windows RPC exposes UuidCreate and UuidCreateSequential as UUID-generation APIs, while current UUID syntax and generation models are standardized independently. Microsoft does not document this NTSTATUS as a normal return from those Win32 RPC functions, so an application should not infer that UuidCreate itself has an “enable server” switch. Preserve the native component and call path that produced the status.
Diagnosis should identify who owns the allocator state and which operation attempted to use it. If the result comes from an old subsystem, compatibility layer, or protocol implementation, inspect its initialization and administrative transition log. Generating a random replacement GUID can hide the service-state failure and may break identity relationships expected by the caller.
What to inspect
- Record the native API or subsystem that returned the status.
- Check allocator initialization and state-transition events before changing IDs.
- Do not substitute a locally generated UUID unless the calling contract explicitly permits it.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: UuidCreate
- Microsoft: UuidCreateSequential
- RFC 9562: UUIDs
- The Open Group DCE RPC: UUID generation
Looking for a different code? Search another status or error code.