| Previous | Next |
| WCM_E_INVALIDDATATYPE | WCM_E_READONLYITEM |
WCM_E_NOTPOSITIONED
WCM_E_NOTPOSITIONED is the failure HRESULT 0x80220009 (signed decimal -2145255415, unsigned decimal 2149711881). Its severity bit is 1, facility is 34 (FACILITY_STATE_MANAGEMENT), and the facility-specific code field is 0x0009.
AllStat records the Windows SDK description as “Enumerator is not positioned.”
Meaning in Settings Management Infrastructure
The enumerator has not been advanced to a valid item. The operation reached use of IItemEnumerator::Current before MoveNext succeeds or after the enumerator has passed its last element. The first branch to test is whether Current is called immediately after creating the enumerator; keep that separate from the possibility that Reset is called without the documented following MoveNext.
Point of failure
At this boundary, capture the exact sequence of Reset, MoveNext, and Current calls, then correlate it with the Boolean result returned by each MoveNext. Assign ownership only after checking thread ownership and any concurrent collection modification.
Causes to test independently
- Current is called immediately after creating the enumerator
- Reset is called without the documented following MoveNext
- the loop calls Current after MoveNext reports no next item
- multiple threads use the same non-thread-safe SMI collection/enumerator
Data to collect
- the exact sequence of Reset, MoveNext, and Current calls
- the Boolean result returned by each MoveNext
- thread ownership and any concurrent collection modification
- whether the enumerator has already reached end-of-collection
- the collection-producing method and namespace/item path
Step-by-step diagnosis
- treat a new or reset enumerator as positioned before the first item
- call MoveNext and inspect its result before every Current call
- stop the loop immediately when no next item is reported
- keep the enumerator and its collection on one controlled thread
- create a new enumerator if surrounding collection operations make state ambiguous
Recovery strategy
Retrying Current alone is incorrect. The caller must establish a valid position with MoveNext or obtain a fresh enumerator.
What this value does not mean
This is not WCM_E_STATENODENOTFOUND: no lookup path necessarily failed. The problem is the cursor state of the enumeration object.
Illustrative scenario
A loop processes the final element, calls MoveNext again, receives false, but still calls Current in shared cleanup code. SMI reports that no current element exists.
Implementation guidance
For operational telemetry, retain thread ownership and any concurrent collection modification; also record whether the enumerator has already reached end-of-collection. Preserve a redacted summary of the collection-producing method and namespace/item path; 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: IItemEnumerator.
- Microsoft: IItemEnumerator::MoveNext.
Looking for a different code? Search another status or error code.