Site icon EfmSoft

What does HRESULT 0xC004C751 (SL_E_CHPA_UNKNOWN_PROPERTY_NAME) mean?

 
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.

Windows reports “The activation server reported that property name specifies unknown property”.

Objects and state transitions

StageRole
CHPA inputThe server receives a key-management or activation payload with business-rule inputs.
Schema and rule evaluationKey type, properties, bindings and program rules are validated before the operation can commit.
Persistent operationInsert, update, delete or lookup state is part of the producing operation.
Server responseThe client sees this result after CHPA rejects or cannot persist the requested change.

Minimum diagnostic record

EvidenceQuestion answered
activation request ID and CHPA/server timestampWhich CHPA entity was being inserted, updated, deleted or queried?
product-key record identity and key typeDid schema validation finish before persistence was attempted?
business-rule name or server operationIs another transaction using the same product-key record?
property name/ID, type, parent record and proposed value hashCan caller identity and elevation be captured before changing state?
Code-specific distinctionDoes 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?

How to reproduce the same condition

  1. Record 0xC004C751, UTC time, caller and the first method or server request that returned it.
  2. Capture business-rule name or server operation.
  3. Before remediation, confirm that the failure is not instead the neighboring condition: a known property with an invalid value.
REM Evidence context: SL_E_CHPA_UNKNOWN_PROPERTY_NAME
cscript %windir%\system32\slmgr.vbs /dlv
cscript %windir%\system32\slmgr.vbs /ato

Do not merge these conditions

ResultDifferent condition
SL_E_CHPA_NULL_VALUE_FOR_PROPERTY_NAME_OR_IDa product-key property operation supplies a null name or identifier where the server requires identity
SL_E_CHPA_UNKNOWN_PROPERTY_IDthe numeric or opaque property identifier is not defined by the activation-server schema
SL_E_CHPA_FAILED_TO_UPDATE_PRODUCTKEY_BINDINGthe server found an existing product-key binding but could not commit its updated state

A focused reproduction for this exact result

ControlDesign
Failing fixtureA newer client sends a property name not understood by the server.
Single variableChange only property identity, declared type and supplied value.
Positive controlA schema-defined property accepts a value of the declared type.
Different resultIf the experiment instead proves “a product-key property operation supplies a null name or identifier where the server requires identity”, diagnose that condition separately rather than treating it as this HRESULT.

Recovery without broad resets

To correct this using supported mechanisms, compare the property name and case with the supported schema and deployment version.

Changes that make this code harder to diagnose

  • Avoid launching parallel requests against the same key record.
  • Avoid editing server XML or properties without preserving the rejected payload.
  • Avoid treating a failed database operation as a client connectivity problem.

Technical references


Looking for a different code? Search another status or error code.

Exit mobile version