| Previous | Next |
| VDS_E_TARGET_SPECIFIC_NOT_SUPPORTED | VDS_E_ISCSI_LOGIN_FAILED |
VDS_E_INITIATOR_SPECIFIC_NOT_SUPPORTED
This status is returned on the target side of the VDS CHAP model. IVdsIscsiTarget::SetSharedSecret can associate a target secret with a specific initiator name, using that iSCSI name as the CHAP name. Some targets do not implement per-initiator secrets and only support a default target secret.
Why this state matters
Microsoft documents that passing a null initiator name applies the change to the default secret for all initiators. That fallback has security and deployment implications: it changes the credential scope. The failure should therefore not be “fixed” by silently clearing the initiator name unless the storage policy explicitly permits a shared default.
Diagnostic focus
- Confirm that the provider is configuring the target-side secret and identify the exact initiator iSCSI name supplied to the call.
- Check the target or array capability for per-initiator CHAP secrets rather than assuming all iSCSI targets support them.
- Use the default-secret form only when the same target credential is intentionally allowed for multiple initiators.
- Keep target-side secret persistence on the subsystem separate from VDS local state; Microsoft says security secrets should not be persisted locally by VDS or hardware providers.
Technical references
IVdsIscsiTarget::SetSharedSecret · VDS_ISCSI_SHARED_SECRET · VDS_ISCSI_TARGET_PROP · RFC 1994: CHAP · RFC 7143: iSCSI
Looking for a different code? Search another status or error code.