| Previous | Next |
| VDS_S_ALREADY_EXISTS | VDS_S_ISCSI_SESSION_NOT_FOUND_PERSISTENT_LOGIN_REMOVED |
VDS_S_PROPERTIES_INCOMPLETE
This success-severity status means the object remains enumerable even though its property set is partial. VDS object structures contain different identifiers, names, status, health, flags, and provider-specific data. A management application that ignores the HRESULT and assumes every field is authoritative can turn an incomplete property read into a false state transition or invalid follow-up request.
Why this state matters
The right handling is field-aware. Preserve which object and provider produced the warning, keep unknown or unavailable properties distinct from valid zero values, and avoid using missing fields as selection keys. Since VDS caches object properties and normally updates them on notifications, a later refresh and requery can be reasonable when the cache appears stale, but repeated incompleteness may indicate provider or path problems.
Diagnostic focus
- Keep the warning HRESULT together with the returned property structure instead of normalizing it to
S_OK. - Mark unavailable fields as unknown; do not substitute zero GUIDs, empty names, or default statuses as if they were returned values.
- Identify whether the incomplete object is a disk, volume, LUN, path, or provider before choosing follow-up queries.
- Requery after a controlled refresh if the object is expected to stabilize; investigate the provider if the same fields remain unavailable.
Technical references
IVdsService · VDS_NOTIFICATION · IVdsService::Refresh · VDS common return codes · MS-VDS error codes
Looking for a different code? Search another status or error code.