| Previous | Next |
| SL_E_CHPA_NULL_VALUE_FOR_PROPERTY_NAME_OR_ID | SL_E_CHPA_UNKNOWN_PROPERTY_ID |
SL_E_CHPA_UNKNOWN_PROPERTY_NAME
Where this result is produced
SL_E_CHPA_UNKNOWN_PROPERTY_NAME is HRESULT 0xC004C751. It belongs to the CHPA activation-server workflow. Its narrow boundary is: the product-key property name is not defined by the activation-server schema.
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 known property with an invalid value.
AllStat records “The activation server reported that property name 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.
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 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. |
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? |
| 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 “compare the property name and case with the supported schema and deployment version” rather than a known property with an invalid value? |
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
- Record
0xC004C751, UTC time, caller and the first method or server request that returned it. - Capture business-rule name or server operation specifically for this HRESULT.
- Prove the distinction between the named boundary and a known property with an invalid value 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.
REM Evidence context: SL_E_CHPA_UNKNOWN_PROPERTY_NAME
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_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_UNKNOWN_PROPERTY_ID | the numeric or opaque property identifier is not defined by the activation-server schema |
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 newer client sends a property name not understood by the server. |
| 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 “a product-key property operation supplies a null name or identifier where the server requires identity”, 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 compare the property name and case with the supported schema and deployment version. A representative incident is a newer client sends a property name not understood by the server.
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 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
- Slmgr.vbs options — official reference for the mechanism surrounding this result.
- Plan for volume activation clients — official reference for the mechanism surrounding it.
- Windows activation error help
- MS-ERREF Windows Error Codes
Looking for a different code? Search another status or error code.