| Previous | Next |
| SL_E_TOKSTO_CANT_CREATE_MUTEX | SL_E_TOKSTO_NO_TOKEN_DATA |
SL_E_TOKSTO_CANT_ACQUIRE_MUTEX
What the security processor has established
The useful meaning of SL_E_TOKSTO_CANT_ACQUIRE_MUTEX, value 0xC004E013, is not simply “activation failed.” It comes from the logical license and token repository, where the repository layer that initializes licensing context, locates token records, parses properties, serializes files and synchronizes concurrent access. The condition to investigate is the repository’s synchronization object exists but cannot be acquired for the operation.
This distinction matters because the failure is contention or mutex state, not creation. A later “not licensed” state should not replace the first exact HRESULT in logs.
Checks in the useful order
- Identify the caller and operation instance that produced
0xC004E013. - Collect the code-specific evidence: capture owner/waiter processes, timeout, abandoned state and concurrent licensing operations.
Where it sits in the licensing pipeline
The logical token repository sits below product activation: a missing, unreadable or inconsistent token can prevent evaluation before any server request occurs. To verify this, capture owner/waiter processes, timeout, abandoned state and concurrent licensing operations.
Store initialization, property parsing, file I/O and synchronization failures require different repairs even when the activation UI shows the same unlicensed state.
The diagnostic record that matters
- store initialization and mutex state
- file path, access result and Security-SPP event
- target Application ID and Activation ID
- token or license identifier
- property name, type and serialized value
Targeted fix
Allow the owning operation to finish or restart the supported service cleanly after diagnosing a deadlock.
Representative case: A hung activation transaction holds the token-store mutex indefinitely.
Adjacent states in the same subsystem
| Result | Different condition |
|---|---|
SL_E_TOKSTO_CANT_CREATE_MUTEX | Compared with this result, the repository cannot create its synchronization object. |
SL_E_TOKSTO_NO_TOKEN_DATA | Compared with this result, a token object lacks the serialized data required for evaluation or persistence. |
SL_E_TOKSTO_INVALID_FILE | Compared with this result, a license-store file is readable but fails identity, structure or integrity validation. |
Actions that usually destroy useful evidence
- Do not repeatedly installing keys while repository operations are failing.
- Do not rename or replacing store files without preserving the original and following the supported rebuild sequence.
Technical references
- Rebuild the Tokens.dat file — official platform context used to interpret it.
- Software Licensing provider — supported state, API or recovery information relevant to this HRESULT.
- SoftwareLicensingService WMI class — reference for evidence collection and post-repair verification.
- SoftwareLicensingProduct WMI class — technical contract for the subsystem producing it.
Looking for a different code? Search another status or error code.