| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_NOT_FOUND | SL_REMAPPING_SP_PUB_TS_NAMESPACE_NOT_FOUND |
SL_REMAPPING_SP_PUB_TS_ACCESS_DENIED
Why this is more specific than an activation failure
Keep the symbolic result SL_REMAPPING_SP_PUB_TS_ACCESS_DENIED together with HRESULT 0xC004D314. The producer is the trusted store and secure-timer layer; at the protected state store that keeps namespaced entries, attributes, secure timers, trusted time, hardware binding, rearm state and integrity breadcrumbs, Windows determined that the caller is not authorized for the requested trusted-store namespace or operation.
This distinction matters because this is authorization, not missing data or an I/O ACL error on Tokens.dat alone. A later “not licensed” state should not replace the first exact HRESULT in logs.
State to compare on both sides of the failure
- requested and actual data size
- trusted time, timer deadline and hardware-binding state
- tamper/recreation/rearm events in chronological order
- namespace, entry key and attribute name
- entry/timer flags including read-only state
Where it sits in the licensing pipeline
Trusted-store results concern protected persistent state; deleting the store can erase the evidence that distinguishes missing data, capacity, access, binding and integrity failures. To verify this, capture caller identity, service context, requested access, namespace ACL/policy and whether elevation changed the result.
A positive trusted-time or rearm/recreation result must be interpreted by HRESULT severity and the subsequent license state, not by treating every nonzero value as a fatal error.
Testing the failing stage
- Identify the caller and operation instance that produced
0xC004D314. - Collect the code-specific evidence: capture caller identity, service context, requested access, namespace ACL/policy and whether elevation changed the result.
Recovery while preserving licensing evidence
Run the supported operation under the required service/security context and repair only documented permission changes.
Representative case: A user process calls a protected store mutation reserved for the Software Protection service.
Related codes with different remedies
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_NOT_FOUND | Compared with this result, the requested attribute is not present on the selected trusted-store entry. |
SL_REMAPPING_SP_PUB_TS_NAMESPACE_NOT_FOUND | Compared with this result, the requested trusted-store namespace does not exist. |
SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_READ_ONLY | Compared with this result, an update targets a protected entry attribute marked read-only. |
Actions that usually destroy useful evidence
- Do not use rearm as a generic repair for unrelated activation or integrity errors.
- Do not manually delete protected store files before collecting state and event evidence.
Technical references
- SoftwareLicensingProduct WMI class — 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.
- Rebuild the Tokens.dat file — official platform context used to interpret it.
Looking for a different code? Search another status or error code.