Severity: ERROR

Message: The global access control policy defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s".

Severity: ERROR

Message: The global access control policy defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s".

Severity: ERROR

Message: The global access control policy defined in "%s" could not be parsed because it contains an unrecognized control alias "%s".

Severity: ERROR

Message: The global access control policy defined in "%s" could not be parsed because it contains an unrecognized extended operation alias "%s".

Severity: ERROR

Message: An error occurred while trying to retrieve relation configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to retrieve the managed object configuration entry %s: %s.

Severity: ERROR

Message: The managed object configuration entry %s does not appear to exist in the Directory Server configuration. This is a required entry.

Severity: ERROR

Message: An error occurred while trying to decode the managed object configuration entry %s: %s.

Severity: ERROR

Message: The Directory Server was unable to load class %s and use it to create a component instance as defined in configuration entry %s. The error that occurred was: %s. This component will be disabled.

Severity: ERROR

Message: The Directory Server jar file %s in directory %s cannot be loaded because an unexpected error occurred while trying to open the file for reading: %s.

Severity: ERROR

Message: Unable to read the Directory Server extensions because the extensions directory %s exists but is not a directory.

Severity: ERROR

Message: Unable to read the Directory Server extensions from directory %s because an unexpected error occurred while trying to list the files in that directory: %s.

Severity: ERROR

Message: The core administration manifest file %s cannot be located.

Severity: ERROR

Message: The administration manifest file %s associated with the extension %s cannot be loaded because an unexpected error occurred while trying to read it: %s.

Severity: ERROR

Message: Unable to register an add/delete listener against the entry "%s" because it does not exist in the configuration.

Severity: ERROR

Message: Reason unknown.

Severity: ERROR

Message: A configuration exception occurred while evaluating a constraint: %s.

Severity: ERROR

Message: The %s could be found but did not contain any type information (e.g. missing object classes in LDAP).

Severity: ERROR

Message: The %s could be found but did not contain the expected type information (e.g. incorrect object classes in LDAP).

Severity: ERROR

Message: The %s could be found but its type resolved to an abstract managed object definition.

Severity: ERROR

Message: The default values for the "%s" property could not be determined.

Severity: ERROR

Message: The value "%s" is not a valid value for the "%s" property, which must have the following syntax: %s.

Severity: ERROR

Message: The "%s" property must be specified as it is mandatory.

Severity: ERROR

Message: The "%s" property must not be modified as it is read-only.

Severity: ERROR

Message: The "%s" property must not contain more than one value.

Severity: ERROR

Message: An internal error occurred while processing property "%s": unknown property type "%s".

Severity: ERROR

Message: Authentication failure.

Severity: ERROR

Message: The requested authentication mechanism is not supported by the server.

Severity: ERROR

Message: Authorization failure.

Severity: ERROR

Message: A communication problem occurred while contacting the server.

Severity: ERROR

Message: The operation was rejected for the following reason: %s.

Severity: ERROR

Message: The operation was rejected for the following reasons: %s.

Severity: ERROR

Message: The operation could not be performed because a conflicting change has already occurred. There may be another client administration tool in use.

Severity: ERROR

Message: The %s could not be decoded due to the following reason: %s.

Severity: ERROR

Message: The %s could not be decoded due to the following reasons: %s.

Severity: ERROR

Message: Empty managed object names are not permitted.

Severity: ERROR

Message: Blank managed object names are not permitted.

Severity: ERROR

Message: The managed object name "%s" is not a valid value for the naming property "%s", which must have the following syntax: %s.

Severity: ERROR

Message: The managed object name "%s" is not permitted.

Severity: ERROR

Message: The managed object could not be created because there is an existing managed object with the same name.

Severity: ERROR

Message: The requested managed object could not be found.

Severity: ERROR

Message: The "%s" property is mandatory.

Severity: ERROR

Message: The following properties are mandatory: %s.

Severity: ERROR

Message: The property "%s" was not recognized.

Severity: ERROR

Message: A communication problem occurred while contacting the server: %s.

Severity: ERROR

Message: The following constraint violation occurred: %s.

Severity: ERROR

Message: The following constraint violations occurred: %s.

Severity: ERROR

Message: The value "%s" in property "%s" in the %s in entry "%s" refers to a non-existent %s in entry "%s".

Severity: ERROR

Message: The value "%s" in property "%s" in the %s in entry "%s" refers to a disabled %s in entry "%s".

Severity: ERROR

Message: The %s in entry "%s" cannot be deleted because it is referenced by the "%s" property of the %s in entry "%s".

Severity: ERROR

Message: The %s in entry "%s" cannot be disabled because it is referenced by the "%s" property of the %s in entry "%s".

Severity: ERROR

Message: An unexpected error occurred while reading the manifest file: %s.

Severity: ERROR

Message: An error occurred while attempting to load class "%s": %s.

Severity: ERROR

Message: Unable to to find the getInstance() method in the managed object definition class "%s": %s.

Severity: ERROR

Message: Unable to to invoke the getInstance() method in the managed object definition class "%s": %s.

Severity: ERROR

Message: Unable initialize the "%s" managed object definition in class "%s": %s.

Severity: ERROR

Message: The extension "%s" with manifest file %s cannot be loaded because an unexpected error occurred while trying to initialize it: %s.

Severity: ERROR

Message: The core administration classes could not be loaded from manifest file %s because an unexpected error occurred: %s.

Severity: ERROR

Message: The %s "%s" referenced in property "%s" does not exist.

Severity: ERROR

Message: The %s "%s" referenced in property "%s" exists but has an invalid configuration: %s.

Severity: ERROR

Message: The %s "%s" referenced in property "%s" is disabled.

Severity: ERROR

Message: The "%s" property in the %s called "%s" references this %s.

Severity: ERROR

Message: The "%s" property in the %s references this %s.

Severity: ERROR

Message: This %s cannot be disabled because it is referenced by the "%s" property in the %s called "%s".

Severity: ERROR

Message: This %s cannot be disabled because it is referenced by the "%s" property in the %s.

Severity: ERROR

Message: An error occurred while attempting to determine if the %s in entry %s is enabled: %s.

Severity: ERROR

Message: The administration connector self-signed certificate cannot be generated because the following error occurred: %s.

Severity: ERROR

Message: The administration connector self-signed certificate cannot be generated because the following files are missing: %s.

Severity: ERROR

Message: The registration information of server %s and server %s could not be merged. Reasons:%n%s.

Severity: ERROR

Message: Configuration attribute %s is required to have at least one value but the resulted operation would have removed all values.

Severity: ERROR

Message: Provided value %s for configuration attribute %s was rejected. The reason provided was: %s.

Severity: ERROR

Message: Configuration attribute %s is single-valued, but multiple values were provided.

Severity: ERROR

Message: Configuration attribute %s is single-valued, but adding the provided value(s) would have given it multiple values.

Severity: ERROR

Message: Configuration attribute %s already contains a value %s.

Severity: ERROR

Message: Cannot remove value %s from configuration attribute %s because the specified value does not exist.

Severity: ERROR

Message: Unable to set the value for Boolean configuration attribute %s because the provided value %s was not either 'true' or 'false'.

Severity: ERROR

Message: Unable to retrieve the value for configuration attribute %s as an integer because that attribute does not have any values.

Severity: ERROR

Message: Unable to retrieve the value for configuration attribute %s as an integer because that attribute has multiple values.

Severity: ERROR

Message: Unable to retrieve the value for configuration attribute %s as a Java int because the value is outside the allowable range for an int.

Severity: ERROR

Message: Unable to set the value for integer configuration attribute %s because the provided value %s cannot be interpreted as an integer value: %s.

Severity: ERROR

Message: Unable to set the value for configuration attribute %s because the provided value %d is less than the lowest allowed value of %d.

Severity: ERROR

Message: Unable to set the value for configuration attribute %s because the provided value %d is greater than the largest allowed value of %d.

Severity: ERROR

Message: Unable to parse value %s for configuration attribute %s as an integer value: %s.

Severity: ERROR

Message: Unable to retrieve the value for configuration attribute %s as a string because that attribute does not have any values.

Severity: ERROR

Message: Unable to retrieve the value for configuration attribute %s as a string because that attribute has multiple values.

Severity: ERROR

Message: An empty value string was provided for configuration attribute %s.

Severity: ERROR

Message: The value %s is not included in the list of acceptable values for configuration attribute %s.

Severity: ERROR

Message: '%s' is not a valid unit for configuration attribute %s.

Severity: ERROR

Message: Cannot decode %s as an integer value and a unit for configuration attribute %s because no value/unit delimiter could be found.

Severity: ERROR

Message: Could not decode the integer portion of value %s for configuration attribute %s: %s.

Severity: ERROR

Message: The provided value %s for integer with unit attribute %s is not allowed: %s.

Severity: ERROR

Message: Unable to add configuration entry %s as a child of configuration entry %s because a child entry was already found with that DN.

Severity: ERROR

Message: Unable to remove entry %s as a child of configuration entry %s because that entry did not have a child with the specified DN.

Severity: ERROR

Message: Unable to remove entry %s as a child of configuration entry %s because that entry had children of its own and non-leaf entries may not be removed.

Severity: ERROR

Message: The specified configuration file %s does not exist or is not readable.

Severity: ERROR

Message: An unexpected error occurred while attempting to determine whether configuration file %s exists: %s.

Severity: ERROR

Message: An error occurred while attempting to open the configuration file %s for reading: %s.

Severity: ERROR

Message: An error occurred while attempting to read the contents of configuration file %s: %s.

Severity: ERROR

Message: Invalid configuration attribute %s detected: the only attribute option allowed in the Directory Server configuration is "pending" to indicate the set of pending values.

Severity: ERROR

Message: An error occurred at or near line %d while trying to parse the configuration from LDIF file %s: %s.

Severity: ERROR

Message: The specified configuration file %s does not appear to contain any configuration entries.

Severity: ERROR

Message: The first entry read from LDIF configuration file %s had a DN of "%s" rather than the expected "%s" which should be used as the Directory Server configuration root.

Severity: ERROR

Message: An unexpected error occurred while attempting to process the Directory Server configuration file %s: %s.

Severity: ERROR

Message: Configuration entry %s starting at or near line %s in the LDIF configuration file %s has the same DN as another entry already read from that file.

Severity: ERROR

Message: Configuration entry %s starting at or near line %d in the configuration LDIF file %s does not appear to have a parent entry (expected parent DN was %s).

Severity: ERROR

Message: The Directory Server was unable to determine the parent DN for configuration entry %s starting at or near line %d in the configuration LDIF file %s.

Severity: ERROR

Message: Unable to determine the Directory Server instance root from either an environment variable or based on the location of the configuration file. Please set an environment variable named %s with a value containing the absolute path to the server installation root.

Severity: ERROR

Message: An unexpected error occurred while trying to write configuration entry %s to LDIF: %s.

Severity: ERROR

Message: An unexpected error occurred while trying to close the LDIF writer: %s.

Severity: ERROR

Message: The Directory Server configuration may not be altered by importing a new configuration from LDIF.

Severity: ERROR

Message: An error occurred while attempting to create a Directory Server logger from the information in configuration entry %s: %s.

Severity: ERROR

Message: Configuration entry %s does not contain a valid objectclass for a Directory Server access, error, or debug logger definition.

Severity: ERROR

Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server access logger: %s.

Severity: ERROR

Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server error logger: %s.

Severity: ERROR

Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server debug logger: %s.

Severity: ERROR

Message: Configuration attribute %s appears to contain multiple pending value sets.

Severity: ERROR

Message: Configuration attribute %s appears to contain multiple active value sets.

Severity: ERROR

Message: Configuration attribute %s does not contain an active value set.

Severity: ERROR

Message: Unable to parse value %s for configuration attribute %s as an integer value because the element was of an invalid type (%s).

Severity: ERROR

Message: Unable to parse value for configuration attribute %s as a set of integer values because the array contained elements of an invalid type (%s).

Severity: ERROR

Message: Unable to parse value %s for configuration attribute %s as a string value: %s.

Severity: ERROR

Message: Unable to parse value %s for configuration attribute %s as a string value because the element was of an invalid type (%s).

Severity: ERROR

Message: Unable to parse value for configuration attribute %s as a set of string values because the array contained elements of an invalid type (%s).

Severity: ERROR

Message: Unable to parse value %s for configuration attribute %s as an integer with unit value because the element was of an invalid type (%s).

Severity: ERROR

Message: Configuration entry %s does not contain attribute %s (or that attribute exists but is not accessible using JMX).

Severity: ERROR

Message: There is no method %s for any invokable component registered with configuration entry %s.

Severity: ERROR

Message: The Directory Server could not register a JMX MBean for the component associated with configuration entry %s: %s.

Severity: ERROR

Message: An unexpected error occurred while trying to export the Directory Server configuration to LDIF: %s.

Severity: ERROR

Message: Worker thread "%s" has experienced too many repeated failures while attempting to retrieve the next operation from the work queue (%d failures experienced, maximum of %d failures allowed). This worker thread will be destroyed.

Severity: ERROR

Message: A problem occurred while trying to create and start an instance of class %s to use as a monitor provider for the Directory Server work queue: %s. No monitor information will be available for the work queue.

Severity: ERROR

Message: A null value was provided for DN configuration attribute %s.

Severity: ERROR

Message: An error occurred while trying to parse value "%s" of attribute %s as a DN: %s.

Severity: ERROR

Message: Unable to parse value %s for configuration attribute %s as a DN: %s.

Severity: ERROR

Message: Unable to parse value %s for configuration attribute %s as a DN because the element was of an invalid type (%s).

Severity: ERROR

Message: Unable to parse value for configuration attribute %s as a set of DN values because the array contained elements of an invalid type (%s).

Severity: ERROR

Message: An unexpected error occurred while trying to register the configuration handler base DN "%s" as a private suffix with the Directory Server: %s.

Severity: ERROR

Message: An error occurred while trying to retrieve configuration entry cn=Backends,cn=config in order to initialize the Directory Server backends: %s.

Severity: ERROR

Message: The entry cn=Backends,cn=config does not appear to exist in the Directory Server configuration. This is a required entry.

Severity: ERROR

Message: An unexpected error occurred while interacting with backend configuration entry %s: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to determine whether the backend associated with configuration entry %s should be enabled or disabled: %s. It will be disabled.

Severity: ERROR

Message: The Directory Server was unable to load class %s and use it to create a backend instance as defined in configuration entry %s. The error that occurred was: %s. This backend will be disabled.

Severity: ERROR

Message: An error occurred while trying to initialize a backend loaded from class %s with the information in configuration entry %s: %s. This backend will be disabled.

Severity: ERROR

Message: The class %s specified in configuration entry %s does not contain a valid Directory Server backend implementation.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a monitor provider as defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to initialize a connection handler loaded from class %s with the information in configuration entry %s: %s. This connection handler will be disabled.

Severity: ERROR

Message: An error occurred while trying to initialize a matching rule loaded from class %s with the information in configuration entry %s: %s. This matching rule will be disabled.

Severity: ERROR

Message: An error occurred while trying to initialize an attribute syntax loaded from class %s with the information in configuration entry %s: %s. This syntax will be disabled.

Severity: ERROR

Message: Unable to read the Directory Server schema definitions because the schema directory %s does not exist.

Severity: ERROR

Message: Unable to read the Directory Server schema definitions because the schema directory %s exists but is not a directory.

Severity: ERROR

Message: Unable to read the Directory Server schema definitions from directory %s because an unexpected error occurred while trying to list the files in that directory: %s.

Severity: ERROR

Message: An unexpected error occurred that prevented the server from installing its default entry cache framework: %s.

Severity: ERROR

Message: An error occurred while attempting to initialize an instance of class %s for use as the Directory Server entry cache: %s. As a result, the entry cache will be disabled.

Severity: ERROR

Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: the entry cache level %d is already in use.

Severity: ERROR

Message: An unexpected error occurred while attempting to remove entry %s as a child of configuration entry %s: %s.

Severity: ERROR

Message: Configuration attribute %s is read-only and its values may not be altered.

Severity: ERROR

Message: An error occurred while attempting to initialize an instance of class %s as a Directory Server plugin using the information in configuration entry %s: %s. This plugin will be disabled.

Severity: ERROR

Message: Class %s specified in configuration entry %s does not contain a valid extended operation handler implementation: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as an extended operation handler as defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a SASL mechanism handler as defined in configuration entry %s: %s.

Severity: ERROR

Message: Entry %s cannot be removed from the Directory Server configuration because that DN does not have a parent.

Severity: ERROR

Message: Entry %s cannot be added to the Directory Server configuration because another configuration entry already exists with that DN.

Severity: ERROR

Message: Entry %s cannot be added to the Directory Server configuration because that DN does not have a parent.

Severity: ERROR

Message: Entry %s cannot be added to the Directory Server configuration because its parent entry %s does not exist.

Severity: ERROR

Message: The Directory Server is unwilling to add configuration entry %s because one of the add listeners registered with the parent entry %s rejected this change with the message: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to add configuration entry %s as a child of entry %s: %s.

Severity: ERROR

Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry does not exist.

Severity: ERROR

Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry has one or more subordinate entries.

Severity: ERROR

Message: Entry %s cannot be removed from the Directory Server configuration because the entry does not have a parent and removing the configuration root entry is not allowed.

Severity: ERROR

Message: Entry %s cannot be removed from the Directory Server configuration because one of the delete listeners registered with the parent entry %s rejected this change with the message: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to remove configuration entry %s as a child of entry %s: %s.

Severity: ERROR

Message: Entry %s cannot be modified because the specified entry does not exist.

Severity: ERROR

Message: Entry %s cannot be modified because one of the configuration change listeners registered for that entry rejected the change: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to modify configuration entry %s as a child of entry %s: %s.

Severity: ERROR

Message: The search operation cannot be processed because base entry %s does not exist.

Severity: ERROR

Message: The search operation cannot be processed because the specified search scope %s is invalid.

Severity: ERROR

Message: An error occurred while attempting to export the new Directory Server configuration to file %s: %s.

Severity: ERROR

Message: An error occurred while attempting to rename the new Directory Server configuration from file %s to %s: %s.

Severity: ERROR

Message: Modify DN operations are not allowed in the Directory Server configuration.

Severity: ERROR

Message: Indicates whether the Directory Server trust manager provider should be enabled. A trust manager provider is required for operations that require access to a trust manager (e.g., communication over SSL). Changes to this configuration attribute will take effect immediately, but will only impact future attempts to access the trust manager.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a password storage scheme as defined in configuration entry %s: %s.

Severity: ERROR

Message: Unable to add a new password storage scheme entry with DN %s because there is already a storage scheme registered with that DN.

Severity: ERROR

Message: The Directory Server was unable to acquire a shared lock for backend %s: %s. This generally means that the backend is in use by a process that requires an exclusive lock (e.g., importing from LDIF or restoring a backup). This backend will be disabled.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as an identity mapper as defined in configuration entry %s: %s.

Severity: ERROR

Message: The Directory Server does not have any identity mapper configured for use in conjunction with proxied authorization V2 operations. The Directory Server will not be able to process requests containing the proxied authorization control with a username-based authorization ID.

Severity: ERROR

Message: The configured proxied authorization identity mapper DN %s does not refer to an active identity mapper. The Directory Server will not be able to process requests containing the proxied authorization control with a username-based authorization ID.

Severity: ERROR

Message: An error occurred while attempting to load class %s referenced in synchronization provider configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to instantiate class %s referenced in synchronization provider configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to initialize the Directory Server synchronization provider referenced in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a password validator as defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a password generator as defined in configuration entry %s: %s.

Severity: ERROR

Message: No password policies have been defined below the cn=Password Policies,cn=config entry in the Directory Server configuration. At least one password policy configuration must be defined.

Severity: ERROR

Message: The password policy defined in configuration entry %s is invalid: %s.

Severity: ERROR

Message: The Directory Server default password policy is defined as %s, but that entry does not exist or is not below the password policy configuration base cn=Password Policies,cn=config.

Severity: ERROR

Message: An error occurred while attempting to instantiate class %s referenced in the access control configuration entry %s: %s.

Severity: ERROR

Message: Unable to register "%s" as an alternate bind DN for user "%s" because it is already registered as an alternate bind DN for root user "%s".

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as an account status notification handler as defined in configuration entry %s: %s.

Severity: ERROR

Message: Unable to add a new account status notification handler entry with DN %s because there is already a notification handler registered with that DN.

Severity: ERROR

Message: An error occurred while attempting to apply the changes contained in file %s to the server configuration at startup: %s.

Severity: ERROR

Message: Unable to apply a change at server startup: %s.

Severity: ERROR

Message: One or more errors occurred while applying changes on server startup: %s.

Severity: ERROR

Message: Configuration entry %s does not contain a valid value for configuration attribute ds-cfg-db-directory-permissions (It should be an UNIX permission mode in three-digit octal notation.).

Severity: ERROR

Message: Invalid UNIX file permissions %s does not allow read and write access to the backend database directory by the backend.

Severity: ERROR

Message: No default password policy is configured for the Directory Server. The default password policy must be specified by the ds-cfg-default-password-policy attribute in the cn=config entry.

Severity: ERROR

Message: An error occurred while trying to create the configuration archive directory %s.

Severity: ERROR

Message: An error occurred while trying to create the configuration archive directory %s: %s.

Severity: ERROR

Message: An error occurred while trying to write the current configuration to the configuration archive: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a group implementation as in configuration entry %s: %s.

Severity: ERROR

Message: You do not have sufficient privileges to perform add operations in the Directory Server configuration.

Severity: ERROR

Message: You do not have sufficient privileges to perform delete operations in the Directory Server configuration.

Severity: ERROR

Message: You do not have sufficient privileges to perform modify operations in the Directory Server configuration.

Severity: ERROR

Message: You do not have sufficient privileges to perform modify DN operations in the Directory Server configuration.

Severity: ERROR

Message: You do not have sufficient privileges to perform search operations in the Directory Server configuration.

Severity: ERROR

Message: You do not have sufficient privileges to change the set of default root privileges.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a certificate mapper as defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to retrieve the key manager provider base entry cn=Key Manager Providers,cn=config from the Directory Server configuration: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a key manager provider as defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to retrieve the trust manager provider base entry cn=Trust Manager Providers,cn=config from the Directory Server configuration: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as a trust manager provider as defined in configuration entry %s: %s.

Severity: ERROR

Message: Unable to retrieve JMX attribute %s associated with configuration entry %s: %s.

Severity: ERROR

Message: %s.%s returned a result of null for entry %s.

Severity: ERROR

Message: %s.%s failed for entry %s: result code=%s, admin action required=%b, messages="%s".

Severity: ERROR

Message: Unable to parse value "%s" from config entry "%s" as a valid search filter: %s.

Severity: ERROR

Message: An error occurred while trying to load an instance of class %s referenced in configuration entry %s as a virtual attribute provider: %s.

Severity: ERROR

Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but provider %s may generate multiple values.

Severity: ERROR

Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but the conflict behavior is configured to merge real and virtual values.

Severity: ERROR

Message: Configuration entry %s cannot be modified because the change would alter its structural object class.

Severity: ERROR

Message: An error occurred while attempting to calculate a SHA-1 digest of file %s: %s.

Severity: ERROR

Message: The Directory Server encountered an error while attempting to determine whether the configuration file %s has been externally edited with the server online, and/or trying to preserve such changes: %s. Any manual changes made to that file may have been lost.

Severity: ERROR

Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log rotation policy: %s.

Severity: ERROR

Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log retention policy: %s.

Severity: ERROR

Message: An error occurred while attempting to create a Directory Server log rotation policy from the information in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to create a Directory Server log retention policy from the information in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to create a text writer for a Directory Server logger from the information in configuration entry %s: %s.

Severity: ERROR

Message: Unable to initialize an instance of class %s as a work queue as specified in configuration entry %s: %s.

Severity: ERROR

Message: The attempt to apply the configuration add failed. The preliminary checks were all successful and the entry was added to the server configuration, but at least one of the configuration add listeners reported an error when attempting to apply the change: %s.

Severity: ERROR

Message: The attempt to apply the configuration delete failed. The preliminary checks were all successful and the entry was removed from the server configuration, but at least one of the configuration delete listeners reported an error when attempting to apply the change: %s.

Severity: ERROR

Message: The attempt to apply the configuration modification failed. The preliminary checks were all successful and the modified entry was written to the server configuration, but at least one of the configuration change listeners reported an error when attempting to apply the change: %s.

Severity: ERROR

Message: The configuration for the key manager provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the account status notification handler defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the attribute syntax defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the certificate mapper defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the group implementation defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the identity mapper defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the matching rule defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the password generator defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the password storage scheme defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the password validator defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the plugin defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the SASL mechanism handler defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the virtual attribute provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: The configuration for the alert handler defined in configuration entry %s was not acceptable: %s.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as an alert handler as defined in configuration entry %s: %s.

Severity: ERROR

Message: The provided SMTP server value '%s' is invalid. An SMTP server value must have an IP address or a resolvable name, and it may optionally be followed by a colon and an integer value between 1 and 65535 to specify the server port number.

Severity: ERROR

Message: An error occurred while attempting to open the current configuration file %s for reading in order to copy it to the ".startok" file: %s.

Severity: ERROR

Message: An error occurred while attempting to open file %s in order to write the ".startok" configuration file: %s.

Severity: ERROR

Message: An error occurred while attempting to copy the current configuration from file %s into temporary file %s for use as the ".startok" configuration file: %s.

Severity: ERROR

Message: An error occurred while attempting to rename file %s to %s for use as the ".startok" configuration file: %s.

Severity: ERROR

Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: %s.

Severity: ERROR

Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property does not follow a singular property=value form.

Severity: ERROR

Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property shadows configuration attribute %s.

Severity: ERROR

Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property is already defined for this component.

Severity: ERROR

Message: An error occurred while attempting to open the configured log file %s for logger %s: %s.

Severity: ERROR

Message: Invalid UNIX file permissions %s does not allow write access to the log file by the log publisher.

Severity: ERROR

Message: Invalid UNIX file permissions %s: %s.

Severity: ERROR

Message: The configuration entry '%s' is currently defined to be the default password policy, however it is not a password policy.

Severity: ERROR

Message: The default password policy value '%s' is invalid because it refers to an authentication policy which is not a password policy.

Severity: ERROR

Message: The timestamp format string "%s" is not a valid format string. The format string should conform to the syntax described in the documentation for the "java.text.SimpleDateFormat" class.

Severity: ERROR

Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s".

Severity: ERROR

Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s".

Severity: ERROR

Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server HTTP access logger: %s.

Severity: ERROR

Message: The log format for configuration entry %s is empty. No information will be logged even if logging is activated.

Severity: ERROR

Message: An error occurred while attempting to update a Directory Server logger from the information in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to delete a Directory Server logger from the information in configuration entry %s: %s.

Severity: ERROR

Message: Cannot configure java.util.logging root logger level: %s. java.util.logging support is now disabled.

Severity: ERROR

Message: An error occurred while trying to initialize an instance of class %s as an HTTP endpoint as defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while starting the HTTP endpoint as defined in configuration entry %s: %s.

Severity: ERROR

Message: The HTTP endpoint configuration defined in %s is invalid: %s.

Severity: ERROR

Message: Invalid configuration URL in the REST2LDAP endpoint configuration entry %s: %s.

Severity: ERROR

Message: Cannot initialize the configuration framework: %s.

Severity: ERROR

Message: Unable to retrieve children of configuration entry with dn: %s.

Severity: ERROR

Message: Unable to load the configuration-enabled schema: %s.

Severity: ERROR

Message: Backend config error when trying to delete an entry: %s.

Severity: ERROR

Message: The HTTP endpoint configuration defined in %s is referencing a non existing authorization DN %s.

Severity: ERROR

Message: The HTTP endpoint configuration defined in %s is referencing mutually exclusive authorization DNs %s and %s.

Severity: ERROR

Message: Unable to read the configuration from %s in the REST2LDAP endpoint configuration entry %s: %s.

Severity: ERROR

Message: Invalid JSON element %s from %s in the REST2LDAP endpoint configuration entry %s: %s.

Severity: ERROR

Message: Invalid configuration element from %s in the REST2LDAP endpoint configuration entry %s: %s.

Severity: ERROR

Message: The OAuth2 authorization mechanism defined in %s contains an invalid JSON Pointer %s: %s.

Severity: ERROR

Message: The authorization mechanism defined in %s is referencing a non-existing or non-readable directory: %s.

Severity: ERROR

Message: The authorization mechanism defined in %s is referencing a non existing DN: %s.

Severity: ERROR

Message: The authorization mechanism defined in %s is referencing an invalid URL %s: %s.

Severity: ERROR

Message: Unable to configure the authorization mechanism defined in %s: %s.

Severity: ERROR

Message: The requested admin API version '%s' is unsupported. This endpoint only supports the following admin API version(s): %s.

Severity: ERROR

Message: The configuration of schema provider '%s' is not acceptable for the following reasons: %s.

Severity: ERROR

Message: The schema provider class '%s' could not be instantiated or initialized with the configuration '%s' : %s.

Severity: ERROR

Message: The core schema provider defined by '%s' has been disabled. The core schema must always be enabled.

Severity: ERROR

Message: Unable to configure the backend '%s' because one of its base DNs is the empty DN.

Severity: ERROR

Message: Cannot configure new SSL protocols for '%s' because the protocols '%s' are not supported. Look for supported protocols in 'cn=System,cn=monitor'.

Severity: ERROR

Message: Cannot configure new SSL cipher suites for '%s' because the cipher suites '%s' are not supported. Look for supported cipher suites in 'cn=System,cn=monitor'.

Severity: ERROR

Message: The metric name pattern to exclude '%s' cannot be parsed as a valid regular expression due to the following error: '%s'.

Severity: ERROR

Message: The metric name pattern to include '%s' cannot be parsed as a valid regular expression due to the following error: '%s'.

Severity: ERROR

Message: The list of keys defined for the JSON matching rule contains an invalid JSON pointer : %s.

Severity: ERROR

Message: The list of keys defined for the JSON matching rule is empty.

Severity: ERROR

Message: Cannot create the property resolver due to the following error: '%s'.

Severity: ERROR

Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the sequence was null.

Severity: ERROR

Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the first element of the sequence could not be decoded as an integer message ID: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the second element of the sequence could not be decoded as the protocol op: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the third element of the sequence could not be decoded as the set of controls: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP control because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP control because the OID could not be decoded as a string: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP control because the criticality could not be decoded as Boolean value: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP control because the value could not be decoded as an octet string: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as a set of LDAP controls because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP abandon request protocol op because a problem occurred while trying to obtain the message ID of the operation to abandon: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because a problem occurred while trying to parse the result sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the first element in the result sequence could not be decoded as an integer result code: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the second element in the result sequence could not be decoded as the matched DN: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the third element in the result sequence could not be decoded as the error message: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the fourth element in the result sequence could not be decoded as a set of referral URLs: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind response protocol op because the final element in the result sequence could not be decoded as the server SASL credentials: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind response protocol op because the response OID could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind response protocol op because the response value could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP unbind request protocol op: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the protocol version could not be decoded as an integer: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the bind DN could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the password to use for simple authentication could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the SASL authentication information could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the authentication info element had an invalid BER type (expected 80 or A3, got %x).

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because an unexpected error occurred while trying to decode the authentication info element: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the target DN could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the attribute value assertion could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the attribute type could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the assertion value could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP delete request protocol op because the target DN could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP extended request protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP extended request protocol op because the OID could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP extended request protocol op because the value could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the entry DN could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the new RDN could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the deleteOldRDN flag could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the new superior DN could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP attribute because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP attribute because the attribute type could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP attribute because the set of values could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP add request protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP add request protocol op because the entry DN could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP add request protocol op because the set of attributes could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modification because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modification because it contained an invalid modification type (%d).

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modification because the modification type could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modification because the attribute could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify request protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify request protocol op because the entry DN could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP modify request protocol op because the set of modifications could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search result entry protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search result entry protocol op because the entry DN could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search result entry protocol op because the set of attributes could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search result reference protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search result reference protocol op because a problem occurred while trying to decode the sequence elements as referral URLs: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the base DN could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the provided scope value (%d) is invalid.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the scope could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the provided alias dereferencing policy value (%d) is invalid.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the alias dereferencing policy could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the size limit could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the time limit could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the typesOnly flag could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the filter could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the requested attribute set could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP protocol op because the element was null.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP protocol op because the element had an invalid BER type (%x) for an LDAP protocol op.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element was null.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element had an invalid BER type (%x) for a search filter.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because an unexpected error occurred while trying to decode one of the compound filter components: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the NOT component element could not be decoded as an LDAP filter: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as a type-and-value sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the attribute type could not be decoded from the type-and-value sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the assertion value could not be decoded from the type-and-value sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as a substring sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the attribute type could not be decoded from the substring sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the substring value sequence could not be decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the substring value sequence did not contain any elements.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because a problem occurred while trying to parse the substring value elements: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as the presence attribute type: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as an extensible matching sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP search filter because a problem occurred while trying to parse the extensible match sequence elements: %s.

Severity: ERROR

Message: The server attempted to send a response to the %s operation (conn=%d, op=%d), but the operation did not have a result code. This could indicate that the operation did not complete properly or that it is one that is not allowed to have a response. Using a generic 'Operations Error' response.

Severity: ERROR

Message: The server attempted to send a response to the %s operation (conn=%d, op=%d), but this type of operation is not allowed to have responses. Backtrace: %s.

Severity: ERROR

Message: The LDAP connection handler defined in configuration entry %s was unable to open a selector to allow it to multiplex the associated accept sockets: %s. This connection handler will be disabled.

Severity: ERROR

Message: The LDAP connection handler defined in configuration entry %s was unable to create a server socket channel to accept connections on %s:%d: %s. The Directory Server will not listen for new connections on that address.

Severity: ERROR

Message: The LDAP connection handler defined in configuration entry %s was unable to create any of the socket channels on any of the configured addresses. This connection handler will be disabled.

Severity: ERROR

Message: The connection attempt from client %s to %s has been rejected because the client was included in one of the denied address ranges.

Severity: ERROR

Message: The connection attempt from client %s to %s has been rejected because the client was not included in one of the allowed address ranges.

Severity: ERROR

Message: The %s defined in configuration entry %s was unable to accept a new client connection: %s.

Severity: ERROR

Message: The %s defined in configuration entry %s has experienced consecutive failures while trying to accept client connections: %s. This connection handler will be disabled.

Severity: ERROR

Message: The LDAP connection handler defined in configuration entry %s caught an unexpected error while trying to listen for new connections: %s. This connection handler will be disabled.

Severity: ERROR

Message: %s was unable to open a selector to multiplex reads from clients: %s. This request handler cannot continue processing.

Severity: ERROR

Message: %s was unable to register this client connection with the selector: %s.

Severity: ERROR

Message: This connection could not be registered with a request handler because the Directory Server is shutting down.

Severity: ERROR

Message: This client connection is being deregistered from the associated request handler because the Directory Server is shutting down.

Severity: ERROR

Message: Cannot decode the provided string as an LDAP search filter because the string was null.

Severity: ERROR

Message: Cannot decode the provided string %s as an LDAP search filter because an unexpected exception was thrown during processing: %s.

Severity: ERROR

Message: The provided search filter "%s" had mismatched parentheses around the portion between positions %d and %d.

Severity: ERROR

Message: The provided search filter "%s" was missing an equal sign in the suspected simple filter component between positions %d and %d.

Severity: ERROR

Message: The provided search filter "%s" had an invalid escaped byte value at position %d. A backslash in a value must be followed by two hexadecimal characters that define the byte that has been encoded.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the compound filter between positions %d and %d did not start with an open parenthesis and end with a close parenthesis (they might be parentheses for different filter components).

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the closing parenthesis at position %d did not have a corresponding open parenthesis.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the opening parenthesis at position %d did not have a corresponding close parenthesis.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the assumed substring filter value between positions %d and %d did not have any asterisk wildcard characters.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the extensible match component starting at position %d did not have a colon to denote the end of the attribute type name.

Severity: ERROR

Message: Terminating this connection because the client sent an invalid message of type %s (LDAP message ID %d) that is not allowed for request messages.

Severity: ERROR

Message: An unexpected failure occurred while trying to process a request of type %s (LDAP message ID %d): %s. The client connection will be terminated.

Severity: ERROR

Message: The bind request message (LDAP message ID %d) included an invalid authentication type of %s. This is a protocol error, and this connection will be terminated as per RFC 2251 section 4.2.3.

Severity: ERROR

Message: This client connection is being terminated because a protocol error occurred while trying to process a bind request. The LDAP message ID was %d and the error message for the bind response was %s.

Severity: ERROR

Message: An extended response message would have been sent to an LDAPv2 client (connection ID=%d, operation ID=%d): %s. LDAPv2 does not allow extended operations, so this response will not be sent.

Severity: ERROR

Message: A search performed by an LDAPv2 client (connection ID=%d, operation ID=%d) would have included a search result reference %s. Referrals are not allowed for LDAPv2 clients, so this search reference will not be sent.

Severity: ERROR

Message: The original result code for this message was 10 but this result is not allowed for LDAPv2 clients.

Severity: ERROR

Message: The response included one or more referrals, which are not allowed for LDAPv2 clients. The referrals included were: %s.

Severity: ERROR

Message: The Directory Server has been configured to deny access to LDAPv2 clients. This connection will be closed.

Severity: ERROR

Message: The client with connection ID %d authenticated to the Directory Server using LDAPv2, but attempted to send an extended operation request (LDAP message ID %d), which is not allowed for LDAPv2 clients. The connection will be terminated.

Severity: ERROR

Message: An attempt was made to initialize the LDAP statistics monitor provider as defined in configuration entry %s. This monitor provider should only be dynamically created within the Directory Server itself and not from within the configuration.

Severity: ERROR

Message: The LDAP request handler thread "%s" encountered an unexpected error that would have caused the thread to die: %s. The error has been caught and the request handler should continue operating as normal.

Severity: ERROR

Message: The attempt to register this connection with the Directory Server was rejected. This might indicate that the server already has the maximum allowed number of concurrent connections established, or that it is in a restricted access mode.

Severity: ERROR

Message: An unexpected error occurred while trying to decode the DN %s used for internal operations as a root user: %s.

Severity: ERROR

Message: The TLS connection security provider cannot be enabled on this client connection because it is already using the %s provider. StartTLS can only be used on clear-text connections.

Severity: ERROR

Message: StartTLS cannot be enabled on this LDAP client connection because the corresponding LDAP connection handler is configured to reject StartTLS requests. The use of StartTLS can be enabled using the ds-cfg-allow-start-tls configuration attribute.

Severity: ERROR

Message: An error occurred while attempting to create a TLS connection security provider for this client connection for use with StartTLS: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the element is null.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the size element could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the cookie could not be properly decoded: %s.

Severity: ERROR

Message: Cannot decode the provided LDAP assertion control because the control does not have a value.

Severity: ERROR

Message: Cannot decode the provided LDAP pre-read request control because the control does not have a value.

Severity: ERROR

Message: Cannot decode the provided LDAP pre-read request control because an error occurred while trying to decode the control value: %s.

Severity: ERROR

Message: Cannot decode the provided LDAP post-read request control because the control does not have a value.

Severity: ERROR

Message: Cannot decode the provided LDAP post-read request control because an error occurred while trying to decode the control value: %s.

Severity: ERROR

Message: Cannot decode the provided LDAP pre-read response control because the control does not have a value.

Severity: ERROR

Message: Cannot decode the provided LDAP pre-read response control because an error occurred while trying to decode the control value: %s.

Severity: ERROR

Message: Cannot decode the provided LDAP post-read response control because the control does not have a value.

Severity: ERROR

Message: Cannot decode the provided LDAP post-read response control because an error occurred while trying to decode the control value: %s.

Severity: ERROR

Message: Cannot decode the provided proxied authorization V1 control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided proxied authorization V1 control because an error occurred while attempting to decode the control value: %s.

Severity: ERROR

Message: User %s specified in the proxied authorization V1 control does not exist in the Directory Server.

Severity: ERROR

Message: Cannot decode the provided proxied authorization V2 control because it does not have a value.

Severity: ERROR

Message: Unable to process proxied authorization V2 control because it contains an authorization ID based on a username and no proxied authorization identity mapper is configured in the Directory Server.

Severity: ERROR

Message: The authorization ID "%s" contained in the proxied authorization V2 control is invalid because it does not start with "dn:" to indicate a user DN or "u:" to indicate a username.

Severity: ERROR

Message: User %s specified in the proxied authorization V2 control does not exist in the Directory Server.

Severity: ERROR

Message: The provided integer value %d does not correspond to any persistent search change type.

Severity: ERROR

Message: The provided integer value indicated that there were no persistent search change types, which is not allowed.

Severity: ERROR

Message: The provided integer value %d was outside the range of acceptable values for an encoded change type set.

Severity: ERROR

Message: Cannot decode the provided persistent search control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided persistent search control because an error occurred while attempting to decode the control value: %s.

Severity: ERROR

Message: Cannot decode the provided entry change notification control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided entry change notification control because it contains a previous DN element but had a change type of %s. The previous DN element can only be provided with the modify DN change type.

Severity: ERROR

Message: Cannot decode the provided entry change notification control because an error occurred while attempting to decode the control value: %s.

Severity: ERROR

Message: Cannot decode the provided authorization identity response control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided ASN.1 element as an LDAP intermediate response protocol op because the element could not be decoded as a sequence: %s.

Severity: ERROR

Message: An error occurred while attempting to decode the intermediate response OID: %s.

Severity: ERROR

Message: An error occurred while attempting to decode the intermediate response value: %s.

Severity: ERROR

Message: The provided LDAP filter "%s" cannot be used as a matched values filter because filters of type %s are not allowed for use in matched values filters.

Severity: ERROR

Message: The provided LDAP filter "%s" cannot be used as a matched values filter because it is an extensible match filter that contains the dnAttributes flag, which is not allowed for matched values filters.

Severity: ERROR

Message: An error occurred while attempting to decode the attribute value assertion in the provided matched values filter: %s.

Severity: ERROR

Message: The provided matched values filter could not be decoded because there were no subInitial, subAny, or subFinal components in the substring filter.

Severity: ERROR

Message: The provided matched values filter could not be decoded because an error occurred while decoding the substring filter component: %s.

Severity: ERROR

Message: The provided matched values filter could not be decoded because an error occurred while decoding the presence filter component: %s.

Severity: ERROR

Message: The provided matched values filter could not be decoded because an error occurred while decoding the extensible match filter component: %s.

Severity: ERROR

Message: The provided matched values filter could not be decoded because it had an invalid BER type of %s.

Severity: ERROR

Message: Cannot decode the provided matched values control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided matched values control because an error occurred while attempting to decode the value as an ASN.1 sequence: %s.

Severity: ERROR

Message: Cannot decode the provided matched values control because the control value does not specify any filters for use in matching attribute values.

Severity: ERROR

Message: Cannot decode the provided control as a password expired control because the provided control had a value that could not be parsed as an integer.

Severity: ERROR

Message: Cannot decode the provided password expiring control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided control as a password expiring control because an error occurred while attempting to decode the number of seconds until expiration: %s.

Severity: ERROR

Message: Cannot decode the provided control as a password policy request control because the provided control had a value but the password policy request control should not have a value.

Severity: ERROR

Message: Cannot decode the provided password policy response control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided password policy response control because the warning element has an invalid type of %s.

Severity: ERROR

Message: Cannot decode the provided password policy response control because the error element has an invalid type of %d.

Severity: ERROR

Message: Cannot decode the provided password policy response control: %s.

Severity: ERROR

Message: Use of the proxied authorization V1 control for user %s is not allowed by the password policy configuration.

Severity: ERROR

Message: Cannot decode the provided control as an account availability request control because the provided control had a value but the account availability request control should not have a value.

Severity: ERROR

Message: Cannot decode the provided account availability response control because it does not have a value.

Severity: ERROR

Message: The account availability response control had an unknown ACCOUNT_USABLE_RESPONSE element type of %s.

Severity: ERROR

Message: Cannot decode the provided account availability response control: %s.

Severity: ERROR

Message: The provided LDAP attribute %s contains duplicate values.

Severity: ERROR

Message: The provided LDAP search filter references unknown matching rule %s.

Severity: ERROR

Message: The provided LDAP search filter has an assertion value but does not include either an attribute type or a matching rule ID.

Severity: ERROR

Message: Unable to call select() in the LDAP connection handler: %s. It appears that your JVM may be susceptible to the issue described at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable to handle LDAP requests in its current configuration. Please upgrade to a newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) or set the number of available file descriptors to a value greater than or equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting the Directory Server.

Severity: ERROR

Message: Unwilling to process the request because it contains a proxied authorization V1 control which is not marked critical. The proxied authorization control must always have a criticality of "true".

Severity: ERROR

Message: Unwilling to process the request because it contains a proxied authorization V2 control which is not marked critical. The proxied authorization control must always have a criticality of "true".

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the NOT filter between positions %d and %d did not contain exactly one filter component.

Severity: ERROR

Message: An LDAP filter enclosed in apostrophes is invalid: %s.

Severity: ERROR

Message: The provided search filter contains an invalid attribute type '%s' with invalid character '%s' at position %d.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the extensible match component starting at position %d did not include either an attribute description or a matching rule ID. At least one of them must be provided.

Severity: ERROR

Message: LDAPv2 clients are not allowed to use request controls.

Severity: ERROR

Message: The %s connection handler defined in configuration entry %s was unable to bind to %s:%d: %s.

Severity: ERROR

Message: You do not have sufficient privileges to perform search operations through JMX.

Severity: ERROR

Message: You do not have sufficient privileges to establish the connection through JMX. At least JMX_READ privilege is required.

Severity: ERROR

Message: User %s does not exist in the directory.

Severity: ERROR

Message: This output stream has been closed.

Severity: ERROR

Message: The provided LDAP message had an invalid operation type (%s) for a request.

Severity: ERROR

Message: SASL bind operations are not supported over internal LDAP sockets.

Severity: ERROR

Message: StartTLS operations are not supported over internal LDAP sockets.

Severity: ERROR

Message: An error occurred while trying to read a change record from the LDIF file: %s. This change will be skipped but processing on the LDIF file will continue.

Severity: ERROR

Message: An error occurred while trying to read a change record from the LDIF file: %s. No further processing on this LDIF file can be performed.

Severity: ERROR

Message: An I/O error occurred while the LDIF connection handler was processing LDIF file %s: %s.

Severity: ERROR

Message: An error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %s.

Severity: ERROR

Message: An error occurred while the LDIF connection handler was attempting to delete processed file %s: %s.

Severity: ERROR

Message: Address already in use.

Severity: ERROR

Message: Cannot decode the provided subentries control because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided subentries control because an error occurred while attempting to decode the control value: %s.

Severity: ERROR

Message: No Configuration was defined for this connection handler. The configuration parameters ds-cfg-listen-port and ds-cfg-trap-port are required by the connection handler to start.

Severity: ERROR

Message: Traps Destination %s is an unknown host. Traps will not be sent to this destination.

Severity: ERROR

Message: You do not have the appropriate OpenDMK jar files to enable the SNMP Connection Handler. The jdmkrt.jar file must be installed into the 'extlib' directory. The SNMP connection Handler could not be started.

Severity: ERROR

Message: Cannot initialize the SNMP Connection Handler. Please check the configuration attributes.

Severity: ERROR

Message: No valid trap destinations has been found. No trap will be sent.

Severity: ERROR

Message: Cannot decode the provided subtree delete control because it contains a value.

Severity: ERROR

Message: An error occurred while attempting to initialize the SSL context for use in the LDAP Connection Handler: %s.

Severity: ERROR

Message: The Directory Server does not support LDAP protocol version %d. This connection will be closed.

Severity: ERROR

Message: The required OpenDMK classes could not be loaded using jar file '%s'. Verify that the jar file is not corrupted.

Severity: ERROR

Message: Cannot decode the provided control %s because an error occurred while attempting to decode the control value: %s.

Severity: ERROR

Message: Unable to process the provided internal modifications request control because it did not contain an origin.

Severity: ERROR

Message: Unable to process the provided internal modifications request control because it did not contain modifications.

Severity: ERROR

Message: Unable to process the provided internal modifications request control: %s.

Severity: ERROR

Message: Unable to process the provided replication context request control because it did not contain a CSN.

Severity: ERROR

Message: Unable to process the provided replication context request control because it did not contain an entry UUID.

Severity: ERROR

Message: Connection reset by client.

Severity: ERROR

Message: Unable to process response received for HTTP client connection for request '%s' because the response '%s' is not of any of the expected types.

Severity: ERROR

Message: The server received configuration changes that require a restart of the %s connection handler to take effect.

Severity: ERROR

Message: No result received after completion for request '%s' received for HTTP client connection.

Severity: ERROR

Message: Unable to process request '%s' received for internal client connection: %s.

Severity: ERROR

Message: Unable to process response received for internal client connection for request '%s' because the response '%s' is not of any of the expected types.

Severity: ERROR

Message: No result received after completion for request '%s' received for internal client connection.

Severity: ERROR

Message: The GSER value does not contain a valid identifier at the current position: %s.

Severity: ERROR

Message: The GSER value does not contain a whitespace character at the current position: %s.

Severity: ERROR

Message: The GSER value does not contain a valid IdentifiedChoiceValue at the current position: %s.

Severity: ERROR

Message: Unable to process response received for JMX client connection for request '%s' because the response '%s' is not of any of the expected types.

Severity: ERROR

Message: Authorization as '%s' specified in the proxied authorization control is not permitted.

Severity: ERROR

Message: Unable to process request '%s' received for JMX client connection: %s.

Severity: ERROR

Message: User authentication is mandatory to access server monitoring information.

Severity: ERROR

Message: Unable to process the provided server-side sort request control because it references unrecognized attribute type '%s'.

Severity: ERROR

Message: Failed to initialize Http Connection Handler.

Severity: ERROR

Message: No value was provided for the transaction id control, whereas an UTF-8 encoded value is expected.

Severity: ERROR

Message: Exception on the underlying client connection: %s.

Severity: ERROR

Message: The underlying client connection timed out or closed: %s.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is disabled.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is expired.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is locked.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account's password is expired.

Severity: ERROR

Message: Abandon requests cannot be canceled.

Severity: ERROR

Message: Bind requests cannot be canceled.

Severity: ERROR

Message: Unbind requests cannot be canceled.

Severity: ERROR

Message: %s encountered an uncaught exception while processing operation %s: %s.

Severity: ERROR

Message: The Directory Server is currently running. The configuration may not be bootstrapped while the server is online.

Severity: ERROR

Message: Unable to create an instance of class %s to serve as the Directory Server configuration handler: %s.

Severity: ERROR

Message: An error occurred while trying to initialize the configuration handler %s using configuration file %s: %s.

Severity: ERROR

Message: The Directory Server may not be started before the configuration has been bootstrapped.

Severity: ERROR

Message: The Directory Server may not be started while it is already running. Please stop the running instance before attempting to start it again.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it is missing attribute %s which is required by objectclass %s.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it includes attribute %s which is not allowed by any of the objectclasses defined in that entry.

Severity: ERROR

Message: An error occurred while attempting to bootstrap the attribute syntax defined in class %s: %s.

Severity: ERROR

Message: An error occurred while attempting to create the JMX MBean server that will be used for monitoring, notification, and configuration interaction within the Directory Server: %s.

Severity: ERROR

Message: An uncaught exception during processing for thread %s has caused it to terminate abnormally. The stack trace for that exception is: %s.

Severity: ERROR

Message: The Directory Server shutdown hook detected that the JVM is shutting down. This generally indicates that JVM received an external request to stop (e.g., through a kill signal).

Severity: ERROR

Message: Unable to decode the provided filter string as a search filter because the provided string was empty or null.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode the string "%s" as a search filter: %s.

Severity: ERROR

Message: The provided search filter "%s" had mismatched parentheses around the portion between positions %d and %d.

Severity: ERROR

Message: The provided search filter "%s" was missing an equal sign in the suspected simple filter component between positions %d and %d.

Severity: ERROR

Message: The provided search filter "%s" had an invalid escaped byte value at position %d. A backslash in a value must be followed by two hexadecimal characters that define the byte that has been encoded.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the compound filter between positions %d and %d did not start with an open parenthesis and end with a close parenthesis (they may be parentheses for different filter components).

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the closing parenthesis at position %d did not have a corresponding open parenthesis.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the opening parenthesis at position %d did not have a corresponding close parenthesis.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the assumed substring filter value between positions %d and %d did not have any asterisk wildcard characters.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the extensible match component starting at position %d did not have a colon to denote the end of the attribute type name.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because it contained an unknown filter type %s.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because the internal check returned an unknown result type "%s".

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because the set of filter components for an %s component was NULL.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because the filter was nested beyond the maximum allowed depth of 100 levels.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because the NOT filter component did not include a subcomponent.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because an equality component had a NULL attribute type.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because an equality component for attribute %s had a NULL assertion value.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a substring component had a NULL attribute type.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a substring component for attribute %s did not have any subInitial, subAny, or subFinal elements.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a greater-or-equal component had a NULL attribute type.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a greater-or-equal component for attribute %s had a NULL assertion value.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a less-or-equal component had a NULL attribute type.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a less-or-equal component for attribute %s had a NULL assertion value.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a presence component had a NULL attribute type.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because an approximate component had a NULL attribute type.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because an approximate component for attribute %s had a NULL assertion value.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a contained extensible match filter did not have an assertion value.

Severity: ERROR

Message: Unable to determine whether entry "%s" matches filter "%s" because a contained extensible match filter did not have either an attribute type or a matching rule ID.

Severity: ERROR

Message: Unable to decode the provided string as a relative distinguished name because the provided string was empty or null.

Severity: ERROR

Message: Unable to decode the provided string "%s" as a relative distinguished name because the string ended with an attribute type name (%s).

Severity: ERROR

Message: Unable to decode the provided string "%s" as a relative distinguished name because the first non-blank character after the attribute type %s was not an equal sign (character read was %c).

Severity: ERROR

Message: Unable to decode the provided string "%s" as a relative distinguished name because it contained an unexpected plus, comma, or semicolon at position %d, which is not allowed in an RDN.

Severity: ERROR

Message: Unable to decode the provided string "%s" as a relative distinguished name because an illegal character %c was found at position %d, where either the end of the string or a '+' sign were expected.

Severity: ERROR

Message: An error occurred while trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) from the Directory Server configuration: %s.

Severity: ERROR

Message: Unable to register objectclass %s with the server schema because its OID %s conflicts with the OID of an existing objectclass %s.

Severity: ERROR

Message: Unable to register objectclass %s with the server schema because its name %s conflicts with the name of an existing objectclass %s.

Severity: ERROR

Message: Unable to register matching rule %s with the server schema because its name %s conflicts with the name of an existing matching rule %s.

Severity: ERROR

Message: Unable to register matching rule use %s with the server schema because its matching rule %s conflicts with the matching rule for an existing matching rule use %s.

Severity: ERROR

Message: Unable to register DIT content rule %s with the server schema because its structural objectclass %s conflicts with the structural objectclass for an existing DIT content rule %s.

Severity: ERROR

Message: Unable to register DIT structure rule %s with the server schema because its name form %s conflicts with the name form for an existing DIT structure rule %s.

Severity: ERROR

Message: Unable to register DIT structure rule %s with the server schema because its rule ID %d conflicts with the rule ID for an existing DIT structure rule %s.

Severity: ERROR

Message: Unable to register name form %s with the server schema because its structural objectclass %s conflicts with the structural objectclass for an existing name form %s.

Severity: ERROR

Message: Unable to register name form %s with the server schema because its OID %s conflicts with the OID for an existing name form %s.

Severity: ERROR

Message: Unable to register name form %s with the server schema because its name %s conflicts with the name for an existing name form %s.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it includes multiple conflicting structural objectclasses %s and %s. Only a single structural objectclass is allowed in an entry.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it does not include a structural objectclass. All entries must contain a structural objectclass.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it includes multiple values for attribute %s, which is defined as a single-valued attribute.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because its RDN does not contain attribute %s that is required by name form %s.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because its RDN contains attribute %s that is not allowed by name form %s.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it is missing attribute %s which is required by DIT content rule %s.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it contains attribute %s which is prohibited by DIT content rule %s.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it includes auxiliary objectClass %s that is not allowed by DIT content rule %s.

Severity: ERROR

Message: The Directory Server was unable to evaluate entry %s to determine whether it was compliant with the DIT structure rule configuration because parent entry %s either does not exist or could not be retrieved.

Severity: ERROR

Message: The Directory Server was unable to evaluate entry %s to determine whether it was compliant with the DIT rule configuration because the parent entry %s does not appear to contain a valid structural objectclass.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because DIT structure rule %s does not allow entries of type %s to be placed immediately below entries of type %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to check entry %s against DIT structure rule %s: %s.

Severity: ERROR

Message: Unable to bind to the Directory Server because no such user exists in the server.

Severity: ERROR

Message: A fatal error occurred when executing one of the Directory Server startup plugins: %s (error ID %d). The Directory Server startup process has been aborted.

Severity: ERROR

Message: Unable to bind to the Directory Server using simple authentication because that user does not have a password.

Severity: ERROR

Message: Unable to process the bind request because it attempted to use an unknown SASL mechanism %s that is not available in the Directory Server.

Severity: ERROR

Message: The specified entry %s does not exist in the Directory Server.

Severity: ERROR

Message: The provided entry cannot be added because it contains a null DN. This DN is reserved for the root DSE, and that entry may not be added over protocol.

Severity: ERROR

Message: The provided entry %s cannot be added because it does not have a parent and is not defined as one of the suffixes within the Directory Server.

Severity: ERROR

Message: Entry %s cannot be added because its parent entry %s does not exist in the server.

Severity: ERROR

Message: Entry %s cannot be added because the server failed to obtain a write lock for this entry after multiple attempts.

Severity: ERROR

Message: Entry %s cannot be removed because the server failed to obtain a write lock for this entry after multiple attempts.

Severity: ERROR

Message: The maximum time limit of %d seconds for processing this search operation has expired.

Severity: ERROR

Message: This search operation has sent the maximum of %d entries to the client.

Severity: ERROR

Message: The entry %s specified as the search base does not exist in the Directory Server.

Severity: ERROR

Message: Entry %s does not exist in the Directory Server.

Severity: ERROR

Message: Entry %s cannot be removed because the backend that should contain that entry has a subordinate backend with a base DN of %s that is below the target DN.

Severity: ERROR

Message: A modify DN operation cannot be performed on entry %s because the new RDN would not have a parent DN.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because no backend is registered to handle that DN.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because no backend is registered to handle the new DN %s.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because the backend holding the current entry is different from the backend used to handle the new DN %s. Modify DN operations may not span multiple backends.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for that DN.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for the new DN %s.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because that entry does not exist in the server.

Severity: ERROR

Message: Entry %s cannot be modified because the server failed to obtain a write lock for this entry after multiple attempts.

Severity: ERROR

Message: Entry %s cannot be modified because no such entry exists in the server.

Severity: ERROR

Message: Entry %s cannot be modified because the modification contained an add component for attribute %s but no values were provided.

Severity: ERROR

Message: When attempting to modify entry %s to add one or more values for attribute %s, value "%s" was found to be invalid according to the associated syntax: %s.

Severity: ERROR

Message: Entry %s cannot be modified because it would have resulted in one or more duplicate values for attribute %s: %s.

Severity: ERROR

Message: Entry %s cannot be modified because the change to attribute %s would have removed a value used in the RDN.

Severity: ERROR

Message: Entry %s cannot be modified because the attempt to update attribute %s would have removed one or more values from the attribute that were not present: %s.

Severity: ERROR

Message: Entry %s cannot be modified because an attempt was made to remove one or more values from attribute %s but this attribute is not present in the entry.

Severity: ERROR

Message: When attempting to modify entry %s to replace the set of values for attribute %s, value "%s" was found to be invalid according to the associated syntax: %s.

Severity: ERROR

Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s which is used as an RDN attribute for the entry.

Severity: ERROR

Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but the request did not include a value for that attribute specifying the amount by which to increment the value.

Severity: ERROR

Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but the request contained multiple values, where only a single integer value is allowed.

Severity: ERROR

Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but the value "%s" contained in the request could not be parsed as an integer.

Severity: ERROR

Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but that attribute did not have any values in the target entry.

Severity: ERROR

Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but the value "%s" could not be parsed as an integer.

Severity: ERROR

Message: Entry %s cannot be modified because the resulting entry would have violated the server schema: %s.

Severity: ERROR

Message: Entry %s cannot be modified because there is no backend registered to handle operations for that entry.

Severity: ERROR

Message: There is no extended operation handler registered with the Directory Server for handling extended operations with a request OID of %s.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it contains an unknown objectclass %s.

Severity: ERROR

Message: An unexpected error was encountered while processing a search in one of the Directory Server backends: %s.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because the change would have violated the server schema: %s.

Severity: ERROR

Message: Object class %s cannot be added to entry %s because that class is not defined in the Directory Server schema.

Severity: ERROR

Message: Object class %s is already present in entry %s and cannot be added a second time.

Severity: ERROR

Message: The password provided by the user did not match any password(s) stored in the user's entry.

Severity: ERROR

Message: An error occurred while attempting to initialize the command-line arguments: %s.

Severity: ERROR

Message: An error occurred while attempting to parse the provided set of command line arguments: %s.

Severity: ERROR

Message: An error occurred while attempting to bootstrap the Directory Server: %s.

Severity: ERROR

Message: An error occurred while trying to start the Directory Server: %s.

Severity: ERROR

Message: The line "%s" associated with the backup information in directory %s could not be parsed because it did not contain an equal sign to delimit the property name from the value.

Severity: ERROR

Message: The line "%s" associated with the backup information in directory %s could not be parsed because it did not include a property name.

Severity: ERROR

Message: The backup information structure in directory %s could not be parsed because it contained multiple backup IDs (%s and %s).

Severity: ERROR

Message: The backup information structure in directory %s could not be parsed because it contained an unknown property %s with value %s.

Severity: ERROR

Message: An unexpected error occurred while trying to decode a backup information structure in directory %s: %s.

Severity: ERROR

Message: Unable to decode a backup information structure in directory %s because the structure did not include a backup ID.

Severity: ERROR

Message: The backup information structure with backup ID %s in directory %s was not valid because it did not contain the backup date.

Severity: ERROR

Message: Cannot add a backup with ID %s to backup directory %s because another backup already exists with that ID.

Severity: ERROR

Message: Cannot remove backup %s from backup directory %s because no backup with that ID exists in that directory.

Severity: ERROR

Message: Cannot remove backup %s from backup directory %s because it is listed as a dependency for backup %s.

Severity: ERROR

Message: Backup directory %s does not exist and an error occurred while attempting to create it: %s.

Severity: ERROR

Message: The backup directory path %s exists but does not reference a directory.

Severity: ERROR

Message: An error occurred while trying to remove saved backup descriptor file %s: %s. The new backup descriptor has been written to %s but will not be used until it is manually renamed to %s.

Severity: ERROR

Message: An error occurred while trying to rename the current backup descriptor file %s to %s: %s. The new backup descriptor has been written to %s but will not be used until it is manually renamed to %s.

Severity: ERROR

Message: An error occurred while trying to rename the new backup descriptor file %s to %s: %s. The new backup descriptor will not be used until it is manually renamed.

Severity: ERROR

Message: No backup directory descriptor file was found at %s.

Severity: ERROR

Message: The backup descriptor file %s is invalid because the first line should have contained the DN of the backend configuration entry but was blank.

Severity: ERROR

Message: The backup descriptor file %s is invalid because the first line of the file was "%s", but the DN of the backend configuration entry was expected.

Severity: ERROR

Message: An error occurred while trying to decode the value "%s" read from the first line of %s as the DN of the backend configuration entry: %s.

Severity: ERROR

Message: The attempt to obtain a shared lock on file %s was rejected because an exclusive lock was already held on that file.

Severity: ERROR

Message: The attempt to obtain a shared lock on file %s was rejected because the attempt to create the lock file failed: %s.

Severity: ERROR

Message: The attempt to obtain a shared lock on file %s was rejected because the attempt to open the lock file failed: %s.

Severity: ERROR

Message: The attempt to obtain a shared lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s.

Severity: ERROR

Message: The shared lock requested for file %s was not granted, which indicates that another process already holds an exclusive lock on that file.

Severity: ERROR

Message: The attempt to obtain an exclusive lock on file %s was rejected because an exclusive lock was already held on that file.

Severity: ERROR

Message: The attempt to obtain an exclusive lock on file %s was rejected because a shared lock was already held on that file.

Severity: ERROR

Message: The attempt to obtain an exclusive lock on file %s was rejected because the attempt to create the lock file failed: %s.

Severity: ERROR

Message: The attempt to obtain an exclusive lock on file %s was rejected because the attempt to open the lock file failed: %s.

Severity: ERROR

Message: The attempt to obtain an exclusive lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s.

Severity: ERROR

Message: The exclusive lock requested for file %s was not granted, which indicates that another process already holds a shared or exclusive lock on that file.

Severity: ERROR

Message: The attempt to release the exclusive lock held on %s failed: %s.

Severity: ERROR

Message: The attempt to release the shared lock held on %s failed: %s.

Severity: ERROR

Message: The attempt to release the lock held on %s failed because no record of a lock on that file was found.

Severity: ERROR

Message: The Directory Server could not acquire an exclusive lock on file %s: %s. This generally means that another instance of this server is already running.

Severity: ERROR

Message: Entry %s cannot be modified because the modification attempted to update attribute %s which is defined as NO-USER-MODIFICATION in the server schema.

Severity: ERROR

Message: Entry %s cannot be added because it includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema.

Severity: ERROR

Message: Entry %s cannot be renamed because the current DN includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema and the deleteOldRDN flag was set in the modify DN request.

Severity: ERROR

Message: Entry %s cannot be renamed because the new RDN includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema, and the target value for that attribute is not already included in the entry.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because a pre-operation plugin modified the entry in a way that caused it to violate the server schema: %s.

Severity: ERROR

Message: Entry %s cannot be modified because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR

Message: Entry %s cannot be modified because the request contained an LDAP assertion control, but an error occurred while attempting to compare the target entry against the filter contained in the control: %s.

Severity: ERROR

Message: Entry %s cannot be modified because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR

Message: Entry %s cannot be removed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR

Message: Entry %s cannot be removed because the request contained an LDAP assertion control, but an error occurred while attempting to compare the target entry against the filter contained in the control: %s.

Severity: ERROR

Message: Entry %s cannot be removed because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR

Message: Entry %s cannot be renamed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR

Message: Entry %s cannot be renamed because the request contained an LDAP assertion control, but an error occurred while attempting to compare the target entry against the filter contained in the control: %s.

Severity: ERROR

Message: Entry %s cannot be renamed because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR

Message: Entry %s cannot be added because the request contained an LDAP assertion control and the associated filter did not match the contents of the provided entry.

Severity: ERROR

Message: Entry %s cannot be added because the request contained an LDAP assertion control, but an error occurred while attempting to compare the provided entry against the filter contained in the control: %s.

Severity: ERROR

Message: Entry %s cannot be added because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR

Message: The search request cannot be processed because it contains an LDAP assertion control and an error occurred while trying to retrieve the base entry to compare it against the assertion filter: %s.

Severity: ERROR

Message: The search request cannot be processed because it contains an LDAP assertion control but the search base entry does not exist.

Severity: ERROR

Message: The search request cannot be processed because it contains an LDAP assertion control and the assertion filter did not match the contents of the base entry.

Severity: ERROR

Message: The search request cannot be processed because it contains an LDAP assertion control, but an error occurred while attempting to compare the base entry against the assertion filter: %s.

Severity: ERROR

Message: The search request cannot be processed because it contains a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR

Message: Cannot perform the compare operation on entry %s because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR

Message: Cannot perform the compare operation on entry %s because the request contained an LDAP assertion control, but an error occurred while attempting to compare the target entry against the filter contained in that control: %s.

Severity: ERROR

Message: Cannot perform the compare operation on entry %s because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR

Message: Entry %s cannot be added because it is missing attribute %s that is contained in the entry's RDN. All attributes used in the RDN must also be provided in the attribute list for the entry.

Severity: ERROR

Message: Unable to process the bind request because it contained a control with OID %s that was marked critical but this control is not supported for the bind operation.

Severity: ERROR

Message: The entry %s cannot be added because an entry with that name already exists.

Severity: ERROR

Message: An error occurred during preoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during postoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during preoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during postoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during preoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during postoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during preoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during postoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during conflict resolution synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during conflict resolution synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during conflict resolution synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: An error occurred during conflict resolution synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

Severity: ERROR

Message: Unable to add entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR

Message: Unable to add entry %s because the backend that should hold that entry is configured in read-only mode.

Severity: ERROR

Message: Unable to delete entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR

Message: Unable to delete entry %s because the backend that holds that entry is configured in read-only mode.

Severity: ERROR

Message: Unable to modify entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR

Message: Unable to modify entry %s because the backend that holds that entry is configured in read-only mode.

Severity: ERROR

Message: Unable to rename entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR

Message: Unable to rename entry %s because the backend that holds that entry is configured in read-only mode.

Severity: ERROR

Message: Unable to process the simple bind request because it contained a bind DN but no password, which is forbidden by the server configuration.

Severity: ERROR

Message: The password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" is not defined in the server schema.

Severity: ERROR

Message: The password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" has a syntax OID of %s. The password attribute must have a syntax OID of either 1.3.6.1.4.1.26027.1.3.1 (for the user password syntax) or 1.3.6.1.4.1.4203.1.1.2 (for the authentication password syntax).

Severity: ERROR

Message: An error occurred while attempting to determine the value for attribute ds-cfg-require-change-by-time in configuration entry %s: %s.

Severity: ERROR

Message: The password policy definition contained in configuration entry "%s" is invalid because the specified last login time format "%s" is not a valid format string The last login time format string should conform to the syntax described in the API documentation for the <CODE>java.text.SimpleDateFormat</CODE> class.

Severity: ERROR

Message: The password policy definition contained in configuration entry "%s" is invalid because the specified previous last login time format "%s" is not a valid format string The previous last login time format strings should conform to the syntax described in the API documentation for the <CODE>java.text.SimpleDateFormat</CODE> class.

Severity: ERROR

Message: Attribute options are not allowed for the password attribute %s.

Severity: ERROR

Message: Only a single value may be provided for the password attribute %s.

Severity: ERROR

Message: Pre-encoded passwords are not allowed for the password attribute %s.

Severity: ERROR

Message: The password value for attribute %s was found to be unacceptable: %s.

Severity: ERROR

Message: The password policy defined in configuration entry %s is configured to always send at least one warning notification before the password is expired, but no warning interval has been set. If configuration attribute ds-cfg-expire-passwords-without-warning is set to "false", then configuration attribute ds-cfg-password-expiration-warning-interval must have a positive value.

Severity: ERROR

Message: A bind operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the bind processing has completed.

Severity: ERROR

Message: %s must change their password before it will be allowed to request any other operations.

Severity: ERROR

Message: An error occurred while attempting to decode the ds-pwp-password-policy-dn value "%s" in user entry "%s" as a DN: %s.

Severity: ERROR

Message: User entry %s is configured to use a password policy subentry of %s but no such password policy has been defined in the server configuration.

Severity: ERROR

Message: An error occurred while attempting to decode value "%s" for attribute %s in user entry %s in accordance with the generalized time format: %s.

Severity: ERROR

Message: Unable to decode value "%s" for attribute %s in user entry %s as a Boolean value.

Severity: ERROR

Message: The entry %s cannot be added due to insufficient access rights.

Severity: ERROR

Message: The user cannot bind due to insufficient access rights.

Severity: ERROR

Message: The entry %s cannot be compared due to insufficient access rights.

Severity: ERROR

Message: The entry %s cannot be deleted due to insufficient access rights.

Severity: ERROR

Message: The extended operation %s cannot be performed due to insufficient access rights.

Severity: ERROR

Message: The entry %s cannot be renamed due to insufficient access rights.

Severity: ERROR

Message: The entry %s cannot be modified due to insufficient access rights.

Severity: ERROR

Message: The entry %s cannot be searched due to insufficient access rights.

Severity: ERROR

Message: Rejecting a simple bind request because the password policy requires secure authentication.

Severity: ERROR

Message: Rejecting a bind request because the account has been administratively disabled.

Severity: ERROR

Message: Rejecting a bind request because the account has been locked due to too many failed authentication attempts.

Severity: ERROR

Message: Rejecting a bind request because the account has been locked after the user's password was not changed in a timely manner after an administrative reset.

Severity: ERROR

Message: Rejecting a bind request because the account has been locked after remaining idle for too long.

Severity: ERROR

Message: Rejecting a bind request because that user's password is expired.

Severity: ERROR

Message: An error occurred while attempting to update password policy state information for user %s: %s.

Severity: ERROR

Message: Rejecting a SASL %s bind request for user %s because the password policy requires secure authentication.

Severity: ERROR

Message: The alternate root bind DN "%s" is already registered with the Directory Server for actual root entry DN "%s".

Severity: ERROR

Message: Rejecting a bind request because the account has expired.

Severity: ERROR

Message: Attributes used to hold user passwords are not allowed to have any attribute options.

Severity: ERROR

Message: Users are not allowed to change their own passwords.

Severity: ERROR

Message: Password changes must be performed over a secure authentication channel.

Severity: ERROR

Message: The password cannot be changed because it has not been long enough since the last password change.

Severity: ERROR

Message: Multiple password values are not allowed in user entries.

Severity: ERROR

Message: User passwords may not be provided in pre-encoded form.

Severity: ERROR

Message: Invalid modification type %s attempted on password attribute %s.

Severity: ERROR

Message: The user entry does not have any existing passwords to remove.

Severity: ERROR

Message: The provided user password does not match any password in the user's entry.

Severity: ERROR

Message: The password policy requires that user password changes include the current password in the request.

Severity: ERROR

Message: The password change would result in multiple password values in the user entry, which is not allowed.

Severity: ERROR

Message: The provided password value was rejected by a password validator: %s.

Severity: ERROR

Message: %s must change their password before it will be allowed to perform any other operations.

Severity: ERROR

Message: The account has been locked as a result of too many failed authentication attempts (time to unlock: %s).

Severity: ERROR

Message: The account has been locked as a result of too many failed authentication attempts. It may only be unlocked by an administrator.

Severity: ERROR

Message: The specified password value already exists in the user entry.

Severity: ERROR

Message: Unable to add one or more values to attribute %s because at least one of the values already exists.

Severity: ERROR

Message: Unable to remove one or more values from attribute %s because at least one of the attributes does not exist in the entry.

Severity: ERROR

Message: The increment operation is not supported for the objectClass attribute.

Severity: ERROR

Message: Unknown modification type %s requested.

Severity: ERROR

Message: Unable to increment the value of attribute %s because the provided modification did not have exactly one value to use as the increment.

Severity: ERROR

Message: Unable to increment the value of attribute %s because either the current value or the increment could not be parsed as an integer.

Severity: ERROR

Message: Entry %s cannot be updated because the request did not contain any modifications.

Severity: ERROR

Message: Unable to increment the value of attribute %s because that attribute does not exist in the entry.

Severity: ERROR

Message: Unable to process the request for extended operation %s because it contained an unsupported critical control with OID %s.

Severity: ERROR

Message: Unable to register backend %s with the Directory Server because another backend with the same backend ID is already registered.

Severity: ERROR

Message: Unable to register base DN %s with the Directory Server for backend %s because that base DN is already registered for backend %s.

Severity: ERROR

Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is within the same hierarchical path.

Severity: ERROR

Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is not subordinate to the same base DN in the parent backend.

Severity: ERROR

Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains one or more other base DNs that are subordinate to backend %s but the new base DN is not.

Severity: ERROR

Message: Unable to de-register base DN %s with the Directory Server because that base DN is not registered for any active backend.

Severity: ERROR

Message: Unable to update the schema element with definition "%s" because a circular reference was identified when attempting to rebuild other schema elements dependent upon it.

Severity: ERROR

Message: Rejecting the requested operation because the connection has not been authenticated.

Severity: ERROR

Message: Entry %s cannot be modified because the modification attempted to set one or more new values for attribute %s which is marked OBSOLETE in the server schema.

Severity: ERROR

Message: Object class %s added to entry %s is marked OBSOLETE in the server schema.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because the new RDN includes attribute type %s which is declared OBSOLETE in the server schema.

Severity: ERROR

Message: Entry %s is invalid according to the server schema because there is no DIT structure rule that applies to that entry, but there is a DIT structure rule for the parent entry %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to perform DIT structure rule processing for the parent of entry %s: %s.

Severity: ERROR

Message: You do not have sufficient privileges to reset user passwords.

Severity: ERROR

Message: You do not have sufficient privileges to access the server configuration.

Severity: ERROR

Message: You do not have sufficient privileges to add entries that include privileges.

Severity: ERROR

Message: You do not have sufficient privileges to modify the set of privileges contained in an entry.

Severity: ERROR

Message: You do not have sufficient privileges to use the proxied authorization control.

Severity: ERROR

Message: Entry %s violates the Directory Server schema configuration because it includes attribute %s without any values.

Severity: ERROR

Message: OpenDJ is configured to run as a Windows service and it cannot run in no-detach mode.

Severity: ERROR

Message: Unable to decode an entry because it had an unsupported entry version byte value of %s.

Severity: ERROR

Message: Unable to decode an entry because an unexpected exception was caught during processing: %s.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the NOT filter between positions %d and %d did not contain exactly one filter component.

Severity: ERROR

Message: The request control with Object Identifier (OID) "%s" cannot be used due to insufficient access rights.

Severity: ERROR

Message: The connection handler %s is trying to use the listener %s which is already in use by another connection handler.

Severity: ERROR

Message: No enabled connection handler available.

Severity: ERROR

Message: Could not start connection handlers.

Severity: ERROR

Message: Unable to process the non-root bind because the server is in lockdown mode.

Severity: ERROR

Message: Unable to decode the provided attribute because it used an undefined attribute description token %s.

Severity: ERROR

Message: Unable to decode the provided object class set because it used an undefined token %s.

Severity: ERROR

Message: Unable to write the updated compressed schema token data: %s.

Severity: ERROR

Message: Unable to decode the provided entry encode configuration element because it has an invalid length.

Severity: ERROR

Message: Unable to create an extensible match search filter using the provided information because it did not contain either an attribute type or a matching rule ID. At least one of these must be provided.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the extensible match component starting at position %d did not contain either an attribute description or a matching rule ID. At least one of these must be provided.

Severity: ERROR

Message: The provided search filter "%s" could not be decoded because the extensible match component starting at position %d referenced an unknown matching rule %s.

Severity: ERROR

Message: Rejecting a bind request for user %s because either the entire server or the user's backend has a writability mode of 'disabled' and password policy state updates would not be allowed.

Severity: ERROR

Message: The provided new password was found in the password history for the user.

Severity: ERROR

Message: The password policy configuration entry "%s" is invalid because if a maximum password age is configured, then the password expiration warning interval must be shorter than the maximum password age.

Severity: ERROR

Message: The password policy configuration entry "%s" is invalid because if both a minimum password age and a maximum password age are configured, then the sum of the minimum password age and the password expiration warning interval must be shorter than the maximum password age.

Severity: ERROR

Message: An error occurred while attempting to disconnect client connection %d: %s.

Severity: ERROR

Message: An unexpected error occurred in the idle time limit thread: %s.

Severity: ERROR

Message: The Directory Server is currently running. Environment configuration changes are not allowed with the server running.

Severity: ERROR

Message: The specified server root directory '%s' is invalid. The specified path must exist and must be a directory.

Severity: ERROR

Message: The specified config file path '%s' is invalid. The specified path must exist and must be a file.

Severity: ERROR

Message: The specified config handler class '%s' is invalid. The specified class must be a subclass of the org.opends.server.api.ConfigHandler superclass.

Severity: ERROR

Message: The specified schema configuration directory '%s' is invalid. The specified path must exist and must be a directory.

Severity: ERROR

Message: The specified lock directory '%s' is invalid. The specified path must exist and must be a directory.

Severity: ERROR

Message: The Directory Server is currently running. The environment configuration can not be altered while the server is online.

Severity: ERROR

Message: An error occurred while attempting to initialize a SSL context for server to server communication: %s.

Severity: ERROR

Message: The ADS trust store backend %s is not enabled.

Severity: ERROR

Message: The backend %s is not a trust store backend.

Severity: ERROR

Message: An error occurred in the trust store synchronization thread: %s.

Severity: ERROR

Message: The password storage scheme defined in configuration entry %s does not support the auth password syntax, which is used by password attribute %s.

Severity: ERROR

Message: Password policy configuration entry %s references deprecated password storage scheme DN %s which does not support the auth password syntax.

Severity: ERROR

Message: CryptoManager cannot get the requested digest %s: %s.

Severity: ERROR

Message: CryptoManager cannot get the requested MAC engine %s: %s.

Severity: ERROR

Message: CryptoManager cannot get the requested encryption cipher %s: %s.

Severity: ERROR

Message: CryptoManager cannot get the preferred key wrapping cipher: %s.

Severity: ERROR

Message: CryptoManager failed to add entry "%s" to initiate instance key generation.

Severity: ERROR

Message: CryptoManager failed to retrieve entry "%s" (the instance-key-pair public-key-certificate): %s.

Severity: ERROR

Message: CryptoManager failed to compute an instance key identifier: %s.

Severity: ERROR

Message: Failed to add entry "%s".

Severity: ERROR

Message: CryptoManager failed to publish the instance-key-pair public-key-certificate entry in ADS: %s.

Severity: ERROR

Message: CryptoManager failed to retrieve the collection of instance-key-pair public-key-certificates from ADS container "%s": %s.

Severity: ERROR

Message: CryptoManager failed to encode symmetric key attribute value: %s.

Severity: ERROR

Message: CryptoManager symmetric key attribute value "%s" syntax is invalid: incorrect number of fields.

Severity: ERROR

Message: CryptoManager symmetric key attribute value "%s" syntax is invalid. Parsing failed in field "%s" at offset %d.

Severity: ERROR

Message: CryptoManager failed to retrieve the instance-key-pair private-key: %s.

Severity: ERROR

Message: CryptoManager failed to decipher the wrapped secret-key value: %s.

Severity: ERROR

Message: CryptoManager cannot find the public-key-certificate (identifier "%s") requested for symmetric key re-encoding.

Severity: ERROR

Message: CryptoManager failed to decode the key entry identifier "%s": %s.

Severity: ERROR

Message: CrytpoManager passed invalid MAC algorithm "%s": %s.

Severity: ERROR

Message: CryptoManager failed to initialize MAC engine: %s.

Severity: ERROR

Message: CryptoManager passed invalid Cipher transformation "%s": %s.

Severity: ERROR

Message: CryptoManager cannot initialize Cipher: %s.

Severity: ERROR

Message: CryptoManager failed to write the stream prologue: %s.

Severity: ERROR

Message: CryptoManager failed to decrypt the supplied data because it could not read the symmetric key identifier in the data prologue: %s.

Severity: ERROR

Message: CryptoManager failed to decrypt the supplied data because the symmetric key identifier in the data prologue does not match any known key entries.

Severity: ERROR

Message: CryptoManager failed to decrypt the supplied data because it could not read the cipher initialization vector in the data prologue.

Severity: ERROR

Message: CryptoManager failed to decrypt the supplied data because there was an error reading from the input stream: %s.

Severity: ERROR

Message: CryptoManager failed to import the symmetric key entry "%s" because it could not obtain a symmetric key attribute value that can be decoded by this instance.

Severity: ERROR

Message: CryptoManager detected a field mismatch between the key entry to be imported and an entry in the key cache that share the key identifier "%s".

Severity: ERROR

Message: CryptoManager failed to import the symmetric key entry "%s": %s.

Severity: ERROR

Message: CryptoManager failed to import the symmetric key entry "%s" because it could not add a symmetric key attribute value that can be decoded by this instance.

Severity: ERROR

Message: CryptoManager failed to instantiate a KeyGenerator for algorithm "%s": %s.

Severity: ERROR

Message: CryptoManager failed to add locally produced symmetric key entry "%s": %s.

Severity: ERROR

Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

Severity: ERROR

Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

Severity: ERROR

Message: CryptoManager failed to decrypt the supplied data because it could not read the version number in the data prologue: %s.

Severity: ERROR

Message: CryptoManager failed to decrypt the supplied data because the version "%d" in the data prologue is unknown.

Severity: ERROR

Message: The provided entry %s cannot be added because its suffix is not defined as one of the suffixes within the Directory Server.

Severity: ERROR

Message: Start TLS extended operations cannot be canceled.

Severity: ERROR

Message: Cancel extended operations can not be canceled.

Severity: ERROR

Message: The modify DN operation for entry %s cannot be performed because the new superior entry %s is equal to or a subordinate of the entry to be moved.

Severity: ERROR

Message: Entry %s can not be added because BER encoding of %s attribute is not supported.

Severity: ERROR

Message: The CryptoManager entry "%s" (the instance-key-pair public-key-certificate) does not contain a public-key certificate.

Severity: ERROR

Message: In no-detach mode, the 'timeout' option cannot be used.

Severity: ERROR

Message: The entry %s does not contain the pwdPolicy objectclass, which is required for Directory Server password policy.

Severity: ERROR

Message: Unable to decode the provided string "%s" as a relative distinguished name because it does not contain a value for attribute type %s.

Severity: ERROR

Message: CryptoManager failed to initialize because the specified cipher key length "%d" is beyond the allowed cryptography strength "%d" in jurisdiction policy files.

Severity: ERROR

Message: Failed to update free disk space for directory %s: %s.

Severity: ERROR

Message: The directory server is not accepting a new persistent search request because the server has already reached its limit.

Severity: ERROR

Message: This operation involves LDAP subentries which you do not have sufficient privileges to administer.

Severity: ERROR

Message: When attempting to modify entry %s, one value for attribute %s was found to be invalid according to the associated syntax: %s.

Severity: ERROR

Message: When attempting to modify entry %s to replace the set of values for attribute %s, one value was found to be invalid according to the associated syntax: %s.

Severity: ERROR

Message: The password policy definition contained in configuration entry "%s" is invalid because the password validator "%s" specified in attribute "%s" cannot be found.

Severity: ERROR

Message: The password could not be validated because of misconfiguration. Please contact the administrator.

Severity: ERROR

Message: The password for user %s could not be validated because the password policy subentry %s is referring to an unknown password validator (%s). Please make sure the password policy subentry only refers to validators that exist on all replicas.

Severity: ERROR

Message: Could not get filesystem for directory %s: %s.

Severity: ERROR

Message: The free space (%s) on the disk containing directory "%s" is between low and full threshold for the following subsystems: %s. Write operations are only permitted by a user with the BYPASS_LOCKDOWN privilege until the free space rises above the threshold. Replication updates are still allowed.

Severity: ERROR

Message: The free space (%s) on the disk containing directory "%s" is below full threshold for the following subsystems: %s. Write operations to the backend, replication updates included, will fail until the free space rises above the threshold.

Severity: ERROR

Message: A StartTLS operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the StartTLS processing has completed.

Severity: ERROR

Message: A SASL bind operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the SASL bind processing has completed.

Severity: ERROR

Message: Cannot properly use SHA-1 using the java provider. Verify java.security is properly configured.

Severity: ERROR

Message: Cannot complete initialization of server's backends because the root and administrative backends have not been initialized yet.

Severity: ERROR

Message: While adding Service Discovery Mechanism '%s' an error occurred : %s.

Severity: ERROR

Message: Registering Service Discovery Manager's listener failed : %s.

Severity: ERROR

Message: Discovery mechanism '%s' initialization failed : %s.

Severity: ERROR

Message: Discovery mechanism '%s' could not process notification of a configuration change : %s.

Severity: ERROR

Message: Error occurred while creating an SSL context for service discovery mechanism '%s' : %s.

Severity: ERROR

Message: Could not retrieve the list of replicas from replication server '%s' for replication server group '%s'. Exception : %s.

Severity: ERROR

Message: Could not retrieve auto-configuration data from directory server '%s' for replication server group '%s'. Exception : %s".

Severity: ERROR

Message: Service discovery mechanism '%s' failed to refresh the partition information. Exception : %s",.

Severity: ERROR

Message: Service discovery mechanism '%s' failed to refresh the connection options. Exception : %s",.

Severity: ERROR

Message: The host and port '%s' is invalid because it does not contain a host name. Valid values should have the format HOST:PORT.

Severity: ERROR

Message: The host and port '%s' is invalid because it does not contain a valid port number. Valid values should have the format HOST:PORT.

Severity: ERROR

Message: The host and port '%s' is invalid because it contains a malformed IPv6 address. Valid values should have the format [IPv6 address]:PORT.

Severity: ERROR

Message: Java property %s which is specified in attribute ds-cfg-bind-password-property of configuration entry %s should contain the password for periodically reading replication server configurations, but this property is not set.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-bind-password-environment-variable of configuration entry %s should contain the password for periodically reading replication server configurations, but this property is not set.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-bind-password-file of configuration entry %s should contain the the password for periodically reading replication server configurations, but this file does not exist.

Severity: ERROR

Message: An error occurred while trying to read the password for periodically reading replication server configurations from file %s specified in configuration attribute ds-cfg-bind-password-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-bind-password-file of configuration entry %s should contain the password for periodically reading replication server configurations, but this file is empty.

Severity: ERROR

Message: "%s" (low=%s, full=%s).

Severity: ERROR

Message: You do not have sufficient privileges to read directory server monitoring information.

Severity: ERROR

Message: An attempt was made to configure the root DSE backend without providing a configuration entry. This is not allowed.

Severity: ERROR

Message: Unwilling to update entry "%s" because modify operations are not supported in the root DSE backend. If you wish to alter the contents of the root DSE itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

Severity: ERROR

Message: Unwilling to perform a search (connection ID %d, operation ID %d) with a base DN of "%s" in the root DSE backend. The base DN for searches in this backend must be the DN of the root DSE itself.

Severity: ERROR

Message: An unexpected failure occurred while trying to process a search operation (connection ID %d, operation ID %d) in the root DSE backend: %s.

Severity: ERROR

Message: Unable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %s.

Severity: ERROR

Message: An unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %s.

Severity: ERROR

Message: An unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %s.

Severity: ERROR

Message: The root DSE backend does not provide a facility for backup and restore operations. The contents of the root DSE should be backed up as part of the Directory Server configuration.

Severity: ERROR

Message: An attempt was made to configure the monitor backend without providing a configuration entry. This is not allowed, and no monitor information will be available over protocol.

Severity: ERROR

Message: Unwilling to add entry "%s" because add operations are not supported in the "%s" backend.

Severity: ERROR

Message: Unwilling to remove entry "%s" because delete operations are not supported in the "%s" backend.

Severity: ERROR

Message: Unwilling to update entry "%s" because modify operations are not supported in the monitor backend. If you wish to alter the contents of the base monitor entry itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

Severity: ERROR

Message: Unwilling to rename entry "%s" because modify DN operations are not supported in the "%s" backend.

Severity: ERROR

Message: An error occurred while attempting to export the base monitor entry: %s.

Severity: ERROR

Message: An error occurred while attempting to export the monitor entry for monitor provider %s: %s.

Severity: ERROR

Message: The "%s" backend does not support LDIF import operations.

Severity: ERROR

Message: Unable to retrieve the requested entry from the "%s" backend because the provided DN was null.

Severity: ERROR

Message: Unable to initialize the "%s" backend because an error occurred while attempting to decode the base DN for this backend: %s.

Severity: ERROR

Message: Unable to retrieve the requested entry %s from the monitor backend because the DN is not below the monitor base of %s.

Severity: ERROR

Message: An attempt was made to configure the schema backend without providing a configuration entry. This is not allowed, and no schema information will be available over protocol.

Severity: ERROR

Message: An error occurred while attempting to export the base schema entry: %s.

Severity: ERROR

Message: Unable to retrieve the requested entry %s from the schema backend because the DN is equal to one of the schema entry DNs.

Severity: ERROR

Message: An unexpected error occurred while trying to open the LDIF writer for the schema backend: %s.

Severity: ERROR

Message: The Directory Server was unable to obtain a lock on entry %s after multiple attempts. This could mean that the entry is already locked by a long-running operation or that the entry has previously been locked but was not properly unlocked.

Severity: ERROR

Message: The task defined in entry %s is invalid because it has an invalid state %s.

Severity: ERROR

Message: An error occurred while trying to parse the scheduled start time value %s from task entry %s.

Severity: ERROR

Message: An error occurred while trying to parse the actual start time value %s from task entry %s.

Severity: ERROR

Message: An error occurred while trying to parse the completion time value %s from task entry %s.

Severity: ERROR

Message: Task entry %s is missing required attribute %s.

Severity: ERROR

Message: There are multiple instances of attribute %s in task entry %s.

Severity: ERROR

Message: There are no values for attribute %s in task entry %s.

Severity: ERROR

Message: There are multiple values for attribute %s in task entry %s.

Severity: ERROR

Message: An error occurred while executing the task defined in entry %s: %s.

Severity: ERROR

Message: The provided recurring task entry does not contain attribute %s which is needed to hold the recurring task ID.

Severity: ERROR

Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold the recurring task ID, but only a single instance is allowed.

Severity: ERROR

Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task ID.

Severity: ERROR

Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the recurring task ID, but only a single value is allowed.

Severity: ERROR

Message: The provided recurring task entry does not contain attribute %s which is needed to specify recurring task schedule.

Severity: ERROR

Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold recurring task schedule, but only a single instance is allowed.

Severity: ERROR

Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task schedule.

Severity: ERROR

Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify recurring task schedule, but only a single value is allowed.

Severity: ERROR

Message: An error occurred while attempting to load class %s specified in attribute %s of the provided recurring task entry: %s. Does this class exist in the Directory Server classpath?.

Severity: ERROR

Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

Severity: ERROR

Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

Severity: ERROR

Message: The specified task data backing file %s already exists and the Directory Server will not attempt to overwrite it. Please delete or rename the existing file before attempting to use that path for the new backing file, or choose a new path.

Severity: ERROR

Message: The specified path %s for the new task data backing file appears to be an invalid path. Please choose a new path for the task data backing file.

Severity: ERROR

Message: The parent directory %s for the new task data backing file %s does not exist. Please create this directory before attempting to use this path for the new backing file or choose a new path.

Severity: ERROR

Message: The parent directory %s for the new task data backing file %s exists but is not a directory. Please choose a new path for the task data backing file.

Severity: ERROR

Message: An error occurred while attempting to determine the new path to the task data backing file: %s.

Severity: ERROR

Message: New entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasks.

Severity: ERROR

Message: Unable to add recurring task %s to the task scheduler because another recurring task already exists with the same ID.

Severity: ERROR

Message: Unable to schedule task %s because another task already exists with the same ID.

Severity: ERROR

Message: An error occurred while attempting to schedule the next iteration of recurring task %s: %s.

Severity: ERROR

Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is not a fatal error, so the task scheduler will attempt to continue parsing the file and schedule any additional tasks that it contains.

Severity: ERROR

Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is an unrecoverable error, and parsing cannot continue.

Severity: ERROR

Message: Entry %s read from the tasks backing file is invalid because it has no parent and does not match the task root DN of %s.

Severity: ERROR

Message: An error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %s.

Severity: ERROR

Message: An error occurred while attempting to parse entry %s as a task and add it to the scheduler: %s.

Severity: ERROR

Message: Entry %s read from the tasks backing file %s has a DN which is not valid for a task or recurring task definition and will be ignored.

Severity: ERROR

Message: An error occurred while attempting to read from the tasks data backing file %s: %s.

Severity: ERROR

Message: An error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %s.

Severity: ERROR

Message: The provided task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logic.

Severity: ERROR

Message: The provided task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowed.

Severity: ERROR

Message: The provided task entry does not contain any values for the %s attribute, which is used to specify the fully-qualified name of the class providing the task logic.

Severity: ERROR

Message: The provided task entry contains multiple values for the %s attribute, which is used to specify the task class name, but only a single value is allowed.

Severity: ERROR

Message: An error occurred while attempting to load class %s specified in attribute %s of the provided task entry: %s. Does this class exist in the Directory Server classpath?.

Severity: ERROR

Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

Severity: ERROR

Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

Severity: ERROR

Message: An error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not work as expected.

Severity: ERROR

Message: An error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lost.

Severity: ERROR

Message: Unable to remove pending task %s because no such task exists.

Severity: ERROR

Message: Unable to remove pending task %s because the task is no longer pending.

Severity: ERROR

Message: Unable to remove completed task %s because no such task exists in the list of completed tasks.

Severity: ERROR

Message: Unable to remove entry %s from the task backend because its DN is either not appropriate for that backend or it is not below the scheduled or recurring tasks base entry.

Severity: ERROR

Message: Unable to remove entry %s from the task backend because there is no scheduled task associated with that entry DN.

Severity: ERROR

Message: Unable to delete entry %s from the task backend because the associated task is currently running.

Severity: ERROR

Message: Unable to remove entry %s from the task backend because there is no recurring task associated with that entry DN.

Severity: ERROR

Message: Unable to process the search operation in the task backend because the provided base DN %s is not valid for entries in the task backend.

Severity: ERROR

Message: Unable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %s.

Severity: ERROR

Message: Unable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %s.

Severity: ERROR

Message: Unable to initialize the "%s" backend because the provided configuration entry is null.

Severity: ERROR

Message: Requested entry %s does not exist in the backup backend.

Severity: ERROR

Message: Unable to retrieve entry %s from the backup backend because the requested DN is one level below the base DN but does not specify a backup directory.

Severity: ERROR

Message: Unable to retrieve entry %s from the backup backend because the requested backup directory is invalid: %s.

Severity: ERROR

Message: An error occurred while attempting to examine the requested backup directory: %s.

Severity: ERROR

Message: Unable to retrieve entry %s from the backup backend because the requested DN is two levels below the base DN but does not specify a backup ID.

Severity: ERROR

Message: Unable to retrieve entry %s from the backup backend because it does not have a parent.

Severity: ERROR

Message: Unable to retrieve entry %s from the backup backend because the DN does not contain the backup directory in which the requested backup should reside.

Severity: ERROR

Message: Backup %s does not exist in backup directory %s.

Severity: ERROR

Message: Unwilling to update entry "%s" because modify operations are not supported in the "%s" backend.

Severity: ERROR

Message: The requested entry %s does not exist in the backup backend.

Severity: ERROR

Message: Exactly one base DN must be provided for use with the memory-based backend.

Severity: ERROR

Message: Entry %s already exists in the memory-based backend.

Severity: ERROR

Message: Entry %s does not belong in the memory-based backend.

Severity: ERROR

Message: Unable to add entry %s because its parent entry %s does not exist in the memory-based backend.

Severity: ERROR

Message: Entry %s does not exist in the "%s" backend.

Severity: ERROR

Message: Cannot delete entry %s because it has one or more subordinate entries.

Severity: ERROR

Message: Unable to create an LDIF writer: %s.

Severity: ERROR

Message: Cannot write entry %s to LDIF: %s.

Severity: ERROR

Message: Unable to create an LDIF reader: %s.

Severity: ERROR

Message: An unrecoverable error occurred while reading from LDIF: %s.

Severity: ERROR

Message: An unexpected error occurred while processing the import: %s.

Severity: ERROR

Message: The memory-based backend does not support backup or restore operations.

Severity: ERROR

Message: Cannot rename entry %s because it has one or more subordinate entries.

Severity: ERROR

Message: Cannot rename entry %s because the target entry is in a different backend.

Severity: ERROR

Message: Cannot rename entry %s because the new parent entry %s doesn't exist.

Severity: ERROR

Message: An error occurred while attempting to register the base DNs %s in the Directory Server: %s.

Severity: ERROR

Message: The schema backend does not support the %s modification type.

Severity: ERROR

Message: The schema backend does not support the modification of the %s attribute type. Only attribute types, object classes, ldap syntaxes, name forms, DIT content rules, DIT structure rules, and matching rule uses may be modified.

Severity: ERROR

Message: An error occurred while attempting to decode the object class "%s": %s.

Severity: ERROR

Message: Unable to add objectclass %s because its superior class of %s is not defined in the server schema.

Severity: ERROR

Message: Unable to add objectclass %s because it requires attribute %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add objectclass %s because it allows attribute %s which is not defined in the server schema.

Severity: ERROR

Message: An error occurred while attempting to write the updated schema: %s.

Severity: ERROR

Message: An error occurred while attempting to decode the name form "%s": %s.

Severity: ERROR

Message: An error occurred while attempting to decode the DIT content rule "%s": %s.

Severity: ERROR

Message: An error occurred while attempting to decode the DIT structure rule "%s": %s.

Severity: ERROR

Message: An error occurred while attempting to decode the matching rule use "%s": %s.

Severity: ERROR

Message: The server will not allow removing all values for the %s attribute type in the server schema.

Severity: ERROR

Message: Unable to add attribute type %s because it conflicts with multiple existing attribute types (%s and %s).

Severity: ERROR

Message: Unable to add objectclass %s because it conflicts with multiple existing objectclasses (%s and %s).

Severity: ERROR

Message: Unable to add name form %s because it conflicts with multiple existing name forms (%s and %s).

Severity: ERROR

Message: Unable to add name form %s because it references structural objectclass %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add name form %s because it references required attribute type %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add name form %s because it references optional attribute type %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it conflicts with multiple existing DIT content rules (%s and %s).

Severity: ERROR

Message: Unable to add DIT content rule %s because it references structural objectclass %s which is already associated with another DIT content rule %s.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references structural objectclass %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references auxiliary objectclass %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references required attribute type %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references optional attribute type %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references prohibited attribute type %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add DIT structure rule %s because it conflicts with multiple existing DIT structure rules (%s and %s).

Severity: ERROR

Message: Unable to add DIT structure rule %s because it references name form %s which is already associated with another DIT structure rule %s.

Severity: ERROR

Message: Unable to add DIT structure rule %s because it references name form %s which is not defined in the server schema.

Severity: ERROR

Message: Unable to add matching rule use %s because it conflicts with multiple existing matching rule uses (%s and %s).

Severity: ERROR

Message: Unable to add matching rule use %s because it references matching rule %s which is already associated with another matching rule use %s.

Severity: ERROR

Message: Unable to add matching rule use %s because it references attribute type %s which is not defined in the server schema.

Severity: ERROR

Message: Circular reference detected for attribute type %s in which the superior type chain references the attribute type itself.

Severity: ERROR

Message: Circular reference detected for objectclass %s in which the superior class chain references the objectclass itself.

Severity: ERROR

Message: Circular reference detected for DIT structure rule %s in which the superior rule chain references the DIT structure rule itself.

Severity: ERROR

Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

Severity: ERROR

Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

Severity: ERROR

Message: An error occurred while attempting to write new versions of the server schema files: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

Severity: ERROR

Message: An error occurred while attempting to write new versions of the server schema files: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

Severity: ERROR

Message: Unable to remove attribute type %s from the server schema because no such attribute type is defined.

Severity: ERROR

Message: Unable to remove attribute type %s from the server schema because it is referenced as the superior type for attribute type %s.

Severity: ERROR

Message: Unable to remove attribute type %s from the server schema because it is referenced as a required or optional attribute type in objectclass %s.

Severity: ERROR

Message: Unable to remove attribute type %s from the server schema because it is referenced as a required or optional attribute type in name form %s.

Severity: ERROR

Message: Unable to remove attribute type %s from the server schema because it is referenced as a required, optional, or prohibited attribute type in DIT content rule %s.

Severity: ERROR

Message: Unable to remove attribute type %s from the server schema because it is referenced by matching rule use %s.

Severity: ERROR

Message: Unable to remove objectclass %s from the server schema because no such objectclass is defined.

Severity: ERROR

Message: Unable to remove objectclass %s from the server schema because it is referenced as the superior class for objectclass %s.

Severity: ERROR

Message: Unable to remove objectclass %s from the server schema because it is referenced as the structural class for name form %s.

Severity: ERROR

Message: Unable to remove objectclass %s from the server schema because it is referenced as a structural or auxiliary class for DIT content rule %s.

Severity: ERROR

Message: Unable to remove name form %s from the server schema because no such name form is defined.

Severity: ERROR

Message: Unable to remove name form %s from the server schema because it is referenced by DIT structure rule %s.

Severity: ERROR

Message: Unable to remove DIT content rule %s from the server schema because no such DIT content rule is defined.

Severity: ERROR

Message: Unable to remove DIT structure rule %s from the server schema because no such DIT structure rule is defined.

Severity: ERROR

Message: Unable to remove DIT structure rule %s from the server schema because it is referenced as a superior rule for DIT structure rule %s.

Severity: ERROR

Message: Unable to remove matching rule use %s from the server schema because no such matching rule use is defined.

Severity: ERROR

Message: Unable to add name form %s because it references objectclass %s which is defined in the server schema but is not a structural objectclass.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references structural objectclass %s which is defined in the server schema but is not structural.

Severity: ERROR

Message: Unable to add attribute type %s because the superior type %s is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add attribute type %s because the associated matching rule %s is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add object class %s because the superior class %s is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add object class %s because required attribute %s is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add object class %s because optional attribute %s is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add name form %s because its structural object class %s is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add name form %s because it requires attribute type %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add name form %s because it allows attribute type %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because its structural object class %s is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references auxiliary object class %s which is defined in the server schema but is not an auxiliary class.

Severity: ERROR

Message: Unable to add DIT content rule %s because it requires attribute type %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it allows attribute type %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it prohibits attribute type %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add DIT structure rule %s because its name form %s is marked OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add DIT structure rule %s because it references superior rule %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add matching rule use %s because its matching rule %s is marked OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add matching rule use %s because it references attribute type %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: Unable to add DIT content rule %s because it references auxiliary object class %s which is marked as OBSOLETE in the server schema.

Severity: ERROR

Message: You do not have sufficient privileges to modify the Directory Server schema.

Severity: ERROR

Message: Unable to find a file containing concatenated schema element definitions in order to determine if any schema changes were made with the server offline. The file was expected in the %s directory and should have been named either %s or %s.

Severity: ERROR

Message: An error occurred while attempting to determine whether any schema changes had been made by directly editing the schema files with the server offline: %s.

Severity: ERROR

Message: An error occurred while attempting to write file %s containing a concatenated list of all server schema elements: %s. The server may not be able to accurately identify any schema changes made with the server offline.

Severity: ERROR

Message: The Directory Server is not configured to allow task %s to be invoked.

Severity: ERROR

Message: Requested entry %s does not exist in the trust store backend.

Severity: ERROR

Message: Unable to process entry %s in the trust store backend because the requested DN is one level below the base DN but does not specify a certificate name.

Severity: ERROR

Message: Error while trying to retrieve certificate %s from the trust store file %s: %s.

Severity: ERROR

Message: Indexes are not supported in the "%s" backend.

Severity: ERROR

Message: LDIF import and export operations are not supported in the "%s" backend.

Severity: ERROR

Message: Backup and restore operations are not supported in the "%s" backend.

Severity: ERROR

Message: The trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not exist.

Severity: ERROR

Message: The trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s.

Severity: ERROR

Message: An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-trust-store-file in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to load the trust store contents from file %s: %s.

Severity: ERROR

Message: An error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %s.

Severity: ERROR

Message: The certificate entry %s already exists.

Severity: ERROR

Message: Error while attempting to generate a self-signed certificate %s in the trust store file %s: %s.

Severity: ERROR

Message: Error while trying to add certificate %s to the trust store file %s: %s.

Severity: ERROR

Message: The entry %s could not be added because it does not contain a certificate attribute %s.

Severity: ERROR

Message: The entry %s could not be added because it contains multiple certificate attributes %s.

Severity: ERROR

Message: The entry %s could not be added because it does not contain a value of certificate attribute %s.

Severity: ERROR

Message: The entry %s could not be added because it contains multiple values of certificate attribute %s.

Severity: ERROR

Message: Error while writing certificate %s to a file: %s.

Severity: ERROR

Message: The root container for backend %s has not been initialized preventing this backend from processing the requested operation.

Severity: ERROR

Message: Unable to obtain a write lock on entry %s.

Severity: ERROR

Message: Entry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backend.

Severity: ERROR

Message: Entry %s cannot be modified because it does not represent a valid task in the server.

Severity: ERROR

Message: Entry %s cannot be modified because the assoicated task has completed running. Completed tasks cannot be modified.

Severity: ERROR

Message: Entry %s cannot be modified because the server does not currently support modifying recurring task entries.

Severity: ERROR

Message: The task associated with entry %s is currently running. The only modification allowed for running tasks is to replace the value of the ds-task-state attribute with "cancel".

Severity: ERROR

Message: Error while trying to delete certificate %s from the trust store file %s: %s.

Severity: ERROR

Message: Unable to retrieve entry %s from the trust store backend because the certificate %s does not exist.

Severity: ERROR

Message: The LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNs.

Severity: ERROR

Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s has multiple entries with a DN of %s.

Severity: ERROR

Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s includes entry %s which is not below the base DN defined for that backend.

Severity: ERROR

Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s contains entry %s but its parent entry has not yet been read.

Severity: ERROR

Message: An error occurred while trying to create file %s to write an updated version of the data for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while attempting to rename file %s to %s while writing updated data for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR

Message: Entry %s already exists in the LDIF backend.

Severity: ERROR

Message: The parent for entry %s does not exist.

Severity: ERROR

Message: Entry %s does not exist.

Severity: ERROR

Message: Entry %s has one or more subordinate entries and cannot be deleted until all of its subordinate entries are removed first.

Severity: ERROR

Message: Entry %s does not exist.

Severity: ERROR

Message: Source entry %s does not exist.

Severity: ERROR

Message: Target entry %s already exists.

Severity: ERROR

Message: The new parent DN %s does not exist.

Severity: ERROR

Message: Entry %s specified as the search base DN does not exist.

Severity: ERROR

Message: An error occurred while trying to create the writer for the LDIF export operation: %s.

Severity: ERROR

Message: An error occurred while trying to write entry %s during the LDIF export: %s.

Severity: ERROR

Message: An error occurred while trying to create the reader for the LDIF import operation: %s.

Severity: ERROR

Message: An unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continue.

Severity: ERROR

Message: The LDIF backend currently does not provide a backup or restore mechanism. Use LDIF import and export operations instead.

Severity: ERROR

Message: The target entry %s does not exist.

Severity: ERROR

Message: The target entry %s does not exist.

Severity: ERROR

Message: Error reading key %s from key store %s: %s.

Severity: ERROR

Message: This backend does not provide support for the hasSubordinates operational attribute.

Severity: ERROR

Message: This backend does not provide support for the numSubordinates operational attribute.

Severity: ERROR

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokens.

Severity: ERROR

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid minute token.

Severity: ERROR

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid hour token.

Severity: ERROR

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month token.

Severity: ERROR

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year token.

Severity: ERROR

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week token.

Severity: ERROR

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar date.

Severity: ERROR

Message: An error occurred while attempting to export task backend data: %s.

Severity: ERROR

Message: The information for backup %s could not be found in the backup directory %s.

Severity: ERROR

Message: Unable to add DIT structure rule %s because its rule identifier conflicts with existing DIT structure rule (%s).

Severity: ERROR

Message: Unable to schedule task %s because its dependency task %s is missing.

Severity: ERROR

Message: Unable to add ldap syntax description with OID %s because it conflicts with an existing ldap syntax description.

Severity: ERROR

Message: Unable to remove ldap syntax description %s from the server schema because no such ldap syntax description is defined.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax because its OID %s corresponds to an attribute syntax that is already implemented.

Severity: ERROR

Message: An error occurred while attempting to decode the ldapsyntax description "%s": %s.

Severity: ERROR

Message: The provided recurring task schedule value has an invalid number of tokens.

Severity: ERROR

Message: The provided recurring task schedule value has an invalid minute token.

Severity: ERROR

Message: The provided recurring task schedule value has an invalid hour token.

Severity: ERROR

Message: The provided recurring task schedule value has an invalid day of the month token.

Severity: ERROR

Message: The provided recurring task schedule value has an invalid month of the year token.

Severity: ERROR

Message: The provided recurring task schedule value has an invalid day of the week token.

Severity: ERROR

Message: The schema backend does not support the Replace modification type for the %s attribute type.

Severity: ERROR

Message: An error occurred while trying to close file %s for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR

Message: The file %s written for the LDIF backend defined in configuration entry %s is 0 bytes long and unusable.

Severity: ERROR

Message: Configuration attribute ds-cfg-db-cache-size has a value of %d but the JVM has only %d available. Consider using ds-cfg-db-cache-percent.

Severity: ERROR

Message: Configuration attribute ds-cfg-db-cache-percent has a value of %d%% but the JVM has only %d%% available.

Severity: ERROR

Message: Unable to process the virtual list view request because the target assertion could not be decoded as a valid value for the '%s' attribute type.

Severity: ERROR

Message: An error occurred while trying to list the files to backup for backend '%s': %s.

Severity: ERROR

Message: An error occurred while trying to switch to append mode for backend '%s': %s.

Severity: ERROR

Message: An error occurred while trying to end append mode for backend '%s': %s.

Severity: ERROR

Message: Insufficient free memory (%d bytes) to perform import. At least %d bytes of free memory is required.

Severity: ERROR

Message: The attribute '%s' cannot have indexing of type '%s' because it does not have a corresponding matching rule.

Severity: ERROR

Message: Unable to process the virtual list view request because the target start position was before the beginning of the result set.

Severity: ERROR

Message: The entry database does not contain a record for ID %s.

Severity: ERROR

Message: Unable to examine the entry with ID %s for sorting purposes: %s.

Severity: ERROR

Message: Execution error during backend operation: %s.

Severity: ERROR

Message: Interrupted error during backend operation: %s.

Severity: ERROR

Message: The backend database directory could not be created: %s.

Severity: ERROR

Message: The backend database directory '%s' is not a valid directory.

Severity: ERROR

Message: The entry '%s' cannot be added because an entry with that name already exists.

Severity: ERROR

Message: The entry '%s' cannot be added because its parent entry does not exist.

Severity: ERROR

Message: There is no index configured for attribute type '%s'.

Severity: ERROR

Message: An error occurred while preloading the database cache for backend %s: %s.

Severity: ERROR

Message: An error occurred while attempting to decode an attribute description token from the compressed schema definitions: %s.

Severity: ERROR

Message: An error occurred while attempting to decode an object class set token from the compressed schema definitions: %s.

Severity: ERROR

Message: An error occurred while attempting to store compressed schema information in the database: %s.

Severity: ERROR

Message: An error occurred while parsing the search filter %s defined for VLV index %s: %s.

Severity: ERROR

Message: Sort attribute %s for VLV index %s is not defined in the server schema.

Severity: ERROR

Message: Database exception: %s.

Severity: ERROR

Message: A plugin caused the delete operation to be aborted while deleting a subordinate entry %s.

Severity: ERROR

Message: The entry '%s' cannot be removed because it has subordinate entries.

Severity: ERROR

Message: The entry '%s' cannot be removed because it does not exist.

Severity: ERROR

Message: An entry container named '%s' is alreadly registered for base DN '%s'.

Severity: ERROR

Message: The entry database does not contain a valid record for ID %s.

Severity: ERROR

Message: I/O error occurred while exporting entry: %s.

Severity: ERROR

Message: The backend must be disabled before the import process can start.

Severity: ERROR

Message: Unable to create the temporary directory %s.

Severity: ERROR

Message: The import has been aborted because the entry '%s' does not have a parent entry.

Severity: ERROR

Message: Entry record is not compatible with this version of the backend database. Entry version: %x.

Severity: ERROR

Message: An error occurred while reading from index %s. The index seems to be corrupt and is now operating in a degraded state. The index must be rebuilt before it can return to normal operation.

Severity: ERROR

Message: The following paged results control cookie value was not recognized: %s.

Severity: ERROR

Message: A plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %s.

Severity: ERROR

Message: A plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %s because the change to that entry violated the server schema configuration: %s.

Severity: ERROR

Message: The entry cannot be renamed to '%s' because an entry with that name already exists.

Severity: ERROR

Message: The entry '%s' cannot be renamed because it does not exist.

Severity: ERROR

Message: The entry '%s' cannot be modified because it does not exist.

Severity: ERROR

Message: The entry cannot be moved because the new parent entry '%s' does not exist.

Severity: ERROR

Message: The database environment could not be opened: %s.

Severity: ERROR

Message: Rebuilding system index(es) must be done with the backend containing the base DN disabled.

Severity: ERROR

Message: The backend database files could not be removed: %s.

Severity: ERROR

Message: The requested search operation included both the simple paged results control and the virtual list view control. These controls are mutually exclusive and cannot be used together.

Severity: ERROR

Message: The search results cannot be sorted because the given search request is not indexed.

Severity: ERROR

Message: The search base entry '%s' does not exist.

Severity: ERROR

Message: You do not have sufficient privileges to perform an unindexed search.

Severity: ERROR

Message: Unchecked exception during database transaction: %s.

Severity: ERROR

Message: There is no VLV index configured with name '%s'.

Severity: ERROR

Message: The database logging level string '%s' provided for configuration entry '%s' is invalid. The value must be one of OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or ALL. Note that these values are case sensitive.

Severity: ERROR

Message: Configuration attribute ds-cfg-db-cache-size has a value of %d which is less than the minimum: %d.

Severity: ERROR

Message: Configuration attributes ds-cfg-db-txn-no-sync and ds-cfg-db-txn-write-no-sync are mutually exclusive and cannot be both set at the same time.

Severity: ERROR

Message: The backend must be disabled before verification process can start.

Severity: ERROR

Message: Missing ID %d%n%s.

Severity: ERROR

Message: Missing entry %s in VLV index %s.

Severity: ERROR

Message: Reference to unknown entry ID %s%n%s.

Severity: ERROR

Message: Reference to entry ID %s has a key which does not match the expected key%n%s.

Severity: ERROR

Message: Empty ID set: %n%s.

Severity: ERROR

Message: Duplicate reference to ID %d%n%s.

Severity: ERROR

Message: Reference to unknown ID %d%n%s.

Severity: ERROR

Message: Reference to entry <%s> which does not match the value%n%s.

Severity: ERROR

Message: File dn2id is missing key %s.

Severity: ERROR

Message: File dn2id has ID %d instead of %d for key %s.

Severity: ERROR

Message: File dn2id has DN <%s> referencing unknown ID %d.

Severity: ERROR

Message: File dn2id has DN <%s> referencing entry with wrong DN <%s>.

Severity: ERROR

Message: The stored entry count in id2entry (%d) does not agree with the actual number of entry records found (%d).

Severity: ERROR

Message: File id2childrenCount has wrong number of children for DN <%s> (got %d, expecting %d).

Severity: ERROR

Message: File id2ChildrenCount references non-existing EntryID <%d>.

Severity: ERROR

Message: Ignoring schema definition '%s' because the following error occurred while it was being parsed: %s.

Severity: ERROR

Message: Schema definition could not be parsed as valid attribute value.

Severity: ERROR

Message: Attribute %s is set as confidential on a backend whose entries are still cleartext. Enable confidentiality on the backend first.

Severity: ERROR

Message: The attribute '%s' cannot enable confidentiality for keys and values at the same time.

Severity: ERROR

Message: Cannot encode entry for writing on storage: %s.

Severity: ERROR

Message: Input stream ended unexpectedly while decoding entry.

Severity: ERROR

Message: Confidentiality cannot be disabled on suffix '%s' because the following indexes have confidentiality still enabled: %s.

Severity: ERROR

Message: Error while enabling confidentiality with cipher %s, %d bits: %s.

Severity: ERROR

Message: The import has been aborted because the data to be imported contains duplicate copies of entry '%s'.

Severity: ERROR

Message: Unwilling to perform a search (connection ID %d, operation ID %d) with a scope of "%s" in the root DSE backend. Only the BASE scope is supported for the root DSE backend.

Severity: ERROR

Message: Proxy backend '%s' could not discover remote servers capabilities: %s.

Severity: ERROR

Message: Proxy backend '%s' is non functional because it could not find any primary nor secondary servers via the service discovery mechanism '%s'.

Severity: ERROR

Message: Proxy backend '%s' cannot find the configured service discovery mechanism '%s'.

Severity: ERROR

Message: No backend is associated with the base DN '%s'.

Severity: ERROR

Message: Proxy backend '%s' cannot register itself against base DN %s because this base DN is already registered against backend '%s'.

Severity: ERROR

Message: Proxy backend '%s' is being deregistered from base DN %s because local backend '%s' is registering against it. Local backends take precedence over proxy backends.

Severity: ERROR

Message: Java property %s which is specified in attribute ds-cfg-proxy-user-password-property of configuration entry %s should contain the password associated with the proxy bind DN, but this property is not set.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-proxy-user-password-environment-variable of configuration entry %s should contain the password associated with the proxy bind DN, but this property is not set.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-proxy-user-password-file of configuration entry %s should contain the password associated with the proxy bind DN, but this file does not exist.

Severity: ERROR

Message: An error occurred while trying to read the password associated with the proxy bind DN from file %s specified in configuration attribute ds-cfg-proxy-user-password-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-proxy-user-password-file of configuration entry %s should contain the password associated with the proxy bind DN, but this file is empty.

Severity: ERROR

Message: The partition base DN '%s' should be subordinate to one of the base DNs %s of proxy backend '%s'.

Severity: ERROR

Message: Backend database cache preload for backend '%s' is not supported in this release.

Severity: ERROR

Message: There are insufficient resources to perform the operation.

Severity: ERROR

Message: The time-to-live (TTL) feature can only be enabled for generalized time ordering indexes.

Severity: ERROR

Message: An unexpected error occurred while purging expired entries: %s.

Severity: ERROR

Message: An error occurred while trying to retrieve the truststore pin from the configuration attribute ds-cfg-trust-store-pin of configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to create the default truststore pin file %s.

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.

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.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid distinguished name because the underscore character is not allowed in an attribute name unless the %s configuration option is enabled.

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.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid distinguished name because the underscore character is not allowed as the first character of an attribute name even if the %s configuration option is enabled.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid distinguished name because the digit '%c' is not allowed as the first character of an attribute name unless the name is specified as an OID or the %s configuration option is enabled.

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.

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.

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'.

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'.

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.

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.

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.

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".

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.

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.

Severity: ERROR

Message: The provided value could not be parsed as a valid attribute type description because it was empty or contained only whitespace.

Severity: ERROR

Message: The provided value could not be parsed as a valid objectclass description because it was empty or contained only whitespace.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an objectclass description because an open parenthesis was expected at position %d but instead a '%s' character was found.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an objectclass description because the end of the value was encountered while the Directory Server expected more data to be provided.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an objectclass description because the numeric OID contained two consecutive periods at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an objectclass description because the numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an objectclass description because the non-numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an objectclass description because it contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an objectclass description because it contained an unexpected closing parenthesis at position %d.

Severity: ERROR

Message: The provided value could not be parsed as a valid DIT content rule description because it was empty or contained only whitespace.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because an open parenthesis was expected at position %d but instead a '%s' character was found.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because the end of the value was encountered while the Directory Server expected more data to be provided.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because the numeric OID contained two consecutive periods at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because the numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because the non-numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because it contained an unexpected closing parenthesis at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because it contained an illegal character %s at position %d.

Severity: ERROR

Message: The DIT content rule "%s" is associated with a structural objectclass %s that is not defined in the server schema.

Severity: ERROR

Message: The DIT content rule "%s" is associated with the objectclass with OID %s (%s). This objectclass exists in the server schema but is defined as %s rather than structural.

Severity: ERROR

Message: The DIT content rule "%s" is associated with an auxiliary objectclass %s that is not defined in the server schema.

Severity: ERROR

Message: The DIT content rule "%s" is associated with an auxiliary objectclass %s. This objectclass exists in the server schema but is defined as %s rather than auxiliary.

Severity: ERROR

Message: The DIT content rule "%s" is associated with a required attribute type %s that is not defined in the server schema.

Severity: ERROR

Message: The DIT content rule "%s" is associated with an optional attribute type %s that is not defined in the server schema.

Severity: ERROR

Message: The DIT content rule "%s" is associated with a prohibited attribute type %s that is not defined in the server schema.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT content rule description because a single quote was expected at position %d but the %s character was found instead.

Severity: ERROR

Message: The provided value could not be parsed as a valid name form description because it was empty or contained only whitespace.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because an open parenthesis was expected at position %d but instead a '%c' character was found.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because the end of the value was encountered while the Directory Server expected more data to be provided.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because the numeric OID contained two consecutive periods at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because the numeric OID contained an illegal character %c at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because the non-numeric OID contained an illegal character %c at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because it contained an unexpected closing parenthesis at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because it contained an illegal character %c at position %d.

Severity: ERROR

Message: The name form description "%s" is associated with a structural objectclass %s that is not defined in the server schema.

Severity: ERROR

Message: The name form description "%s" is associated with the objectclass with OID %s (%s). This objectclass exists in the server schema but is defined as %s rather than structural.

Severity: ERROR

Message: The definition for the name form with OID %s declared that it should include required attribute "%s". No attribute type matching this name or OID exists in the server schema.

Severity: ERROR

Message: The definition for the name form with OID %s declared that it should include optional attribute "%s". No attribute type matching this name or OID exists in the server schema.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because it does not specify the structural objectclass with which it is associated.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a name form description because a single quote was expected at position %d but the %c character was found instead.

Severity: ERROR

Message: The provided value could not be parsed as a valid matching rule use description because it was empty or contained only whitespace.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because an open parenthesis was expected at position %d but instead a '%s' character was found.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because the end of the value was encountered while the Directory Server expected more data to be provided.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because the numeric OID contained two consecutive periods at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because the numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because the non-numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because the specified matching rule %s is unknown.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because it contained an unexpected closing parenthesis at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because it contained an illegal character %s at position %d.

Severity: ERROR

Message: The matching rule use description "%s" is associated with attribute type %s that is not defined in the server schema.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule description because it does not specify the set of attribute types that may be used with the associated OID.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a matching rule use description because a single quote was expected at position %d but the %s character was found instead.

Severity: ERROR

Message: The provided value could not be parsed as a valid DIT structure rule description because it was empty or contained only whitespace.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because an open parenthesis was expected at position %d but instead a '%s' character was found.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because the end of the value was encountered while the Directory Server expected more data to be provided.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because the rule ID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because it contained an unexpected closing parenthesis at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because it contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because it referenced an unknown name form %s.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because it referenced an unknown rule ID %d for a superior DIT structure rule.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because it did not specify the name form for the rule.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because a single quote was expected at position %d but the %s character was found instead.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because the numeric OID contained two consecutive periods at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because the numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a DIT structure rule description because the non-numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s contained an illegal character %c at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not contain a close parenthesis that corresponded to the initial open parenthesis.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s started with a question mark but was not followed by the string "true" or "false".

Severity: ERROR

Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not contain a dollar sign to separate the attribute type from the match type.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not specify an attribute type before the dollar sign.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not specify a match type after the dollar sign.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s had an invalid match type starting at position %d.

Severity: ERROR

Message: The provided authPassword value had an invalid scheme character at position %d.

Severity: ERROR

Message: The provided authPassword value had a zero-length scheme element.

Severity: ERROR

Message: The provided authPassword value was missing the separator character or had an illegal character between the scheme and authInfo elements.

Severity: ERROR

Message: The provided authPassword value had an invalid authInfo character at position %d.

Severity: ERROR

Message: The provided authPassword value had a zero-length authInfo element.

Severity: ERROR

Message: The provided authPassword value was missing the separator character or had an illegal character between the authInfo and authValue elements.

Severity: ERROR

Message: No value was given to decode by the user password attribute syntax.

Severity: ERROR

Message: Unable to decode the provided value according to the user password syntax because the value does not start with the opening curly brace ("{") character.

Severity: ERROR

Message: Unable to decode the provided value according to the user password syntax because the value does not contain a closing curly brace ("}") character.

Severity: ERROR

Message: Unable to decode the provided value according to the user password syntax because the value does not contain a storage scheme name.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid RFC 3672 subtree specification.

Severity: ERROR

Message: The provided authPassword value had an invalid authValue character at position %d.

Severity: ERROR

Message: The provided authPassword value had a zero-length authValue element.

Severity: ERROR

Message: The provided authPassword value had an invalid trailing character at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid subtree specification.

Severity: ERROR

Message: The DIT content rule "%s" is not valid because it prohibits the use of attribute type %s which is required by the associated structural object class %s.

Severity: ERROR

Message: The DIT content rule "%s" is not valid because it prohibits the use of attribute type %s which is required by the associated auxiliary object class %s.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with a character at position %d that needs to be escaped.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid object class definition because character '%c' at position %d is not allowed in an object class name.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid object class definition because the underscore character is not allowed in an object class name unless the %s configuration option is enabled.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid object class definition because the hyphen character is not allowed as the first character of an object class name.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid object class definition because the underscore character is not allowed as the first character of an object class name even if the %s configuration option is enabled.

Severity: ERROR

Message: The provided value "%s" could not be parsed as a valid object class definition because the digit '%c' is not allowed as the first character of an object class name unless the name is specified as an OID or the %s configuration option is enabled.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax because it contains an unrecognized extension %s at position %d.

Severity: ERROR

Message: The provided value could not be parsed as a valid ldap syntax description because it was empty or contained only whitespace.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because an open parenthesis was expected at position %d but instead a '%s' character was found.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because the end of the value was encountered while the Directory Server expected more data to be provided.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because the numeric OID contained two consecutive periods at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because the numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because the non-numeric OID contained an illegal character %s at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because it contained an unexpected closing parenthesis at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because it contains more than one form of constructor.

Severity: ERROR

Message: The definition for the ldap syntax with OID %s declared that it's a substitute for a syntax with OID %s. No such syntax is configured for use in the Directory Server.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an enumeration syntax, because there is no value.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax extension because an invalid character was found at position %d.

Severity: ERROR

Message: The provided value "%s" could not be parsed as an ldap syntax description because a single quote was expected at position %d but the character %s was found instead.

Severity: ERROR

Message: The provided value "%s" is not safe for X-SCHEMA-FILE.

Severity: ERROR

Message: Attribute type could not be registered from definition: %s.

Severity: ERROR

Message: There should be no warnings on the schema, but instead got %d warnings: %s.

Severity: ERROR

Message: Matching rule use could not be registered from definition: %s.

Severity: ERROR

Message: Object class could not be registered from definition: %s.

Severity: ERROR

Message: Unable to parse the OID from the provided definition of objectclass: '%s'.

Severity: ERROR

Message: Unable to parse the OID from the provided definition of attribute type: '%s'.

Severity: ERROR

Message: Unable to parse the OID from the provided definition of ldap syntax: '%s'.

Severity: ERROR

Message: Unable to parse the OID from the provided definition of matching rule use: '%s'.

Severity: ERROR

Message: DIT content rule could not be registered from definition: %s.

Severity: ERROR

Message: Name form could not be registered from definition: %s.

Severity: ERROR

Message: Unable to parse the OID from the provided definition of name form: '%s'.

Severity: ERROR

Message: Unable to parse the OID from the provided definition of DIT content rule: '%s'.

Severity: ERROR

Message: Unable to parse the rule ID from the provided definition of DIT structure rule: '%s'.

Severity: ERROR

Message: Error occurred while writing log record for logger %s: %s. Any further write errors will be ignored.

Severity: ERROR

Message: Error occurred while opening log file %s for logger %s: %s.

Severity: ERROR

Message: Error occurred while closing log file for logger %s: %s.

Severity: ERROR

Message: Error occurred while flushing writer buffer for logger %s: %s.

Severity: ERROR

Message: Error occurred while listing log files named by policy with initial file name %s.

Severity: ERROR

Message: Error occurred while obtaining free disk space in the partition containing log file %s: %s.

Severity: ERROR

Message: Error occurred while enforcing retention policy %s for logger %s: %s.

Severity: ERROR

Message: Error occurred while creating common audit facility: %s.

Severity: ERROR

Message: Error while creating or updating common audit log publisher %s: %s.

Severity: ERROR

Message: Error while removing common audit log publisher %s: %s.

Severity: ERROR

Message: Error while adding common audit log publisher %s, the publisher has an unsupported handler type.

Severity: ERROR

Message: Error while reading JSON configuration file %s while creating common audit external log publisher %s: %s.

Severity: ERROR

Message: Error while creating common audit external log publisher %s: %s.

Severity: ERROR

Message: Error while creating common audit log publisher %s: %s.

Severity: ERROR

Message: Error while adding common audit log publisher %s, the publisher defines an unsupported log rotation policy %s.

Severity: ERROR

Message: Error while adding common audit log publisher %s, the publisher defines an unsupported log retention policy %s.

Severity: ERROR

Message: Error while processing common audit log publisher %s, this type of log publisher is unsupported.

Severity: ERROR

Message: Error while processing common audit log publisher %s, delimiter char '%s' should not contains more than one character.

Severity: ERROR

Message: Error while processing common audit log publisher %s, quote char '%s' should not contains more than one character.

Severity: ERROR

Message: Error while processing common audit log publisher %s, time of the day value '%s' for fixed time log rotation policy is not valid, it should use a 24-hour format "HHmm" : %s.

Severity: ERROR

Message: Error while decoding a transaction id control received from a request: %s.

Severity: ERROR

Message: Error while processing a log event for common audit: %s.

Severity: ERROR

Message: Error while processing common audit log publisher %s, the keystore pin file %s is missing.

Severity: ERROR

Message: Error while processing common audit log publisher %s, the keystore pin file %s could not be read: %s.

Severity: ERROR

Message: Error while processing common audit log publisher %s, the keystore pin file %s contains an empty pin.

Severity: ERROR

Message: Error while processing common audit log publisher %s, the keystore file %s is missing.

Severity: ERROR

Message: Error while processing common audit log publisher %s, the keystore file %s could not be read: %s.

Severity: ERROR

Message: Error while processing common audit log publisher %s, the keystore file %s is empty.

Severity: ERROR

Message: The configured DN is already used by another domain.

Severity: ERROR

Message: Replication Server failed to start because the hostname is unknown.

Severity: ERROR

Message: Replication Server failed to start : could not bind to the listen port : %d. Error : %s.

Severity: ERROR

Message: Unknown operation type : %s.

Severity: ERROR

Message: Internal Error : Operation %s change number %s was not found in pending list.

Severity: ERROR

Message: The replication server failed to start because the database %s could not be read : %s.

Severity: ERROR

Message: An Exception was caught while replaying operation %s : %s.

Severity: ERROR

Message: Error %s when searching for server state %s : %s base dn : %s.

Severity: ERROR

Message: Caught IOException while sending topology info (for update) on domain %s for %s server %s : %s.

Severity: ERROR

Message: Error when searching old changes from the database for base DN %s.

Severity: ERROR

Message: Error trying to replay %s, operation could not be decoded :.

Severity: ERROR

Message: Error trying to use the underlying database. The Replication Server is going to shut down: %s.

Severity: ERROR

Message: Error during the Replication Server database trimming or flush process. The Changelog service is going to shutdown: %s.

Severity: ERROR

Message: An unexpected error happened handling connection with %s. This connection is going to be closed.

Severity: ERROR

Message: In replication server %s: an unexpected error occurred while sending an ack to server id %s for change number %s in domain %s . This connection is going to be closed and reopened.

Severity: ERROR

Message: A loop was detected while replaying operation: %s error %s.

Severity: ERROR

Message: An Exception was caught while testing existence or trying to create the directory for the Replication Server database : %s.

Severity: ERROR

Message: The current request is rejected due to an import or an export already in progress for the same data.

Severity: ERROR

Message: On domain %s, initialization of server with serverId:%s has been requested from a server with an invalid serverId:%s. %s.

Severity: ERROR

Message: Invalid target for the export.

Severity: ERROR

Message: Domain %s: the server with serverId=%s is unreachable.

Severity: ERROR

Message: No domain matches the provided base DN '%s'.

Severity: ERROR

Message: Multiple domains match the base DN provided.

Severity: ERROR

Message: The provider class does not allow the operation requested.

Severity: ERROR

Message: The hostname %s could not be resolved as an IP address.

Severity: ERROR

Message: In Replication server %s: servers %s and %s have the same ServerId : %d.

Severity: ERROR

Message: In Replication server %s: replication servers %s and %s have the same ServerId : %d.

Severity: ERROR

Message: Entry %s was containing some unknown historical information, This may cause some inconsistency for this entry.

Severity: ERROR

Message: A conflict was detected but the conflict information could not be added. Operation: %s, Result: %s.

Severity: ERROR

Message: An error happened trying to rename a conflicting entry. DN: %s, Operation: %s, Result: %s.

Severity: ERROR

Message: The Replication is configured for suffix %s but was not able to connect to any Replication Server.

Severity: ERROR

Message: An unexpected error occurred while sending an Error Message to %s. This connection is going to be closed and reopened.

Severity: ERROR

Message: An unexpected error occurred while sending a Message to %s. This connection is going to be closed and reopened.

Severity: ERROR

Message: Could not replay operation %s with ChangeNumber %s error %s %s.

Severity: ERROR

Message: The entry %s has historical information for attribute %s which is not defined in the schema. This information will be ignored.

Severity: ERROR

Message: The Replication Server socket could not be closed : %s.

Severity: ERROR

Message: The thread listening on the replication server port could not be stopped : %s.

Severity: ERROR

Message: An unexpected error occurred when searching for generation id for domain "%s": %s.

Severity: ERROR

Message: An unexpected error occurred when looking for the replicated backend : %s. It may be not configured or disabled.

Severity: ERROR

Message: An unexpected error occurred when searching in %s for the generation ID : %s.

Severity: ERROR

Message: An unexpected error occurred when updating generation ID for domain "%s": %s.

Severity: ERROR

Message: The following error has been received : %s.

Severity: ERROR

Message: Initialization cannot be done because import is not supported by the backend %s.

Severity: ERROR

Message: Initialization cannot be done because export is not supported by the backend %s.

Severity: ERROR

Message: Initialization cannot be done because the following error occurred while locking the backend %s : %s.

Severity: ERROR

Message: Replication server caught exception while listening for client connections %s.

Severity: ERROR

Message: While clearing the database %s , the following error happened: %s.

Severity: ERROR

Message: An unexpected error occurred when testing existence or creating the replication backend : %s.

Severity: ERROR

Message: An error occurred when searching for %s : %s.

Severity: ERROR

Message: The base DN %s is not stored by any of the Directory Server backend.

Severity: ERROR

Message: Monitor data of remote servers are missing due to a processing error : %s.

Severity: ERROR

Message: Unable to send monitor data request for domain "%s" to replication server RS(%d) due to the following error: %s.

Severity: ERROR

Message: An Exception was caught while replaying replication message : %s.

Severity: ERROR

Message: Caught exception publishing fake operations for domain %s : %s.

Severity: ERROR

Message: Caught exception computing fake operations for domain %s for replication server %s : %s.

Severity: ERROR

Message: For replicated domain %s, in server with serverId=%s, the generation ID could not be set to value %s in the rest of the topology because this server is NOT connected to any replication server. You should check in the configuration that the domain is enabled and that there is one replication server up and running.

Severity: ERROR

Message: DN sent by remote replication server: %s does not match local replication server one: %s.

Severity: ERROR

Message: DN sent by replication server: %s does not match local directory server one: %s.

Severity: ERROR

Message: Caught IOException while forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %s.

Severity: ERROR

Message: Computed invalid initial status: %s in DS replication domain %s with server id %s.

Severity: ERROR

Message: Replication server received invalid initial status: %s for replication domain %s from server id %s.

Severity: ERROR

Message: Received invalid requested status %s in DS replication domain %s with server id %s.

Severity: ERROR

Message: Could not compute new status in RS replication domain %s for server id %s. Was in %s status and received %s event.

Severity: ERROR

Message: Could not compute new status in DS replication domain %s with server id %s. Was in %s status and received %s event.

Severity: ERROR

Message: Caught IOException while changing status for domain %s and serverId: %s after reset for generation id: %s.

Severity: ERROR

Message: Received change status message does not come from a directory server (dn: %s, server id: %s, msg: %s).

Severity: ERROR

Message: Received invalid new status %s in RS for replication domain %s and directory server id %s.

Severity: ERROR

Message: Replication broker with dn %s and server id %s failed to signal status change because of: %s.

Severity: ERROR

Message: Caught IOException while changing status for domain %s and serverId: %s from status analyzer: %s.

Severity: ERROR

Message: In directory server %s, received unknown assured update mode: %s, for domain %s. Message: %s.

Severity: ERROR

Message: In replication server %s, received unknown assured update mode: %s, for domain %s. Message: %s.

Severity: ERROR

Message: In replication server %s, received a safe data assured update message with incoherent level: %s, this is for domain %s. Message: %s.

Severity: ERROR

Message: The generation ID could not be reset for domain %s.

Severity: ERROR

Message: The Replication was not started on base-dn %s : %s.

Severity: ERROR

Message: Replication protocol error. Bad message type. %s received, %s required.

Severity: ERROR

Message: The Server Handler byte count is not correct Byte Count=%s (Fixed).

Severity: ERROR

Message: The fractional replication ldif import plugin is configured with invalid plugin type %s. Only the ldifImport plugin type is allowed.

Severity: ERROR

Message: An error occurred when accessing the change number database : %s.

Severity: ERROR

Message: The initialization failed because the domain %s is not connected to a replication server.

Severity: ERROR

Message: Could not retrieve the configuration for a replication domain matching the entry %s.

Severity: ERROR

Message: Directory server %s was attempting to connect to replication server %s but has disconnected in handshake phase. Error: %s.

Severity: ERROR

Message: Replication server %s was attempting to connect to replication server %s but has disconnected in handshake phase. Error: %s.