| Previous | Next |
| SL_E_CHPA_UNKNOWN_PROPERTY_NAME | SL_E_CHPA_FAILED_TO_UPDATE_PRODUCTKEY_BINDING |
SL_E_CHPA_UNKNOWN_PROPERTY_ID
What the constant narrows down
HRESULT 0xC004C752 is exposed as SL_E_CHPA_UNKNOWN_PROPERTY_ID by the CHPA activation-server workflow. The code says more than the friendly message: the numeric or opaque property identifier is not defined by the activation-server schema.
The CHPA layer evaluates key type, binding, business-rule inputs and persistent key data. Its insert, update and delete failures need server correlation; repeating slmgr on the client cannot repair a failed server transaction. The code is not interchangeable with a missing property identifier or an unknown textual name.
AllStat records “The activation server reported that property Id specifies unknown property” for this HRESULT. That identifies the official outcome; the additional value is the producing object, evidence set, nearby conditions and safe verification path.
From input to HRESULT
| 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 failure concerns typed metadata attached to a key or license object. |
| Operation | The suffix names the object or transition to inspect before any broad activation reset. |
| State | Its HRESULT severity is failure; later status messages can describe only the resulting state. |
Evidence to keep before remediation
| 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? |
| property name/ID, type, parent record and proposed value hash | For this HRESULT: Can caller identity and elevation be captured before changing state? |
| caller identity and elevation | For this HRESULT: Does the evidence support “capture the property ID and server version and use the matching schema” rather than a missing property identifier or an unknown textual name? |
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.
Work from identity to cause
- Capture property name/ID, type, parent record and proposed value hash specifically for this HRESULT.
- Prove the distinction between the named boundary and a missing property identifier or an unknown textual name 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
0xC004C752, UTC time, caller and the first method or server request that returned it.
REM Evidence context: SL_E_CHPA_UNKNOWN_PROPERTY_ID
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.
Similar messages, different boundaries
| Result | Different condition |
|---|---|
SL_E_CHPA_UNKNOWN_PROPERTY_NAME | the product-key property name is not defined by the activation-server schema |
SL_E_CHPA_NULL_VALUE_FOR_PROPERTY_NAME_OR_ID | a product-key property operation supplies a null name or identifier where the server requires identity |
SL_E_CHPA_FAILED_TO_UPDATE_PRODUCTKEY_BINDING | the server found an existing product-key binding but could not commit its updated state |
Sort related HRESULTs by timestamp and object/request identity. The first code from the producing layer is usually more actionable than a later summary from Settings, deployment software or a wrapper.
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | A stale integration sends an identifier retired from the server schema. |
| Single variable | Change only property identity, declared type and supplied value. |
| Positive control | A schema-defined property accepts a value of the declared type. |
| Different result | If the experiment instead proves “the product-key property name is not defined by the activation-server schema”, 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.
What successful remediation must prove
A supported correction is to capture the property ID and server version and use the matching schema. A representative incident is a stale integration sends an identifier retired from the server schema.
Verification for this HRESULT must repeat the original operation for the same product or request scope. Confirm the intended license status, binding, policy, record or server response persists after any required restart.
Changes that make this code harder to diagnose
- 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.
- avoid launching parallel requests against the same key record; 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.