Log Message Reference

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

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

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

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

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.

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.

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

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.

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

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.

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

Message: Reason unknown.

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

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

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

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

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

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

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

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

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

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

Message: Authentication failure.

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

Message: Authorization failure.

Message: A communication problem occurred while contacting the server.

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

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

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

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

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

Message: Empty managed object names are not permitted.

Message: Blank managed object names are not permitted.

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

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

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

Message: The requested managed object could not be found.

Message: The "%s" property is mandatory.

Message: The following properties are mandatory: %s.

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

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

Message: The following constraint violation occurred: %s.

Message: The following constraint violations occurred: %s.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Message: There is already an existing backend with name: %s.

Message: An attempt was made to configure the root DSE backend without providing a configuration entry. This is not allowed.

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.

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.

Message: An unexpected failure occurred while trying to process a search operation (connection ID %d, operation ID %d) in the root DSE backend: %s.

Message: Unable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %s.

Message: An unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %s.

Message: An unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %s.

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.

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.

Message: An unexpected error occurred while attempting to decode cn=monitor as the base DN for the Directory Server monitor information: %s. No monitor information will be available over protocol.

Message: Unwilling to add entry "%s" because add operations are not supported in the "%s" backend.

Message: Unwilling to remove entry "%s" because delete operations are not supported in the "%s" backend.

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.

Message: Unwilling to rename entry "%s" because modify DN operations are not supported in the "%s" backend.

Message: An error occurred while attempting to export the base monitor entry: %s.

Message: An error occurred while attempting to export the monitor entry for monitor provider %s: %s.

Message: The "%s" backend does not support LDIF import operations.

Message: Unable to retrieve the requested entry from the "%s" backend because the provided DN was null.

Message: Unable to initialize the "%s" backend because an error occurred while attempting to decode the base DN for this backend: %s.

Message: Unable to retrieve the requested entry %s from the monitor backend because the DN is not below the monitor base of %s.

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.

Message: An error occurred while trying to determine the base DNs to use when publishing the Directory Server schema information, as specified in the ds-cfg-schema-entry-dn attribute of configuration entry %s: %s. The default schema base DN of cn=schema will be used.

Message: An error occurred while attempting to export the base schema entry: %s.

Message: Unable to retrieve the requested entry %s from the schema backend because the DN is equal to one of the schema entry DNs.

Message: An unexpected error occurred while trying to open the LDIF writer for the schema backend: %s.

Message: An error occurred while trying to deregister %s as a schema entry DN: %s.

Message: An error occurred while trying to register %s as a schema entry DN: %s.

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.

Message: The task defined in entry %s is invalid because it has an invalid state %s.

Message: An error occurred while trying to parse the scheduled start time value %s from task entry %s.

Message: An error occurred while trying to parse the actual start time value %s from task entry %s.

Message: An error occurred while trying to parse the completion time value %s from task entry %s.

Message: Task entry %s is missing required attribute %s.

Message: There are multiple instances of attribute %s in task entry %s.

Message: There are no values for attribute %s in task entry %s.

Message: There are multiple values for attribute %s in task entry %s.

Message: An error occurred while executing the task defined in entry %s: %s.

Message: The provided recurring task entry does not contain attribute %s which is needed to hold the recurring task ID.

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.

Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task ID.

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.

Message: The provided recurring task entry does not contain attribute %s which is needed to specify recurring task schedule.

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.

Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task schedule.

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.

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?.

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?.

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.

Message: The task backend configuration entry does not contain any base DNs. There must be exactly one base DN for task information in the Directory Server.

Message: The task backend configuration entry contains multiple base DNs. There must be exactly one base DN for task information in the Directory Server.

Message: An error occurred while attempting to decode recurring task base %s as a DN: %s.

Message: An error occurred while attempting to decode scheduled task base %s as a DN: %s.

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.

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.

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.

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.

Message: An error occurred while attempting to determine the new path to the task data backing file: %s.

Message: New entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasks.

Message: Unable to add recurring task %s to the task scheduler because another recurring task already exists with the same ID.

Message: Unable to schedule task %s because another task already exists with the same ID.

Message: An error occurred while attempting to schedule the next iteration of recurring task %s: %s.

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.

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.

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.

Message: An error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %s.

Message: An error occurred while attempting to parse entry %s as a task and add it to the scheduler: %s.

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.

Message: An error occurred while attempting to read from the tasks data backing file %s: %s.

Message: An error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %s.

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.

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.

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.

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.

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?.

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?.

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.

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.

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.

Message: Unable to remove pending task %s because no such task exists.

Message: Unable to remove pending task %s because the task is no longer pending.

Message: Unable to remove completed task %s because no such task exists in the list of completed tasks.

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.

Message: Unable to remove entry %s from the task backend because there is no scheduled task associated with that entry DN.

Message: Unable to delete entry %s from the task backend because the associated task is currently running.

Message: Unable to remove entry %s from the task backend because there is no recurring task associated with that entry DN.

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.

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.

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.

Message: Unable to initialize the "%s" backend because the provided configuration entry is null.

Message: Requested entry %s does not exist in the backup backend.

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.

Message: Unable to retrieve entry %s from the backup backend because the requested backup directory is invalid: %s.

Message: An error occurred while attempting to examine the requested backup directory: %s.

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.

Message: Unable to retrieve entry %s from the backup backend because it does not have a parent.

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.

Message: Backup %s does not exist in backup directory %s.

Message: Unwilling to update entry "%s" because modify operations are not supported in the "%s" backend.

Message: The requested entry %s does not exist in the backup backend.

Message: Exactly one base DN must be provided for use with the memory-based backend.

Message: Entry %s already exists in the memory-based backend.

Message: Entry %s does not belong in the memory-based backend.

Message: Unable to add entry %s because its parent entry %s does not exist in the memory-based backend.

Message: Entry %s does not exist in the "%s" backend.

Message: Cannot delete entry %s because it has one or more subordinate entries.

Message: Unable to create an LDIF writer: %s.

Message: Cannot write entry %s to LDIF: %s.

Message: Unable to create an LDIF reader: %s.

Message: An unrecoverable error occurred while reading from LDIF: %s.

Message: An unexpected error occurred while processing the import: %s.

Message: The memory-based backend does not support backup or restore operations.

Message: Cannot rename entry %s because it has one or more subordinate entries.

Message: Cannot rename entry %s because the target entry is in a different backend.

Message: Cannot rename entry %s because the new parent entry %s doesn’t exist.

Message: An error occurred while attempting to register base DN %s in the Directory Server: %s.

Message: The schema backend does not support the %s modification type.

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.

Message: An error occurred while attempting to decode the object class "%s": %s.

Message: Unable to add objectclass %s because its superior class of %s is not defined in the server schema.

Message: Unable to add objectclass %s because it requires attribute %s which is not defined in the server schema.

Message: Unable to add objectclass %s because it allows attribute %s which is not defined in the server schema.

Message: An error occurred while attempting to write the updated schema: %s.

Message: An error occurred while attempting to decode the name form "%s": %s.

Message: An error occurred while attempting to decode the DIT content rule "%s": %s.

Message: An error occurred while attempting to decode the DIT structure rule "%s": %s.

Message: An error occurred while attempting to decode the matching rule use "%s": %s.

Message: The server will not allow removing all values for the %s attribute type in the server schema.

Message: Unable to add attribute type %s because it conflicts with multiple existing attribute types (%s and %s).

Message: Unable to add objectclass %s because it conflicts with multiple existing objectclasses (%s and %s).

Message: Unable to add name form %s because it conflicts with multiple existing name forms (%s and %s).

Message: Unable to add name form %s because it references structural objectclass %s which is not defined in the server schema.

Message: Unable to add name form %s because it references required attribute type %s which is not defined in the server schema.

Message: Unable to add name form %s because it references optional attribute type %s which is not defined in the server schema.

Message: Unable to add DIT content rule %s because it conflicts with multiple existing DIT content rules (%s and %s).

Message: Unable to add DIT content rule %s because it references structural objectclass %s which is already associated with another DIT content rule %s.

Message: Unable to add DIT content rule %s because it references structural objectclass %s which is not defined in the server schema.

Message: Unable to add DIT content rule %s because it references auxiliary objectclass %s which is not defined in the server schema.

Message: Unable to add DIT content rule %s because it references required attribute type %s which is not defined in the server schema.

Message: Unable to add DIT content rule %s because it references optional attribute type %s which is not defined in the server schema.

Message: Unable to add DIT content rule %s because it references prohibited attribute type %s which is not defined in the server schema.

Message: Unable to add DIT structure rule %s because it conflicts with multiple existing DIT structure rules (%s and %s).

Message: Unable to add DIT structure rule %s because it references name form %s which is already associated with another DIT structure rule %s.

Message: Unable to add DIT structure rule %s because it references name form %s which is not defined in the server schema.

Message: Unable to add matching rule use %s because it conflicts with multiple existing matching rule uses (%s and %s).

Message: Unable to add matching rule use %s because it references matching rule %s which is already associated with another matching rule use %s.

Message: Unable to add matching rule use %s because it references attribute type %s which is not defined in the server schema.

Message: Circular reference detected for attribute type %s in which the superior type chain references the attribute type itself.

Message: Circular reference detected for objectclass %s in which the superior class chain references the objectclass itself.

Message: Circular reference detected for DIT structure rule %s in which the superior rule chain references the DIT structure rule itself.

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.

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.

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.

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.

Message: Unable to remove attribute type %s from the server schema because no such attribute type is defined.

Message: Unable to remove attribute type %s from the server schema because it is referenced as the superior type for attribute type %s.

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.

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.

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.

Message: Unable to remove attribute type %s from the server schema because it is referenced by matching rule use %s.

Message: Unable to remove objectclass %s from the server schema because no such objectclass is defined.

Message: Unable to remove objectclass %s from the server schema because it is referenced as the superior class for objectclass %s.

Message: Unable to remove objectclass %s from the server schema because it is referenced as the structural class for name form %s.

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.

Message: Unable to remove name form %s from the server schema because no such name form is defined.

Message: Unable to remove name form %s from the server schema because it is referenced by DIT structure rule %s.

Message: Unable to remove DIT content rule %s from the server schema because no such DIT content rule is defined.

Message: Unable to remove DIT structure rule %s from the server schema because no such DIT structure rule is defined.

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.

Message: Unable to remove matching rule use %s from the server schema because no such matching rule use is defined.

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.

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.

Message: Unable to add attribute type %s because the superior type %s is marked as OBSOLETE in the server schema.

Message: Unable to add attribute type %s because the associated matching rule %s is marked as OBSOLETE in the server schema.

Message: Unable to add object class %s because the superior class %s is marked as OBSOLETE in the server schema.

Message: Unable to add object class %s because required attribute %s is marked as OBSOLETE in the server schema.

Message: Unable to add object class %s because optional attribute %s is marked as OBSOLETE in the server schema.

Message: Unable to add name form %s because its structural object class %s is marked as OBSOLETE in the server schema.

Message: Unable to add name form %s because it requires attribute type %s which is marked as OBSOLETE in the server schema.

Message: Unable to add name form %s because it allows attribute type %s which is marked as OBSOLETE in the server schema.

Message: Unable to add DIT content rule %s because its structural object class %s is marked as OBSOLETE in the server schema.

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.

Message: Unable to add DIT content rule %s because it requires attribute type %s which is marked as OBSOLETE in the server schema.

Message: Unable to add DIT content rule %s because it allows attribute type %s which is marked as OBSOLETE in the server schema.

Message: Unable to add DIT content rule %s because it prohibits attribute type %s which is marked as OBSOLETE in the server schema.

Message: Unable to add DIT structure rule %s because its name form %s is marked OBSOLETE in the server schema.

Message: Unable to add DIT structure rule %s because it references superior rule %s which is marked as OBSOLETE in the server schema.

Message: Unable to add matching rule use %s because its matching rule %s is marked OBSOLETE in the server schema.

Message: Unable to add matching rule use %s because it references attribute type %s which is marked as OBSOLETE in the server schema.

Message: Unable to add DIT content rule %s because it references auxiliary object class %s which is marked as OBSOLETE in the server schema.

Message: You do not have sufficient privileges to modify the Directory Server schema.

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.

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.

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.

Message: The Directory Server is not configured to allow task %s to be invoked.

Message: Requested entry %s does not exist in the trust store backend.

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.

Message: Error while trying to retrieve certificate %s from the trust store file %s: %s.

Message: Indexes are not supported in the "%s" backend.

Message: Unable to initialize the trust store backend from configuration entry %s because it does not contain exactly one base DN.

Message: LDIF import and export operations are not supported in the "%s" backend.

Message: Backup and restore operations are not supported in the "%s" backend.

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

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

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.

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.

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.

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.

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.

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

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

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

Message: The certificate entry %s already exists.

Message: Error while attempting to generate a self-signed certificate %s in the trust store file %s: %s.

Message: Error while trying to add certificate %s to the trust store file %s: %s.

Message: The entry %s could not be added because it does not contain a certificate attribute %s.

Message: The entry %s could not be added because it contains multiple certificate attributes %s.

Message: The entry %s could not be added because it does not contain a value of certificate attribute %s.

Message: The entry %s could not be added because it contains multiple values of certificate attribute %s.

Message: Error while writing certificate %s to a file: %s.

Message: The root container for backend %s has not been initialized preventing this backend from processing the requested operation.

Message: Unable to obtain a write lock on entry %s.

Message: Entry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backend.

Message: Entry %s cannot be modified because it does not represent a valid task in the server.

Message: Entry %s cannot be modified because the assoicated task has completed running. Completed tasks cannot be modified.

Message: Entry %s cannot be modified because the server does not currently support modifying recurring task entries.

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".

Message: Error while trying to delete certificate %s from the trust store file %s: %s.

Message: Unable to retrieve entry %s from the trust store backend because the certificate %s does not exist.

Message: The LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNs.

Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s has multiple entries with a DN of %s.

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.

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.

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.

Message: An error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %s.

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.

Message: Entry %s already exists in the LDIF backend.

Message: The parent for entry %s does not exist.

Message: Entry %s does not exist.

Message: Entry %s has one or more subordinate entries and cannot be deleted until all of its subordinate entries are removed first.

Message: Entry %s does not exist.

Message: Source entry %s does not exist.

Message: Target entry %s already exists.

Message: The new parent DN %s does not exist.

Message: Entry %s specified as the search base DN does not exist.

Message: An error occurred while trying to create the writer for the LDIF export operation: %s.

Message: An error occurred while trying to write entry %s during the LDIF export: %s.

Message: An error occurred while trying to create the reader for the LDIF import operation: %s.

Message: An unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continue.

Message: The LDIF backend currently does not provide a backup or restore mechanism. Use LDIF import and export operations instead.

Message: The target entry %s does not exist.

Message: The target entry %s does not exist.

Message: Error reading key %s from key store %s: %s.

Message: This backend does not provide support for the hasSubordinates operational attribute.

Message: This backend does not provide support for the numSubordinates operational attribute.

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokens.

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid minute token.

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid hour token.

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month token.

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year token.

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week token.

Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar date.

Message: An error occurred while attempting to export task backend data: %s.

Message: The information for backup %s could not be found in the backup directory %s.

Message: Unable to add DIT structure rule %s because its rule identifier conflicts with existing DIT structure rule (%s).

Message: Unable to schedule task %s because its dependency task %s is missing.

Message: Unable to add ldap syntax description with OID %s because it conflicts with an existing ldap syntax description.

Message: Unable to remove ldap syntax description %s from the server schema because no such ldap syntax description is defined.

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.

Message: An error occurred while attempting to decode the ldapsyntax description "%s": %s.

Message: The provided recurring task schedule value has an invalid number of tokens.

Message: The provided recurring task schedule value has an invalid minute token.

Message: The provided recurring task schedule value has an invalid hour token.

Message: The provided recurring task schedule value has an invalid day of the month token.

Message: The provided recurring task schedule value has an invalid month of the year token.

Message: The provided recurring task schedule value has an invalid day of the week token.

Message: The schema backend does not support the Replace modification type for the %s attribute type.

Message: An error occurred while trying to close file %s for the LDIF backend defined in configuration entry %s: %s.

Message: The file %s written for the LDIF backend defined in configuration entry %s is 0 bytes long and unusable.

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.

Message: Configuration attribute ds-cfg-db-cache-percent has a value of %d%% but the JVM has only %d%% available.

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.

Message: An error occurred while trying to list the files to backup for backend '%s': %s.

Message: An error occurred while trying to switch to append mode for backend '%s': %s.

Message: An error occurred while trying to end append mode for backend '%s': %s.

Message: Insufficient free memory (%d bytes) to perform import. At least %d bytes of free memory is required.

Message: The attribute '%s' cannot have indexing of type '%s' because it does not have a corresponding matching rule.

Message: Unable to process the virtual list view request because the target start position was before the beginning of the result set.

Message: The entry database does not contain a record for ID %s.

Message: Unable to examine the entry with ID %s for sorting purposes: %s.

Message: Execution error during backend operation: %s.

Message: Interrupted error during backend operation: %s.

Message: The backend database directory could not be created: %s.

Message: The backend database directory '%s' is not a valid directory.

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

Message: The entry '%s' cannot be added because its parent entry does not exist.

Message: There is no index configured for attribute type '%s'.

Message: An error occurred while preloading the database cache for backend %s: %s.

Message: An error occurred while attempting to decode an attribute description token from the compressed schema definitions: %s.

Message: An error occurred while attempting to decode an object class set token from the compressed schema definitions: %s.

Message: An error occurred while attempting to store compressed schema information in the database: %s.

Message: An error occurred while parsing the search filter %s defined for VLV index %s: %s.

Message: Sort attribute %s for VLV index %s is not defined in the server schema.

Message: Database exception: %s.

Message: A plugin caused the delete operation to be aborted while deleting a subordinate entry %s.

Message: The entry '%s' cannot be removed because it has subordinate entries.

Message: The entry '%s' cannot be removed because it does not exist.

Message: An entry container named '%s' is alreadly registered for base DN '%s'.

Message: The entry database does not contain a valid record for ID %s.

Message: I/O error occurred while exporting entry: %s.

Message: The backend must be disabled before the import process can start.

Message: Unable to create the temporary directory %s.

Message: The parent entry '%s' does not exist.

Message: Entry record is not compatible with this version of the backend database. Entry version: %x.

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.

Message: The following paged results control cookie value was not recognized: %s.

Message: A plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %s.

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.

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

Message: The entry '%s' cannot be renamed because it does not exist.

Message: The entry '%s' cannot be modified because it does not exist.

Message: The entry cannot be moved because the new parent entry '%s' does not exist.

Message: The database environment could not be opened: %s.

Message: Rebuilding system index(es) must be done with the backend containing the base DN disabled.

Message: The backend database files could not be removed: %s.

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.

Message: The search results cannot be sorted because the given search request is not indexed.

Message: The search base entry '%s' does not exist.

Message: You do not have sufficient privileges to perform an unindexed search.

Message: Unchecked exception during database transaction: %s.

Message: There is no VLV index configured with name '%s'.

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.

Message: Configuration attribute ds-cfg-db-cache-size has a value of %d which is less than the minimum: %d.

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.

Message: The backend must be disabled before verification process can start.

Message: Missing ID %d%n%s.

Message: Missing entry %s in VLV index %s.

Message: Reference to unknown entry ID %s%n%s.

Message: Reference to entry ID %s has a key which does not match the expected key%n%s.

Message: Empty ID set: %n%s.

Message: Duplicate reference to ID %d%n%s.

Message: Reference to unknown ID %d%n%s.

Message: Reference to entry <%s> which does not match the value%n%s.

Message: File dn2id is missing key %s.

Message: File dn2id has ID %d instead of %d for key %s.

Message: File dn2id has DN <%s> referencing unknown ID %d.

Message: File dn2id has DN <%s> referencing entry with wrong DN <%s>.

Message: The stored entry count in id2entry (%d) does not agree with the actual number of entry records found (%d).

Message: File id2childrenCount has wrong number of children for DN <%s> (got %d, expecting %d).

Message: File id2ChildrenCount references non-existing EntryID <%d>.

Message: Ignoring schema definition '%s' because the following error occurred while it was being parsed: %s.

Message: Schema definition could not be parsed as valid attribute value.

Message: Attribute %s is set as confidential on a backend whose entries are still cleartext. Enable confidentiality on the backend first.

Message: The attribute '%s' cannot enable confidentiality for keys and values at the same time.

Message: Cannot encode entry for writing on storage: %s.

Message: Input stream ended unexpectedly while decoding entry.

Message: Confidentiality cannot be disabled on suffix '%s' because the following indexes have confidentiality still enabled: %s.

Message: Error while enabling confidentiality with cipher %s, %d bits: %s.

Message: There are insufficient resources to perform the operation.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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.

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

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

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.

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

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.

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).

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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).

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

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

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).

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).

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

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

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

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

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.

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.

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

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

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

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

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).

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

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

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

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

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.

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.

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.

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

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

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.

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.

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.

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

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

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.

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

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.

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

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

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

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

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.

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

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.

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.

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

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

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

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

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.

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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.

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.

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

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.

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

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.

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.

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

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

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

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

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

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.

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

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.

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

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".

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.

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.

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

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

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

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.).

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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.

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.

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

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

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

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

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

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.

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.

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

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

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.

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.

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.

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

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

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

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

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.

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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

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.

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

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

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.

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

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

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

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

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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

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

Message: Cannot initialize the configuration framework: %s.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Message: Abandon requests cannot be canceled.

Message: Bind requests cannot be canceled.

Message: Unbind requests cannot be canceled.

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

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

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

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

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

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

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

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.

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

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.

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

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).

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

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

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

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

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.

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).

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

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

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.

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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

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).

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.

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.

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

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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

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

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

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

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.

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.

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.

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

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

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.

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

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.

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

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.

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.

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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.

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

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

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

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

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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.

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

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.

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.

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.

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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).

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

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.

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.

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

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

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

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

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.

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.

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Message: Unknown modification type %s requested.

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

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

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

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

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

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

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

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.

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.

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.

Message: Unable to de-register base DN %s with the Directory Server because that base DN is not registered for any active backend.

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.

Message: Rejecting the requested operation because the connection has not been authenticated.

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.

Message: Object class %s added to entry %s is marked OBSOLETE in the server schema.

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.

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.

Message: An unexpected error occurred while attempting to perform DIT structure rule processing for the parent of entry %s: %s.

Message: You do not have sufficient privileges to reset user passwords.

Message: You do not have sufficient privileges to access the server configuration.

Message: You do not have sufficient privileges to add entries that include privileges.

Message: You do not have sufficient privileges to modify the set of privileges contained in an entry.

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

Message: Entry %s violates the Directory Server schema configuration because it includes attribute %s without any values.

Message: OpenDJ is configured to run as a Windows service and it cannot run in no-detach mode.

Message: Unable to decode an entry because it had an unsupported entry version byte value of %s.

Message: Unable to decode an entry because an unexpected exception was caught during processing: %s.

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.

Message: The request control with Object Identifier (OID) "%s" cannot be used due to insufficient access rights.

Message: The connection handler %s is trying to use the listener %s which is already in use by another connection handler.

Message: No enabled connection handler available.

Message: Could not start connection handlers.

Message: Unable to process the non-root bind because the server is in lockdown mode.

Message: Unable to decode the provided attribute because it used an undefined attribute description token %s.

Message: Unable to decode the provided object class set because it used an undefined token %s.

Message: Unable to write the updated compressed schema token data: %s.

Message: Unable to decode the provided entry encode configuration element because it has an invalid length.

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.

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.

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.

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.

Message: The provided new password was found in the password history for the user.

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.

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.

Message: An error occurred while attempting to disconnect client connection %d: %s.

Message: An unexpected error occurred in the idle time limit thread: %s.

Message: The Directory Server is currently running. Environment configuration changes are not allowed with the server running.

Message: The specified server root directory '%s' is invalid. The specified path must exist and must be a directory.

Message: The specified config file path '%s' is invalid. The specified path must exist and must be a file.

Message: The specified config handler class '%s' is invalid. The specified class must be a subclass of the org.opends.server.api.ConfigHandler superclass.

Message: The specified schema configuration directory '%s' is invalid. The specified path must exist and must be a directory.

Message: The specified lock directory '%s' is invalid. The specified path must exist and must be a directory.

Message: The Directory Server is currently running. The environment configuration can not be altered while the server is online.

Message: An error occurred while attempting to initialize a SSL context for server to server communication: %s.

Message: The ADS trust store backend %s is not enabled.

Message: The backend %s is not a trust store backend.

Message: An error occurred in the trust store synchronization thread: %s.

Message: The password storage scheme defined in configuration entry %s does not support the auth password syntax, which is used by password attribute %s.

Message: Password policy configuration entry %s references deprecated password storage scheme DN %s which does not support the auth password syntax.

Message: CryptoManager cannot get the requested digest %s: %s.

Message: CryptoManager cannot get the requested MAC engine %s: %s.

Message: CryptoManager cannot get the requested encryption cipher %s: %s.

Message: CryptoManager cannot get the preferred key wrapping cipher: %s.

Message: CryptoManager failed to add entry "%s" to initiate instance key generation.

Message: CryptoManager failed to retrieve entry "%s" (the instance-key-pair public-key-certificate): %s.

Message: CryptoManager failed to compute an instance key identifier: %s.

Message: Failed to add entry "%s".

Message: CryptoManager failed to publish the instance-key-pair public-key-certificate entry in ADS: %s.

Message: CryptoManager failed to retrieve the collection of instance-key-pair public-key-certificates from ADS container "%s": %s.

Message: CryptoManager failed to encode symmetric key attribute value: %s.

Message: CryptoManager symmetric key attribute value "%s" syntax is invalid: incorrect number of fields.

Message: CryptoManager symmetric key attribute value "%s" syntax is invalid. Parsing failed in field "%s" at offset %d.

Message: CryptoManager failed to retrieve the instance-key-pair private-key: %s.

Message: CryptoManager failed to decipher the wrapped secret-key value: %s.

Message: CryptoManager cannot find the public-key-certificate (identifier "%s") requested for symmetric key re-encoding.

Message: CryptoManager failed to decode the key entry identifier "%s": %s.

Message: CrytpoManager passed invalid MAC algorithm "%s": %s.

Message: CryptoManager failed to initialize MAC engine: %s.

Message: CryptoManager passed invalid Cipher transformation "%s": %s.

Message: CryptoManager cannot initialize Cipher: %s.

Message: CryptoManager failed to write the stream prologue: %s.

Message: CryptoManager failed to decrypt the supplied data because it could not read the symmetric key identifier in the data prologue: %s.

Message: CryptoManager failed to decrypt the supplied data because the symmetric key identifier in the data prologue does not match any known key entries.

Message: CryptoManager failed to decrypt the supplied data because it could not read the cipher initialization vector in the data prologue.

Message: CryptoManager failed to decrypt the supplied data because there was an error reading from the input stream: %s.

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.

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".

Message: CryptoManager failed to import the symmetric key entry "%s": %s.

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.

Message: CryptoManager failed to instantiate a KeyGenerator for algorithm "%s": %s.

Message: CryptoManager failed to add locally produced symmetric key entry "%s": %s.

Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

Message: CryptoManager failed to decrypt the supplied data because it could not read the version number in the data prologue: %s.

Message: CryptoManager failed to decrypt the supplied data because the version "%d" in the data prologue is unknown.

Message: The provided entry %s cannot be added because its suffix is not defined as one of the suffixes within the Directory Server.

Message: Start TLS extended operations cannot be canceled.

Message: Cancel extended operations can not be canceled.

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.

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

Message: Entry %s can not be added because BER encoding of %s attribute is not supported.

Message: The CryptoManager entry "%s" (the instance-key-pair public-key-certificate) does not contain a public-key certificate.

Message: In no-detach mode, the 'timeout' option cannot be used.

Message: The entry %s does not contain the pwdPolicy objectclass, which is required for Directory Server password policy.

Message: Unable to decode the provided string "%s" as a relative distinguished name because it does not contain a value for attribute type %s.

Message: CryptoManager failed to initialize because the specified cipher key length "%d" is beyond the allowed cryptography strength "%d" in jurisdiction policy files.

Message: Failed to update free disk space for directory %s: %s.

Message: The directory server is not accepting a new persistent search request because the server has already reached its limit.

Message: This operation involves LDAP subentries which you do not have sufficient privileges to administer.

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

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.

Message: The password policy definition contained in configuration entry "%s" is invalid because the password validator "%s" specified in attribute "%s" cannot be found.

Message: The password could not be validated because of misconfiguration. Please contact the administrator.

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.

Message: Could not get filesystem for directory %s: %s.

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.

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.

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.

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.

Message: Cannot properly use SHA-1 using the java provider. Verify java.security is properly configured.

Message: Cannot complete initialization of server’s backends because the root and administrative backends have not been initialized yet.

Message: An error occurred while attempting to initialize the message digest generator for the %s algorithm: %s.

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

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

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

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

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.

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.

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

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

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

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

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.

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.

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

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".

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

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

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

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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

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

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

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

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

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

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.

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.

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.

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.

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.

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

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

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

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

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).

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.

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.

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

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

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

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

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.

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

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

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.

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

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.

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

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.

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.

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.

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.

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.

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

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.

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

Message: The provided password is invalid.

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

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.

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.

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.

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.

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

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.

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

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.

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

Message: The provided password is invalid.

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.

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.

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

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

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.

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

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.

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.

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

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

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

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

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

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

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.

Message: SASL %s protocol error: %s.

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

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

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

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

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

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

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

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

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

Message: ID string %s mapped to multiple users.

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.