| Previous | Next |
| SL_REMAPPING_SP_PUB_TIMER_EXPIRED | SL_REMAPPING_SP_PUB_TS_FULL |
SL_REMAPPING_SP_PUB_TIMER_NAME_SIZE_TOO_BIG
What the protected licensing code means
SL_REMAPPING_SP_PUB_TIMER_NAME_SIZE_TOO_BIG (0xC004D30D) is emitted by the trusted store and secure-timer layer. It marks a specific point inside the protected state store that keeps namespaced entries, attributes, secure timers, trusted time, hardware binding, rearm state and integrity breadcrumbs: the secure-timer name exceeds the supported encoded length.
This distinction matters because the timer definition is rejected before any deadline is stored. A later “not licensed” state should not replace the first exact HRESULT in logs.
A reproducible troubleshooting path
- Record this result,
0xC004D30D, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: record timer name length, encoding, namespace and caller version.
- Compare the neighboring results below and identify which condition actually applies.
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, record timer name length, encoding, namespace and caller version.
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.
Minimum data for a reliable diagnosis
- 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
Recovery while preserving licensing evidence
Use the compact timer identifier defined by the supported schema.
Representative case: A caller constructs a timer name from an unbounded user-visible description.
Adjacent states in the same subsystem
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TIMER_EXPIRED | Compared with this result, trusted time has passed the secure timer’s protected deadline. |
SL_REMAPPING_SP_PUB_TS_FULL | Compared with this result, the trusted store has no capacity for the requested additional protected state. |
SL_REMAPPING_SP_PUB_TIMER_NOT_FOUND | Compared with it, the named secure timer is absent from the selected namespace. |
Actions that usually destroy useful evidence
- Do not manually delete protected store files before collecting state and event evidence.
- Do not use rearm as a generic repair for unrelated activation or integrity errors.
Technical references
- SoftwareLicensingProduct WMI class — official platform context used to interpret it.
- SoftwareLicensingService WMI class — supported state, API or recovery information relevant to this HRESULT.
- Slmgr.vbs options — reference for evidence collection and post-repair verification.
- Rebuild the Tokens.dat file — technical contract for the subsystem producing it.
Looking for a different code? Search another status or error code.