| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_RECREATED | SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_ALREADY_EXISTS |
SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_NOT_FOUND
Why this is more specific than an activation failure
This result already rules out several broad guesses: the namespace exists; only the named entry is missing. Preserve its operation name, product instance and timestamp so a later retry does not hide the original failure.
Checks in the useful order
- Record this result,
0xC004D304, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: record namespace, entry key, operation, expected creator and whether the namespace was opened successfully.
- Compare the neighboring results below and identify which condition actually applies.
The diagnostic record that matters
- tamper/recreation/rearm events in chronological order
- namespace, entry key and attribute name
- entry/timer flags including read-only state
- requested and actual data size
- trusted time, timer deadline and hardware-binding 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, record namespace, entry key, operation, expected creator and whether the namespace was opened successfully.
Similar symptoms, different conditions
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_ALREADY_EXISTS | Compared with this result, creation conflicts with an existing entry key in the same trusted-store namespace. |
SL_REMAPPING_SP_PUB_TS_RECREATED | Compared with this result, the trusted store was recreated rather than opened in its previous generation. |
SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_SIZE_TOO_BIG | Compared with it, the entry-key identifier exceeds the trusted store’s supported key-size limit. |
What to repair—and what not to reset
Create or restore the entry through its owning supported component rather than inserting raw store data.
Representative case: A policy query expects an entry that was never created after store recreation.
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 — technical contract for the subsystem producing it.
- SoftwareLicensingService WMI class — official platform context used to interpret it.
- Slmgr.vbs options — supported state, API or recovery information relevant to this HRESULT.
- Rebuild the Tokens.dat file — reference for evidence collection and post-repair verification.
Looking for a different code? Search another status or error code.