| Previous | Next |
| VDS_E_SECURITY_INCOMPLETELY_SET | VDS_E_INITIATOR_SPECIFIC_NOT_SUPPORTED |
VDS_E_TARGET_SPECIFIC_NOT_SUPPORTED
This HRESULT is a capability boundary in the initiator secret model. IVdsServiceIscsi::SetInitiatorSharedSecret accepts a target ID so an initiator implementation can associate different CHAP secrets with different targets, but Microsoft documents that target-specific support cannot be queried in advance.
Why this state matters
The documented fallback is precise: if this status is returned, call the method again with GUID_NULL for the target ID to set the initiator default secret. Microsoft also states that its iSCSI Software Initiator does not support target-specific initiator secrets. That is different from target-side CHAP configuration and from remembering a target secret for one-way CHAP.
Diagnostic focus
- Determine whether the application is setting the initiator secret or the target secret; the two directions of CHAP configuration are separate.
- On this HRESULT, use the documented
GUID_NULLfallback only if a machine-wide/default initiator secret is acceptable for the deployment. - Do not log the secret bytes while diagnosing the capability failure; record only target ID, operation, and status.
- Review mutual-CHAP assumptions because replacing a target-specific secret with a default changes which targets may share initiator credentials.
Technical references
IVdsServiceIscsi::SetInitiatorSharedSecret · VDS_ISCSI_SHARED_SECRET · IVdsServiceIscsi::RememberTargetSharedSecret · RFC 1994: CHAP · RFC 7143: iSCSI
Looking for a different code? Search another status or error code.
