Log message reference

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

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

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

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

Severity: ERROR
Message: Could not find the "%s" command in "%s".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: Cannot initialize the configuration framework: %s.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: Error creating SSL socket factory: %s.

Severity: ERROR
Message: The smtp-server value '%s' is invalid: %s.

Severity: ERROR
Message: Unable to resolve the host for the listen address '%s' of the LDAP connection handler %s.

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: The attempt to register this connection with the Directory Server was rejected. This indicates that the server already has the maximum allowed number of concurrent connections established.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: An error occurred during multi-stage authentication: '%s'.

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

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

Severity: ERROR
Message: Unable to process request '%s' received for JMX client because this type of request is not supported for JMX.

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

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

Severity: ERROR
Message: The key with alias '%s' used by '%s' could not be found, which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configured.

Severity: ERROR
Message: No usable key was found for '%s', which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configured.

Severity: ERROR
Message: Could not write data to the client for %s.

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

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

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

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

Severity: ERROR
Message: The connection attempt from client %s to %s has been rejected because there are too many open connections from this client.

Severity: ERROR
Message: Unable to process the provided server-side sort request control: %s.

Severity: ERROR
Message: Unable to process HTTP request '%s': %s.

Severity: ERROR
Message: Unable to write HTTP response to the client '%s': %s.

Severity: ERROR
Message: Error while starting the HTTP application: %s.

Severity: ERROR
Message: cancel() invoked.

Severity: ERROR
Message: JMX connection %s with JMX connection ID '%s' has been disconnected because it was finalized by GC.

Severity: ERROR
Message: JMX connection %s with JMX connection ID '%s' has been disconnected because it received a '%s' notification.

Severity: ERROR
Message: The key with alias '%s' used by '%s' is not valid yet. The key will be used, but SSL connections may fail depending on the validation performed by the peer. Verify that the underlying keystore is properly configured with a valid key.

Severity: ERROR
Message: The key with alias '%s' used by '%s' has expired. The key will be used, but SSL connections may fail depending on the validation performed by the peer. Verify that the underlying keystore is properly configured with a valid key.

Severity: ERROR
Message: Abandon requests cannot be canceled.

Severity: ERROR
Message: Bind requests cannot be canceled.

Severity: ERROR
Message: Unbind requests cannot be canceled.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: CryptoManager failed to verify the wrapped key entry signature: %s.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is within the same hierarchical path.

Severity: ERROR
Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is not subordinate to the same base DN in the parent backend.

Severity: ERROR
Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains one or more other base DNs that are subordinate to backend %s but the new base DN is not.

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

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

Severity: ERROR
Message: Entry %s cannot be modified because the modification attempted to set one or more new values for attribute %s which is marked OBSOLETE in the server schema.

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

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the new RDN includes attribute type %s which is declared OBSOLETE in the server schema.

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

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

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

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

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

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

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

Severity: ERROR
Message: The wrapped key entry signature does not match the entry content.

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

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

Severity: ERROR
Message: No enabled connection handler available.

Severity: ERROR
Message: Could not start connection handlers.

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

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

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

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

Severity: ERROR
Message: Rejecting a bind request for user %s because either the entire server or the user’s backend has a writability mode of 'disabled' and password policy state updates would not be allowed.

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

Severity: ERROR
Message: The password policy configuration entry "%s" is invalid because if a maximum password age is configured, then the password expiration warning interval must be shorter than the maximum password age.

Severity: ERROR
Message: The password policy configuration entry "%s" is invalid because if both a minimum password age and a maximum password age are configured, then the sum of the minimum password age and the password expiration warning interval must be shorter than the maximum password age.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: CryptoManager cannot initialize Cipher: %s.

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

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

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

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

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

Severity: ERROR
Message: CryptoManager failed to import the symmetric key entry "%s" because it could not obtain a symmetric key attribute value that can be decoded by this instance.

Severity: ERROR
Message: CryptoManager detected a field mismatch between the key entry to be imported and an entry in the key cache that share the key identifier "%s".

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

Severity: ERROR
Message: CryptoManager failed to import the symmetric key entry "%s" because it could not add a symmetric key attribute value that can be decoded by this instance.

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

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

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

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

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

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

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

Severity: ERROR
Message: Start TLS extended operations cannot be canceled.

Severity: ERROR
Message: Cancel extended operations can not be canceled.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the new superior entry %s is equal to or a subordinate of the entry to be moved.

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

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

Severity: ERROR
Message: The subentry %s must have either the pwdPolicy or ds-pwp-password-policy objectclasses, which is required for the Directory Server password policy.

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

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

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

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

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

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

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

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

Severity: ERROR
Message: The password for user %s could not be validated because the password policy subentry %s is referring to an unknown password validator (%s). Please make sure the password policy subentry only refers to validators that exist on all replicas.

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

Severity: ERROR
Message: The free space (%s) on the disk containing directory "%s" is between low and full threshold for the following subsystems: %s. Write operations are only permitted by a user with the BYPASS_LOCKDOWN privilege until the free space rises above the threshold. Replication updates are still allowed.

Severity: ERROR
Message: The free space (%s) on the disk containing directory "%s" is below full threshold for the following subsystems: %s. Write operations to the backend, replication updates included, will fail until the free space rises above the threshold.

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

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

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

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

Severity: ERROR
Message: An error occurred while adding Service Discovery Mechanism '%s': %s.

Severity: ERROR
Message: Registering Service Discovery Manager’s listener failed : %s.

Severity: ERROR
Message: Discovery mechanism '%s' initialization failed : %s.

Severity: ERROR
Message: Error occurred while creating an SSL context for service discovery mechanism '%s' : %s.

Severity: ERROR
Message: Could not retrieve the list of replicas from replication server '%s' for replication server group '%s'. Exception : %s.

Severity: ERROR
Message: Could not retrieve auto-configuration data from directory server '%s' for replication server group '%s'. Exception : %s".

Severity: ERROR
Message: Service discovery mechanism '%s' failed to refresh the partition information. Exception : %s",.

Severity: ERROR
Message: Service discovery mechanism '%s' failed to refresh the connection options. Exception : %s",.

Severity: ERROR
Message: "%s" (low=%s, full=%s).

Severity: ERROR
Message: You do not have sufficient privileges to read directory server monitoring information.

Severity: ERROR
Message: Entry %s cannot be added because its parent entry %s is a subentry.

Severity: ERROR
Message: The master key with alias '%s' does not exist in the '%s' key manager. Please check that the correct key manager has been configured and that it contains the specified master keys.

Severity: ERROR
Message: The CryptoManager could not encode a symmetric because the master key with alias '%s' does not exist in the '%s' key manager. Please check that the correct key manager has been configured and that it contains the specified master keys.

Severity: ERROR
Message: Cipher %s is not yet supported.

Severity: ERROR
Message: The CryptoManager could was not able to obtain the deployment’s pepper. Please check that the CryptoManager has a correctly configured key manager and preferred digest mechanism.

Severity: ERROR
Message: No enabled password storage schemes in '%s' in subentry '%s'.

Severity: ERROR
Message: Cannot use both pwdValidatorPolicy and ds-pwp-validator in subentry '%s'.

Severity: ERROR
Message: The dictionary data could not be decompressed: %s.

Severity: ERROR
Message: CryptoManager failed to find the master key pair with ID '%s', make sure cryptoManager has access to the master key pair that was used at the time of wrapping the key.

Severity: ERROR
Message: Requested cipher for a non existing cipher key: cryptographic services were not properly initialized, programming error.

Severity: ERROR
Message: Type %d is not a valid secret key type. The Valid type is '0' for a cipher key. Secret key initialization cannot continue, check the data source and re-initialize if needed.

Severity: ERROR
Message: The subentry %s cannot use both %s and %s objectclasses.

Severity: ERROR
Message: The subentry %s using the %s objectclass cannot define validators using the old %s objectclass.

Severity: ERROR
Message: The subentry %s using the %s objectclass cannot define validators using the new %s objectclass.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid duration.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid integer.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid boolean.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid time.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid string.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid attribute.

Severity: ERROR
Message: The values for the '%s' attribute are not valid strings.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid state update failure policy.

Severity: ERROR
Message: A values for the '%s' attribute is not a valid attribute name.

Severity: ERROR
Message: Could not start connection handler %s with listen addresses "%s". The error was: %s.

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

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

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

Severity: ERROR
Message: 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: 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: 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: 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: 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: Index for attribute '%s' cannot be created for matching rule '%s' because it cannot be found in the schema. Fix the matching rule name in the config or add the matching rule to the schema.

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: 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: Reference to unknown entry ID %s%n%s.

Severity: ERROR
Message: The entry with ID %s is associated with the wrong 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.

Severity: ERROR
Message: The index(es) cannot be rebuilt because the server failed to obtain a write lock for the entry '%s' after multiple attempts.

Severity: ERROR
Message: VLV index '%s' must be configured with at least one sort attribute.

Severity: ERROR
Message: Missing entry %s in index %s.

Severity: ERROR
Message: Big index for attribute '%s' cannot be created for matching rule '%s' because it is not an equality matching rule.

Severity: ERROR
Message: A Server Side Sort control must be specified whenever a Virtual List View control is present.

Severity: ERROR
Message: Counter of %s reports wrong number of entries for key <%s> (got %d, expecting %d).

Severity: ERROR
Message: An error occurred while attempting to send an email for the completion of %s task: Task ID: %s, Task State: %s, Scheduled Start Time: %s, Actual Start Time: %s, Completion Time: %s. The error was: %s.

Severity: ERROR
Message: Index for attribute '%s' cannot be created because the configuration contains an included attribute value '%s' which appears to be invalid according to the schema: %s.

Severity: ERROR
Message: An internal error occurred when accessing backend '%s': %s.

Severity: ERROR
Message: An internal error was detected when accessing backend '%s'.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was a comma or semicolon.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not allowed in an attribute name.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the hyphen character is not allowed as the first character of an attribute name.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because it contained an RDN containing an empty attribute name.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the parsed attribute name %s included a period but that name did not appear to be a valid OID.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was part of the attribute name '%s'.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because the next non-space character after attribute name "%s" should have been an equal sign but instead was '%c'.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not valid.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with an octothorpe (#) but was not followed by a positive multiple of two hexadecimal digits.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with an octothorpe (#) but contained a character %c that was not a valid hexadecimal digit.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because an unexpected failure occurred while attempting to parse an attribute value from one of the RDN components: "%s".

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because one of the RDN components included a quoted value that did not have a corresponding closing quotation mark.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid distinguished name because one of the RDN components included a value with an escaped hexadecimal digit that was not followed by a second hexadecimal digit.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid RFC 3672 subtree specification.

Severity: ERROR
Message: The provided value "%s" could not be parsed as a valid subtree specification.

Severity: ERROR
Message: There should be no warnings on the schema, but instead got %d warnings: %s.

Severity: ERROR
Message: Unable to parse the OID from the provided definition of objectclass: '%s'.

Severity: ERROR
Message: Unable to parse the OID from the provided definition of attribute type: '%s'.

Severity: ERROR
Message: Unable to parse the OID from the provided definition of ldap syntax: '%s'.

Severity: ERROR
Message: Unable to parse the OID from the provided definition of matching rule use: '%s'.

Severity: ERROR
Message: Unable to parse the OID from the provided definition of name form: '%s'.

Severity: ERROR
Message: Unable to parse the OID from the provided definition of DIT content rule: '%s'.

Severity: ERROR
Message: Unable to parse the rule ID from the provided definition of DIT structure rule: '%s'.

Severity: ERROR
Message: Error occurred while writing log record for logger %s: %s. Any further write errors will be ignored.

Severity: ERROR
Message: Error occurred while opening log file %s for logger %s: %s.

Severity: ERROR
Message: Error occurred while closing log file for logger %s: %s.

Severity: ERROR
Message: Error occurred while flushing writer buffer for logger %s: %s.

Severity: ERROR
Message: Error occurred while listing log files named by policy with initial file name %s.

Severity: ERROR
Message: Error occurred while obtaining free disk space in the partition containing log file %s: %s.

Severity: ERROR
Message: Error occurred while enforcing retention policy %s for logger %s: %s.

Severity: ERROR
Message: Error while creating or updating common audit log publisher %s: %s.

Severity: ERROR
Message: Error while adding common audit log publisher %s, the publisher has an unsupported handler type.

Severity: ERROR
Message: Error while reading JSON configuration file %s while creating common audit external log publisher %s: %s.

Severity: ERROR
Message: Error while creating common audit external log publisher %s: %s.

Severity: ERROR
Message: Error while creating common audit log publisher %s: %s.

Severity: ERROR
Message: Error while adding common audit log publisher %s, the publisher defines an unsupported log rotation policy %s.

Severity: ERROR
Message: Error while adding common audit log publisher %s, the publisher defines an unsupported log retention policy %s.

Severity: ERROR
Message: Error while processing common audit log publisher %s, this type of log publisher is unsupported.

Severity: ERROR
Message: Error while processing common audit log publisher %s, delimiter char '%s' should not contains more than one character.

Severity: ERROR
Message: Error while processing common audit log publisher %s, quote char '%s' should not contains more than one character.

Severity: ERROR
Message: Error while processing common audit log publisher %s, time of the day value '%s' for fixed time log rotation policy is not valid, it should use a 24-hour format "HHmm" : %s.

Severity: ERROR
Message: Error while processing a log event for common audit: %s.

Severity: ERROR
Message: Error while processing common audit log publisher %s, the keystore pin file %s is missing.

Severity: ERROR
Message: Error while processing common audit log publisher %s, the keystore pin file %s could not be read: %s.

Severity: ERROR
Message: Error while processing common audit log publisher %s, the keystore pin file %s contains an empty pin.

Severity: ERROR
Message: Error while processing common audit log publisher %s, the keystore file %s is missing.

Severity: ERROR
Message: Error while processing common audit log publisher %s, the keystore file %s could not be read: %s.

Severity: ERROR
Message: Error while processing common audit log publisher %s, the keystore file %s is empty.

Severity: ERROR
Message: The log file %s unexpectedly disappeared. It looks like an external system is also trying to manage the log files retention (either deleting or moving files away). This system configuration is incorrect: either ForgeRock DS manages the log file retention OR the external system does. Pick one only.

Severity: ERROR
Message: The message with ID %d has been generated %d times in the last second: %s.

Severity: ERROR
Message: The configured DN is already used by another domain.

Severity: ERROR
Message: Replication Server failed to start : could not bind to the listen port : %d. Error : %s.

Severity: ERROR
Message: Unknown operation type : %s.

Severity: ERROR
Message: Internal Error : Operation %s change number %s was not found in local change list.

Severity: ERROR
Message: Internal Error : Operation %s change number %s was not found in remote change list.

Severity: ERROR
Message: The replication server failed to start because the database %s could not be read : %s.

Severity: ERROR
Message: An Exception was caught while replaying operation %s %s (%s) : %s.

Severity: ERROR
Message: Error %s when searching for server state %s : %s base dn : %s.

Severity: ERROR
Message: Caught IOException while sending topology info (for update) on domain %s for %s server %s : %s.

Severity: ERROR
Message: Error when searching old changes from the database for base DN %s: %s.

Severity: ERROR
Message: Error trying to replay %s, operation could not be decoded: %s.

Severity: ERROR
Message: Error during the Replication Server database trimming or flush process. The Changelog service is going to shutdown: %s.

Severity: ERROR
Message: An unexpected error happened handling connection with %s. This connection is going to be closed.

Severity: ERROR
Message: A loop was detected while replaying operation: %s %s (%s) error %s.

Severity: ERROR
Message: An Exception was caught while testing existence or trying to create the directory for the Replication Server database : %s %s.

Severity: ERROR
Message: The current request is rejected due to an import or an export already in progress for the same data.

Severity: ERROR
Message: On domain %s, initialization of server with serverId:%s has been requested from a server with an invalid serverId:%s. %s.

Severity: ERROR
Message: Invalid target for the export.

Severity: ERROR
Message: Domain %s: the server with serverId=%s is unreachable.

Severity: ERROR
Message: No domain matches the provided base DN '%s'.

Severity: ERROR
Message: Multiple domains match the base DN provided.

Severity: ERROR
Message: The provider class does not allow the operation requested.

Severity: ERROR
Message: Duplicate server IDs found: replica '%s' for domain '%s' tried to connect from '%s', but replica '%s' is already connected from '%s'. Make sure the two replicas are configured with different server IDs.

Severity: ERROR
Message: Duplicate server IDs found: replication server '%s' tried to connect from '%s', but replication server '%s' is already connected from '%s'. Make sure the two replication servers are configured with different server IDs.

Severity: ERROR
Message: Entry %s was containing some unknown historical information, This may cause some inconsistency for this entry.

Severity: ERROR
Message: A conflict was detected but the conflict information could not be added to entry %s. Conflict with %s %s, Result: %s.

Severity: ERROR
Message: An error happened trying to rename a conflicting entry. DN: %s, Operation: %s, Result: %s.

Severity: ERROR
Message: The Replication is configured for suffix %s but was not able to connect to any Replication Server.

Severity: ERROR
Message: An unexpected error occurred while sending an Error Message to %s. This connection is going to be closed and reopened.

Severity: ERROR
Message: An unexpected error occurred while sending a Message to %s. This connection is going to be closed and reopened.

Severity: ERROR
Message: Could not replay operation %s %s with ChangeNumber %s error %s %s.

Severity: ERROR
Message: The entry %s has historical information for attribute %s which is not defined in the schema. This information will be ignored.

Severity: ERROR
Message: The Replication Server socket could not be closed : %s.

Severity: ERROR
Message: The thread listening on the replication server port could not be stopped : %s.

Severity: ERROR
Message: An unexpected error occurred when searching for generation id for domain "%s": %s.

Severity: ERROR
Message: An unexpected error occurred when looking for the replicated backend : %s. It may be not configured or disabled.

Severity: ERROR
Message: An unexpected error occurred when searching in %s for the generation ID : %s.

Severity: ERROR
Message: An unexpected error occurred when updating generation ID for domain "%s": %s.

Severity: ERROR
Message: The following error has been received : %s.

Severity: ERROR
Message: Initialization cannot be done because import is not supported by the backend %s.

Severity: ERROR
Message: Initialization cannot be done because export is not supported by the backend %s.

Severity: ERROR
Message: Initialization cannot be done because the following error occurred while locking the backend %s : %s.

Severity: ERROR
Message: Replication server caught exception while listening for client connections: %s.

Severity: ERROR
Message: While clearing the database %s , the following error happened: %s.

Severity: ERROR
Message: An unexpected error occurred when testing existence or creating the replication backend : %s.

Severity: ERROR
Message: An error occurred when searching for %s : %s.

Severity: ERROR
Message: The base DN %s is not stored by any of the Directory Server backend.

Severity: ERROR
Message: An Exception was caught while replaying replication message : %s.

Severity: ERROR
Message: Caught exception publishing fake operations for domain %s : %s.

Severity: ERROR
Message: Caught exception computing fake operations for domain %s for replication server %s : %s.

Severity: ERROR
Message: For replicated domain %s, in server with serverId=%s, the generation ID could not be set to value %s in the rest of the topology because this server is NOT connected to any replication server. You should check in the configuration that the domain is enabled and that there is one replication server up and running.

Severity: ERROR
Message: Directory server DS(%s) encountered an unexpected error while connecting to replication server %s for domain "%s": %s.

Severity: ERROR
Message: DN sent by remote replication server: %s does not match local replication server one: %s.

Severity: ERROR
Message: DN sent by replication server: %s does not match local directory server one: %s.

Severity: ERROR
Message: Caught IOException while forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %s.

Severity: ERROR
Message: Computed invalid initial status: %s in DS replication domain %s with server id %s.

Severity: ERROR
Message: Replication server received invalid initial status: %s for replication domain %s from server id %s.

Severity: ERROR
Message: Received invalid requested status %s in DS replication domain %s with server id %s.

Severity: ERROR
Message: Could not compute new status in RS replication domain %s for server id %s. Was in %s status and received %s event.

Severity: ERROR
Message: Could not compute new status in DS replication domain %s with server id %s. Was in %s status and received %s event.

Severity: ERROR
Message: Caught IOException while changing status for domain %s and serverId: %s after reset for generation id: %s.

Severity: ERROR
Message: Received change status message does not come from a directory server (dn: %s, server id: %s, msg: %s).

Severity: ERROR
Message: Received invalid new status %s in RS for replication domain %s and directory server id %s.

Severity: ERROR
Message: Replication broker with dn %s and server id %s failed to signal status change because of: %s.

Severity: ERROR
Message: Caught IOException while changing status for domain %s and serverId: %s from status analyzer: %s.

Severity: ERROR
Message: The generation ID could not be reset for domain %s.

Severity: ERROR
Message: The Replication was not started on base-dn %s : %s.

Severity: ERROR
Message: Replication protocol error. Bad message type. %s received, %s required.

Severity: ERROR
Message: The fractional replication ldif import plugin is configured with invalid plugin type %s. Only the ldifImport plugin type is allowed.

Severity: ERROR
Message: An error occurred when accessing the change number database : %s.

Severity: ERROR
Message: The initialization failed because the domain %s is not connected to a replication server.

Severity: ERROR
Message: Could not retrieve the configuration for a replication domain matching the entry %s.

Severity: ERROR
Message: The connection from this replication server RS(%s) to replication server RS(%s) at %s for domain "%s" has failed.

Severity: ERROR
Message: Full resync required. Reason: The provided cookie contains unknown replicated domain %s. Current starting cookie <%s>.

Severity: ERROR
Message: Full resync required. Reason: The provided cookie is older than the start of historical in the server for the replicated domain : %s.

Severity: ERROR
Message: Invalid syntax for the provided cookie '%s'.

Severity: ERROR
Message: Domain %s (server id: %s) : remote exporter server disconnection (server id: %s ) detected during initialization.

Severity: ERROR
Message: During initialization from a remote server, the following error occurred : %s.

Severity: ERROR
Message: Connection failure with Replication Server %s during import.

Severity: ERROR
Message: Bad msg id sequence during import. Expected:%s Actual:%s.

Severity: ERROR
Message: The following servers did not acknowledge initialization in the expected time for domain %s. They are potentially down or too slow. Servers list: %s.

Severity: ERROR
Message: The following servers did not end initialization being connected with the right generation (%s). They are potentially stopped or too slow. Servers list: %s.

Severity: ERROR
Message: When initializing remote server(s), connection to Replication Server with serverId=%s is lost.

Severity: ERROR
Message: When initializing remote server(s), the initialized server with serverId=%s is potentially stopped or too slow.

Severity: ERROR
Message: When sending a new initialization request for an initialization from a remote server, the following error occurred %s. The initial error was : %s.

Severity: ERROR
Message: Error while trying to solve conflict with DN : %s ERROR : %s.

Severity: ERROR
Message: The connection from this replication server RS(%s) to directory server DS(%s) at %s for domain "%s" has failed.

Severity: ERROR
Message: Could not create replica database because the changelog database is shutting down.

Severity: ERROR
Message: Could not add change %s to replicaDB %s %s because flushing thread is shutting down.

Severity: ERROR
Message: Error when retrieving changelog state from root path '%s' : IO error on domain directory '%s' when retrieving list of server ids.

Severity: ERROR
Message: Could not get or create replica DB for base DN '%s', serverId '%s', generationId '%d': %s.

Severity: ERROR
Message: Could not get or create change number index DB in root path '%s', using path '%s'.

Severity: ERROR
Message: Could not delete generation id file '%s' for DN '%s': %s.

Severity: ERROR
Message: Could not create directory '%s' for server id %s: %s.

Severity: ERROR
Message: Could not create generation id file '%s': %s.

Severity: ERROR
Message: Could not read server id filename because it uses a wrong format, expecting '[id].server' where [id] is numeric but got '%s'.

Severity: ERROR
Message: Could not read generation id because it uses a wrong format, expecting a number but got '%s'.

Severity: ERROR
Message: Could not open log file '%s' for write.

Severity: ERROR
Message: Could not open a reader on log file '%s': %s.

Severity: ERROR
Message: Could not decode a record from data read in log file '%s'.

Severity: ERROR
Message: Could not delete log files: %s.

Severity: ERROR
Message: Could not create log file '%s'.

Severity: ERROR
Message: Could not add record '%s' in log file '%s'.

Severity: ERROR
Message: Could not synchronize written records to file system for log file '%s'.

Severity: ERROR
Message: Could not seek to position %d for reader on log file '%s'.

Severity: ERROR
Message: Could not create root directory '%s' for log file: %s.

Severity: ERROR
Message: Could not decode DN from domain state file '%s', from line '%s'.

Severity: ERROR
Message: Could not read domain state file '%s'. The replication server cannot continue, it should be restored from a backup. Cause was : %s.

Severity: ERROR
Message: There is a mismatch between domain state file and actual domain directories found in file system. Expected domain ids : %s. Actual domain ids found in file system: %s.

Severity: ERROR
Message: Could not create a new domain id %s for domain DN %s and save it in the domain state file. Replication will continue, but if the domain state file cannot be written when stopping the server, it should be restored from backup. Cause was : %s.

Severity: ERROR
Message: Could not decode the key from string [%s].

Severity: ERROR
Message: Could not initialize the log '%s' : %s.

Severity: ERROR
Message: Could not retrieve key bounds from log file '%s'.

Severity: ERROR
Message: Could not retrieve read-only log files from log '%s'.

Severity: ERROR
Message: While purging log, could not delete log file(s): '%s'.

Severity: ERROR
Message: The following log '%s' must be released but it is not referenced.

Severity: ERROR
Message: Could not read replica offline state file '%s' for domain %s, it should contain exactly one line corresponding to the offline CSN.

Severity: ERROR
Message: Could not read content of replica offline state file '%s' for domain %s.

Severity: ERROR
Message: Could not retrieve file length of log file '%s'.

Severity: ERROR
Message: An error occurred while recovering the replication change log file '%s'. The recovery has been aborted and this replication server will be removed from the replication topology. The change log file system may be read-only, full, or corrupt and must be fixed before this replication server can be used. The underlying error was: %s.

Severity: ERROR
Message: An error occurred when searching base DN '%s' with filter '%s' in changelog backend : %s.

Severity: ERROR
Message: An error occurred when retrieving attribute value for attribute '%s' for entry DN '%s' in changelog backend : %s.

Severity: ERROR
Message: Could not create file '%s' to store last log rotation time %d.

Severity: ERROR
Message: Could not delete file '%s' that stored the previous last log rotation time.

Severity: ERROR
Message: Cursor on log '%s' has been aborted after a purge.

Severity: ERROR
Message: Could not position and read newest record from log file '%s'.

Severity: ERROR
Message: The change number index could not be reset to start with %d in base DN '%s' because starting CSN '%s' does not exist in the change log.

Severity: ERROR
Message: The change number could not be reset to %d because the associated change with CSN '%s' has already been purged from the change log. Try resetting to a more recent change.

Severity: ERROR
Message: Change number indexing is disabled for replication domain '%s'.

Severity: ERROR
Message: Cannot decode change-log record with version %x.

Severity: ERROR
Message: Cannot start total update in domain "%s" from this directory server DS(%s): no remote directory servers found.

Severity: ERROR
Message: Cannot start total update in domain "%s" from this directory server DS(%s): cannot find remote directory server DS(%s).

Severity: ERROR
Message: New replication connection from %s started with unexpected message %s and is being closed.

Severity: ERROR
Message: The directory server %s can no longer keep up with changes coming from replication server %s for base DN %s. Some missing changes have been purged by this replication server and the connection will be terminated. The directory server may fail-over to another replication server that has not purged the changes that it needs. If there is no replication server containing the missing changes then it will fail to connect to any replication server and will need to be reinitialized. (Underlying error is: %s).

Severity: ERROR
Message: The replication server %s can no longer keep up with changes coming from replication server %s for base DN %s. Some missing changes have been purged by this replication server and the connection will be terminated. The directory servers connected to this replication server may fail-over to another replication server that has not purged the changes that it needs. If there is no replication server containing the missing changes then the directory servers will fail to connect to any replication server and will need to be reinitialized. (Underlying error is: %s).

Severity: ERROR
Message: Invalid operator '%s' specified in historicalCsnRangeMatch extensible matching rule assertion.

Severity: ERROR
Message: Specified assertion '%s' for historicalCsnRangeMatch extensible matching rule does not conform to expected syntax. The assertion must specify a CSN range.

Severity: ERROR
Message: Specified CSNs '%s' and '%s' have two different server ids. The historicalCsnRangeMatch extensible matching rule requires CSNs to have the same server id.

Severity: ERROR
Message: Specified operators '%s' and '%s' do not specify a range for historicalCsnRangeMatch extensible matching rule.

Severity: ERROR
Message: Could not restart the Replication Server, bind to listen port %d failed : %s.

Severity: ERROR
Message: The replication server has detected that the file system containing the changelog is full. In order to prevent further problems, the replication server will disconnect from the replication topology and wait for sufficient disk space to be recovered, at which point it will reconnect.

Severity: ERROR
Message: The replication server connector thread could not be stopped : %s.

Severity: ERROR
Message: Unable to position reader to key '%s' using strategy '%s' on log '%s'. Changelog may be corrupted. Directory servers connected to this replication server may need to be reinitialized.

Severity: ERROR
Message: Assured replication is not supported anymore, it should be disabled on the topology.

Severity: ERROR
Message: Replication Server '%s' expected to negotiate with another Replication Server but got information for Directory Server '%s' instead. The connection will be closed.

Severity: ERROR
Message: Detected one or more corrupted records in log file '%s', this replication server will be removed from the replication topology. Recover the server from a valid filesystem backup if available or re-create it.

Severity: ERROR
Message: An error occurred while verifying integrity of log file '%s' : %s.

Severity: ERROR
Message: Cannot enable replication to server '%s' as this server’s ID '%s' is not a number between 1 and 32767.

Severity: ERROR
Message: An error occurred in session '%s' when trying to send a message to the socket: %s.

Severity: ERROR
Message: Could not convert value '%s' to long.

Severity: ERROR
Message: Could not find replica update message matching the index record. No more replica update messages with a csn newer than %s exist.

Severity: ERROR
Message: An exception was encountered while trying to encode a replication %s message for entry "%s" into an External Change Log entry: %s.

Severity: ERROR
Message: Unexpected message type when trying to create changelog entry for dn %s : %s".

Severity: ERROR
Message: %s in Replication Server=%s, an initialization message of type %s cannot be sent to its destination server. Details: routing table is empty.

Severity: ERROR
Message: %s message of type %s cannot be routed. Details: %s.

Severity: ERROR
Message: Error when trying to publish a message in '%s'. The connection is going to be closed and reopened.

Severity: ERROR
Message: Error when trying to publish a message in '%s'. The connection is going to be closed and reopened. Error: %s.

Severity: ERROR
Message: Error when initializing publisher of messages in '%s'.

Severity: ERROR
Message: Error when initializing publisher of messages in '%s'.

Severity: ERROR
Message: Directory server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %s.

Severity: ERROR
Message: Replication server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %s.

Severity: ERROR
Message: Error when enabling external changelog: %s.

Severity: ERROR
Message: The domain state file cannot be written. The server will shutdown but it should be restored from backup. Cause was : %s.

Severity: ERROR
Message: Some data in the domain state file '%s' in not of the form <domainId>[csn:csn]:<domainDN>, the replication server cannot start. Restore the server from backup.

Severity: ERROR
Message: Error when purging historical information for entry %s: %s.

Severity: ERROR
Message: Replication server failed to start because setting socket timeout on port %d caused error %s.

Severity: ERROR
Message: %s for domain %s cannot route message of type %s to all the replicas in the topology because none are reachable.

Severity: ERROR
Message: "%s for domain %s cannot route message of type %s to replica %s because it is unreachable. Reachable replicas: %s.

Severity: ERROR
Message: Server %s should be initialized but is not connected to the topology.

Severity: ERROR
Message: Changelog file %s should be version %d, but found version %d. Likely causes for this error: the server binaries were accidentally downgraded, data was restored from a file system backup taken on a more recent version of the server, or the changelog file was corrupted. If the server was downgraded, upgrade it. If the data was restored from a file system backup, restore it again from a recent, valid file system backup taken on the same version of the server. Otherwise, as last resort, remove the changelog by running the 'dsrepl clear-changelog' command and restart the server.

Severity: ERROR
Message: Peer '%s' has sent an update, but it is not allowed to do so by the configuration of this replication server. This update will be discarded. Check the configuration of both this replication server and its peer to determine if they have to be adjusted.

Severity: ERROR
Message: Replication peer certificate verification failed with error: %s.

Severity: ERROR
Message: Digest algorithm '%s' of fingerprint '%s' is not supported by the JVM.

Severity: ERROR
Message: The following replication server listener threads were unexpectedly stopped: %s. A server restart may be needed.

Severity: ERROR
Message: Cursor on log '%s' has been aborted after a clear.

Severity: ERROR
Message: Initialization of domain '%s' interrupted: no data received from the remote exporter '%s' for %s.

Severity: ERROR
Message: Publish of a replication message to server '%s' was interrupted.

Severity: ERROR
Message: The changelog no longer contains changes for domain '%s' which are required by replica '%s'. The replica will no longer receive replicated changes and must be re-initialized.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: The provided password is invalid.

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: SASL %s protocol error: %s.

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

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

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

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

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

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

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

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

Severity: ERROR
Message: ID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'.

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

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

Severity: ERROR
Message: ID string %s mapped to multiple users.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: The user account has been administratively disabled.

Severity: ERROR
Message: The user account is locked.

Severity: ERROR
Message: Entry %s cannot be parsed as a valid static group because it does not contain the groupOfEntries, groupOfNames or groupOfUniqueNames object classes.

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: An unexpected error occurred while attempting to read the instance key '%s' in "cn=admin data": %s.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: The provided password contained a word from the server’s dictionary.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: The processed ID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: Failed to create a SASL server for SASL mechanism %s.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: There is no private key entry in keystore '%s' used by file based key manager provider '%s'. TLS connections which rely on this key manager provider may fail. Ensure that keystore file contains at least one private key.

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

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

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

Severity: ERROR
Message: An error occurred while trying to create a trust manager factory to access the certificates in "cn=admin data": %s.

Severity: ERROR
Message: '%s' cannot list the secret files in directory '%s', all the secrets will be ignored: %s.

Severity: ERROR
Message: The file '%s' exceeds max size '%s'.

Severity: ERROR
Message: '%s' cannot decode the secret file '%s': %s.

Severity: ERROR
Message: Invalid excluded file name pattern: %s.

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

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

Severity: ERROR
Message: Unable to load JVM default keystore from system properties: %s.

Severity: ERROR
Message: An error occurred while reading information contained within key manager provider from configuration: "%s".

Severity: ERROR
Message: Unable to get the JVM default truststore: %s.

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

Severity: ERROR
Message: Could not map the provided certificate chain to a user because the matching user entry with DN '%s' does not contain an issuer DN matching the certificate issuer DN '%s'.

Severity: ERROR
Message: The baseDN '%s' specified as match base DN in the exact match identity mapper defined in configuration entry '%s', does not belong to a local backend.

Severity: ERROR
Message: The baseDN '%s' specified as match base DN in the regular expression identity mapper defined in configuration entry '%s', does not belong to a local backend.

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

Severity: ERROR
Message: File based key manager provider '%s' failed to load content from file '%s'. TLS connections which rely on this key manager provider may fail. Ensure that keystore file contains at least one private key compatible with the security providers. Security providers available in the running JVM are '%s'. The security provider used for loading key manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR
Message: File based key manager provider '%s' cannot load an X509 extended key manager from keystore file '%s'. TLS connections which rely on this key manager provider may fail. Security providers available in the running JVM are %s. The security provider used for loading key manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR
Message: File based key manager provider '%s' cannot load content from keystore file '%s'. TLS connections which rely on this key manager provider may fail. Restarting the server or the impacted connection handler may resolve this problem. Error detail: %s.

Severity: ERROR
Message: File based trust manager provider '%s' cannot load content from truststore file '%s'. TLS connections which rely on this trust manager provider may fail. Restarting the server or the impacted connection handler may resolve this problem. Error detail: %s.

Severity: ERROR
Message: File based trust manager provider '%s' failed to load content from file '%s'. TLS connections which rely on this trust manager provider may fail. Ensure that truststore file contains at least one private key compatible with the security providers. Security providers available in the running JVM are '%s'. The security provider used for loading trust manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR
Message: File based trust manager provider '%s' cannot load an X509 extended trust manager from truststore file '%s'. TLS connections which rely on this trust manager provider may fail. Security providers available in the running JVM are %s. The security provider used for loading trust manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR
Message: The %s SCRAM password storage scheme could not be initialized because the algorithm is not supported by the JVM.

Severity: ERROR
Message: An error occurred while attempting to decode the SCRAM credential value %s: %s.

Severity: ERROR
Message: SASL %s authentication is not possible for user '%s' because the user entry does not contain any SCRAM credentials.

Severity: ERROR
Message: An error occurred while attempting to retrieve the SCRAM credentials for user '%s' in order to perform SASL %s authentication: %s.

Severity: ERROR
Message: The %s SCRAM SASL mechanism handler could not be initialized because the algorithm is not supported by the JVM.

Severity: ERROR
Message: Error loading dictionary: %s.

Severity: ERROR
Message: The LDAP attribute description list plugin instance defined in configuration entry %s does not list any plugin types. This plugin must be configured to operate as a pre-parse search plugin.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Severity: ERROR
Message: The opration could not be processed due to an unexpected exception: '%s'.

Severity: ERROR
Message: An attempt was made to register the Graphite Monitor Reporter Plugin plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

Severity: ERROR
Message: Unable to report metrics to Graphite server '%s' because the Graphite server hostname resolution has failed. Ensure that the plugin configuration is correct and that the Graphite server is reachable. The Graphite plugin will be disabled until a change is performed in its configuration or the server restart.

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

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

Severity: ERROR
Message: The value %s cannot be decoded as a hexadecimal string because it does not have a length that is a multiple of two bytes.

Severity: ERROR
Message: The value %s cannot be decoded as a hexadecimal string because it contains an illegal character %c that is not a valid hexadecimal digit.

Severity: ERROR
Message: Unable to parse line %d ("%s") from the LDIF source because the line started with a space but there were no previous lines in the entry to which this line could be appended.

Severity: ERROR
Message: Unable to parse LDIF entry starting at line %d because the line "%s" does not include an attribute name.

Severity: ERROR
Message: Unable to parse LDIF entry starting at line %d because the first line does not contain a DN (the first line was "%s".

Severity: ERROR
Message: Unable to parse LDIF entry starting at line %d because an error occurred while trying to parse the value of line "%s" as a distinguished name: %s.

Severity: ERROR
Message: Unable to parse LDIF entry starting at line %d because it was not possible to base64-decode the DN on line "%s": %s.

Severity: ERROR
Message: Unable to parse LDIF entry %s starting at line %d because it was not possible to base64-decode the attribute on line "%s": %s.

Severity: ERROR
Message: Entry %s starting at line %d includes multiple values for single-valued attribute %s.

Severity: ERROR
Message: Entry %s read from LDIF starting at line %d is not valid because it violates the server’s schema configuration: %s.

Severity: ERROR
Message: The specified LDIF file %s already exists and the export configuration indicates that no attempt should be made to append to or replace the file.

Severity: ERROR
Message: Unable to parse LDIF entry %s starting at line %d because the value of attribute %s was to be read from a URL but the URL was invalid: %s.

Severity: ERROR
Message: Unable to parse LDIF entry %s starting at line %d because the value of attribute %s was to be read from URL %s but an error occurred while trying to read that content: %s.

Severity: ERROR
Message: The specified reject file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the file.

Severity: ERROR
Message: An error occurred while attempting to determine whether LDIF entry "%s" starting at line %d should be imported as a result of the include and exclude filter configuration: %s.

Severity: ERROR
Message: The provided sender address %s is invalid: %s.

Severity: ERROR
Message: The provided recipient address %s is invalid: %s.

Severity: ERROR
Message: The specified e-mail message could not be sent using any of the configured mail servers.

Severity: ERROR
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain the necessary :// component to separate the scheme from the rest of the URL.

Severity: ERROR
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain a protocol scheme.

Severity: ERROR
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain a host before the colon to specify the port number.

Severity: ERROR
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain a port number after the colon following the host.

Severity: ERROR
Message: The provided string "%s" cannot be decoded as an LDAP URL because the port number portion %s cannot be decoded as an integer.

Severity: ERROR
Message: The provided string "%s" cannot be decoded as an LDAP URL because the provided port number %d is not within the valid range between 1 and 65535.

Severity: ERROR
Message: The provided string "%s" cannot be decoded as an LDAP URL because the scope string %s was not one of the allowed values of base, one, sub, or subordinate.

Severity: ERROR
Message: The provided URL component "%s" could not be decoded because the percent character at byte %d was not followed by two hexadecimal digits.

Severity: ERROR
Message: The provided URL component "%s" could not be decoded because the character at byte %d was not a valid hexadecimal digit.

Severity: ERROR
Message: Cannot decode value "%s" as a named character set because it does not contain a colon to separate the name from the set of characters.

Severity: ERROR
Message: The named character set is invalid because it does not contain a name.

Severity: ERROR
Message: The named character set is invalid because the provide name "%s" has an invalid character at position %d. Only ASCII alphabetic characters are allowed in the name.

Severity: ERROR
Message: Cannot decode value "%s" as a named character set because it does not contain a name to use for the character set.

Severity: ERROR
Message: Cannot decode value "%s" as a named character set because there are no characters to include in the set.

Severity: ERROR
Message: Unable to set permissions for file %s because it does not exist.

Severity: ERROR
Message: One or more exceptions were thrown in the process of updating the file permissions for %s. Some of the permissions for the file may have been altered.

Severity: ERROR
Message: The provided string %s does not represent a valid UNIX file mode. UNIX file modes must be a three-character string in which each character is a numeric digit between zero and seven.

Severity: ERROR
Message: The specified skip file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the file.

Severity: ERROR
Message: Skipping entry %s because the DN is not one that should be included based on the include and exclude branches/filters.

Severity: ERROR
Message: The embedded server with server root '%s' cannot be started because it is already running.

Severity: ERROR
Message: Skipping entry %s because the DN is excluded by the exclude branch "%s".

Severity: ERROR
Message: Skipping entry %s because the DN is excluded by the exclude filter "%s".

Severity: ERROR
Message: Skipping entry %s because the DN is not included by any include branches.

Severity: ERROR
Message: Skipping entry %s because the DN is not included by any include filters.

Severity: ERROR
Message: Rejecting entry %s because it was rejected by a plugin.

Severity: ERROR
Message: Rejecting entry %s because it was rejected by a plugin: %s.

Severity: ERROR
Message: Unable to parse LDIF entry %s starting at line %d because it has an invalid binary option for attribute %s.

Severity: ERROR
Message: Skipping entry %s because the following error was received when reading its attributes: %s.

Severity: ERROR
Message: An error occurred while attempting to obtain a list of the files in directory %s to include in the backup: %s.

Severity: ERROR
Message: An error occurred while attempting to extract server archive '%s' before setup of embedded server with server root '%s': %s.

Severity: ERROR
Message: An error occurred while attempting to rebuild index of embedded server with server root '%s': %s.

Severity: ERROR
Message: An error occurred while attempting to start the embedded server with server root '%s' : %s.

Severity: ERROR
Message: An error occurred while attempting to upgrade the embedded server with server root '%s' : %s.

Severity: ERROR
Message: An error occurred while attempting to retrieve an internal connection to the server with the user DN '%s'.

Severity: ERROR
Message: The setup from an archive can only be done with a server root directory named after the root directory contained in the archive: '%s'. The provided server root was: '%s'.

Severity: ERROR
Message: An error occurred while attempting to initialize the configuration framework or to read the configuration file '%s'.

Severity: ERROR
Message: An error occurred while attempting to import LDIF file '%s' into embedded server with server root '%s'. Import LDIF task state was '%s'. You can look at the task logs printed on the embedded server output stream for more details.

Severity: ERROR
Message: An error occurred while attempting to import LDIF file '%s' into embedded server with server root '%s': '%s'.

Severity: ERROR
Message: An error occurred while attempting to rebuild index of embedded server with server root '%s'. Rebuild task state was '%s'. You can look at the task logs printed on the embedded server output stream for more details.

Severity: ERROR
Message: An error occurred while attempting to retrieve the configuration version of the directory server: '%s'.

Severity: ERROR
Message: An error occurred while attempting to retrieve the data version of the directory server: '%s'.

Severity: ERROR
Message: An error occurred while initializing configuration of embedded server with server root '%s': %s.

Severity: ERROR
Message: The directory to move %s does not exist.

Severity: ERROR
Message: The directory to move %s exists but is a file.

Severity: ERROR
Message: The target directory %s already exists.

Severity: ERROR
Message: Configuration error: an LDAP port or an LDAPS port must be configured before finishing configuring the embedded server.

Severity: ERROR
Message: An error occurred while attempting to write the monitor user entry: %s.

Severity: ERROR
Message: Unable to add one or more files to the server schema because no schema file names were provided in attribute %s of task entry %s.

Severity: ERROR
Message: Unable to add one or more files to the server schema because the specified schema file %s does not exist in schema directory %s.

Severity: ERROR
Message: Unable to add one or more files to the server schema because an error occurred while attempting to determine whether file %s exists in schema directory %s: %s.

Severity: ERROR
Message: An error occurred while attempting to load the contents of schema file %s into the server schema: %s.

Severity: ERROR
Message: Unable to add one or more files to the server schema because the server was unable to obtain a write lock on the schema entry %s after multiple attempts.

Severity: ERROR
Message: You do not have sufficient privileges to modify the server schema.

Severity: ERROR
Message: You do not have sufficient privileges to initiate a Directory Server backup or backup purge.

Severity: ERROR
Message: You do not have sufficient privileges to initiate a Directory Server restore.

Severity: ERROR
Message: You do not have sufficient privileges to initiate an LDIF import.

Severity: ERROR
Message: You do not have sufficient privileges to initiate an LDIF export.

Severity: ERROR
Message: You do not have sufficient privileges to initiate a Directory Server restart.

Severity: ERROR
Message: You do not have sufficient privileges to initiate a Directory Server shutdown.

Severity: ERROR
Message: An error occurred while attempting to notify a synchronization provider of type %s about the schema changes made by the add schema file task: %s.

Severity: ERROR
Message: You do not have sufficient privileges to initiate an index rebuild.

Severity: ERROR
Message: Invalid DN provided to the Initialize task: %s.

Severity: ERROR
Message: Only users with the SERVER_LOCKDOWN privilege may place the server in lockdown mode.

Severity: ERROR
Message: Only users with the SERVER_LOCKDOWN privilege connected from a loopback address may place the server in lockdown mode.

Severity: ERROR
Message: Only users with the SERVER_LOCKDOWN privilege may cause the server to leave lockdown mode.

Severity: ERROR
Message: Only users with the SERVER_LOCKDOWN privilege connected from a loopback address may cause the server to leave lockdown mode.

Severity: ERROR
Message: You do not have sufficient privileges to terminate client connections.

Severity: ERROR
Message: Unable to decode value %s as an integer connection ID.

Severity: ERROR
Message: Attribute %s must be provided to specify the connection ID for the client to disconnect.

Severity: ERROR
Message: Unable to decode value %s as an indication of whether to notify the client before disconnecting it. The provided value should be either 'true' or 'false'.

Severity: ERROR
Message: There is no client connection with connection ID %s.

Severity: ERROR
Message: Invalid generation ID provided with the Initialize task. Error was: %s.

Severity: ERROR
Message: Index option cannot be specified when the rebuildAll or rebuildDegraded option is used.

Severity: ERROR
Message: Attribute %s has an invalid value. Reason: %s.

Severity: ERROR
Message: No changelog database was found for baseDN '%s'. Either the baseDN is not replicated or its changelog has not been enabled in this server.

Severity: ERROR
Message: The change number index cannot be reset because this OpenDJ instance does not appear to be a replication server.

Severity: ERROR
Message: Invalid change number (%d) specified, it must be greater than zero.

Severity: ERROR
Message: Unable to reset the change number index: %s.

Severity: ERROR
Message: The changes made by the add schema file task failed schema validation: %s.

Severity: ERROR
Message: Invalid DN provided to the Initialize Target task: %s.

Severity: ERROR
Message: Invalid DN provided to the Purge Conflicts Historical task: %s.

Severity: ERROR
Message: Invalid DN provided to the Reset Generation ID task: %s.

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

Severity: ERROR
Message: No clear-text password was specified. Use --%s, --%s or --%s to specify the password to encode.

Severity: ERROR
Message: No password storage scheme was specified. Use the --%s argument to specify the storage scheme.

Severity: ERROR
Message: An unexpected error occurred while attempting to bootstrap the Directory Server client-side code: %s.

Severity: ERROR
Message: An error occurred while trying to load the Directory Server configuration: %s.

Severity: ERROR
Message: An error occurred while trying to load the Directory Server schema: %s.

Severity: ERROR
Message: An error occurred while trying to initialize the core Directory Server configuration: %s.

Severity: ERROR
Message: An error occurred while trying to initialize the Directory Server password storage schemes: %s.

Severity: ERROR
Message: No password storage schemes have been configured for use in the Directory Server.

Severity: ERROR
Message: Password storage scheme "%s" is not configured for use in the Directory Server.

Severity: ERROR
Message: An error occurred while attempting to encode the clear-text password: %s.

Severity: ERROR
Message: Unable to decode exclude filter string "%s" as a valid search filter: %s.

Severity: ERROR
Message: Unable to decode include filter string "%s" as a valid search filter: %s.

Severity: ERROR
Message: Unable to decode base DN string "%s" as a valid distinguished name: %s.

Severity: ERROR
Message: Multiple Directory Server backends are configured with the requested backend ID "%s".

Severity: ERROR
Message: None of the Directory Server backends are configured with the requested backend ID "%s".

Severity: ERROR
Message: Unable to decode exclude branch string "%s" as a valid distinguished name: %s.

Severity: ERROR
Message: Unable to decode wrap column value "%s" as an integer.

Severity: ERROR
Message: An error occurred while attempting to process the LDIF export: %s.

Severity: ERROR
Message: Unable to load class %s referenced in configuration entry %s for use as a Directory Server backend: %s.

Severity: ERROR
Message: Unable to create an instance of class %s referenced in configuration entry %s as a Directory Server backend: %s.

Severity: ERROR
Message: Unable to decode exclude filter string "%s" as a valid search filter: %s.

Severity: ERROR
Message: Unable to decode include filter string "%s" as a valid search filter: %s.

Severity: ERROR
Message: Imported branches or backend IDs can not span across multiple Directory Server backends.

Severity: ERROR
Message: None of the Directory Server backends are configured with the requested backend ID or base DNs that include the specified branches.

Severity: ERROR
Message: Unable to decode exclude branch string "%s" as a valid distinguished name: %s.

Severity: ERROR
Message: An error occurred while trying to open the rejects file %s for writing: %s.

Severity: ERROR
Message: An error occurred while attempting to process the LDIF import: %s.

Severity: ERROR
Message: An error occurred while attempting to perform index verification: %s.

Severity: ERROR
Message: Only one index at a time may be verified for cleanliness.

Severity: ERROR
Message: The backend does not support indexing.

Severity: ERROR
Message: The Directory Server backend with backend ID "%s" does not provide a mechanism for performing LDIF exports.

Severity: ERROR
Message: The Directory Server backend with backend ID %s does not provide a mechanism for performing LDIF imports.

Severity: ERROR
Message: Unable to decode include branch string "%s" as a valid distinguished name: %s.

Severity: ERROR
Message: Provided include base DN "%s" is not handled by the backend with backend ID %s.

Severity: ERROR
Message: Multiple Directory Server backends are configured to support base DN "%s".

Severity: ERROR
Message: None of the Directory Server backends are configured to support the requested base DN "%s".

Severity: ERROR
Message: Provided include base DN "%s" is not handled by the backend with backend ID %s.

Severity: ERROR
Message: An error occurred while attempting to initialize the crypto manager: %s.

Severity: ERROR
Message: An error occurred while attempting to initialize the subentry manager: %s.

Severity: ERROR
Message: An error occurred while attempting to acquire an exclusive lock for backend %s: %s. This generally means some other process is still using this backend (e.g., it is in use by the Directory Server or a backup or LDIF export is in progress). The LDIF import cannot continue.

Severity: ERROR
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The LDIF export cannot continue.

Severity: ERROR
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The index verification cannot continue.

Severity: ERROR
Message: Authentication password storage scheme "%s" is not configured for use in the Directory Server.

Severity: ERROR
Message: An error occurred while copying OpenDMK jar file '%s' to '%s': %s.

Severity: ERROR
Message: An error occurred while attempting to initialize the password policy components: %s.

Severity: ERROR
Message: ERROR: Unable to decode the provided stop time. It should be in the form YYYYMMDDhhmmssZ for UTC time or YYYYMMDDhhmmss for local time.

Severity: ERROR
Message: ERROR: An I/O error occurred while attempting to communicate with the Directory Server: %s.

Severity: ERROR
Message: Neither the %s or the %s argument was provided. One of these arguments must be given to specify the source for the LDIF data to be imported.

Severity: ERROR
Message: Unable to parse the specified file %s as a MakeLDIF template file: %s.

Severity: ERROR
Message: The provided password is not a valid encoded user password value: %s.

Severity: ERROR
Message: Could not find the service name for the server.

Severity: ERROR
Message: An unexpected error occurred starting the server as a windows service.

Severity: ERROR
Message: An unexpected error occurred stopping the server windows service.

Severity: ERROR
Message: You can only provide one of the following arguments: enableService, disableService, serviceState or cleanupService.

Severity: ERROR
Message: You must provide at least one of the following arguments: enableService, disableService or serviceState or cleanupService.

Severity: ERROR
Message: The server could not be enabled to run as a Windows service. The service name is already in use.

Severity: ERROR
Message: An unexpected error occurred trying to enable the server as a Windows service.%nCheck that you have administrator rights (only Administrators can enable the server to run as a Windows Service).

Severity: ERROR
Message: An unexpected error occurred trying to disable the server as a Windows service%nCheck that you have administrator rights (only Administrators can disable the server as a Windows Service).

Severity: ERROR
Message: An unexpected error occurred trying to retrieve the state of the server as a Windows service.

Severity: ERROR
Message: Could not find the service with name %s.

Severity: ERROR
Message: An unexpected error occurred cleaning up the service %s.

Severity: ERROR
Message: An error occurred while attempting to perform index rebuild: %s.

Severity: ERROR
Message: The backend does not support rebuilding of indexes.

Severity: ERROR
Message: At least one index must be specified for the rebuild process.

Severity: ERROR
Message: An error occurred while attempting to acquire a exclusive lock for backend %s: %s. This generally means that some other process has an lock on this backend or the server is running with this backend online. The rebuild process cannot continue.

Severity: ERROR
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The rebuild process cannot continue.

Severity: ERROR
Message: The specified LDIF file %s cannot be read.

Severity: ERROR
Message: An error occurred while trying to open the skip file %s for writing: %s.

Severity: ERROR
Message: The file '%s' could not be renamed to '%s': %s.

Severity: ERROR
Message: This tool may only be used on UNIX-based systems.

Severity: ERROR
Message: Unable to determine the path to the server root directory. Please ensure that the %s system property or the %s environment variable is set to the path of the server root directory.

Severity: ERROR
Message: An error occurred while attempting to generate the RC script: %s.

Severity: ERROR
Message: None of the Directory Server JE backends are configured with the requested backend ID %s.

Severity: ERROR
Message: None of the entry containers are configured with the requested base DN %s in backend %s.

Severity: ERROR
Message: Unable to decode base DN string "%s" as a valid distinguished name: %s.

Severity: ERROR
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has exclusive access to this backend (e.g., a restore or an LDIF import).

Severity: ERROR
Message: A sub-command must be specified.

Severity: ERROR
Message: The directory %s specified as the OPENDJ_JAVA_HOME path does not exist or is not a directory.

Severity: ERROR
Message: The argument '%s' is incompatible with '%s'.

Severity: ERROR
Message: Invalid menu item or task number '%s'.

Severity: ERROR
Message: Error retrieving task entry %s: %s.

Severity: ERROR
Message: There are no tasks with ID %s.

Severity: ERROR
Message: Error canceling task '%s': %s.

Severity: ERROR
Message: Error accessing logs for task '%s': %s.

Severity: ERROR
Message: Task at index %d is not cancelable.

Severity: ERROR
Message: There are no tasks defined with ID '%s'.

Severity: ERROR
Message: Task '%s' has finished and cannot be canceled.

Severity: ERROR
Message: State for task '%s' cannot be determined.

Severity: ERROR
Message: The start date/time must in YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time.

Severity: ERROR
Message: You have provided options for scheduling this operation as a task but options provided for connecting to the server’s tasks backend resulted in the following error: '%s'.

Severity: ERROR
Message: The option %s is only applicable when scheduling this operation as a task.

Severity: ERROR
Message: The value %s for option %s is not a valid email address.

Severity: ERROR
Message: The failed dependency action value %s is invalid. The value must be one of %s.

Severity: ERROR
Message: The failed dependency action option is to be used in conjunction with one or more dependencies.

Severity: ERROR
Message: Error: task %s is not in a cancelable state.

Severity: ERROR
Message: An error occurred while attempting to initialize server components to run the tool: %s.

Severity: ERROR
Message: The %s argument is not supported for online imports.

Severity: ERROR
Message: The specified start time '%s' has already passed.

Severity: ERROR
Message: The specified stop time '%s' has already passed.

Severity: ERROR
Message: The timeout of '%d' seconds has been reached. You can use the argument '--%s' to increase this timeout.

Severity: ERROR
Message: The value %s for threadCount cannot be parsed: %s.

Severity: ERROR
Message: Provided passwords don’t matched.

Severity: ERROR
Message: Cannot read password from the input: %s.