| Previous | Next |
| VDS_E_INVALID_MEMBER_COUNT | VDS_E_INVALID_MEMBER_ORDER |
VDS_E_INVALID_PLEX_ORDER
This status is an ordering validation failure in a structured volume description. VDS identifies plexes by GUID in its object model, but internal or provider-facing topology input can also validate ordered plex positions. The published error requires plex indexes to begin at zero and increase monotonically. A set such as 0, 2 or 1, 0 is therefore structurally invalid even if every referenced disk and plex object exists.
Why this state matters
Treat this as a serialization or array-construction problem before investigating media. A common failure pattern is preserving indexes from a filtered list after one plex was removed, or sorting records by disk path instead of plex position. Reconstruct the ordered model from the volume and plex relationships and keep GUID identity separate from zero-based position.
Diagnostic focus
- Dump the plex index sequence exactly as passed to the provider before any sorting or normalization.
- Verify the first plex position is zero and every following position increments without gaps.
- Keep persistent plex GUIDs separate from temporary array indexes used to encode the request.
- If a prior plex was removed, rebuild indexes from current topology rather than reusing historical positions.
Technical references
Volume Plex Object · VDS_VOLUME_PLEX_PROP · MS-VDS IVdsVolume::QueryPlexes · MS-VDS storage object relationships · MS-VDS error codes
Looking for a different code? Search another status or error code.