| Previous | Next |
| E_ADS_PROPERTY_NOT_SET | E_ADS_PROPERTY_INVALID |
E_ADS_PROPERTY_NOT_SUPPORTED
E_ADS_PROPERTY_NOT_SUPPORTED points to a mismatch between the property requested by the application and the capabilities of the bound ADSI provider/object. It differs from a supported attribute that is merely unset and from a cache miss for a valid attribute.
Verify the provider and schema class that define the property surface
- Record the bound object
ClassandSchemavalues together with the provider prefix in the ADsPath. - Use the LDAP display name defined by the directory schema rather than a friendly UI label or a property name from another ADSI provider.
- For provider-specific objects, compare the documented property set for that provider before retrying the same
GetorPut.
ADSI spans multiple namespaces, and its common interfaces do not imply that every provider or schema class implements every property. A property that works through the LDAP provider on an Active Directory user might not exist on a WinNT-provider object or another class. Diagnose the actual binding target first. Repeated cache refreshes will not add an unsupported property; the correction is to request the right attribute or use the right provider/object interface.
Generic ADSI errors · Binding model · ADSI attribute syntax
Looking for a different code? Search another status or error code.