| Previous | Next |
| STATUS_INVALID_ID_AUTHORITY | STATUS_INVALID_VOLUME_LABEL |
STATUS_AGENTS_EXHAUSTED
The exhausted resource is an authority-agent namespace component
STATUS_AGENTS_EXHAUSTED is more specific than a generic GUID allocation failure. The Windows status text says that no authority-agent values remain for a particular identifier-authority value. The identifier authority is therefore part of the failing allocation context and should be logged explicitly.
Do not merge this status with STATUS_GUIDS_EXHAUSTED. One names exhaustion inside an authority agent; this one names exhaustion of agent values associated with an identifier authority. The common NTSTATUS catalog does not publish the legacy allocator’s field widths or recycling rules. Modern UUID standards and Windows RPC creation APIs use different public abstractions, so their existence is not evidence for a particular reset or wraparound procedure here.
Diagnosis should retain the authority value, requested operation, allocator state version, and any administrative configuration that partitions identifiers by authority. If multiple nodes share the allocator, compare state ownership and restoration history. Do not recycle an old agent value merely to clear the error: reuse could undermine the uniqueness property the allocator is trying to preserve.
What to inspect
- Record the identifier-authority value associated with the failure.
- Compare allocator state across nodes or restored copies before making changes.
- Avoid manual agent-value reuse unless the owning allocator explicitly documents it.
References
- Microsoft Open Specifications: NTSTATUS values
- RFC 9562: UUID uniqueness considerations
- Microsoft: UuidCreateSequential
- Microsoft: UuidCompare
- The Open Group DCE RPC: UUID generation
Looking for a different code? Search another status or error code.