What does Windows error code 1395 (ERROR_LICENSE_QUOTA_EXCEEDED) mean?

 
Previous Next
ERROR_NO_USER_SESSION_KEY ERROR_WRONG_TARGET_NAME

ERROR_LICENSE_QUOTA_EXCEEDED

The service has reached its licensed connection capacity.

ERROR_LICENSE_QUOTA_EXCEEDED is Win32 error 1395 (0x573). The accessed service is licensed for a limited number of connections and already has as many active connections as it may accept. The limit is an entitlement constraint, not necessarily a CPU, memory, socket, or operating-system resource shortage.

What to verify

  • the purchased or configured concurrent-connection entitlement
  • how the service defines a connection, session, device, or named user
  • whether disconnected clients remain licensed until a lease expires
  • duplicate sessions created by retries, reconnects, or load balancers
  • whether every service node sees the same licensing state

Evidence to collect

Record the service instance, license edition and version, configured limit, active-session count, session identifiers, user or device mapping, lease expiration, cluster node, and time of denial. Preserve vendor licensing logs and the connection lifecycle around clients that recently disconnected. Do not include license keys in ordinary telemetry.

Diagnostic sequence

Use the supported administration interface to compare entitlement with active consumption. Identify stale sessions and determine why their normal close or heartbeat path did not release capacity. Check whether health probes, background agents, or retry loops are counted as licensed clients. In a cluster, verify that the license manager and all nodes agree on ownership.

Do not assume that increasing an operating-system connection setting will affect error 1395. Likewise, killing random processes may free no licensed seats and can corrupt active work. Confirm the product’s license model before changing topology or session timeout.

Recovery

Close unused sessions through the supported interface, repair session cleanup, wait for documented lease expiration, or obtain additional entitlement. If the count is wrong after a crash, use the vendor’s license-reconciliation procedure. Queueing or backoff can improve user experience, but software must not bypass or falsify license accounting.

Difference from system quotas

ERROR_NO_QUOTAS_FOR_ACCOUNT concerns absence of an account-specific system quota. ERROR_NO_SYSTEM_RESOURCES reports resource exhaustion. Error 1395 is specifically about the maximum service usage allowed by licensing.

Example

A remote-access service is licensed for fifty concurrent sessions. Mobile clients reconnect after a network outage, but their old leases remain active for ten minutes, so the new attempts receive 1395. Correcting disconnect reconciliation prevents temporary double counting.

References

Looking for a different code? Search another status or error code.