Category: Generic Backends

Severity: ERROR

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

Severity: ERROR

Message: Unwilling to update entry "%s" because modify operations are not supported in the root DSE backend. If you wish to alter the contents of the root DSE itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

Severity: ERROR

Message: Unwilling to perform a search (connection ID %d, operation ID %d) with a base DN of "%s" in the root DSE backend. The base DN for searches in this backend must be the DN of the root DSE itself.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The root DSE backend does not provide a facility for backup and restore operations. The contents of the root DSE should be backed up as part of the Directory Server configuration.

Severity: ERROR

Message: An attempt was made to configure the monitor backend without providing a configuration entry. This is not allowed, and no monitor information will be available over protocol.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Unwilling to update entry "%s" because modify operations are not supported in the monitor backend. If you wish to alter the contents of the base monitor entry itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: An attempt was made to configure the schema backend without providing a configuration entry. This is not allowed, and no schema information will be available over protocol.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The Directory Server was unable to obtain a lock on entry %s after multiple attempts. This could mean that the entry is already locked by a long-running operation or that the entry has previously been locked but was not properly unlocked.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold the recurring task ID, but only a single instance is allowed.

Severity: ERROR

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

Severity: ERROR

Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the recurring task ID, but only a single value is allowed.

Severity: ERROR

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

Severity: ERROR

Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold recurring task schedule, but only a single instance is allowed.

Severity: ERROR

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

Severity: ERROR

Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify recurring task schedule, but only a single value is allowed.

Severity: ERROR

Message: An error occurred while attempting to load class %s specified in attribute %s of the provided recurring task entry: %s. Does this class exist in the Directory Server classpath?.

Severity: ERROR

Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

Severity: ERROR

Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

Severity: ERROR

Message: The specified task data backing file %s already exists and the Directory Server will not attempt to overwrite it. Please delete or rename the existing file before attempting to use that path for the new backing file, or choose a new path.

Severity: ERROR

Message: The specified path %s for the new task data backing file appears to be an invalid path. Please choose a new path for the task data backing file.

Severity: ERROR

Message: The parent directory %s for the new task data backing file %s does not exist. Please create this directory before attempting to use this path for the new backing file or choose a new path.

Severity: ERROR

Message: The parent directory %s for the new task data backing file %s exists but is not a directory. Please choose a new path for the task data backing file.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is not a fatal error, so the task scheduler will attempt to continue parsing the file and schedule any additional tasks that it contains.

Severity: ERROR

Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is an unrecoverable error, and parsing cannot continue.

Severity: ERROR

Message: Entry %s read from the tasks backing file is invalid because it has no parent and does not match the task root DN of %s.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Entry %s read from the tasks backing file %s has a DN which is not valid for a task or recurring task definition and will be ignored.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The provided task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logic.

Severity: ERROR

Message: The provided task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowed.

Severity: ERROR

Message: The provided task entry does not contain any values for the %s attribute, which is used to specify the fully-qualified name of the class providing the task logic.

Severity: ERROR

Message: The provided task entry contains multiple values for the %s attribute, which is used to specify the task class name, but only a single value is allowed.

Severity: ERROR

Message: An error occurred while attempting to load class %s specified in attribute %s of the provided task entry: %s. Does this class exist in the Directory Server classpath?.

Severity: ERROR

Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

Severity: ERROR

Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

Severity: ERROR

Message: An error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not work as expected.

Severity: ERROR

Message: An error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lost.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Unable to remove entry %s from the task backend because its DN is either not appropriate for that backend or it is not below the scheduled or recurring tasks base entry.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Unable to process the search operation in the task backend because the provided base DN %s is not valid for entries in the task backend.

Severity: ERROR

Message: Unable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %s.

Severity: ERROR

Message: Unable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %s.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The schema backend does not support the modification of the %s attribute type. Only attribute types, object classes, ldap syntaxes, name forms, DIT content rules, DIT structure rules, and matching rule uses may be modified.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

Severity: ERROR

Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

Severity: ERROR

Message: An error occurred while attempting to write new versions of the server schema files: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

Severity: ERROR

Message: An error occurred while attempting to write new versions of the server schema files: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Unable to find a file containing concatenated schema element definitions in order to determine if any schema changes were made with the server offline. The file was expected in the %s directory and should have been named either %s or %s.

Severity: ERROR

Message: An error occurred while attempting to determine whether any schema changes had been made by directly editing the schema files with the server offline: %s.

Severity: ERROR

Message: An error occurred while attempting to write file %s containing a concatenated list of all server schema elements: %s. The server may not be able to accurately identify any schema changes made with the server offline.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The task associated with entry %s is currently running. The only modification allowed for running tasks is to replace the value of the ds-task-state attribute with "cancel".

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s includes entry %s which is not below the base DN defined for that backend.

Severity: ERROR

Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s contains entry %s but its parent entry has not yet been read.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Entry %s does not exist.

Severity: ERROR

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

Severity: ERROR

Message: Entry %s does not exist.

Severity: ERROR

Message: Source entry %s does not exist.

Severity: ERROR

Message: Target entry %s already exists.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The target entry %s does not exist.

Severity: ERROR

Message: The target entry %s does not exist.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Unable to process the virtual list view request because the target assertion could not be decoded as a valid value for the '%s' attribute type.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Execution error during backend operation: %s.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Database exception: %s.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Unable to create the temporary directory %s.

Severity: ERROR

Message: The import has been aborted because the entry '%s' does not have a parent entry.

Severity: ERROR

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

Severity: ERROR

Message: An error occurred while reading from index %s. The index seems to be corrupt and is now operating in a degraded state. The index must be rebuilt before it can return to normal operation.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The requested search operation included both the simple paged results control and the virtual list view control. These controls are mutually exclusive and cannot be used together.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Unchecked exception during database transaction: %s.

Severity: ERROR

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

Severity: ERROR

Message: The database logging level string '%s' provided for configuration entry '%s' is invalid. The value must be one of OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or ALL. Note that these values are case sensitive.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Missing ID %d%n%s.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Empty ID set: %n%s.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: File dn2id is missing key %s.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: Input stream ended unexpectedly while decoding entry.

Severity: ERROR

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

Severity: ERROR

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

Severity: ERROR

Message: The import has been aborted because the data to be imported contains duplicate copies of entry '%s'.

Severity: ERROR

Message: Proxy backend '%s' could not discover remote servers capabilities: %s.

Severity: ERROR

Message: Proxy backend '%s' is non functional because it could not find any primary nor secondary servers via the service discovery mechanism '%s'.

Severity: ERROR

Message: Proxy backend '%s' cannot find the configured service discovery mechanism '%s'.

Severity: ERROR

Message: No backend is associated with the base DN '%s'.

Severity: ERROR

Message: Proxy backend '%s' cannot register itself against base DN %s because this base DN is already registered against backend '%s'.

Severity: ERROR

Message: Proxy backend '%s' is being deregistered from base DN %s because local backend '%s' is registering against it. Local backends take precedence over proxy backends.

Severity: ERROR

Message: The partition base DN '%s' should be subordinate to one of the base DNs %s of proxy backend '%s'.

Severity: ERROR

Message: Backend database cache preload for backend '%s' is not supported in this release.

Severity: ERROR

Message: There are insufficient resources to perform the operation.

Severity: ERROR

Message: The time-to-live (TTL) feature can only be enabled for generalized time ordering indexes.

Severity: ERROR

Message: An unexpected error occurred while purging expired entries: %s.

Severity: ERROR

Message: The partition base DN '%s' shouldn't be subordinate to one of the other partition base DNs %s of proxy backend '%s'.

Severity: ERROR

Message: An error occurred while trying to retrieve the key managers from the key manager provider `%s`.

Severity: ERROR

Message: Could not stop export-ldif threads after 30 seconds. Now forcing stop by interrupting them.