| Previous | Next |
| WCM_E_NOTSUPPORTEDFUNCTION | WCM_E_INVALIDATTRIBUTECOMBINATION |
WCM_E_VALUETOOBIG
WCM_E_VALUETOOBIG is the failure HRESULT 0x80220026 (signed decimal -2145255386, unsigned decimal 2149711910). Its severity bit is 1, facility is 34 (FACILITY_STATE_MANAGEMENT), and the facility-specific code field is 0x0026.
AllStat records the Windows SDK description as “A value is too big to process”
Documented meaning
The setting payload is too large for SMI processing. The operation reached parsing, conversion, storage, or handler transfer of a value whose size exceeds the applicable limit. The first branch to test is whether a string, binary blob, or list serialization is unexpectedly large; keep that separate from the possibility that generated content repeats data because of a template loop.
Operation phase
At this boundary, capture logical value length and serialized byte count, then correlate it with declared type and destination setting path. Assign ownership only after checking source artifact and generator inputs.
Root-cause branches
- a string, binary blob, or list serialization is unexpectedly large
- generated content repeats data because of a template loop
- the wrong file or payload was assigned to a scalar setting
- encoding expansion makes the serialized representation much larger than expected
Diagnostic record
- logical value length and serialized byte count
- declared type and destination setting path
- source artifact and generator inputs
- size before and after encoding/escaping
- whether the component documents a smaller domain-specific maximum
Correction workflow
- confirm that the correct artifact is being assigned
- remove duplication or accidental embedding
- use a supported external resource/reference when the schema provides one
- measure the final serialized representation
- avoid splitting one logical value unless the setting contract explicitly supports multiple elements
Retry policy
Retry only after reducing or correcting the value. The public HRESULT does not publish a universal byte threshold, so do not hard-code one from a single observation.
Nearby HRESULT distinctions
WCM_E_INVALIDVALUE can reject content for semantic reasons at any size. VALUETOOBIG identifies processing size as the limiting dimension.
Concrete example
A generator accidentally places an entire XML document into a setting intended for a short identifier. The payload reaches SMI but exceeds what the setting pipeline can process.
Operational logging
For operational telemetry, retain source artifact and generator inputs; also record size before and after encoding/escaping. Preserve a redacted summary of whether the component documents a smaller domain-specific maximum; use a cryptographic hash when that evidence is a file, stream, or generated artifact.
Official Microsoft references.
- Microsoft: SMI error and success constants.
- Microsoft: Settings Management Infrastructure API.
- Microsoft: SMI interfaces.
- Microsoft: WcmDataType.
- Microsoft: ISettingsItem::GetDataType.
Looking for a different code? Search another status or error code.