| Previous | Next |
| SL_E_NON_GENUINE_STATUS_LAST | SL_E_CHPA_NULL_VALUE_FOR_PROPERTY_NAME_OR_ID |
SL_E_CHPA_BUSINESS_RULE_INPUT_NOT_FOUND
Where this result is produced
SL_E_CHPA_BUSINESS_RULE_INPUT_NOT_FOUND is HRESULT 0xC004C700. It belongs to the CHPA activation-server workflow. Its narrow boundary is: a selected activation business rule requires an input that the request or service context did not provide.
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 an unknown property name, where a field is present but not recognized.
AllStat records “The activation server reported that business rule cound not find required input” 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 | A lookup completed without locating the named 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? |
| caller identity and elevation | For this HRESULT: Can whether a clean reboot reproduces the result without modifying state be captured before changing state? |
| whether a clean reboot reproduces the result without modifying state | For this HRESULT: Does the evidence support “identify the rule and missing input and correct the request producer or service configuration” rather than an unknown property name, where a field is present but not recognized? |
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
- Prove the distinction between the named boundary and an unknown property name, where a field is present but not recognized 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
0xC004C700, UTC time, caller and the first method or server request that returned it. - Capture whether a clean reboot reproduces the result without modifying state specifically for this HRESULT.
REM Evidence context: SL_E_CHPA_BUSINESS_RULE_INPUT_NOT_FOUND
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_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 |
A focused reproduction for this exact result
| Control | Design |
|---|---|
| Failing fixture | A rule expects product-channel data omitted by the calling workflow. |
| Single variable | Change only presence of the exact required object in the correct product and storage scope. |
| Positive control | Restoring only that official dependency removes the code without a broad store reset. |
| 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 identify the rule and missing input and correct the request producer or service configuration. A representative incident is a rule expects product-channel data omitted by the calling workflow.
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
- Windows activation error help — official reference for the mechanism surrounding this result.
- MS-ERREF Windows Error Codes — official reference for the mechanism surrounding it.
- Troubleshoot Windows activation error codes
- Slmgr.vbs options
Looking for a different code? Search another status or error code.