| Previous | Next |
| SL_E_SFS_INVALID_FILE_POSITION | SL_E_SFS_INVALID_FS_HEADER |
SL_E_SFS_NO_ACTIVE_TRANSACTION
Where the failure occurs in Software Protection Platform
The useful meaning of SL_E_SFS_NO_ACTIVE_TRANSACTION, value 0x8004E10C, is not simply “activation failed.” It comes from the serialized Token Store file format, where the low-level reader/writer that validates the Token Store container, descriptor table, token records and transaction state before licenses can be evaluated. The condition to investigate is a commit, rollback or mutation was requested without an active store transaction.
For triage, this belongs to the serialized Token Store file format. The file can be healthy; the error is about transaction lifetime. Product-key changes or network tests are useful only when the evidence points back to those layers.
A reproducible troubleshooting path
- Record this result,
0x8004E10C, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: record the exact API sequence, transaction identifier, prior failure and whether service restart invalidated the context.
- Compare the neighboring results below and identify which condition actually applies.
Where it sits in the licensing pipeline
A structural Token Store error occurs before an individual product key can be accepted or rejected. To verify this, record the exact API sequence, transaction identifier, prior failure and whether service restart invalidated the context.
Minimum data for a reliable diagnosis
- descriptor table and token offsets
- token name, extension, declared size and hash
- file-system result and Software Protection event
- Tokens.dat or the applicable licensing-store file
- store header and format version
Targeted fix
Restart the operation from transaction begin and ensure the same live context performs mutation and commit.
Representative case: A retry path calls commit after an earlier exception already rolled the transaction back.
Adjacent states in the same subsystem
| Result | Different condition |
|---|---|
SL_E_SFS_INVALID_FILE_POSITION | Compared with this result, a store operation attempted to seek or access a position outside the valid container layout. |
SL_E_SFS_INVALID_FS_HEADER | Compared with this result, the Token Store container header fails structural validation. |
SL_E_SFS_FILE_WRITE_ERROR | Compared with it, the store writer could not persist a token or metadata update. |
Actions that usually destroy useful evidence
- Do not edit or copy individual records inside the signed store.
- Do not assume a product-key change can repair a malformed container.
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.
- Slmgr.vbs options — technical contract for the subsystem producing it.
Looking for a different code? Search another status or error code.