| Previous | Next |
| SL_E_CHPA_BUSINESS_RULE_INPUT_NOT_FOUND | SL_E_CHPA_UNKNOWN_PROPERTY_NAME |
SL_E_CHPA_NULL_VALUE_FOR_PROPERTY_NAME_OR_ID
How to interpret this HRESULT
When SL_E_CHPA_NULL_VALUE_FOR_PROPERTY_NAME_OR_ID returns 0xC004C750, diagnosis has reached the CHPA activation-server workflow. Specifically, a product-key property operation supplies a null name or identifier where the server requires identity.
This result comes from activation-service processing after request construction. The useful distinction is whether a business rule, schema field, key record or persistence operation failed. The code is not interchangeable with an unknown but non-null property name or ID.
Windows reports “The activation server reported that NULL value specified for business property name and Id”.
Relevant processing model
| Stage | Role |
|---|---|
| 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 operation. |
| Server response | The client sees this result after CHPA rejects or cannot persist the requested change. |
What to collect first
| Evidence | Question answered |
|---|---|
| activation request ID and CHPA/server timestamp | Which CHPA entity was being inserted, updated, deleted or queried? |
| product-key record identity and key type | Did schema validation finish before persistence was attempted? |
| business-rule name or server operation | Is another transaction using the same product-key record? |
| property name/ID, type, parent record and proposed value hash | Can caller identity and elevation be captured before changing state? |
| Code-specific distinction | Does the evidence support “fix the property payload before resubmitting; do not substitute arbitrary identifiers” rather than an unknown but non-null property name or ID? |
Checks in a useful order
- Record
0xC004C750, UTC time, caller and the first method or server request that returned it. - Capture business-rule name or server operation.
- Before remediation, confirm that the failure is not instead the neighboring condition: an unknown but non-null property name or ID.
REM Evidence context: SL_E_CHPA_NULL_VALUE_FOR_PROPERTY_NAME_OR_ID
cscript %windir%\system32\slmgr.vbs /dlv
cscript %windir%\system32\slmgr.vbs /atoKeep neighboring codes separate
| 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_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 |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | An integration serializes an empty property identity during key maintenance. |
| 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”, diagnose that condition separately rather than treating it as this HRESULT. |
Safe recovery direction
To correct this using supported mechanisms, fix the property payload before resubmitting; do not substitute arbitrary identifiers.
Changes that make this code harder to diagnose
- Avoid treating a failed database operation as a client connectivity problem.
- Avoid launching parallel requests against the same key record.
- Avoid editing server XML or properties without preserving the rejected payload.
Technical references
Looking for a different code? Search another status or error code.