| Previous | Next |
| WCM_E_INVALIDVALUEFORMAT | WCM_E_INVALIDDATATYPE |
WCM_E_TYPENOTSPECIFIED
WCM_E_TYPENOTSPECIFIED is the failure HRESULT 0x80220007 (signed decimal -2145255417, unsigned decimal 2149711879). Its severity bit is 1, facility is 34 (FACILITY_STATE_MANAGEMENT), and the facility-specific code field is 0x0007.
AllStat records the Windows SDK description as “XSD type is missing in metadata.”
Interpretation without overreach
The manifest metadata does not declare an XSD type. The operation reached manifest compilation or metadata validation before values can be converted and exposed through ISettingsItem. The first branch to test is whether a setting declaration lacks its required type attribute; keep that separate from the possibility that schema generation dropped a type during transformation or merge.
SMI object or metadata boundary
At this boundary, capture source manifest and exact line reported by ISettingsResult, then correlate it with the setting declaration and any referenced simpleType or complexType. Assign ownership only after checking compiler version and target-image schema package.
Common origins
- a setting declaration lacks its required type attribute
- schema generation dropped a type during transformation or merge
- an extension element was copied without the metadata that defines its value model
- a malformed import/reference prevents the compiler from seeing the type declaration
Useful artifacts
- source manifest and exact line reported by ISettingsResult
- the setting declaration and any referenced simpleType or complexType
- compiler version and target-image schema package
- preprocessed/merged XML actually handed to SMI
- whether sibling settings generated by the same template include proper types
How to isolate the defect
- restore the explicit XSD type in the authoritative source
- resolve schema references before compiling the manifest
- avoid inferring type from a default value or current registry representation
- compile the smallest containing metadata unit to confirm the missing declaration
- regenerate dependent artifacts after correcting the source manifest
When another attempt is justified
This failure is deterministic. Retry only with corrected metadata; changing the setting value cannot supply a missing type definition.
Related result codes
WCM_E_INVALIDDATATYPE reports disagreement with a known type. TYPENOTSPECIFIED means SMI has no declared type against which to interpret the value.
Example from an offline image
A manifest transformation preserves a setting name and default but drops the type attribute. Compilation stops before the default can be converted.
Developer and administrator notes
For operational telemetry, retain compiler version and target-image schema package; also record preprocessed/merged XML actually handed to SMI. Preserve a redacted summary of whether sibling settings generated by the same template include proper types; 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: ISettingsContext::Deserialize.
- Microsoft: ISettingsResult::GetLine.
Looking for a different code? Search another status or error code.