| Previous | Next |
| VDS_E_CORRUPT_NOTIFICATION_INFO | VDS_E_DISK_NOT_FOUND_IN_PACK |
VDS_E_INVALID_PLEX_GUID
Plexes are first-class VDS objects with stable object IDs exposed through VDS_VOLUME_PLEX_PROP.id. The published VDS error states that GUID_NULL is not a valid plex GUID for this path. Methods such as BreakPlex and RemovePlex require the ID of an actual plex associated with the volume, and MS-VDS describes obtaining that ID from plex properties after enumeration.
Why this state matters
A zeroed or stale GUID should be treated as an object-resolution failure in the client. Do not substitute the volume ID or disk ID because the storage relationships are separate. Enumerate the current plexes, retrieve their properties, and validate the selected GUID against the current volume immediately before the topology-changing call.
Diagnostic focus
- Reject
GUID_NULLbefore entering the VDS method and log the caller path that produced it. - Obtain plex IDs from
QueryPlexesplusIVdsVolumePlex::GetProperties. - Confirm the selected plex still belongs to the intended volume after any refresh or mirror operation.
- Keep volume, plex, and disk GUID fields strongly separated in request structures and diagnostic output.
Technical references
VDS_VOLUME_PLEX_PROP · MS-VDS IVdsVolume::QueryPlexes · IVdsVolumePlex · IVdsVolume::RemovePlex · MS-VDS storage object relationships
Looking for a different code? Search another status or error code.
