Windows error 1363 (ERROR_LOGON_SESSION

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: a request attempted to create an LSA logon session using an identifier already assigned to a session.

Previous	Next
ERROR_NOT_LOGON_PROCESS	ERROR_NO_SUCH_PACKAGE

ERROR_LOGON_SESSION_EXISTS

The requested logon-session identifier is already active

An LSA logon session is identified by a locally unique logon ID. Authentication packages create sessions during successful authentication and tokens can refer to the same session through their AuthenticationId. This status indicates a create path encountered an identifier that is already in use, rather than a request to query an existing session.

For custom authentication packages, trace the CreateLogonSession/cleanup sequence and the LUID source. Ensure failure paths delete only sessions they actually created and do not reuse a caller-supplied AuthenticationId. If the code allocates LUIDs itself, use the system allocator rather than a counter persisted across reboot. Compare the duplicate identifier with active session enumeration and token statistics. A collision can also expose a lifecycle bug where a package retries creation after the original request actually succeeded.

What to inspect

Record the requested logon LUID and check whether an active session already owns it.
Audit authentication-package create/delete cleanup and retry paths.
Use system LUID allocation rather than a persistent or caller-derived counter.

References

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