| Previous | Next |
| SL_E_CHPA_FAILED_TO_INSERT_PRODUCT_KEY_RECORD | SL_REMAPPING_SP_PUB_API_INVALID_LICENSE |
SL_E_CHPA_FAILED_TO_UPDATE_PRODUCT_KEY_RECORD
Where this result is produced
SL_E_CHPA_FAILED_TO_UPDATE_PRODUCT_KEY_RECORD is HRESULT 0xC004C781. It belongs to the CHPA activation-server workflow. Its narrow boundary is: the server cannot commit changes to the primary product-key record.
CHPA results describe the activation service’s business-rule and product-key administration workflow. Several codes concern server records and transactions rather than the end user’s local licensing store. The code is not interchangeable with a property-only update or a client-side key installation failure.
AllStat records “The activation server reported that it failed to update product key record” for this HRESULT. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.
Objects and state transitions
| Stage | Role for this HRESULT |
|---|---|
| CHPA input | The server receives a key-management or activation payload with business-rule inputs. |
| Schema and rule evaluation | Key type, properties, bindings and program rules are validated before the operation can commit. |
| Persistent operation | Insert, update, delete or lookup state is part of the producing boundary for this HRESULT. |
| Server response | The client sees this result after CHPA rejects or cannot persist the requested change. |
A later unlicensed, notification or grace-state message describes a consequence. Preserve the earliest event carrying this HRESULT for the same product object or service request.
What the constant itself tells you
| Signal | Interpretation |
|---|---|
| Family | The CHPA prefix places the result in server business-rule or product-key data processing. |
| Object | The named operation began but could not complete or commit. |
| Operation | Modification of an existing server-side object failed. |
| State | Product/key identity must remain tied to the exact SKU and Activation ID. |
| Scope | The primary persistent product-key object is involved. |
Minimum diagnostic record
| Evidence | Question answered |
|---|---|
| activation request ID and CHPA/server timestamp | For this HRESULT: Which CHPA entity was being inserted, updated, deleted or queried? |
| product-key record identity and key type | For this HRESULT: Did schema validation finish before persistence was attempted? |
| business-rule name or server operation | For this HRESULT: Is another transaction using the same product-key record? |
| record key, insert/update intent and concurrency version | For this HRESULT: Can caller identity and elevation be captured before changing state? |
| caller identity and elevation | For this HRESULT: Does the evidence support “preserve record version, requested changes and transaction correlation for server-side diagnosis” rather than a property-only update or a client-side key installation failure? |
Redact full keys, activation blobs, account tokens, private certificate material and raw hardware identifiers. Partial keys, hashes, IDs and UTC timestamps retain correlation value without publishing secrets.
How to reproduce the same boundary
- Capture record key, insert/update intent and concurrency version specifically for this HRESULT.
- Prove the distinction between the named boundary and a property-only update or a client-side key installation failure before remediation.
- After one supported change, repeat the same operation and compare state, events and response correlation for this HRESULT.
- Bind this result to the exact Application ID, Activation ID, edition and partial key.
- Record
0xC004C781, UTC time, caller and the first method or server request that returned it.
REM Evidence context: SL_E_CHPA_FAILED_TO_UPDATE_PRODUCT_KEY_RECORD
cscript %windir%\system32\slmgr.vbs /dlv
cscript %windir%\system32\slmgr.vbs /atoUse the status output as evidence. Run an activation retry only after the collected state supports the identified prerequisite; blind retries can add quota, throttle or cleanup noise.
Do not merge these conditions
| Result | Different condition |
|---|---|
SL_E_CHPA_FAILED_TO_INSERT_PRODUCT_KEY_RECORD | the server cannot create the primary product-key record |
SL_E_CHPA_PRODUCT_KEY_BEING_USED | another server-side operation or user currently owns the product-key record needed by this request |
SL_E_CHPA_UNKNOWN_PRODUCT_KEY_TYPE | the server does not recognize the product-key type named by the request or stored record |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | Optimistic concurrency or storage failure prevents record maintenance. |
| Single variable | Change only existing object version and the exact old-to-new value transition. |
| Positive control | The same update commits when row version and dependencies match. |
| Different result | If the experiment instead proves “the server cannot create the primary product-key record”, follow that neighboring boundary rather than treating it as this result. |
This controlled comparison is stronger than a broad reset because it changes one prerequisite and leaves product identity, evidence source and observation method stable.
Recovery without broad resets
A supported correction is to preserve record version, requested changes and transaction correlation for server-side diagnosis. A representative incident is optimistic concurrency or storage failure prevents record maintenance.
Changes that make this code harder to diagnose
- avoid launching parallel requests against the same key record; it changes evidence without proving the named boundary.
- avoid editing server XML or properties without preserving the rejected payload; it changes evidence without proving the named boundary.
- avoid treating a failed database operation as a client connectivity problem; it changes evidence without proving the named boundary.
Technical references
- Plan for volume activation clients — official reference for the mechanism surrounding this result.
- Windows activation error help — official reference for the mechanism surrounding it.
- MS-ERREF Windows Error Codes
- Troubleshoot Windows activation error codes
Looking for a different code? Search another status or error code.