| Previous | Next |
| TPM_20_E_MEMORY | TPM_20_E_OBJECT_HANDLES |
TPM_20_E_SESSION_HANDLES
No new session handle can be allocated
TPM_20_E_SESSION_HANDLES wraps TPM_RC_SESSION_HANDLES. The TPM has a bounded set of handles for loaded sessions. Unlike a session-memory warning, this response specifically states that no session handle is available and directs software to flush a session before starting another one.
Sessions are stateful security objects. Discarding a handle without understanding its purpose can invalidate a policy flow, lose an audit digest, or break parameter encryption. Cleanup should target completed or abandoned sessions rather than whichever handle is easiest to remove.
Practical checks
- List loaded session handles and correlate them with owning processes or TBS contexts.
- Close each session after the final authorized command instead of waiting for process termination.
- Keep long multi-command policy sessions on a connection that the resource manager can preserve.
- After abnormal termination, verify that the resource manager has reclaimed the client's virtual resources.
References
Looking for a different code? Search another status or error code.