| Previous | Next |
| ERROR_NO_MATCH | ERROR_POINT_NOT_FOUND |
ERROR_SET_NOT_FOUND
The requested property set does not exist on the object.
ERROR_SET_NOT_FOUND has decimal value 1170 (0x492). It distinguishes an absent group of related properties or controls from a missing object. The object can be valid and accessible while a particular optional set is unsupported, uninitialized, removed, or unavailable in the current operating state.
Where this distinction matters
- camera, media, or device-control APIs query an optional control family
- a property-store layer requests a set identified by a GUID or schema identifier
- hardware exposes different controls before and after streaming starts
- a driver version omits a property set supported by another model
- migration or configuration code expects a set created only by newer software
Microsoft camera examples use HRESULT_FROM_WIN32(ERROR_SET_NOT_FOUND) when a requested legacy control is not available. This is a useful model: absence can be a capability result rather than corruption.
Evidence to record
- object identity and the property-set or control-set identifier
- API method, operation type, and whether the result was plain Win32 or HRESULT-wrapped
- device model, driver version, firmware, and current operating state
- enumerated property sets or controls available at the same time
- whether the set is mandatory, optional, or version-dependent in the product contract
Diagnostic steps
- confirm that the object itself was opened successfully
- enumerate supported sets when the API provides capability discovery
- verify the set identifier and schema version byte for byte
- check whether initialization or a state transition exposes the set later
- compare behavior with the vendor's documented driver and firmware combination
Correct application behavior
For an optional control, disable the related feature or use a documented fallback. For a mandatory set, report a clear incompatibility and stop before applying partial configuration. Creating an empty set locally is not a valid repair unless the owning API explicitly defines a creation operation.
Caching support forever can be wrong on hot-plug devices or stateful media components. Bind capability data to the device instance and relevant state generation, then refresh it after reinitialization or driver replacement.
Developer guidance
Public interfaces should distinguish “object missing,” “set missing,” “property missing,” and “value invalid.” This lets callers implement feature detection without interpreting all failures as fatal. Unit tests should cover devices with the complete set, no set, and a set whose individual properties differ by version.
Related codes
ERROR_NOT_FOUND is a generic missing-element result. ERROR_NO_MATCH indicates that matching criteria selected no candidate. ERROR_NOT_SUPPORTED can mean the entire operation is unavailable. Error 1170 specifically says that the requested property-set grouping is absent from an otherwise identified object.
Example
A camera application loads saved defaults and requests a legacy exposure-control set. A newer device exposes only a different control model, so the call returns an HRESULT derived from 1170. The application records the missing set identifier, disables the legacy slider, and continues with supported controls instead of declaring the camera broken.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: IMFCameraConfigurationManager
- Microsoft: Frame Server custom media source
Looking for a different code? Search another status or error code.