Category: LDAP Schema
Access and audit logs concern client operations rather than the server and tools, and so are not listed here. Instead, this document covers severe and fatal error messages for the server and its tools, such as those logged in logs/errors, and logs/replication.
- ID: 26
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was a comma or semicolon.
- ID: 28
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not allowed in an attribute name.
- ID: 30
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the hyphen character is not allowed as the first character of an attribute name.
- ID: 33
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because it contained an RDN containing an empty attribute name.
- ID: 34
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the parsed attribute name %s included a period but that name did not appear to be a valid OID.
- ID: 35
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was part of the attribute name '%s'.
- ID: 36
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the next non-space character after attribute name "%s" should have been an equal sign but instead was '%c'.
- ID: 37
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not valid.
- ID: 38
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with an octothorpe (#) but was not followed by a positive multiple of two hexadecimal digits.
- ID: 39
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with an octothorpe (#) but contained a character %c that was not a valid hexadecimal digit.
- ID: 40
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because an unexpected failure occurred while attempting to parse an attribute value from one of the RDN components: "%s".
- ID: 41
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because one of the RDN components included a quoted value that did not have a corresponding closing quotation mark.
- ID: 42
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because one of the RDN components included a value with an escaped hexadecimal digit that was not followed by a second hexadecimal digit.
- ID: 257
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid RFC 3672 subtree specification.
- ID: 269
Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid subtree specification.
- ID: 341
Severity: ERROR
Message: There should be no warnings on the schema, but instead got %d warnings: %s.
- ID: 344
Severity: ERROR
Message: Unable to parse the OID from the provided definition of objectclass: '%s'.
- ID: 345
Severity: ERROR
Message: Unable to parse the OID from the provided definition of attribute type: '%s'.
- ID: 346
Severity: ERROR
Message: Unable to parse the OID from the provided definition of ldap syntax: '%s'.
- ID: 347
Severity: ERROR
Message: Unable to parse the OID from the provided definition of matching rule use: '%s'.
- ID: 350
Severity: ERROR
Message: Unable to parse the OID from the provided definition of name form: '%s'.
- ID: 351
Severity: ERROR
Message: Unable to parse the OID from the provided definition of DIT content rule: '%s'.
- ID: 352
Severity: ERROR
Message: Unable to parse the rule ID from the provided definition of DIT structure rule: '%s'.