| Previous | Next |
| ERROR_DS_ADMIN_LIMIT_EXCEEDED | ERROR_DS_COMPARE_TRUE |
ERROR_DS_COMPARE_FALSE
Compare false is a completed protocol result, not a transport failure
ERROR_DS_COMPARE_FALSE is the negative result of an LDAP Compare operation. The server located the target entry, evaluated the asserted attribute value using the attribute’s matching semantics, and determined that no value matched. Applications should handle it as a boolean outcome distinct from errors such as no-such-object, insufficient access, invalid syntax, or connection failure.
Record the target DN, attribute description, matching value representation, and server used. Normalize the assertion according to the attribute syntax rather than applying application-side string rules; case folding, DN normalization, and binary equality can differ by attribute. A false result can also be intentionally nondisclosing when access checks prevent visibility, depending on the operation and directory behavior. For asynchronous calls, correlate the final result with the message ID instead of interpreting successful request submission as a true comparison.
Comparison details
- Target DN and compared attribute.
- Exact assertion bytes or normalized textual value.
- Synchronous or asynchronous API used.
- Distinct handling for false versus LDAP errors.
References
- Microsoft: ldap_compare_s true and false results
- Microsoft: asynchronous LDAP Compare workflow
- IETF RFC 4511: Compare request and response
Looking for a different code? Search another status or error code.