| Previous | Next |
| SL_E_INVALID_GUID | SL_E_TOKSTO_NO_PROPERTIES |
SL_E_TOKSTO_TOKEN_NOT_FOUND
What this Software Protection result isolates
SL_E_TOKSTO_TOKEN_NOT_FOUND (0xC004E007) is emitted by the logical license and token repository. It marks a specific point inside the repository layer that initializes licensing context, locates token records, parses properties, serializes files and synchronizes concurrent access: the logical store cannot locate the requested license/token identifier.
This result already rules out several broad guesses: the repository is initialized; a specific token is absent. Preserve its operation name, product instance and timestamp so a later retry does not hide the original failure.
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, record requested token ID, product/dependency chain, installed license inventory and store-recreation history.
Store initialization, property parsing, file I/O and synchronization failures require different repairs even when the activation UI shows the same unlicensed state.
A practical way to isolate the cause
- Use read-only inspection first: record requested token ID, product/dependency chain, installed license inventory and store-recreation history.
What to capture before recovery
- file path, access result and Security-SPP event
- target Application ID and Activation ID
- token or license identifier
- property name, type and serialized value
- store initialization and mutex state
Comparison with neighboring results
| Result | Different condition |
|---|---|
SL_E_INVALID_GUID | Compared with this result, a licensing identifier expected to be a GUID is malformed, empty or semantically invalid. |
SL_E_TOKSTO_NO_PROPERTIES | Compared with this result, the token record has no usable property collection where the evaluator requires one. |
SL_E_TOKSTO_NOT_INITIALIZED | Compared with it, a repository operation was requested before token-store initialization completed. |
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.
Recommended handling
Install or restore the signed license package that owns the token and refresh status.
Representative case: An add-on license references a base token removed during incomplete cleanup.
Technical references
- Rebuild the Tokens.dat file — reference for evidence collection and post-repair verification.
- Software Licensing provider — technical contract for the subsystem producing it.
- SoftwareLicensingService WMI class — official platform context used to interpret it.
- SoftwareLicensingProduct WMI class — supported state, API or recovery information relevant to this HRESULT.
Looking for a different code? Search another status or error code.