| Previous | Next |
| ERROR_BAD_LOGON_SESSION_STATE | ERROR_INVALID_LOGON_TYPE |
ERROR_LOGON_SESSION_COLLISION
Two logon-session paths attempted to use the same local logon identifier
The AuthenticationId associated with an access token is an LUID identifying the logon session represented by that token. Multiple tokens can legitimately refer to one session, but two independent session-creation paths must not accidentally claim the same ID. This error points to that identity collision and should not be treated as a duplicate user logon; the same user can have many distinct logon sessions.
Compare the colliding LUID with active logon-session data and token statistics. In custom LSA/authentication-package code, audit LUID allocation, retry behavior, and restoration of partially created state. Do not derive AuthenticationId from a process ID, user SID, timestamp, or persistent sequence. Also distinguish this from ERROR_LOGON_SESSION_EXISTS at the API boundary: both imply identifier reuse, but logs and the precise creation path are needed to determine which session operation reported the conflict.
What to inspect
- Capture the colliding LUID and enumerate the session currently using it.
- Audit any custom generation or persistence of AuthenticationId values.
- Remember that multiple sessions for one user are valid; the conflict is the session ID itself.
References
Looking for a different code? Search another status or error code.