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: There is already an existing backend with name: %s.

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 error occurred while trying to create the PIN file %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s.

Severity: ERROR

Message: An error occurred while trying to read the trust store PIN from file %s specified in configuration attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the trust store, but this file is empty.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-trust-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the trust store, but this property is not set.

Severity: ERROR

Message: Java property %s which is specified in attribute ds-cfg-trust-store-pin-property of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this property is not set.

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: 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: Entry '%s' cannot be added because attribute '%s' contained an expression '%s' that could not be evaluated: %s.

Severity: ERROR

Message: Entry '%s' cannot be deleted because attribute '%s' contained an expression '%s' that could not be evaluated: %s.

Severity: ERROR

Message: Entry '%s' cannot be modified because attribute '%s' contained an expression '%s' that could not be evaluated: %s.

Severity: ERROR

Message: Entry '%s' cannot be read because attribute '%s' contained an expression '%s' that could not be evaluated: %s.

Severity: ERROR

Message: Cannot configure new SSL protocols for '%s' because the protocols '%s' are not supported. Look for supported protocols in 'cn=System Information,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 Information,cn=monitor'.

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: Unable to register workflow element %s with the Directory Server because another workflow element with the same ID is already registered.

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 disk containing directory %s used by %s is low on free space (%d bytes free). 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 disk containing directory %s used by %s is full (%d bytes free). 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 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: An error occurred while attempting to initialize the message digest generator for the %s algorithm: %s.

Severity: ERROR

Message: An error occurred while attempting to base64-decode the password value %s: %s.

Severity: ERROR

Message: The %s password storage scheme is not reversible, so it is impossible to recover the plaintext version of an encoded password.

Severity: ERROR

Message: An error occurred while trying to register the JMX alert handler with the MBean server: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to encode a password using the storage scheme defined in class %s: %s.

Severity: ERROR

Message: The ds-cfg-include-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are included in the cache, has an invalid value of "%s": %s.

Severity: ERROR

Message: The ds-cfg-exclude-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are excluded from the cache, has an invalid value of "%s": %s.

Severity: ERROR

Message: A fatal error occurred while trying to initialize fifo entry cache: %s.

Severity: ERROR

Message: A fatal error occurred while trying to initialize soft reference entry cache: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode the password modify extended request sequence: %s.

Severity: ERROR

Message: The password modify extended request cannot be processed because it does not contain an authorization ID and the underlying connection is not authenticated.

Severity: ERROR

Message: The password modify extended request cannot be processed because the server was unable to obtain a write lock on user entry %s after multiple attempts.

Severity: ERROR

Message: The password modify extended request cannot be processed because the server cannot decode "%s" as a valid DN for use in the authorization ID for the operation.

Severity: ERROR

Message: The password modify extended request cannot be processed because it contained an invalid userIdentity field. The provided userIdentity string was "%s".

Severity: ERROR

Message: The password modify extended request cannot be processed because it was not possible to identify the user entry to update based on the authorization DN of "%s".

Severity: ERROR

Message: The password modify extended operation cannot be processed because the current password provided for the user is invalid.

Severity: ERROR

Message: The keystore file %s specified in attribute ds-cfg-key-store-file of configuration entry %s does not exist.

Severity: ERROR

Message: An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-key-store-file in configuration entry %s: %s.

Severity: ERROR

Message: Java property %s which is specified in attribute ds-cfg-key-store-pin-property of configuration entry %s should contain the PIN needed to access the file-based key manager, but this property is not set.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-key-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the file-based key manager, but this property is not set.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based key manager, but this file does not exist.

Severity: ERROR

Message: An error occurred while trying to read the keystore PIN from file %s specified in configuration attribute ds-cfg-key-store-pin-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based key manager, but this file is empty.

Severity: ERROR

Message: An error occurred while trying to load the keystore contents from file %s: %s.

Severity: ERROR

Message: The keystore type %s specified in attribute ds-cfg-key-store-type of configuration entry %s is not valid: %s.

Severity: ERROR

Message: Java property %s which is specified in attribute ds-cfg-key-store-pin-property of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this property is not set.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-key-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this property is not set.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this file does not exist.

Severity: ERROR

Message: An error occurred while trying to read the keystore PIN from file %s specified in configuration attribute ds-cfg-key-store-pin-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this file is empty.

Severity: ERROR

Message: An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-key-store-pin in configuration entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to access the PKCS#11 key manager: %s.

Severity: ERROR

Message: An error occurred while trying to create a key manager factory to access the contents of keystore file %s: %s.

Severity: ERROR

Message: An error occurred while trying to create a key manager factory to access the contents of the PKCS#11 keystore: %s.

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: 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: Java property %s which is specified in attribute ds-cfg-trust-store-pin-property of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this property is not set.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-trust-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this property is not set.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this file does not exist.

Severity: ERROR

Message: An error occurred while trying to read the trust store PIN from file %s specified in configuration attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this file is empty.

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 trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate subject "%s" could not be decoded as an LDAP DN: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because an error occurred while attempting to retrieve the user entry with DN "%s": %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because no user entry exists with a DN of %s.

Severity: ERROR

Message: The SASL EXTERNAL bind request could not be processed because the associated bind request does not have a reference to the client connection.

Severity: ERROR

Message: The SASL EXTERNAL bind request could not be processed because the associated client connection instance is not an instance of LDAPClientConnection.

Severity: ERROR

Message: The SASL EXTERNAL bind request could not be processed because the client did not present a certificate chain during SSL/TLS negotiation.

Severity: ERROR

Message: The SASL EXTERNAL bind request failed because the certificate chain presented by the client during SSL/TLS negotiation could not be mapped to a user entry in the Directory Server.

Severity: ERROR

Message: StartTLS cannot be used on this connection because the underlying client connection is not available.

Severity: ERROR

Message: StartTLS cannot be used on this client connection because this connection type is not capable of using StartTLS to protect its communication.

Severity: ERROR

Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s does not have any certificates with which to verify the presented peer certificate.

Severity: ERROR

Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s did not contain the peer certificate presented by the client.

Severity: ERROR

Message: An error occurred while attempting to validate the peer certificate presented by the client with a certificate from the user's entry %s: %s.

Severity: ERROR

Message: SASL PLAIN authentication requires that SASL credentials be provided but none were included in the bind request.

Severity: ERROR

Message: The SASL PLAIN bind request did not include any NULL characters. NULL characters are required as delimiters between the authorization ID and authentication ID, and also between the authentication ID and the password.

Severity: ERROR

Message: The SASL PLAIN bind request did not include a second NULL character in the credentials, which is required as a delimiter between the authentication ID and the password.

Severity: ERROR

Message: The authentication ID contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the authentication ID.

Severity: ERROR

Message: The password contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the password.

Severity: ERROR

Message: An error occurred while attempting to decode the SASL PLAIN authentication ID "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR

Message: The authentication ID in the SASL PLAIN bind request appears to be an empty DN. This is not allowed.

Severity: ERROR

Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based authentication ID of a SASL PLAIN bind request: %s.

Severity: ERROR

Message: The server was not able to find any user entries for the provided authentication ID of %s.

Severity: ERROR

Message: The provided password is invalid.

Severity: ERROR

Message: An unexpected error occurred while attempting to obtain an MD5 digest engine for use by the CRAM-MD5 SASL handler: %s.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request contained SASL credentials but there is no stored challenge for this client connection. The first CRAM-MD5 bind request in the two-stage process must not contain client SASL credentials.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request contained SASL credentials, but the stored SASL state information for this client connection is not in an appropriate form for the challenge.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request from the client included SASL credentials but there was no space to separate the username from the authentication digest.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request included SASL credentials, but the decoded digest string had an invalid length of %d bytes rather than the %d bytes expected for a hex representation of an MD5 digest.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request included SASL credentials, but the decoded digest was not comprised of only hexadecimal digits: %s.

Severity: ERROR

Message: An error occurred while attempting to decode the SASL CRAM-MD5 username "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR

Message: The username in the SASL CRAM-MD5 bind request appears to be an empty DN. This is not allowed.

Severity: ERROR

Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL CRAM-MD5 bind request: %s.

Severity: ERROR

Message: The server was not able to find any user entries for the provided username of %s.

Severity: ERROR

Message: The provided password is invalid.

Severity: ERROR

Message: SASL CRAM-MD5 authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form.

Severity: ERROR

Message: The client connection included %s state information, indicating that the client was in the process of performing a %s bind, but the bind request did not include any credentials.

Severity: ERROR

Message: An unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %s.

Severity: ERROR

Message: An unexpected error occurred while trying to create an %s context: %s.

Severity: ERROR

Message: An error occurred while attempting to decode the SASL %s username "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR

Message: The username in the SASL %s bind request appears to be an empty DN. This is not allowed.

Severity: ERROR

Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL %s bind request: %s.

Severity: ERROR

Message: The username contained in the SASL %s bind request had a length of zero characters, which is not allowed. %s authentication does not allow an empty string for use as the username.

Severity: ERROR

Message: The server was not able to find any user entries for the provided username of %s.

Severity: ERROR

Message: The provided authorization ID %s contained an invalid DN: %s.

Severity: ERROR

Message: The entry %s specified as the authorization identity does not exist.

Severity: ERROR

Message: The entry %s specified as the authorization identity could not be retrieved: %s.

Severity: ERROR

Message: The server was unable to find any entry corresponding to authorization ID %s.

Severity: ERROR

Message: An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL %s authentication: %s.

Severity: ERROR

Message: SASL %s authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form.

Severity: ERROR

Message: SASL %s protocol error: %s.

Severity: ERROR

Message: The authenticating user %s does not have sufficient privileges to assume a different authorization identity.

Severity: ERROR

Message: The authenticating user %s does not have sufficient access to assume a different authorization identity.

Severity: ERROR

Message: The server was unable to find any entry corresponding to authentication ID %s.

Severity: ERROR

Message: The server was unable to because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be defined or neither defined.

Severity: ERROR

Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

Severity: ERROR

Message: An error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %s.

Severity: ERROR

Message: An error occurred while attempting to create the JAAS login context for GSSAPI authentication: %s.

Severity: ERROR

Message: No client connection was available for use in processing the GSSAPI bind request.

Severity: ERROR

Message: You do not have sufficient privileges to use the proxied authorization control.

Severity: ERROR

Message: ID string %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to resolve ID string %s to a user entry: %s.

Severity: ERROR

Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR

Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR

Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR

Message: Unable to process the cancel request because the extended operation did not include a request value.

Severity: ERROR

Message: An error occurred while attempting to decode the value of the cancel extended request: %s.

Severity: ERROR

Message: Password storage scheme %s does not support use with the authentication password attribute syntax.

Severity: ERROR

Message: The configured minimum password length of %d characters is greater than the configured maximum password length of %d.

Severity: ERROR

Message: The provided password is shorter than the minimum required length of %d characters.

Severity: ERROR

Message: The provided password is longer than the maximum allowed length of %d characters.

Severity: ERROR

Message: Configuration entry "%s" does not contain attribute ds-cfg-password-character-set which specifies the sets of characters that should be used when generating the password. This is a required attribute.

Severity: ERROR

Message: Configuration entry "%s" contains multiple definitions for the %s character set.

Severity: ERROR

Message: An error occurred while attempting to decode the value(s) of the configuration attribute ds-cfg-password-character-set, which is used to hold the character set(s) for use in generating the password: %s.

Severity: ERROR

Message: The password format string "%s" references an undefined character set "%s".

Severity: ERROR

Message: The password format string "%s" contains an invalid syntax. This value should be a comma-delimited sequence of elements, where each element is the name of a character set followed by a colon and the number of characters to choose at random from that character set.

Severity: ERROR

Message: An error occurred while attempting to decode the value for configuration attribute ds-cfg-password-format, which is used to specify the format for the generated passwords: %s.

Severity: ERROR

Message: An error occurred while attempting to get the password policy for user %s: %s.

Severity: ERROR

Message: The current password must be provided for self password changes.

Severity: ERROR

Message: Password modify operations that supply the user's current password must be performed over a secure communication channel.

Severity: ERROR

Message: End users are not allowed to change their passwords.

Severity: ERROR

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

Severity: ERROR

Message: The password cannot be changed because the previous password change was too recent.

Severity: ERROR

Message: The password cannot be changed because it is expired.

Severity: ERROR

Message: No new password was provided, and no password generator has been defined that may be used to automatically create a new password.

Severity: ERROR

Message: An error occurred while attempting to create a new password using the password generator: %s.

Severity: ERROR

Message: The password policy does not allow users to supply pre-encoded passwords.

Severity: ERROR

Message: The provided new password failed the validation checks defined in the server: %s.

Severity: ERROR

Message: Unable to encode the provided password using the default scheme(s): %s.

Severity: ERROR

Message: The identity mapper with configuration entry DN %s as specified for use with the password modify extended operation defined in entry %s either does not exist or is not enabled. The identity mapper is a required component, and the password modify extended operation will not be enabled.

Severity: ERROR

Message: An error occurred while attempting to determine the identity mapper to use in conjunction with the password modify extended operation defined in configuration entry %s: %s. The password modify extended operation will not be enabled for use in the server.

Severity: ERROR

Message: The provided authorization ID string "%s" could not be mapped to any user in the directory.

Severity: ERROR

Message: An error occurred while attempting to map authorization ID string "%s" to a user entry: %s.

Severity: ERROR

Message: An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL CRAM-MD5 authentication: %s.

Severity: ERROR

Message: An error occurred while attempting to verify the password for user %s during SASL PLAIN authentication: %s.

Severity: ERROR

Message: The user account has been administratively disabled.

Severity: ERROR

Message: The user account is locked.

Severity: ERROR

Message: Unable to examine entry %s as a potential member of static group %s because that entry does not exist in the Directory Server.

Severity: ERROR

Message: An error occurred while attempting to retrieve entry %s as a potential member of static group %s: %s.

Severity: ERROR

Message: Entry %s cannot be parsed as a valid static group because static groups are not allowed to have both the %s and %s object classes.

Severity: ERROR

Message: Entry %s cannot be parsed as a valid static group because it does not contain exactly one of the %s or the %s object classes.

Severity: ERROR

Message: Value %s for attribute %s in entry %s cannot be parsed as a valid DN: %s. It will be excluded from the set of group members.

Severity: ERROR

Message: Cannot add user %s as a new member of static group %s because that user is already in the member list for the group.

Severity: ERROR

Message: Cannot remove user %s as a member of static group %s because that user is not included in the member list for the group.

Severity: ERROR

Message: Cannot add user %s as a new member of static group %s because an error occurred while attempting to perform an internal modification to update the group: %s.

Severity: ERROR

Message: Cannot remove user %s as a member of static group %s because an error occurred while attempting to perform an internal modification to update the group: %s.

Severity: ERROR

Message: You do not have sufficient privileges to perform password reset operations.

Severity: ERROR

Message: The provided authorization ID was empty, which is not allowed for DIGEST-MD5 authentication.

Severity: ERROR

Message: The provided authorization ID %s contained an invalid DN: %s.

Severity: ERROR

Message: The authenticating user %s does not have sufficient privileges to specify an alternate authorization ID.

Severity: ERROR

Message: The entry corresponding to authorization DN %s does not exist in the Directory Server.

Severity: ERROR

Message: An error occurred while attempting to retrieve entry %s specified as the authorization ID: %s.

Severity: ERROR

Message: No entry corresponding to authorization ID %s was found in the server.

Severity: ERROR

Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: The certificate with subject %s could not be mapped to exactly one user. It maps to both %s and %s.

Severity: ERROR

Message: Configuration entry %s has value '%s' which violates the format required for attribute mappings. The expected format is 'certattr:userattr'.

Severity: ERROR

Message: Configuration entry %s contains multiple mappings for certificate attribute %s.

Severity: ERROR

Message: Mapping %s in configuration entry %s references attribute %s which is not defined in the server schema.

Severity: ERROR

Message: Configuration entry %s contains multiple mappings for user attribute %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: Unable to decode peer certificate subject %s as a DN: %s.

Severity: ERROR

Message: Peer certificate subject %s does not contain any attributes for which a mapping has been established.

Severity: ERROR

Message: The certificate with subject %s could not be mapped to exactly one user. It maps to both %s and %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: An error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %s.

Severity: ERROR

Message: The certificate with fingerprint %s could not be mapped to exactly one user. It maps to both %s and %s.

Severity: ERROR

Message: Unable to decode value "%s" in entry "%s" as an LDAP URL: %s.

Severity: ERROR

Message: Dynamic groups do not support nested groups.

Severity: ERROR

Message: Dynamic groups do not support explicitly altering their membership.

Severity: ERROR

Message: An error occurred while attempting perform an internal search with base DN %s and filter %s to resolve the member list for dynamic group %s: result code %s, error message %s.

Severity: ERROR

Message: The server encountered a timeout while attempting to add user %s to the member list for dynamic group %s.

Severity: ERROR

Message: The provided password differs less than the minimum required difference of %d characters.

Severity: ERROR

Message: The provided password contained too many instances of the same character appearing consecutively. The maximum number of times the same character may appear consecutively in a password is %d.

Severity: ERROR

Message: The provided password does not contain enough unique characters. The minimum number of unique characters that may appear in a user password is %d.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The provided password contained a word from the server's dictionary.

Severity: ERROR

Message: The specified dictionary file %s does not exist.

Severity: ERROR

Message: An error occurred while attempting to load the dictionary from file %s: %s.

Severity: ERROR

Message: The provided password was found in another attribute in the user entry.

Severity: ERROR

Message: The provided password contained character '%s' which is not allowed for use in passwords.

Severity: ERROR

Message: The provided password did not contain enough characters from the character set '%s'. The minimum number of characters from that set that must be present in user passwords is %d.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character set.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because the provided character set is empty.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because it contains character '%s' which has already been used.

Severity: ERROR

Message: The virtual static group defined in entry %s contains multiple target group DNs, but only one is allowed.

Severity: ERROR

Message: Unable to decode "%s" as the target DN for group %s: %s.

Severity: ERROR

Message: The virtual static group defined in entry %s does not contain a target group definition.

Severity: ERROR

Message: Virtual static groups do not support nesting.

Severity: ERROR

Message: Target group %s referenced by virtual static group %s does not exist.

Severity: ERROR

Message: Altering membership for virtual static group %s is not allowed.

Severity: ERROR

Message: Virtual static group %s references target group %s which is itself a virtual static group. One virtual static group is not allowed to reference another as its target group.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: You do not have sufficient privileges to use the password policy state extended operation.

Severity: ERROR

Message: The provided password policy state extended request did not include a request value.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode password policy state extended request value: %s.

Severity: ERROR

Message: Multiple entries were found with DN %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode an operation from the password policy state extended request: %s.

Severity: ERROR

Message: No value was provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: The value provided for the password policy state operation intended to set the disabled state for the user was invalid. The value must be either 'true' or 'false'.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the account expiration time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the account expiration time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the password changed time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the password changed time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the password warned time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the password warned time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to add an authentication failure time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to update the authentication failure times was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the last login time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the last login time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: No value was provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: The value provided for the password policy state operation intended to set the reset state for the user was invalid. The value must be either 'true' or 'false'.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to add a grace login use time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to update the grace login use times was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the required change time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the required change time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: The password policy state extended request included an operation with an invalid or unsupported operation type of %s.

Severity: ERROR

Message: The provided new password was already contained in the password history.

Severity: ERROR

Message: The Directory Server is not configured with any SMTP servers. The SMTP alert handler cannot be used unless the Directory Server is configured with information about at least one SMTP server.

Severity: ERROR

Message: The provided match pattern "%s" could not be parsed as a regular expression: %s.

Severity: ERROR

Message: The processed ID string %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on processed ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to resolve processed ID string %s to a user entry: %s.

Severity: ERROR

Message: Cannot add group %s as a new nested group of static group %s because that group is already in the nested group list for the group.

Severity: ERROR

Message: Cannot remove group %s as a nested group of static group %s because that group is not included in the nested group list for the group.

Severity: ERROR

Message: Group instance with DN %s has been deleted and is no longer valid.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The SMTP account status notification handler defined in configuration entry %s cannot be enabled unless the Directory Server is with information about one or more SMTP servers.

Severity: ERROR

Message: SMTP account status notification handler configuration entry '%s' does not include any email address attribute types or recipient addresses. At least one of these must be provided.

Severity: ERROR

Message: Unable to parse message subject value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the subject.

Severity: ERROR

Message: Unable to parse message subject value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type.

Severity: ERROR

Message: The message subject definitions contained in configuration entry '%s' have multiple subjects defined for notification type %s.

Severity: ERROR

Message: Unable to parse message template file path value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the template file path.

Severity: ERROR

Message: Unable to parse message template file path value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type.

Severity: ERROR

Message: The message template file path definitions contained in configuration entry '%s' have multiple template file paths defined for notification type %s.

Severity: ERROR

Message: The message template file '%s' referenced in configuration entry '%s' does not exist.

Severity: ERROR

Message: An unclosed token was found starting at column %d of line %d.

Severity: ERROR

Message: The notification-user-attr token starting at column %d of line %d references undefined attribute type %s.

Severity: ERROR

Message: The notification-property token starting at column %d of line %d references undefined notification property %s.

Severity: ERROR

Message: An unrecognized token %s was found at column %d of line %d.

Severity: ERROR

Message: An error occurred while attempting to parse message template file '%s' referenced in configuration entry '%s': %s.

Severity: ERROR

Message: An error occurred while attempting to send an account status notification message for notification type %s for user entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to encrypt a value using password storage scheme %s: %s.

Severity: ERROR

Message: An error occurred while trying to decrypt a value using password storage scheme %s: %s.

Severity: ERROR

Message: Cannot decode the provided symmetric key extended operation because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided symmetric key extended request: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode the symmetric key extended request sequence: %s.

Severity: ERROR

Message: The exact match identity mapper defined in configuration entry %s references attribute type %s which is does not have an equality index defined in backend %s.

Severity: ERROR

Message: The regular expression identity mapper defined in configuration entry %s references attribute type %s which is does not have an equality index defined in backend %s.

Severity: ERROR

Message: Failed to create a SASL server for SASL mechanism %s using a server FQDN of %s.

Severity: ERROR

Message: GSSAPI SASL mechanism handler initalization failed because the keytab file %s does not exist.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The password value %s has been base64-decoded but is too short to be valid.

Severity: ERROR

Message: The provided minimum required number of character sets '%d' is invalid because it must at least include all mandatory character sets.

Severity: ERROR

Message: The provided minimum required number of character sets '%d' is invalid because it is greater than the total number of defined character sets.

Severity: ERROR

Message: The provided password did not contain characters from at least %d of the following character sets or ranges: %s.

Severity: ERROR

Message: An error occurred while attempting to decode member's DN %s of static group %s: %s.

Severity: ERROR

Message: SASL %s authentication is not supported for user %s because the account is not managed locally.

Severity: ERROR

Message: Password modification is not supported for user %s because the account is not managed locally.

Severity: ERROR

Message: The password policy state extended operation is not supported for user %s because the account is not managed locally.

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the following mapping attributes were not found in the user's entry: %s.

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search of base DN "%s" returned more than one entry matching the filter "%s".

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search did not return any entries matching the filter "%s".

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search failed unexpectedly for the following reason: %s.

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the bind failed unexpectedly for the following reason: %s.

Severity: ERROR

Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because the host name "%s" could not be resolved to an IP address.

Severity: ERROR

Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because the connection was refused. This may indicate that the server is either offline or it is not listening on port %d.

Severity: ERROR

Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because the connection attempt timed out. This may indicate that the server is slow to respond, the network is slow, or that there is some other network problem.

Severity: ERROR

Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because SSL negotiation failed for the following reason: %s.

Severity: ERROR

Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because an unexpected error occurred: %s.

Severity: ERROR

Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has failed unexpectedly: %s.

Severity: ERROR

Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has been closed unexpectedly.

Severity: ERROR

Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has timed out and will be closed. This may indicate that the server is slow to respond, the network is slow, or that there is some other network problem.

Severity: ERROR

Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has encountered a protocol error while decoding a response from the server and will be closed. The decoding error was: %s.

Severity: ERROR

Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has received an unexpected response from the server and will be closed. The unexpected response message was: %s.

Severity: ERROR

Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has received a disconnect notification with response code %d (%s) and error message "%s".

Severity: ERROR

Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" has failed to authenticate user "%s", returning the response code %d (%s) and error message "%s".

Severity: ERROR

Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" returned multiple matching entries while searching "%s" using the filter "%s".

Severity: ERROR

Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" did not return any matching entries while searching "%s" using the filter "%s".

Severity: ERROR

Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" returned an error while searching "%s" using the filter "%s": response code %d (%s) and error message "%s".

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because the remote LDAP server address "%s" specifies a port number which is invalid. Port numbers should be greater than 0 and less than 65536.

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because the Java property %s which should contain the mapped search bind password is not set.

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because the environment variable %s which should contain the mapped search bind password is not set.

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because the file %s which should contain the mapped search bind password does not exist.

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because the file %s which should contain the mapped search bind password cannot be read for the following reason: %s.

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because the file %s which should contain the mapped search bind password is empty.

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because it does not specify the a means for obtaining the mapped search bind password.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The certificate with subject %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s.

Severity: ERROR

Message: The certificate with subject %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s.

Severity: ERROR

Message: The certificate with fingerprint %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on the certificate with fingerprint %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to map the certificate with fingerprint %s to a user entry: %s.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The provided password did not contain enough characters from the character range '%s'. The minimum number of characters from that range that must be present in user passwords is %d.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the range '%s' is reversed.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the range '%s' is missing the minus.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the range '%s' is too short.

Severity: ERROR

Message: There is no private key entry in keystore %s.

Severity: ERROR

Message: An error occurred while attempting to match a bcrypt hashed password value: %s.

Severity: ERROR

Message: The mapped search filter template "%s" could not be parsed as a valid LDAP filter.

Severity: ERROR

Message: An error occurred while trying to create a key manager factory to access the contents of LDAP keystore with base DN '%s': %s.

Severity: ERROR

Message: An error occurred while trying to create a trust manager factory to access the contents of LDAP keystore with base DN '%s': %s.

Severity: ERROR

Message: Java property %s which is specified in attribute ds-cfg-key-store-pin-property of configuration entry %s should contain the PIN needed to access the LDAP key manager, but this property is not set.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-key-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the LDAP key manager, but this property is not set.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the LDAP key manager, but this file does not exist.

Severity: ERROR

Message: An error occurred while trying to read the keystore PIN from file %s specified in configuration attribute ds-cfg-key-store-pin-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the LDAP key manager, but this file is empty.

Severity: ERROR

Message: Java property %s which is specified in attribute ds-cfg-trust-store-pin-property of configuration entry %s should contain the PIN needed to access the LDAP trust manager, but this property is not set.

Severity: ERROR

Message: Environment variable %s which is specified in attribute ds-cfg-trust-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the LDAP trust manager, but this property is not set.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the LDAP trust manager, but this file does not exist.

Severity: ERROR

Message: An error occurred while trying to read the trust store PIN from file %s specified in configuration attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s.

Severity: ERROR

Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the LDAP trust manager, but this file is empty.

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 LDAP attribute description list plugin instance defined in configuration entry %s does not list any plugin types. This plugin must be configured to operate as a pre-parse search plugin.

Severity: ERROR

Message: The LDAP attribute description list plugin instance defined in configuration entry %s lists an invalid plugin type %s. This plugin can only be used as a pre-parse search plugin.

Severity: ERROR

Message: The Directory Server profiler plugin instance defined in configuration entry %s does not list any plugin types. This plugin must be configured to operate as a startup plugin.

Severity: ERROR

Message: The Directory Server profiler plugin instance defined in configuration entry %s lists an invalid plugin type %s. This plugin can only be used as a startup plugin.

Severity: ERROR

Message: An unexpected error occurred when the profiler plugin defined in configuration entry %s attempted to write the information captured to output file %s: %s.

Severity: ERROR

Message: The startup plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server startup process: %s. The server startup process has been aborted.

Severity: ERROR

Message: The startup plugin defined in configuration entry %s returned a null value when it was invoked during the Directory Server startup process. This is an illegal return value, and the server startup process has been aborted.

Severity: ERROR

Message: The startup plugin defined in configuration entry %s encountered an error when it was invoked during the Directory Server startup process: %s (error ID %d). The server startup process has been aborted.

Severity: ERROR

Message: The shutdown plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server shutdown process: %s.

Severity: ERROR

Message: The post-connect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %s. The connection will be terminated.

Severity: ERROR

Message: The post-connect plugin defined in configuration entry %s returned null when invoked for connection %d from %s. This is an illegal response, and the connection will be terminated.

Severity: ERROR

Message: The post-disconnect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %s.

Severity: ERROR

Message: The post-disconnect plugin defined in configuration entry %s returned null when invoked for connection %d from %s. This is an illegal response.

Severity: ERROR

Message: The pre-parse %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

Severity: ERROR

Message: The pre-parse %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

Severity: ERROR

Message: The pre-operation %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

Severity: ERROR

Message: The pre-operation %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

Severity: ERROR

Message: The post-operation %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

Severity: ERROR

Message: The post-operation %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

Severity: ERROR

Message: The post-response %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

Severity: ERROR

Message: The post-response %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

Severity: ERROR

Message: The search result entry plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d with entry %s: %s. Processing on this search operation will be terminated.

Severity: ERROR

Message: The search result entry plugin defined in configuration entry %s returned null when invoked for connection %d operation %d with entry %s. This is an illegal response, and processing on this search operation will be terminated.

Severity: ERROR

Message: The search result reference plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d with referral URL(s) %s: %s. Processing on this search operation will be terminated.

Severity: ERROR

Message: The search result reference plugin defined in configuration entry %s returned null when invoked for connection %d operation %d with referral URL(s) %s. This is an illegal response, and processing on this search operation will be terminated.

Severity: ERROR

Message: An attempt was made to register the LastMod plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR

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

Severity: ERROR

Message: An error occurred while parsing the command-line arguments: %s.

Severity: ERROR

Message: An error occurred while trying to process the profile data in file %s: %s.

Severity: ERROR

Message: The LDIF import plugin defined in configuration entry %s threw an exception when it was invoked on entry %s: %s.

Severity: ERROR

Message: The LDIF import plugin defined in configuration entry %s returned null when invoked on entry %s. This is an illegal response.

Severity: ERROR

Message: The LDIF export plugin defined in configuration entry %s threw an exception when it was invoked on entry %s: %s.

Severity: ERROR

Message: The LDIF export plugin defined in configuration entry %s returned null when invoked on entry %s. This is an illegal response.

Severity: ERROR

Message: An attempt was made to register the EntryUUID plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR

Message: The intermediate response plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

Severity: ERROR

Message: The intermediate response plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

Severity: ERROR

Message: An attempt was made to register the password policy import plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR

Message: An error occurred while attempting to encode a password value stored in attribute %s of user entry %s: %s. Password values for this user will not be encoded.

Severity: ERROR

Message: The plugin defined in configuration entry %s does not support the %s plugin type.

Severity: ERROR

Message: The password policy import plugin is not configured any default auth password schemes, and the server does not support the %s auth password scheme.

Severity: ERROR

Message: Auth password storage scheme %s referenced by the password policy import plugin is not configured for use in the server.

Severity: ERROR

Message: The password policy import plugin is not configured any default user password schemes, and the server does not support the %s auth password scheme.

Severity: ERROR

Message: User password storage scheme %s referenced by the password policy import plugin is not configured for use in the server.

Severity: ERROR

Message: The subordinate modify DN plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

Severity: ERROR

Message: The subordinate modify DN plugin defined in configuration entry %s returned null when invoked for connection %d operation %s. This is an illegal response, and processing on this operation will be terminated.

Severity: ERROR

Message: An attempt was made to register the Unique Attribute plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR

Message: An attempt was made to register the Referential Integrity plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR

Message: An error occurred during Referential Integity plugin initialization because log file creation failed: %s.

Severity: ERROR

Message: An error occurred closing the Referential Integrity plugin update log file: %s.

Severity: ERROR

Message: An error occurred replacing the Referential Integrity plugin update log file: %s.

Severity: ERROR

Message: The Referential Integrity plugin failed when performaing an internal search: %s.

Severity: ERROR

Message: The Referential Integrity plugin failed when performing an internal modify on entry %s: %s.

Severity: ERROR

Message: The Referential Integrity plugin failed to decode a entry DN from the update log: %s.

Severity: ERROR

Message: An error occurred in the Referential Integrity plugin while attempting to configure the attribute type %s which has a syntax OID of %s. A Referential Integrity attribute type must have a syntax OID of either 1.3.6.1.4.1.1466.115.121.1.12 (for the distinguished name syntax) or 1.3.6.1.4.1.1466.115.121.1.34 (for the name and optional uid syntax).

Severity: ERROR

Message: The 7-bit clean plugin is configured with invalid plugin type %s. Only the ldifImport, preOperationAdd, preOperationModify, and preOperationModifyDN plugin types are allowed.

Severity: ERROR

Message: An error occurred while trying to decode the DN of the target entry: %s.

Severity: ERROR

Message: An error occurred while trying to decode attribute %s in the target entry: %s.

Severity: ERROR

Message: An error occurred while trying to decode the new RDN: %s.

Severity: ERROR

Message: The modify DN operation would have resulted in a value for attribute %s that was not 7-bit clean.

Severity: ERROR

Message: The entry included a value for attribute %s that was not 7-bit clean.

Severity: ERROR

Message: The password policy import plugin references default auth password storage scheme %s which is not available for use in the server.

Severity: ERROR

Message: The post-synchronization %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s.

Severity: ERROR

Message: A unique attribute conflict was detected for attribute %s: value %s already exists in entry %s.

Severity: ERROR

Message: A unique attribute conflict was detected for attribute %s during synchronization (connID=%d, opID=%d): value %s in entry %s conflicts with an existing value in entry %s. Manual interaction is required to eliminate the conflict.

Severity: ERROR

Message: An internal error occurred while attempting to determine whether the operation would have resulted in a unique attribute conflict (result %s, message %s).

Severity: ERROR

Message: An internal error occurred while attempting to determine whether the synchronization operation (connID=%d, opID=%d) for entry %s would have resulted in a unique attribute conflict (result %s, message %s).

Severity: ERROR

Message: The referential integrity plugin defined in configuration entry %s is configured to operate on attribute %s but there is no equality index defined for this attribute in backend %s.

Severity: ERROR

Message: The unique attribute plugin defined in configuration entry %s is configured to operate on attribute %s but there is no equality index defined for this attribute in backend %s.

Severity: ERROR

Message: An attempt was made to register the Change Number Control plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR

Message: An attempt was made to register the Change Number Control plugin with the following plugin types : %s. However this plugin must be configured with all of the following plugin types : %s.

Severity: ERROR

Message: The subordinate delete plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

Severity: ERROR

Message: The subordinate delete plugin defined in configuration entry %s returned null when invoked for connection %d operation %s. This is an illegal response, and processing on this operation will be terminated.

Severity: ERROR

Message: An attempt was made to register the Samba password synchronization plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR

Message: The Samba password synchronization plugin could not encode a password for the following reasons: %s.

Severity: ERROR

Message: The Samba password synchronization plugin could not process a modification for the following reason: %s.

Severity: ERROR

Message: Invalid plugin type '%s' for the Attribute Cleanup plugin.

Severity: ERROR

Message: Attribute '%s' is not defined in the directory schema.

Severity: ERROR

Message: The attribute '%s' has already been defined in the configuration.

Severity: ERROR

Message: The mapping '%s:%s' maps the attribute to itself.

Severity: ERROR

Message: The property 'check-references-filter-criteria' specifies filtering criteria for attribute '%s', but this attribute is not listed in the 'attribute-type' property.

Severity: ERROR

Message: The filtering criteria '%s' specified in property 'check-references-filter-criteria' is invalid because the filter could not be decoded: '%s'.

Severity: ERROR

Message: The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not exist in any of the configured naming contexts.

Severity: ERROR

Message: The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not match the filter '%s'.

Severity: ERROR

Message: The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not belong to any of the configured naming contexts.

Severity: ERROR

Message: The opration could not be processed due to an unexpected exception: '%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.