Package org.opends.messages
Class ServerMessages
java.lang.Object
org.opends.messages.ServerMessages
This file contains localizable message descriptors having the resource
name
org.opends.messages.server. This file was generated
automatically by the opendj-maven-plugin from the property file
org/opends/messages/server.properties and it should not be manually edited.-
Field Summary
FieldsModifier and TypeFieldDescriptionError %s when updating server state %s : %s base dn : %sRecovery interrupted because shutdown of replication domain has been requested/path/to/opendjNo plugin found to handle the storage scheme '%s'Access denied to file '%s'The '%s' backend files have been removed after restore failed. The backend is now emptyEither the --%s or --%s argument must be providedThe backup process failed with one or more errorsThe backup ID '%s' already exists{backup ID}Location containing backups: file-system path or URI for alternative storage mechanisms. File-system paths may be expressed as absolute or relative paths and are resolved relative to the current working directory when the tool is run in offline mode, or relative to the server instance directory when the tool is run in task mode. Read the documentation for further information regarding alternative backup storage mechanismsBackup file-system path or URI for alternative storage mechanisms. File-system paths may be expressed as absolute or relative paths and are resolved relative to the current working directory when the tool is run in offline mode, or relative to the server instance directory when the tool is run in task mode. Read the documentation for further information regarding alternative backup storage mechanismsBacking up file (%d/%d) '%s'Starting backup for backend '%s'Backup completed for backend '%s' with backup ID '%s'Cannot find backup with ID %sThe attempt to remove backend files from directory '%s' has failed, backend '%s' may contain corrupted data, please remove the files manuallyCannot compute the fingerprint for backend file '%s': %sCannot create the backend directory '%s' before restoring: %sCannot delete backend files from directory '%s': %sCannot delete corrupted file '%s'Cannot delete the backup lock file '%s', please remove this file manually: %sThere are no backups for backends %sCannot read backend files in directory '%s': %sCannot read backup directory content: %sThe backends %s cannot be restored while the server is running. Please stop the server first and try again with the --offline optionDeleting corrupted file from backend directoryDeleting corrupted file from backup storageThe name of the backend to back up. Specify this option multiple times to backup multiple backends or skip this option to backup all the enabled backends that support backupsCannot 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)Cannot release the shared lock for backend '%s': %s. This lock should automatically be cleared when the backup process exits, so no further action should be requiredTake encrypted and signed backups of individual backends and send them to the desired locationThere are no enabled backends that support backup operationThe backup command was interruptedThe following backends do not support backups: %s. Here is the list of enabled backends that support backups: %sThe following backends do not exist or are disabled: %s. Here is the list of enabled backends that support backups: %sBackup and restore backends, manage backup filesBackup and restore backendsThe directory does not exist'%s' is not a valid name for a directoryNot a directoryAn error occurred while attempting to backup backend '%s': %sAn error occurred while attempting to restore backend '%s' with backup ID '%s': %sCannot continue purging backups, errors were encountered while reading the list of available backups: %sCannot continue the restore process, errors were encountered while reading the list of available backups: %sFile '%s' is corrupted: %sFile '%s' is missingIO error: %sProblem with file '%s' : %sBackend name: %sShow only backups taken from the provided backendBackup ID: %s%s backup(s) cannot be restoredBadBackup Date: %sList the backups at the specified locationError: %sFound %s backup(s) that cannot be fully identified due to the following error(s):Show only the last backup for each backendThere are no backups with the requested characteristicsFound %s backup(s) with the requested characteristicsServer ID: %sShow only backups taken from the provided server{server ID}Status: %sVerified{backup location}signature does not matchBackup still in progress, new files have been createdIndicates that the command will operate independently of the server process. It will run regardless of whether the server is started or stopped. When using this option with the %1$s sub-command, the server must be stopped; also as the command will write to server files, you should run the command as a user having the same filesystem permissions as the user running the server. Using this option with the %2$s sub-command when the server is running is possible and supported. With JE Backends, the integrity of the backup is ensured by the process. With LDIF backends, avoid simultaneous changes to the backendsOperation was interruptedThe option '--%s' can only be used with the option '--%s'At least one of these options must be declared: %sAn error occurred while attempting to purge backup files starting with '%s': %sPurge only backups of the specified backend. Specify this option multiple times to allow purging backups of different backends. Skip this option to allow purging backups of all backends. This can only be used with options '--%s' or '--%s'{backend name}The ID of the backup that should be deleted. Specify this option multiple times to purge multiple backupsBackup purge process failed with one or more errorsDelete one or more backupsAn error occurred while attempting to purge the backup '%s': %sMust be used with the '--%s' option, indicates that the last backup of each backend can be deleted if older than the provided durationThe number of backups to keep per backend. Use this option to keep the n latest backups of each backend and delete the others. If n=0, all the backups will be removed{number of backups}Invalid value for '%s': %s'%d' is not allowed: the value must be equal or greater than 0Delete backups that are older than the provided duration. The latest backup of each backend will always be kept unless the '--%s' option is also provided. Duration examples: '12 hours', '3 days', '1y'{duration}Purging backup (%d/%d) '%s'Purge completed successfullyFound backup IDs that correspond to the same backend name: %s. Make sure each backup ID corresponds to a distinct backendRestore the last backup of the provided backend. Specify this option multiple times to restore multiple backendsRestore the backup having the provided ID. Specify this option multiple times to restore multiple backendsCannot 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)Cannot release the exclusive lock for backend '%s': %s. This lock should automatically be cleared when the restore process exits, so no further action should be requiredThe restore process failed with one or more errorsRestore one or more backends. In order to decrypt and verify signatures on backup files, the server must have access to the master key pair used to encrypt and sign the files when they were createdThe backends %s cannot be restored because they do not exist or are disabledRestoring file (%d/%d) '%s'Starting restore for backend '%s' with backup ID '%s'Restore completed for backend '%s' with backup ID '%s'Cannot enable backend '%s' after restoring: %sThe storage property '%s' has several values while it can have only one. The provided properties string was: "%s"Assigns a value to a storage property where PROP is the name of the property and VALUE is the single value to be assigned. Specify the same property multiple times in order to assign more than one value to it{PROP:VALUE}Unable to access the backup storage: %sunexpected contentVerifying file (%d/%d) '%s'Verify backups completeness, integrity and whether they can be decryptedUser authentication is mandatory to access server monitoring informationEntry %s cannot be added because the request contained an LDAP assertion control and the associated filter did not match the contents of the provided entryEntry %s can not be added because BER encoding of %s attribute is not supportedEntry %s cannot be added because it includes attribute %s which is defined as NO-USER-MODIFICATION in the server schemaThe entry %s cannot be added due to insufficient access rightsUnable to add entry %s because the backend that should hold that entry is configured in read-only modeThe 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 protocolEntry %s cannot be added because the server failed to obtain a write lock for this entry after multiple attemptsYou do not have sufficient privileges to add entries that include privilegesThe entry '%s' cannot be added because an entry with that name already existsThe 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 ServerThe provided entry %s cannot be added because its suffix is not defined as one of the suffixes within the Directory ServerEntry %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 entryEntry %s cannot be added because its parent entry %s does not exist in the serverThe entry '%s' cannot be added because its parent entry does not existEntry %s cannot be added because its parent entry %s is a subentryUnable to add entry %s because the Directory Server is configured in read-only modeAn error occurred during conflict resolution synchronization processing for the add operation with connection ID %d and operation ID %d: %sAn error occurred during postoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %sAn error occurred during preoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %sEntry %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 operationAn error occurred while trying to create a trust manager factory to access the certificates in "cn=admin data": %sAn unexpected error occurred while attempting to read the instance key '%s' in "cn=admin data": %sAn unexpected error occurred while accessing the instance keys in "cn=admin data": %sAssured replication is not supported anymore, it should be disabled on the topologyThe provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not allowed in an attribute nameThe 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 nameThe 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 OIDThe provided value "%s" could not be parsed as a valid distinguished name because it contained an RDN containing an empty attribute nameThe 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"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'The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was a comma or semicolonThe 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 digitThe 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 digitsThe provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not validThe 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 digitThe 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'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 markThe provided value "%s" could not be parsed as a valid subtree specificationThere is no index configured for attribute type '%s'The provided password was found in another attribute in the user entryUnwilling to add entry "%s" because add operations are not supported in the "%s" backendConfidentiality cannot be disabled on suffix '%s' because the following indexes have confidentiality still enabled: %sThe 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 unlockedAn error occurred while attempting to register the base DNs %s in the Directory Server: %sConfiguration attribute ds-cfg-db-cache-percent has a value of %d%% but the JVM has only %d%% availableConfiguration attribute ds-cfg-db-cache-size has a value of %d but the JVM has only %d available. Consider using ds-cfg-db-cache-percentAn 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)Unable to decode base DN string "%s" as a valid distinguished name: %sNone of the Directory Server JE backends are configured with the requested backend ID %sNone of the entry containers are configured with the requested base DN %s in backend %sUnwilling to remove entry "%s" because delete operations are not supported in the "%s" backendEntry %s does not exist in the "%s" backendError while enabling confidentiality with cipher %s, %d bits: %sUnable to retrieve the requested entry from the "%s" backend because the provided DN was nullLDIF import and export operations are not supported in the "%s" backendThe "%s" backend does not support LDIF import operationsAn error occurred while trying to list the files to backup for backend '%s': %sUnwilling to rename entry "%s" because modify DN operations are not supported in the "%s" backendUnwilling to update entry "%s" because modify operations are not supported in the "%s" backendThe backend does not support indexingAn error occurred when searching for %s : %sAt key number %d, %s:Data decoder for printing is not available, should use hex dumpAn unexpected error occurred while attempting to initialize the backend '%s': %sAn error occurred while listing the base DNs: %sAn error occurred while listing indexes: %sAn unexpected error occurred while attempting to read and/or decode records from an index: %sAn error occurred while trying to execute %s: %sNo index exists with the requested name '%s' in base DN '%s' and backend '%s'No storage index exists with the requested name %s in backend %sCannot specify a maximum key both as a string and as an hexadecimal stringCannot specify a minimum key both as a string and as an hexadecimal stringAn error occurred while processing arguments: %sAn error occurred while attempting to obtain a list of the files in directory %s to include in the backup: %sThe requested admin API version '%s' is unsupported. This endpoint only supports the following admin API version(s): %sEntry %s was containing some unknown historical information, This may cause some inconsistency for this entryThe account has been locked as a result of too many failed authentication attempts. It may only be unlocked by an administratorThe account has been locked as a result of too many failed authentication attempts (time to unlock: %s)The user cannot bind due to insufficient access rightsUnable to process the simple bind request because it contained a bind DN but no password, which is forbidden by the server configurationRejecting a bind request because the account has been administratively disabledRejecting a bind request because the account has expiredRejecting a bind request because the account has been locked due to too many failed authentication attemptsRejecting a bind request because the account has been locked after remaining idle for too longRejecting a bind request because the account has been locked after the user's password was not changed in a timely manner after an administrative resetRejecting a SASL %s bind request for user %s because the password policy requires secure authenticationRejecting a simple bind request because the password policy requires secure authenticationUnable to bind to the Directory Server using simple authentication because that user does not have a passwordRejecting a bind request because that user's password is expiredUnable to process the bind request because it attempted to use an unknown SASL mechanism %s that is not available in the Directory ServerUnable to bind to the Directory Server because no such user exists in the serverRejecting 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 allowedThe password provided by the user did not match any password(s) stored in the user's entryUnable to process the non-root bind because the server is in lockdown modeUnable 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 operationThe 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": %sThe 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": %sBackend database cache preload for backend '%s' is not supported in this releaseThe Directory Server could not acquire an exclusive lock on file %s: %s. This generally means that another instance of this server is already runningA conflict was detected but the conflict information could not be added to entry %s. Conflict with %s %s, Result: %sThe Directory Server is currently running. The configuration may not be bootstrapped while the server is onlineAbandon requests cannot be canceledBind requests cannot be canceledCancel extended operations can not be canceledStart TLS extended operations cannot be canceledUnbind requests cannot be canceledAn error occurred while attempting to create the JMX MBean server that will be used for monitoring, notification, and configuration interaction within the Directory Server: %sCould not create replica database because the changelog database is shutting downUnable to decode base DN string "%s" as a valid distinguished name: %sCannot decode the provided control %s because an error occurred while attempting to decode the control value: %sInput stream ended unexpectedly while decoding entryCould not map the provided certificate chain to a user becausethe peer certificate issuer "%s" could not be decoded as an LDAP DN: %sCannot encode entry for writing on storage: %sAn error occurred while trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) from the Directory Server configuration: %sCannot properly use SHA-1 using the java provider. Verify java.security is properly configuredAn error occurred while initializing server backends: %sCannot initialize the configuration framework: %sAn error occurred while trying to initialize the core Directory Server configuration: %sAn error occurred while attempting to initialize the crypto manager: %sAn error occurred while attempting to initialize the password policy components: %sAn error occurred while attempting to initialize server components to run the tool: %sAn error occurred while initializing plugins: %sAn error occurred while trying to initialize the Directory Server password storage schemes: %sAn error occurred while attempting to initialize the subentry manager: %sUnable to create an instance of class %s referenced in configuration entry %s as a Directory Server backend: %s'%s' cannot list the secret files in directory '%s', all the secrets will be ignored: %sUnable to load class %s referenced in configuration entry %s for use as a Directory Server backend: %sAn error occurred while trying to load the Directory Server configuration: %sAn error occurred while trying to load the Directory Server schema: %sAn error occurred when trying to read the configuration version in %s : %sAn error occurred when trying to read the upgrade version in second line of file '%s' (%s)Error when searching old changes from the database for base DN %s: %sAn error happened trying to rename a conflicting entry. DN: %s, Operation: %s, Result: %sThe Directory Server is currently running. The environment configuration can not be altered while the server is onlineThe Directory Server may not be started before the configuration has been bootstrappedThe Directory Server may not be started while it is already running. Please stop the running instance before attempting to start it againSubsystem %s should be initialized firstReplication peer certificate verification failed with error: %sCould not find the "%s" command in "%s"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'Error when enabling external changelog: %sAn error occurred when retrieving attribute value for attribute '%s' for entry DN '%s' in changelog backend : %sCould not convert value '%s' to longCould not find replica update message matching the index record. No more replica update messages with a csn newer than %s existThe search cannot be processed because the external changelog is not configured to generate change numbers. Change the replication server configuration if change numbers are neededAn exception was encountered while trying to encode a replication %s message for entry "%s" into an External Change Log entry: %sAn error occurred when searching base DN '%s' with filter '%s' in changelog backend : %sUnexpected message type when trying to create changelog entry for dn %s: '%s'Could not position and read newest record from log file '%s'. Current thread is '%s'. Error was: %sThe domain state file cannot be written. The server will shutdown but it should be restored from backup. Cause was : %sCursor on log '%s' has been aborted after a clearCursor on log '%s' has been aborted after a purgeDetected 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 itAn unexpected error occurred while sending an Error Message to %s. This connection is going to be closed and reopenedAn unexpected error occurred while sending a Message to %s. This connection is going to be closed and reopenedCould not read generation id because it uses a wrong format, expecting a number but got '%s'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: %sCould not read replica offline state file '%s' for domain %s, it should contain exactly one line corresponding to the offline CSNAn error occurred while verifying integrity of log file '%s' : %sSome 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 backupError when retrieving changelog state from root path '%s' : IO error on domain directory '%s' when retrieving list of server idsUnable 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 reinitializedThe 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 logThe 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 changeCould not read server id filename because it uses a wrong format, expecting '[id].server' where [id] is numeric but got '%s'Cannot convert the filename '%s' to a valid change numberCannot convert the filename '%s' to a valid CSNThe output folder '%s' cannot be createdCannot list the changelog files in '%s': %sThe replication domain '%s' is not found. Make sure the domain is replicatedError while decoding the changelog file '%s' : %sAn error occurred when reading the replication server configuration entry '%s': %sThe provided change number '%s' is not validThe provided CSN '%s' is not validThe provided DN '%s' is invalidThe provided output folder '%s' doesn't existReplica DB folder '%s' not foundCould not add record '%s' in log file '%s': %sCould not get or create change number index DB in root path '%s', using path '%s': %sCould not create generation id file '%s': %sCould not create file '%s' to store last log rotation time %dCould not create root directory '%s' for log file: %sCould not create log file '%s': %sCould not get or create replica DB for base DN '%s', serverId '%s', generationId '%s': %sCould not create directory '%s' for server id %s: %sCould not decode DN from domain state file '%s', from line '%s'Could not decode the key from string [%s]Could not decode a record from data read in log file '%s'Could not delete generation id file '%s' for DN '%s': %sCould not delete file '%s' that stored the previous last log rotation timeCould not delete log files: %sWhile purging log, could not delete log file(s): '%s'Could not initialize the log '%s' : %sCould not open log file '%s' for write: %sCould not open a reader on log file '%s': %sCould not read domain state file '%s'. The replication server cannot continue, it should be restored from a backup. Cause was : %sCould not read content of replica offline state file '%s' for domain %sAn 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: %sCould not retrieve file length of log file '%s'Could not retrieve key bounds from log file '%s': %sCould not retrieve read-only log files from log '%s': %sCould not seek to position %d for reader on log file '%s'Could not synchronize written records to file system for log file '%s': %sCould 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 : %sChangelog 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 serverThe following log '%s' must be released but it is not referencedAn error occurred when accessing the change number database : %sThe 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 nameThe named character set is invalid because it does not contain a nameCannot decode value "%s" as a named character set because there are no characters to include in the setCannot decode value "%s" as a named character set because it does not contain a colon to separate the name from the set of charactersCannot decode value "%s" as a named character set because it does not contain a name to use for the character setThe provided character set definition '%s' is invalid because it contains character '%s' which has already been usedThe provided password contained character '%s' which is not allowed for use in passwordsThe provided character range definition '%s' is invalid because the value before the colon must be an integer greater or equal to zeroThe provided character set definition '%s' is invalid because the value before the colon must be an integer greater or equal to zeroThe provided character range definition '%s' is invalid because the range '%s' is missing the minusThe provided minimum required number of character sets '%d' is invalid because it is greater than the total number of defined character setsThe provided minimum required number of character sets '%d' is invalid because it must at least include all mandatory character setsThe provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character rangeThe provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character rangeThe provided character set definition '%s' is invalid because the provided character set is emptyThe provided character set definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character setThe provided character range definition '%s' is invalid because the range '%s' is too shortThe 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 %dThe 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 %dThe provided password did not contain characters from at least %d of the following character sets or ranges: %sThe provided character range definition '%s' is invalid because the range '%s' is reversedAn unexpected error occurred when testing existence or creating the replication backend : %sType %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 neededRequested cipher for a non existing cipher key: cryptographic services were not properly initialized, programming errorAttribute %s is set as confidential on a backend whose entries are still cleartext. Enable confidentiality on the backend firstError while creating or updating common audit log publisher %s: %sError while processing common audit log publisher %s, delimiter char '%s' should not contain more than one characterError while processing common audit log publisher %s, quote char '%s' should not contain more than one characterError while processing common audit log publisher %s, the keystore file %s could not be read: %sError while processing common audit log publisher %s, the keystore pin file %s could not be read: %sError while creating common audit external log publisher %s: %sError while reading JSON configuration file %s while creating common audit external log publisher %s: %sError while creating common audit log publisher %s: %sError 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" : %sError while processing common audit log publisher %s, the keystore file %s is emptyError while processing common audit log publisher %s, the keystore file %s is missingError while processing common audit log publisher %s, the keystore pin file %s contains an empty pinError while processing common audit log publisher %s, the keystore pin file %s is missingError while processing a log event for common audit: %sError while adding common audit log publisher %s, the publisher has an unsupported handler typeError while processing common audit log publisher %s, this type of log publisher is unsupportedError while adding common audit log publisher %s, the publisher defines an unsupported log retention policy %sError while adding common audit log publisher %s, the publisher defines an unsupported log rotation policy %sCannot 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 entryThe entry %s cannot be compared due to insufficient access rightsYou do not have sufficient privileges to access the server configurationThe specified entry %s does not exist in the Directory ServerCannot 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 operationUnable to decode the provided object class set because it used an undefined token %sUnable to decode the provided attribute because it used an undefined attribute description token %sAn error occurred while attempting to decode an attribute description token from the compressed schema definitions: %sAn error occurred while attempting to decode an object class set token from the compressed schema definitions: %sAn error occurred while attempting to store compressed schema information in the database: %sThe configuration for the account status notification handler defined in configuration entry %s was not acceptable: %sUnable to add a new account status notification handler entry with DN %s because there is already a notification handler registered with that DNAn error occurred while trying to initialize an instance of class %s as an account status notification handler as defined in configuration entry %s: %sThe configuration for the alert handler defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as an alert handler as defined in configuration entry %s: %sUnable to set the value for configuration attribute %s because the provided value %d is greater than the largest allowed value of %dUnable to set the value for configuration attribute %s because the provided value %d is less than the lowest allowed value of %dUnable to set the value for Boolean configuration attribute %s because the provided value %s was not either 'true' or 'false'Unable to set the value for integer configuration attribute %s because the provided value %s cannot be interpreted as an integer value: %sThe configuration for the trust manager provider defined in configuration entry %s was not acceptable: %sThe authorization mechanism defined in %s is referencing a non existing DN: %sAn error occurred while attempting to instantiate class %s referenced in the access control configuration entry %s: %sThe entry cn=Backends,cn=config does not appear to exist in the Directory Server configuration. This is a required entryUnable to configure the backend '%s' because one of its base DNs is the empty DNThe 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 disabledBackend config error when trying to delete an entry: %sAn error occurred while trying to initialize a backend loaded from class %s with the information in configuration entry %s: %s. This backend will be disabledThe 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 disabledInvalid UNIX file permissions %s does not allow read and write access to the backend database directory by the backendConfiguration 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.)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 disabledBig index for attribute '%s' cannot be created for matching rule '%s' because it is not an equality matching ruleAn error occurred while attempting to calculate a SHA-1 digest of file %s: %sCannot configure java.util.logging root logger level: %s. java.util.logging support is now disabledUnable 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 rootAn unexpected error occurred while trying to register the configuration handler base DN "%s" as a private suffix with the Directory Server: %sThe configuration for the certificate mapper defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as a certificate mapper as defined in configuration entry %s: %s%s.%s returned a result of null for entry %s%s.%s failed for entry %s: result code=%s, admin action required=%b, messages="%s"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 disabledThe core schema provider defined by '%s' has been disabled. The core schema must always be enabledAn 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 disabledAn unexpected error occurred that prevented the server from installing its default entry cache framework: %sThe configuration for the entry cache defined in configuration entry %s was not acceptable: the entry cache level %d is already in useThe configuration for the entry cache defined in configuration entry %s was not acceptable: %sError creating SSL socket factory: %sAn error occurred while trying to initialize an instance of class %s as an extended operation handler as defined in configuration entry %s: %sClass %s specified in configuration entry %s does not contain a valid extended operation handler implementation: %sEntry %s cannot be added to the Directory Server configuration because another configuration entry already exists with that DNThe 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: %sAn unexpected error occurred while attempting to add configuration entry %s as a child of entry %s: %sYou do not have sufficient privileges to perform add operations in the Directory Server configurationEntry %s cannot be added to the Directory Server configuration because its parent entry %s does not existEntry %s cannot be added to the Directory Server configuration because that DN does not have a parentThe 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: %sAn error occurred while trying to create the configuration archive directory %s: %sAn error occurred while attempting to open the configuration file %s for reading: %sAn error occurred while trying to write the current configuration to the configuration archive: %sThe 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: %sAn unexpected error occurred while attempting to remove configuration entry %s as a child of entry %s: %sEntry %s cannot be removed from the Directory Server configuration because the specified entry has one or more subordinate entriesYou do not have sufficient privileges to perform delete operations in the Directory Server configurationEntry %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 allowedEntry %s cannot be removed from the Directory Server configuration because that DN does not have a parentEntry %s cannot be removed from the Directory Server configuration because the specified entry does not existEntry %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: %sThe specified configuration file %s does not exist or is not readableAn unexpected error occurred while attempting to process the Directory Server configuration file %s: %sThe 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 rootYou do not have sufficient privileges to perform modify DN operations in the Directory Server configurationModify DN operations are not allowed in the Directory Server configurationThe 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: %sAn unexpected error occurred while attempting to modify configuration entry %s as a child of entry %s: %sYou do not have sufficient privileges to perform modify operations in the Directory Server configurationEntry %s cannot be modified because the specified entry does not existYou do not have sufficient privileges to change the set of default root privilegesEntry %s cannot be modified because one of the configuration change listeners registered for that entry rejected the change: %sConfiguration entry %s cannot be modified because the change would alter its structural object classYou do not have sufficient privileges to perform search operations in the Directory Server configurationThe Directory Server configuration may not be altered by importing a new configuration from LDIFAn error occurred while attempting to export the new Directory Server configuration to file %s: %sAn error occurred while attempting to rename the new Directory Server configuration from file %s to %s: %sAn unexpected error occurred while trying to write configuration entry %s to LDIF: %sThe HTTP endpoint configuration defined in %s is referencing mutually exclusive authorization DNs %s and %sAn error occurred while trying to initialize an instance of class %s as an HTTP endpoint as defined in configuration entry %s: %sThe HTTP endpoint configuration defined in %s is referencing a non existing authorization DN %sThe HTTP endpoint configuration defined in %s is invalid: %sAn error occurred while starting the HTTP endpoint as defined in configuration entry %s: %sThe configuration for the identity mapper defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as an identity mapper as defined in configuration entry %s: %sThe attribute '%s' cannot enable confidentiality for keys and values at the same timeThe time-to-live (TTL) feature can only be enabled for generalized time ordering indexesIndex 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 schemaIndex for attribute '%s' cannot be created because the configuration contains an included attribute value '%s' which appears to be invalid according to the schema: %sThe metric name pattern to exclude '%s' cannot be parsed as a valid regular expression due to the following error: '%s'The metric name pattern to include '%s' cannot be parsed as a valid regular expression due to the following error: '%s'The smtp-server value '%s' is invalid: %sAn error occurred while trying to parse and validate Berkeley DB JE property %s: the property is already defined for this componentAn error occurred while trying to parse and validate Berkeley DB JE property %s: %sAn error occurred while trying to parse and validate Berkeley DB JE property %s: the property does not follow a singular property=value formAn error occurred while trying to parse and validate Berkeley DB JE property %s: the property shadows configuration attribute %sConfiguration attribute ds-cfg-db-cache-size has a value of %d which is less than the minimum: %dConfiguration entry %s does not contain attribute %s (or that attribute exists but is not accessible using JMX)Unable to retrieve JMX attribute %s associated with configuration entry %s: %sThe Directory Server could not register a JMX MBean for the component associated with configuration entry %s: %sThere is no method %s for any invokable component registered with configuration entry %sThe configuration for the key manager provider defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as a key manager provider as defined in configuration entry %s: %sAn unexpected error occurred while trying to export the Directory Server configuration to LDIF: %sAn error occurred while attempting to create a Directory Server logger from the information in configuration entry %s: %sAn error occurred while attempting to update a Directory Server logger from the information in configuration entry %s: %sClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server access logger: %sClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server debug logger: %sClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server error logger: %sClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server HTTP access logger: %sConfiguration entry %s does not contain a valid objectclass for a Directory Server access, error, or debug logger definitionAn error occurred while attempting to create a text writer for a Directory Server logger from the information in configuration entry %s: %sAn error occurred while attempting to open the configured log file %s for logger %s: %sInvalid UNIX file permissions %s does not allow write access to the log file by the log publisherThe access log filtering criteria defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s"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" classThe access log filtering criteria defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s"Invalid UNIX file permissions %s: %sThe 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 lostThe list of keys defined for the JSON matching rule contains an invalid JSON pointer : %sUnable to configure the authorization mechanism defined in %s: %sThe OAuth2 authorization mechanism defined in %s contains an invalid JSON Pointer %s: %sThe authorization mechanism defined in %s is referencing an invalid URL %s: %sThe authorization mechanism defined in %s is referencing a non-existing or non-readable directory: %sAn 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 disabledThe configuration for the plugin defined in configuration entry %s was not acceptable: %sCannot create the property resolver due to the following error: '%s'The configuration for the password generator defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as a password generator as defined in configuration entry %s: %sThe default password policy value '%s' is invalid because it refers to an authentication policy which is not a password policyThe configuration entry '%s' is currently defined to be the default password policy, however it is not a password policyThe password policy defined in configuration entry %s is invalid: %sThe 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=configNo 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 entryNo 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 definedThe configuration for the password storage scheme defined in configuration entry %s was not acceptable: %sUnable to add a new password storage scheme entry with DN %s because there is already a storage scheme registered with that DNAn error occurred while trying to initialize an instance of class %s as a password storage scheme as defined in configuration entry %s: %sThe configuration for the password validator defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as a password validator as defined in configuration entry %s: %sInvalid configuration element from %s in the REST2LDAP endpoint configuration entry %s: %sUnable to read the configuration from %s in the REST2LDAP endpoint configuration entry %s: %sInvalid JSON element %s from %s in the REST2LDAP endpoint configuration entry %s: %sAn error occurred while attempting to create a Directory Server log retention policy from the information in configuration entry %s: %sClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log retention policy: %sAn error occurred while attempting to create a Directory Server log rotation policy from the information in configuration entry %s: %sClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log rotation policy: %sThe configuration for the SASL mechanism handler defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as a SASL mechanism handler as defined in configuration entry %s: %sUnable to read the Directory Server schema definitions from directory %s because an unexpected error occurred while trying to list the files in that directory: %sUnable to read the Directory Server schema definitions because the schema directory %s exists but is not a directoryUnable to read the Directory Server schema definitions because the schema directory %s does not existThe schema provider class '%s' could not be instantiated or initialized with the configuration '%s' : %sThe configuration of schema provider '%s' is not acceptable for the following reasons: %sAn error occurred while attempting to initialize the Directory Server synchronization provider referenced in configuration entry %s: %sAn error occurred while attempting to instantiate class %s referenced in synchronization provider configuration entry %s: %sThe configuration for the trust manager provider defined in configuration entry %s was not acceptable: %sAn error occurred while trying to initialize an instance of class %s as a trust manager provider as defined in configuration entry %s: %sOne or more errors occurred while applying changes on server startup: %sAn error occurred while attempting to apply the changes contained in file %s to the server configuration at startup: %sUnable to resolve the host for the listen address '%s' of the LDAP connection handler %sCannot configure new SSL cipher suites because the following cipher suites are not supported: %s. Look for supported cipher suites in 'cn=jvm,cn=monitor'Cannot configure new SSL protocols because the following protocols are not supported: %s. Look for supported protocols in 'cn=jvm,cn=monitor'The configuration for the virtual attribute provider defined in configuration entry %s was not acceptable: %sAn error occurred while trying to load an instance of class %s referenced in configuration entry %s as a virtual attribute provider: %sUnable to parse value "%s" from config entry "%s" as a valid search filter: %sThe 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 valuesThe virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but provider %s may generate multiple valuesThe OpenDJ binary version '%s' does not match the installed configuration version '%s'. Please run upgrade before continuingAn error occurred while parsing the search filter %s defined for VLV index %s: %sVLV index '%s' must be configured with at least one sort attributeSort attribute %s for VLV index %s is not defined in the server schemaUnable to initialize an instance of class %s as a work queue as specified in configuration entry %s: %sWorker 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 destroyedAn error occurred while attempting to write the monitor user entry: %sAn error occurred while attempting to configure the backend for the monitor user: %sYou must provide at least one of the following arguments: enableService, disableService or serviceState or cleanupServiceYou can only provide one of the following arguments: enableService, disableService, serviceState or cleanupServiceThe server received configuration changes that require a restart of the %s connection handler to take effectThe connection attempt from client %s to %s has been rejected because the client was included in one of the denied address rangesThe connection attempt from client %s to %s has been rejected because the client was not included in one of the allowed address rangesThe connection attempt from client '%s' to '%s' has been rejected because the proxy protocol header indicated that the client used SSL but the header does not specify which SSL cipher was used. The proxy should be configured to transmit all SSL headersThe 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 establishedThe connection attempt from client %s to %s has been rejected because there are too many open connections from this clientAn error occurred while attempting to initialize the SSL context for use in the LDAP Connection Handler: %sThe request control with Object Identifier (OID) "%s" cannot be used due to insufficient access rightsCould not add change %s to replicaDB %s %s because flushing thread is shutting downReplication Server failed to start : could not bind to the listen port : %d. Error : %sThe Replication Server socket could not be closed : %sThe replication server failed to start because the database %s could not be read : %sCould not restart the Replication Server, bind to listen port %d failed : %sReplication server failed to start because setting socket timeout on port %d caused error %sError while trying to solve conflict with DN : %s ERROR : %sThe Replication was not started on base-dn %s : %sThe replication server connector thread could not be stopped : %sThe thread listening on the replication server port could not be stopped : %sThe backend database directory could not be created: %sAn error occurred while attempting to generate the RC script: %sAn error occurred while attempting to generate the systemd service file: %sThe directory %s specified as the OPENDJ_JAVA_HOME path does not exist or is not a directoryThis tool may only be used on UNIX-based systemsYou must provide either the --%s or the --%s argumentUnable 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 directoryA problem occurred while connecting to cloud provider '%s' using the provided credentials: %sThe 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 keysCryptoManager cannot get the preferred key wrapping cipher: %sCryptoManager cannot get the requested digest %s: %sCryptoManager cannot get the requested encryption cipher %s: %sCryptoManager cannot get the requested MAC engine %s: %sThe 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 keysCryptoManager failed to sign the wrapped key entry: %sCryptoManager failed to verify the wrapped key entry signature: %sCryptoManager failed to decipher the wrapped secret-key value: %sCryptoManager symmetric key attribute value "%s" syntax is invalid: incorrect number of fieldsCryptoManager symmetric key attribute value "%s" syntax is invalid. Parsing failed in field "%s" at offset %dCryptoManager failed to decrypt the supplied data because there was an error reading from the input stream: %sCryptoManager failed to decrypt the supplied data because it could not read the cipher initialization vector in the data prologueCryptoManager failed to decrypt the supplied data because it could not read the symmetric key identifier in the data prologue: %sCryptoManager failed to decrypt the supplied data because it could not read the version number in the data prologue: %sCryptoManager failed to decrypt the supplied data because the symmetric key identifier in the data prologue does not match any known key entriesCryptoManager failed to decrypt the supplied data because the version "%d" in the data prologue is unknownCryptoManager failed to encode symmetric key attribute value: %sCryptoManager failed to retrieve the collection of instance-key-pair public-key-certificates from ADS container "%s": %sCryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding"CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding"CryptoManager cannot initialize Cipher: %sCryptoManager passed invalid Cipher transformation "%s": %sCryptoManager failed to write the stream prologue: %sCryptoManager failed to initialize MAC engine: %sCryptoManager passed invalid MAC algorithm "%s": %sCryptoManager failed to import the symmetric key entry "%s": %sCryptoManager failed to import the symmetric key entry "%s" because it could not add a symmetric key attribute value that can be decoded by this instanceCryptoManager failed to import the symmetric key entry "%s" because it could not obtain a symmetric key attribute value that can be decoded by this instanceCryptoManager detected a field mismatch between the key entry to be imported and an entry in the key cache that share the key identifier "%s"CryptoManager failed to decode the key entry identifier "%s": %sCryptoManager failed to instantiate a KeyGenerator for algorithm "%s": %sCryptoManager failed to initialize because the specified cipher key length "%d" is beyond the allowed cryptography strength "%d" in jurisdiction policy filesThe wrapped key entry is missing the following attributes: %sCryptoManager cannot find the public-key-certificate (identifier "%s") requested for symmetric key re-encodingAn error occurred while attempting to initialize a SSL context for server to server communication: %sCryptoManager failed to add locally produced symmetric key entry "%s": %sCryptoManager 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 keyThe 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 mechanismThe wrapped key entry signature does not match the entry contentSpecified CSNs '%s' and '%s' have two different server ids. The historicalCsnRangeMatch extensible matching rule requires CSNs to have the same server idSpecified operators '%s' and '%s' do not specify a range for historicalCsnRangeMatch extensible matching ruleThe OpenDJ binary version '%s' does not match the installed data version '%s'. Please run 'upgrade --dataOnly' before continuingDatabase exception: %sA plugin caused the delete operation to be aborted while deleting a subordinate entry %sEntry %s cannot be removed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entryThe entry %s cannot be deleted due to insufficient access rightsUnable to delete entry %s because the backend that holds that entry is configured in read-only modeEntry %s cannot be removed because the server failed to obtain a write lock for this entry after multiple attemptsEntry %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 DNEntry %s does not exist in the Directory ServerThe entry '%s' cannot be removed because it does not existThe entry '%s' cannot be removed because it has subordinate entriesUnable to delete entry %s because the Directory Server is configured in read-only modeAn error occurred during conflict resolution synchronization processing for the delete operation with connection ID %d and operation ID %d: %sAn error occurred during postoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %sAn error occurred during preoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %sEntry %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 operationThis server received a replication message to signal a disaster recovery. This means that this server is part of a mixed topology where the deprecated start-disaster-recovery command is used. The operation will continue, but it is not supported anymore and the disaster recovery procedure for mixed topologies must be used instead.Unable to de-register base DN %s with the Directory Server because that base DN is not registered for any active backendError loading dictionary: %sAn error occurred while attempting to load the dictionary from file %s: %sThe specified dictionary file %s does not existThe provided password contained a word from the server's dictionaryThe Directory server DS(%s) and Replication server RS(%s) are working on different dataset regarding the domain '%s' : the Directory server DS(%s) will reject all modification operations and must be re-initializedThe specified config file path '%s' is invalid. The specified path must exist and must be a fileThe specified schema configuration directory '%s' is invalid. The specified path must exist and must be a directoryThe specified server root directory '%s' is invalid. The specified path must exist and must be a directoryThe Directory Server is currently running. Environment configuration changes are not allowed with the server runningThe backend database directory '%s' is not a valid directoryThe 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 reconnectThe 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 thresholdCould not get filesystem for directory %s: %sThe 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 allowedFailed to update free disk space for directory %s: %s"%s" (low=%s, full=%s)There is no data in domain '%s' to run disaster recovery onThe connection from this replication server RS(%s) to directory server DS(%s) at %s for domain "%s" has failedCould not compute new status in DS replication domain %s with server id %s. Was in %s status and received %s eventDN sent by replication server: %s does not match local directory server one: %sDirectory server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %sReceived invalid requested status %s in DS replication domain %s with server id %sChangelog on replication server '%s' 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-initializedAn error occurred while attempting to bootstrap the Directory Server: %sAn error occurred while trying to start the Directory Server: %sOpenDJ is configured to run as a Windows service and it cannot run in no-detach modeIn no-detach mode, the 'timeout' option cannot be usedAn error occurred while attempting to parse the provided set of command line arguments: %sThe replication changelog file '%s' could not be deleted. Check file permissions and filesystem status. The error is: %sThe replication changelog files could not be retrieved. Check file permissions and filesystem status. The error is: %sCannot read the configuration of the local server. The error was: %sCannot delete entries under '%s' in admin backend. The error was: %sCannot disable admin backend on the local server. The error was: %sCannot obtain a connection for one of the servers in the topology. The error was: %sCannot obtain a connection to server '%s' from the topology. The error was: %sCannot read monitor entries under '%s' on the local server. The error was: %sCannot update configuration for server '%s'. The error was: %sAn error occurred opening (or closing) a connection to read or change the configuration of the local server. The error was: %sA problem occurred while clearing the changelog data: %sThe CSN cannot be parsed as a valid CSNThe provided base DN '%s' does not match the disaster recovery id '%s'. Please verify that the base DN and disaster recovery id correspond to the base DN and id from the first recovered serverThe disaster recovery procedure cannot be continued on this server because the domain '%s' does not contain the expected data. Make sure the server has been restored using exactly the same procedure used on the first serverAn error occurred while clearing the changelog for the domain '%s'. This server will not be able to connect to the servers which have already completed the disaster recovery procedure. Make sure the filesystem at '%s' is readable with delete permissions and try again. The error is: %sAn error occurred while clearing the change number index. The change number index on this server will expose erroneous data. Make sure the filesystem at '%s' is readable with delete permissions and try again. The error is: %sAn error occurred while computing the disaster recovery id for base DN '%s': %sAn error occurred while rewriting the base entry of the domain '%s'. This server will not be able to connect to the servers which already have received the disaster recovery procedure. Make sure the filesystem is writeable and there is some free disk space, and try again. The error is: %sAn error occurred while rewriting replication data for the domain '%s'. This server will not be able to connect to the servers which already have received the disaster recovery procedure. Make sure the filesystem at %s is writeable and there is some free disk space and try again. The error is: %sDisaster recovery for base DN '%s' failed on this serverDisaster recovery must be started on a directory server or a combined directory/replication serverThe disaster recovery id '%s' is invalid. Verify the value of the disaster recovery id parameter matches the value printed when '--generate-recovery-id' was run on the first serverThe provided disaster recovery id had version %d, but only version 1 is supported. Verify the value of the disaster recovery id parameter matches the value printed when '--generate-recovery-id' was run on the first serverBase Dn '%s' is not a replicated domain on this server. Disaster recovery must be run on a directory server or a combined directory/replication serverThe server is neither a replica nor a replication server for base DN '%s'Cannot add the entry '%s' to the server '%s'. The error was: %sCannot add an entry describing the new server to 'cn=admin data' in the remote server '%s' in the existing topology. The error was: %sCannot add '%s' to the bootstrap replication server list on server '%s'. The error was: %sCannot add '%s' to the configuration of replication domain '%s' on server '%s'. The error was: %sCannot add '%s' to the configuration of replication server on server '%s'. The error was: %sCannot configure the local server so it can replicate with the servers in the existing topology. The error was: %sCannot configure all the servers in the existing topology to replicate with the new server. The error was: %sCannot determine server ID for server '%s' on DNs '%s' and '%s'Cannot discover the configuration of the local server. The error was: %sCannot modify the entry '%s' on server '%s' to reconcile it with what is expected by the tool. The error was: %sCannot obtain a connection for one of the servers in the existing topology. The error was: %sCannot obtain a connection to server '%s' from the existing topology. The error was: %sCannot read 'cn=admin data' in server '%s'. The error was: %sCannot read the entry '%s' on server '%s'. The error was: %sCannot read server ID from server '%s' on DNs '%s' and '%s'. The errors were: %sCannot read the server ID or the group ID for the local server. The error(s) are: %sError when reading the server IDs from all the servers in the old topology. The error was: %sCannot retrieve the replication port from server '%s'. The error was: %sCannot add server instance keys to the new server. The error was: %sAn error occurred opening connections to the server in the existing topology or the new server. The error was: %sAn error occurred opening (or closing) a connection to change the configuration of the local server. The error was: %sInappropriate group ID '%s' for the local server: it cannot be converted to an integer, but this is required to communicate with pre 7.0 servers. Use a group ID that can be converted into an integer, or use 'default' if you do not want to set a group IDInappropriate server ID '%s' for the local server: it does not represent a numeric value as required to communicate with pre 7.0 servers. Use an integer server ID without leading zerosOnce done, restart the server for the changes to take effectCannot use server ID '%s' for the local server because it is already used by server '%s' (configuration object %s)Error while reading cn=monitor: %sAn error occurred while reading cn=monitor on server %s: %sGeneral error: %sCannot contact server: no admin port could be discovered in its entry %sServer is not healthy: %sDuplicate 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 IDsDuplicate 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 IDsDynamic groups do not support explicitly altering their membershipUnable to decode value "%s" in entry "%s" as an LDAP URL: %sAn error occurred while attempting to 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 %sCannot decode the provided entry changelog notification control because an error occurred while attempting to decode the control value: %sCannot decode the provided entry changelog notification control because it does not have a valueThe specified e-mail message could not be sent using any of the configured mail serversThe provided recipient address %s is invalid: %sThe provided sender address %s is invalid: %sThe 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'An error occurred while attempting to retrieve the configuration version of the directory server: '%s'An error occurred while attempting to retrieve the data version of the directory server: '%s'An error occurred while attempting to import LDIF file '%s' into embedded server with server root '%s': '%s'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 detailsAn error occurred while initializing configuration of embedded server with server root '%s': %sAn error occurred while attempting to retrieve an internal connection to the server with the user DN '%s'An error occurred while attempting to initialize the configuration framework or to read the configuration file '%s'An error occurred while attempting to rebuild index of embedded server with server root '%s': %sAn 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 detailsAn error occurred while attempting to extract server archive '%s' before setup of embedded server with server root '%s': %sConfiguration error: an LDAP port or an LDAPS port must be configured before finishing configuring the embedded serverAn error occurred while attempting to start the embedded server with server root '%s' : %sAn error occurred while attempting to upgrade the embedded server with server root '%s' : %sThe embedded server with server root '%s' cannot be started because it is already runningAn error occurred while attempting to encode the clear-text password: %sCannot read password from the input: %sThe provided password is not a valid encoded authentication password value: %sThe provided password is not a valid encoded user password value: %sNo clear-text password was specified. Use --%s, --%s or --%s to specify the password to encodeNo password storage scheme was specified. Use the --%s argument to specify the storage schemeNo password storage schemes have been configured for use in the Directory ServerAuthentication password storage scheme "%s" is not configured for use in the Directory ServerPassword storage scheme "%s" is not configured for use in the Directory ServerProvided passwords don't matchedA 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%s must change their password before it will be allowed to request any other operationsA 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 completedA 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 completedObject class %s added to entry %s is marked OBSOLETE in the server schemaObject class %s cannot be added to entry %s because that class is not defined in the Directory Server schemaAn entry container named '%s' is already registered for base DN '%s'The entry database does not contain a valid record for ID %sUnable to decode an entry because an unexpected exception was caught during processing: %sUnable to decode an entry because it had an unsupported entry version byte value of %sUnable to decode the provided entry encode configuration element because it has an invalid lengthUnable to process the virtual list view request because the target start position was before the beginning of the result setNo value found for property '%s'No environment value '%s' found for property '%s'. If you are running the tool in offline mode, make sure the command has access to this variable, or else make sure the directory server has access to itWhile clearing the database %s, the following error happened: %sThe following error has been received : %sAn error occurred while parsing the command-line arguments: %sCould not replay operation %s %s with ChangeNumber %s error %s %sError %s when searching for server state %s : %s base dn : %sCould not start connection handler %s with listen addresses "%s". The error was: %sCould not start connection handlersThe baseDN '%s' specified as match base DN in the exact match identity mapper defined in configuration entry '%s', does not belong to a local backendThe 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 searchesID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'ID string %s mapped to multiple usersAn internal failure occurred while attempting to resolve ID string %s to a user entry: %sError during the Replication Server database trimming or flush process. The Changelog service is going to shutdown: %sCaught IOException while changing status for domain %s and serverId: %s after reset for generation id: %sCaught IOException while changing status for domain %s and serverId: %s from status analyzer: %sError trying to replay %s, operation could not be decoded: %sCaught IOException while forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %sReplication server caught exception while listening for client connections: %sAn Exception was caught while replaying operation %s %s (%s) : %sAn Exception was caught while replaying replication message : %sReplication broker with dn %s and server id %s failed to signal status change because of: %sCaught IOException while sending topology info (for update) on domain %s for %s server %s : %sDirectory server DS(%s) encountered an unexpected error while connecting to replication server %s for domain "%s": %sExecution error during backend operation: %sI/O error occurred while exporting entry: %sCould not stop export-ldif threads after 30 seconds. Now forcing stop by interrupting themThe extended operation %s cannot be performed due to insufficient access rightsThere is no extended operation handler registered with the Directory Server for handling extended operations with a request OID of %sUnable to process the request for extended operation %s because it contained an unsupported critical control with OID %sExternal process has been interrupted: '%s'External process contains errors: %sAn error occurred while attempting to decode the value of the cancel extended request: %sUnable to process the cancel request because the extended operation did not include a request valueThe user account has been administratively disabledThe user account is lockedPassword modification is not supported for user %s because the account is not managed locallyThe 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 operationAn unexpected error occurred while attempting to decode the password modify extended request sequence: %sAn 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 serverUnable to encode the provided password using the default scheme(s): %sAn error occurred while attempting to create a new password using the password generator: %sAn error occurred while attempting to get the password policy for user %s: %sThe password modify extended request cannot be processed because the server was unable to obtain a write lock on user entry %s after multiple attemptsThe provided authorization ID string "%s" could not be mapped to any user in the directoryAn error occurred while attempting to map authorization ID string "%s" to a user entry: %sThe password cannot be changed because the previous password change was too recentYou do not have sufficient privileges to perform password reset operationsThe password modify extended request cannot be processed because it contained an invalid userIdentity field. The provided userIdentity string was "%s"The password modify extended operation cannot be processed because the current password provided for the user is invalidThe password modify extended request cannot be processed because it does not contain an authorization ID and the underlying connection is not authenticatedNo new password was provided, and no password generator has been defined that may be used to automatically create a new passwordThe 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"The password cannot be changed because it is expiredThe password policy does not allow users to supply pre-encoded passwordsThe provided new password was already contained in the password historyThe current password must be provided for self password changesPassword modify operations that supply the user's current password must be performed over a secure communication channelPassword changes must be performed over a secure communication channelThe provided new password failed the validation checks defined in the server: %sEnd users are not allowed to change their passwordsThe password policy state extended operation is not supported for user %s because the account is not managed locallyYou do not have sufficient privileges to use the proxied authorization controlError when purging historical information for entry %s: %sAn error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %sThe 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 searchesThe certificate with fingerprint '%s' could not be mapped to exactly one user. It maps at least to both '%s' and '%s'The certificate with fingerprint %s mapped to multiple usersCould not map the provided certificate chain to a user entry because no peer certificate was availableCould not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)An internal failure occurred while attempting to map the certificate with fingerprint %s to a user entry: %sA fatal error occurred while trying to initialize fifo entry cache: %sAn Exception was caught while testing existence or trying to create the directory for the Replication Server database : %s %sCould not collect all the filesFailed to parse the credential file '%s'Credential file '%s' not foundAn error occurred while trying to create a key manager factory to access the contents of keystore file %s: %sAn error occurred while trying to load the keystore contents from file %s: %sThe keystore type %s specified in attribute ds-cfg-key-store-type of configuration entry %s is not valid: %sThe keystore file %s specified in attribute ds-cfg-key-store-file of configuration entry %s does not existAn error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %sAn error occurred while trying to load the trust store contents from file %s: %sThe trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %sThe trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not existThe attempt to obtain an exclusive lock on file %s was rejected because the attempt to create the lock file failed: %sThe attempt to obtain an exclusive lock on file %s was rejected because an error occurred while attempting to acquire the lock: %sThe attempt to obtain an exclusive lock on file %s was rejected because the attempt to open the lock file failed: %sThe exclusive lock requested for file %s was not granted, which indicates that another process already holds a shared or exclusive lock on that fileThe attempt to obtain an exclusive lock on file %s was rejected because an exclusive lock was already held on that fileThe attempt to obtain an exclusive lock on file %s was rejected because a shared lock was already held on that fileThe attempt to obtain a shared lock on file %s was rejected because the attempt to create the lock file failed: %sThe attempt to obtain a shared lock on file %s was rejected because an error occurred while attempting to acquire the lock: %sThe attempt to obtain a shared lock on file %s was rejected because the attempt to open the lock file failed: %sThe shared lock requested for file %s was not granted, which indicates that another process already holds an exclusive lock on that fileThe attempt to obtain a shared lock on file %s was rejected because an exclusive lock was already held on that fileThe attempt to release the exclusive lock held on %s failed: %sThe attempt to release the shared lock held on %s failed: %sThe attempt to release the lock held on %s failed because no record of a lock on that file was foundThe 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 sevenOne 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 alteredUnable to set permissions for file %s because it does not existCould not retrieve the configuration for a replication domain matching the entry %sCannot start total update in domain "%s" from this directory server DS(%s): cannot find remote directory server DS(%s)Cannot start total update in domain "%s" from this directory server DS(%s): no remote directory servers foundCannot decode the provided symmetric key extended request: %sAn unexpected error occurred while attempting to decode the symmetric key extended request sequence: %sCannot decode the provided symmetric key extended operation because it does not have a valueThe global access control policy defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s"The global access control policy defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s"The global access control policy defined in "%s" could not be parsed because it contains an unrecognized control alias "%s"The global access control policy defined in "%s" could not be parsed because it contains an unrecognized extended operation alias "%s"The value %s cannot be decoded as a hexadecimal string because it contains an illegal character %c that is not a valid hexadecimal digitThe value %s cannot be decoded as a hexadecimal string because it does not have a length that is a multiple of two bytesThe connection handler %s is trying to use the listener %s which is already in use by another connection handlerError while starting the HTTP application: %sUnable to process request '%s' received for HTTP client connection: %sUnable to process HTTP request '%s': %sUnable to write HTTP response to the client '%s': %sThe processed ID string %s is mapped to multiple usersAn error occurred while attempting to disconnect client connection %d: %sThe backend must be disabled before the import process can startUnable to create the temporary directory %sThe import has been aborted because the data to be imported contains duplicate copies of entry '%s'Insufficient free memory (%d bytes) to perform import. At least %d bytes of free memory is requiredThe import has been aborted because the entry '%s' does not have a parent entryEntry record is not compatible with this version of the backend database. Entry version: %xAn 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 operationIndexes are not supported in the "%s" backendBad msg id sequence during import. Expected:%s Actual:%sInitialization cannot be done because the following error occurred while locking the backend %s : %sInitialization of replication domain '%s' interrupted because the domain is shutting down. The domain still needs to be re-initializedInitialization cannot be done because export is not supported by the backend %sDomain %s (server id: %s) : remote exporter server disconnection (server id: %s ) detected during initializationWhen initializing remote server(s), the initialized server with serverId=%s is potentially stopped or too slowDuring initialization from a remote server, the following error occurred : %sInitialization cannot be done because import is not supported by the backend %sThe following servers did not end initialization being connected with the right generation (%s). They are potentially stopped or too slow. Servers list: %sThe following servers did not acknowledge initialization in the expected time for domain %s. They are potentially down or too slow. Servers list: %sReplica '%s' seems to have disconnected from the topology while it was being re-initialized, initialization will stopWhen initializing remote server(s), connection to Replication Server with serverId=%s is lostConnection failure with Replication Server %s during importThe initialization failed because the domain %s is not connected to a replication serverInvalid plugin type '%s', a backup plugin must be of type '%s'The server has not been configured. Please run the 'setup' command firstValue '%s' must be a valid numberValue '%s' must be a valid version (two or three digits separated with a dot)Please select at least version %sUnable to process request '%s' received for internal client connection: %sNo result received after completion for request '%s' received for internal client connectionAn internal error occurred when accessing backend '%s': %sAn internal error was detected when accessing backend '%s'Unable to process the provided internal modifications request control because it did not contain modificationsUnable to process the provided internal modifications request control because it did not contain an originError: %sUser %s does not exist in the directoryBackup id '%s' is invalid: cannot parse '%s' as a timestampBackup id '%s' is invalid: expected to find an underscore in itInvalid syntax for the provided cookie '%s'Specified assertion '%s' for historicalCsnRangeMatch extensible matching rule does not conform to expected syntax. The assertion must specify a CSN rangeInvalid operator '%s' specified in historicalCsnRangeMatch extensible matching rule assertionInvalid target for the exportOn domain %s, initialization of server with serverId:%s has been requested from a server with an invalid serverId:%s. %sNo usable key was found for '%s', which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configuredThe date argument for "logsAfterDate" is invalidThe number argument for "maxLogFiles" is invalidThe following paged results control cookie value was not recognized: %sInvalid excluded file name pattern: %sThe provider class does not allow the operation requestedThe serverPID argument is not a valid numberThe 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 sensitiveAn error occurred while trying to register the JMX alert handler with the MBean server: %sJMX connection %s with JMX connection ID '%s' has been disconnected because it was finalized by GCUnable to process request '%s' received for JMX client connection: %sNo result received after completion for request '%s' received for JMX client connectionJMX connection %s with JMX connection ID '%s' has been disconnected because it received a '%s' notificationUnable to process request '%s' received for JMX client because this type of request is not supported for JMXUnable to process response received for JMX client connection for request '%s' because the response '%s' is not of any of the expected typesYou do not have sufficient privileges to establish the connection through JMX. At least JMX_READ privilege is requiredYou do not have sufficient privileges to perform search operations through JMXUnable to get the JVM default truststore: %sAn error occurred while reading information contained within key manager provider from configuration: "%s"An error occurred while trying to retrieve the key managers from the key manager provider `%s`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 configuredThe 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 keyThe 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 keycancel() invokedThe 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: %sThe 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' responseLDAP connection %s has been closed because the LDAP connection handler %s is shutting downThis 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 %sTerminating this connection because the client sent an invalid message of type %s (LDAP message ID %d) that is not allowed for request messagesAn unexpected failure occurred while trying to process a request of type %s (LDAP message ID %d): %s. The client connection will be terminatedAn error occurred while trying to create a key manager factory to access the contents of LDAP keystore with base DN '%s': %sThe mapped search filter template "%s" could not be parsed as a valid LDAP filterThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the bind failed unexpectedly for the following reason: %sThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the search failed unexpectedly for the following reason: %sThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the search did not return any entries matching the filter "%s"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"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: %sThe configuration of LDAP PTA policy "%s" is invalid because it does not specify a means for obtaining the mapped search bind passwordAn error occurred while trying to create a trust manager factory to access the contents of LDAP keystore with base DN '%s': %sThe Directory Server does not support LDAP protocol version %d. This connection will be closedThe provided string "%s" cannot be decoded as an LDAP URL because the port number portion %s cannot be decoded as an integerThe provided URL component "%s" could not be decoded because the character at byte %d was not a valid hexadecimal digitThe 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 65535The 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 subordinateThe 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 URLThe provided string "%s" cannot be decoded as an LDAP URL because it does not contain a host before the colon to specify the port numberThe provided string "%s" cannot be decoded as an LDAP URL because it does not contain a port number after the colon following the hostThe provided string "%s" cannot be decoded as an LDAP URL because it does not contain a protocol schemeThe provided URL component "%s" could not be decoded because the percent character at byte %d was not followed by two hexadecimal digitsThe Directory Server has been configured to deny access to LDAPv2 clients. This connection will be closedLDAPv2 clients are not allowed to use request controlsThe 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 terminatedThe original result code for this message was 10 but this result is not allowed for LDAPv2 clientsThe response included one or more referrals, which are not allowed for LDAPv2 clients. The referrals included were: %sAn 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 sentA 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 sentEntry %s already exists in the LDIF backendThe parent for entry %s does not existAn error occurred while trying to create the reader for the LDIF import operation: %sAn error occurred while trying to create the writer for the LDIF export operation: %sAn error occurred while trying to write entry %s during the LDIF export: %sEntry %s does not existEntry %s has one or more subordinate entries and cannot be deleted until all of its subordinate entries are removed firstLDIF file %s configured for use with the LDIF backend defined in configuration entry %s has multiple entries with a DN of %sLDIF 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 backendAn error occurred while trying to close file %s for the LDIF backend defined in configuration entry %s: %sAn 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: %sThe file %s written for the LDIF backend defined in configuration entry %s is 0 bytes long and unusableAn unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continueAn error occurred while attempting to rename file %s to %s while writing updated data for the LDIF backend defined in configuration entry %s: %sAn error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %sThe target entry %s does not existLDIF 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 readThe new parent DN %s does not existSource entry %s does not existTarget entry %s already existsEntry %s does not existThe LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNsThe target entry %s does not existEntry %s specified as the search base DN does not existAn error occurred while the LDIF connection handler was attempting to delete processed file %s: %sAn error occurred while trying to read a change record from the LDIF file: %s. No further processing on this LDIF file can be performedAn 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 continueAn error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %sAn I/O error occurred while the LDIF connection handler was processing LDIF file %s: %sUnable to parse LDIF entry %s starting at line %d because it was not possible to base64-decode the attribute on line "%s": %sUnable to parse LDIF entry starting at line %d because it was not possible to base64-decode the DN on line "%s": %sAn 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: %sThe specified LDIF file %s already exists and the export configuration indicates that no attempt should be made to append to or replace the fileUnable to parse LDIF entry %s starting at line %d because it has an invalid binary option for attribute %sUnable 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: %sUnable 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 appendedUnable 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: %sEntry %s starting at line %d includes multiple values for single-valued attribute %sUnable to parse LDIF entry starting at line %d because the line "%s" does not include an attribute nameUnable to parse LDIF entry starting at line %d because the first line does not contain a DN (the first line was "%s"Skipping entry %s because the following error was received when reading its attributes: %sRejecting entry %s because it was rejected by a plugin: %sRejecting entry %s because it was rejected by a pluginEntry %s read from LDIF starting at line %d is not valid because it violates the server's schema configuration: %sSkipping entry %s because the DN is not one that should be included based on the include and exclude branches/filtersSkipping entry %s because the DN is excluded by the exclude branch "%s"Skipping entry %s because the DN is excluded by the exclude filter "%s"Skipping entry %s because the DN is not included by any include branchesSkipping entry %s because the DN is not included by any include filtersUnable 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: %sUnable to decode exclude branch string "%s" as a valid distinguished name: %sUnable to decode wrap column value "%s" as an integerThe Directory Server backend with backend ID "%s" does not provide a mechanism for performing LDIF exportsAn 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 continueUnable to decode exclude filter string "%s" as a valid search filter: %sUnable to decode include filter string "%s" as a valid search filter: %sAn error occurred while attempting to process the LDIF export: %sProvided include base DN "%s" is not handled by the backend with backend ID %sMultiple Directory Server backends are configured with the requested backend ID "%s"None of the Directory Server backends are configured with the requested backend ID "%s"Unable to decode exclude branch string "%s" as a valid distinguished name: %sUnable to decode include branch string "%s" as a valid distinguished name: %sThe Directory Server backend with backend ID %s does not provide a mechanism for performing LDIF importsAn 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 continueAn error occurred while trying to open the rejects file %s for writing: %sAn error occurred while trying to open the skip file %s for writing: %sUnable to decode exclude filter string "%s" as a valid search filter: %sUnable to decode include filter string "%s" as a valid search filter: %sUnable to parse the specified file %s as a MakeLDIF template file: %sThe value %s for threadCount cannot be parsed: %sThe specified LDIF file %s cannot be readThe %s argument is not supported for online importsAn error occurred while attempting to process the LDIF import: %sProvided include base DN "%s" is not handled by the backend with backend ID %sUnable to access the LDIF file %s to import. Please check that the file is local to the server and the path correctNeither the %s nor the %s argument was provided. One of these arguments must be given to specify the backend for the LDIF data to be imported toNeither the %s nor the %s argument was provided. One of these arguments must be given to specify the source for the LDIF data to be importedImported branches or backend IDs can not span across multiple Directory Server backendsNone of the Directory Server backends are configured with the requested backend ID or base DNs that include the specified branchesAn unexpected error occurred when searching in %s for the generation ID : %sUnable to load JVM default keystore from system properties: %sProxy backend '%s' is being deregistered from base DN %s because local backend '%s' is registering against it. Local backends take precedence over proxy backendsThe message with ID %d has been generated %d times in the last second: %sThe 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 onlyError occurred while closing log file for logger %s: %sError occurred while enforcing retention policy %s for logger %s: %sError occurred while flushing writer buffer for logger %s: %sError occurred while listing log files named by policy with initial file name %sError occurred while obtaining free disk space in the partition containing log file %s: %sError occurred while opening log file %s for logger %s: %sError occurred while writing log record for logger %s: %s. Any further write errors will be ignoredA loop was detected while replaying operation: %s %s (%s) error %sCould not write data to the client for %sThe directory server is not accepting a new persistent search request because the server has already reached its limitUnable to create an LDIF reader: %sUnable to create an LDIF writer: %sCannot delete entry %s because it has one or more subordinate entriesCannot rename entry %s because it has one or more subordinate entriesCannot rename entry %s because the target entry is in a different backendCannot write entry %s to LDIF: %sEntry %s already exists in the memory-based backendEntry %s does not belong in the memory-based backendAn unexpected error occurred while processing the import: %sAn unrecoverable error occurred while reading from LDIF: %sUnable to add entry %s because its parent entry %s does not exist in the memory-based backendCannot rename entry %s because the new parent entry %s doesn't existExactly one base DN must be provided for use with the memory-based backendCannot complete initialization of server's backends because the root and administrative backends have not been initialized yetThe --bindDN and/or --bindPassword arguments are missingThe entry database does not contain a record for ID %sAn error occurred while parsing the command-line arguments: The argument --outputDirectory is required to have a value but none was provided in the argument list and no default value is availableA sub-command must be specifiedEntry %s cannot be renamed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entryThe entry %s cannot be renamed due to insufficient access rightsUnable to rename entry %s because the backend that holds that entry is configured in read-only modeThe modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for that DNThe modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for the new DN %sThe 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 backendsEntry %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 entryThe 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 movedThe modify DN operation for entry %s cannot be performed because the new RDN includes attribute type %s which is declared OBSOLETE in the server schemaThe modify DN operation for entry %s cannot be performed because no backend is registered to handle that DNThe modify DN operation for entry %s cannot be performed because no backend is registered to handle the new DN %sThe modify DN operation for entry %s cannot be performed because that entry does not exist in the serverA modify DN operation cannot be performed on entry %s because the new RDN would not have a parent DNEntry %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 requestThe 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: %sUnable to rename entry %s because the Directory Server is configured in read-only modeAn error occurred during conflict resolution synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %sAn error occurred during postoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %sAn error occurred during preoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %sEntry %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 operationThe modify DN operation for entry %s cannot be performed because the change would have violated the server schema: %sEntry %s cannot be modified because it would have resulted in one or more duplicate values for attribute %s: %sWhen 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: %sWhen attempting to modify entry %s, one value for attribute %s was found to be invalid according to the associated syntax: %sEntry %s cannot be modified because the modification contained an add component for attribute %s but no values were providedEntry %s cannot be modified because the request contained an LDAP assertion control and the associated filter did not match the contents of the entryEntry %s cannot be modified because the modification attempted to update attribute %s which is defined as NO-USER-MODIFICATION in the server schemaEntry %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 schemaThe entry %s cannot be modified due to insufficient access rightsUnable to modify entry %s because the backend that holds that entry is configured in read-only modeEntry %s cannot be modified because the server failed to obtain a write lock for this entry after multiple attemptsYou do not have sufficient privileges to modify the set of privileges contained in an entryEntry %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: %sEntry %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 entryEntry %s cannot be modified because the change to attribute %s would have removed a value used in the RDNEntry %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 entryEntry %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 entryEntry %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 integerEntry %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 allowedEntry %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 valueInvalid modification type %s attempted on password attribute %sThe provided user password does not match any password in the user's entryThe password change would result in multiple password values in the user entry, which is not allowedMultiple password values are not allowed in user entries%s must change their password before it will be allowed to perform any other operationsThe user entry does not have any existing passwords to removeEntry %s cannot be updated because the request did not contain any modificationsUser passwords may not be provided in pre-encoded formEntry %s cannot be modified because no such entry exists in the serverThe entry '%s' cannot be modified because it does not existUsers are not allowed to change their own passwordsThe specified password value already exists in the user entryAttributes used to hold user passwords are not allowed to have any attribute optionsThe password policy requires that user password changes include the current password in the requestThe provided new password was found in the password history for the userThe provided password value was rejected by a password validator: %sYou do not have sufficient privileges to reset user passwordsWhen 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: %sWhen 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: %sPassword changes must be performed over a secure authentication channelUnable to modify entry %s because the Directory Server is configured in read-only modeAn error occurred during conflict resolution synchronization processing for the modify operation with connection ID %d and operation ID %d: %sAn error occurred during postoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %sAn error occurred during preoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %sEntry %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 operationEntry %s cannot be modified because the resulting entry would have violated the server schema: %sThe password cannot be changed because it has not been long enough since the last password changeA plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %sThe entry cannot be renamed to '%s' because an entry with that name already existsThe entry '%s' cannot be renamed because it does not existYou do not have sufficient privileges to read directory server monitoring informationAn 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 protocolUnable to retrieve the requested entry %s from the monitor backend because the DN is not below the monitor base of %sUnwilling 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 configurationAn error occurred while attempting to export the base monitor entry: %sAn error occurred while attempting to export the monitor entry for monitor provider %s: %sCould not collect monitoring data from the directory server: %sThe directory to move %s exists but is a fileThe directory to move %s does not existThe target directory %s already existsMultiple Directory Server backends are configured to support base DN "%s"Multiple domains match the base DN providedThe entry cannot be moved because the new parent entry '%s' does not existNo backend is associated with the base DN '%s'None of the Directory Server backends are configured to support the requested base DN "%s"Could not find file '%s' in cloud bucket '%s'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 keyFile 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'No domain matches the provided base DN '%s'Domain %s: the server with serverId=%s is unreachableFile 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'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'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'No enabled connection handler availableServer %s should be initialized but is not connected to the topologyThere are insufficient resources to perform the operationThis backend does not provide support for the numSubordinates operational attributeA target server must be specified either by using LDAP connection options or the --%s optionThe database environment could not be opened: %sInternal Error : Operation %s change number %s was not found in local change listInternal Error : Operation %s change number %s was not found in remote change listThe output directory "%s" could not be foundUnable to parse the OID from the provided definition of attribute type: '%s'Unable to parse the OID from the provided definition of DIT content rule: '%s'Unable to parse the rule ID from the provided definition of DIT structure rule: '%s'Unable to parse the OID from the provided definition of ldap syntax: '%s'Unable to parse the OID from the provided definition of matching rule use: '%s'Unable to parse the OID from the provided definition of name form: '%s'Unable to parse the OID from the provided definition of objectclass: '%s'An error occurred while trying to create a key manager factory to access the contents of the PKCS#11 keystore: %sAn error occurred while trying to access the PKCS#11 key manager: %sAn error occurred while trying to create a trust manager factory to access the contents of the PKCS#11 keystore: %sAn error occurred while trying to access the PKCS#11 trust manager: %sThe entry included a value for attribute %s that was not 7-bit cleanThe 7-bit clean plugin is configured with invalid plugin type %s. Only the ldifImport, preOperationAdd, preOperationModify, and preOperationModifyDN plugin types are allowedThe modify DN operation would have resulted in a value for attribute %s that was not 7-bit cleanThe 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 pluginThe 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 pluginAttribute '%s' is not defined in the directory schemaThe attribute '%s' has already been defined in the configurationThe mapping '%s:%s' maps the attribute to itselfInvalid plugin type '%s' for the Attribute Cleanup pluginAn 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 pluginAn 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 : %sAn attempt was made to register the Entity Tag plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginAn attempt was made to register the EntryUUID plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginThe fractional replication ldif import plugin is configured with invalid plugin type %s. Only the ldifImport plugin type is allowedAn 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 pluginUnable 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 restartAn attempt was made to register the LastMod plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginThe LDIF import plugin defined in configuration entry %s threw an exception when it was invoked on entry %s: %sThe LDIF import plugin defined in configuration entry %s returned null when invoked on entry %s. This is an illegal responseThe post-commit %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %sThe 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 terminatedThe 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 terminatedThe post-disconnect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %sThe post-disconnect plugin defined in configuration entry %s returned null when invoked for connection %d from %s. This is an illegal responseThe 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 terminatedThe 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 terminatedThe 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 terminatedThe 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 terminatedThe post-synchronization %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %sThe 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 terminatedThe 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 terminatedThe 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 terminatedThe 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 terminatedAuth password storage scheme %s referenced by the password policy import plugin is not configured for use in the serverUser password storage scheme %s referenced by the password policy import plugin is not configured for use in the serverThe password policy import plugin is not configured any default auth password schemes, and the server does not support the %s auth password schemeThe password policy import plugin is not configured any default user password schemes, and the server does not support the %s auth password schemeThe password policy import plugin references default auth password storage scheme %s which is not available for use in the serverAn 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 encodedAn 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 pluginThe 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 %sThe property 'check-references-filter-criteria' specifies filtering criteria for attribute '%s', but this attribute is not listed in the 'attribute-type' propertyThe 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 %sThe filtering criteria '%s' specified in property 'check-references-filter-criteria' is invalid because the filter could not be decoded: '%s'The Referential Integrity plugin failed to decode a entry DN from the update log: %sAn error occurred closing the Referential Integrity plugin update log file: %sAn error occurred during Referential Integrity plugin initialization because log file creation failed: %sThe entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not exist in any of the configured naming contextsThe operation could not be processed due to an unexpected exception: '%s'The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not match the filter '%s'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)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 pluginThe Referential Integrity plugin failed when performing an internal modify on entry %s: %sThe entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not belong to any of the configured naming contextsAn error occurred replacing the Referential Integrity plugin update log file: %sThe Referential Integrity plugin failed when performing an internal search: %sThe Samba password synchronization plugin could not encode a password for the following reasons: %sAn 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 pluginThe Samba password synchronization plugin could not process a modification for the following reason: %sThe 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 terminatedThe 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 terminatedThe 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 terminatedThe 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 terminatedThe shutdown plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server shutdown process: %sThe 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 abortedThe 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 abortedThe 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 abortedThe 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 terminatedThe 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 terminatedThe 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 terminatedThe 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 terminatedThe plugin defined in configuration entry %s does not support the %s plugin typeA unique attribute conflict was detected for attribute %s: value %s already exists in entry %sThe 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 %sAn internal error occurred while attempting to determine whether the operation would have resulted in a unique attribute conflict (result %s, message %s)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)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 pluginA 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 conflictProxy backend '%s' cannot register itself against base DN %s because this base DN is already registered against backend '%s'Proxy backend '%s' could not discover remote servers capabilities: %sProxy backend '%s' is non functional because it could not find any primary nor secondary servers via the service discovery mechanism '%s'The partition base DN '%s' should be subordinate to one of the base DNs %s of proxy backend '%s'The partition base DN '%s' shouldn't be subordinate to one of the other partition base DNs %s of proxy backend '%s'Proxy backend '%s' cannot find the configured service discovery mechanism '%s'Authorization as '%s' specified in the proxied authorization control is not permittedYou do not have sufficient privileges to use the proxied authorization controlUser %s specified in the proxied authorization V1 control does not exist in the Directory ServerUse of the proxied authorization V1 control for user %s is not allowed by the password policy configurationUse of the proxied authorization V2 control for user %s is not allowed: the account is disabledUse of the proxied authorization V2 control for user %s is not allowed: the account is expiredUse of the proxied authorization V2 control for user %s is not allowed: the account is lockedThe 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 usernameUnable 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 ServerUser %s specified in the proxied authorization V2 control does not exist in the Directory ServerUse of the proxied authorization V2 control for user %s is not allowed: the account's password is expiredCaught exception publishing fake operations for domain %s : %sThe provided password differs less than the minimum required difference of %d charactersThe configured minimum password length of %d characters is greater than the configured maximum password length of %dThe provided password is longer than the maximum allowed length of %d charactersThe provided password is shorter than the minimum required length of %d charactersAttribute options are not allowed for the password attribute %sAn error occurred while attempting to determine the value for attribute ds-cfg-require-change-by-time in configuration entry %s: %sThe dictionary data could not be decompressed: %sCannot use both pwdValidatorPolicy and ds-pwp-validator in subentry '%s'Password policy configuration entry %s references deprecated password storage scheme DN %s which does not support the auth password syntaxThe value for the '%s' attribute is not a valid booleanThe dictionary validator configuration is invalidThe value for the '%s' attribute is not a valid durationThe value for the '%s' attribute is not a valid timeThe value for the '%s' attribute is not a valid integerThe 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 'java.text.SimpleDateFormat' classThe 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)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 'java.text.SimpleDateFormat' classThe value for the '%s' attribute is not a valid state update failure policyThe value for the '%s' attribute is not a valid stringThe values for the '%s' attribute are not valid stringsThe 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 ageOnly a single value may be provided for the password attribute %sThe 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 valueThe subentry %s using the %s objectclass cannot define validators using the new %s objectclassThe subentry %s cannot use both %s and %s objectclassesThe subentry %s must have either the pwdPolicy or ds-pwp-password-policy objectclasses, which is required for the Directory Server password policyThe subentry %s using the %s objectclass cannot define validators using the old %s objectclassPre-encoded passwords are not allowed for the password attribute %sThe 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 replicasThe password could not be validated because of misconfiguration. Please contact the administratorThe password storage scheme defined in configuration entry %s does not support the auth password syntax, which is used by password attribute %sThe value for the '%s' attribute is not a valid attributeA values for the '%s' attribute is not a valid attribute nameThe password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" is not defined in the server schemaNo enabled password storage schemes in '%s' in subentry '%s'The password policy definition contained in configuration entry "%s" is invalid because the password validator "%s" specified in attribute "%s" cannot be foundThe password value for attribute %s was found to be unacceptable: %sThe 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 ageUnable to decode value "%s" for attribute %s in user entry %s as a Boolean valueAn error occurred while attempting to decode value "%s" for attribute %s in user entry %s in accordance with the generalized time format: %sAn error occurred while attempting to decode the ds-pwp-password-policy-dn value "%s" in user entry "%s" as a DN: %sAn error occurred while attempting to update password policy state information for user %s: %sThe 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 formatMultiple values were provided for the password policy state operation intended to set the account expiration time for the user. Exactly one value must be givenMultiple values were provided for the password policy state operation intended to add an authentication failure time for the user. Exactly one value must be givenMultiple 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 givenThe 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 formatThe 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'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 givenThe 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 formatThe 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 formatMultiple values were provided for the password policy state operation intended to set the last login time for the user. Exactly one value must be givenThe 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 formatMultiple values were provided for the password policy state operation intended to set the password changed time for the user. Exactly one value must be givenThe 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 formatMultiple values were provided for the password policy state operation intended to set the password warned time for the user. Exactly one value must be givenThe 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 formatMultiple values were provided for the password policy state operation intended to set the required change time for the user. Exactly one value must be givenThe 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'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 givenAn unexpected error occurred while attempting to decode password policy state extended request value: %sAn unexpected error occurred while attempting to decode an operation from the password policy state extended request: %sNo 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 givenYou do not have sufficient privileges to use the password policy state extended operationThe provided password policy state extended request did not include a request valueNo 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 givenThe password policy state extended request included an operation with an invalid or unsupported operation type of %sUser entry %s is configured to use a password policy subentry of %s but no such password policy has been defined in the server configurationA new Argon2 password storage scheme can only be added by running dsconfig in offline modeThe Argon2 password storage scheme could not be configured because it requires %s kB of memory, exceeding the maximum available of %s kB. Configure a bigger heap or reduce the Argon2 memory requirementsAn error occurred while attempting to base64-decode the password value %s: %sAn error occurred while attempting to decode the SCRAM credential value %s: %sAn error occurred while trying to decrypt a value using password storage scheme %s: %sAn unexpected error occurred while attempting to encode a password using the storage scheme defined in class %s: %sAn error occurred while trying to encrypt a value using password storage scheme %s: %sAn error occurred while attempting to initialize the message digest generator for the %s algorithm: %sThe %s SCRAM password storage scheme could not be initialized because the algorithm is not supported by the JVMPassword storage scheme %s does not support use with the authentication password attribute syntaxThe password value %s has been base64-decoded but is too short to be validAn error occurred while attempting to match a bcrypt hashed password value: %sThe %s password storage scheme is not reversible, so it is impossible to recover the plaintext version of an encoded passwordAn 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: %sAn 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: %sConfiguration entry "%s" contains multiple definitions for the %s character setThe 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 setConfiguration 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 attributeThe password format string "%s" references an undefined character set "%s"An error occurred while reading file '%s': %sRebuilding system index(es) must be done with the backend containing the base DN disabledAn 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 continueAn 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 continueAn error occurred while attempting to perform index rebuild: %sRebuild index aborted: an error has occurred while rebuilding indexes for base DN '%s'At least one index must be specified for the rebuild processThe backend does not support rebuilding of indexesReceived change status message does not come from a directory server (dn: %s, server id: %s, msg: %s)The provided schedule value has an invalid format. The schedule must be expressed using a crontab(5) format. Error details: %sAn error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %sAn error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?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?The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month tokenThe provided recurring task schedule value has an invalid day of the month tokenThe provided recurring task entry attribute %s holding the recurring task schedule has invalid hour tokenThe provided recurring task schedule value has an invalid hour tokenThe provided recurring task entry attribute %s holding the recurring task schedule has invalid minute tokenThe provided recurring task schedule value has an invalid minute tokenThe provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year tokenThe provided recurring task schedule value has an invalid month of the year tokenThe provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokensThe provided recurring task schedule value has an invalid number of tokensThe provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar dateThe provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week tokenThe provided recurring task schedule value has an invalid day of the week tokenThe 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 allowedThe 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 allowedThe provided recurring task entry contains multiple attributes with type %s, which is used to hold recurring task schedule, but only a single instance is allowedThe 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 allowedThe provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task IDThe provided recurring task entry does not contain attribute %s which is needed to hold the recurring task IDThe provided recurring task entry does not contain attribute %s which is needed to specify recurring task scheduleThe provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task scheduleFile 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: %sFile 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: %sThe baseDN '%s' specified as match base DN in the regular expression identity mapper defined in configuration entry '%s', does not belong to a local backendThe 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 searchesThe provided match pattern "%s" could not be parsed as a regular expression: %sThe processed ID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'The processed ID string %s mapped to multiple usersAn internal failure occurred while attempting to resolve processed ID string %s to a user entry: %sUnable to register backend %s with the Directory Server because another backend with the same backend ID is already registeredUnable to register base DN %s with the Directory Server for backend %s because that base DN is already registered for backend %sUnable 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 backendUnable 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 pathUnable 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 notThe index(es) cannot be rebuilt because the server failed to obtain a write lock for the entry '%s' after multiple attemptsThe specified reject file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the fileRejecting the requested operation because the connection has not been authenticatedInitialization of domain '%s' interrupted: no data received from the remote exporter '%s' for %sThe backend database files could not be removed: %sThe 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 %dChange number indexing is disabled for replication domain '%s'The Replication is configured for suffix %s but was not able to connect to any Replication ServerUnable to process the provided replication context request control because it did not contain a CSNUnable to process the provided replication context request control because it did not contain an entry UUIDThe following replication server listener threads were unexpectedly stopped: %s. A server restart may be neededReplication protocol error. Bad message type. %s received, %s requiredReplication Server '%s' expected to negotiate with another Replication Server but got information for Directory Server '%s' instead. The connection will be closedCannot enable replication to server '%s' as this server's ID '%s' is not a number between 1 and 32767New replication connection from %s started with unexpected message %s and is being closedThe entry '%s' specified in the request does not exist in the Directory ServerFor 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 runningThe generation ID could not be reset for domain %sUnable to resolve the server installation root directoryFull resync required. Reason: The provided cookie is older than the start of historical in the server for the replicated domain : %sFull resync required. Reason: The provided cookie contains unknown replicated domain %s. Current starting cookie <%s>The root container for backend %s has not been initialized preventing this backend from processing the requested operationAn attempt was made to configure the root DSE backend without providing a configuration entry. This is not allowedUnwilling 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 itselfUnable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %sUnwilling 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 configurationAn unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %sAn unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %sThe connection from this replication server RS(%s) to replication server RS(%s) at %s for domain "%s" has failedCould not compute new status in RS replication domain %s for server id %s. Was in %s status and received %s eventDN sent by remote replication server: %s does not match local replication server one: %sReplication server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %sReplication server received invalid initial status: %s for replication domain %s from server id %sReceived invalid new status %s in RS for replication domain %s and directory server id %sError when trying to publish a message in '%s'. The connection is going to be closed and reopened. Error: %sError when trying to publish a message in '%s'. The connection is going to be closed and reopenedError when initializing publisher of messages in '%s'Error when initializing publisher of messages in '%s'SASL %s authentication is not supported for user %s because the account is not managed locallyThe server was unable to find any entry corresponding to authentication ID %sThe entry %s specified as the authorization identity could not be retrieved: %sThe authenticating user %s does not have sufficient access to assume a different authorization identityThe authenticating user %s does not have sufficient privileges to assume a different authorization identityThe provided authorization ID %s contained an invalid DN: %sThe server was unable to find any entry corresponding to authorization ID %sThe entry %s specified as the authorization identity does not existAn error occurred during multi-stage authentication: '%s'An error occurred while attempting to decode the SASL %s username "%s" because it appeared to contain a DN but DN decoding failed: %sAn error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL %s bind request: %sAn error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL %s authentication: %sAn error occurred while attempting to retrieve the SCRAM credentials for user '%s' in order to perform SASL %s authentication: %sAn unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %sAn error occurred while attempting to map authorization ID %s to a user entry: %sAn unexpected error occurred while trying to create an %s context: %sFailed to create a SASL server for SASL mechanism %sGSSAPI SASL mechanism handler initialization failed because the keytab file %s does not existThe server was not able to find any user entries for the provided username of %sSASL %s authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible formSASL %s authentication is not possible for user '%s' because the user entry does not contain any SCRAM credentialsSASL %s protocol error: %sThe %s SCRAM SASL mechanism handler could not be initialized because the algorithm is not supported by the JVMThe username in the SASL %s bind request appears to be an empty DN. This is not allowedThe 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 usernameAn error occurred while attempting to map username %s to a Directory Server entry: %sThe provided authorization ID was empty, which is not allowed for DIGEST-MD5 authenticationAn error occurred while attempting to validate the peer certificate presented by the client with a certificate from the user's entry %s: %sUnable to authenticate via SASL EXTERNAL because the mapped user entry %s does not have any certificates with which to verify the presented peer certificateThe SASL EXTERNAL bind request could not be processed because the client did not present a certificate chain during SSL/TLS negotiationThe SASL EXTERNAL bind request could not be processed because the associated bind request does not have a reference to the client connectionThe 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 ServerThe SASL EXTERNAL bind request could not be processed because the associated client connection instance is not an instance of LDAPClientConnectionUnable to authenticate via SASL EXTERNAL because the mapped user entry %s did not contain the peer certificate presented by the clientAn error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %sAn error occurred while attempting to create the JAAS login context for GSSAPI authentication: %sThe server was unable to because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be defined or neither definedThe authentication ID in the SASL PLAIN bind request appears to be an empty DN. This is not allowedAn error occurred while attempting to retrieve entry %s specified as the authorization ID: %sAn error occurred while attempting to map authorization ID %s to a user entry: %sThe authenticating user %s does not have sufficient privileges to specify an alternate authorization IDThe provided authorization ID %s contained an invalid DN: %sNo entry corresponding to authorization ID %s was found in the serverThe entry corresponding to authorization DN %s does not exist in the Directory ServerAn error occurred while attempting to verify the password for user %s during SASL PLAIN authentication: %sAn error occurred while attempting to decode the SASL PLAIN authentication ID "%s" because it appeared to contain a DN but DN decoding failed: %sAn error occurred while attempting to retrieve user entry %s as specified in the DN-based authentication ID of a SASL PLAIN bind request: %sAn error occurred while attempting to map username %s to a Directory Server entry: %sThe provided password is invalidThe server was not able to find any user entries for the provided authentication ID of %sThe 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 passwordSASL PLAIN authentication requires that SASL credentials be provided but none were included in the bind requestThe 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 passwordThe 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 IDThe 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 passwordUnable to decode peer certificate subject %s as a DN: %sConfiguration entry %s contains multiple mappings for certificate attribute %sConfiguration entry %s contains multiple mappings for user attribute %sThe 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 searchesConfiguration entry %s has value '%s' which violates the format required for attribute mappings. The expected format is 'certattr:userattr'The certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'The certificate with subject %s mapped to multiple usersPeer certificate subject %s does not contain any attributes for which a mapping has been establishedCould not map the provided certificate chain to a user entry because no peer certificate was availableMapping %s in configuration entry %s references attribute %s which is not defined in the server schemaCould not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %sUnable 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 %sAn 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 offlineAn 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 protocolSchema definition could not be parsed as valid attribute valueAn error occurred while attempting to determine whether any schema changes had been made by directly editing the schema files with the server offline: %sThere should be no warnings on the schema, but instead got %d warnings: %sUnable to retrieve the requested entry %s from the schema backend because the DN is equal to one of the schema entry DNsThe schema backend does not support the %s modification typeThe schema backend does not support the Replace modification type for the %s attribute typeAn error occurred while attempting to decode the ldapsyntax description "%s": %sAn 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 cleanupAn 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 requiredAn error occurred while attempting to write the updated schema: %sAn 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 requiredAn 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 cleanupCircular reference detected for attribute type %s in which the superior type chain references the attribute type itselfCircular reference detected for DIT structure rule %s in which the superior rule chain references the DIT structure rule itselfCircular reference detected for objectclass %s in which the superior class chain references the objectclass itselfThe server will not allow removing all values for the %s attribute type in the server schemaYou do not have sufficient privileges to modify the Directory Server schemaUnable to remove attribute type %s from the server schema because no such attribute type is definedUnable to remove DIT content rule %s from the server schema because no such DIT content rule is definedUnable to remove DIT structure rule %s from the server schema because no such DIT structure rule is definedUnable to remove ldap syntax description %s from the server schema because no such ldap syntax description is definedUnable to remove matching rule use %s from the server schema because no such matching rule use is definedUnable to remove name form %s from the server schema because no such name form is definedUnable to remove objectclass %s from the server schema because no such objectclass is definedThe 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 modifiedIgnoring schema definition '%s' because the following error occurred while it was being parsed: %sAn unexpected error occurred while trying to open the LDIF writer for the schema backend: %sAn error occurred while attempting to export the base schema entry: %sThe 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 searchesThe certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'The certificate with subject %s mapped to multiple usersCould not map the provided certificate chain to a user entry because no peer certificate was availableCould not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %sThe search request cannot be processed because it contains an LDAP assertion control and the assertion filter did not match the contents of the base entryThe entry %s cannot be searched due to insufficient access rightsAn unexpected error was encountered while processing a search in one of the Directory Server backends: %sThe entry %s specified as the search base does not exist in the Directory ServerThe 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: %sThe 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 togetherThe requested search operation included the persistent search control together with either the simple paged results control or the virtual list view control. These controls are mutually exclusive and cannot be used togetherThe search results cannot be sorted because the given search request is not indexedThe VLV request cannot be processed because the search is not indexed. Configure a VLV index matching the requestThe search request cannot be processed because it contains an LDAP assertion control but the search base entry does not existThe search base entry '%s' does not existThis search operation has sent the maximum of %d entries to the clientThe maximum time limit of %d seconds for processing this search operation has expiredYou do not have sufficient privileges to perform an unindexed searchThe 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 operationAn unexpected error occurred when looking for the replicated backend : %s. It may be not configured or disabledAn unexpected error occurred when loading the fractional replication configuration of domain "%s": %sAn unexpected error occurred when loading the generation id of domain "%s": %s'%s' cannot decode the secret file '%s': %sThe file '%s' exceeds max size '%s'Could not map the provided certificate chain to a user because the peer certificate subject "%s" could not be decoded as an LDAP DN: %sCould not map the provided certificate chain to a user because an error occurred while attempting to retrieve the user entry with DN "%s": %sCould not map the provided certificate chain to a user entry because no peer certificate was availableCould not map the provided certificate chain to a user because no user entry exists with a DN of %sCould not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)When sending a new initialization request for an initialization from a remote server, the following error occurred %s. The initial error was : %sAn unexpected error occurred while attempting to bootstrap the Directory Server client-side code: %sPeer '%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 adjustedServer is running. Please stop the server before running this toolAn error occurred while adding Service Discovery Mechanism '%s': %sDiscovery mechanism '%s' initialization failed : %sRegistering Service Discovery Manager's listener failed : %sError occurred while creating an SSL context for service discovery mechanism '%s' : %sService discovery mechanism '%s' failed to refresh the connection options. Exception : %s",Service discovery mechanism '%s' failed to refresh the partition information. Exception : %s",Could not retrieve auto-configuration data from directory server '%s' for replication server group '%s'. Exception : %s"Could not retrieve the list of replicas from replication server '%s' for replication server group '%s'. Exception : %sAn error occurred in session '%s' when trying to send a message to the socket: %sCould not access the %s keystore '%s'. Check that the content of the file corresponds to a valid keystore, that you have access rights to it and that a valid password has been provided if needed. Error details: %sCould not read the %s keystore '%s' entries. Check that the content of the file corresponds to a valid keystore, that you have access rights to it and that a valid password has been provided if needed. Error details: %sCould not access the PKCS#11 keystore. Check that the JVM security settings have been configured to use a PKCS#11 keystore and that a valid password has been provided if needed. Error details: %sCould not access the %s truststore '%s'. Check that the content of the file corresponds to a valid truststore, that you have access rights to it and that a valid password has been provided if needed. Error details: %sUnable to write the upgrade version in '%s' file (%s)The fully qualified host name must be a non blank stringUnable to bind to port %d. This port may already be in use, or you may not have permission to bind to itUnable to bind to port %d. This port may already be in use, or you may not have permission to bind to it. On UNIX-based operating systems, non-root users may not be allowed to bind to ports 1 through 1024An error occurred while configuring the server ID or the advertised listen address in global configuration: %sAn error occurred while creating the PKCS#11 key manager provider: %sAn error occurred while attempting to enable key manager provider entry: %sAn error occurred while attempting to update the administration connector port: %sAn error occurred while attempting to update the crypto manager in the Directory Server: %sAn error occurred while attempting to update the port on which to listen for LDAP communication: %sAn error occurred while attempting to update the port on which to listen for LDAPS communication: %sAn error occurred while attempting to update the entry for the initial Directory Server root user: %sUnable to write a required file. Make sure that the %s tool has sufficient permissions to create and write the file: %sYou cannot specify certificate aliases without providing an existing keystoreThe provided certificate nickname '%s' could not be found. The keystore contains the following certificate nicknames: %sclear-text password cannot be emptyThe --%s option should only be provided when using a file based trust store optionUnable to bootstrap the Directory Server configuration because of the following error: %sAn error occurred while writing password in configuration file: '%s'An error occurred while copying file '%s' into '%s': '%s'Unable to set access permissions to allow write operations on file '%s'. Ensure that you have enough rights to change the access permissions on instance filesAn error occurred while creating directory '%s'An error occurred while trying to write instance.loc file: %sAn error occurred while creating the file based trust manager provider: %sUnable to create server instance directory '%s'Unable to parse the version in '%s' file in order to initialize the content of the '%s' fileUnable to add certificates derived from deployment ID in keystore: %sThis deployment ID is using a key-pair generator which is not available in this Java environment. Retry the command with the Java environment that was used for generating this deployment IDUnable to display license because '%s'The value '%s' for parameter '%s' in profile '%s' is invalid. Please provide a value having the following syntax: %sInvalid profile parameter value '%s'. Supported format is '%s'Option to setup profile parameters have been provided but not the profile name. If you want to use a setup profile, please provide its name with the '%s' optionError in profile '%s': the default value for parameter '%s' cannot be derived from the SetupConfiguration method '%s' because the method invocation threw an error: %sError in profile '%s': the default value for parameter '%s' cannot be derived from the SetupConfiguration method '%s' because no such method existsThe parameter '%s' is required by profile '%s', but no value has been providedSetup profile '%s' cannot be found. %sSetup profile parameter '%s' references the profile '%s' which has not been provided on the command line. Setup profiles can be added on the command line with the '%s' optionSetup profile parameter '%s' has been provided multiple times with different values. Please either choose one value or prefix the option values with a profile nameProfile '%s' has been specified multiple times. It is not possible to configure the server for multiple versions of the same profile. Please choose one version for this profileThe server can only be enabled as a windows service on a Windows operating systemUnable to enable the file based HTTP access logger because: %sAn error occurred while enabling the %s trust manager provider: %sUnable to enable windows service (return code '%d'): %sUnable to encode provided password because '%s'You must specify the keystore password of the file based keystore. You can use either --%s or --%s options to specify itThe provided truststore file '%s' must be an existing readable fileThere is already a server instance configured in the directory %s. Please make sure there is no configuration (config) or data (db) directory in the server instance root pathA server instance (%s) has already been setup in the directory %sThe file '%s' is referring to an invalid instance (%s). You must remove this file before setting up a new instance in the directory %s. Please use either the --%s option in non interactive mode or the interactive mode to setup an instance elsewhereThe instance parent (%s) must be a valid existing directoryThe instance path must be a directoryThe file based keystore password cannot be emptyYou must specify a valid port number'%s' is not a valid hostnameInvalid input: keystore path cannot be emptyLicense not accepted, %s will exitInput tries limit reached (%d)Invalid configuration: you must use at least one certificate nicknameThe provided password values do not matchPlease provide a value having the following syntax: %sAdministration connector port '%d' is not in allowed range %d, %dHTTP port '%d' is not in allowed range %d, %dHTTPS port '%d' is not in allowed range %d, %dThe provided server install path '%s' must reference an existing directoryLDAP port '%d' is not in allowed range %d, %dLDAPS port '%d' is not in allowed range %d, %dPort '%d' is not in allowed range %d, %dReplication port '%d' is not in allowed range %d, %dYou cannot provide a keystore password without providing an existing keystoreYou must accept the product license to run setup. Either use interactive mode or the '--%s' optionUnable to write configuration file '%s' (%s)DN for the monitor user cannot be emptyMonitor user DN value '%s' is invalid because: %sThe keystore contains the following certificate nicknames: %s.%nYou have to provide the nickname of the certificate you want to useThe number of entries to import must be a positive integerThe deployment ID password is missing, provide it with the --%s optionNo private key entry found in keystore '%s'. Keystores used for securing client connections must contain at least one private key entry. Beware: you may need to provide the keystore password to access keystore private entriesThe root user password is missing, provide it with the --%s optionpassword is emptyThe provided password file '%s' must be an existing readable fileInvalid content for password file '%s'. A password file must contain a single line with the passwordUnable to read password in file '%s'. A password file must contain a single line with the keystore password, details: %sValue '%d' has been specified for different portsUnable to create '%s' backend (%s)Unable to add index for attribute '%s' (%s)An error occurred while initializing tool: %sInstance path '%s' is not a valid existing directoryInstance path '%s' does not contain an OpenDJ instanceYou must select at least one profile by using the option '%s'. %sUnable to setup the profile '%s' because it is already configured in the serverUnable to setup profiles '%s' because they are already configured in the serverProfiles can be setup only when the server is offline, please stop the server and retryUnable to create replication domain for base DN '%s' (%s)Unable to update server configurationThe value for DN parameter '%s' of profile '%s' cannot be emptyUnable to encode password associated to parameter '%s' of profile '%s' (%s)Unable to read file '%s'. Please ensure that the file exists and that you have appropriate permissions to read the fileAn IO error occurred while running profile '%s': '%s'Unable to import dataUnable to import data because some entries have been rejectedUnable to import data because some entries have been skippedUnable to import data (%s)Unable to import generated users (%s)The value '%s' for domain parameter '%s' of profile '%s' is invalid (%s)The value '%s' for parameter '%s' in profile '%s' is invalid because it does not match any allowed values (%s)Folder '%s' of the setup profile '%s' must be a readable existing folderFile '%s' from the setup profile '%s' must be a readable regular fileThe value for password parameter '%s' of profile '%s' is invalid (%s)Last folder of profile '%s' path '%s' must be the profile version (two or three digits separated by either dot or hyphen, e.g /path/to/profile/6.5.0)'%s' setup profile failed to update server configuration file, dsconfig tool options: '%s'. Exception message:'%s'. Tool output: %s'%s' setup profile failed to import data contained in '%s' file(s) into '%s' backend. Import LDIF tool options: '%s'. Exception message:'%s'. Tool output: %s'%s' setup profile failed to import data contained in '%s' file(s) into '%s' backend because of rejected entries (listed in '%s'). Import LDIF tool options: '%s'. Tool output: %s'%s' setup profile failed to import data contained in '%s' file(s) into '%s' backend because of skipped entries (listed in '%s'). Import LDIF tool options: '%s'. Tool output: %sFolder of the setup profile '%s' must contain a '%s' readable regular fileNo backend has been created in the profileThe value for domain parameter '%s' of profile '%s' cannot be blankUnable to read template file '%s'. Please ensure that the file exists and that you have appropriate permissions to read the fileAn error occurred while substituting properties from profile '%s' resource file '%s': %sThe '%s' setup profile failed: %sUnable to find resource '%s' of profile '%s' in profile version foldersAn error occurred while configuring replication: %sThe root user DN cannot be emptyThe administrator user bind DN '%s' is invalid. %sServer ID '%s' is not valid. A Server ID is an ASCII alpha-numeric string possibly containing underscore and hyphen charactersYou cannot specify truststore without providing an existing keystoreUnable to edit runtime settings file because '%s'An error occurred while trying to read instance.loc file: %sThe provided keystore file '%s' must be an existing readable fileUnable to write file '%s' because: '%s'An unexpected error has been raised during setup: '%s'An error occurred while attempting to update the HTTP connector port: '%s'An error occurred while attempting to update the HTTPS connector: '%s'An error occurred while storing provided password in the instance file '%s', details: %sThe 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)The current request is rejected due to an import or an export already in progress for the same dataThe specified skip file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the fileSkipping log "%s" (unsupported config)An error occurred while attempting to send an account status notification message for notification type %s for user entry %s: %sThe 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 serversSMTP 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 providedThe message subject definitions contained in configuration entry '%s' have multiple subjects defined for notification type %sUnable to parse message subject value '%s' from configuration entry '%s' because '%s' is not a valid account status notification typeUnable 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 subjectAn error occurred while attempting to parse message template file '%s' referenced in configuration entry '%s': %sThe message template file path definitions contained in configuration entry '%s' have multiple template file paths defined for notification type %sUnable to parse message template file path value '%s' from configuration entry '%s' because '%s' is not a valid account status notification typeUnable 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 pathThe message template file '%s' referenced in configuration entry '%s' does not existAn unclosed token was found starting at column %d of line %dThe notification-user-attr token starting at column %d of line %d references undefined attribute type %sThe notification-property token starting at column %d of line %d references undefined notification property %sAn unrecognized token %s was found at column %d of line %dThe 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 serverA fatal error occurred while trying to initialize soft reference entry cache: %sA Server Side Sort control must be specified whenever a Virtual List View control is presentYou do not have sufficient privileges to perform the sort requestUnable to process the provided server-side sort request control: %sWhen specifying a default user for monitoring a password should also be providedThe specified start time '%s' has already passedThe start date/time must in YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local timeAn error occurred while attempting to open the current configuration file %s for reading in order to copy it to the ".startok" file: %sAn error occurred while attempting to rename file %s to %s for use as the ".startok" configuration file: %sAn error occurred while attempting to copy the current configuration from file %s into temporary file %s for use as the ".startok" configuration file: %sStartTLS cannot be used on this client connection because this connection type is not capable of using StartTLS to protect its communicationA fatal error occurred when executing one of the Directory Server startup plugins: %s (error ID %d). The Directory Server startup process has been abortedGroup instance with DN %s has been deleted and is no longer validEntry %s cannot be parsed as a valid static group because it does not contain the groupOfEntries, groupOfNames or groupOfUniqueNames object classesAn error occurred while printing server status script friendly output: %sAn error occurred while reading the server configuration: %sUnable to perform the search on the monitor backend. To display information, the status tool requires the remote server monitor backend to be enabledERROR: Unable to decode the provided stop time. It should be in the form YYYYMMDDhhmmssZ for UTC time or YYYYMMDDhhmmss for local timeThe specified stop time '%s' has already passedERROR: An I/O error occurred while attempting to communicate with the Directory Server: %sThis operation involves LDAP subentries which you do not have sufficient privileges to administerThere was at least one error during the tasks execution: %sThe configured DN is already used by another domainUnable 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 attemptsAn error occurred while attempting to notify a synchronization provider of type %s about the schema changes made by the add schema file task: %sUnable 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: %sAn error occurred while attempting to load the contents of schema file %s into the server schema: %sYou do not have sufficient privileges to modify the server schemaUnable to add one or more files to the server schema because no schema file names were provided in attribute %s of task entry %sUnable to add one or more files to the server schema because the specified schema file %s does not exist in schema directory %sThe changes made by the add schema file task failed schema validation: %sYou do not have sufficient privileges to initiate a Directory Server backup or backup purgeAn error occurred while trying to parse the actual start time value %s from task entry %sAn error occurred while trying to parse the completion time value %s from task entry %sAn error occurred while trying to parse the scheduled start time value %s from task entry %sState for task '%s' cannot be determinedTask '%s' has finished and cannot be canceledThere are no tasks defined with ID '%s'Unable to decode value %s as an integer connection IDUnable 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'Attribute %s must be provided to specify the connection ID for the client to disconnectYou do not have sufficient privileges to terminate client connectionsThere is no client connection with connection ID %sOnly users with the SERVER_LOCKDOWN privilege connected from a loopback address may place the server in lockdown modeOnly users with the SERVER_LOCKDOWN privilege may place the server in lockdown modeAn error occurred while executing the task defined in entry %s: %sIndex option cannot be specified when the rebuildAll or rebuildDegraded option is usedYou do not have sufficient privileges to initiate an index rebuildInvalid DN provided to the Initialize task: %sInvalid DN provided to the Initialize Target task: %sAttribute %s has an invalid value. Reason: %sThe task defined in entry %s is invalid because it has an invalid state %sYou do not have sufficient privileges to initiate an LDIF exportYou do not have sufficient privileges to initiate an LDIF importOnly users with the SERVER_LOCKDOWN privilege connected from a loopback address may cause the server to leave lockdown modeOnly users with the SERVER_LOCKDOWN privilege may cause the server to leave lockdown modeTask entry %s is missing required attribute %sThere are multiple instances of attribute %s in task entry %sThere are multiple values for attribute %s in task entry %sInvalid DN provided to the Purge Conflicts Historical task: %sNo changelog database was found for baseDN '%s'. Either the baseDN is not replicated or its changelog has not been enabled in this serverUnable to reset the change number index: %sInvalid change number (%d) specified, it must be greater than zeroThe change number index cannot be reset because this OpenDJ instance does not appear to be a replication serverInvalid DN provided to the Reset Generation ID task: %sYou do not have sufficient privileges to initiate a Directory Server restoreYou do not have sufficient privileges to initiate a Directory Server restartYou do not have sufficient privileges to initiate a Directory Server shutdowntool exit with error return code '%d'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'New entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasksThe 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 pathThe 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 pathThe 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 fileUnable 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 entryUnable to remove entry %s from the task backend because there is no recurring task associated with that entry DNUnable to remove entry %s from the task backend because there is no scheduled task associated with that entry DNUnable to delete entry %s from the task backend because the associated task is currently runningAn error occurred while attempting to determine the new path to the task data backing file: %sThe 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 fileEntry %s cannot be modified because the associated task has completed running. Completed tasks cannot be modifiedEntry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backendEntry %s cannot be modified because it does not represent a valid task in the serverEntry %s cannot be modified because the server does not currently support modifying recurring task entriesThe 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"Unable to process the search operation in the task backend because the provided base DN %s is not valid for entries in the task backendUnable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %sUnable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %sError accessing logs for task '%s': %sError canceling task '%s': %sInvalid menu item or task number '%s'Task at index %d is not cancelableError retrieving task entry %s: %sError: task %s is not in a cancelable stateThere are no tasks with ID %sAn error occurred while attempting to export task backend data: %sAn error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %sAn error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %sAn error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?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?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 continueAn 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 containsAn 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 expectedAn error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %sAn error occurred while attempting to parse entry %s as a task and add it to the scheduler: %sAn 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: %sAn error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lostUnable to schedule task %s because its dependency task %s is missingUnable to add recurring task %s to the task scheduler because another recurring task already exists with the same IDUnable to schedule task %s because another task already exists with the same IDEntry %s read from the tasks backing file is invalid because it has no parent and does not match the task root DN of %sAn error occurred while attempting to read from the tasks data backing file %s: %sAn error occurred while attempting to schedule the next iteration of recurring task %s: %sEntry %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 ignoredThe provided task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowedThe 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 allowedThe provided task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logicThe 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 logicThe Directory Server is not configured to allow task %s to be invokedUnable to remove completed task %s because no such task exists in the list of completed tasksUnable to remove pending task %s because no such task existsUnable to remove pending task %s because the task is no longer pendingThe failed dependency action option is to be used in conjunction with one or more dependenciesThe value %s for option %s is not a valid email addressThe failed dependency action value %s is invalid. The value must be one of %sThe option %s is only applicable when scheduling this operation as a taskThe timeout of '%d' seconds has been reached. You can use the argument '--%s' to increase this timeoutAn error occurred in the trust store synchronization thread: %sUnable to load the configuration-enabled schema: %sAn unexpected error occurred while purging expired entries: %sUnable to retrieve children of configuration entry with dn: %sAn uncaught exception during processing for thread "%s" has caused it to terminate abnormally. The stack trace for that exception is: %s%s encountered an uncaught exception while processing operation %s: %sUnchecked exception during database transaction: %sPublish of a replication message to server '%s' was interruptedThe provided password does not contain enough unique characters. The minimum number of unique characters that may appear in a user password is %dThe entry %s has historical information for attribute %s which is not defined in the schema. This information will be ignoredThe base DN %s is not stored by any of the Directory Server backendAn unexpected error has been raised during execution of the tool: '%s'Digest algorithm '%s' of fingerprint '%s' is not supported by the JVMUnknown operation type : %sCannot decode change-log record with version %x%s in Replication Server=%s, an initialization message of type %s cannot be sent to its destination server. Details: routing table is empty%s message of type %s cannot be routed. Details: %s%s for domain %s cannot route message of type %s to all the replicas in the topology because none are reachable%s for domain '%s' cannot route message of type %s to replica %s because it is unreachable. Reachable replicas: %sAn unexpected error occurred when updating generation ID for domain "%s": %sAn error occurred while adding configuration file '%s': %sAn error occurred while adding one or more attributes to the schema file '%s': %sAn error occured when trying to read the configuration file %s: %s'%s' attributes couldn't be removed from backup tasksThe restore tasks couldn't be removedAttribute 'ds-backup-directory-path' could not be renamed to 'ds-backup-location' in entries of objectclass '%s'An error occurred when trying to upgrade the config/upgrade folder: %s"Error parsing existing schema file '%s' - %s"An error occurred while copying data from '%s' to the server instance configuration directory. Error details: %sAn error occurred while copying OpenDMK jar file '%s' to '%s': %sAn error occurred while copying the schema file '%s': %s'%s' is missing or empty, it is probably corruptedOpenDJ data has already been upgraded to version %sAn unexpected error occurred while attempting to display a confirmation : %sAn unexpected error occurred while attempting to display a notification: %sThe upgrade failed because %d errors were encountered. Please check log for further detailsThe argument '%s' is incompatible with '%s'Invalid log file %sInvalid sequence for task version: task %s tried to register for version %s but the previous task used a higher version: %s. This suggests there is a copy/paste error in the version numberThe upgrade failed to complete for the following reason: %sAn error occurred during post upgrade task. Process aborted. Please check log for further detailsAn error occurred while reading configuration file: %sOpenDJ cannot be upgraded because the server is currently running. Please stop the server and try againThe directory '%s' could not be created: %sAn error occurred reading the changelog files: %sAn error occurred while renaming the changelog files: %sThe file '%s' could not be renamed to '%s': %sAn error occurred while migrating encrypted changelog files: %sAn error occurred while migrating replicas' offline states to the changelog files: %sRoot DNs could not be migrated because the '%s' directory could not be created: %sAn error occurred while trying to modify %s : %sCould not find a server ID to set for the server. Verify the configuration references a valid server ID for domain cn=admin dataAn error occurred while performing an upgrade task: %sThe OpenDJ binary version '%s' is older than the configuration version '%s', it usually means that an older version has been unzipped over the previous binaries. Unzip a more recent version than the configuration version and run upgrade againThe OpenDJ binary version '%s' is older than the data version '%s', it usually means that an older version has been unzipped over the previous binaries. Unzip a more recent version than the data version and run upgrade againNo %s with OID %s exists in the schemaOpenDJ has already been upgraded to version %sAn error occurred while uploading the file to the cloud storage. The cloud provider returned the following error message: '%s'An error occurred while uploading the file to the cloud storage: the host '%s' is an unknown hostCrypto manager configuration entry not foundThe %s attribute is not searchable and should not be included in otherwise unindexed search filtersCounter of %s reports wrong number of entries for key <%s> (got %d, expecting %d)File dn2id is missing key %sFile dn2id has DN <%s> referencing unknown ID %dFile dn2id has DN <%s> referencing entry with wrong DN <%s>File dn2id has ID %d instead of %d for key %sDuplicate reference to ID %d%n%sEmpty ID set: %n%sThe entry with ID %s is associated with the wrong key%n%sFile id2childrenCount has wrong number of children for DN <%s> (got %d, expecting %d)File id2ChildrenCount references non-existing EntryID <%d>Missing entry %s in index %sMissing ID %d%n%sReference to entry <%s> which does not match the value%n%sReference to unknown entry ID %s%n%sReference to unknown ID %d%n%sThe stored entry count in id2entry (%d) does not agree with the actual number of entry records found (%d)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 continueAn error occurred while attempting to perform index verification: %sOnly one index at a time may be verified for cleanlinessThe version of the installed OpenDJ could not be determined because the version file '%s' exists but contains invalid data. Restore it from backup before continuingThe version of the installed OpenDJ could not be determined because the version file '%s' could not be found. Restore it from backup before continuingAltering membership for virtual static group %s is not allowedUnable to decode "%s" as the target DN for group %s: %sThe virtual static group defined in entry %s contains multiple target group DNs, but only one is allowedThe virtual static group defined in entry %s does not contain a target group definitionTarget group %s referenced by virtual static group %s does not existVirtual 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 groupUnable to process the virtual list view request because the target assertion could not be decoded as a valid value for the '%s' attribute typeThere is no VLV index configured with name '%s'An unexpected error occurred cleaning up the service %sCould not find the service with name %sAn 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)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)The Windows Service was successfully configured but there was an error starting it. Error code starting Windows Service: %dThe server could not be enabled to run as a Windows service. The service name is already in useCould not find the service name for the serverAn unexpected error occurred starting the server as a windows serviceAn unexpected error occurred trying to retrieve the state of the server as a Windows serviceAn unexpected error occurred stopping the server windows serviceThe 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)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)An unexpected error happened handling connection with %s. This connection is going to be closedCould not find 'ads-certificate' entry in the truststore '%s'. This entry is required for the correct behavior of the directory serverUnable to retrieve the local hostname, the 'advertised-listen-address' attribute in global configuration must be set manuallyA mandatory argument is missing. Choose one and only one argument from '--generate-recovery-id', '--generated-id' and '--user-generated-id'An error occurred when launching initialization: %sAn error occurred during initialization. Last log details: %s. Task state: %sAn error occurred during initialization. Task state: %sError during the processing of the reset generationID task. Last log details: %s. Task state: %sError during the processing of the reset generationID task. Task state: %sA mandatory argument is missing. Choose one and only one argument from '--toServer', '--fromServer' and '--toAllServers'An error occurred while attempting to monitor the task progress. The error was: %sAn error occurred while purging old replication meta-data. Last log details: %s. Task state: %sAn error occurred while purging old replication meta-data. Task state: %sAn error occurred while purging old replication meta-data: %sThe source and target server have distinct replication domains. As a consequence the change number from the target server can't be reset from a change number of the source serverAn error occurred during the re-synchronization of the change number. Last log details: %s. Task state: %sAn error occurred during the re-synchronization of the change number. Task state: %sAn error occurred when re-synchronizing the change number: %sAn error occurred when searching replicated domains in server: %sNo base DN found for the change number '%s' in the source serverNo CSN found for the change number '%s' in the source serverUnable to find a replicated domain in the target serverUnable to find a replicated domain matching the DN '%s' corresponding to the change numberError when searching change number '%s' in the source server: %sUnable to retrieve the newest change number in the source serverUnable to retrieve change number '%s' in the source serverAn error occurred when searching replicated domains in server. Result code was: '%s'Invalid combination of arguments. Choose one and only one argument from '--toServer', '--fromServer' and '--toAllServers'Replication server RS(%s) ignoring update %s for domain "%s" from replication server RS(%s) at %s because its generation ID %s is different to the local generation ID %sError while loading "java.properties": %sCould not find "java.properties"Parameter(s) '%s' provided for profile '%s' is (are) not used in the profileParameter '%s' is provided without any profile specification which is not allowed when multiple profiles are usedAn error occurred while removing some 'listen-address' attribute values from the configurationThe current 7.4.0 server is configured to use an incompatible confidentiality setting which prevents automated upgrade from working. Follow the procedure detailed in the Upgrade Guide to upgrade this serverAn attempt to add the entry "%s" containing an aci attribute type failed, because the authorization DN "%s" lacked modify-acl privilegesAdded %s Access Control Instruction (ACI) attribute types found in context "%s" to the access control evaluation engineAdded %s Global Access Control Instruction (ACI) attribute types to the access control evaluation engineAn unexpected error occurred while processing the aci attributes in the configuration system: %sAn unexpected error occurred while processing the ds-cfg-global-aci attribute in configuration entry %s: %sAn attempt to modify an aci attribute type in the entry "%s" failed, because the authorization DN "%s" lacked modify-acl privileges{action}The add operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the requestAdding %sAdministration connector portThe following archive has been created : %s{args}Define and enable a default user for querying monitoring information?{attribute}{backendName}Backend ID(s)Backup LocationStorage propertyBackup ID(s)Backup locationForceKeep countRemove older thanBackend name(s)Purge backup(s){baseDN}{branchDN}Free memory = %d MB, Cache miss rate = %.1f/recordThe operation was canceled because the client issued an abandon request (message ID %d) for this operationProcessing on this operation has been canceled because the Directory Server received a bind request on this connection, which requires that all operations in progress to be abandonedProcessing on this operation has been canceled because the Directory Server is shutting downUpgrade failed to delete the obsolete file '%s'. Reason: %sCursor on replica '%s' invalidatedLog file '%s' was successfully recovered by removing unreadable records. The file changed size from %d to %d bytes.Arguments for changelogstat: %s{base dn}{change number}{csn}{directory}{clearPW}Change number indexing will resume since replica '%s' is now sending messages againCollecting backend statisticsCollecting ChangelogDb informationNo changelogDb data found (is a DS or is not replicated)Disk informationExtract environment variablesCollecting the GC log filesCollecting JVM heap dump : using %sCollecting the log filesCollecting the monitoring info from cn=monitorNetwork informationCollecting system node informationOS informationLinux /proc info filesLinux releaseDS /proc filesCollecting process statisticsCollecting process thread information, sample number : %dProcessor informationCollecting the configuration filesVM environment informationOpenDJ will be upgraded from version %s to %sThe backend defined in configuration entry %s is marked as disabled and therefore will not be used%s.%s succeeded but generated the following messages for entry %s: %sPassword policy entry %s has been removed from the Directory Server configuration. Any user entries that explicitly reference this password policy will no longer be allowed to authenticateOpenDJ configuration was successfully upgraded to version %sOpenDJ configuration will be upgraded from version %s to %sThe class used to provide the Directory Server work queue implementation has been changed from %s to %s, but this change will not take effect until the server is restartedDisables the server as a Windows service and removes the Windows registry information associated with the specified serviceDisables the server as a Windows service and stops the serverEnables the server as a Windows serviceProvides information about the state of the server as a Windows serviceThis utility can be used to configure the server as a Windows serviceAn internal error prevented the Directory Server from properly registering the client connection from %s to %s with an appropriate request handler: %sContinuing data gathering though there was an error: %sMaking copy of the %s file before collecting process statisticsThe name of the group account under which the server should runA set of arguments that should be passed to the JVM when running the serverThe path to the Java installation that should be used to run the serverThe path to the RC script to createThe path to the systemd service file to createCreate an RC script or systemd service that may be used to start, stop, and restart the Directory Server on UNIX-based systemsThe name of the user account under which the server should runOpenDJ data will be upgraded to version %sOpenDJ data was successfully upgraded to version %sOpenDJ data will be upgraded from version %s to %s{databaseName}Remove LDIF change record remnants from the configurationThe delete operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the requestRemoving file copy %s{deploymentIdPassword}{deploymentId}The backend ID of the backendThe base DN within the backendThe name of the indexOnly show records whose data is no larger than the provided valueOnly show records with keys that should be ordered before the provided value using the comparator for the database containerOnly show records whose data is no smaller than the provided valueOnly show records with keys that should be ordered after the provided value using the comparator for the database containerThe raw database nameDo not try to decode backend data to their appropriate typesDo not display backend data, just statisticsList the base DNs in a backendShows the status of indexes for a backend base DN. This subcommand can take a long time to complete, as it reads all indexes for all backendsThis utility can be used to debug a backendDump records from an index, decoding keys and values. Depending on index size, this subcommand can generate lots of outputDump the raw records in hexadecimal format for a low-level database within the pluggable backend's storage engine. Depending on index size, this subcommand can generate lots of outputList the pluggable backendsList the indexes associated with a pluggable backend. This subcommand may take a long time to complete depending on the size of the backendList the low-level databases within a pluggable backend's storage engine. This subcommand may take a long time to complete depending on the size of the backendWrite hexadecimal data on a single line instead of pretty formatUses SI Units for printing sizesThis utility can be used to debug changelog and changenumber filesThe base-dn of the changes contained in the provided replica DB fileThe lower bound of the range of change numbers to dumpThe lower bound of the range of changes to dumpThe output directory for the dump filesDump the change number DBDump the replica DB for a given domain and replicaDump a replica DB fileThe upper bound of the range of change numbers to dumpThe upper bound of the range of changes to dumpInitialize replication data for the serverThis tool manages data synchronization between servers. For replication to work you must initialize the contents of one of the servers with the contents of the others using the '%s' subcommandPerforms disaster recovery on the local server. The subcommand has two forms. The first form verifies each replica has the same data after recovery: on a replica, run dsrepl disaster-recovery --baseDn dc=example,dc=com --generate-recovery-id The command prints the identifier to use on all other servers with the --generated-id option: dsrepl disaster-recovery --baseDn dc=example,dc=com --generated-id {identifier} The second form uses an identifier you provide. It lets you automate the recovery process when you cannot use the first form. Do not use this form if the topology has standalone replication servers. With this form of the subcommand, you must ensure you recover each replica with the same data. Run the same subcommand on all servers. Example: dsrepl disaster-recovery --baseDn dc=example,dc=com --user-generated-id Recovery_Date_20240101 Read the documentation on disaster recovery carefully before using this commandEnd disaster recovery for all servers. Read the documentation on disaster recovery carefully before using this commandPurges old replication meta-data from application dataRe-synchronizes the change-log change number of the target server with the change-log change number of the source serverStart disaster recovery for all servers. Read the documentation on disaster recovery carefully before using this commandDisplays the status of the replication service and various diagnostics about it. The information is derived from reading cn=monitor on all the servers in the replication topology. The status of a server is one of the following. - BAD - DATA MISMATCH: either the fractional replication configuration does not match the backend data, or the initial state of the replicated data does not match other servers and this server must be re-initialized; - BAD - TOO LATE: the server has fallen further behind than the replication purge delay and must be re-initialized; - GOOD: normal operation, nothing to do; - SLOW: the server's replay delay is greater than five seconds; - UNHEALTHY: read the server health errors in the server monitoring data for detailsPath were the instance should be set upIndicates the task is recurring and will be scheduled according to the value argument expressed in crontab(5) compatible time/date patternWhen this argument is specified, the status command will display its contents periodically. Used to specify the period (in seconds) between two displays of the statusIndicates the date/time at which this operation will start when scheduled as a server task expressed in YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time. A value of '0' will cause the task to be scheduled for immediate execution. When this option is specified the operation will be scheduled to start at the specified time after which this utility will exit immediatelyAdds the local server (with version 7.0 or more) to a topology with older server versions (prior to 7.0)Clean all the servers (with version 7.0 or more) that have been migrated from a topology of older servers (version prior to 7.0)Clears all replication server changelog data for the offline local server; the other replication servers in the topology will transfer any needed data when the server restartsDecodes one or more CSNs and displays them in a human readable JSON formatEmail address of a recipient to be notified when the task completes. This option may be specified more than onceID of a task upon which this task depends. A task will not start execution until all its dependencies have completed executionGives a description to the taskEmail address of a recipient to be notified if an error occurs when this task executes. This option may be specified more than onceAction this task will take should one if its dependent tasks fail. The value must be one of %s. If not specified defaults to %sGives an ID to the taskTask Backend Connection OptionsTask Scheduling OptionsDIGEST-MD5 SASL mechanism using a realm of: %sThe Directory Server is beginning the configuration bootstrapping processAdministrative TerminationConnection Closed by PluginAdministrative Limit ExceededClient DisconnectIdle Time Limit ExceededInvalid CredentialsI/O ErrorI/O TimeoutMaximum Request Size ExceededProtocol ErrorClient Connection RejectedSecurity ProblemServer ErrorServer ShutdownClient UnbindServer in lockdown modeUnknown Closure ReasonAttempt to start using the configuration that was in place at the last successful startup (if it is available) rather than using the current active configurationDo not detach from the terminal and continue running in the foreground. This option cannot be used with the -t, --timeout optionDisplay general system informationMaximum time (in seconds) to wait before the command returns (the server continues the startup process, regardless). A value of '0' indicates an infinite timeout, which means that the command returns only when the server startup is completed. The default value is 60 seconds. This option cannot be used with the -N, --nodetach optionThis utility can be used to start the Directory Server, as well as to obtain the server version and other forms of general server informationBase DN(s) to use. Multiple base DNs can be provided by using this option multiple timesCheck the server error logs for additional detailsServers have been cleaned, however the administrator user '%s' in the admin backend was not removed because it was used to bind to the server. To remove it, you should run the following commands on all servers using a bind DN, such as "uid=admin", which lies outside the "cn=admin data" backend:All servers have been cleanedAll servers have been cleaned. The admin backend will remain enabled because it contains secret keys that may be used by reversible password storage schemesThis server has already been cleaned, there is nothing left to doCleaning and updating configuration of server %sDisable admin backend for server %sRemoving administrators from admin backendRemoving instance keys from admin backendRemoving servers from admin backendThe server %s has now been cleanedSet bootstrap servers configuration for server %sThe remaining cleanup on this server cannot be performed because the administrator user '%s' in the admin backend was used to bind to the server. You should run again this command using a bind DN, such as "uid=admin", which lies outside the "cn=admin data" backend to be able to complete the cleanup on this serverNothing to do: this server does not keep any replication server changelog dataClearing all replication server changelog data for the local servercsn [csn ...]Base DN of the domain to be recoveredThe disaster recovery process has been canceled, no operation was performed. This server may still not be operationaldsrepl disaster-recovery --baseDn '%s' --generated-id %sThe disaster recovery process completed successfully for the first server. The next step is to restore the same data using the same procedure on all the remaining servers in the topology and run the following command on each server:Disaster recovery id: %sDisaster recovery for base DN '%s' ended successfully on this server{generatedRecoveryId}Starting disaster recovery on local server for base DN '%s'Disaster recovery for domain '%s' has already been run with recovery ID '%s'. Verify all servers in the topology are being recovered with the same recovery IDEnabling 'cn=admin data' backendServer ID of the server containing the source dataGenerate a disaster recovery identifier during recovery. Use this for the first directory server in a replication topology with standalone RS servers. For all subsequent servers to recover, omit this option and use --generated-id {generatedRecoveryId} with the generated identifierUse the disaster recovery identifier generated on the first server. You must use the same identifier for all servers involved in the same disaster recovery procedureContinue the disaster recovery procedureDisaster recovery will erase replication metadata on this server. This server will then only be able to replicate changes with other recovered servers. You will have to run the recovery procedure on every other server of the topology. Servers which have not been recovered will not be able to connect to recovered servers anymoreAdding server instances keys from the existing topology into 'cn=admin data' in the new serverBase DN(s) to replicateCannot find a CA certificate in the replication trust managers of the local server. Please verify the %s trust-manager-provider configuration valueCannot extract the master key pair certificate with alias '%s' because the crypto-manager's key manager provider of the local server does not contain such key or does not support extracting certificatesUpdating replication configuration on local serverUpdating replication configuration for baseDN '%s' on local serverConfiguring the servers in the topology to talk to the local serverCreating the trust manager '%s' to be used by replication connections in the local serverReplication has been successfully configured on the local server. Note that for replication to work you must initialize the contents of the base DNs that are being replicated. Run the following command(s) to do so:Maximum duration of the command in seconds{maximum duration in seconds}Purging old replication meta-data for server '%s' for base DNs: %sThe change number to use as the basis for re-synchronization{change number}Change number corresponds to start CSN '%s' and base DN '%s'Re-synchronizing with change number '%s'Start to re-synchronize the change-log change number of server '%s' from the source server '%s'Starting initialization for base DN: '%s'Starting initialization from '%s' to '%s' for base DNs: %sStarting initialization from '%s' to all replicas for base DNs: %sBase DN(s) to display. Multiple base DNs can be provided by using this option multiple times. If no base DNs are provided, then all the base DNs will be displayedBase DNBase DN / DSBase DN / RSBase DN / RS / DSEntry countError or diagnosticGroupHostnameReceive delay (ms)Replay delay (ms)Server / host portStatusDisplays individual changelog servers in the outputDisplay replication group information in the outputDisplays individual replicas in the outputInitialize all the other servers in the topologyServer ID of the server to be initializedSet the identifier for this recovery to {userGeneratedRecoveryId}, a string of your choice. Do not use this option if the replication topology has standalone RS servers. You must use the same identifier for all servers involved in the same disaster recovery procedure.{userGeneratedRecoveryId}{emailAddress}{encodedPW}Use the authentication password syntax rather than the user password syntaxClear-text password to encode or to compare against an encoded passwordEncoded password to compare against the clear-text passwordThe password to encode or to compare against an encoded password is interactively asked to the userList available password storage schemesScheme to use for the encoded passwordUse the LDAP compare result as an exit code for the password comparisonPlease enter the password :Please renter the password:The provided clear-text and encoded passwords do not matchThe provided clear-text and encoded passwords matchThis utility can be used to encode user passwords with a specified storage scheme, or to determine whether a given clear-text value matches a provided encoded passwordJE backend '%s' does not specify the number of cleaner threads: defaulting to %d threadsJE backend '%s' does not specify the number of lock tables: defaulting to %dConnection handler '%s' does not specify the number of request handler threads: defaulting to %d threadsNo worker queue thread pool size specified: sizing automatically to use %d threadsAn error occurred while configuring the certificates: %sAn error occurred while copying the file '%s' to '%s'An error occurred creating the temporary fileAn error occurred while deleting directory '%s'. Check that you have the rights to delete this directory and that there is no other application using it. Error was: %sAn error occurred while deleting file '%s': %s. Check that you have the rights to delete this file and that there is no other application using itError Enabling Windows serviceError Installing Backup Cloud Extension for Directory Server: %sUnable to process operation because this search scope is not allowed in this network groupError Starting Directory ServerError Starting Directory Server. Error code: %sAppend To LDIFBackend IDCompress LDIFEncrypt LDIFExclude AttributeExclude BranchExclude FilterInclude AttributeInclude BranchInclude FilterLDIF FileSign HashWrap Column%s%s with exception: %sLaunch external process: '%s'External process standard output: %sProcessing on this operation was terminated as a result of receiving a cancel request (message ID %d)Password to use to bind to the server{password}Collect log files after this date. Format "YYYYMMDDhhmmss" like "20161123143612" = 23 November 2016, 14:36 12s. Overrides --maxLogFiles{date}Maximum number of log files to collect. Ignored if --logsAfterDate is provided{number}Specifies whether a Java Heap Dump (using jmap) should be produced. The binary file is generated at the same location as the ZIP archive before being added to it; please make sure that the target directory's volume has sufficient capacitySpecifies whether audit files are excludedSpecifies whether keystore files are excludedSpecifies that the tool should not interact with the server, that is no LDAP operation, and no jstack samplingThe folder into which the files will be placed into{directory}When the server is embedded in OpenAM, there is no PID file. Therefore this option indicates the server PID of the OpenAM application server{pid}This tool collects support data from the OpenDJ instance it is bound toPath to the JDK utility binaries directory such as jstack{directory}CancelDisableProcess{filter}{serverSource}See %s for a detailed log of the failed operation.%nPlease report this error and provide the log file mentioned aboveGenerating stack dump, sample number : %d using %s for pid %dRegistered %d static groups, %d dynamic groups and %d virtual static groups. The static group cache is using %d bytes of memory{groupName}GSSAPI mechanism using a principal name of: %sGSSAPI SASL mechanism using a server fully qualified domain name of: %sThe GSSAPI SASL mechanism handler initialization was successfulThe GSSAPI SASL mechanism handler has been stoppedUse %s %s to list profile parametersProfiles available with this OpenDJ version are:{host}This connection has been terminated because it has remained idle for too longBackend IDClear BackendExclude AttributeExclude BranchExclude FilterInclude AttributeInclude BranchInclude FilterIs CompressedIs EncryptedLDIF FileOverwriteRandom SeedReject FileSkip FileSkip Schema ValidationTemplate FileThe filter value exceeded the index entry limit for the %s index%s index is invalid and needs to be rebuilt%s index type is disabled for the %s attribute{indexName}{index}%s entries processed (%s %% complete)%s entries processed%s remaining to be processedTask '%s' to initialize domain '%s' failed to contact the source server. The task will be retried because the current server may be in the process of re-connecting to the best replication server for itselfThe instance is not runningThe instance is runningInternal operations can't be cancelledNo value was provided for %s, JDK tool directory is set to %sBackend IDBase DN80th95th99thEntry LimitKey CountOverMeanMedianIndex NameSecureSizeTypeRecords%nIndex: %s%nKey (len %d):Keys SizeOver index-entry-limit keys: %s%nRaw DB Name%nTotal: %d%nTotal / Average Data Size: %d bytes / %d bytes%nTotal / Average Key Size: %d bytes / %d bytes%nTotal Keys%nTotal Records: %d%nTotal SizeValue (len %d):Values SizeThe Directory Server is closing the connection to this clientThe change to the LDIF backend base DN will not take effect until the backend is disabled and re-enabledThe change to the LDIF file path will not take effect until the backend is disabled and re-enabledThe change to the LDIF backend visibility will not take effect until the backend is disabled and re-enabledAdditional Info: %sMatched DN: %sReferral URL: %sResult Code: %d (%s)Append an existing LDIF file rather than overwriting itBackend ID for the backend to exportCompress the LDIF data as it is exportedAttribute to exclude from the LDIF exportBase DN of a branch to exclude from the LDIF exportFilter to identify entries to exclude from the LDIF exportExclude operational attributes from the LDIF exportAttribute to include in the LDIF exportBase DN of a branch to include in the LDIF exportFilter to identify entries to include in the LDIF exportPath to the LDIF file to write. All paths are relative to the server's installation directory, which can be remoteColumn at which to wrap long lines (0 for no wrapping)Exporting to %sThis utility can be used to export data from a Directory Server backend in LDIF form{ldifFile}Backend ID for the backend to importRemove all entries for all base DNs in the backend before importingCount the number of entries rejected by the server and return that value as the exit code (values > 255 will be reduced to 255 due to exit code restrictions)Attribute to exclude from the LDIF importBase DN of a branch to exclude from the LDIF importFilter to identify entries to exclude from the LDIF importAttribute to include in the LDIF importBase DN of a branch to include in the LDIF importFilter to identify entries to include in the LDIF importLDIF file is compressedPath to the LDIF file to import. All paths are relative to the server's installation directory, which can be remoteOverwrite an existing rejects and/or skip file rather than appending to itUse quiet mode (no output)Seed for the MakeLDIF random number generator. To always generate the same data with the same command, use the same non-zero seed value. A value of zero (the default) results in different data each time the tool is runWrite rejected entries to the specified fileWrite skipped entries to the specified fileSkip schema validation during the LDIF importPath to temporary directory for index scratch files during LDIF importPath to a MakeLDIF template to use to generate the import dataNumber of threads used to read LDIF files during import. If 0, the number of threads will be set to twice the number of CPUs{directory}{count}This utility can be used to import LDIF data into a Directory Server backend, overwriting existing data. It cannot be used to append data to the backend databaseDo you accept the License Agreement?Please read the License Agreement above.%nYou must accept the terms of the agreement before continuing with the installationThe following logging categories are defined for the server: %sListing the security stores{maxDataSize}{maxKeyValue}{minDataSize}{minKeyValue}The modify DN operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the requestThe user account has been administratively disabledThe user account has been administratively enabledThe user account has been administratively unlockedThe modify operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the requestThe user password has been changedThe user password has been administratively reset{monitorUserDn}{monitorUserPassword}The monitor configuration has been updated so that it will now use a new set of user-defined attributesSkipping GC logs collection because GC logging is not enabledNo JVM stack dump can be produced when the server is not running or no server interaction is allowedNo monitoring data can be collected when the server is not running or no server interaction is allowed%s: received message <%s>{path}{period}The Referential Integrity plugin has started background processing using the update interval %sThe Referential Integrity plugin background processing has been stoppedThe Referential Integrity plugin background processing update interval has been changed from %s to %s, the new value will now be during background processingThe file name that the Referential Integrity plugin logs changes to during background processing has been changed from %s to %s, but this change will not take effect until the server is restartedThe Referential Integrity plugin failed when performing a search because the base DN %s does not existDefault:Derived from the setup global optionsDescription:%s (%s) parametersParameter:Profile '%s (%s)' does not have any parametersDoneEnabling Windows serviceError.....Starting directory serverConfiguring certificatesnonyesyProxy backend '%s' automatically registered itself against the base DNs %s. It was previously registered against the base DNs %sConfiguration of proxy backend '%s' with service discovery mechanism '%s' is in progress. Requests will not be proxied until configuration completesProxy backend '%s' successfully configured failover via the service discovery mechanism '%s': primary servers are %s and secondary servers are %sThe primary servers for proxy backend '%s' are now available and will be used for proxying requestsThe secondary servers for proxy backend '%s' are now available and will be used if the primary servers are unavailableThe server '%s' for proxy backend '%s' is available and will be used for proxying requestsThe purge delay has been set to: %sPurging is disabled (delay set to 0)Base DN of a backend supporting indexing. Rebuild is performed on indexes within the scope of the given base DNIndicates that indexes do not need rebuilding because they are known to be empty and forcefully marks them as valid. This is an advanced option which must only be used in cases where a degraded index is known to be empty and does not therefore need rebuildingNames of index(es) to rebuild. For an attribute index this is simply an attribute name. At least one index must be specified for rebuild. Cannot be used with the "--rebuildAll" optionRebuild all indexes, including any DN2ID, DN2URI, VLV and extensible indexes. Cannot be used with the "-i" option or the "--rebuildDegraded" optionRebuild all degraded indexes, including any DN2ID, DN2URI, VLV and extensible indexes. Cannot be used with the "-i" option or the "--rebuildAll" optionPath to temporary directory for index scratch files during index rebuilding{directory}This utility can be used to rebuild index data within an indexed backend database{schedulePattern}{rejectFile}Replacing non allowed comma in groupID definition with a dotDirectory server DS(%s) did not find a generation ID for domain '%s'. A new generation ID will be computed by exporting the first %d entries in the domainChecking registration informationEstablishing connectionsReplication server RS(%s) has accepted a connection from directory server DS(%s) for domain "%s" at %sReplication server RS(%s) has accepted a connection from replication server RS(%s) for domain "%s" at %sReplication server RS(%s) has connected to replication server RS(%s) for domain "%s" at %sBackup DirectoryBackup IDInvalid CredentialsOperations ErrorThe root DSE configuration has been updated so that configuration attribute %s will now use a value of %sThe root DSE configuration has been updated so that it will now use a new set of user-defined attributesAn unsupported or unexpected callback was provided to the SASL server for use during %s authentication: %s{seconds}{seed}Root user DNServer IDMonitor userMonitor user passwordSkipping backup of %s log (file not found){serviceName}{bootstrapReplicationServer}{nickname}Configuring serverAccept these choices and continue?Port on which the Administration Connector should listen for communicationAvailable setup profiles: %sThe addresses of one or more replication servers within the topology which the server should connect to for discovering the rest of the topology. Use syntax "hostname:port" or "[IPv6Address]:port" for IPv6 addressesNickname of a keystore entry containing a certificate that the server should use when negotiating secure connections using StartTLS or SSL. Multiple keystore entries may be provided by using this option multiple timesDeployment ID passwordEnable StartTLS to allow secure communication with the server using the LDAP portEnable the server to run as a Windows ServiceDisplay profile parametersDisplay all available profilesThe fully-qualified directory server host name that will be used when generating certificates for LDAP SSL/StartTLS, the administration connector, and replicationPath of the file containing the keystore password. The specified path will be used as the configuration value in the new serverPort on which the Directory Server should listen for LDAP communicationPort on which the Directory Server should listen for LDAPS communication. The LDAPS port will be configured and SSL will be enabled only if this option is explicitly specifiedDN of the default user allowed to query monitoring informationPassword of the default user allowed to query monitoring informationThere are no setup profiles available for this OpenDJ versionSetup profile to apply when initially configuring the server. If the version is not specified, the most recent version older or equal to this OpenDJ version is used. Use this option multiple times to apply multiple profiles. This option cannot be combined with data import options. %sAssign a value to a setup profile parameter. Profile name must be provided if multiple profiles are provided, indicate the profile that a parameter applies to by using the profileName/parameterName formatPort used for replication protocol communications with other servers. Use this option to configure a local replication server. When this option is not used, this server is configured as a standalone DS (no local replication server)DN for the initial root user for the Directory ServerPassword for the initial root user for the Directory ServerSpecify the server ID for this server. An acceptable ID is an ASCII alpha-numeric string; it may also contain underscore and hyphen characters provided they are not the first characterSkip the check to determine whether the specified ports are usableStart the server when the configuration is completedBlindly trust peer SSL certificatesPath of the file containing the truststore password. The specified path will be used as the configuration value in the new serverThe deployment ID which should be used for securing the deployment. If no existing certificates are specified using the key-store and trust-store options then the deployment ID will also be used for securing all TLS network communicationPath of a JCEKS keystore containing the certificate(s) that the server should use when negotiating secure connections using StartTLS or SSLUse existing JCEKS truststore file for validating peer SSL certificatesPath of a JKS keystore containing the certificate(s) that the server should use when negotiating secure connections using StartTLS or SSLUse existing JKS truststore file for validating peer SSL certificatesUse certificate(s) in a PKCS#11 token that the server should use when accepting SSL-based connections or performing StartTLS negotiationPath of a PKCS#12 keystore containing the certificate(s) that the server should use when negotiating secure connections using StartTLS or SSLUse existing PKCS12 truststore file for validating peer SSL certificatesEnable windows service command (return code '%d') output: %sYou have chosen to combine an evaluation profile with another profile that is intended for production. Applying an evaluation profile after others can compromise the security of your server. Review the server configuration carefully before deploymentPort on which the server should listen for HTTP communicationPort on which the server should listen for HTTPS communicationDo you want to add another replication serverAdministration connector portAll Server ParametersReplication server hostnameWhat are the hostname and port number of the server to replicate with? (e.g ds.example.com on port 8989)Replication port on %sReplicate with serverUse an existing certificate in a JCEKS keystoreUse an existing certificate in a JKS keystoreUse an existing certificate on a PKCS#11 tokenUse an existing certificate in a PKCS#12 keystoreConfigure server for profile '%s'What would you like to do?Confirm the password for the default monitor user:Confirm the password for root user:How would you like to secure your deployment?You already have a CA certificate for the deployment and an SSL key-pair for this serverGenerate a CA certificate and SSL key-pair using the deployment ID (easier to deploy, but not suitable for public facing services)DisabledEnable HTTP?Enable HTTPS?Enable LDAP?Enable LDAPS?Listening on port %dEnabledEquivalent non-interactive command:Provide the deployment ID:Global ParametersWelcome to the OpenDJ %s interactive setup.%n%nInteractive mode helps you quickly set up an OpenDJ server.%nProvide all required options to set up the server in non-interactive mode,%nor use the command shown at the end of your interactive sessionProvide the server's fully qualified host nameProvide hostname for '%s'Provide port for '%s'HTTP portHTTPS portDo you want to specify a server to replicate with? This step can be skipped if this is the first server in the topologyJCEKS truststore path:JKS truststore path:Provide the SSL certificate that will be used for securing server connections:LDAP portLDAPS portThe keystore contains the following certificate nicknames: %s.%nYou will be prompted for the nickname(s) to useDo you want to add another value for parameter '%s'?Network ParametersNo password providedNo value specified for '%s'PKCS#12 truststore path:Confirm the %s:Value set for '%s'Provide a value for '%s'Which version of '%s' do you want to use (minimum %s)?Customize Server With ProfilesEnter profile number(s) separated by comma (leave empty to skip this step):Available profiles:Enter profile number(s) separated by comma [%s]:Use nickname %s?Provide the deployment ID password:Enable the server to run as a Windows Service?Provide the server instance pathJCEKS keystore path:Java keystore (JKS) path:Keystore password:Provide the DN for the default monitor userProvide the password for the default monitor user:PKCS#12 keystore path:Provide the directory root user DNProvide the password for root user (leave empty to use the deployment ID password):Unique server ID (used for identifying the server in the topology)Start the server when setup is complete? Note: starting with version 7.0, it is advised to only start the server once it is customized for the intended deployment. If more configuration is needed, then select 'no'QuitReplication portSet up the server with the specified settingsDo you want to set a value for parameter '%s'?Start overCertificate nickname(s) to useServer securityNo profiles configured or data to be importedUse existing JCEKS keystoreUse existing JCEKS truststoreUse existing JKS keystoreUse existing JKS truststoreKeystore fileKeystore passwordUse existing PKCS#11 keystoreUse existing PKCS#12 keystoreUse existing PKCS#12 truststoreConfigure server for profile '%s (%s)'Trust remote server certificatesTruststore fileTruststore passwordSame as deployment ID passwordServer's fully qualified host nameHTTP (cleartext)HTTPS (secure)Server instance pathLDAP (cleartext)LDAPS (secure)Root user passwordReplication (secure)Start server after setupUse deployment IDRun as Windows serviceHow should the server trust certificates from SSL peers?Truststore password (leave empty if the truststore has no password):Blindly trust all certificates (evaluation only - unsafe for production)Use a JCEKS truststoreUse a JKS truststoreUse the JVM truststoreUse a PKCS#12 truststore{path}Name of the profile to be configured. If the version is not specified, the most recent version older or equal to this OpenDJ version is used. Use this option multiple times to apply multiple profilesPath of the server instance where profiles should be setupconfigure profiles in an offline OpenDJ server instanceThis utility configures profiles in an offline OpenDJ server instance. %sDecimal numberDNDomain nameOne of the following values:File or directory pathhost:portNumber{[profileName/]parameterName:value}Syntax:%s or configuration expressionPassword{name[:version]}Stringinstall OpenDJ server{rootUserDN}{rootUserPassword}Configuring profile %s{serverId}To see basic server status and configuration, you can launch %s{path}Validating parameters{skipFile}Skipping audit filesSkipping %sSkipping java security storesDirectory Account Status NotificationUnable to process the provided server-side sort request control because it included attribute %s which does not have a default ordering matching rule and no ordering rule was specified in the sort keyReplication server accepted a connection from %s to local address %s but the SSL handshake failed. This is probably benign, but may indicate a transient network outage or a misconfigured client application connecting to this replication server. The error was: %s{startTime}Administration port (LDAPS)Active cacheBackendTypeLoad m1 rateLoad m5 rateNamePortProtocolThis utility can be used to display basic server informationConnect to the server to obtain disk space informationConnect to the server to obtain JVM informationThere are no connection handlers setup in the serverConnection handlersFree spaceDisk spaceNo disks are monitored by the serverStateEntriesReceive delayReplay delayReplicationBase DNGeneral detailsHost nameInstallation and instance pathInstallation pathInstance pathJava vendorJava versionJVM max heap sizeJVM available CPUsThere are no local backends setup in the serverLocal backendsOpen connectionsThere are no proxy backends setup in the serverProxy backendsRunning server Java detailsServer IDRun statusStartedStoppedVersion{stopReason}{stopTime}Reason the server is being stopped or restartedIndicates the date/time at which the shutdown operation will begin as a server task expressed in format YYYYMMDDhhmmssZ for UTC time or YYYYMMDDhhmmss for local time. A value of '0' will cause the shutdown to be scheduled for immediate execution. When this option is specified the operation will be scheduled to start at the specified time after which this utility will exit immediatelyStopping Server...Server already stoppedThis utility can be used to request that the Directory Server stop running or perform a restart. When run without explicit connection options, this utility sends a signal to the OpenDJ process to stop the server. When run with explicit connection options, this utility connects to the OpenDJ administration port and creates a shutdown task to stop the server{scheme}Add Schema FileBackupTask ID: %s Task State: %s Scheduled Start Time: %s Actual Start Time: %s Completion Time: %s Description: %s Log Messages:{description}Disconnect ClientAn administrator has terminated this client connectionLockdownExport{taskID}ImportInitialize From ReplicaInitialize BackendLeave LockdownPurge conflicts historicalRebuild IndexReset change number index to begin with a given number and changeRestoreSet Generation IDThe Directory Server shutdown process has been initiated by task %s: %sThe Directory Server shutdown process has been initiated by task %sShutdownCanceled before startingCompleted successfullyCompleted with errorsDisabledRecurringRunningStopped by administratorStopped by errorStopped by shutdownUnscheduledWaiting on dependencyWaiting on start time{taskStatus}Task was stopped by an administrator: %sRecurring %s task %s scheduled successfully%s task %s did not complete successfully%s task %s scheduled to start %s%s task %s scheduled to start immediately%s task %s has been successfully completed{taskType}RetryingThis file contains the data used by the Directory Server task scheduler backend. Do not edit this file directly, as there is a risk that those changes will be lost. Scheduled and recurring task definitions should only be edited using the administration utilities provided with the Directory ServerThe tasks backend is being shut downTask processing was interrupted by a modify request to cancel the taskThe path to the task data backing file has been changed to %s. A snapshot of the current task configuration has been written to that file and it will continue to be used for future updatesThe completed task retention time has been updated to %d seconds. This will take effect immediatelycancel taskcEnter the number of a task to cancelTask %s canceledrefreshrview logslTask DetailsActual Start TimeCompletion TimeDependenciesDescriptionFailed Dependency ActionIDLast Log MessageLog Message(s)Email Upon CompletionEmail Upon ErrorScheduled Start TimeStatusTypeImmediate executionError connecting to the directory server: '%s'. Verify that the connection options are correct and that the server is runningThere are currently no cancelable tasksNo tasks existNoneNone Specified%s OptionsShow only tasks with this statusPrint a summary of tasksID of a particular task to cancelID of a particular task about which this tool will display informationThis utility can be used to obtain a list of tasks scheduled to run within the Directory Server as well as information about individual tasksShow only tasks of this type{templateFile}The server '%s' may retry the initialization process because the server '%s' in domain '%s' is temporarily unreachable%d days, %d hours, %d minutes, %d seconds%d hours, %d minutes, %d seconds%d minutes, %d seconds%d seconds{serverToInitialize}Cannot extract process statistics (by running "top" command) on OS '%s'. Only %s dump samples will be collectedError while trying to add entry %s to the trust store: %sError while searching base %s to synchronize the trust store: %sThe upgrade has been canceledAdd ACI to make Root DSE fullVendorVersion operational attribute user visibleAdd a new HDAP authorization mechanism '%s'Adding 'ds-cfg-exclude-values-of-attributes' with the list the attribute names which values will be excluded from the list of requested modificationsYou have to rebuild all indexes manually to get a fully functional serverAllowing dsbackup purge tasksAdd 'ldapSyntaxes' to attribute list which can be read in the schema access global access control policiesRemoving 'ds-cfg-argon2-migration-memory' and adding 'ds-cfg-argon2-memory-pool-size' which specifies the size of the memory pool allocated for concurrent Argon2 password hashing computations...Change(s) done in %s (x%s)The classes folder has been renamed to '%s' to avoid compatibility issuesOpenDJ data can't be upgraded because the configuration has not been upgraded yet. Upgrade the configuration first before upgrading the dataRemoving debug logging configurationRemoving replica degraded status threshold configurationRemoving deprecated HTTP Basic DN and JWT authorization mechanisms. The HDAP authorization mechanism '%s' replaces themRemoving look through limit from the configurationRemoving LDAP send reject notification configurationRemoving VLV indexes with base-object scope from the configurationUpgrades OpenDJ configuration and application data so that it is compatible with the installed binaries.%n%nThis tool should be run immediately after upgrading the OpenDJ binaries and before restarting the server.%n%nNOTE: this tool does not provide backup or restore capabilities. Therefore, it is the responsibility of the OpenDJ administrator to take necessary precautions before performing the upgradeContinue to allow invalid certificate lists, certificate pairs and postal addressesThe upgrade is ready to proceed. Do you wish to continue?Enabling change numbers in the replication changelogSee '%s' for a detailed log of this operationMigrating JE environment properties to configuration attributes...No change applied in %sNo indexes to rebuild for backend '%s'Upgrades only application data. OpenDJ configuration must have been upgraded beforeForces a non-interactive upgrade to continue even if it requires user interaction. In particular, long running or critical upgrade tasks, such as re-indexing, which require user confirmation will be performed automatically. This option may only be used with the '%s' optionIgnores any errors which occur during the upgrade. This option should be used with caution and may be useful in automated deployments where potential errors are known in advance and resolved after the upgrade has completedPerforming post upgrade tasksPerforming upgradePost upgrade tasks completeEnd of the upgrade processRebuilding all indexesChanges in Unicode string normalization require that all indexes are rebuilt. Do you want to rebuild the indexes automatically at the end of the upgrade?OPENDJ-9550 on 7.3.0 caused static groups to lose their operational attributes on modify operations, corrupting data and the entryUUID index which needs to be rebuilt. Do you want to rebuild the indexes automatically at the end of the upgrade?The rebuild index tool arguments are %sRebuild index task endsRebuilding index(es) %s for base dn(s): %sYou have to rebuild the '%s' index(es) manually to get a fully functional serverOpenDJ 7.0.0 changed the indexing algorithm for TelephoneNumber equality and substring matching rules. All TelephoneNumber syntax based attribute indexes must be rebuilt which may take a long time. Do you want to rebuild the indexes automatically at the end of the upgrade?Removing 'backup' backendRemoving empty configuration for groupsRemoving references to 'backup' backendRemoving '%s' attribute(s) from backup tasksRemoving restore tasksRemoving SNMP supportRemoving max-work-queue-capacityRenaming 'ds-cfg-cursor-entry-limit' to 'ds-cfg-max-candidate-set-size'Replace the authentication mechanism of the '/hdap' endpoint '%s' with the new HDAP authorization mechanism '%s'Replace multiple severity values by a single one in logging configurationsPreparing to upgradeDS 7.0.0 breaks restore tasks compatibility, all existing restore tasks will be removedOpenDJ was successfully upgraded to version %sAdding configuration entry '%s'Adding '%s' configuration fileAdding Mail ServersReplacing compute change number setting in replication serverConsolidating bootstrap replication servers from replication server and replication domains into Multimaster Synchronization providerSet the database cache mode 'ds-cfg-db-cache-mode' to 'cache-ln'Removing file '%s'Use the old JE backend caches instead of the new shared cacheChanging syntax for 'inheritAttribute' attribute type to IA5StringAdd 'inheritFromDNParent' attribute type to the 'inheritedCollectiveAttributeSubentry' object classReplacing high durability settings in JE backendsReplacing low durability settings in JE backendsReplacing medium durability settings in JE backendsMake the File-Based Error Loggers perform asynchronous logging for optimal performance after merging the debug and error loggerMigrating replication changelog files to 6.5.0 formatThe upgrade will not be performed because the configuration file config.ldif could not be parsedRemove External change log domain configuration entries and migrate information to the domains and the replication server configuration entriesMigrating encrypted replication changelog filesMigrate isolation policy attribute to replication synchronization provider configurationMerge replication-purge-delay and conflicts-historical-purge-delay attribute into a single replication-purge-delay attribute in replication synchronizer provider configurationMigrate common replication domain configuration attributes to replication synchronization provider configurationThe upgrade will not be performed because some Root DNs need to be migratedRemoving root DN users from configurationOpenDJ 6.0.0 drops support for Root DNs and replaces them with standard user entries which are stored in LDIF backends. The root DN '%s' has multiple alias names, but only the alias name '%s' will be kept. Do you want to proceed with the upgrade?OpenDJ 6.0.0 drops support for Root DNs and replaces them with standard user entries which are stored in LDIF backends. The root DN '%s' does not have an alias name so it must be renamed to '%s' so that it no longer resides inside the configuration. Do you want to proceed with the upgrade?Migrating root DN '%s'Migrate source address attribute from replication server configuration to replication synchronization provider configurationMigrating truststore backend configurationMigrating truststore backend configuration to crypto managerMove SSL protocols and cipher suites configuration from crypto manager into each configuration element where they are used%s.%nDo you want to make this change?WARNING: OpenDJ %s removes support for the PDB Backends. The upgrade tool will reconfigure all PDB backends as JE backends. After the upgrade the new JE backend(s) will be empty. It is therefore very strongly recommended that any data that was in the PDB backends be exported to LDIF so that it can be re-imported once the upgrade completesReconfiguring PDB backends to JE backendsYou must reimport all your data into the JE backends in order to have a fully functional serverUpdating existing Prometheus endpoints to keep using the legacy formatSet the proxy backend configuration property 'hash-function' to MD5OpenDJ 6.5.0 changed the indexing algorithm for replication metadata. Its index must be rebuilt which may take a long time; without a working index every server start will take longer than normal. Do you want to rebuild the index automatically at the end of the upgrade?OpenDJ 7.2.0 fixed an indexing bug that may cause searches to return duplicate entries in certain circumstances. All indexes have to be rebuilt. This could take a long time to proceed. Do you want to launch this process automatically at the end of the upgrade?Archiving concatenated schemaReplacing "reject unauthenticated requests" policy in global configurationRemoving configuration for assured replicationRemoving configuration entries for the monitor providersRemoving configuration for replication monitoringThe attribute has been removed because it was referring to a file that does not exist. You should replace it with the attribute %s before being able to enable the object corresponding to the configuration entryRemoving profiler pluginsRemoving 'ds-cfg-load-balancing-algorithm' attribute from the proxy backendRemoving generation-id data from configurationRemoving 'listen-address' attributes that are redundant with default value provided by the global configurationRemoving synchronization state data from configurationRemoving 'ds-cfg-request-connection-pool-size' attribute,'ds-cfg-connection-pool-size' will be used insteadRemoving global server ID from replication domains and replication serverRemoving send and receive window size configuration in replicationRename attribute 'ds-backup-directory-path' to 'ds-backup-location' in entries of objectClass '%s'Renaming 'ds-cfg-big-index-matching-rule' attribute to 'ds-cfg-big-index-extensible-matching-rule`Renaming 'ds-cfg-bind-connection-pool-*' attributes to 'ds-cfg-connection-pool-*'Renaming replication changelog files from .log to .cdb suffixRenaming ds-cfg-connection-pool-* attributes to ds-cfg-bind-connection-pool-*Renaming 'ds-cfg-json-schema' object class to 'ds-cfg-json-query-equality-matching-rule'Renaming 'ds-cfg-log-control-oids' attribute to 'ds-cfg-log-controls'Renaming the 'use-mutual-tls' configuration property to 'use-sasl-external'Renaming PDB backend directory '%s' to '%s'Renaming proxy 'ds-cfg-heartbeat-*' attributes to 'ds-cfg-keep-alive-*`Renaming the 'replication-server' configuration property to 'bootstrap-replication-server'Renaming the proxy backend configuration property 'service discovery mechanism' to 'shard'Replacing all pin related configuration attributes by a single pin configuration attributeReplacing schema file '%s'Segregating mutable and immutable filesAdding 'listen-address' and 'advertised-listen-address' attributes to the global configurationSetting global group ID and removing per domain valuesSetting global server IDSetting new global server IDUpdate admin-backend.ldif file locationAdding objectClass to JSON, CSV, and External access logger configurationsMigrating security settingsUpdate replication SSL configurationUpdate replication SSL configuration from crypto manager and trust store backend to dedicated key and trust manager provider configuration elementsUpdate tasks backend file locationOpenDJ Upgrade UtilityThis tool cannot be used for upgrading versions of OpenDJ which are older than '%s'. Please upgrade to the latest 6.5 revision first before attempting further upgrades{userName}Average number of entries referenced is %.2f/recordNumber of records that exceed the entry limit: %dStatistics for records that have exceeded the entry limit:File %s has %d such record(s) min=%d max=%d median=%dMaximum number of entries referenced by any record is %dNumber of records referencing more than one entry: %dBase DN of a backend supporting indexing. Verification is performed on indexes within the scope of the given base DNCount the number of errors found during the verification and return that value as the exit code (values > 255 will be reduced to 255 due to exit code restrictions)Name of an index to be verified. For an attribute index this is simply an attribute name. Multiple indexes may be verified for completeness, or all indexes if no indexes are specified. An index is complete if each index value references all entries containing that valueSpecifies that a single index should be verified to ensure it is clean. An index is clean if each index value references only entries containing that value. Only one index at a time may be verified in this wayThis utility ensures that index data is consistent within an indexed backend database. Stop the server before running this toolPath to a file containing log output to monitorPath to a file to which the command will write the outputPath to the file to watch for deletionMaximum length of time in seconds to wait for the target file to be deleted before exitingThis utility can be used to wait for a file to be removed from the filesystemThe server was already disabled as a Windows serviceThe server was already enabled to run as a Windows serviceClean up of service %s was successfulNext Generation Directory Server. Installation path: %sThe server is disabled as a Windows serviceThe server is enabled as a Windows service. The service name for the server is: %s%sThe server was successfully disabled as a Windows serviceThe server was successfully enabled to run as a Windows service%s has been stopped because the total number of worker threads in the Directory Server was reduced{wrapColumn}The SASL mechanism "%s" provided in the Access Control Instruction (ACI) bind rule authmethod expression is not one of the currently registered mechanisms in the serverAvailable Processors: %dDS(%s) stayed connected to RS(%s) to avoid the yoyo effectThe backend %s is now taken offlineThe database backend %s containing %d entries has startedIgnoring reset generation ID request from '%s' to '%s' for replica '%s' because the replica is being re-initializedRS(%s) has been evaluated to be the best replication server for DS(%s) to connect to because it was the only one standing after all testsDS(%s) will connect to RS(%s) because it has the biggest weight among all the replication serversBuild ID: %sAccess control has been enabled and will use the %s implementationThe requested change to configuration entry %s would cause the class for the associated backend to change from %s to %s. This change will not take effect until the backend is disabled and re-enabled, or until the Directory Server is restartedThe change to the DB directory will not take effect until the backend is restarted. The DB files from the previous directory %s must be moved to the new directory %s after shutting down the backend to retain the existing dataThe Directory Server is starting using the last known good configuration file %s rather than the active configuration file %sChanging confidentiality for index '%s' requires the index to be rebuilt before it can be used againSome index keys have already exceeded the previous index entry limit in index %s. This index must be rebuilt before it can use the new limitStarted listening for new connections on %sStopped listening for new connections on %sCurrent Directory: %sDIGEST-MD5 SASL mechanism using a server fully qualified domain name of: %sDirectory server DS(%s) for domain "%s" has changed its status to %sThe Directory Server is leaving lockdown mode and will resume normal operationThe Directory Server has started successfully%s (build %s, revision number %s) starting upDS(%s) disconnected from overloaded RS(%s)The free space (%s) on the disk containing directory "%s" is now above the low threshold for the following subsystems: %sDS(%s) not disconnected from current RS(%s), because RS is underloaded or its load goal is reachedDS(%s) not disconnected from overloaded RS(%s), other DSs will disconnectThis replica `%s` has received a notification from its replication server `%s` to stop processing updates for domain `%s` as part of a disaster recovery procedure. This replica must be reinitialized as part of the recovery procedureCannot change the configuration while a total update is in progressFractional replication : exception for domain : %s : %sWrong fractional replication configuration : cannot use both exclusive and inclusive modesWrong fractional replication configuration : attribute %s is not optional in class %sWrong fractional replication configuration : prohibited attribute %s usageWrong fractional replication configuration : could not find attribute type definition for %s in schemaWrong fractional replication configuration: could not find object class definition for %s in schemaWrong fractional replication configuration : wrong format : %s (need at least [<className>|*],attributeName)The export of domain %s from server %s to all other servers of the topology is forbidden as the source server has some fractional configuration : only fractional servers in a replicated topology does not make senseThe following operation has been forbidden in suffix %s due to inconsistency with the fractional replication configuration : %sThe online full update for importing suffix %s data from remote directory server %s has been stopped due to fractional configuration inconsistency between destination and source server : imported data set has not the same fractional configurationThe online full update for importing suffix %s data from remote directory server %s has been stopped due to fractional configuration inconsistency between destination and source server : imported data set has some fractional configuration but not destination serverThe LDIF import for importing suffix %s data has been stopped due to fractional configuration inconsistency : imported data set has not the same fractional configuration as local serverThe LDIF import for importing suffix %s data has been stopped due to fractional configuration inconsistency : imported data set has some fractional configuration but not local serverError when loading a virtual attribute for external change log: Attribute: %s , Error: %sAccount-Status-Notification type='%s' userdn='%s' id=%d msg='%s'Exported %d entries and skipped %d in %d seconds (average rate %.1f/sec)Exported %d records and skipped %d (recent rate %.1f/sec)Warning : domain %s fractional replication configuration is inconsistent with backend data set : need resynchronization or fractional configuration to be changedCurrently Free Memory: %dFinished total update: exported domain "%s" from this directory server DS(%s) to remote directory server DS(%s). %sFinished total update: exported domain "%s" from this directory server DS(%s) to all remote directory servers. %sStarting total update: exporting %d entries in domain "%s" from this directory server DS(%s) to remote directory server DS(%s)Starting total update: exporting %d entries in domain "%s" from this directory server DS(%s) to all remote directory serversFinished total update: imported domain "%s" from remote directory server DS(%s) to this directory server DS(%s). %sStarting total update: importing domain "%s" from remote directory server DS(%s) to this directory server DS(%s)Flushing data to diskProcessed %d entries, imported %d, skipped %d and rejected %d in %d seconds (average rate %.1f/sec)Setting DB cache size to %d bytes and phase one buffer size to %d bytesIndex %s phase two processing completedIndex %s phase two started processing %d buffers in %d batchesSetting DB cache size to %d MB. Using %d mb off-heap memory through %d phase one buffers of %d KBIndex %s %d%% complete: remaining = %d KB, rate = %d KB/s; batch %d/%dImport LDIF environment close took %d secondsThe amount of free memory available to the import task is %d bytes. The number of phase one buffers required is %d buffersTotal import time was %d seconds. Phase one processing completed in %d seconds, phase two processing completed in %d secondsProcessed %d entries, skipped %d and rejected %d (recent rate %.1f/sec)%s starting import (build %s, R%s)Import Thread Count: %d threadsDue to changes in the configuration, index %s is currently operating in a degraded state and must be rebuilt before it can be usedInstallation Directory: %sInstance Directory: %sClass Path: %sJAVA Home: %sJAVA Vendor: %sJAVA Version: %sJVM Architecture: %sJVM Arguments: %sJVM Host: %s, running %s, %d bytes physical memory size, number of processors available %dJVM Host: %s, running %s, unknown physical memory size, number of processors available %dJVM Information: %s by %s, %s architecture, %d bytes heap sizeJVM Vendor: %sJVM Version: %sDirectory Server DS(%s) is disconnecting from replication server RS(%s) at %s for domain "%s" in order to find another replication server in the topology and distribute load more equallyMax Available Memory: %dDirectory Server DS(%s) is switching from replication server RS(%s) at %s to RS(%s) for domain "%s" because it is more suitable. The previous replication server evaluation was: "%s", and the new replication server evaluation was: "%s"DS(%s) not disconnected from current RS(%s), since there is no need to rebalance all directory servers to other replication servers in the topologyDirectory server DS(%s) has connected to replication server RS(%s) for domain "%s" at %s with generation ID %sOperating System: %sConnection options have changed for the proxy backend '%s'. The existing connections are being closed immediately. New ones are being openedConnection pool options have changed for the proxy backend '%s'. The existing connections are being closed and re-openedRemote servers changed for the proxy backend '%s'. The proxy was using: primary servers=%s, secondary servers=%s; and it will now be using: primary servers=%s, secondary servers=%sService discovery mechanism has changed from '%s' to '%s' for proxy backend '%s'. The existing connections are being closed immediatelyException when reading messages from %s: %sAn I/O error occurred while reading replication messages from %s. The connection will close and replication server (%s) will not process any more updates from it. Reported error is: %s%s is disconnecting from this replication server %sRebuild of all indexes started with %d total entries to processDegraded state of index(es) %s has been clearedRebuild of all degraded indexes started with %d total entries to processRebuild complete. Processed %d entries in %d seconds (average rate %.1f/sec)Rebuilding index finished: no indexes to rebuild%.1f%% Completed. Processed %d/%d entries. (recent rate %.1f/sec)Rebuild of index(es) %s started with %d total entries to processA referral entry %s indicates that the operation must be processed at a different serverRejecting the requested operation because the server is in lockdown mode and will only accept requests from root users over loopback connectionsReplication server RS(%s) started listening for new connections on address %s port %dResending a new initialization request for an initialization from a remote server due to the root error : %sThe generation ID for domain "%s" has been reset to %sRS(%s) generation Id %s does not match DS(%s) generation Id %s, but at least another RS doesRS(%s) groupId '%s' does not match DS(%s) groupId '%s', but at least one other RS doesRS(%s) groupId '%s' has lower priority than groupId '%s' which matched at least one other RSRS(%s) has no generation Id, but at least one other RS has the same generation Id %s as DS(%s)RS(%s) newest change %s is behind another RS which is ahead of DS(%s) newest change %sRS(%s) newest change %s is behind DS(%s) newest change %s, but at least another RS is at the same point or ahead of the DSRS(%s) is on a different host than DS(%s), but at least another RS is on the same hostRS(%s) is not on the same virtual machine as DS(%s) but another RS isA schema element could not be imported: %s, %sYou do not have sufficient privileges to perform a search request on cn=changelogThe Directory Server has sent an alert notification generated by class %s (alert type %s, alert ID %s): %sThe Directory Server has started the shutdown process. The shutdown was initiated by an instance of class %s and the reason provided for the shutdown was %sServerState recovery for domain %s, updated with changeNumber %sThe Directory Server is now stoppedSystem Name: %s%s task %s finished execution in the state %s%s task %s started executionCurrently Used Memory: %dInstallation Directory: unknownInstance Directory: unknownRS(%s) could not be contacted by DS(%s)Both equality and presence index types are defined for attribute '%s'. When no presence index exists, presence search filters are processed using the equality index. Therefore, consider deleting the presence index for attribute '%s'An unresolved conflict was detected in CSN %s replaying an ADD of "%s" which already exists (adding as "%s"). Consider reviewing both entries and either merge the contents manually or delete oneAn unresolved conflict was detected in CSN %s replaying an ADD of "%s" as the parent entry is missing (adding as "%s"). Consider restoring the parent entry, or deleting the new entryAn unresolved conflict was detected in CSN %s replaying a DELETE of "%s" as child entries exist (renaming child "%s" to "%s"). Consider restoring the parent entry, or deleting the renamed child entriesAn unresolved conflict was detected in CSN %s replaying a MODIFYDN of "%s" to "%s" which already exists (renaming as "%s"). Consider merging the two entries manually, or deleting one of themAn unresolved conflict was detected in CSN %s replaying a MODIFYDN of "%s" as the new parent entry "%s" does not exist. Consider restoring the parent entry, or deleting this entryChecked %d records and found %d error(s) in %d seconds (average rate %.1f/sec)Checked %d entries and found %d error(s) in %d seconds (average rate %.1f/sec)Processed %d out of %d records and found %d error(s) (recent rate %.1f/sec)%sThe global access control policy '%s' has been addedThe global access control policy '%s' has been modifiedThe global access control policy '%s' has been removedThe global access control engine has been initialized with %d policiesInitial result code was '%s', with diagnostic message: %sgather OpenDJ backend debugging informationdebug changelog and changenumber filesscript to manage OpenDJ as a service on UNIXManages data synchronization between serversencode a password with a storage schemeexport directory data in LDIFextract support dataimport directory data from LDIFmanage server administration tasksrebuild index after configuration changestart OpenDJ serverdisplay basic OpenDJ server informationstop OpenDJ serverupgrade OpenDJ configuration and application datacheck index for consistency or errorsregister OpenDJ server as a Windows ServiceThis utility sets up an OpenDJ server. Use the %s option to list available profiles<xinclude:include href="variablelist-backendstat-index-status.xml" /><xinclude:include href="description-recurring-task-info.xml" /><xinclude:include href="description-upgrade.xml" /><xinclude:include href="description-supportextract.xml" />An attempt to add the entry "%s" containing an aci attribute type failed because of the following reason: %s"%s", located in the entry "%s", because of the following reason: %sBackend %s does not have a presence index defined for attribute type %s. Access control initialization may take a very long time to complete in this backendThe server is being put into lockdown mode because invalid ACIs rules were detected either when the server was started or during a backend initializationAn error occurred while attempting to determine whether hostname %s referenced in dns expression bind rule "%s" used the correct canonical representation: %s. This likely means that the provided hostname will never match any clientsThe provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, which resolves to IP address %s, but the canonical hostname for that IP address is %s. This likely means that the provided hostname will never match any clientsThe provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, but the canonical representation for that hostname is configured to be %s. The server will attempt to automatically interpret the correct localhost valueAn attempt to modify an aci attribute type in the entry "%s" failed because of the following reason: %sSelfwrite check skipped because an attribute "%s" with a distinguished name syntax was not a valid DNFailed to decode the Access Control Instruction (ACI)%sThe provided Access Control Instruction (ACI) bind rule value "%s" is invalid because it is missing a close parenthesis that corresponded to the initial open parenthesisThe provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the numeric OID contained two consecutive periods at position %dThe provided string "%s" could not be parsed as a valid Access Control Instruction (ACI) because it failed general ACI syntax evaluationThe provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the value contained an illegal character %c at position %dThe provided Access Control Instruction access type value "%s" is invalid. A valid access type value is either allow or denyThe provided Access Control Instruction (ACI) attribute name value %s is invalid. A valid attribute type name must begin with an ASCII letter and must contain only ASCII letters,digits or the "-" characterThe provided Access Control Instruction (ACI) bind rule authmethod expression value "%s" is invalid. A valid authmethod value is one of the following: none, simple,SSL, or "sasl mechanism", where mechanism is one of the supported SASL mechanisms including CRAM-MD5, DIGEST-MD5, and GSSAPIThe provided Access Control Instruction (ACI) bind rule boolean operator value "%s" is invalid. A valid bind rule boolean operator value is either "OR" or "AND"The provided Access Control Instruction (ACI) bind rule keyword value "%s" is invalid. A valid keyword value is one of the following: userdn, groupdn, roledn, userattr,ip, dns, dayofweek, timeofday or authmethodThe provided Access Control Instruction (ACI) bind rule keyword string "%s" is invalid for the bind rule operator string "%s"The provided Access Control Instruction (ACI) bind rule operator value "%s" is invalid. A valid bind rule operator value is either '=' or "!="The provided Access Control Instruction (ACI) bind rule value "%s" is invalid. A valid bind rule value must be in the following form: keyword operator "expression"The provided Access Control Instruction (ACI) bind rule dayofweek expression value "%s" is invalid, because of an invalid day of week value. A valid dayofweek value is one of the following English three-letter abbreviations for the days of the week: sun, mon, tue, wed, thu, fri, or satThe provided Access Control Instruction (ACI) bind rule dns expression value "%s" is invalid. A valid dns keyword expression value requires a valid fully qualified DNS domain nameThe provided Access Control Instruction (ACI) bind rule dns expression value "%s" is invalid, because a wild-card pattern was found in the wrong position. A valid dns keyword wild-card expression value requires the '*' character only be in the leftmost position of the domain nameThe provided Access Control Instruction (ACI) bind rule groupdn expression value "%s" is invalid. A valid groupdn keyword expression value requires one or more LDAP URLs in the following format: ldap:///groupdn [|| ldap:///groupdn] ... [|| ldap:///groupdn]The provided Access Control Instruction (ACI) bind rule groupdn expression value failed to URL decode for the following reason: %sThe provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid because it is non-numericThe provided Access Control Instruction (ACI) bind rule ip expression value "%s" is invalid. A valid ip keyword expression requires one or more comma-separated elements of a valid IP address list expressionThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" format was invalidThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" contains an invalid value. All values of the address must be between 0 and 255The provided Access Control Instruction (ACI) bind rule IP address expression "%s" failed to parse for the following reason: "%s"The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid valueThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid formatThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix part of the expression "%s" has an invalid formatThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix value of the expression "%s" was an invalid value. All values must greater than or equal to 0 and either less than or equal 32 for IPV4 addresses or less than or equal to 128 for IPV6 addressesThe provided Access Control Instruction (ACI) rights keyword values "%s" are invalid. The valid rights keyword values are one or more of the following: read, write, add, delete, search, compare or the single value allThe provided Access Control Instruction (ACI) rights values "%s" are invalid. The rights must be a list of 1 to 6 comma-separated keywords enclosed in parenthesesThe provided Access Control Instruction (ACI) bind rule SSF expression "%s" failed to parse for the following reason: "%s"The provided Access Control Instruction (ACI) bind rule ssf expression value "%s" is not in the valid range. A valid ssf value is in the range of 1 to 1024The provided Access Control Instruction (ACI) targattrfilter expression value %s is invalid because it is not in the correct format. A valid targattrsfilters expression value must be in the following format: "add=attr1: F1 && attr2: F2 ... && attrN: FN,del= attr1: F1 && attr2: F2 ... && attrN: FN"The provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because the provided filter list string is in the wrong format. A valid targattrfilters filter list must be in the following format: add=attr1: F1 && attr2: F2 ... && attrN: FNThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because one or more of the specified filters are invalid because of non-matching attribute type names in the filterThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because one or more of the specified filters are invalid for the following reason: %sThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because there are more than two filter list statementsThe provided Access Control Instruction (ACI) targattrfilter expression value %s is invalid because the both operation tokens match in the two filter listsThe provided Access Control Instruction (ACI) target keyword value "%s" was seen multiple times in the ACI "%s"The provided Access Control Instruction (ACI) target keyword value "%s" is invalid. A valid target keyword value is one of the following: target, targetscope, targetfilter, targetattr or targattrfiltersThe provided Access Control Instruction (ACI) target operator value "%s" is invalid. The only valid target operator value for the "%s" keyword is '='The provided Access Control Instruction (ACI) target rule value "%s" is invalid. A valid target rule value must be in the following form: keyword operator "expression"The provided Access Control Instruction (ACI) targetattr expression value "%s" is invalid. A valid targetattr keyword expression value requires one or more valid attribute type names in the following format: attribute1 [|| attribute2] ... [|| attributeN]. Attribute options are not supportedThe provided Access Control Instruction (ACI) targetcontrol expression value "%s" is invalid. A valid targetcontrol keyword expression value requires one or more valid control OID strings in the following format: oid [|| oid1] ... [|| oidN]The provided Access Control Instruction (ACI) targetfilter expression value "%s" is invalid because it is not a valid LDAP filterThe provided Access Control Instruction (ACI) target expression value "%s" is invalid. A valid target keyword expression value requires a LDAP URL in the following format: ldap:///distinguished_name_patternThe provided Access Control Instruction (ACI) target keyword operator value "%s" is invalid. A valid target keyword operator value is either '=' or "!="The provided Access Control Instruction (ACI) targetscope expression operator value "%s" is invalid. A valid targetscope expression value is one of the following: one, onelevel, subtree or subordinateThe provided Access Control Instruction (ACI) extop expression value "%s" is invalid. A valid extop keyword expression value requires one or more valid extended operation request OID strings in the following format: oid [|| oid1] ... [|| oidN]The provided Access Control Instruction (ACI) bind rule timeofday expression value "%s" is invalid. A valid timeofday value is expressed as four digits representing hours and minutes in the 24-hour clock (0 to 2359)The provided Access Control Instruction (ACI) bind rule timeofday expression "%s" failed to parse for the following reason: "%s"The provided Access Control Instruction (ACI) bind rule timeofday expression value "%s" is not in the valid range. A valid timeofday value is expressed as four digits representing hours and minutes in the 24-hour clock (0 to 2359)The provided Access Control Instruction (ACI) bind rule userattr expression value failed to parse because the attribute field of the ldap URL "%s" either contains more than one description or the field is emptyThe provided Access Control Instruction (ACI) bind rule userattr expression value failed to parse because the ldap URL "%s" contains an empty base DNThe provided Access Control Instruction (ACI) bind rule userattr expression value "%s" is invalidThe provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid. A valid inheritance pattern value must have the following format: parent[inheritance_level].attribute#bindTypeThe provided Access Control Instruction (ACI) bind rule userattr expression value failed to URL decode for the following reason: %sThe provided Access Control Instruction (ACI) bind rule userdn expression failed to URL decode for the following reason: %sThe provided Access Control Instruction (ACI) version value "%s" is invalid, only the version 3.0 is supportedThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" contains a non-numeric valueThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv6 address expression "%s" contains an illegal wildcard character. Wildcards are not supported when using IPv6 addresses in a IP bind rule expressionThe provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid. The inheritance level value cannot exceed the max level limit of %sThe provided Access Control Instruction (ACI) bind rule expression value corresponding to the keyword value "%s" is missing an expression. A valid bind rule value must be in the following form: keyword operator "expression"The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix part of the expression "%s" has an non-numeric valueThe provided Access Control Instruction (ACI) expression value "%s" is invalid because it contains the roledn keyword, which is not supported, replace it with the groupdn keywordThe provided Access Control Instruction (ACI) target expression DN value "%s" is invalid. The target expression DN value must be a descendant of the ACI entry DN "%s", if no wild-card is specified in the target expression DNThe provided Access Control Instruction (ACI) targetattr expression value "%s" is invalid because the expression contains invalid or duplicate tokensEntry "%s" cannot be added because it contains attribute type %s which is declared OBSOLETE in the server schemaEntry "%s" cannot be added because it contains objectclass %s which is declared OBSOLETE in the server schemaEntry "%s" contains a value "%s" for attribute %s that is invalid according to the syntax for that attribute: %sEntry "%s" contains a value for attribute %s that is invalid according to the syntax for that attribute: %sAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the process exits, so no further action should be requiredThe file system used by '%s' backend does not support last file modification time. Backups will still work but will take longer and consume more space in the backup storageDirectory server DS(%s) at %s presented generation ID %s for domain "%s", but the generation ID of this replication server RS(%s) is %s. This usually indicates that one or more directory servers in the replication topology have not been initialized with the same data, and re-initialization is requiredReplication server RS(%s) at %s presented generation ID %s for domain "%s", but the generation ID of this replication server RS(%s) is %s. This usually indicates that one or more directory servers in the replication topology have not been initialized with the same data, and re-initialization is requiredThe user-specific cursor entry limit value '%s' contained in user entry '%s' could not be parsed as an integer. The default server cursor entry limit will be usedThe user-specific idle time limit value %s contained in user entry %s could not be parsed as an integer. The default server idle time limit will be usedThe user-specific size limit value %s contained in user entry %s could not be parsed as an integer. The default server size limit will be usedThe user-specific time limit value %s contained in user entry %s could not be parsed as an integer. The default server time limit will be usedThere are multiple user-specific cursor entry limit values contained in user entry '%s'. The default server cursor entry limit will be usedThere are multiple user-specific idle time limit values contained in user entry %s. The default server idle time limit will be usedThere are multiple user-specific size limit values contained in user entry %s. The default server size limit will be usedThere are multiple user-specific time limit values contained in user entry %s. The default server time limit will be usedThe user password is about to expire (time to expiration: %s)Cannot open database %s because shutdown was requested from replication server RS(%s)Property '%s' contains value '%s' which cannot be parsed as a long. Defaulting to '%s' bytes for small DB size'%s' cannot read the secret file '%s': %sError while setting replication listener socket timeout to 1 second for domain '%s', server state may be reported as being a bit late with respect to other servers. Cause was: %sThe changelog '%s' has been opened in read-only mode, it is not enabled for writeDirectory server DS(%s) was unable to connect to replication server at %s for domain '%s': unknown hostThe Directory Server is currently in the process of closing this client connectionTerminating the client connection because its associated authentication or authorization entry %s has been deletedChange number indexing cannot advance because replica '%s' has not sent any messages since '%s'. The changelog is temporarily unable to purge old files. Verify whether the replica is still running or is connected to a replication serverChange number indexing cannot advance because some replicas do not seem to be part of the topology anymore. The changelog will not be able to purge old files until replicas reconnect or their reference is deleted from user data. The following replicas are referenced by replication, but they are not connected to the topology or they have not been properly stopped: %sEntry "%s" does not contain any values for attribute "%s"Entry "%s" does not contain any values for attribute "%s" with the specified set of optionsThe latest archived configuration file %s appears to be invalid. Forcing creation of a new oneAccess control has been disabledAn error occurred while attempting to register backend %s with the Directory Server: %sAn error occurred while attempting to release a shared lock for backend %s: %s. This may interfere with operations that require exclusive access, including LDIF import and restoring a backupThe backend defined in configuration entry %s has a backend ID of %s that conflicts with the backend ID for another backend in the server. The backend will be disabled%s.%s indicated that administrative action is required for entry %s: messages="%s"The entry cache configuration entry "cn=Entry Caches,cn=config" does not exist in the Directory Server configuration. No entry cache will be available until this entry is created with a valid entry cache configurationNo last known good configuration file %s exists. The server will attempt to start using the active configuration file %sThere are no active access loggers defined in the Directory Server configuration. No access logging will be performedThere are no active error loggers defined in the Directory Server configuration. No error logging will be performedThere are no active HTTP access loggers defined in the Directory Server configuration. No HTTP access logging will be performedThe log format for %s contains the following unsupported fields: %s. Their output will be replaced with a dash ("-") characterThe Directory Server has detected that one or more external changes have been made to the configuration file %s while the server was online, but another change has caused the server configuration to be overwritten. The manual changes have not been applied, but they have been preserved in file %sThe plugin order definition for plugins of type %s contains an empty element. This may cause the plugin order to be evaluated incorrectlyThe plugin order definition for plugins of type %s includes multiple references to the '%s' plugin. This may cause the plugin order to be evaluated incorrectlyThe plugin order definition for plugins of type %s contains multiple wildcard characters. All plugin definitions should contain exactly one wildcard element to indicate where unmatched plugins should be included in the order, and including multiple wildcards may cause the plugin order to be evaluated incorrectlyThe plugin order definition for plugins of type %s does not include a wildcard element to indicate where unmatched plugins should be included in the order. The server will default to invoking all unnamed plugins after set of named pluginsThe specified entry %s is currently defined as the configuration entry for the default password policy. The default password policy configuration entry may not be removedSchema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to open the file for reading: %sSchema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to read its contents as an LDIF entry: %sThe config schema file '%s' generated warning when trying to update schema with its content: %sThe config schema file '%s' generated warning when trying to update schema with its content, despite allowing to overwrite definitions: %sSchema configuration file %s in directory %s contains more than one entry. Only the first entry will be examined, and the additional entries will be ignoredConnected to a replication server with wrong group id. We have group id %s and replication server id %s %s has group id %s. This is for domain %s in directory server %sReplica '%s' for domain '%s' tried to connect but the replication server is still processing messages from the previous replication session and considers the replica already connected. The connection will be closed, the replica will connect againDirectory server DS(%s) was unable to connect to any of the following replication servers for domain "%s": %sUnable to look up server key id '%s' in the admin backendUnable to retrieve the hostname from the admin backend using the truststore as source of keys; 'advertised-listen-address' attribute in global configuration will use the local hostname as value. Cause: %sUnable to retrieve the keys from the truststoreUnable to find configuration for crypto manager "%s", replication SSL configuration will use default valuesChangeTime Heartbeat publisher '%s' for domain '%s' will be forcibly stopped because the peer server is unresponsiveAn error occurred while decoding a internal modification control: %sAn error occurred while decoding a replicated request control: %s'%s' is DEPRECATED for removal since %s. Its usage is highly discouragedProperty '%s' in %s '%s' is DEPRECATED for removal since %s. Its usage is highly discouragedBase DN %s has been deregistered from the Directory Server for backend %s. This base DN had both superior and subordinate entries in other backends, and there might be inconsistent or unexpected behavior when accessing entries in this portion of the hierarchy because of the missing entries that had been held in the de-registered backendThe Directory Server is entering lockdown mode, in which clients will only be allowed to connect via a loopback address, and only root users will be allowed to process operationsDisk space for the replication changelog is getting low. The replication server will continue to operate, but will stop in the event of a full diskThe replication server has detected that the file system containing the changelog has sufficient disk space to resume operationDisk free space of %d bytes for directory %s is now below disk low threshold of %d bytes. Backend %s is now offline and will no longer accept any operations until sufficient disk space is restoredDisk free space of %d bytes for directory %s is now below low threshold of %d bytes. Backend %s is now locked down and will no longer accept any operations from clients until sufficient disk space is restoredA transient problem occurred while Directory Server %s was connecting to this Replication Server %s. The peer server may try to establish a connection again. The problem was: %sDirectory server %s stopped the handshake process with replication server %s because it received the unexpected message '%s'Some reversible password storage schemes are enabled in the configuration, note that it won't be possible to use them in password policies since the admin data backend has been disabledThe local replication server never received changes for base DN '%s'. Make sure you are running the disaster recovery on the right serverBase DN %s specified in dynamic group %s does not exist in the serverEmbedded Directory Servers are NOT SUPPORTED in productionInvalid error log category "%s"Invalid override of severity level "%s"Invalid error log severity "%s"Invalid error log severity "%s", only one severity must be provided, the highest one at which logging should occurThe exact match identity mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %sDirectory server DS(%s) encountered a transient problem while connecting to replication server %s for domain "%s". Directory server will try to connect to a replication server again. The problem was: %sAn error occurred while attempting to update the password policy state information for user %s as part of a password modify extended operation (result code='%s', error message='%s')The password modify operation was not actually performed in the Directory Server because the LDAP no-op control was present in the requestThe replication domain connection for '%s' will be forcibly closed because the peer replication server '%s' is unresponsiveThe replication server domain connection for '%s' will be forcibly closed because the peer replication server '%s' is unresponsiveThe requested operation is not supported by this backendUnable to determine the total number of entries in the container: %sThe search filter "%s" used by group implementation %s is not indexed in backend %s. Backend initialization for this group implementation might take a very long time to completeDirectory server DS(%s) is closing its connection to replication server RS(%s) at %s for domain "%s" because it could not detect a heart beatReplication server RS(%s) ignoring update %s for domain "%s" from directory server DS(%s) at %s because its generation ID %s is different to the local generation ID %sReplication server RS(%s) ignoring update %s for domain "%s" from directory server DS(%s) at %s because the peer DS reported to be in BAD_DATA status. The generation ID matches, (DS is %s, RS is %s), there may be a problem with fractional replication configuration. Check the DS error logs for more detailsReplication server RS(%s) ignoring update %s for domain "%s" from directory server DS(%s) at %s because it is currently performing a full updateReplication server RS(%s) is ignoring update %s for domain "%s" from directory server DS(%s) at %s because the replica is too late and must be re-initializedReplication server RS(%s) not sending update %s for domain "%s" to directory server DS(%s) at %s because its generation ID %s is different to the local generation ID %sReplication server RS(%s) not sending update %s for domain "%s" to directory server DS(%s) at %s because the peer DS reported to be in BAD_DATA status. The generation ID matches, (DS is %s, RS is %s), there may be a problem with fractional replication configuration. Check the DS error logs for more detailsReplication server RS(%s) not sending update %s for domain "%s" to directory server DS(%s) at %s because it is currently performing a full updateReplication server RS(%s) not sending update %s for domain "%s" to replication server RS(%s) at %s because its generation ID %s is different to the local generation ID %sReplication server RS(%s) is not sending update %s for domain '%s' to directory server DS(%s) at %s because the replica is too late and must be re-initializedThe attribute value '%s' is not a valid synchronization history valueThe Directory Server is already processing another request on the same client connection with the same message ID of %dThe directory %s referenced by the LDIF connection handler defined in configuration entry %s does not exist. The LDIF connection handler will start, but will not be able to process any changes until this directory is createdThe value %s specified as the LDIF directory path for the LDIF connection handler defined in configuration entry %s exists but is not a directory. The specified path must be a directory. The LDIF connection handler will start, but will not be able to proces any changes until this path is changed to a directoryEntry %s read from LDIF starting at line %d includes a duplicate attribute %s with value %s. The second occurrence of that attribute value has been skippedEntry %s read from LDIF starting at line %d includes value "%s" for attribute %s that is invalid according to the associated syntax: %sAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the export process exits, so no further action should be requiredAn error occurred while attempting to release the exclusive lock for backend %s: %s. This lock should automatically be cleared when the import process exits, so no further action should be required'%s' is LEGACY since %s. Its usage is highly discouragedProperty '%s' in %s '%s' is LEGACY since %s. Its usage is highly discouragedError occurred while setting file permissions for the log file %s: %sThis platform does not support setting file permissions %s to the log file %sFile based key manager provider '%s' has loaded multiple key manager from keystore file '%s'. Only one will be used for securing TLS connections which rely on this key manager provider. 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'Found %d conflicting password policy subentries for user %s, used %sFile based trust manager provider '%s' has loaded multiple trust manager from truststore file '%s'. Only one will be used for securing TLS connections which rely on this trust manager provider. 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'Directory server DS(%s) was unable to connect to any replication servers for domain "%s"Directory server DS(%s) was unable to connect to replication server %s for domain "%s". Please check that there is a replication server listening at this addressThe subtree delete against '%s' is being performed non-atomically because it is deleting more than %s subordinate entries. To prevent inconsistency across replicas, the client must retry this same delete operation until it succeedsDirectory server DS(%s) has connected to replication server RS(%s) for domain "%s" at %s, but the generation IDs do not match, indicating that a full re-initialization is required. The local (DS) generation ID is %s and the remote (RS) generation ID is %sThe request to process this operation has been rejected because the Directory Server has already started its shutdown processThe pattern DN %s is not valid because it contains two consecutive wildcards in an attribute valueThe pattern DN %s is not valid because it uses wildcards for substring matching on an attribute type. A single wildcard is allowed in place of an attribute typeThe pattern DN %s is not valid because it contains a wildcard in an attribute type in a multi-valued RDNPeer replica '%s' is too late compared to changelog '%s' for domain '%s'. It asked for changes that are not present in the changelog or have been purged. The peer replica will no longer receive replicated changes and must be re-initialized. Diagnostic information follows: %sAn error occurred while attempting to decode the value of the custom password policy attribute in entry '%s': %s. Any passwords contained in the entry will be encoded using the default storage schemes, but authentication as this user might not be possibleEntry '%s' indicates that it uses custom password policy '%s', but no such policy is defined in the server. Any passwords contained in the entry will be encoded using the default storage schemes, but authentication as this user might not be possibleVersion %s not found, best match is %sProxy backend '%s' cannot failover: only primary servers have been discovered via the service discovery mechanism '%s'. Primary servers are %sProxy backend '%s' cannot failover: only secondary servers have been discovered via the service discovery mechanism '%s'. Secondary servers are %sThe primary servers for proxy backend '%s' are unavailable. The secondary servers, if available, will be used for processing requests until the primary servers become available again. The last failure that prevented the primary servers from being used was: %sThe secondary servers for proxy backend '%s' are unavailable. If the primary servers are unavailable, or become unavailable, then it will no longer be possible to proxy requests. The last failure that prevented the secondary servers from being used was: %sThe server '%s' for proxy backend '%s' is unavailable. The last failure that prevented the server from being used was: %sThe proxy backend '%s' will ignore the discovered servers '%s' from shard '%s' because they do not expose the required base DNs '%s'The work queue caught an exception while trying to cancel pending operation %s when the Directory Server was shutting down: %sAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the rebuild process exits, so no further action should be requiredThe regular expression identity mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %sBackend %s already contains entry %s which has just been registered as the base DN for backend %s. These conflicting entries can cause unexpected or errant search results, and both backends should be reinitialized to ensure that each has the correct contentPeer replica asked for changes from replica '%1$s' starting from %2$s (CSN '%3$s'), but changelog DB only contains changes starting from %4$s (CSN '%5$s'). The last recorded purge information in 'domains.state' is: last update CSN: %6$s, last message CSN: %7$s. The replica DB description is: number of files: %8$d, replica offline: %9$b. The replica DB newest file content is: oldest CSN: %10$s, newest CSN: %11$s, number of updates: %12$d, number of ReplicaOfflineMsg: %13$dPeer replica asked for changes from replica '%1$s' starting from %2$s (CSN '%3$s'), but changelog DB only contains changes starting from %4$s (CSN '%5$s'). The administrator explicitly decided to ignore the recorded purge information in 'domains.state' by setting the 'org.forgerock.opendj.allowReplicaPastPurgeDelay' system property to 'true'. The replica DB description is: number of files: %6$d, replica offline: %7$b. The replica DB newest file content is: oldest CSN: %8$s, newest CSN: %9$s, number of updates: %10$d, number of ReplicaOfflineMsg: %11$dPeer replica asked for changes from replica '%s' starting from %s (CSN '%s'), but the changelog DB has purged this change, and the last known generated change timestamp is %s (CSN '%s'). The last recorded purge information in 'domains.state' is: last update CSN: %s, last message CSN: %sReplication delay for '%s' is above %dms, current delay: %dmsReplication domain '%s' status '%s' is not healthyDirectory server DS(%s) encountered an error while receiving changes for domain "%s" from replication server RS(%s) at %s. The connection will be closed, and this directory server will now try to connect to another replication server. The error was: %sReplication server RS(%s) at %s has closed the connection to this directory server DS(%s). This directory server will now try to connect to another replication server in order to receive changes for the domain "%s"The replication server has detected that the file system containing the changelog has sufficient disk space to resume operation. It is now reconnecting to the rest of the replication topologyBase DN "%s" is configured as one of the subordinate base DNs to use for searches below the root DSE. However, this base DN is not handled by any suffix registered with the Directory Server and will therefore not be usedA transient problem occurred while Replication Server %s was connecting to this Replication Server %s. The Replication Server should try to reconnect later. The problem was: %sReplication server RS(%s) is closing its connection to %s at %s for domain '%s' because it could not detect a heartbeat: time since last message (%s) is greater than the timeout interval %s ms (heartbeat interval is %s ms)The subject attribute to user attribute certificate mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %s'%s' has ignored the file '%s' either because the certificate does not contain the key usage extension '%s', or because the file does not contain the appropriate key typesCannot connect to replica '%s' for replication service discovery mechanism '%s'. The replica entry is: %sSettings for Replica '%s' should provide a hostnameReplication server '%s' references server '%s' that could not be parsed correctly; the definition will be skippedScheduled discovery '%s' failed : %sCannot gather naming contexts from server %s: %sAn error occurred while setting file permissions for the backend database directory %s: %sAn error occurred while attempting to remove content of directory '%s': %sSetup has failed, see the errors in the messages below. The process also failed to automatically remove the files that it created during setup. Please manually remove the 'db' and 'config' directories from the instance directory before trying to run the setup againSetup has failed, see the errors in the messages below. The process also failed to automatically remove the files that it created during setup. Please manually remove the 'db' and 'config' directories from the instance directory and the '%s' file before trying to run the setup againAn error occurred while attempting to release a shared lock for backend %s: %s. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessaryAn error occurred when trying to send an e-mail message for administrative alert with type %s and message %s: %sThe search filter "%s" used by subentry manager is not indexed in backend %s. Backend initialization for subentry manager processing might take a very long time to completeAn error occurred while attempting to rename the current tasks backing file from %s to %s: %s. The previous task configuration (which does not reflect the latest update) may be lostUnable to add completed task %s to the task scheduler because another task already exists with the same IDDirectory server DS(%s) timed out while connecting to replication server %s for domain "%s"Timed out while trying to acquire the domain lock for domain "%s". The connection attempt from replication server RS(%s) at %s to this replication server RS(%s) will be aborted. This is probably benign and a result of a simultaneous cross connection attemptA transient problem occurred while DS(%s) was connecting to RS(%s), Directory Server will try to connect again. Problem was: %sUnable to find configuration for truststore backend "%s", using default values insteadUnable to locate all expired entries on backend '%s' because the ttl-enabled index '%s' has reached the configured index-entry-limitThis platform does not support setting file permissions %s to the database directory %s%s is unexpectedly exiting when the Directory Server is not in the process of shutting down. This likely indicates that the thread encountered an unexpected errorThe server is performing an unindexed internal search request with base DN '%s', scope '%s', and filter '%s'. Unindexed internal searches are usually unexpected and could impact performance. Please verify that this backend's indexes are configured correctly for these search parametersUnable to find the task backend file location in the configuration file %s, entry '%s' or attribute '%s' is missingEXPERIMENTAL virtual threads support has been enabled. DO NOT USE in productionAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the verification process exits, so no further action should be requiredWARNING: Unable to open log file %s for reading: %sWARNING: Unable to open output file %s for writing: %sService %s has been marked for deletionThe server has been marked for deletion as a Windows Service%s was interrupted while waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effectsAn unexpected exception was caught while %s was waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effectsConfiguration attribute %s has distinct values in replication domain configuration entries. Migration to replication synchronization provider configuration will keep only one value, '%s' and discarded '%s' -
Method Summary
Modifier and TypeMethodDescriptionstatic StringReturns the name of the resource associated with the messages contained in this class.
-
Field Details
-
WARN_ACI_SYNTAX_GENERAL_PARSE_FAILED
The provided string "%s" could not be parsed as a valid Access Control Instruction (ACI) because it failed general ACI syntax evaluation -
WARN_ACI_SYNTAX_INVALID_VERSION
The provided Access Control Instruction (ACI) version value "%s" is invalid, only the version 3.0 is supported -
WARN_ACI_SYNTAX_INVALID_ACCESS_TYPE_VERSION
The provided Access Control Instruction access type value "%s" is invalid. A valid access type value is either allow or deny -
WARN_ACI_SYNTAX_INVALID_RIGHTS_SYNTAX
The provided Access Control Instruction (ACI) rights values "%s" are invalid. The rights must be a list of 1 to 6 comma-separated keywords enclosed in parentheses -
WARN_ACI_SYNTAX_INVALID_RIGHTS_KEYWORD
The provided Access Control Instruction (ACI) rights keyword values "%s" are invalid. The valid rights keyword values are one or more of the following: read, write, add, delete, search, compare or the single value all -
WARN_ACI_SYNTAX_BIND_RULE_MISSING_CLOSE_PAREN
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_BIND_RULE_MISSING_CLOSE_PARENThe provided Access Control Instruction (ACI) bind rule value "%s" is invalid because it is missing a close parenthesis that corresponded to the initial open parenthesis -
WARN_ACI_SYNTAX_INVALID_BIND_RULE_SYNTAX
The provided Access Control Instruction (ACI) bind rule value "%s" is invalid. A valid bind rule value must be in the following form: keyword operator "expression" -
WARN_ACI_SYNTAX_INVALID_BIND_RULE_KEYWORD
The provided Access Control Instruction (ACI) bind rule keyword value "%s" is invalid. A valid keyword value is one of the following: userdn, groupdn, roledn, userattr,ip, dns, dayofweek, timeofday or authmethod -
WARN_ACI_SYNTAX_INVALID_BIND_RULE_OPERATOR
The provided Access Control Instruction (ACI) bind rule operator value "%s" is invalid. A valid bind rule operator value is either '=' or "!=" -
WARN_ACI_SYNTAX_MISSING_BIND_RULE_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_MISSING_BIND_RULE_EXPRESSIONThe provided Access Control Instruction (ACI) bind rule expression value corresponding to the keyword value "%s" is missing an expression. A valid bind rule value must be in the following form: keyword operator "expression" -
WARN_ACI_SYNTAX_INVALID_BIND_RULE_BOOLEAN_OPERATOR
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_BIND_RULE_BOOLEAN_OPERATORThe provided Access Control Instruction (ACI) bind rule boolean operator value "%s" is invalid. A valid bind rule boolean operator value is either "OR" or "AND" -
WARN_ACI_SYNTAX_INVALID_BIND_RULE_KEYWORD_OPERATOR_COMBO
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_ACI_SYNTAX_INVALID_BIND_RULE_KEYWORD_OPERATOR_COMBOThe provided Access Control Instruction (ACI) bind rule keyword string "%s" is invalid for the bind rule operator string "%s" -
WARN_ACI_SYNTAX_INVALID_USERDN_URL
The provided Access Control Instruction (ACI) bind rule userdn expression failed to URL decode for the following reason: %s -
WARN_ACI_SYNTAX_INVALID_GROUPDN_EXPRESSION
The provided Access Control Instruction (ACI) bind rule groupdn expression value "%s" is invalid. A valid groupdn keyword expression value requires one or more LDAP URLs in the following format: ldap:///groupdn [|| ldap:///groupdn] ... [|| ldap:///groupdn] -
WARN_ACI_SYNTAX_INVALID_GROUPDN_URL
The provided Access Control Instruction (ACI) bind rule groupdn expression value failed to URL decode for the following reason: %s -
WARN_ACI_SYNTAX_INVALID_IP_EXPRESSION
The provided Access Control Instruction (ACI) bind rule ip expression value "%s" is invalid. A valid ip keyword expression requires one or more comma-separated elements of a valid IP address list expression -
WARN_ACI_SYNTAX_INVALID_DNS_EXPRESSION
The provided Access Control Instruction (ACI) bind rule dns expression value "%s" is invalid. A valid dns keyword expression value requires a valid fully qualified DNS domain name -
WARN_ACI_SYNTAX_INVALID_DNS_WILDCARD
The provided Access Control Instruction (ACI) bind rule dns expression value "%s" is invalid, because a wild-card pattern was found in the wrong position. A valid dns keyword wild-card expression value requires the '*' character only be in the leftmost position of the domain name -
WARN_ACI_SYNTAX_INVALID_DAYOFWEEK
The provided Access Control Instruction (ACI) bind rule dayofweek expression value "%s" is invalid, because of an invalid day of week value. A valid dayofweek value is one of the following English three-letter abbreviations for the days of the week: sun, mon, tue, wed, thu, fri, or sat -
WARN_ACI_SYNTAX_INVALID_TIMEOFDAY
The provided Access Control Instruction (ACI) bind rule timeofday expression value "%s" is invalid. A valid timeofday value is expressed as four digits representing hours and minutes in the 24-hour clock (0 to 2359) -
WARN_ACI_SYNTAX_INVALID_TIMEOFDAY_RANGE
The provided Access Control Instruction (ACI) bind rule timeofday expression value "%s" is not in the valid range. A valid timeofday value is expressed as four digits representing hours and minutes in the 24-hour clock (0 to 2359) -
WARN_ACI_SYNTAX_INVALID_AUTHMETHOD_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_AUTHMETHOD_EXPRESSIONThe provided Access Control Instruction (ACI) bind rule authmethod expression value "%s" is invalid. A valid authmethod value is one of the following: none, simple,SSL, or "sasl mechanism", where mechanism is one of the supported SASL mechanisms including CRAM-MD5, DIGEST-MD5, and GSSAPI -
WARN_ACI_SYNTAX_INVALID_USERATTR_EXPRESSION
The provided Access Control Instruction (ACI) bind rule userattr expression value "%s" is invalid -
WARN_ACI_SYNTAX_INVALID_USERATTR_INHERITANCE_PATTERN
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_USERATTR_INHERITANCE_PATTERNThe provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid. A valid inheritance pattern value must have the following format: parent[inheritance_level].attribute#bindType -
WARN_ACI_SYNTAX_MAX_USERATTR_INHERITANCE_LEVEL_EXCEEDED
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_ACI_SYNTAX_MAX_USERATTR_INHERITANCE_LEVEL_EXCEEDEDThe provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid. The inheritance level value cannot exceed the max level limit of %s -
WARN_ACI_SYNTAX_INVALID_INHERITANCE_VALUE
The provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid because it is non-numeric -
WARN_ACI_SYNTAX_INVALID_TARGET_SYNTAX
The provided Access Control Instruction (ACI) target rule value "%s" is invalid. A valid target rule value must be in the following form: keyword operator "expression" -
WARN_ACI_SYNTAX_INVALID_TARGET_KEYWORD
The provided Access Control Instruction (ACI) target keyword value "%s" is invalid. A valid target keyword value is one of the following: target, targetscope, targetfilter, targetattr or targattrfilters -
WARN_ACI_SYNTAX_INVALID_TARGET_NOT_OPERATOR
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_ACI_SYNTAX_INVALID_TARGET_NOT_OPERATORThe provided Access Control Instruction (ACI) target operator value "%s" is invalid. The only valid target operator value for the "%s" keyword is '=' -
WARN_ACI_SYNTAX_INVALID_TARGET_DUPLICATE_KEYWORDS
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_ACI_SYNTAX_INVALID_TARGET_DUPLICATE_KEYWORDSThe provided Access Control Instruction (ACI) target keyword value "%s" was seen multiple times in the ACI "%s" -
WARN_ACI_SYNTAX_INVALID_TARGETS_OPERATOR
The provided Access Control Instruction (ACI) target keyword operator value "%s" is invalid. A valid target keyword operator value is either '=' or "!=" -
WARN_ACI_SYNTAX_INVALID_TARGETSCOPE_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGETSCOPE_EXPRESSIONThe provided Access Control Instruction (ACI) targetscope expression operator value "%s" is invalid. A valid targetscope expression value is one of the following: one, onelevel, subtree or subordinate -
WARN_ACI_SYNTAX_INVALID_TARGETKEYWORD_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGETKEYWORD_EXPRESSIONThe provided Access Control Instruction (ACI) target expression value "%s" is invalid. A valid target keyword expression value requires a LDAP URL in the following format: ldap:///distinguished_name_pattern -
WARN_ACI_SYNTAX_TARGET_DN_NOT_DESCENDENTOF
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_ACI_SYNTAX_TARGET_DN_NOT_DESCENDENTOFThe provided Access Control Instruction (ACI) target expression DN value "%s" is invalid. The target expression DN value must be a descendant of the ACI entry DN "%s", if no wild-card is specified in the target expression DN -
WARN_ACI_SYNTAX_INVALID_TARGETATTRKEYWORD_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGETATTRKEYWORD_EXPRESSIONThe provided Access Control Instruction (ACI) targetattr expression value "%s" is invalid. A valid targetattr keyword expression value requires one or more valid attribute type names in the following format: attribute1 [|| attribute2] ... [|| attributeN]. Attribute options are not supported -
WARN_ACI_SYNTAX_INVALID_TARGETFILTERKEYWORD_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGETFILTERKEYWORD_EXPRESSIONThe provided Access Control Instruction (ACI) targetfilter expression value "%s" is invalid because it is not a valid LDAP filter -
INFO_ACI_ADD_FAILED_PRIVILEGE
An attempt to add the entry "%s" containing an aci attribute type failed, because the authorization DN "%s" lacked modify-acl privileges -
INFO_ACI_MODIFY_FAILED_PRIVILEGE
An attempt to modify an aci attribute type in the entry "%s" failed, because the authorization DN "%s" lacked modify-acl privileges -
WARN_ACI_ADD_FAILED_DECODE
An attempt to add the entry "%s" containing an aci attribute type failed because of the following reason: %s -
WARN_ACI_MODIFY_FAILED_DECODE
An attempt to modify an aci attribute type in the entry "%s" failed because of the following reason: %s -
WARN_ACI_ADD_LIST_FAILED_DECODE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_ACI_ADD_LIST_FAILED_DECODEObject> "%s", located in the entry "%s", because of the following reason: %s -
INFO_ACI_ADD_LIST_ACIS
Added %s Access Control Instruction (ACI) attribute types found in context "%s" to the access control evaluation engine -
WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_EXPRESSIONThe provided Access Control Instruction (ACI) targattrfilter expression value %s is invalid because it is not in the correct format. A valid targattrsfilters expression value must be in the following format: "add=attr1: F1 && attr2: F2 ... && attrN: FN,del= attr1: F1 && attr2: F2 ... && attrN: FN" -
WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_OPS_MATCH
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_OPS_MATCHThe provided Access Control Instruction (ACI) targattrfilter expression value %s is invalid because the both operation tokens match in the two filter lists -
WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_MAX_FILTER_LISTS
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_MAX_FILTER_LISTSThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because there are more than two filter list statements -
WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_FILTER_LIST_FORMAT
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_FILTER_LIST_FORMATThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because the provided filter list string is in the wrong format. A valid targattrfilters filter list must be in the following format: add=attr1: F1 && attr2: F2 ... && attrN: FN -
WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_FILTER_LISTS_FILTER
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_FILTER_LISTS_FILTERThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because one or more of the specified filters are invalid for the following reason: %s -
WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_FILTER_LISTS_ATTR_FILTER
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_FILTER_LISTS_ATTR_FILTERThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because one or more of the specified filters are invalid because of non-matching attribute type names in the filter -
WARN_ACI_SYNTAX_INVALID_ATTRIBUTE_TYPE_NAME
The provided Access Control Instruction (ACI) attribute name value %s is invalid. A valid attribute type name must begin with an ASCII letter and must contain only ASCII letters,digits or the "-" character -
NOTE_ACI_SYNTAX_DUBIOUS_AUTHMETHOD_SASL_MECHANISM
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_ACI_SYNTAX_DUBIOUS_AUTHMETHOD_SASL_MECHANISMThe SASL mechanism "%s" provided in the Access Control Instruction (ACI) bind rule authmethod expression is not one of the currently registered mechanisms in the server -
WARN_ACI_LOCALHOST_DOESNT_MATCH_CANONICAL_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_ACI_LOCALHOST_DOESNT_MATCH_CANONICAL_VALUEObject> The provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, but the canonical representation for that hostname is configured to be %s. The server will attempt to automatically interpret the correct localhost value -
WARN_ACI_HOSTNAME_DOESNT_MATCH_CANONICAL_VALUE
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_ACI_HOSTNAME_DOESNT_MATCH_CANONICAL_VALUEObject, Object> The provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, which resolves to IP address %s, but the canonical hostname for that IP address is %s. This likely means that the provided hostname will never match any clients -
WARN_ACI_ERROR_CHECKING_CANONICAL_HOSTNAME
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_ACI_ERROR_CHECKING_CANONICAL_HOSTNAMEObject> An error occurred while attempting to determine whether hostname %s referenced in dns expression bind rule "%s" used the correct canonical representation: %s. This likely means that the provided hostname will never match any clients -
INFO_ACI_ADD_LIST_GLOBAL_ACIS
Added %s Global Access Control Instruction (ACI) attribute types to the access control evaluation engine -
INFO_ACI_HANDLER_FAIL_PROCESS_GLOBAL_ACI
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_ACI_HANDLER_FAIL_PROCESS_GLOBAL_ACIAn unexpected error occurred while processing the ds-cfg-global-aci attribute in configuration entry %s: %s -
INFO_ACI_HANDLER_FAIL_PROCESS_ACI
An unexpected error occurred while processing the aci attributes in the configuration system: %s -
WARN_PATTERN_DN_CONSECUTIVE_WILDCARDS_IN_VALUE
public static LocalizableMessageDescriptor.Arg1<Object> WARN_PATTERN_DN_CONSECUTIVE_WILDCARDS_IN_VALUEThe pattern DN %s is not valid because it contains two consecutive wildcards in an attribute value -
WARN_PATTERN_DN_TYPE_CONTAINS_SUBSTRINGS
The pattern DN %s is not valid because it uses wildcards for substring matching on an attribute type. A single wildcard is allowed in place of an attribute type -
WARN_PATTERN_DN_TYPE_WILDCARD_IN_MULTIVALUED_RDN
public static LocalizableMessageDescriptor.Arg1<Object> WARN_PATTERN_DN_TYPE_WILDCARD_IN_MULTIVALUED_RDNThe pattern DN %s is not valid because it contains a wildcard in an attribute type in a multi-valued RDN -
WARN_ACI_NOT_VALID_DN
Selfwrite check skipped because an attribute "%s" with a distinguished name syntax was not a valid DN -
WARN_ACI_TARGETATTR_INVALID_ATTR_TOKEN
The provided Access Control Instruction (ACI) targetattr expression value "%s" is invalid because the expression contains invalid or duplicate tokens -
WARN_ACI_SYNTAX_ROLEDN_NOT_SUPPORTED
The provided Access Control Instruction (ACI) expression value "%s" is invalid because it contains the roledn keyword, which is not supported, replace it with the groupdn keyword -
WARN_ACI_SERVER_DECODE_FAILED
Failed to decode the Access Control Instruction (ACI)%s -
WARN_ACI_ENTER_LOCKDOWN_MODE
The server is being put into lockdown mode because invalid ACIs rules were detected either when the server was started or during a backend initialization -
WARN_ACI_SYNTAX_INVALID_USERATTR_URL
The provided Access Control Instruction (ACI) bind rule userattr expression value failed to URL decode for the following reason: %s -
WARN_ACI_SYNTAX_INVALID_USERATTR_BASEDN_URL
The provided Access Control Instruction (ACI) bind rule userattr expression value failed to parse because the ldap URL "%s" contains an empty base DN -
WARN_ACI_SYNTAX_INVALID_USERATTR_ATTR_URL
The provided Access Control Instruction (ACI) bind rule userattr expression value failed to parse because the attribute field of the ldap URL "%s" either contains more than one description or the field is empty -
WARN_ACI_SYNTAX_INVALID_PREFIX_FORMAT
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix part of the expression "%s" has an invalid format -
WARN_ACI_SYNTAX_INVALID_PREFIX_VALUE
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix value of the expression "%s" was an invalid value. All values must greater than or equal to 0 and either less than or equal 32 for IPV4 addresses or less than or equal to 128 for IPV6 addresses -
WARN_ACI_SYNTAX_PREFIX_NOT_NUMERIC
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix part of the expression "%s" has an non-numeric value -
WARN_ACI_SYNTAX_INVALID_IPV4_FORMAT
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" format was invalid -
WARN_ACI_SYNTAX_INVALID_IPV4_VALUE
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" contains an invalid value. All values of the address must be between 0 and 255 -
WARN_ACI_SYNTAX_IPV4_NOT_NUMERIC
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" contains a non-numeric value -
WARN_ACI_SYNTAX_IPV6_WILDCARD_INVALID
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv6 address expression "%s" contains an illegal wildcard character. Wildcards are not supported when using IPv6 addresses in a IP bind rule expression -
WARN_ACI_SYNTAX_INVALID_IPV6_FORMAT
The provided Access Control Instruction (ACI) bind rule IP address expression "%s" failed to parse for the following reason: "%s" -
WARN_ACI_SYNTAX_INVALID_NETMASK_FORMAT
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid format -
WARN_ACI_SYNTAX_INVALID_NETMASK
The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid value -
WARN_ACI_SYNTAX_INVALID_TARGETCONTROL_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGETCONTROL_EXPRESSIONThe provided Access Control Instruction (ACI) targetcontrol expression value "%s" is invalid. A valid targetcontrol keyword expression value requires one or more valid control OID strings in the following format: oid [|| oid1] ... [|| oidN] -
WARN_ACI_SYNTAX_ILLEGAL_CHAR_IN_NUMERIC_OID
public static LocalizableMessageDescriptor.Arg3<Object,Character, WARN_ACI_SYNTAX_ILLEGAL_CHAR_IN_NUMERIC_OIDNumber> The provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the value contained an illegal character %c at position %d -
WARN_ACI_SYNTAX_DOUBLE_PERIOD_IN_NUMERIC_OID
public static LocalizableMessageDescriptor.Arg2<Object,Number> WARN_ACI_SYNTAX_DOUBLE_PERIOD_IN_NUMERIC_OIDThe provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the numeric OID contained two consecutive periods at position %d -
WARN_ACI_SYNTAX_INVALID_TARGEXTOP_EXPRESSION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ACI_SYNTAX_INVALID_TARGEXTOP_EXPRESSIONThe provided Access Control Instruction (ACI) extop expression value "%s" is invalid. A valid extop keyword expression value requires one or more valid extended operation request OID strings in the following format: oid [|| oid1] ... [|| oidN] -
WARN_ACI_ATTRIBUTE_NOT_INDEXED
Backend %s does not have a presence index defined for attribute type %s. Access control initialization may take a very long time to complete in this backend -
WARN_ACI_SYNTAX_INVALID_SSF_FORMAT
The provided Access Control Instruction (ACI) bind rule SSF expression "%s" failed to parse for the following reason: "%s" -
WARN_ACI_SYNTAX_INVALID_SSF_RANGE
The provided Access Control Instruction (ACI) bind rule ssf expression value "%s" is not in the valid range. A valid ssf value is in the range of 1 to 1024 -
WARN_ACI_SYNTAX_INVALID_TIMEOFDAY_FORMAT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_ACI_SYNTAX_INVALID_TIMEOFDAY_FORMATThe provided Access Control Instruction (ACI) bind rule timeofday expression "%s" failed to parse for the following reason: "%s" -
NOTICE_GLOBAL_ACCESS_CONTROL_ADDED
The global access control policy '%s' has been added -
NOTICE_GLOBAL_ACCESS_CONTROL_DELETED
The global access control policy '%s' has been removed -
NOTICE_GLOBAL_ACCESS_CONTROL_CHANGED
The global access control policy '%s' has been modified -
NOTICE_GLOBAL_ACCESS_CONTROL_INITIALIZED
The global access control engine has been initialized with %d policies -
ERR_GLOBAL_ACCESS_CONTROL_INVALID_TARGET_DN_PATTERN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_GLOBAL_ACCESS_CONTROL_INVALID_TARGET_DN_PATTERNThe global access control policy defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s" -
ERR_GLOBAL_ACCESS_CONTROL_INVALID_USER_DN_PATTERN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_GLOBAL_ACCESS_CONTROL_INVALID_USER_DN_PATTERNThe global access control policy defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s" -
ERR_GLOBAL_ACCESS_CONTROL_UNRECOGNIZED_CONTROL_ALIAS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_GLOBAL_ACCESS_CONTROL_UNRECOGNIZED_CONTROL_ALIASThe global access control policy defined in "%s" could not be parsed because it contains an unrecognized control alias "%s" -
ERR_GLOBAL_ACCESS_CONTROL_UNRECOGNIZED_EXTOP_ALIAS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_GLOBAL_ACCESS_CONTROL_UNRECOGNIZED_EXTOP_ALIASThe global access control policy defined in "%s" could not be parsed because it contains an unrecognized extended operation alias "%s" -
INFO_STATUS_CLI_USAGE_DESCRIPTION
This utility can be used to display basic server information -
INFO_DESCRIPTION_SUBCMD_ADD_SERVER_TO_PRE_7_0_TOPOLOGY
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_SUBCMD_ADD_SERVER_TO_PRE_7_0_TOPOLOGYAdds the local server (with version 7.0 or more) to a topology with older server versions (prior to 7.0) -
INFO_REPLICATION_CONNECTING
Establishing connections -
INFO_REPLICATION_CONFIGURE_UPDATING_ADS_CONTENTS
Checking registration information -
INFO_INITIALIZE_PROGRESS_WITH_PERCENTAGE
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_INITIALIZE_PROGRESS_WITH_PERCENTAGE%s entries processed (%s %% complete) -
INFO_INITIALIZE_PROGRESS_WITH_PROCESSED
%s entries processed -
INFO_INITIALIZE_PROGRESS_WITH_UNPROCESSED
%s remaining to be processed -
ERR_OFFLINE_TOOL_TARGET_SERVER_MISSING
A target server must be specified either by using LDAP connection options or the --%s option -
ERR_STATUS_READ_LOCAL_SERVER_CONFIGURATION
An error occurred while reading the server configuration: %s -
ERR_STATUS_PRINT_SCRIPT_FRIENDLY_OUTPUT
An error occurred while printing server status script friendly output: %s -
INFO_STATUS_SERVER_IS_RUNNING_LABEL
Run status -
INFO_STATUS_SERVER_STARTED
Started -
INFO_STATUS_SERVER_STOPPED
Stopped -
INFO_STATUS_NB_OPEN_CONNECTIONS_LABEL
Open connections -
INFO_STATUS_GENERAL_DETAILS_TITLE
General details -
INFO_STATUS_HOSTNAME_LABEL
Host name -
INFO_STATUS_SERVER_ID_LABEL
Server ID -
INFO_STATUS_ADMIN_CONNECTOR_LABEL
Administration port (LDAPS) -
INFO_STATUS_VERSION_LABEL
Version -
INFO_STATUS_INSTALL_PATH_LABEL
Installation path -
INFO_STATUS_INSTANCE_PATH_LABEL
Instance path -
INFO_STATUS_INSTALL_AND_INSTANCE_PATH_LABEL
Installation and instance path -
INFO_STATUS_RUNNING_SERVER_JAVA_DETAILS_TITLE
Running server Java details -
INFO_STATUS_JAVA_VERSION_LABEL
Java version -
INFO_STATUS_JAVA_VENDOR_LABEL
Java vendor -
INFO_STATUS_JVM_PROCESSORS_LABEL
JVM available CPUs -
INFO_STATUS_JVM_MAX_HEAP_SIZE_LABEL
JVM max heap size -
INFO_STATUS_CONNECTION_HANDLERS_TITLE
Connection handlers -
INFO_STATUS_CH_NAME_TITLE
Name -
INFO_STATUS_CH_PORT_TITLE
Port -
INFO_STATUS_CH_TYPE_TITLE
Protocol -
INFO_STATUS_CH_M1_RATE_TITLE
Load m1 rate -
INFO_STATUS_CH_M5_RATE_TITLE
Load m5 rate -
INFO_STATUS_LOCAL_BACKENDS_TITLE
Local backends -
INFO_STATUS_PROXY_BACKENDS_TITLE
Proxy backends -
INFO_STATUS_BACKEND_NAME_TITLE
Backend -
INFO_STATUS_BACKEND_TYPE_TITLE
Type -
INFO_STATUS_BACKEND_DB_TYPE_CACHE_SIZE_TITLE
Active cache -
INFO_STATUS_DN_TITLE
Base DN -
INFO_STATUS_DN_NB_ENTRIES_TITLE
Entries -
INFO_STATUS_DN_REPLICATION_STATUS_TITLE
Replication -
INFO_STATUS_DN_REPLICATION_RECEIVE_DELAY_TITLE
Receive delay -
INFO_STATUS_DN_REPLICATION_REPLAY_DELAY_TITLE
Replay delay -
INFO_STATUS_DISK_ROOT_TITLE
Disk space -
INFO_STATUS_DISK_STATE_TITLE
State -
INFO_STATUS_DISK_REMAINING_SPACE_TITLE
Free space -
INFO_STATUS_CONNECTION_HANDLER_TABLE_EMPTY_MSG
There are no connection handlers setup in the server -
INFO_STATUS_LOCAL_BACKEND_TABLE_EMPTY_MSG
There are no local backends setup in the server -
INFO_STATUS_PROXY_BACKEND_TABLE_EMPTY_MSG
There are no proxy backends setup in the server -
INFO_STATUS_DISK_SPACE_TABLE_EMPTY_MSG
No disks are monitored by the server -
INFO_STATUS_CONNECT_TO_SERVER_FOR_JVM_INFO
Connect to the server to obtain JVM information -
INFO_STATUS_CONNECT_TO_SERVER_FOR_DISKS_INFO
Connect to the server to obtain disk space information -
ERR_STATUS_UNABLE_TO_READ_MONITOR_BACKEND_MSG
Unable to perform the search on the monitor backend. To display information, the status tool requires the remote server monitor backend to be enabled -
INFO_EXTRACT_OUTPUT_DIRECTORY
The folder into which the files will be placed into -
INFO_EXTRACT_OUTPUT_DIRECTORY_PLACEHOLDER
{directory} -
INFO_INSTANCE_RUNNING
The instance is running -
INFO_INSTANCE_NOT_RUNNING
The instance is not running -
INFO_EXTRACT_BINDPASSWORD
Password to use to bind to the server -
INFO_EXTRACT_BINDPASSWORD_PLACEHOLDER
{password} -
INFO_EXTRACT_TOOLSDIR
Path to the JDK utility binaries directory such as jstack -
INFO_EXTRACT_TOOLSDIR_PLACEHOLDER
{directory} -
INFO_EXTRACT_NOAUDIT
Specifies whether audit files are excluded -
INFO_EXTRACT_NOKEYSTORE
Specifies whether keystore files are excluded -
INFO_EXTRACT_NOSERVERINTERACTION
Specifies that the tool should not interact with the server, that is no LDAP operation, and no jstack sampling -
INFO_EXTRACT_NEEDJAVAHEAPDUMP
Specifies whether a Java Heap Dump (using jmap) should be produced. The binary file is generated at the same location as the ZIP archive before being added to it; please make sure that the target directory's volume has sufficient capacity -
INFO_EXTRACT_MAX_LOG_FILES
Maximum number of log files to collect. Ignored if --logsAfterDate is provided -
INFO_EXTRACT_MAX_LOG_FILES_PLACEHOLDER
{number} -
INFO_EXTRACT_LOGS_AFTER_DATE
Collect log files after this date. Format "YYYYMMDDhhmmss" like "20161123143612" = 23 November 2016, 14:36 12s. Overrides --maxLogFiles -
INFO_EXTRACT_LOGS_AFTER_DATE_PLACEHOLDER
{date} -
INFO_EXTRACT_SERVERPID
When the server is embedded in OpenAM, there is no PID file. Therefore this option indicates the server PID of the OpenAM application server -
INFO_EXTRACT_SERVERPID_PLACEHOLDER
{pid} -
INFO_EXTRACT_TOOL_DESCRIPTION
This tool collects support data from the OpenDJ instance it is bound to -
SUPPLEMENT_EXTRACT_TOOL_DESCRIPTION
<xinclude:include href="description-supportextract.xml" /> -
REF_SHORT_DESC_EXTRACT_TOOL
extract support data -
ERR_INTERNAL_PACKAGING_ERROR
Error: %s -
ERR_OUTPUT_DIRECTORY_NOT_FOUND
The output directory "%s" could not be found -
ERR_INVALID_MAX_LOG_FILES
The number argument for "maxLogFiles" is invalid -
ERR_INVALID_LOG_AFTER_DATE
The date argument for "logsAfterDate" is invalid -
ERR_INVALID_SERVER_PID
The serverPID argument is not a valid number -
ERR_MISSING_CREDENTIAL_ARGS
The --bindDN and/or --bindPassword arguments are missing -
ERR_MONITORING_DATA
Could not collect monitoring data from the directory server: %s -
ERR_FILE_COLLECTOR
Could not collect all the files -
ERR_MISSING_OUTPUTDIR_ARG
An error occurred while parsing the command-line arguments: The argument --outputDirectory is required to have a value but none was provided in the argument list and no default value is available -
INFO_CONTINUING_PROCESSING
Continuing data gathering though there was an error: %s -
INFO_ARCHIVE_HAS_BEEN_WRITTEN
The following archive has been created : %s -
ERROR_NO_JAVA_PROPERTIES
Could not find "java.properties" -
ERROR_LOADING_JAVA_PROPERTIES
Error while loading "java.properties": %s -
INFO_NO_MONITORING_DATA
No monitoring data can be collected when the server is not running or no server interaction is allowed -
INFO_NO_JVM_STACK_DUMP
No JVM stack dump can be produced when the server is not running or no server interaction is allowed -
ERR_CANT_LOCATE_JAVA_CMD
Could not find the "%s" command in "%s" -
ERR_SKIPPING_LOG_FILE
Skipping log "%s" (unsupported config) -
INFO_COLLECTING_THE_CONFIGURATION_FILES
Collecting the configuration files -
INFO_COLLECTING_PROCESS_STATISTICS
Collecting process statistics -
INFO_COPYING_SERVEROUT_FILE
Making copy of the %s file before collecting process statistics -
INFO_DELETING_SERVEROUTCOPY_FILE
Removing file copy %s -
INFO_SERVEROUT_NOT_FOUND_ERR
Skipping backup of %s log (file not found) -
INFO_COLLECTING_JVM_HEAPDUMP
Collecting JVM heap dump : using %s -
INFO_COLLECTING_LOG_FILES
Collecting the log files -
INFO_COLLECTING_BACKEND_INFO
Collecting backend statistics -
INFO_COLLECTING_GC_LOG_FILES
Collecting the GC log files -
INFO_NO_GC_LOGGING
Skipping GC logs collection because GC logging is not enabled -
INFO_COLLECTING_CHANGELOG_INFO
Collecting ChangelogDb information -
INFO_COLLECTING_CHANGELOG_INFO_FAILURE
No changelogDb data found (is a DS or is not replicated) -
INFO_COLLECTING_MONITORING_INFO
Collecting the monitoring info from cn=monitor -
INFO_COLLECTING_PROCESS_THREAD_INFO
Collecting process thread information, sample number : %d -
INFO_GENERATING_STACK_DUMP
Generating stack dump, sample number : %d using %s for pid %d -
INFO_COLLECTING_PROCESSOR_INFO
Processor information -
INFO_COLLECTING_OS_INFO
OS information -
INFO_COLLECTING_ENV_VARS
Extract environment variables -
INFO_COLLECTING_PROC_ENVIRON_FILE
DS /proc files -
INFO_COLLECTING_VM_ENVIRON_FILES
VM environment information -
INFO_COLLECTING_DISK_INFO
Disk information -
INFO_COLLECTING_NETWORK_INFO
Network information -
INFO_COLLECTING_OS_RELEASE
Linux release -
INFO_COLLECTING_OS_PROC_INFO
Linux /proc info files -
INFO_COLLECTING_NODE_INFO
Collecting system node information -
INFO_LISTING_KEYSTORE_CONTENT
Listing the security stores -
INFO_ADDING_FILE
Adding %s -
INFO_SKIPPING_FILE
Skipping %s -
INFO_SKIPPING_KEYSTORES
Skipping java security stores -
INFO_SKIPPING_AUDIT
Skipping audit files -
ERR_SUPPORT_EXTRACT_TASK_ERRORS
There was at least one error during the tasks execution: %s -
INFO_JDKTOOLS_DIRECTORY_DEFAULT_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_JDKTOOLS_DIRECTORY_DEFAULT_VALUENo value was provided for %s, JDK tool directory is set to %s -
INFO_TOP_NOT_SUPPORTED_ON_OS
Cannot extract process statistics (by running "top" command) on OS '%s'. Only %s dump samples will be collected -
INFO_DESCRIPTION_DS_REPL_TOOL
This tool manages data synchronization between servers. For replication to work you must initialize the contents of one of the servers with the contents of the others using the '%s' subcommand -
REF_SHORT_DESC_DS_REPL_TOOL
Manages data synchronization between servers -
ERR_UNKNOWN_EXCEPTION_DURING_TOOL_EXECUTION
An unexpected error has been raised during execution of the tool: '%s' -
INFO_DESCRIPTION_DS_REPL_SUBCMD_INITIALIZE
Initialize replication data for the server -
INFO_DSREPL_START_INITIALIZATION_FROM_OR_TO_SINGLE_REMOTE
public static LocalizableMessageDescriptor.Arg3<Object,Object, INFO_DSREPL_START_INITIALIZATION_FROM_OR_TO_SINGLE_REMOTEObject> Starting initialization from '%s' to '%s' for base DNs: %s -
INFO_DSREPL_START_INITIALIZATION_TO_ALL_REMOTE
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_DSREPL_START_INITIALIZATION_TO_ALL_REMOTEStarting initialization from '%s' to all replicas for base DNs: %s -
INFO_DSREPL_START_BASE_DN_INITIALIZATION
Starting initialization for base DN: '%s' -
ERROR_DSREPL_ERROR_LAUNCHING_INITIALIZATION
An error occurred when launching initialization: %s -
INFO_DSREPL_BASE_DN_DESCRIPTION
Base DN(s) to use. Multiple base DNs can be provided by using this option multiple times -
INFO_DSREPL_FROM_SERVER_DESCRIPTION
Server ID of the server containing the source data -
INFO_FROM_SERVER_PLACEHOLDER
{serverSource} -
INFO_DSREPL_TO_SERVER_DESCRIPTION
Server ID of the server to be initialized -
INFO_TO_SERVER_PLACEHOLDER
{serverToInitialize} -
INFO_DSREPL_TO_ALL_SERVERS_DESCRIPTION
Initialize all the other servers in the topology -
ERROR_DSREPL_MISSING_SERVER_VALUE
A mandatory argument is missing. Choose one and only one argument from '--toServer', '--fromServer' and '--toAllServers' -
ERROR_DSREPL_TOO_MANY_SERVER_VALUES
Invalid combination of arguments. Choose one and only one argument from '--toServer', '--fromServer' and '--toAllServers' -
ERROR_DSREPL_INITIALIZATION_DURING_INIT_TASK_WITH_LOG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERROR_DSREPL_INITIALIZATION_DURING_INIT_TASK_WITH_LOGAn error occurred during initialization. Last log details: %s. Task state: %s -
ERROR_DSREPL_INITIALIZATION_DURING_INIT_TASK_WITHOUT_LOG
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_INITIALIZATION_DURING_INIT_TASK_WITHOUT_LOGAn error occurred during initialization. Task state: %s -
ERROR_DSREPL_INITIALIZATION_DURING_RESET_GENID_TASK_WITH_LOG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERROR_DSREPL_INITIALIZATION_DURING_RESET_GENID_TASK_WITH_LOGError during the processing of the reset generationID task. Last log details: %s. Task state: %s -
ERROR_DSREPL_INITIALIZATION_DURING_RESET_GENID_TASK_WITHOUT_LOG
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_INITIALIZATION_DURING_RESET_GENID_TASK_WITHOUT_LOGError during the processing of the reset generationID task. Task state: %s -
INFO_DSREPL_MIGRATION_CANNOT_EXTRACT_MASTER_KEY_CERTIFICATE
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_MIGRATION_CANNOT_EXTRACT_MASTER_KEY_CERTIFICATECannot extract the master key pair certificate with alias '%s' because the crypto-manager's key manager provider of the local server does not contain such key or does not support extracting certificates -
INFO_DSREPL_MIGRATION_CANNOT_EXTRACT_CA_CERTIFICATE
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_MIGRATION_CANNOT_EXTRACT_CA_CERTIFICATECannot find a CA certificate in the replication trust managers of the local server. Please verify the %s trust-manager-provider configuration value -
INFO_DSREPL_MIGRATION_BASE_DN_DESCRIPTION
Base DN(s) to replicate -
ERR_DSREPL_MIGRATION_INAPPROPRIATE_SERVER_ID
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_INAPPROPRIATE_SERVER_IDInappropriate server ID '%s' for the local server: it does not represent a numeric value as required to communicate with pre 7.0 servers. Use an integer server ID without leading zeros -
ERR_DSREPL_MIGRATION_INAPPROPRIATE_GROUP_ID
Inappropriate group ID '%s' for the local server: it cannot be converted to an integer, but this is required to communicate with pre 7.0 servers. Use a group ID that can be converted into an integer, or use 'default' if you do not want to set a group ID -
ERR_DSREPL_MIGRATION_SERVER_ID_ALREADY_USED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_MIGRATION_SERVER_ID_ALREADY_USEDObject> Cannot use server ID '%s' for the local server because it is already used by server '%s' (configuration object %s) -
ERR_DSREPL_CANNOT_READ_CONFIGURATION
Cannot read the configuration of the local server. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_READ_CN_ADMIN_DATA
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_MIGRATION_CANNOT_READ_CN_ADMIN_DATACannot read 'cn=admin data' in server '%s'. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_READ_SERVER_IDS
Error when reading the server IDs from all the servers in the old topology. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_DISCOVER_NEW_SERVER_CONFIG
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_CANNOT_DISCOVER_NEW_SERVER_CONFIGCannot discover the configuration of the local server. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_ADD_NEW_SERVER_TO_CN_ADMIN_DATA
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_MIGRATION_CANNOT_ADD_NEW_SERVER_TO_CN_ADMIN_DATACannot add an entry describing the new server to 'cn=admin data' in the remote server '%s' in the existing topology. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_BOOTSTRAP_REPL_SERVERS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_BOOTSTRAP_REPL_SERVERSObject> Cannot add '%s' to the bootstrap replication server list on server '%s'. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_REPL_SERVER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_REPL_SERVERObject> Cannot add '%s' to the configuration of replication server on server '%s'. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_REPL_DOMAIN
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_REPL_DOMAINObject, Object> Cannot add '%s' to the configuration of replication domain '%s' on server '%s'. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_RETRIEVE_REPLICATION_PORT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_MIGRATION_CANNOT_RETRIEVE_REPLICATION_PORTCannot retrieve the replication port from server '%s'. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_CONFIGURE_NEW_SERVER_TO_REPLICATE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_CANNOT_CONFIGURE_NEW_SERVER_TO_REPLICATECannot configure the local server so it can replicate with the servers in the existing topology. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_READ_SERVER_ID
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_READ_SERVER_IDObject, Object> Cannot read server ID from server '%s' on DNs '%s' and '%s'. The errors were: %s -
ERR_DSREPL_MIGRATION_CANNOT_DETERMINE_SERVER_ID
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_DETERMINE_SERVER_IDObject> Cannot determine server ID for server '%s' on DNs '%s' and '%s' -
ERR_DSREPL_MIGRATION_CANNOT_OBTAIN_CONNECTION_TO_SERVER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_MIGRATION_CANNOT_OBTAIN_CONNECTION_TO_SERVERCannot obtain a connection to server '%s' from the existing topology. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_OBTAIN_CONNECTION_TO_ALL_SERVERS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_CANNOT_OBTAIN_CONNECTION_TO_ALL_SERVERSCannot obtain a connection for one of the servers in the existing topology. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_CONFIGURE_REPLICATION_WITH_ALL_SERVERS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_CANNOT_CONFIGURE_REPLICATION_WITH_ALL_SERVERSCannot configure all the servers in the existing topology to replicate with the new server. The error was: %s -
ERR_DSREPL_MIGRATION_ERROR_WHILE_OPENING_OR_CLOSING_MANAGEMENT_CONTEXT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_ERROR_WHILE_OPENING_OR_CLOSING_MANAGEMENT_CONTEXTAn error occurred opening (or closing) a connection to change the configuration of the local server. The error was: %s -
ERR_DSREPL_MIGRATION_ERROR_WHILE_OPENING_CONNECTIONS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_ERROR_WHILE_OPENING_CONNECTIONSAn error occurred opening connections to the server in the existing topology or the new server. The error was: %s -
ERR_DSREPL_MIGRATION_RESTART_THE_SERVER
Once done, restart the server for the changes to take effect -
ERR_DSREPL_MIGRATION_CANNOT_READ_SERVER_ID_OR_GROUP_ID
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_CANNOT_READ_SERVER_ID_OR_GROUP_IDCannot read the server ID or the group ID for the local server. The error(s) are: %s -
ERR_DSREPL_MIGRATION_CANNOT_ADD_ENTRY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_ADD_ENTRYObject> Cannot add the entry '%s' to the server '%s'. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_READ_ENTRY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_READ_ENTRYObject> Cannot read the entry '%s' on server '%s'. The error was: %s -
ERR_DSREPL_MIGRATION_CANNOT_MODIFY_ENTRY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_MIGRATION_CANNOT_MODIFY_ENTRYObject> Cannot modify the entry '%s' on server '%s' to reconcile it with what is expected by the tool. The error was: %s -
INFO_DSREPL_MIGRATION_ADD_INSTANCE_KEYS_TO_CN_ADMIN_DATA
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_MIGRATION_ADD_INSTANCE_KEYS_TO_CN_ADMIN_DATAAdding server instances keys from the existing topology into 'cn=admin data' in the new server -
ERR_DSREPL_MIGRATION_ERROR_WHILE_ADDING_INSTANCE_KEYS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_MIGRATION_ERROR_WHILE_ADDING_INSTANCE_KEYSCannot add server instance keys to the new server. The error was: %s -
INFO_DSREPL_ENABLE_ADMIN_DATA_BACKEND
Enabling 'cn=admin data' backend -
INFO_DSREPL_MIGRATION_CREATE_REPLICATION_TRUST_MANAGER
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_MIGRATION_CREATE_REPLICATION_TRUST_MANAGERCreating the trust manager '%s' to be used by replication connections in the local server -
INFO_DSREPL_MIGRATION_CONFIGURING_REPLICATION
Updating replication configuration on local server -
INFO_DSREPL_MIGRATION_CONFIGURING_REPLICATION_DOMAIN
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_MIGRATION_CONFIGURING_REPLICATION_DOMAINUpdating replication configuration for baseDN '%s' on local server -
INFO_DSREPL_MIGRATION_CONFIGURING_TOPOLOGY_TO_TALK_TO_NEW_SERVER
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_MIGRATION_CONFIGURING_TOPOLOGY_TO_TALK_TO_NEW_SERVERConfiguring the servers in the topology to talk to the local server -
INFO_DSREPL_MIGRATION_POST_CONFIGURE
Replication has been successfully configured on the local server. Note that for replication to work you must initialize the contents of the base DNs that are being replicated. Run the following command(s) to do so: -
INFO_DESCRIPTION_DSREPL_START_DISASTER_RECOVERY_SUBCMD
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_DSREPL_START_DISASTER_RECOVERY_SUBCMDStart disaster recovery for all servers. Read the documentation on disaster recovery carefully before using this command -
INFO_DESCRIPTION_DSREPL_END_DISASTER_RECOVERY_SUBCMD
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_DSREPL_END_DISASTER_RECOVERY_SUBCMDEnd disaster recovery for all servers. Read the documentation on disaster recovery carefully before using this command -
ERROR_DSREPL_POLLING_TASK
An error occurred while attempting to monitor the task progress. The error was: %s -
INFO_DSREPL_CHECK_SERVER_LOGS
Check the server error logs for additional details -
INFO_DESCRIPTION_DSREPL_PURGE_METADATA_SUBCMD
Purges old replication meta-data from application data -
INFO_DSREPL_PURGE_METADATA_MAX_DURATION_DESCRIPTION
Maximum duration of the command in seconds -
INFO_DSREPL_PURGE_METADATA_MAX_DURATION_DESCRIPTION_PLACEHOLDER
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_PURGE_METADATA_MAX_DURATION_DESCRIPTION_PLACEHOLDER{maximum duration in seconds} -
INFO_DSREPL_PURGE_METADATA_START_MSG
Purging old replication meta-data for server '%s' for base DNs: %s -
ERROR_DSREPL_PURGE_METADATA_ERROR_LAUNCHING
An error occurred while purging old replication meta-data: %s -
ERROR_DSREPL_PURGE_METADATA_DURING_TASK_WITH_LOG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERROR_DSREPL_PURGE_METADATA_DURING_TASK_WITH_LOGAn error occurred while purging old replication meta-data. Last log details: %s. Task state: %s -
ERROR_DSREPL_PURGE_METADATA_DURING_TASK_WITHOUT_LOG
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_PURGE_METADATA_DURING_TASK_WITHOUT_LOGAn error occurred while purging old replication meta-data. Task state: %s -
INFO_DESCRIPTION_DSREPL_RESET_CHANGE_NUMBER_SUBCMD
Re-synchronizes the change-log change number of the target server with the change-log change number of the source server -
INFO_DSREPL_RESET_CHANGE_NUMBER_CN_DESCRIPTION
The change number to use as the basis for re-synchronization -
INFO_DSREPL_RESET_CHANGE_NUMBER_CN_DESCRIPTION_PLACEHOLDER
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_RESET_CHANGE_NUMBER_CN_DESCRIPTION_PLACEHOLDER{change number} -
INFO_DSREPL_RESET_CHANGE_NUMBER_START_MSG
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_DSREPL_RESET_CHANGE_NUMBER_START_MSGStart to re-synchronize the change-log change number of server '%s' from the source server '%s' -
INFO_DSREPL_RESET_CHANGE_NUMBER_SELECTED_CN
Re-synchronizing with change number '%s' -
INFO_DSREPL_RESET_CHANGE_NUMBER_CSN_AND_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_DSREPL_RESET_CHANGE_NUMBER_CSN_AND_DNChange number corresponds to start CSN '%s' and base DN '%s' -
ERROR_DSREPL_RESET_CHANGE_NUMBER_SEARCH_ERROR
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_SEARCH_ERRORError when searching change number '%s' in the source server: %s -
ERROR_DSREPL_RESET_CHANGE_NUMBER_UNKNOWN_CN
Unable to retrieve change number '%s' in the source server -
ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_CSN_FOUND
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_CSN_FOUNDNo CSN found for the change number '%s' in the source server -
ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_BASE_DN_FOUND
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_BASE_DN_FOUNDNo base DN found for the change number '%s' in the source server -
ERROR_DSREPL_RESET_CHANGE_NUMBER_UNABLE_TO_RETRIEVE_NEWEST_CN
public static LocalizableMessageDescriptor.Arg0 ERROR_DSREPL_RESET_CHANGE_NUMBER_UNABLE_TO_RETRIEVE_NEWEST_CNUnable to retrieve the newest change number in the source server -
ERROR_DSREPL_RESET_CHANGE_NUMBER_ERROR_LAUNCHING
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_ERROR_LAUNCHINGAn error occurred when re-synchronizing the change number: %s -
ERROR_DSREPL_RESET_CHANGE_NUMBER_DURING_TASK_WITH_LOG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_DURING_TASK_WITH_LOGAn error occurred during the re-synchronization of the change number. Last log details: %s. Task state: %s -
ERROR_DSREPL_RESET_CHANGE_NUMBER_DURING_TASK_WITHOUT_LOG
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_DURING_TASK_WITHOUT_LOGAn error occurred during the re-synchronization of the change number. Task state: %s -
ERROR_DSREPL_RESET_CHANGE_NUMBER_DOMAINS_DO_NOT_MATCH
public static LocalizableMessageDescriptor.Arg0 ERROR_DSREPL_RESET_CHANGE_NUMBER_DOMAINS_DO_NOT_MATCHThe source and target server have distinct replication domains. As a consequence the change number from the target server can't be reset from a change number of the source server -
ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_DOMAIN_FOUND
Unable to find a replicated domain in the target server -
ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_MATCHING_DOMAIN_FOUND
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_MATCHING_DOMAIN_FOUNDUnable to find a replicated domain matching the DN '%s' corresponding to the change number -
ERROR_DSREPL_RESET_CHANGE_NUMBER_UNSUCCESSFUL_WHEN_SEARCHING_DOMAIN
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_UNSUCCESSFUL_WHEN_SEARCHING_DOMAINAn error occurred when searching replicated domains in server. Result code was: '%s' -
ERROR_DSREPL_RESET_CHANGE_NUMBER_ERROR_WHEN_SEARCHING_DOMAIN
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_DSREPL_RESET_CHANGE_NUMBER_ERROR_WHEN_SEARCHING_DOMAINAn error occurred when searching replicated domains in server: %s -
INFO_DESCRIPTION_DSREPL_STATUS_SUBCMD
Displays the status of the replication service and various diagnostics about it. The information is derived from reading cn=monitor on all the servers in the replication topology. The status of a server is one of the following. - BAD - DATA MISMATCH: either the fractional replication configuration does not match the backend data, or the initial state of the replicated data does not match other servers and this server must be re-initialized; - BAD - TOO LATE: the server has fallen further behind than the replication purge delay and must be re-initialized; - GOOD: normal operation, nothing to do; - SLOW: the server's replay delay is greater than five seconds; - UNHEALTHY: read the server health errors in the server monitoring data for details -
INFO_DSREPL_STATUS_HEADING_BASEDN
Base DN -
INFO_DSREPL_STATUS_HEADING_BASEDN_DS
Base DN / DS -
INFO_DSREPL_STATUS_HEADING_BASEDN_RS
Base DN / RS -
INFO_DSREPL_STATUS_HEADING_BASEDN_RS_DS
Base DN / RS / DS -
INFO_DSREPL_STATUS_HEADING_STATUS
Status -
INFO_DSREPL_STATUS_HEADING_GROUP
Group -
INFO_DSREPL_STATUS_HEADING_RECEIVE_DELAY
Receive delay (ms) -
INFO_DSREPL_STATUS_HEADING_REPLAY_DELAY
Replay delay (ms) -
INFO_DSREPL_STATUS_HEADING_ENTRIES_COUNT
Entry count -
INFO_DSREPL_STATUS_HEADING_SERVER_HOSTPORT
Server / host port -
INFO_DSREPL_STATUS_HEADING_ERROR_OR_DIAGNOSTIC
Error or diagnostic -
INFO_DSREPL_STATUS_SHOW_REPLICAS_DESCRIPTION
Displays individual replicas in the output -
INFO_DSREPL_STATUS_SHOW_CHANGELOGS_DESCRIPTION
Displays individual changelog servers in the output -
INFO_DSREPL_STATUS_SHOW_GROUPS_DESCRIPTION
Display replication group information in the output -
ERR_DSREPL_STATUS_CANNOT_READ_CN_MONITOR_ON_TARGET_SERVER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_STATUS_CANNOT_READ_CN_MONITOR_ON_TARGET_SERVERAn error occurred while reading cn=monitor on server %s: %s -
ERR_DSREPL_STATUS_CANNOT_READ_CN_MONITOR_ON_SERVER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_STATUS_CANNOT_READ_CN_MONITOR_ON_SERVERError while reading cn=monitor: %s -
ERR_DSREPL_STATUS_NO_ADMIN_PORT_FOR_SERVER
Cannot contact server: no admin port could be discovered in its entry %s -
ERR_DSREPL_STATUS_UNHEALTHY_SERVER
Server is not healthy: %s -
ERR_DSREPL_STATUS_GENERAL_ERROR_READING_CN_MONITOR
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_STATUS_GENERAL_ERROR_READING_CN_MONITORGeneral error: %s -
INFO_DSREPL_STATUS_BASE_DN_DESCRIPTION
Base DN(s) to display. Multiple base DNs can be provided by using this option multiple times. If no base DNs are provided, then all the base DNs will be displayed -
INFO_DESCRIPTION_SUBCMD_CLEAR_CHANGELOG
Clears all replication server changelog data for the offline local server; the other replication servers in the topology will transfer any needed data when the server restarts -
ERR_DSREPL_CLEAR_CHANGELOG_DELETE_FAILED
A problem occurred while clearing the changelog data: %s -
INFO_DSREPL_CLEAR_CHANGELOG_PROGRESS
Clearing all replication server changelog data for the local server -
INFO_DSREPL_CLEAR_CHANGELOG_NOTHING_TO_DO
Nothing to do: this server does not keep any replication server changelog data -
ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_OBTAIN_CONNECTION_TO_ALL_SERVERS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_OBTAIN_CONNECTION_TO_ALL_SERVERSCannot obtain a connection for one of the servers in the topology. The error was: %s -
ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_OBTAIN_CONNECTION_TO_SERVER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_OBTAIN_CONNECTION_TO_SERVERCannot obtain a connection to server '%s' from the topology. The error was: %s -
ERR_DSREPL_CLEANUP_MIGRATED_ERROR_WHILE_OPENING_OR_CLOSING_MANAGEMENT_CONTEXT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_CLEANUP_MIGRATED_ERROR_WHILE_OPENING_OR_CLOSING_MANAGEMENT_CONTEXTAn error occurred opening (or closing) a connection to read or change the configuration of the local server. The error was: %s -
INFO_DSREPL_CLEANUP_MIGRATED_ALREADY_DONE
This server has already been cleaned, there is nothing left to do -
INFO_DSREPL_CLEANUP_MIGRATED_WRONG_BIND_DN
The remaining cleanup on this server cannot be performed because the administrator user '%s' in the admin backend was used to bind to the server. You should run again this command using a bind DN, such as "uid=admin", which lies outside the "cn=admin data" backend to be able to complete the cleanup on this server -
ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_DISABLE_ADMIN_BACKEND
public static LocalizableMessageDescriptor.Arg1<Object> ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_DISABLE_ADMIN_BACKENDCannot disable admin backend on the local server. The error was: %s -
ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_UPDATE_CONFIGURATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_UPDATE_CONFIGURATIONCannot update configuration for server '%s'. The error was: %s -
ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_READ_MONITOR_ENTRY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_READ_MONITOR_ENTRYCannot read monitor entries under '%s' on the local server. The error was: %s -
ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_DELETE_ADMIN_ENTRIES
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_DELETE_ADMIN_ENTRIESCannot delete entries under '%s' in admin backend. The error was: %s -
INFO_DSREPL_CLEANUP_MIGRATED_ALL_SERVERS_CLEANED_UP
All servers have been cleaned -
INFO_DSREPL_CLEANUP_MIGRATED_ALL_SERVERS_CLEANED_UP_WITH_SECRET_KEYS
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_CLEANUP_MIGRATED_ALL_SERVERS_CLEANED_UP_WITH_SECRET_KEYSAll servers have been cleaned. The admin backend will remain enabled because it contains secret keys that may be used by reversible password storage schemes -
INFO_DSREPL_CLEANUP_MIGRATED_SECONDARY_CLEANUP_DONE
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_CLEANUP_MIGRATED_SECONDARY_CLEANUP_DONEThe server %s has now been cleaned -
INFO_DSREPL_CLEANUP_MIGRATED_ADMIN_USER_NOT_REMOVED
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_CLEANUP_MIGRATED_ADMIN_USER_NOT_REMOVEDServers have been cleaned, however the administrator user '%s' in the admin backend was not removed because it was used to bind to the server. To remove it, you should run the following commands on all servers using a bind DN, such as "uid=admin", which lies outside the "cn=admin data" backend: -
INFO_DSREPL_CLEANUP_MIGRATED_REMOVE_ADMIN_BACKEND_SERVERS
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_CLEANUP_MIGRATED_REMOVE_ADMIN_BACKEND_SERVERSRemoving servers from admin backend -
INFO_DSREPL_CLEANUP_MIGRATED_REMOVE_ADMIN_BACKEND_INSTANCE_KEYS
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_CLEANUP_MIGRATED_REMOVE_ADMIN_BACKEND_INSTANCE_KEYSRemoving instance keys from admin backend -
INFO_DSREPL_CLEANUP_MIGRATED_REMOVE_ADMIN_BACKEND_ADMINISTRATORS
public static LocalizableMessageDescriptor.Arg0 INFO_DSREPL_CLEANUP_MIGRATED_REMOVE_ADMIN_BACKEND_ADMINISTRATORSRemoving administrators from admin backend -
INFO_DSREPL_CLEANUP_MIGRATED_CLEANUP_CONFIGURATION
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_CLEANUP_MIGRATED_CLEANUP_CONFIGURATIONCleaning and updating configuration of server %s -
INFO_DSREPL_CLEANUP_MIGRATED_SET_BOOTSTRAP_SERVERS_CONFIG
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_CLEANUP_MIGRATED_SET_BOOTSTRAP_SERVERS_CONFIGSet bootstrap servers configuration for server %s -
INFO_DSREPL_CLEANUP_MIGRATED_DISABLE_ADMIN_BACKEND
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DSREPL_CLEANUP_MIGRATED_DISABLE_ADMIN_BACKENDDisable admin backend for server %s -
WARN_DSREPL_CLEANUP_MIGRATED_REVERSIBLE_PASSWORD_STORAGE_SCHEME_ENABLED
public static LocalizableMessageDescriptor.Arg0 WARN_DSREPL_CLEANUP_MIGRATED_REVERSIBLE_PASSWORD_STORAGE_SCHEME_ENABLEDSome reversible password storage schemes are enabled in the configuration, note that it won't be possible to use them in password policies since the admin data backend has been disabled -
INFO_DESCRIPTION_SUBCMD_CLEANUP_MIGRATED_PRE_70_TOPOLOGY
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_SUBCMD_CLEANUP_MIGRATED_PRE_70_TOPOLOGYClean all the servers (with version 7.0 or more) that have been migrated from a topology of older servers (version prior to 7.0) -
ERR_ROOTDSE_CONFIG_ENTRY_NULL
An attempt was made to configure the root DSE backend without providing a configuration entry. This is not allowed -
WARN_ROOTDSE_NO_BACKEND_FOR_SUBORDINATE_BASE
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ROOTDSE_NO_BACKEND_FOR_SUBORDINATE_BASEBase DN "%s" is configured as one of the subordinate base DNs to use for searches below the root DSE. However, this base DN is not handled by any suffix registered with the Directory Server and will therefore not be used -
ERR_ROOTDSE_MODIFY_NOT_SUPPORTED
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 -
ERR_ROOTDSE_INVALID_SEARCH_BASE
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_ROOTDSE_INVALID_SEARCH_BASEObject> 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 -
ERR_ROOTDSE_INVALID_SEARCH_SCOPE
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_ROOTDSE_INVALID_SEARCH_SCOPEObject> Unable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %s -
ERR_ROOTDSE_UNABLE_TO_CREATE_LDIF_WRITER
An unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %s -
ERR_ROOTDSE_UNABLE_TO_EXPORT_DSE
An unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %s -
INFO_ROOTDSE_USING_NEW_USER_ATTRS
The root DSE configuration has been updated so that it will now use a new set of user-defined attributes -
ERR_MONITOR_CONFIG_ENTRY_NULL
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 -
ERR_BACKEND_ADD_NOT_SUPPORTED
Unwilling to add entry "%s" because add operations are not supported in the "%s" backend -
ERR_BACKEND_DELETE_NOT_SUPPORTED
Unwilling to remove entry "%s" because delete operations are not supported in the "%s" backend -
ERR_MONITOR_MODIFY_NOT_SUPPORTED
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 -
ERR_BACKEND_MODIFY_DN_NOT_SUPPORTED
Unwilling to rename entry "%s" because modify DN operations are not supported in the "%s" backend -
ERR_MONITOR_UNABLE_TO_EXPORT_BASE
An error occurred while attempting to export the base monitor entry: %s -
ERR_MONITOR_UNABLE_TO_EXPORT_PROVIDER_ENTRY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MONITOR_UNABLE_TO_EXPORT_PROVIDER_ENTRYAn error occurred while attempting to export the monitor entry for monitor provider %s: %s -
ERR_BACKEND_IMPORT_NOT_SUPPORTED
The "%s" backend does not support LDIF import operations -
INFO_MONITOR_USING_NEW_USER_ATTRS
The monitor configuration has been updated so that it will now use a new set of user-defined attributes -
ERR_BACKEND_GET_ENTRY_NULL
Unable to retrieve the requested entry from the "%s" backend because the provided DN was null -
ERR_MONITOR_INVALID_BASE
Unable to retrieve the requested entry %s from the monitor backend because the DN is not below the monitor base of %s -
ERR_SCHEMA_CONFIG_ENTRY_NULL
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 -
ERR_SCHEMA_UNABLE_TO_EXPORT_BASE
An error occurred while attempting to export the base schema entry: %s -
ERR_SCHEMA_INVALID_BASE
Unable to retrieve the requested entry %s from the schema backend because the DN is equal to one of the schema entry DNs -
ERR_SCHEMA_UNABLE_TO_CREATE_LDIF_WRITER
An unexpected error occurred while trying to open the LDIF writer for the schema backend: %s -
ERR_BACKEND_CANNOT_LOCK_ENTRY
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 -
ERR_TASK_INVALID_STATE
The task defined in entry %s is invalid because it has an invalid state %s -
ERR_TASK_CANNOT_PARSE_SCHEDULED_START_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASK_CANNOT_PARSE_SCHEDULED_START_TIMEAn error occurred while trying to parse the scheduled start time value %s from task entry %s -
ERR_TASK_CANNOT_PARSE_ACTUAL_START_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASK_CANNOT_PARSE_ACTUAL_START_TIMEAn error occurred while trying to parse the actual start time value %s from task entry %s -
ERR_TASK_CANNOT_PARSE_COMPLETION_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASK_CANNOT_PARSE_COMPLETION_TIMEAn error occurred while trying to parse the completion time value %s from task entry %s -
ERR_TASK_MISSING_ATTR
Task entry %s is missing required attribute %s -
ERR_TASK_MULTIPLE_ATTRS_FOR_TYPE
There are multiple instances of attribute %s in task entry %s -
ERR_TASK_MULTIPLE_VALUES_FOR_ATTR
There are multiple values for attribute %s in task entry %s -
ERR_TASK_EXECUTE_FAILED
An error occurred while executing the task defined in entry %s: %s -
ERR_RECURRINGTASK_NO_ID_ATTRIBUTE
The provided recurring task entry does not contain attribute %s which is needed to hold the recurring task ID -
ERR_RECURRINGTASK_MULTIPLE_ID_TYPES
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 -
ERR_RECURRINGTASK_NO_ID
The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task ID -
ERR_RECURRINGTASK_MULTIPLE_ID_VALUES
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 -
ERR_RECURRINGTASK_NO_SCHEDULE_ATTRIBUTE
The provided recurring task entry does not contain attribute %s which is needed to specify recurring task schedule -
ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_TYPES
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 -
ERR_RECURRINGTASK_NO_SCHEDULE_VALUES
The provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task schedule -
ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_VALUES
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 -
ERR_RECURRINGTASK_CANNOT_LOAD_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_RECURRINGTASK_CANNOT_LOAD_CLASSObject> 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? -
ERR_RECURRINGTASK_CANNOT_INSTANTIATE_CLASS_AS_TASK
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_RECURRINGTASK_CANNOT_INSTANTIATE_CLASS_AS_TASKAn error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s? -
ERR_RECURRINGTASK_CANNOT_INITIALIZE_INTERNAL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_RECURRINGTASK_CANNOT_INITIALIZE_INTERNALAn error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s -
ERR_TASKBE_BACKING_FILE_EXISTS
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 -
ERR_TASKBE_INVALID_BACKING_FILE_PATH
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 -
ERR_TASKBE_BACKING_FILE_MISSING_PARENT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKBE_BACKING_FILE_MISSING_PARENTThe 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 -
ERR_TASKBE_BACKING_FILE_PARENT_NOT_DIRECTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKBE_BACKING_FILE_PARENT_NOT_DIRECTORYThe 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 -
ERR_TASKBE_ERROR_GETTING_BACKING_FILE
An error occurred while attempting to determine the new path to the task data backing file: %s -
INFO_TASKBE_UPDATED_RETENTION_TIME
The completed task retention time has been updated to %d seconds. This will take effect immediately -
INFO_TASKBE_UPDATED_BACKING_FILE
The path to the task data backing file has been changed to %s. A snapshot of the current task configuration has been written to that file and it will continue to be used for future updates -
ERR_TASKBE_ADD_DISALLOWED_DN
New entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasks -
INFO_TASKBE_BACKING_FILE_HEADER
This file contains the data used by the Directory Server task scheduler backend. Do not edit this file directly, as there is a risk that those changes will be lost. Scheduled and recurring task definitions should only be edited using the administration utilities provided with the Directory Server -
ERR_TASKSCHED_DUPLICATE_RECURRING_ID
Unable to add recurring task %s to the task scheduler because another recurring task already exists with the same ID -
ERR_TASKSCHED_DUPLICATE_TASK_ID
Unable to schedule task %s because another task already exists with the same ID -
WARN_TASKSCHED_DUPLICATE_TASK_ID
Unable to add completed task %s to the task scheduler because another task already exists with the same ID -
ERR_TASKSCHED_ERROR_SCHEDULING_RECURRING_ITERATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_ERROR_SCHEDULING_RECURRING_ITERATIONAn error occurred while attempting to schedule the next iteration of recurring task %s: %s -
ERR_TASKSCHED_CANNOT_PARSE_ENTRY_RECOVERABLE
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_TASKSCHED_CANNOT_PARSE_ENTRY_RECOVERABLEObject> 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 -
ERR_TASKSCHED_CANNOT_PARSE_ENTRY_FATAL
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_TASKSCHED_CANNOT_PARSE_ENTRY_FATALObject> 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 -
ERR_TASKSCHED_ENTRY_HAS_NO_PARENT
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 -
ERR_TASKSCHED_CANNOT_SCHEDULE_RECURRING_TASK_FROM_ENTRY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_CANNOT_SCHEDULE_RECURRING_TASK_FROM_ENTRYAn error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %s -
ERR_TASKSCHED_CANNOT_SCHEDULE_TASK_FROM_ENTRY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_CANNOT_SCHEDULE_TASK_FROM_ENTRYAn error occurred while attempting to parse entry %s as a task and add it to the scheduler: %s -
ERR_TASKSCHED_INVALID_TASK_ENTRY_DN
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 -
ERR_TASKSCHED_ERROR_READING_TASK_BACKING_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_ERROR_READING_TASK_BACKING_FILEAn error occurred while attempting to read from the tasks data backing file %s: %s -
ERR_TASKSCHED_CANNOT_CREATE_BACKING_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_CANNOT_CREATE_BACKING_FILEAn error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %s -
ERR_TASKSCHED_NO_CLASS_ATTRIBUTE
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 -
ERR_TASKSCHED_MULTIPLE_CLASS_TYPES
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 -
ERR_TASKSCHED_NO_CLASS_VALUES
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 -
ERR_TASKSCHED_MULTIPLE_CLASS_VALUES
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 -
ERR_TASKSCHED_CANNOT_LOAD_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_TASKSCHED_CANNOT_LOAD_CLASSObject> 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? -
ERR_TASKSCHED_CANNOT_INSTANTIATE_CLASS_AS_TASK
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_CANNOT_INSTANTIATE_CLASS_AS_TASKAn error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s? -
ERR_TASKSCHED_CANNOT_INITIALIZE_INTERNAL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_CANNOT_INITIALIZE_INTERNALAn error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s -
WARN_TASKSCHED_CANNOT_RENAME_CURRENT_BACKING_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_TASKSCHED_CANNOT_RENAME_CURRENT_BACKING_FILEObject> An error occurred while attempting to rename the current tasks backing file from %s to %s: %s. The previous task configuration (which does not reflect the latest update) may be lost -
ERR_TASKSCHED_CANNOT_RENAME_NEW_BACKING_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_TASKSCHED_CANNOT_RENAME_NEW_BACKING_FILEObject> 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 -
ERR_TASKSCHED_CANNOT_WRITE_BACKING_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASKSCHED_CANNOT_WRITE_BACKING_FILEAn error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lost -
INFO_TASKBE_INTERRUPTED_BY_SHUTDOWN
The tasks backend is being shut down -
INFO_ROOTDSE_UPDATED_SHOW_ALL_ATTRS
The root DSE configuration has been updated so that configuration attribute %s will now use a value of %s -
ERR_TASKSCHED_REMOVE_PENDING_NO_SUCH_TASK
Unable to remove pending task %s because no such task exists -
ERR_TASKSCHED_REMOVE_PENDING_NOT_PENDING
Unable to remove pending task %s because the task is no longer pending -
ERR_TASKSCHED_REMOVE_COMPLETED_NO_SUCH_TASK
Unable to remove completed task %s because no such task exists in the list of completed tasks -
ERR_TASKBE_DELETE_INVALID_ENTRY
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 -
ERR_TASKBE_DELETE_NO_SUCH_TASK
Unable to remove entry %s from the task backend because there is no scheduled task associated with that entry DN -
ERR_TASKBE_DELETE_RUNNING
Unable to delete entry %s from the task backend because the associated task is currently running -
ERR_TASKBE_DELETE_NO_SUCH_RECURRING_TASK
Unable to remove entry %s from the task backend because there is no recurring task associated with that entry DN -
ERR_TASKBE_SEARCH_INVALID_BASE
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 -
ERR_TASKBE_SEARCH_NO_SUCH_TASK
Unable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %s -
ERR_TASKBE_SEARCH_NO_SUCH_RECURRING_TASK
Unable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %s -
ERR_BACKEND_MODIFY_NOT_SUPPORTED
Unwilling to update entry "%s" because modify operations are not supported in the "%s" backend -
ERR_MEMORYBACKEND_REQUIRE_EXACTLY_ONE_BASE
Exactly one base DN must be provided for use with the memory-based backend -
ERR_MEMORYBACKEND_ENTRY_ALREADY_EXISTS
Entry %s already exists in the memory-based backend -
ERR_MEMORYBACKEND_ENTRY_DOESNT_BELONG
Entry %s does not belong in the memory-based backend -
ERR_MEMORYBACKEND_PARENT_DOESNT_EXIST
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MEMORYBACKEND_PARENT_DOESNT_EXISTUnable to add entry %s because its parent entry %s does not exist in the memory-based backend -
ERR_BACKEND_ENTRY_DOESNT_EXIST
Entry %s does not exist in the "%s" backend -
ERR_MEMORYBACKEND_CANNOT_DELETE_ENTRY_WITH_CHILDREN
public static LocalizableMessageDescriptor.Arg1<Object> ERR_MEMORYBACKEND_CANNOT_DELETE_ENTRY_WITH_CHILDRENCannot delete entry %s because it has one or more subordinate entries -
ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_WRITER
Unable to create an LDIF writer: %s -
ERR_MEMORYBACKEND_CANNOT_WRITE_ENTRY_TO_LDIF
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MEMORYBACKEND_CANNOT_WRITE_ENTRY_TO_LDIFCannot write entry %s to LDIF: %s -
ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_READER
Unable to create an LDIF reader: %s -
ERR_MEMORYBACKEND_ERROR_READING_LDIF
An unrecoverable error occurred while reading from LDIF: %s -
ERR_MEMORYBACKEND_ERROR_DURING_IMPORT
An unexpected error occurred while processing the import: %s -
ERR_MEMORYBACKEND_CANNOT_RENAME_ENRY_WITH_CHILDREN
public static LocalizableMessageDescriptor.Arg1<Object> ERR_MEMORYBACKEND_CANNOT_RENAME_ENRY_WITH_CHILDRENCannot rename entry %s because it has one or more subordinate entries -
ERR_MEMORYBACKEND_CANNOT_RENAME_TO_ANOTHER_BACKEND
public static LocalizableMessageDescriptor.Arg1<Object> ERR_MEMORYBACKEND_CANNOT_RENAME_TO_ANOTHER_BACKENDCannot rename entry %s because the target entry is in a different backend -
ERR_MEMORYBACKEND_RENAME_PARENT_DOESNT_EXIST
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MEMORYBACKEND_RENAME_PARENT_DOESNT_EXISTCannot rename entry %s because the new parent entry %s doesn't exist -
ERR_BACKEND_CANNOT_REGISTER_BASEDNS
An error occurred while attempting to register the base DNs %s in the Directory Server: %s -
ERR_SCHEMA_INVALID_MODIFICATION_TYPE
The schema backend does not support the %s modification type -
ERR_SCHEMA_MODIFY_UNSUPPORTED_ATTRIBUTE_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SCHEMA_MODIFY_UNSUPPORTED_ATTRIBUTE_TYPEThe 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 -
ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_SCHEMA
An error occurred while attempting to write the updated schema: %s -
ERR_SCHEMA_MODIFY_DELETE_NO_VALUES
The server will not allow removing all values for the %s attribute type in the server schema -
ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_AT
Circular reference detected for attribute type %s in which the superior type chain references the attribute type itself -
ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_OC
Circular reference detected for objectclass %s in which the superior class chain references the objectclass itself -
ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_DSR
Circular reference detected for DIT structure rule %s in which the superior rule chain references the DIT structure rule itself -
ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_CLEANED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_CLEANEDAn 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 -
ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_NOT_CLEANED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_NOT_CLEANEDAn 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 -
ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_RESTORED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_RESTOREDAn 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 -
ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_NOT_RESTORED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_NOT_RESTOREDAn 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 -
ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_ATTRIBUTE_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_ATTRIBUTE_TYPEUnable to remove attribute type %s from the server schema because no such attribute type is defined -
ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_OBJECTCLASS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_OBJECTCLASSUnable to remove objectclass %s from the server schema because no such objectclass is defined -
ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_NAME_FORM
Unable to remove name form %s from the server schema because no such name form is defined -
ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DCR
Unable to remove DIT content rule %s from the server schema because no such DIT content rule is defined -
ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DSR
Unable to remove DIT structure rule %s from the server schema because no such DIT structure rule is defined -
ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_MR_USE
Unable to remove matching rule use %s from the server schema because no such matching rule use is defined -
ERR_SCHEMA_MODIFY_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to modify the Directory Server schema -
ERR_SCHEMA_CANNOT_FIND_CONCAT_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SCHEMA_CANNOT_FIND_CONCAT_FILEObject> 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 -
ERR_SCHEMA_ERROR_DETERMINING_SCHEMA_CHANGES
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 -
ERR_SCHEMA_CANNOT_WRITE_CONCAT_SCHEMA_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SCHEMA_CANNOT_WRITE_CONCAT_SCHEMA_FILEAn 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 -
ERR_TASKSCHED_NOT_ALLOWED_TASK
The Directory Server is not configured to allow task %s to be invoked -
INFO_TASK_COMPLETION_BODY
public static LocalizableMessageDescriptor.Arg6<Object,Object, INFO_TASK_COMPLETION_BODYObject, Object, Object, Object> Task ID: %s Task State: %s Scheduled Start Time: %s Actual Start Time: %s Completion Time: %s Description: %s Log Messages: -
ERR_INDEXES_NOT_SUPPORTED
Indexes are not supported in the "%s" backend -
ERR_BACKEND_IMPORT_AND_EXPORT_NOT_SUPPORTED
LDIF import and export operations are not supported in the "%s" backend -
ERR_ROOT_CONTAINER_NOT_INITIALIZED
The root container for backend %s has not been initialized preventing this backend from processing the requested operation -
ERR_TASKBE_MODIFY_INVALID_ENTRY
Entry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backend -
ERR_TASKBE_MODIFY_NO_SUCH_TASK
Entry %s cannot be modified because it does not represent a valid task in the server -
ERR_TASKBE_MODIFY_COMPLETED
Entry %s cannot be modified because the associated task has completed running. Completed tasks cannot be modified -
ERR_TASKBE_MODIFY_RECURRING
Entry %s cannot be modified because the server does not currently support modifying recurring task entries -
ERR_TASKBE_MODIFY_RUNNING
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" -
INFO_TASKBE_RUNNING_TASK_CANCELLED
Task processing was interrupted by a modify request to cancel the task -
ERR_LDIF_BACKEND_MULTIPLE_BASE_DNS
The LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNs -
ERR_LDIF_BACKEND_DUPLICATE_ENTRY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDIF_BACKEND_DUPLICATE_ENTRYObject> LDIF file %s configured for use with the LDIF backend defined in configuration entry %s has multiple entries with a DN of %s -
ERR_LDIF_BACKEND_ENTRY_OUT_OF_SCOPE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDIF_BACKEND_ENTRY_OUT_OF_SCOPEObject> 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 -
ERR_LDIF_BACKEND_MISSING_PARENT
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDIF_BACKEND_MISSING_PARENTObject> 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 -
ERR_LDIF_BACKEND_ERROR_CREATING_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDIF_BACKEND_ERROR_CREATING_FILEObject> 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 -
ERR_LDIF_BACKEND_ERROR_WRITING_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDIF_BACKEND_ERROR_WRITING_FILEObject> An error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %s -
ERR_LDIF_BACKEND_ERROR_RENAMING_FILE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_LDIF_BACKEND_ERROR_RENAMING_FILEObject, Object> 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 -
ERR_LDIF_BACKEND_ADD_ALREADY_EXISTS
Entry %s already exists in the LDIF backend -
ERR_LDIF_BACKEND_ADD_MISSING_PARENT
The parent for entry %s does not exist -
ERR_LDIF_BACKEND_DELETE_NO_SUCH_ENTRY
Entry %s does not exist -
ERR_LDIF_BACKEND_DELETE_NONLEAF
Entry %s has one or more subordinate entries and cannot be deleted until all of its subordinate entries are removed first -
ERR_LDIF_BACKEND_MODIFY_NO_SUCH_ENTRY
Entry %s does not exist -
ERR_LDIF_BACKEND_MODDN_NO_SUCH_SOURCE_ENTRY
Source entry %s does not exist -
ERR_LDIF_BACKEND_MODDN_TARGET_ENTRY_ALREADY_EXISTS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIF_BACKEND_MODDN_TARGET_ENTRY_ALREADY_EXISTSTarget entry %s already exists -
ERR_LDIF_BACKEND_MODDN_NEW_PARENT_DOESNT_EXIST
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIF_BACKEND_MODDN_NEW_PARENT_DOESNT_EXISTThe new parent DN %s does not exist -
ERR_LDIF_BACKEND_SEARCH_NO_SUCH_BASE
Entry %s specified as the search base DN does not exist -
ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_WRITER
An error occurred while trying to create the writer for the LDIF export operation: %s -
ERR_LDIF_BACKEND_CANNOT_WRITE_ENTRY_TO_LDIF
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIF_BACKEND_CANNOT_WRITE_ENTRY_TO_LDIFAn error occurred while trying to write entry %s during the LDIF export: %s -
ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_READER
An error occurred while trying to create the reader for the LDIF import operation: %s -
ERR_LDIF_BACKEND_ERROR_READING_LDIF
An unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continue -
INFO_LDIF_BACKEND_LDIF_FILE_CHANGED
The change to the LDIF file path will not take effect until the backend is disabled and re-enabled -
INFO_LDIF_BACKEND_BASE_DN_CHANGED
The change to the LDIF backend base DN will not take effect until the backend is disabled and re-enabled -
ERR_LDIF_BACKEND_HAS_SUBORDINATES_NO_SUCH_ENTRY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIF_BACKEND_HAS_SUBORDINATES_NO_SUCH_ENTRYThe target entry %s does not exist -
ERR_LDIF_BACKEND_NUM_SUBORDINATES_NO_SUCH_ENTRY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIF_BACKEND_NUM_SUBORDINATES_NO_SUCH_ENTRYThe target entry %s does not exist -
ERR_NUM_SUBORDINATES_NOT_SUPPORTED
This backend does not provide support for the numSubordinates operational attribute -
NOTE_BACKEND_OFFLINE
The backend %s is now taken offline -
ERR_RECURRINGTASK_INVALID_N_TOKENS
The provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokens -
ERR_RECURRINGTASK_INVALID_MINUTE_TOKEN
The provided recurring task entry attribute %s holding the recurring task schedule has invalid minute token -
ERR_RECURRINGTASK_INVALID_HOUR_TOKEN
The provided recurring task entry attribute %s holding the recurring task schedule has invalid hour token -
ERR_RECURRINGTASK_INVALID_DAY_TOKEN
The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month token -
ERR_RECURRINGTASK_INVALID_MONTH_TOKEN
The provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year token -
ERR_RECURRINGTASK_INVALID_WEEKDAY_TOKEN
The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week token -
ERR_RECURRINGTASK_INVALID_TOKENS_COMBO
The provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar date -
ERR_TASKS_CANNOT_EXPORT_TO_FILE
An error occurred while attempting to export task backend data: %s -
INFO_ERGONOMIC_SIZING_OF_JE_CLEANER_THREADS
public static LocalizableMessageDescriptor.Arg2<Object,Number> INFO_ERGONOMIC_SIZING_OF_JE_CLEANER_THREADSJE backend '%s' does not specify the number of cleaner threads: defaulting to %d threads -
INFO_ERGONOMIC_SIZING_OF_JE_LOCK_TABLES
public static LocalizableMessageDescriptor.Arg2<Object,Number> INFO_ERGONOMIC_SIZING_OF_JE_LOCK_TABLESJE backend '%s' does not specify the number of lock tables: defaulting to %d -
ERR_TASKSCHED_DEPENDENCY_MISSING
Unable to schedule task %s because its dependency task %s is missing -
NOTE_TASK_STARTED
%s task %s started execution -
NOTE_TASK_FINISHED
%s task %s finished execution in the state %s -
ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_LSD
Unable to remove ldap syntax description %s from the server schema because no such ldap syntax description is defined -
ERR_SCHEMA_MODIFY_CANNOT_DECODE_LDAP_SYNTAX
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SCHEMA_MODIFY_CANNOT_DECODE_LDAP_SYNTAXAn error occurred while attempting to decode the ldapsyntax description "%s": %s -
ERR_RECURRINGTASK_INVALID_N_TOKENS_SIMPLE
The provided recurring task schedule value has an invalid number of tokens -
ERR_RECURRINGTASK_INVALID_MINUTE_TOKEN_SIMPLE
The provided recurring task schedule value has an invalid minute token -
ERR_RECURRINGTASK_INVALID_HOUR_TOKEN_SIMPLE
The provided recurring task schedule value has an invalid hour token -
ERR_RECURRINGTASK_INVALID_DAY_TOKEN_SIMPLE
The provided recurring task schedule value has an invalid day of the month token -
ERR_RECURRINGTASK_INVALID_MONTH_TOKEN_SIMPLE
The provided recurring task schedule value has an invalid month of the year token -
ERR_RECURRINGTASK_INVALID_WEEKDAY_TOKEN_SIMPLE
The provided recurring task schedule value has an invalid day of the week token -
ERR_SCHEMA_INVALID_REPLACE_MODIFICATION
The schema backend does not support the Replace modification type for the %s attribute type -
ERR_LDIF_BACKEND_ERROR_CLOSING_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDIF_BACKEND_ERROR_CLOSING_FILEObject> An error occurred while trying to close file %s for the LDIF backend defined in configuration entry %s: %s -
ERR_LDIF_BACKEND_ERROR_EMPTY_FILE
The file %s written for the LDIF backend defined in configuration entry %s is 0 bytes long and unusable -
ERR_BACKEND_CONFIG_CACHE_SIZE_GREATER_THAN_JVM_HEAP
public static LocalizableMessageDescriptor.Arg2<Number,Number> ERR_BACKEND_CONFIG_CACHE_SIZE_GREATER_THAN_JVM_HEAPConfiguration 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 -
ERR_BACKEND_CONFIG_CACHE_PERCENT_GREATER_THAN_JVM_HEAP
public static LocalizableMessageDescriptor.Arg2<Number,Number> ERR_BACKEND_CONFIG_CACHE_PERCENT_GREATER_THAN_JVM_HEAPConfiguration attribute ds-cfg-db-cache-percent has a value of %d%% but the JVM has only %d%% available -
ERR_VLV_BAD_ASSERTION
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 -
WARN_DISK_SPACE_LOW_THRESHOLD_CROSSED
public static LocalizableMessageDescriptor.Arg4<Number,Object, WARN_DISK_SPACE_LOW_THRESHOLD_CROSSEDNumber, Object> Disk free space of %d bytes for directory %s is now below low threshold of %d bytes. Backend %s is now locked down and will no longer accept any operations from clients until sufficient disk space is restored -
WARN_DISK_SPACE_FULL_THRESHOLD_CROSSED
public static LocalizableMessageDescriptor.Arg4<Number,Object, WARN_DISK_SPACE_FULL_THRESHOLD_CROSSEDNumber, Object> Disk free space of %d bytes for directory %s is now below disk low threshold of %d bytes. Backend %s is now offline and will no longer accept any operations until sufficient disk space is restored -
ERR_BACKEND_LIST_FILES_TO_BACKUP
An error occurred while trying to list the files to backup for backend '%s': %s -
ERR_IMPORT_LDIF_LACK_MEM
Insufficient free memory (%d bytes) to perform import. At least %d bytes of free memory is required -
ERR_CONFIG_INDEX_TYPE_NEEDS_MATCHING_RULE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_INDEX_TYPE_NEEDS_MATCHING_RULEIndex 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 -
ERR_ENTRYIDSORTER_NEGATIVE_START_POS
Unable to process the virtual list view request because the target start position was before the beginning of the result set -
ERR_MISSING_ID2ENTRY_RECORD
The entry database does not contain a record for ID %s -
ERR_EXECUTION_ERROR
Execution error during backend operation: %s -
ERR_CREATE_FAIL
The backend database directory could not be created: %s -
WARN_UNABLE_SET_PERMISSIONS
This platform does not support setting file permissions %s to the database directory %s -
WARN_SET_PERMISSIONS_FAILED
An error occurred while setting file permissions for the backend database directory %s: %s -
NOTE_CONFIG_DB_DIR_REQUIRES_RESTART
The change to the DB directory will not take effect until the backend is restarted. The DB files from the previous directory %s must be moved to the new directory %s after shutting down the backend to retain the existing data -
ERR_DIRECTORY_INVALID
The backend database directory '%s' is not a valid directory -
ERR_ADD_ENTRY_ALREADY_EXISTS
The entry '%s' cannot be added because an entry with that name already exists -
ERR_ADD_NO_SUCH_OBJECT
The entry '%s' cannot be added because its parent entry does not exist -
ERR_ATTRIBUTE_INDEX_NOT_CONFIGURED
There is no index configured for attribute type '%s' -
ERR_COMPSCHEMA_CANNOT_DECODE_AD_TOKEN
An error occurred while attempting to decode an attribute description token from the compressed schema definitions: %s -
ERR_COMPSCHEMA_CANNOT_DECODE_OC_TOKEN
An error occurred while attempting to decode an object class set token from the compressed schema definitions: %s -
ERR_COMPSCHEMA_CANNOT_STORE_EX
An error occurred while attempting to store compressed schema information in the database: %s -
ERR_CONFIG_VLV_INDEX_BAD_FILTER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_VLV_INDEX_BAD_FILTERObject> An error occurred while parsing the search filter %s defined for VLV index %s: %s -
ERR_CONFIG_VLV_INDEX_UNDEFINED_ATTR
Sort attribute %s for VLV index %s is not defined in the server schema -
ERR_DATABASE_EXCEPTION
Database exception: %s -
ERR_DELETE_ABORTED_BY_SUBORDINATE_PLUGIN
A plugin caused the delete operation to be aborted while deleting a subordinate entry %s -
ERR_DELETE_NOT_ALLOWED_ON_NONLEAF
The entry '%s' cannot be removed because it has subordinate entries -
ERR_DELETE_NO_SUCH_OBJECT
The entry '%s' cannot be removed because it does not exist -
ERR_ENTRY_CONTAINER_ALREADY_REGISTERED
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_ENTRY_CONTAINER_ALREADY_REGISTEREDAn entry container named '%s' is already registered for base DN '%s' -
ERR_ENTRY_DATABASE_CORRUPT
The entry database does not contain a valid record for ID %s -
ERR_EXPORT_IO_ERROR
I/O error occurred while exporting entry: %s -
ERR_IMPORT_BACKEND_ONLINE
The backend must be disabled before the import process can start -
ERR_IMPORT_CREATE_TMPDIR_ERROR
Unable to create the temporary directory %s -
ERR_IMPORT_PARENT_NOT_FOUND
The import has been aborted because the entry '%s' does not have a parent entry -
ERR_INCOMPATIBLE_ENTRY_VERSION
Entry record is not compatible with this version of the backend database. Entry version: %x -
ERR_INDEX_CORRUPT_REQUIRES_REBUILD
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 -
ERR_INVALID_PAGED_RESULTS_COOKIE
The following paged results control cookie value was not recognized: %s -
ERR_MODIFYDN_ABORTED_BY_SUBORDINATE_PLUGIN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODIFYDN_ABORTED_BY_SUBORDINATE_PLUGINA plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %s -
ERR_MODIFYDN_ALREADY_EXISTS
The entry cannot be renamed to '%s' because an entry with that name already exists -
ERR_MODIFYDN_NO_SUCH_OBJECT
The entry '%s' cannot be renamed because it does not exist -
ERR_MODIFY_NO_SUCH_OBJECT
The entry '%s' cannot be modified because it does not exist -
ERR_NEW_SUPERIOR_NO_SUCH_OBJECT
The entry cannot be moved because the new parent entry '%s' does not exist -
ERR_OPEN_ENV_FAIL
The database environment could not be opened: %s -
ERR_REBUILD_BACKEND_ONLINE
Rebuilding system index(es) must be done with the backend containing the base DN disabled -
ERR_REMOVE_FAIL
The backend database files could not be removed: %s -
ERR_SEARCH_CANNOT_MIX_PAGEDRESULTS_AND_VLV
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 -
ERR_SEARCH_CANNOT_SORT_UNINDEXED
The search results cannot be sorted because the given search request is not indexed -
ERR_SEARCH_NO_SUCH_OBJECT
The search base entry '%s' does not exist -
ERR_SEARCH_UNINDEXED_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform an unindexed search -
ERR_UNCHECKED_EXCEPTION
Unchecked exception during database transaction: %s -
ERR_VLV_INDEX_NOT_CONFIGURED
There is no VLV index configured with name '%s' -
INFO_INDEX_FILTER_INDEX_LIMIT_EXCEEDED
The filter value exceeded the index entry limit for the %s index -
INFO_INDEX_FILTER_INDEX_NOT_TRUSTED
%s index is invalid and needs to be rebuilt -
INFO_INDEX_FILTER_INDEX_TYPE_DISABLED
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_INDEX_FILTER_INDEX_TYPE_DISABLED%s index type is disabled for the %s attribute -
INFO_VERIFY_AVERAGE_REFERENCE_COUNT
Average number of entries referenced is %.2f/record -
INFO_CACHE_AND_MEMORY_REPORT
Free memory = %d MB, Cache miss rate = %.1f/record -
INFO_VERIFY_ENTRY_LIMIT_EXCEEDED_COUNT
Number of records that exceed the entry limit: %d -
INFO_VERIFY_ENTRY_LIMIT_STATS_HEADER
Statistics for records that have exceeded the entry limit: -
INFO_VERIFY_ENTRY_LIMIT_STATS_ROW
public static LocalizableMessageDescriptor.Arg5<Object,Number, INFO_VERIFY_ENTRY_LIMIT_STATS_ROWNumber, Number, Number> File %s has %d such record(s) min=%d max=%d median=%d -
INFO_VERIFY_MAX_REFERENCE_COUNT
Maximum number of entries referenced by any record is %d -
INFO_VERIFY_MULTIPLE_REFERENCE_COUNT
Number of records referencing more than one entry: %d -
NOTE_BACKEND_STARTED
The database backend %s containing %d entries has started -
NOTE_CONFIG_INDEX_ENTRY_LIMIT_REQUIRES_REBUILD
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_CONFIG_INDEX_ENTRY_LIMIT_REQUIRES_REBUILDSome index keys have already exceeded the previous index entry limit in index %s. This index must be rebuilt before it can use the new limit -
NOTE_EXPORT_FINAL_STATUS
public static LocalizableMessageDescriptor.Arg4<Number,Number, NOTE_EXPORT_FINAL_STATUSNumber, Number> Exported %d entries and skipped %d in %d seconds (average rate %.1f/sec) -
NOTE_EXPORT_PROGRESS_REPORT
Exported %d records and skipped %d (recent rate %.1f/sec) -
NOTE_IMPORT_CLOSING_DATABASE
Flushing data to disk -
NOTE_IMPORT_FINAL_STATUS
public static LocalizableMessageDescriptor.Arg6<Number,Number, NOTE_IMPORT_FINAL_STATUSNumber, Number, Number, Number> Processed %d entries, imported %d, skipped %d and rejected %d in %d seconds (average rate %.1f/sec) -
NOTE_IMPORT_LDIF_DB_MEM_BUF_INFO
Setting DB cache size to %d bytes and phase one buffer size to %d bytes -
NOTE_IMPORT_LDIF_INDEX_CLOSE
Index %s phase two processing completed -
NOTE_IMPORT_LDIF_INDEX_STARTED
public static LocalizableMessageDescriptor.Arg3<Object,Number, NOTE_IMPORT_LDIF_INDEX_STARTEDNumber> Index %s phase two started processing %d buffers in %d batches -
NOTE_IMPORT_LDIF_PHASE_TWO_REPORT
public static LocalizableMessageDescriptor.Arg6<Object,Number, NOTE_IMPORT_LDIF_PHASE_TWO_REPORTNumber, Number, Number, Number> Index %s %d%% complete: remaining = %d KB, rate = %d KB/s; batch %d/%d -
NOTE_IMPORT_LDIF_ROOTCONTAINER_CLOSE
Import LDIF environment close took %d seconds -
NOTE_IMPORT_LDIF_TOT_MEM_BUF
The amount of free memory available to the import task is %d bytes. The number of phase one buffers required is %d buffers -
NOTE_IMPORT_PHASE_STATS
Total import time was %d seconds. Phase one processing completed in %d seconds, phase two processing completed in %d seconds -
NOTE_IMPORT_PROGRESS_REPORT
public static LocalizableMessageDescriptor.Arg4<Number,Number, NOTE_IMPORT_PROGRESS_REPORTNumber, Number> Processed %d entries, skipped %d and rejected %d (recent rate %.1f/sec) -
NOTE_IMPORT_STARTING
%s starting import (build %s, R%s) -
NOTE_IMPORT_THREAD_COUNT
Import Thread Count: %d threads -
NOTE_INDEX_ADD_REQUIRES_REBUILD
Due to changes in the configuration, index %s is currently operating in a degraded state and must be rebuilt before it can be used -
NOTE_REBUILD_ALL_START
Rebuild of all indexes started with %d total entries to process -
NOTE_REBUILD_CLEARDEGRADEDSTATE_FINAL_STATUS
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_REBUILD_CLEARDEGRADEDSTATE_FINAL_STATUSDegraded state of index(es) %s has been cleared -
NOTE_REBUILD_DEGRADED_START
Rebuild of all degraded indexes started with %d total entries to process -
NOTE_REBUILD_FINAL_STATUS
Rebuild complete. Processed %d entries in %d seconds (average rate %.1f/sec) -
NOTE_REBUILD_PROGRESS_REPORT
public static LocalizableMessageDescriptor.Arg4<Number,Number, NOTE_REBUILD_PROGRESS_REPORTNumber, Number> %.1f%% Completed. Processed %d/%d entries. (recent rate %.1f/sec) -
NOTE_REBUILD_START
Rebuild of index(es) %s started with %d total entries to process -
NOTE_REFERRAL_RESULT_MESSAGE
A referral entry %s indicates that the operation must be processed at a different server -
NOTE_VERIFY_CLEAN_FINAL_STATUS
public static LocalizableMessageDescriptor.Arg4<Number,Number, NOTE_VERIFY_CLEAN_FINAL_STATUSNumber, Number> Checked %d records and found %d error(s) in %d seconds (average rate %.1f/sec) -
NOTE_VERIFY_FINAL_STATUS
public static LocalizableMessageDescriptor.Arg4<Number,Number, NOTE_VERIFY_FINAL_STATUSNumber, Number> Checked %d entries and found %d error(s) in %d seconds (average rate %.1f/sec) -
NOTE_VERIFY_PROGRESS_REPORT
public static LocalizableMessageDescriptor.Arg4<Number,Number, NOTE_VERIFY_PROGRESS_REPORTNumber, Number> Processed %d out of %d records and found %d error(s) (recent rate %.1f/sec) -
WARN_FUNCTION_NOT_SUPPORTED
The requested operation is not supported by this backend -
WARN_GET_ENTRY_COUNT_FAILED
Unable to determine the total number of entries in the container: %s -
ERR_JEB_INVALID_LOGGING_LEVEL
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 -
ERR_CONFIG_JEB_CACHE_SIZE_TOO_SMALL
Configuration attribute ds-cfg-db-cache-size has a value of %d which is less than the minimum: %d -
ERR_VERIFY_MISSING_ID
Missing ID %d%n%s -
ERR_VERIFY_UNKNOWN_ID
Reference to unknown entry ID %s%n%s -
ERR_VERIFY_ENTRY_NON_MATCHING_KEY
The entry with ID %s is associated with the wrong key%n%s -
ERR_VERIFY_EMPTY_IDSET
Empty ID set: %n%s -
ERR_VERIFY_DUPLICATE_REFERENCE
Duplicate reference to ID %d%n%s -
ERR_VERIFY_UNKNOWN_REFERENCE
Reference to unknown ID %d%n%s -
ERR_VERIFY_UNEXPECTED_REFERENCE
Reference to entry <%s> which does not match the value%n%s -
ERR_VERIFY_DN2ID_MISSING_KEY
File dn2id is missing key %s -
ERR_VERIFY_DN2ID_WRONG_ID
File dn2id has ID %d instead of %d for key %s -
ERR_VERIFY_DN2ID_UNKNOWN_ID
File dn2id has DN <%s> referencing unknown ID %d -
ERR_VERIFY_DN2ID_WRONG_ENTRY
File dn2id has DN <%s> referencing entry with wrong DN <%s> -
ERR_VERIFY_WRONG_ENTRY_COUNT
The stored entry count in id2entry (%d) does not agree with the actual number of entry records found (%d) -
ERR_VERIFY_ID2COUNT_WRONG_COUNT
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_VERIFY_ID2COUNT_WRONG_COUNTNumber> File id2childrenCount has wrong number of children for DN <%s> (got %d, expecting %d) -
ERR_VERIFY_ID2COUNT_WRONG_ID
File id2ChildrenCount references non-existing EntryID <%d> -
NOTE_REBUILD_NOTHING_TO_REBUILD
Rebuilding index finished: no indexes to rebuild -
NOTE_IMPORT_LDIF_OFFHEAP_MEM_BUF_INFO
public static LocalizableMessageDescriptor.Arg4<Number,Number, NOTE_IMPORT_LDIF_OFFHEAP_MEM_BUF_INFONumber, Number> Setting DB cache size to %d MB. Using %d mb off-heap memory through %d phase one buffers of %d KB -
ERR_SCHEMA_PARSE_LINE
Ignoring schema definition '%s' because the following error occurred while it was being parsed: %s -
ERR_SCHEMA_COULD_NOT_PARSE_DEFINITION
Schema definition could not be parsed as valid attribute value -
ERR_CLEARTEXT_BACKEND_FOR_INDEX_CONFIDENTIALITY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CLEARTEXT_BACKEND_FOR_INDEX_CONFIDENTIALITYAttribute %s is set as confidential on a backend whose entries are still cleartext. Enable confidentiality on the backend first -
ERR_CONFIG_INDEX_CANNOT_PROTECT_BOTH
The attribute '%s' cannot enable confidentiality for keys and values at the same time -
ERR_CANNOT_ENCODE_ENTRY
Cannot encode entry for writing on storage: %s -
ERR_CANNOT_DECODE_ENTRY
Input stream ended unexpectedly while decoding entry -
ERR_BACKEND_CANNOT_CHANGE_CONFIDENTIALITY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_BACKEND_CANNOT_CHANGE_CONFIDENTIALITYConfidentiality cannot be disabled on suffix '%s' because the following indexes have confidentiality still enabled: %s -
NOTE_CONFIG_INDEX_CONFIDENTIALITY_REQUIRES_REBUILD
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_CONFIG_INDEX_CONFIDENTIALITY_REQUIRES_REBUILDChanging confidentiality for index '%s' requires the index to be rebuilt before it can be used again -
ERR_BACKEND_FAULTY_CRYPTO_TRANSFORMATION
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_BACKEND_FAULTY_CRYPTO_TRANSFORMATIONObject> Error while enabling confidentiality with cipher %s, %d bits: %s -
ERR_IMPORT_DUPLICATE_ENTRY
The import has been aborted because the data to be imported contains duplicate copies of entry '%s' -
ERR_PROXY_CANNOT_DISCOVER_REMOTE_CAPABILITIES
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PROXY_CANNOT_DISCOVER_REMOTE_CAPABILITIESProxy backend '%s' could not discover remote servers capabilities: %s -
INFO_PROXY_FAILOVER_EFFECTIVE
public static LocalizableMessageDescriptor.Arg4<Object,Object, INFO_PROXY_FAILOVER_EFFECTIVEObject, Object> Proxy backend '%s' successfully configured failover via the service discovery mechanism '%s': primary servers are %s and secondary servers are %s -
WARN_PROXY_NO_FAILOVER_ONLY_PRIMARY_SERVERS_DISCOVERED
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_PROXY_NO_FAILOVER_ONLY_PRIMARY_SERVERS_DISCOVEREDObject> Proxy backend '%s' cannot failover: only primary servers have been discovered via the service discovery mechanism '%s'. Primary servers are %s -
WARN_PROXY_NO_FAILOVER_ONLY_SECONDARY_SERVERS_DISCOVERED
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_PROXY_NO_FAILOVER_ONLY_SECONDARY_SERVERS_DISCOVEREDObject> Proxy backend '%s' cannot failover: only secondary servers have been discovered via the service discovery mechanism '%s'. Secondary servers are %s -
ERR_PROXY_NO_PRIMARY_NOR_SECONDARY_SERVERS_DISCOVERED
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PROXY_NO_PRIMARY_NOR_SECONDARY_SERVERS_DISCOVEREDProxy backend '%s' is non functional because it could not find any primary nor secondary servers via the service discovery mechanism '%s' -
ERR_PROXY_UNKNOWN_SERVICE_DISCOVERY
Proxy backend '%s' cannot find the configured service discovery mechanism '%s' -
NOTE_PROXY_CONNECTION_OPTIONS_CHANGED
Connection options have changed for the proxy backend '%s'. The existing connections are being closed immediately. New ones are being opened -
NOTE_PROXY_CONNECTION_POOL_OPTIONS_CHANGED
Connection pool options have changed for the proxy backend '%s'. The existing connections are being closed and re-opened -
NOTE_PROXY_SERVICE_DISCOVERY_CHANGED
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_PROXY_SERVICE_DISCOVERY_CHANGEDObject> Service discovery mechanism has changed from '%s' to '%s' for proxy backend '%s'. The existing connections are being closed immediately -
NOTE_PROXY_REMOTE_SERVERS_CHANGED
public static LocalizableMessageDescriptor.Arg5<Object,Object, NOTE_PROXY_REMOTE_SERVERS_CHANGEDObject, Object, Object> Remote servers changed for the proxy backend '%s'. The proxy was using: primary servers=%s, secondary servers=%s; and it will now be using: primary servers=%s, secondary servers=%s -
INFO_PROXY_BASE_DNS_REGISTRATION_CHANGE
public static LocalizableMessageDescriptor.Arg3<Object,Object, INFO_PROXY_BASE_DNS_REGISTRATION_CHANGEObject> Proxy backend '%s' automatically registered itself against the base DNs %s. It was previously registered against the base DNs %s -
ERR_NO_BACKEND_FOUND_FOR_BASE_DN
No backend is associated with the base DN '%s' -
ERR_PROXY_BACKEND_CANNOT_USE_BASE_DN_ALREADY_IN_USE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PROXY_BACKEND_CANNOT_USE_BASE_DN_ALREADY_IN_USEObject> Proxy backend '%s' cannot register itself against base DN %s because this base DN is already registered against backend '%s' -
ERR_LOCAL_BACKEND_TAKES_PRECEDENCE_OVER_PROXY_BACKEND
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LOCAL_BACKEND_TAKES_PRECEDENCE_OVER_PROXY_BACKENDObject> 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 -
INFO_LDIF_BACKEND_VISIBILITY_CHANGED
The change to the LDIF backend visibility will not take effect until the backend is disabled and re-enabled -
INFO_PROXY_PRIMARY_SERVERS_AVAILABLE
The primary servers for proxy backend '%s' are now available and will be used for proxying requests -
INFO_PROXY_SECONDARY_SERVERS_AVAILABLE
The secondary servers for proxy backend '%s' are now available and will be used if the primary servers are unavailable -
WARN_PROXY_PRIMARY_SERVERS_UNAVAILABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_PROXY_PRIMARY_SERVERS_UNAVAILABLEThe primary servers for proxy backend '%s' are unavailable. The secondary servers, if available, will be used for processing requests until the primary servers become available again. The last failure that prevented the primary servers from being used was: %s -
WARN_PROXY_SECONDARY_SERVERS_UNAVAILABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_PROXY_SECONDARY_SERVERS_UNAVAILABLEThe secondary servers for proxy backend '%s' are unavailable. If the primary servers are unavailable, or become unavailable, then it will no longer be possible to proxy requests. The last failure that prevented the secondary servers from being used was: %s -
INFO_PROXY_SERVER_AVAILABLE
The server '%s' for proxy backend '%s' is available and will be used for proxying requests -
WARN_PROXY_SERVER_UNAVAILABLE
The server '%s' for proxy backend '%s' is unavailable. The last failure that prevented the server from being used was: %s -
ERR_PROXY_PARTITION_BASE_DN_MUST_BE_SUBORDINATES
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PROXY_PARTITION_BASE_DN_MUST_BE_SUBORDINATESObject> The partition base DN '%s' should be subordinate to one of the base DNs %s of proxy backend '%s' -
ERR_CACHE_PRELOAD_NOT_SUPPORTED
Backend database cache preload for backend '%s' is not supported in this release -
INFO_PROXY_DISCOVERY_RECONFIGURATION_IN_PROGRESS
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_PROXY_DISCOVERY_RECONFIGURATION_IN_PROGRESSConfiguration of proxy backend '%s' with service discovery mechanism '%s' is in progress. Requests will not be proxied until configuration completes -
WARN_UNINDEXED_INTERNAL_SEARCH
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_UNINDEXED_INTERNAL_SEARCHObject> The server is performing an unindexed internal search request with base DN '%s', scope '%s', and filter '%s'. Unindexed internal searches are usually unexpected and could impact performance. Please verify that this backend's indexes are configured correctly for these search parameters -
PROXY_DIAGNOSTIC_MESSAGE_WITH_CLIENT_SIDE_RESULT_CODE
public static LocalizableMessageDescriptor.Arg2<Object,Object> PROXY_DIAGNOSTIC_MESSAGE_WITH_CLIENT_SIDE_RESULT_CODEInitial result code was '%s', with diagnostic message: %s -
ERR_NOT_ENOUGH_RESOURCES
There are insufficient resources to perform the operation -
ERR_CONFIG_INDEX_TTL_ORDERING_GENERALIZED_TIME
The time-to-live (TTL) feature can only be enabled for generalized time ordering indexes -
ERR_UNABLE_TO_PURGE_ENTRIES
An unexpected error occurred while purging expired entries: %s -
WARN_TTL_INDEX_OVER_INDEX_ENTRY_LIMIT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_TTL_INDEX_OVER_INDEX_ENTRY_LIMITUnable to locate all expired entries on backend '%s' because the ttl-enabled index '%s' has reached the configured index-entry-limit -
ERR_PROXY_PARTITION_BASE_DN_MUST_NOT_BE_SUBORDINATES
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PROXY_PARTITION_BASE_DN_MUST_NOT_BE_SUBORDINATESObject> The partition base DN '%s' shouldn't be subordinate to one of the other partition base DNs %s of proxy backend '%s' -
WARN_PROXY_WILL_IGNORE_SERVERS
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_PROXY_WILL_IGNORE_SERVERSObject, Object> The proxy backend '%s' will ignore the discovered servers '%s' from shard '%s' because they do not expose the required base DNs '%s' -
WARN_CANNOT_PARSE_ENV_VARIABLE_FOR_SMALL_DB_SIZE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_CANNOT_PARSE_ENV_VARIABLE_FOR_SMALL_DB_SIZEObject> Property '%s' contains value '%s' which cannot be parsed as a long. Defaulting to '%s' bytes for small DB size -
ERR_KEYMANAGERS_COULD_NOT_BE_RETRIEVED
An error occurred while trying to retrieve the key managers from the key manager provider `%s` -
ERR_EXPORT_LDIF_FORCE_STOP_THREADS
Could not stop export-ldif threads after 30 seconds. Now forcing stop by interrupting them -
WARN_BACKUP_FS_DOES_NOT_SUPPORT_LAST_MODIFIED
public static LocalizableMessageDescriptor.Arg1<Object> WARN_BACKUP_FS_DOES_NOT_SUPPORT_LAST_MODIFIEDThe file system used by '%s' backend does not support last file modification time. Backups will still work but will take longer and consume more space in the backup storage -
ERR_REINDEX_CANNOT_LOCK_ENTRY
The index(es) cannot be rebuilt because the server failed to obtain a write lock for the entry '%s' after multiple attempts -
ERR_CONFIG_VLV_INDEX_MISSING_SORT_KEY
VLV index '%s' must be configured with at least one sort attribute -
ERR_VERIFY_MISSING_ENTRY
Missing entry %s in index %s -
ERR_CONFIG_BIG_INDEX_EQUALITY_MATCHING_RULE_REQUIRED
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_BIG_INDEX_EQUALITY_MATCHING_RULE_REQUIREDBig index for attribute '%s' cannot be created for matching rule '%s' because it is not an equality matching rule -
WARN_NON_ATOMIC_SUBTREE_DELETE
The subtree delete against '%s' is being performed non-atomically because it is deleting more than %s subordinate entries. To prevent inconsistency across replicas, the client must retry this same delete operation until it succeeds -
ERR_SORT_CONTROL_REQUIRED_WITH_VLV
A Server Side Sort control must be specified whenever a Virtual List View control is present -
ERR_VERIFY_BIGINDEX_COUNT_WRONG_COUNT
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_VERIFY_BIGINDEX_COUNT_WRONG_COUNTNumber, Number> Counter of %s reports wrong number of entries for key <%s> (got %d, expecting %d) -
ERR_TASKSCHED_CANNOT_SEND_TASK_COMPLETED_EMAIL
public static LocalizableMessageDescriptor.Arg7<Object,Object, ERR_TASKSCHED_CANNOT_SEND_TASK_COMPLETED_EMAILObject, Object, Object, Object, Object> 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 -
ERR_CONFIG_INVALID_BIG_INDEX_INCLUDED_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_INVALID_BIG_INDEX_INCLUDED_VALUEObject> 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 -
ERR_SEARCH_CANNOT_USE_VLV_UNINDEXED
The VLV request cannot be processed because the search is not indexed. Configure a VLV index matching the request -
NOTE_UNNECESSARY_PRESENCE_INDEX
Both equality and presence index types are defined for attribute '%s'. When no presence index exists, presence search filters are processed using the equality index. Therefore, consider deleting the presence index for attribute '%s' -
ERR_INTERNAL_ERROR_WITH_EXCEPTION
An internal error occurred when accessing backend '%s': %s -
ERR_INTERNAL_ERROR_WITHOUT_EXCEPTION
An internal error was detected when accessing backend '%s' -
DSBACKUP_BACKUP_STARTS
Starting backup for backend '%s' -
DSBACKUP_RESTORE_STARTS
Starting restore for backend '%s' with backup ID '%s' -
DSBACKUP_BACKUP_SUCCESSFUL
Backup completed for backend '%s' with backup ID '%s' -
DSBACKUP_RESTORE_SUCCESSFUL
Restore completed for backend '%s' with backup ID '%s' -
DSBACKUP_ERROR_DURING_BACKUP
An error occurred while attempting to backup backend '%s': %s -
DSBACKUP_BACKUP_COMPLETED_WITH_ERROR
The backup process failed with one or more errors -
DSBACKUP_RESTORE_COMPLETED_WITH_ERROR
The restore process failed with one or more errors -
DSBACKUP_ERROR_DURING_RESTORE
An error occurred while attempting to restore backend '%s' with backup ID '%s': %s -
DSBACKUP_CREATE_FOUND_NO_BACKEND
There are no enabled backends that support backup operation -
DSBACKUP_CREATE_INTERRUPTED
The backup command was interrupted -
DSBACKUP_CANNOT_READ_BACKUP_DIRECTORY_CONTENT
public static LocalizableMessageDescriptor.Arg1<Object> DSBACKUP_CANNOT_READ_BACKUP_DIRECTORY_CONTENTCannot read backup directory content: %s -
DSBACKUP_NEW_FILES_FOUND
Backup still in progress, new files have been created -
DSBACKUP_BACKUP_PROGRESS_STATUS
public static LocalizableMessageDescriptor.Arg3<Number,Number, DSBACKUP_BACKUP_PROGRESS_STATUSObject> Backing up file (%d/%d) '%s' -
DSBACKUP_VERIFY_PROGRESS_STATUS
public static LocalizableMessageDescriptor.Arg3<Number,Number, DSBACKUP_VERIFY_PROGRESS_STATUSObject> Verifying file (%d/%d) '%s' -
DSBACKUP_RESTORE_PROGRESS_STATUS
public static LocalizableMessageDescriptor.Arg3<Number,Number, DSBACKUP_RESTORE_PROGRESS_STATUSObject> Restoring file (%d/%d) '%s' -
DSBACKUP_PURGE_PROGRESS_STATUS
public static LocalizableMessageDescriptor.Arg3<Number,Number, DSBACKUP_PURGE_PROGRESS_STATUSObject> Purging backup (%d/%d) '%s' -
DSBACKUP_CREATE_REQUESTED_BACKENDS_NOT_ENABLED
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_CREATE_REQUESTED_BACKENDS_NOT_ENABLEDThe following backends do not exist or are disabled: %s. Here is the list of enabled backends that support backups: %s -
DSBACKUP_CREATE_REQUESTED_BACKENDS_DO_NOT_SUPPORT_BACKUP
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_CREATE_REQUESTED_BACKENDS_DO_NOT_SUPPORT_BACKUPThe following backends do not support backups: %s. Here is the list of enabled backends that support backups: %s -
DSBACKUP_RESTORE_NO_BACKENDS_WITH_NAME
The backends %s cannot be restored because they do not exist or are disabled -
DSBACKUP_BACKUPS_DO_NOT_EXIST
Cannot find backup with ID %s -
DSBACKUP_CANNOT_FIND_BACKUP_FOR_BACKENDS
There are no backups for backends %s -
DSBACKUP_CANNOT_RESTORE_ONLINE
The backends %s cannot be restored while the server is running. Please stop the server first and try again with the --offline option -
DSBACKUP_DIRECTORY_INVALID_NAME
'%s' is not a valid name for a directory -
DSBACKUP_RESTORE_AMBIGUOUS_BACKUP_ID
Found backup IDs that correspond to the same backend name: %s. Make sure each backup ID corresponds to a distinct backend -
DSBACKUP_BACKEND_NAME_OR_BACKUP_ID_ARG_MISSING
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_BACKEND_NAME_OR_BACKUP_ID_ARG_MISSINGEither the --%s or --%s argument must be provided -
DSBACKUP_CANNOT_DELETE_CORRUPTED_FILE
Cannot delete corrupted file '%s' -
DSBACKUP_CLEANUP_BACKEND_DIRECTORY
Deleting corrupted file from backend directory -
DSBACKUP_CLEANUP_BACKUP_STORAGE
Deleting corrupted file from backup storage -
DSBACKUP_MAC_DOES_NOT_MATCH
signature does not match -
DSBACKUP_UNEXPECTED_CONTENT
unexpected content -
DSBACKUP_IO_EXCEPTION_WITH_FILE
Problem with file '%s' : %s -
DSBACKUP_IO_EXCEPTION
IO error: %s -
DSBACKUP_OPERATION_INTERRUPTED
Operation was interrupted -
DSBACKUP_FILE_IS_CORRUPTED
File '%s' is corrupted: %s -
DSBACKUP_FILE_IS_MISSING
File '%s' is missing -
DSBACKUP_DIRECTORY_DOES_NOT_EXIST
The directory does not exist -
DSBACKUP_DIRECTORY_IS_NOT_A_DIRECTORY
Not a directory -
DSBACKUP_CANNOT_READ_BACKEND_FILES
Cannot read backend files in directory '%s': %s -
DSBACKUP_CANNOT_DELETE_BACKEND_FILES
Cannot delete backend files from directory '%s': %s -
DSBACKUP_BACKEND_FILES_REMOVED_AFTER_RESTORE_FAILURE
public static LocalizableMessageDescriptor.Arg1<Object> DSBACKUP_BACKEND_FILES_REMOVED_AFTER_RESTORE_FAILUREThe '%s' backend files have been removed after restore failed. The backend is now empty -
DSBACKUP_CANNOT_CREATE_BACKEND_DIRECTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_CANNOT_CREATE_BACKEND_DIRECTORYCannot create the backend directory '%s' before restoring: %s -
DSBACKUP_CANNOT_CLEAN_BACKEND_DIRECTORY_AFTER_RESTORED_FAILED
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_CANNOT_CLEAN_BACKEND_DIRECTORY_AFTER_RESTORED_FAILEDThe attempt to remove backend files from directory '%s' has failed, backend '%s' may contain corrupted data, please remove the files manually -
DSBACKUP_BACKUP_ID_ALREADY_EXISTS
The backup ID '%s' already exists -
DSBACKUP_CANNOT_COMPUTE_BACKEND_FILE_FINGERPRINT
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_CANNOT_COMPUTE_BACKEND_FILE_FINGERPRINTCannot compute the fingerprint for backend file '%s': %s -
DSBACKUP_UNABLE_TO_ACCESS_BACKUP_STORAGE
Unable to access the backup storage: %s -
DS_BACKUP_PLUGIN_NOT_FOUND
No plugin found to handle the storage scheme '%s' -
DSBACKUP_CANNOT_DELETE_LOCK_FILE
Cannot delete the backup lock file '%s', please remove this file manually: %s -
DSBACKUP_CREATE_CANNOT_LOCK_BACKEND
Cannot 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) -
DSBACKUP_CREATE_CANNOT_UNLOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_CREATE_CANNOT_UNLOCK_BACKENDCannot release the shared lock for backend '%s': %s. This lock should automatically be cleared when the backup process exits, so no further action should be required -
DSBACKUP_RESTORE_CANNOT_LOCK_BACKEND
Cannot 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) -
DSBACKUP_RESTORE_CANNOT_UNLOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_RESTORE_CANNOT_UNLOCK_BACKENDCannot release the exclusive lock for backend '%s': %s. This lock should automatically be cleared when the restore process exits, so no further action should be required -
DSBACKUP_RESTORE_WARN_CANNOT_ACTIVATE_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_RESTORE_WARN_CANNOT_ACTIVATE_BACKENDCannot enable backend '%s' after restoring: %s -
DSBACKUP_LIST_BACKUP_ID
Backup ID: %s -
DSBACKUP_LIST_DATE
Backup Date: %s -
DSBACKUP_LIST_BACKEND_NAME
Backend name: %s -
DSBACKUP_LIST_SERVER_ID
Server ID: %s -
DSBACKUP_LIST_STATUS
Status: %s -
DSBACKUP_LIST_ERROR
Error: %s -
DSBACKUP_LIST_VERIFIED
Verified -
DSBACKUP_LIST_BAD
Bad -
DSBACKUP_LIST_NUMBER_OF_BACKUPS_WITH_REQUESTED_PROPERTIES
public static LocalizableMessageDescriptor.Arg1<Object> DSBACKUP_LIST_NUMBER_OF_BACKUPS_WITH_REQUESTED_PROPERTIESFound %s backup(s) with the requested characteristics -
DSBACKUP_LIST_NO_BACKUPS_WITH_REQUESTED_PROPERTIES
There are no backups with the requested characteristics -
DSBACKUP_LIST_BACKUPS_CANNOT_BE_RESTORED
%s backup(s) cannot be restored -
DSBACKUP_LIST_ERROR_UNIDENTIFIED_BACKUPS
Found %s backup(s) that cannot be fully identified due to the following error(s): -
DSBACKUP_DESCRIPTION
Backup and restore backends, manage backup files -
DSBACKUP_DESCRIPTION_SHORT
Backup and restore backends -
DSBACKUP_LOCATION_PLACEHOLDER
{backup location} -
DSBACKUP_OFFLINE_DESCRIPTION_WARNING_RESTORE
Indicates that the command will operate independently of the server process. It will run regardless of whether the server is started or stopped. When using this option with the %1$s sub-command, the server must be stopped; also as the command will write to server files, you should run the command as a user having the same filesystem permissions as the user running the server. Using this option with the %2$s sub-command when the server is running is possible and supported. With JE Backends, the integrity of the backup is ensured by the process. With LDIF backends, avoid simultaneous changes to the backends -
DSBACKUP_BACKUP_LOCATION_DESC_FOR_WRITING
Backup file-system path or URI for alternative storage mechanisms. File-system paths may be expressed as absolute or relative paths and are resolved relative to the current working directory when the tool is run in offline mode, or relative to the server instance directory when the tool is run in task mode. Read the documentation for further information regarding alternative backup storage mechanisms -
DSBACKUP_BACKUP_LOCATION_DESC_FOR_READING
Location containing backups: file-system path or URI for alternative storage mechanisms. File-system paths may be expressed as absolute or relative paths and are resolved relative to the current working directory when the tool is run in offline mode, or relative to the server instance directory when the tool is run in task mode. Read the documentation for further information regarding alternative backup storage mechanisms -
DSBACKUP_STORAGE_PROPERTY_PLACEHOLDER
{PROP:VALUE} -
DSBACKUP_STORAGE_PROPERTY_DESCRIPTION
Assigns a value to a storage property where PROP is the name of the property and VALUE is the single value to be assigned. Specify the same property multiple times in order to assign more than one value to it -
DSBACKUP_LIST_DESCRIPTION
List the backups at the specified location -
DSBACKUP_LIST_BACKEND_NAME_DESCRIPTION
Show only backups taken from the provided backend -
DSBACKUP_LIST_SERVER_ID_DESCRIPTION
Show only backups taken from the provided server -
DSBACKUP_LIST_SERVER_ID_PLACEHOLDER
{server ID} -
DSBACKUP_LIST_LAST_DESCRIPTION
Show only the last backup for each backend -
DSBCAKUP_LIST_VERIFY_DESCRIPTION
Verify backups completeness, integrity and whether they can be decrypted -
DSBACKUP_CREATE_DESCRIPTION
Take encrypted and signed backups of individual backends and send them to the desired location -
DSBACKUP_CREATE_BACKEND_NAME_DESC
The name of the backend to back up. Specify this option multiple times to backup multiple backends or skip this option to backup all the enabled backends that support backups -
DSBACKUP_BACKUP_ID_PLACEHOLDER
{backup ID} -
DSBACKUP_RESTORE_DESCRIPTION
Restore one or more backends. In order to decrypt and verify signatures on backup files, the server must have access to the master key pair used to encrypt and sign the files when they were created -
DSBACKUP_RESTORE_BACKUP_ID_DESCRIPTION
Restore the backup having the provided ID. Specify this option multiple times to restore multiple backends -
DSBACKUP_RESTORE_BACKEND_NAME_DESCRIPTION
Restore the last backup of the provided backend. Specify this option multiple times to restore multiple backends -
DSBACKUP_PURGE_DESCRIPTION
Delete one or more backups -
DSBACKUP_PURGE_BACKUP_ID_DESCRIPTION
The ID of the backup that should be deleted. Specify this option multiple times to purge multiple backups -
DSBACKUP_PURGE_AT_LEAST_ONE_ARG_PRESENT
At least one of these options must be declared: %s -
DSBACKUP_PURGE_ARG_CAN_ONLY_BE_USED_WITH_OTHER_ARG
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_PURGE_ARG_CAN_ONLY_BE_USED_WITH_OTHER_ARGThe option '--%s' can only be used with the option '--%s' -
DSBACKUP_PURGE_KEEP_COUNT_PLACEHOLDER
{number of backups} -
DSBACKUP_PURGE_KEEP_COUNT_DESCRIPTION
The number of backups to keep per backend. Use this option to keep the n latest backups of each backend and delete the others. If n=0, all the backups will be removed -
DSBACKUP_PURGE_OLDER_THAN_PLACEHOLDER
{duration} -
DSBACKUP_PURGE_OLDER_THAN_DESCRIPTION
Delete backups that are older than the provided duration. The latest backup of each backend will always be kept unless the '--%s' option is also provided. Duration examples: '12 hours', '3 days', '1y' -
DSBACKUP_PURGE_FORCE_OLDER_THAN_DESCRIPTION
Must be used with the '--%s' option, indicates that the last backup of each backend can be deleted if older than the provided duration -
DSBACKUP_PURGE_BACKEND_NAME_PLACEHOLDER
{backend name} -
DSBACKUP_PURGE_BACKEND_NAME_DESCRIPTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_PURGE_BACKEND_NAME_DESCRIPTIONPurge only backups of the specified backend. Specify this option multiple times to allow purging backups of different backends. Skip this option to allow purging backups of all backends. This can only be used with options '--%s' or '--%s' -
DSBACKUP_PURGE_KEEPCOUNT_ARG_ILLEGAL_VALUE
'%d' is not allowed: the value must be equal or greater than 0 -
DSBACKUP_PURGE_KEEPCOUNT_ARG_EXCEPTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_PURGE_KEEPCOUNT_ARG_EXCEPTIONInvalid value for '%s': %s -
DSBACKUP_PURGE_ERROR
An error occurred while attempting to purge the backup '%s': %s -
DSBACKUP_PURGE_BACKEND_FILES_ERROR
An error occurred while attempting to purge backup files starting with '%s': %s -
DSBACKUP_PURGE_COMPLETED_WITH_ERROR
Backup purge process failed with one or more errors -
DSBACKUP_PURGE_SUCCESSFUL
Purge completed successfully -
DSBACKUP_STORAGE_PROPERTY_ARG_ONLY_ONE_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> DSBACKUP_STORAGE_PROPERTY_ARG_ONLY_ONE_VALUEThe storage property '%s' has several values while it can have only one. The provided properties string was: "%s" -
ERR_INVALID_BACKUP_ID_NO_UNDERSCORE
Backup id '%s' is invalid: expected to find an underscore in it -
ERR_INVALID_BACKUP_ID_CANNOT_PARSE_TIMESTAMP
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_INVALID_BACKUP_ID_CANNOT_PARSE_TIMESTAMPBackup id '%s' is invalid: cannot parse '%s' as a timestamp -
DSBACKUP_ACCESS_DENIED
Access denied to file '%s' -
ERR_FILE_CREDENTIALS_NOT_FOUND
Credential file '%s' not found -
ERR_FILE_CREDENTIALS_FAILED_TO_PARSE
Failed to parse the credential file '%s' -
ERR_INITIALIZE_PLUGIN
Invalid plugin type '%s', a backup plugin must be of type '%s' -
ERR_CREDENTIALS_ISSUE
A problem occurred while connecting to cloud provider '%s' using the provided credentials: %s -
ERR_ENV_VAR_PROPERTY_VALUE_NOT_FOUND
No value found for property '%s' -
ERR_ENV_VAR_VALUE_NOT_FOUND
No environment value '%s' found for property '%s'. If you are running the tool in offline mode, make sure the command has access to this variable, or else make sure the directory server has access to it -
ERR_NO_CLOUD_FILE_FOUND
Could not find file '%s' in cloud bucket '%s' -
ERR_UPLOAD_UNKNOWN_HOST
An error occurred while uploading the file to the cloud storage: the host '%s' is an unknown host -
ERR_UPLOAD_CLOUD_PROVIDER_MESSAGE
An error occurred while uploading the file to the cloud storage. The cloud provider returned the following error message: '%s' -
ERR_CONFIG_ATTR_INVALID_BOOLEAN_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_ATTR_INVALID_BOOLEAN_VALUEUnable to set the value for Boolean configuration attribute %s because the provided value %s was not either 'true' or 'false' -
ERR_CONFIG_ATTR_INVALID_INT_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_ATTR_INVALID_INT_VALUEObject> Unable to set the value for integer configuration attribute %s because the provided value %s cannot be interpreted as an integer value: %s -
ERR_CONFIG_ATTR_INT_BELOW_LOWER_BOUND
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_CONFIG_ATTR_INT_BELOW_LOWER_BOUNDNumber> Unable to set the value for configuration attribute %s because the provided value %d is less than the lowest allowed value of %d -
ERR_CONFIG_ATTR_INT_ABOVE_UPPER_BOUND
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_CONFIG_ATTR_INT_ABOVE_UPPER_BOUNDNumber> Unable to set the value for configuration attribute %s because the provided value %d is greater than the largest allowed value of %d -
ERR_CONFIG_FILE_DOES_NOT_EXIST
The specified configuration file %s does not exist or is not readable -
ERR_CONFIG_FILE_CANNOT_OPEN_FOR_READ
An error occurred while attempting to open the configuration file %s for reading: %s -
ERR_CONFIG_FILE_INVALID_BASE_DN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_FILE_INVALID_BASE_DNObject> 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 -
ERR_CONFIG_FILE_GENERIC_ERROR
An unexpected error occurred while attempting to process the Directory Server configuration file %s: %s -
ERR_CONFIG_CANNOT_DETERMINE_SERVER_ROOT
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 -
ERR_CONFIG_FILE_WRITE_ERROR
An unexpected error occurred while trying to write configuration entry %s to LDIF: %s -
ERR_CONFIG_FILE_UNWILLING_TO_IMPORT
The Directory Server configuration may not be altered by importing a new configuration from LDIF -
WARN_CONFIG_LOGGER_NO_ACTIVE_ACCESS_LOGGERS
There are no active access loggers defined in the Directory Server configuration. No access logging will be performed -
WARN_CONFIG_LOGGER_NO_ACTIVE_ERROR_LOGGERS
There are no active error loggers defined in the Directory Server configuration. No error logging will be performed -
ERR_CONFIG_LOGGER_CANNOT_CREATE_LOGGER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_LOGGER_CANNOT_CREATE_LOGGERAn error occurred while attempting to create a Directory Server logger from the information in configuration entry %s: %s -
ERR_CONFIG_LOGGER_INVALID_OBJECTCLASS
Configuration entry %s does not contain a valid objectclass for a Directory Server access, error, or debug logger definition -
ERR_CONFIG_LOGGER_INVALID_ACCESS_LOGGER_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_LOGGER_INVALID_ACCESS_LOGGER_CLASSObject> Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server access logger: %s -
ERR_CONFIG_LOGGER_INVALID_ERROR_LOGGER_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_LOGGER_INVALID_ERROR_LOGGER_CLASSObject> Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server error logger: %s -
ERR_CONFIG_LOGGER_INVALID_DEBUG_LOGGER_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_LOGGER_INVALID_DEBUG_LOGGER_CLASSObject> Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server debug logger: %s -
ERR_CONFIG_JMX_ATTR_NO_ATTR
Configuration entry %s does not contain attribute %s (or that attribute exists but is not accessible using JMX) -
ERR_CONFIG_JMX_NO_METHOD
There is no method %s for any invokable component registered with configuration entry %s -
ERR_CONFIG_JMX_CANNOT_REGISTER_MBEAN
The Directory Server could not register a JMX MBean for the component associated with configuration entry %s: %s -
ERR_CONFIG_LDIF_WRITE_ERROR
An unexpected error occurred while trying to export the Directory Server configuration to LDIF: %s -
ERR_CONFIG_WORK_QUEUE_TOO_MANY_FAILURES
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_CONFIG_WORK_QUEUE_TOO_MANY_FAILURESNumber> 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 -
ERR_CONFIG_CANNOT_REGISTER_AS_PRIVATE_SUFFIX
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_CANNOT_REGISTER_AS_PRIVATE_SUFFIXAn unexpected error occurred while trying to register the configuration handler base DN "%s" as a private suffix with the Directory Server: %s -
ERR_CONFIG_BACKEND_BASE_DOES_NOT_EXIST
The entry cn=Backends,cn=config does not appear to exist in the Directory Server configuration. This is a required entry -
INFO_CONFIG_BACKEND_DISABLED
The backend defined in configuration entry %s is marked as disabled and therefore will not be used -
ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_ENABLED_STATE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_ENABLED_STATEAn 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 -
ERR_CONFIG_BACKEND_CANNOT_INSTANTIATE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_BACKEND_CANNOT_INSTANTIATEObject> 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 -
ERR_CONFIG_BACKEND_CANNOT_INITIALIZE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_BACKEND_CANNOT_INITIALIZEObject> 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 -
NOTE_CONFIG_BACKEND_ACTION_REQUIRED_TO_CHANGE_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_CONFIG_BACKEND_ACTION_REQUIRED_TO_CHANGE_CLASSObject> The requested change to configuration entry %s would cause the class for the associated backend to change from %s to %s. This change will not take effect until the backend is disabled and re-enabled, or until the Directory Server is restarted -
ERR_CONFIG_CONNHANDLER_CANNOT_INITIALIZE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_CONNHANDLER_CANNOT_INITIALIZEObject> 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 -
ERR_CONFIG_SCHEMA_NO_SCHEMA_DIR
Unable to read the Directory Server schema definitions because the schema directory %s does not exist -
ERR_CONFIG_SCHEMA_DIR_NOT_DIRECTORY
Unable to read the Directory Server schema definitions because the schema directory %s exists but is not a directory -
ERR_CONFIG_SCHEMA_CANNOT_LIST_FILES
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 -
WARN_CONFIG_SCHEMA_CANNOT_OPEN_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_CONFIG_SCHEMA_CANNOT_OPEN_FILEObject> Schema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to open the file for reading: %s -
WARN_CONFIG_SCHEMA_CANNOT_READ_LDIF_ENTRY
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_CONFIG_SCHEMA_CANNOT_READ_LDIF_ENTRYObject> Schema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to read its contents as an LDIF entry: %s -
ERR_CONFIG_ENTRYCACHE_CANNOT_INSTALL_DEFAULT_CACHE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONFIG_ENTRYCACHE_CANNOT_INSTALL_DEFAULT_CACHEAn unexpected error occurred that prevented the server from installing its default entry cache framework: %s -
WARN_CONFIG_ENTRYCACHE_NO_CONFIG_ENTRY
The entry cache configuration entry "cn=Entry Caches,cn=config" does not exist in the Directory Server configuration. No entry cache will be available until this entry is created with a valid entry cache configuration -
ERR_CONFIG_ENTRYCACHE_CANNOT_INITIALIZE_CACHE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_ENTRYCACHE_CANNOT_INITIALIZE_CACHEAn 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 -
ERR_CONFIG_ENTRYCACHE_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_ENTRYCACHE_CONFIG_NOT_ACCEPTABLEThe configuration for the entry cache defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_ENTRYCACHE_CONFIG_LEVEL_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Number> ERR_CONFIG_ENTRYCACHE_CONFIG_LEVEL_NOT_ACCEPTABLEThe configuration for the entry cache defined in configuration entry %s was not acceptable: the entry cache level %d is already in use -
ERR_CONFIG_PLUGIN_CANNOT_INITIALIZE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_PLUGIN_CANNOT_INITIALIZEObject> 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 -
ERR_CONFIG_EXTOP_INVALID_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_EXTOP_INVALID_CLASSObject> Class %s specified in configuration entry %s does not contain a valid extended operation handler implementation: %s -
ERR_CONFIG_EXTOP_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_EXTOP_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as an extended operation handler as defined in configuration entry %s: %s -
ERR_CONFIG_SASL_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_SASL_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as a SASL mechanism handler as defined in configuration entry %s: %s -
ERR_CONFIG_FILE_DELETE_NO_PARENT_DN
Entry %s cannot be removed from the Directory Server configuration because that DN does not have a parent -
ERR_CONFIG_FILE_ADD_ALREADY_EXISTS
Entry %s cannot be added to the Directory Server configuration because another configuration entry already exists with that DN -
ERR_CONFIG_FILE_ADD_NO_PARENT_DN
Entry %s cannot be added to the Directory Server configuration because that DN does not have a parent -
ERR_CONFIG_FILE_ADD_NO_PARENT
Entry %s cannot be added to the Directory Server configuration because its parent entry %s does not exist -
ERR_CONFIG_FILE_ADD_REJECTED_BY_LISTENER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_FILE_ADD_REJECTED_BY_LISTENERObject> 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 -
ERR_CONFIG_FILE_ADD_FAILED
An unexpected error occurred while attempting to add configuration entry %s as a child of entry %s: %s -
ERR_CONFIG_FILE_DELETE_NO_SUCH_ENTRY
Entry %s cannot be removed from the Directory Server configuration because the specified entry does not exist -
ERR_CONFIG_FILE_DELETE_HAS_CHILDREN
Entry %s cannot be removed from the Directory Server configuration because the specified entry has one or more subordinate entries -
ERR_CONFIG_FILE_DELETE_NO_PARENT
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 -
ERR_CONFIG_FILE_DELETE_REJECTED_BY_LISTENER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_FILE_DELETE_REJECTED_BY_LISTENERObject> 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 -
ERR_CONFIG_FILE_DELETE_FAILED
An unexpected error occurred while attempting to remove configuration entry %s as a child of entry %s: %s -
ERR_CONFIG_FILE_MODIFY_NO_SUCH_ENTRY
Entry %s cannot be modified because the specified entry does not exist -
ERR_CONFIG_FILE_MODIFY_REJECTED_BY_CHANGE_LISTENER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_FILE_MODIFY_REJECTED_BY_CHANGE_LISTENEREntry %s cannot be modified because one of the configuration change listeners registered for that entry rejected the change: %s -
ERR_CONFIG_FILE_MODIFY_FAILED
An unexpected error occurred while attempting to modify configuration entry %s as a child of entry %s: %s -
ERR_CONFIG_FILE_WRITE_CANNOT_EXPORT_NEW_CONFIG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_FILE_WRITE_CANNOT_EXPORT_NEW_CONFIGAn error occurred while attempting to export the new Directory Server configuration to file %s: %s -
ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_NEW_CONFIG
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_NEW_CONFIGObject> An error occurred while attempting to rename the new Directory Server configuration from file %s to %s: %s -
ERR_CONFIG_FILE_MODDN_NOT_ALLOWED
Modify DN operations are not allowed in the Directory Server configuration -
ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as a password storage scheme as defined in configuration entry %s: %s -
ERR_CONFIG_PWSCHEME_EXISTS
Unable to add a new password storage scheme entry with DN %s because there is already a storage scheme registered with that DN -
WARN_CONFIG_BACKEND_DUPLICATE_BACKEND_ID
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_BACKEND_DUPLICATE_BACKEND_IDThe backend defined in configuration entry %s has a backend ID of %s that conflicts with the backend ID for another backend in the server. The backend will be disabled -
ERR_CONFIG_BACKEND_CANNOT_ACQUIRE_SHARED_LOCK
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_BACKEND_CANNOT_ACQUIRE_SHARED_LOCKThe 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 -
WARN_CONFIG_BACKEND_CANNOT_RELEASE_SHARED_LOCK
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_BACKEND_CANNOT_RELEASE_SHARED_LOCKAn error occurred while attempting to release a shared lock for backend %s: %s. This may interfere with operations that require exclusive access, including LDIF import and restoring a backup -
ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as an identity mapper as defined in configuration entry %s: %s -
ERR_CONFIG_SYNCH_UNABLE_TO_INSTANTIATE_PROVIDER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_SYNCH_UNABLE_TO_INSTANTIATE_PROVIDERObject> An error occurred while attempting to instantiate class %s referenced in synchronization provider configuration entry %s: %s -
ERR_CONFIG_SYNCH_ERROR_INITIALIZING_PROVIDER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_SYNCH_ERROR_INITIALIZING_PROVIDERAn error occurred while attempting to initialize the Directory Server synchronization provider referenced in configuration entry %s: %s -
ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as a password validator as defined in configuration entry %s: %s -
ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as a password generator as defined in configuration entry %s: %s -
ERR_CONFIG_PWPOLICY_NO_POLICIES
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 -
ERR_CONFIG_PWPOLICY_INVALID_POLICY_CONFIG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_PWPOLICY_INVALID_POLICY_CONFIGThe password policy defined in configuration entry %s is invalid: %s -
ERR_CONFIG_PWPOLICY_MISSING_DEFAULT_POLICY
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 -
WARN_CONFIG_PWPOLICY_CANNOT_DELETE_DEFAULT_POLICY
public static LocalizableMessageDescriptor.Arg1<Object> WARN_CONFIG_PWPOLICY_CANNOT_DELETE_DEFAULT_POLICYThe specified entry %s is currently defined as the configuration entry for the default password policy. The default password policy configuration entry may not be removed -
INFO_CONFIG_PWPOLICY_REMOVED_POLICY
Password policy entry %s has been removed from the Directory Server configuration. Any user entries that explicitly reference this password policy will no longer be allowed to authenticate -
WARN_CONFIG_AUTHZ_DISABLED
Access control has been disabled -
NOTE_CONFIG_AUTHZ_ENABLED
Access control has been enabled and will use the %s implementation -
ERR_CONFIG_AUTHZ_UNABLE_TO_INSTANTIATE_HANDLER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_AUTHZ_UNABLE_TO_INSTANTIATE_HANDLERObject> An error occurred while attempting to instantiate class %s referenced in the access control configuration entry %s: %s -
ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILEDObject> 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 -
ERR_CONFIG_ACCTNOTHANDLER_EXISTS
Unable to add a new account status notification handler entry with DN %s because there is already a notification handler registered with that DN -
ERR_CONFIG_UNABLE_TO_APPLY_STARTUP_CHANGES
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_UNABLE_TO_APPLY_STARTUP_CHANGESAn error occurred while attempting to apply the changes contained in file %s to the server configuration at startup: %s -
ERR_CONFIG_UNABLE_TO_APPLY_CHANGES_FILE
One or more errors occurred while applying changes on server startup: %s -
ERR_CONFIG_BACKEND_MODE_INVALID
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.) -
ERR_CONFIG_BACKEND_INSANE_MODE
Invalid UNIX file permissions %s does not allow read and write access to the backend database directory by the backend -
ERR_CONFIG_PWPOLICY_NO_DEFAULT_POLICY
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 -
WARN_CONFIG_BACKEND_CANNOT_REGISTER_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_BACKEND_CANNOT_REGISTER_BACKENDAn error occurred while attempting to register backend %s with the Directory Server: %s -
ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIR
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIRAn error occurred while trying to create the configuration archive directory %s: %s -
ERR_CONFIG_FILE_CANNOT_WRITE_CONFIG_ARCHIVE
An error occurred while trying to write the current configuration to the configuration archive: %s -
ERR_CONFIG_FILE_ADD_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform add operations in the Directory Server configuration -
ERR_CONFIG_FILE_DELETE_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform delete operations in the Directory Server configuration -
ERR_CONFIG_FILE_MODIFY_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform modify operations in the Directory Server configuration -
ERR_CONFIG_FILE_MODDN_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform modify DN operations in the Directory Server configuration -
ERR_CONFIG_FILE_SEARCH_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform search operations in the Directory Server configuration -
ERR_CONFIG_FILE_MODIFY_PRIVS_INSUFFICIENT_PRIVILEGES
public static LocalizableMessageDescriptor.Arg0 ERR_CONFIG_FILE_MODIFY_PRIVS_INSUFFICIENT_PRIVILEGESYou do not have sufficient privileges to change the set of default root privileges -
ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as a certificate mapper as defined in configuration entry %s: %s -
ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as a key manager provider as defined in configuration entry %s: %s -
ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as a trust manager provider as defined in configuration entry %s: %s -
ERR_CONFIG_JMX_CANNOT_GET_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_JMX_CANNOT_GET_ATTRIBUTEObject> Unable to retrieve JMX attribute %s associated with configuration entry %s: %s -
ERR_CONFIG_CHANGE_NO_RESULT
%s.%s returned a result of null for entry %s -
ERR_CONFIG_CHANGE_RESULT_ERROR
public static LocalizableMessageDescriptor.Arg6<Object,Object, ERR_CONFIG_CHANGE_RESULT_ERRORObject, Object, Boolean, Object> %s.%s failed for entry %s: result code=%s, admin action required=%b, messages="%s" -
WARN_CONFIG_CHANGE_RESULT_ACTION_REQUIRED
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_CONFIG_CHANGE_RESULT_ACTION_REQUIREDObject, Object> %s.%s indicated that administrative action is required for entry %s: messages="%s" -
INFO_CONFIG_CHANGE_RESULT_MESSAGES
public static LocalizableMessageDescriptor.Arg4<Object,Object, INFO_CONFIG_CHANGE_RESULT_MESSAGESObject, Object> %s.%s succeeded but generated the following messages for entry %s: %s -
ERR_CONFIG_VATTR_INVALID_SEARCH_FILTER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_VATTR_INVALID_SEARCH_FILTERObject> Unable to parse value "%s" from config entry "%s" as a valid search filter: %s -
ERR_CONFIG_VATTR_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_VATTR_INITIALIZATION_FAILEDObject> An error occurred while trying to load an instance of class %s referenced in configuration entry %s as a virtual attribute provider: %s -
ERR_CONFIG_VATTR_SV_TYPE_WITH_MV_PROVIDER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_VATTR_SV_TYPE_WITH_MV_PROVIDERObject> The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but provider %s may generate multiple values -
ERR_CONFIG_VATTR_SV_TYPE_WITH_MERGE_VALUES
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_VATTR_SV_TYPE_WITH_MERGE_VALUESThe 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 -
ERR_CONFIG_FILE_MODIFY_STRUCTURAL_CHANGE_NOT_ALLOWED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONFIG_FILE_MODIFY_STRUCTURAL_CHANGE_NOT_ALLOWEDConfiguration entry %s cannot be modified because the change would alter its structural object class -
ERR_CONFIG_CANNOT_CALCULATE_DIGEST
An error occurred while attempting to calculate a SHA-1 digest of file %s: %s -
WARN_CONFIG_MANUAL_CHANGES_DETECTED
The Directory Server has detected that one or more external changes have been made to the configuration file %s while the server was online, but another change has caused the server configuration to be overwritten. The manual changes have not been applied, but they have been preserved in file %s -
ERR_CONFIG_MANUAL_CHANGES_LOST
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 -
ERR_CONFIG_ROTATION_POLICY_INVALID_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_ROTATION_POLICY_INVALID_CLASSObject> Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log rotation policy: %s -
ERR_CONFIG_RETENTION_POLICY_INVALID_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_RETENTION_POLICY_INVALID_CLASSObject> Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log retention policy: %s -
ERR_CONFIG_ROTATION_POLICY_CANNOT_CREATE_POLICY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_ROTATION_POLICY_CANNOT_CREATE_POLICYAn error occurred while attempting to create a Directory Server log rotation policy from the information in configuration entry %s: %s -
ERR_CONFIG_RETENTION_POLICY_CANNOT_CREATE_POLICY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_RETENTION_POLICY_CANNOT_CREATE_POLICYAn error occurred while attempting to create a Directory Server log retention policy from the information in configuration entry %s: %s -
ERR_CONFIG_LOGGING_CANNOT_CREATE_WRITER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_LOGGING_CANNOT_CREATE_WRITERAn error occurred while attempting to create a text writer for a Directory Server logger from the information in configuration entry %s: %s -
WARN_CONFIG_SCHEMA_MULTIPLE_ENTRIES_IN_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_SCHEMA_MULTIPLE_ENTRIES_IN_FILESchema configuration file %s in directory %s contains more than one entry. Only the first entry will be examined, and the additional entries will be ignored -
WARN_CONFIG_PLUGIN_EMPTY_ELEMENT_IN_ORDER
The plugin order definition for plugins of type %s contains an empty element. This may cause the plugin order to be evaluated incorrectly -
WARN_CONFIG_PLUGIN_MULTIPLE_WILDCARDS_IN_ORDER
public static LocalizableMessageDescriptor.Arg1<Object> WARN_CONFIG_PLUGIN_MULTIPLE_WILDCARDS_IN_ORDERThe plugin order definition for plugins of type %s contains multiple wildcard characters. All plugin definitions should contain exactly one wildcard element to indicate where unmatched plugins should be included in the order, and including multiple wildcards may cause the plugin order to be evaluated incorrectly -
WARN_CONFIG_PLUGIN_LISTED_MULTIPLE_TIMES
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_PLUGIN_LISTED_MULTIPLE_TIMESThe plugin order definition for plugins of type %s includes multiple references to the '%s' plugin. This may cause the plugin order to be evaluated incorrectly -
WARN_CONFIG_PLUGIN_ORDER_NO_WILDCARD
The plugin order definition for plugins of type %s does not include a wildcard element to indicate where unmatched plugins should be included in the order. The server will default to invoking all unnamed plugins after set of named plugins -
ERR_CONFIG_WORK_QUEUE_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_WORK_QUEUE_INITIALIZATION_FAILEDObject> Unable to initialize an instance of class %s as a work queue as specified in configuration entry %s: %s -
INFO_CONFIG_WORK_QUEUE_CLASS_CHANGE_REQUIRES_RESTART
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_CONFIG_WORK_QUEUE_CLASS_CHANGE_REQUIRES_RESTARTThe class used to provide the Directory Server work queue implementation has been changed from %s to %s, but this change will not take effect until the server is restarted -
ERR_CONFIG_FILE_ADD_APPLY_FAILED
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 -
ERR_CONFIG_FILE_DELETE_APPLY_FAILED
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 -
ERR_CONFIG_FILE_MODIFY_APPLY_FAILED
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 -
ERR_CONFIG_KEYMANAGER_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_KEYMANAGER_CONFIG_NOT_ACCEPTABLEThe configuration for the key manager provider defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_TRUSTMANAGER_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_TRUSTMANAGER_CONFIG_NOT_ACCEPTABLEThe configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_AUTHZ_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_AUTHZ_CONFIG_NOT_ACCEPTABLEThe configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_ACCTNOTHANDLER_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_ACCTNOTHANDLER_CONFIG_NOT_ACCEPTABLEThe configuration for the account status notification handler defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_CERTMAPPER_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_CERTMAPPER_CONFIG_NOT_ACCEPTABLEThe configuration for the certificate mapper defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_IDMAPPER_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_IDMAPPER_CONFIG_NOT_ACCEPTABLEThe configuration for the identity mapper defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_PWGENERATOR_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_PWGENERATOR_CONFIG_NOT_ACCEPTABLEThe configuration for the password generator defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_PWSCHEME_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_PWSCHEME_CONFIG_NOT_ACCEPTABLEThe configuration for the password storage scheme defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_PWVALIDATOR_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_PWVALIDATOR_CONFIG_NOT_ACCEPTABLEThe configuration for the password validator defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_PLUGIN_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_PLUGIN_CONFIG_NOT_ACCEPTABLEThe configuration for the plugin defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_SASL_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_SASL_CONFIG_NOT_ACCEPTABLEThe configuration for the SASL mechanism handler defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_VATTR_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_VATTR_CONFIG_NOT_ACCEPTABLEThe configuration for the virtual attribute provider defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_ALERTHANDLER_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_ALERTHANDLER_CONFIG_NOT_ACCEPTABLEThe configuration for the alert handler defined in configuration entry %s was not acceptable: %s -
ERR_CONFIG_ALERTHANDLER_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_ALERTHANDLER_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as an alert handler as defined in configuration entry %s: %s -
ERR_STARTOK_CANNOT_OPEN_FOR_READING
An error occurred while attempting to open the current configuration file %s for reading in order to copy it to the ".startok" file: %s -
ERR_STARTOK_CANNOT_WRITE
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 -
ERR_STARTOK_CANNOT_RENAME
An error occurred while attempting to rename file %s to %s for use as the ".startok" configuration file: %s -
NOTE_CONFIG_FILE_USING_STARTOK_FILE
The Directory Server is starting using the last known good configuration file %s rather than the active configuration file %s -
WARN_CONFIG_FILE_NO_STARTOK_FILE
No last known good configuration file %s exists. The server will attempt to start using the active configuration file %s -
ERR_CONFIG_JE_PROPERTY_INVALID
An error occurred while trying to parse and validate Berkeley DB JE property %s: %s -
ERR_CONFIG_JE_PROPERTY_INVALID_FORM
An error occurred while trying to parse and validate Berkeley DB JE property %s: the property does not follow a singular property=value form -
ERR_CONFIG_JE_PROPERTY_SHADOWS_CONFIG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_JE_PROPERTY_SHADOWS_CONFIGAn error occurred while trying to parse and validate Berkeley DB JE property %s: the property shadows configuration attribute %s -
ERR_CONFIG_JE_DUPLICATE_PROPERTY
An error occurred while trying to parse and validate Berkeley DB JE property %s: the property is already defined for this component -
ERR_CONFIG_LOGGING_CANNOT_OPEN_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_LOGGING_CANNOT_OPEN_FILEObject> An error occurred while attempting to open the configured log file %s for logger %s: %s -
ERR_CONFIG_LOGGING_INSANE_MODE
Invalid UNIX file permissions %s does not allow write access to the log file by the log publisher -
ERR_CONFIG_LOGGING_MODE_INVALID
Invalid UNIX file permissions %s: %s -
ERR_CONFIG_PWPOLICY_DEFAULT_POLICY_IS_WRONG_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONFIG_PWPOLICY_DEFAULT_POLICY_IS_WRONG_TYPEThe configuration entry '%s' is currently defined to be the default password policy, however it is not a password policy -
ERR_CONFIG_PWPOLICY_CANNOT_CHANGE_DEFAULT_POLICY_WRONG_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONFIG_PWPOLICY_CANNOT_CHANGE_DEFAULT_POLICY_WRONG_TYPEThe default password policy value '%s' is invalid because it refers to an authentication policy which is not a password policy -
ERR_CONFIG_LOGGING_INVALID_TIME_FORMAT
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 -
ERR_CONFIG_LOGGING_INVALID_USER_DN_PATTERN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_LOGGING_INVALID_USER_DN_PATTERNThe access log filtering criteria defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s" -
ERR_CONFIG_LOGGING_INVALID_TARGET_DN_PATTERN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_LOGGING_INVALID_TARGET_DN_PATTERNThe access log filtering criteria defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s" -
WARN_CONFIG_LOGGER_NO_ACTIVE_HTTP_ACCESS_LOGGERS
There are no active HTTP access loggers defined in the Directory Server configuration. No HTTP access logging will be performed -
ERR_CONFIG_LOGGER_INVALID_HTTP_ACCESS_LOGGER_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_LOGGER_INVALID_HTTP_ACCESS_LOGGER_CLASSObject> Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server HTTP access logger: %s -
WARN_CONFIG_LOGGING_UNSUPPORTED_FIELDS_IN_LOG_FORMAT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_LOGGING_UNSUPPORTED_FIELDS_IN_LOG_FORMATThe log format for %s contains the following unsupported fields: %s. Their output will be replaced with a dash ("-") character -
ERR_CONFIG_LOGGER_CANNOT_UPDATE_LOGGER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_LOGGER_CANNOT_UPDATE_LOGGERAn error occurred while attempting to update a Directory Server logger from the information in configuration entry %s: %s -
ERR_CONFIG_CANNOT_CONFIGURE_JUL_LOGGER
Cannot configure java.util.logging root logger level: %s. java.util.logging support is now disabled -
ERR_CONFIG_HTTPENDPOINT_INITIALIZATION_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_HTTPENDPOINT_INITIALIZATION_FAILEDObject> An error occurred while trying to initialize an instance of class %s as an HTTP endpoint as defined in configuration entry %s: %s -
ERR_CONFIG_HTTPENDPOINT_UNABLE_TO_START
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_HTTPENDPOINT_UNABLE_TO_STARTAn error occurred while starting the HTTP endpoint as defined in configuration entry %s: %s -
ERR_CONFIG_HTTPENDPOINT_INVALID_CONFIGURATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_HTTPENDPOINT_INVALID_CONFIGURATIONThe HTTP endpoint configuration defined in %s is invalid: %s -
ERR_CANNOT_INITIALIZE_CONFIGURATION_FRAMEWORK
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CANNOT_INITIALIZE_CONFIGURATION_FRAMEWORKCannot initialize the configuration framework: %s -
ERR_UNABLE_TO_RETRIEVE_CHILDREN_OF_CONFIGURATION_ENTRY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_UNABLE_TO_RETRIEVE_CHILDREN_OF_CONFIGURATION_ENTRYUnable to retrieve children of configuration entry with dn: %s -
ERR_UNABLE_TO_LOAD_CONFIGURATION_ENABLED_SCHEMA
public static LocalizableMessageDescriptor.Arg1<Object> ERR_UNABLE_TO_LOAD_CONFIGURATION_ENABLED_SCHEMAUnable to load the configuration-enabled schema: %s -
ERR_CONFIG_BACKEND_CANNOT_DELETE_ENTRY
Backend config error when trying to delete an entry: %s -
ERR_CONFIG_HTTPENDPOINT_INVALID_AUTHZ_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_HTTPENDPOINT_INVALID_AUTHZ_DNThe HTTP endpoint configuration defined in %s is referencing a non existing authorization DN %s -
ERR_CONFIG_HTTPENDPOINT_CONFLICTING_AUTHZ_DN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_HTTPENDPOINT_CONFLICTING_AUTHZ_DNObject> The HTTP endpoint configuration defined in %s is referencing mutually exclusive authorization DNs %s and %s -
ERR_CONFIG_REST2LDAP_UNABLE_READ
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_REST2LDAP_UNABLE_READObject> Unable to read the configuration from %s in the REST2LDAP endpoint configuration entry %s: %s -
ERR_CONFIG_REST2LDAP_UNEXPECTED_JSON
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_CONFIG_REST2LDAP_UNEXPECTED_JSONObject, Object> Invalid JSON element %s from %s in the REST2LDAP endpoint configuration entry %s: %s -
ERR_CONFIG_REST2LDAP_INVALID
Invalid configuration element from %s in the REST2LDAP endpoint configuration entry %s: %s -
ERR_CONFIG_OAUTH2_INVALID_JSON_POINTER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_OAUTH2_INVALID_JSON_POINTERObject> The OAuth2 authorization mechanism defined in %s contains an invalid JSON Pointer %s: %s -
ERR_CONFIG_OAUTH2_NON_EXISTING_DIRECTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_OAUTH2_NON_EXISTING_DIRECTORYThe authorization mechanism defined in %s is referencing a non-existing or non-readable directory: %s -
ERR_CONFIG_AUTHZ_REFERENCED_DN_DOESNT_EXISTS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_AUTHZ_REFERENCED_DN_DOESNT_EXISTSThe authorization mechanism defined in %s is referencing a non existing DN: %s -
ERR_CONFIG_OAUTH2_INVALID_URL
The authorization mechanism defined in %s is referencing an invalid URL %s: %s -
ERR_CONFIG_OAUTH2_CONFIG_ERROR
Unable to configure the authorization mechanism defined in %s: %s -
ERR_BAD_ADMIN_API_RESOURCE_VERSION
The requested admin API version '%s' is unsupported. This endpoint only supports the following admin API version(s): %s -
ERR_CONFIG_SCHEMA_PROVIDER_CONFIG_NOT_ACCEPTABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_SCHEMA_PROVIDER_CONFIG_NOT_ACCEPTABLEThe configuration of schema provider '%s' is not acceptable for the following reasons: %s -
ERR_CONFIG_SCHEMA_PROVIDER_CANT_BE_INITIALIZED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CONFIG_SCHEMA_PROVIDER_CANT_BE_INITIALIZEDObject> The schema provider class '%s' could not be instantiated or initialized with the configuration '%s' : %s -
ERR_CONFIG_CORE_SCHEMA_PROVIDER_DISABLED
The core schema provider defined by '%s' has been disabled. The core schema must always be enabled -
WARN_CONFIG_SCHEMA_FILE_HAS_SCHEMA_WARNING
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_SCHEMA_FILE_HAS_SCHEMA_WARNINGThe config schema file '%s' generated warning when trying to update schema with its content: %s -
WARN_CONFIG_SCHEMA_FILE_HAS_SCHEMA_WARNING_WITH_OVERWRITE
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CONFIG_SCHEMA_FILE_HAS_SCHEMA_WARNING_WITH_OVERWRITEThe config schema file '%s' generated warning when trying to update schema with its content, despite allowing to overwrite definitions: %s -
ERR_CONFIG_BACKEND_BASE_IS_EMPTY
Unable to configure the backend '%s' because one of its base DNs is the empty DN -
ERR_CONFIG_UNSUPPORTED_SSL_PROTOCOL
Cannot configure new SSL protocols because the following protocols are not supported: %s. Look for supported protocols in 'cn=jvm,cn=monitor' -
ERR_CONFIG_UNSUPPORTED_SSL_CIPHER_SUITE
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' -
ERR_CONFIG_INVALID_REGEXP_EXCLUSION_PATTERN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_INVALID_REGEXP_EXCLUSION_PATTERNThe metric name pattern to exclude '%s' cannot be parsed as a valid regular expression due to the following error: '%s' -
ERR_CONFIG_INVALID_REGEXP_INCLUSION_PATTERN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CONFIG_INVALID_REGEXP_INCLUSION_PATTERNThe metric name pattern to include '%s' cannot be parsed as a valid regular expression due to the following error: '%s' -
ERR_CONFIG_MATCHING_RULE_INVALID_JSON_POINTER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONFIG_MATCHING_RULE_INVALID_JSON_POINTERThe list of keys defined for the JSON matching rule contains an invalid JSON pointer : %s -
ERR_CONFIG_PROPERTY_RESOLVER_ERROR
Cannot create the property resolver due to the following error: '%s' -
ERR_CONFIG_ERROR_CREATING_MAILSSLSOCKETFACTORY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONFIG_ERROR_CREATING_MAILSSLSOCKETFACTORYError creating SSL socket factory: %s -
ERR_CONFIG_INVALID_SMTP_HOSTPORT
The smtp-server value '%s' is invalid: %s -
ERR_CONFIG_UNABLE_TO_RESOLVE_HOST
Unable to resolve the host for the listen address '%s' of the LDAP connection handler %s -
WARN_CONFIG_ARCHIVE_FILE_INVALID
The latest archived configuration file %s appears to be invalid. Forcing creation of a new one -
WARN_DEPRECATED_CONFIGURATION
'%s' is DEPRECATED for removal since %s. Its usage is highly discouraged -
WARN_LEGACY_CONFIGURATION
'%s' is LEGACY since %s. Its usage is highly discouraged -
ERR_CANNOT_CANCEL_ABANDON
Abandon requests cannot be canceled -
ERR_CANNOT_CANCEL_BIND
Bind requests cannot be canceled -
ERR_CANNOT_CANCEL_UNBIND
Unbind requests cannot be canceled -
INFO_DISCONNECT_DUE_TO_UNBIND
Client Unbind -
INFO_DISCONNECT_DUE_TO_CLIENT_CLOSURE
Client Disconnect -
INFO_DISCONNECT_DUE_TO_REJECTED_CLIENT
Client Connection Rejected -
INFO_DISCONNECT_DUE_TO_IO_ERROR
I/O Error -
INFO_DISCONNECT_DUE_TO_PROTOCOL_ERROR
Protocol Error -
INFO_DISCONNECT_DUE_TO_SERVER_SHUTDOWN
Server Shutdown -
INFO_DISCONNECT_BY_ADMINISTRATOR
Administrative Termination -
INFO_DISCONNECT_DUE_TO_SECURITY_PROBLEM
Security Problem -
INFO_DISCONNECT_DUE_TO_MAX_REQUEST_SIZE
Maximum Request Size Exceeded -
INFO_DISCONNECT_DUE_TO_ADMIN_LIMIT
Administrative Limit Exceeded -
INFO_DISCONNECT_DUE_TO_IDLE_TIME_LIMIT
Idle Time Limit Exceeded -
INFO_DISCONNECT_DUE_TO_IO_TIMEOUT
I/O Timeout -
INFO_DISCONNECT_BY_PLUGIN
Connection Closed by Plugin -
INFO_DISCONNECT_OTHER
Unknown Closure Reason -
INFO_RESULT_OPERATIONS_ERROR
Operations Error -
INFO_RESULT_INVALID_CREDENTIALS
Invalid Credentials -
INFO_CANCELED_BY_SHUTDOWN
Processing on this operation has been canceled because the Directory Server is shutting down -
ERR_UNCAUGHT_WORKER_THREAD_EXCEPTION
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_UNCAUGHT_WORKER_THREAD_EXCEPTIONObject> %s encountered an uncaught exception while processing operation %s: %s -
WARN_UNEXPECTED_WORKER_THREAD_EXIT
%s is unexpectedly exiting when the Directory Server is not in the process of shutting down. This likely indicates that the thread encountered an unexpected error -
WARN_OP_REJECTED_BY_SHUTDOWN
The request to process this operation has been rejected because the Directory Server has already started its shutdown process -
WARN_WORKER_INTERRUPTED_WITHOUT_SHUTDOWN
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_WORKER_INTERRUPTED_WITHOUT_SHUTDOWN%s was interrupted while waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effects -
WARN_WORKER_WAITING_UNCAUGHT_EXCEPTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_WORKER_WAITING_UNCAUGHT_EXCEPTIONAn unexpected exception was caught while %s was waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effects -
WARN_QUEUE_UNABLE_TO_CANCEL
The work queue caught an exception while trying to cancel pending operation %s when the Directory Server was shutting down: %s -
INFO_DISCONNECT_DUE_TO_SERVER_ERROR
Server Error -
ERR_CANNOT_BOOTSTRAP_WHILE_RUNNING
The Directory Server is currently running. The configuration may not be bootstrapped while the server is online -
ERR_CANNOT_START_BEFORE_BOOTSTRAP
The Directory Server may not be started before the configuration has been bootstrapped -
ERR_CANNOT_START_WHILE_RUNNING
The Directory Server may not be started while it is already running. Please stop the running instance before attempting to start it again -
INFO_DIRECTORY_BOOTSTRAPPING
The Directory Server is beginning the configuration bootstrapping process -
NOTE_DIRECTORY_SERVER_STARTING
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_DIRECTORY_SERVER_STARTINGObject> %s (build %s, revision number %s) starting up -
NOTE_DIRECTORY_SERVER_STARTED
The Directory Server has started successfully -
ERR_CANNOT_CREATE_MBEAN_SERVER
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 -
NOTE_SENT_ALERT_NOTIFICATION
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_SENT_ALERT_NOTIFICATIONObject, Object> The Directory Server has sent an alert notification generated by class %s (alert type %s, alert ID %s): %s -
ERR_UNCAUGHT_THREAD_EXCEPTION
An uncaught exception during processing for thread "%s" has caused it to terminate abnormally. The stack trace for that exception is: %s -
NOTE_SERVER_SHUTDOWN
The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class %s and the reason provided for the shutdown was %s -
ERR_SHUTDOWN_DUE_TO_SHUTDOWN_HOOK
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) -
ERR_CANNOT_GET_ROOT_DSE_CONFIG_ENTRY
An error occurred while trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) from the Directory Server configuration: %s -
WARN_ADD_OP_INVALID_SYNTAX
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_ADD_OP_INVALID_SYNTAXObject, Object> Entry "%s" contains a value "%s" for attribute %s that is invalid according to the syntax for that attribute: %s -
WARN_COMPARE_OP_NO_SUCH_ATTR
Entry "%s" does not contain any values for attribute "%s" -
WARN_COMPARE_OP_NO_SUCH_ATTR_WITH_OPTIONS
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_COMPARE_OP_NO_SUCH_ATTR_WITH_OPTIONSEntry "%s" does not contain any values for attribute "%s" with the specified set of options -
NOTE_SERVER_STOPPED
The Directory Server is now stopped -
INFO_WORKER_STOPPED_BY_REDUCED_THREADNUMBER
%s has been stopped because the total number of worker threads in the Directory Server was reduced -
INFO_CANCELED_BY_BIND_REQUEST
Processing on this operation has been canceled because the Directory Server received a bind request on this connection, which requires that all operations in progress to be abandoned -
ERR_BIND_OPERATION_UNKNOWN_USER
Unable to bind to the Directory Server because no such user exists in the server -
ERR_STARTUP_PLUGIN_ERROR
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 -
ERR_BIND_OPERATION_NO_PASSWORD
Unable to bind to the Directory Server using simple authentication because that user does not have a password -
ERR_BIND_OPERATION_UNKNOWN_SASL_MECHANISM
Unable to process the bind request because it attempted to use an unknown SASL mechanism %s that is not available in the Directory Server -
ERR_COMPARE_NO_SUCH_ENTRY
The specified entry %s does not exist in the Directory Server -
INFO_CANCELED_BY_ABANDON_REQUEST
The operation was canceled because the client issued an abandon request (message ID %d) for this operation -
ERR_ADD_CANNOT_ADD_ROOT_DSE
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 -
ERR_ADD_ENTRY_NOT_SUFFIX
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 -
ERR_ADD_NO_PARENT
Entry %s cannot be added because its parent entry %s does not exist in the server -
ERR_ADD_CANNOT_LOCK_ENTRY
Entry %s cannot be added because the server failed to obtain a write lock for this entry after multiple attempts -
ERR_DELETE_CANNOT_LOCK_ENTRY
Entry %s cannot be removed because the server failed to obtain a write lock for this entry after multiple attempts -
ERR_SEARCH_TIME_LIMIT_EXCEEDED
The maximum time limit of %d seconds for processing this search operation has expired -
ERR_SEARCH_SIZE_LIMIT_EXCEEDED
This search operation has sent the maximum of %d entries to the client -
ERR_SEARCH_BASE_DOESNT_EXIST
The entry %s specified as the search base does not exist in the Directory Server -
ERR_DELETE_NO_SUCH_ENTRY
Entry %s does not exist in the Directory Server -
ERR_DELETE_HAS_SUB_BACKEND
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 -
ERR_MODDN_NO_PARENT
A modify DN operation cannot be performed on entry %s because the new RDN would not have a parent DN -
ERR_MODDN_NO_BACKEND_FOR_CURRENT_ENTRY
The modify DN operation for entry %s cannot be performed because no backend is registered to handle that DN -
ERR_MODDN_NO_BACKEND_FOR_NEW_ENTRY
The modify DN operation for entry %s cannot be performed because no backend is registered to handle the new DN %s -
ERR_MODDN_DIFFERENT_BACKENDS
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 -
ERR_MODDN_CANNOT_LOCK_CURRENT_DN
The modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for that DN -
ERR_MODDN_CANNOT_LOCK_NEW_DN
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 -
ERR_MODDN_NO_CURRENT_ENTRY
The modify DN operation for entry %s cannot be performed because that entry does not exist in the server -
ERR_MODIFY_CANNOT_LOCK_ENTRY
Entry %s cannot be modified because the server failed to obtain a write lock for this entry after multiple attempts -
ERR_MODIFY_NO_SUCH_ENTRY
Entry %s cannot be modified because no such entry exists in the server -
ERR_MODIFY_ADD_NO_VALUES
Entry %s cannot be modified because the modification contained an add component for attribute %s but no values were provided -
ERR_MODIFY_ADD_INVALID_SYNTAX
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_MODIFY_ADD_INVALID_SYNTAXObject, Object> 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 -
ERR_MODIFY_ADD_DUPLICATE_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_MODIFY_ADD_DUPLICATE_VALUEObject> Entry %s cannot be modified because it would have resulted in one or more duplicate values for attribute %s: %s -
ERR_MODIFY_DELETE_RDN_ATTR
Entry %s cannot be modified because the change to attribute %s would have removed a value used in the RDN -
ERR_MODIFY_DELETE_MISSING_VALUES
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_MODIFY_DELETE_MISSING_VALUESObject> 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 -
ERR_MODIFY_DELETE_NO_SUCH_ATTR
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 -
ERR_MODIFY_REPLACE_INVALID_SYNTAX
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_MODIFY_REPLACE_INVALID_SYNTAXObject, Object> 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 -
ERR_MODIFY_INCREMENT_RDN
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 -
ERR_MODIFY_INCREMENT_REQUIRES_VALUE
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 -
ERR_MODIFY_INCREMENT_REQUIRES_SINGLE_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODIFY_INCREMENT_REQUIRES_SINGLE_VALUEEntry %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 -
ERR_MODIFY_INCREMENT_REQUIRES_EXISTING_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODIFY_INCREMENT_REQUIRES_EXISTING_VALUEEntry %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 -
ERR_MODIFY_INCREMENT_REQUIRES_INTEGER_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_MODIFY_INCREMENT_REQUIRES_INTEGER_VALUEObject> 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 -
ERR_MODIFY_VIOLATES_SCHEMA
Entry %s cannot be modified because the resulting entry would have violated the server schema: %s -
ERR_EXTENDED_NO_HANDLER
There is no extended operation handler registered with the Directory Server for handling extended operations with a request OID of %s -
ERR_SEARCH_BACKEND_EXCEPTION
An unexpected error was encountered while processing a search in one of the Directory Server backends: %s -
ERR_MODDN_VIOLATES_SCHEMA
The modify DN operation for entry %s cannot be performed because the change would have violated the server schema: %s -
ERR_ENTRY_ADD_UNKNOWN_OC
Object class %s cannot be added to entry %s because that class is not defined in the Directory Server schema -
ERR_BIND_OPERATION_WRONG_PASSWORD
The password provided by the user did not match any password(s) stored in the user's entry -
INFO_DSCORE_DESCRIPTION_SYSINFO
Display general system information -
ERR_DSCORE_ERROR_PARSING_ARGS
An error occurred while attempting to parse the provided set of command line arguments: %s -
ERR_DSCORE_CANNOT_BOOTSTRAP
An error occurred while attempting to bootstrap the Directory Server: %s -
ERR_DSCORE_CANNOT_START
An error occurred while trying to start the Directory Server: %s -
ERR_FILELOCKER_LOCK_SHARED_REJECTED_BY_EXCLUSIVE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_FILELOCKER_LOCK_SHARED_REJECTED_BY_EXCLUSIVEThe attempt to obtain a shared lock on file %s was rejected because an exclusive lock was already held on that file -
ERR_FILELOCKER_LOCK_SHARED_FAILED_CREATE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_LOCK_SHARED_FAILED_CREATEThe attempt to obtain a shared lock on file %s was rejected because the attempt to create the lock file failed: %s -
ERR_FILELOCKER_LOCK_SHARED_FAILED_OPEN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_LOCK_SHARED_FAILED_OPENThe attempt to obtain a shared lock on file %s was rejected because the attempt to open the lock file failed: %s -
ERR_FILELOCKER_LOCK_SHARED_FAILED_LOCK
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_LOCK_SHARED_FAILED_LOCKThe attempt to obtain a shared lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s -
ERR_FILELOCKER_LOCK_SHARED_NOT_GRANTED
The shared lock requested for file %s was not granted, which indicates that another process already holds an exclusive lock on that file -
ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_EXCLUSIVE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_EXCLUSIVEThe attempt to obtain an exclusive lock on file %s was rejected because an exclusive lock was already held on that file -
ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_SHARED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_SHAREDThe attempt to obtain an exclusive lock on file %s was rejected because a shared lock was already held on that file -
ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_CREATE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_CREATEThe attempt to obtain an exclusive lock on file %s was rejected because the attempt to create the lock file failed: %s -
ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_OPEN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_OPENThe attempt to obtain an exclusive lock on file %s was rejected because the attempt to open the lock file failed: %s -
ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_LOCK
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_LOCKThe attempt to obtain an exclusive lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s -
ERR_FILELOCKER_LOCK_EXCLUSIVE_NOT_GRANTED
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 -
ERR_FILELOCKER_UNLOCK_EXCLUSIVE_FAILED_RELEASE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_UNLOCK_EXCLUSIVE_FAILED_RELEASEThe attempt to release the exclusive lock held on %s failed: %s -
ERR_FILELOCKER_UNLOCK_SHARED_FAILED_RELEASE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILELOCKER_UNLOCK_SHARED_FAILED_RELEASEThe attempt to release the shared lock held on %s failed: %s -
ERR_FILELOCKER_UNLOCK_UNKNOWN_FILE
The attempt to release the lock held on %s failed because no record of a lock on that file was found -
WARN_SHUTDOWN_CANNOT_RELEASE_SHARED_BACKEND_LOCK
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_SHUTDOWN_CANNOT_RELEASE_SHARED_BACKEND_LOCKAn error occurred while attempting to release a shared lock for backend %s: %s. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary -
ERR_CANNOT_ACQUIRE_EXCLUSIVE_SERVER_LOCK
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CANNOT_ACQUIRE_EXCLUSIVE_SERVER_LOCKThe Directory Server could not acquire an exclusive lock on file %s: %s. This generally means that another instance of this server is already running -
ERR_MODIFY_ATTR_IS_NO_USER_MOD
Entry %s cannot be modified because the modification attempted to update attribute %s which is defined as NO-USER-MODIFICATION in the server schema -
ERR_ADD_ATTR_IS_NO_USER_MOD
Entry %s cannot be added because it includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema -
ERR_MODDN_OLD_RDN_ATTR_IS_NO_USER_MOD
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODDN_OLD_RDN_ATTR_IS_NO_USER_MODEntry %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 -
ERR_MODDN_NEW_RDN_ATTR_IS_NO_USER_MOD
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODDN_NEW_RDN_ATTR_IS_NO_USER_MODEntry %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 -
ERR_MODDN_PREOP_VIOLATES_SCHEMA
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 -
ERR_MODIFY_ASSERTION_FAILED
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 -
ERR_MODIFY_UNSUPPORTED_CRITICAL_CONTROL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODIFY_UNSUPPORTED_CRITICAL_CONTROLEntry %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 -
ERR_DELETE_ASSERTION_FAILED
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 -
ERR_DELETE_UNSUPPORTED_CRITICAL_CONTROL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DELETE_UNSUPPORTED_CRITICAL_CONTROLEntry %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 -
ERR_MODDN_ASSERTION_FAILED
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 -
ERR_MODDN_UNSUPPORTED_CRITICAL_CONTROL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODDN_UNSUPPORTED_CRITICAL_CONTROLEntry %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 -
ERR_ADD_ASSERTION_FAILED
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 -
ERR_ADD_UNSUPPORTED_CRITICAL_CONTROL
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 -
ERR_SEARCH_CANNOT_GET_ENTRY_FOR_ASSERTION
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 -
ERR_SEARCH_NO_SUCH_ENTRY_FOR_ASSERTION
The search request cannot be processed because it contains an LDAP assertion control but the search base entry does not exist -
ERR_SEARCH_ASSERTION_FAILED
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 -
ERR_SEARCH_UNSUPPORTED_CRITICAL_CONTROL
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 -
ERR_COMPARE_ASSERTION_FAILED
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 -
ERR_COMPARE_UNSUPPORTED_CRITICAL_CONTROL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMPARE_UNSUPPORTED_CRITICAL_CONTROLCannot 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 -
INFO_ADD_NOOP
The add operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request -
INFO_DELETE_NOOP
The delete operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request -
INFO_MODIFY_NOOP
The modify operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request -
INFO_MODDN_NOOP
The modify DN operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request -
ERR_ADD_MISSING_RDN_ATTRIBUTE
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 -
ERR_BIND_UNSUPPORTED_CRITICAL_CONTROL
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 -
WARN_BIND_MULTIPLE_USER_SIZE_LIMITS
There are multiple user-specific size limit values contained in user entry %s. The default server size limit will be used -
WARN_BIND_CANNOT_PROCESS_USER_SIZE_LIMIT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_BIND_CANNOT_PROCESS_USER_SIZE_LIMITThe user-specific size limit value %s contained in user entry %s could not be parsed as an integer. The default server size limit will be used -
WARN_BIND_MULTIPLE_USER_TIME_LIMITS
There are multiple user-specific time limit values contained in user entry %s. The default server time limit will be used -
WARN_BIND_CANNOT_PROCESS_USER_TIME_LIMIT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_BIND_CANNOT_PROCESS_USER_TIME_LIMITThe user-specific time limit value %s contained in user entry %s could not be parsed as an integer. The default server time limit will be used -
ERR_ADD_SYNCH_PREOP_FAILED
An error occurred during preoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s -
ERR_ADD_SYNCH_POSTOP_FAILED
An error occurred during postoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s -
ERR_DELETE_SYNCH_PREOP_FAILED
An error occurred during preoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s -
ERR_DELETE_SYNCH_POSTOP_FAILED
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_DELETE_SYNCH_POSTOP_FAILEDObject> An error occurred during postoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s -
ERR_MODIFY_SYNCH_PREOP_FAILED
An error occurred during preoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s -
ERR_MODIFY_SYNCH_POSTOP_FAILED
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_MODIFY_SYNCH_POSTOP_FAILEDObject> An error occurred during postoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s -
ERR_MODDN_SYNCH_PREOP_FAILED
An error occurred during preoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s -
ERR_MODDN_SYNCH_POSTOP_FAILED
An error occurred during postoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s -
ERR_ADD_SYNCH_CONFLICT_RESOLUTION_FAILED
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_ADD_SYNCH_CONFLICT_RESOLUTION_FAILEDObject> An error occurred during conflict resolution synchronization processing for the add operation with connection ID %d and operation ID %d: %s -
ERR_DELETE_SYNCH_CONFLICT_RESOLUTION_FAILED
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_DELETE_SYNCH_CONFLICT_RESOLUTION_FAILEDObject> An error occurred during conflict resolution synchronization processing for the delete operation with connection ID %d and operation ID %d: %s -
ERR_MODIFY_SYNCH_CONFLICT_RESOLUTION_FAILED
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_MODIFY_SYNCH_CONFLICT_RESOLUTION_FAILEDObject> An error occurred during conflict resolution synchronization processing for the modify operation with connection ID %d and operation ID %d: %s -
ERR_MODDN_SYNCH_CONFLICT_RESOLUTION_FAILED
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_MODDN_SYNCH_CONFLICT_RESOLUTION_FAILEDObject> An error occurred during conflict resolution synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s -
ERR_ADD_SERVER_READONLY
Unable to add entry %s because the Directory Server is configured in read-only mode -
ERR_ADD_BACKEND_READONLY
Unable to add entry %s because the backend that should hold that entry is configured in read-only mode -
ERR_DELETE_SERVER_READONLY
Unable to delete entry %s because the Directory Server is configured in read-only mode -
ERR_DELETE_BACKEND_READONLY
Unable to delete entry %s because the backend that holds that entry is configured in read-only mode -
ERR_MODIFY_SERVER_READONLY
Unable to modify entry %s because the Directory Server is configured in read-only mode -
ERR_MODIFY_BACKEND_READONLY
Unable to modify entry %s because the backend that holds that entry is configured in read-only mode -
ERR_MODDN_SERVER_READONLY
Unable to rename entry %s because the Directory Server is configured in read-only mode -
ERR_MODDN_BACKEND_READONLY
Unable to rename entry %s because the backend that holds that entry is configured in read-only mode -
ERR_BIND_DN_BUT_NO_PASSWORD
Unable to process the simple bind request because it contained a bind DN but no password, which is forbidden by the server configuration -
ERR_PWPOLICY_UNDEFINED_PASSWORD_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPOLICY_UNDEFINED_PASSWORD_ATTRIBUTEThe password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" is not defined in the server schema -
ERR_PWPOLICY_INVALID_PASSWORD_ATTRIBUTE_SYNTAX
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PWPOLICY_INVALID_PASSWORD_ATTRIBUTE_SYNTAXObject> 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) -
ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CHANGE_BY_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CHANGE_BY_TIMEAn error occurred while attempting to determine the value for attribute ds-cfg-require-change-by-time in configuration entry %s: %s -
ERR_PWPOLICY_INVALID_LAST_LOGIN_TIME_FORMAT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPOLICY_INVALID_LAST_LOGIN_TIME_FORMATThe 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 'java.text.SimpleDateFormat' class -
ERR_PWPOLICY_INVALID_PREVIOUS_LAST_LOGIN_TIME_FORMAT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPOLICY_INVALID_PREVIOUS_LAST_LOGIN_TIME_FORMATThe 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 'java.text.SimpleDateFormat' class -
ERR_PWPOLICY_ATTRIBUTE_OPTIONS_NOT_ALLOWED
Attribute options are not allowed for the password attribute %s -
ERR_PWPOLICY_MULTIPLE_PW_VALUES_NOT_ALLOWED
Only a single value may be provided for the password attribute %s -
ERR_PWPOLICY_PREENCODED_NOT_ALLOWED
Pre-encoded passwords are not allowed for the password attribute %s -
ERR_PWPOLICY_VALIDATION_FAILED
The password value for attribute %s was found to be unacceptable: %s -
ERR_PWPOLICY_MUST_HAVE_WARNING_IF_NOT_EXPIRE_WITHOUT_WARNING
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PWPOLICY_MUST_HAVE_WARNING_IF_NOT_EXPIRE_WITHOUT_WARNINGThe 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 -
ERR_ENQUEUE_BIND_IN_PROGRESS
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 -
ERR_ENQUEUE_STARTTLS_IN_PROGRESS
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 -
ERR_ENQUEUE_SASLBIND_IN_PROGRESS
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 -
ERR_ENQUEUE_MUST_CHANGE_PASSWORD
%s must change their password before it will be allowed to request any other operations -
ERR_PWPSTATE_CANNOT_DECODE_SUBENTRY_VALUE_AS_DN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PWPSTATE_CANNOT_DECODE_SUBENTRY_VALUE_AS_DNObject> An error occurred while attempting to decode the ds-pwp-password-policy-dn value "%s" in user entry "%s" as a DN: %s -
ERR_PWPSTATE_NO_SUCH_POLICY
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 -
ERR_PWPSTATE_CANNOT_DECODE_GENERALIZED_TIME
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_PWPSTATE_CANNOT_DECODE_GENERALIZED_TIMEObject, Object> An error occurred while attempting to decode value "%s" for attribute %s in user entry %s in accordance with the generalized time format: %s -
ERR_PWPSTATE_CANNOT_DECODE_BOOLEAN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PWPSTATE_CANNOT_DECODE_BOOLEANObject> Unable to decode value "%s" for attribute %s in user entry %s as a Boolean value -
ERR_ADD_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
The entry %s cannot be added due to insufficient access rights -
ERR_BIND_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
The user cannot bind due to insufficient access rights -
ERR_COMPARE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_COMPARE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe entry %s cannot be compared due to insufficient access rights -
ERR_DELETE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
The entry %s cannot be deleted due to insufficient access rights -
ERR_EXTENDED_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_EXTENDED_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe extended operation %s cannot be performed due to insufficient access rights -
ERR_MODDN_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
The entry %s cannot be renamed due to insufficient access rights -
ERR_MODIFY_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
The entry %s cannot be modified due to insufficient access rights -
ERR_SEARCH_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS
The entry %s cannot be searched due to insufficient access rights -
ERR_BIND_OPERATION_INSECURE_SIMPLE_BIND
Rejecting a simple bind request because the password policy requires secure authentication -
ERR_BIND_OPERATION_ACCOUNT_DISABLED
Rejecting a bind request because the account has been administratively disabled -
ERR_BIND_OPERATION_ACCOUNT_FAILURE_LOCKED
Rejecting a bind request because the account has been locked due to too many failed authentication attempts -
ERR_BIND_OPERATION_ACCOUNT_RESET_LOCKED
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 -
ERR_BIND_OPERATION_ACCOUNT_IDLE_LOCKED
Rejecting a bind request because the account has been locked after remaining idle for too long -
ERR_BIND_OPERATION_PASSWORD_EXPIRED
Rejecting a bind request because that user's password is expired -
ERR_PWPSTATE_CANNOT_UPDATE_USER_ENTRY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_CANNOT_UPDATE_USER_ENTRYAn error occurred while attempting to update password policy state information for user %s: %s -
ERR_BIND_OPERATION_INSECURE_SASL_BIND
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_BIND_OPERATION_INSECURE_SASL_BINDRejecting a SASL %s bind request for user %s because the password policy requires secure authentication -
ERR_BIND_OPERATION_ACCOUNT_EXPIRED
Rejecting a bind request because the account has expired -
ERR_MODIFY_PASSWORDS_CANNOT_HAVE_OPTIONS
Attributes used to hold user passwords are not allowed to have any attribute options -
ERR_MODIFY_NO_USER_PW_CHANGES
Users are not allowed to change their own passwords -
ERR_MODIFY_REQUIRE_SECURE_CHANGES
Password changes must be performed over a secure authentication channel -
ERR_MODIFY_WITHIN_MINIMUM_AGE
The password cannot be changed because it has not been long enough since the last password change -
ERR_MODIFY_MULTIPLE_VALUES_NOT_ALLOWED
Multiple password values are not allowed in user entries -
ERR_MODIFY_NO_PREENCODED_PASSWORDS
User passwords may not be provided in pre-encoded form -
ERR_MODIFY_INVALID_MOD_TYPE_FOR_PASSWORD
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_MODIFY_INVALID_MOD_TYPE_FOR_PASSWORDInvalid modification type %s attempted on password attribute %s -
ERR_MODIFY_NO_EXISTING_VALUES
The user entry does not have any existing passwords to remove -
ERR_MODIFY_INVALID_PASSWORD
The provided user password does not match any password in the user's entry -
ERR_MODIFY_PW_CHANGE_REQUIRES_CURRENT_PW
The password policy requires that user password changes include the current password in the request -
ERR_MODIFY_MULTIPLE_PASSWORDS_NOT_ALLOWED
The password change would result in multiple password values in the user entry, which is not allowed -
ERR_MODIFY_PW_VALIDATION_FAILED
The provided password value was rejected by a password validator: %s -
ERR_MODIFY_MUST_CHANGE_PASSWORD
%s must change their password before it will be allowed to perform any other operations -
WARN_BIND_PASSWORD_EXPIRING
The user password is about to expire (time to expiration: %s) -
ERR_BIND_ACCOUNT_TEMPORARILY_LOCKED
The account has been locked as a result of too many failed authentication attempts (time to unlock: %s) -
ERR_BIND_ACCOUNT_PERMANENTLY_LOCKED
The account has been locked as a result of too many failed authentication attempts. It may only be unlocked by an administrator -
INFO_MODIFY_PASSWORD_CHANGED
The user password has been changed -
INFO_MODIFY_PASSWORD_RESET
The user password has been administratively reset -
INFO_MODIFY_ACCOUNT_ENABLED
The user account has been administratively enabled -
INFO_MODIFY_ACCOUNT_DISABLED
The user account has been administratively disabled -
INFO_MODIFY_ACCOUNT_UNLOCKED
The user account has been administratively unlocked -
ERR_MODIFY_PASSWORD_EXISTS
The specified password value already exists in the user entry -
ERR_MODIFY_NO_MODIFICATIONS
Entry %s cannot be updated because the request did not contain any modifications -
INFO_DSCORE_DESCRIPTION_NODETACH
Do not detach from the terminal and continue running in the foreground. This option cannot be used with the -t, --timeout option -
INFO_DSCORE_TOOL_DESCRIPTION
This utility can be used to start the Directory Server, as well as to obtain the server version and other forms of general server information -
ERR_EXTENDED_UNSUPPORTED_CRITICAL_CONTROL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EXTENDED_UNSUPPORTED_CRITICAL_CONTROLUnable to process the request for extended operation %s because it contained an unsupported critical control with OID %s -
ERR_REGISTER_BACKEND_ALREADY_EXISTS
Unable to register backend %s with the Directory Server because another backend with the same backend ID is already registered -
ERR_REGISTER_BASEDN_ALREADY_EXISTS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_REGISTER_BASEDN_ALREADY_EXISTSObject> Unable to register base DN %s with the Directory Server for backend %s because that base DN is already registered for backend %s -
ERR_REGISTER_BASEDN_HIERARCHY_CONFLICT
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_REGISTER_BASEDN_HIERARCHY_CONFLICTObject> 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 -
ERR_REGISTER_BASEDN_DIFFERENT_PARENT_BASES
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_REGISTER_BASEDN_DIFFERENT_PARENT_BASESObject> 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 -
ERR_REGISTER_BASEDN_NEW_BASE_NOT_SUBORDINATE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_REGISTER_BASEDN_NEW_BASE_NOT_SUBORDINATEObject> 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 -
WARN_REGISTER_BASEDN_ENTRIES_IN_MULTIPLE_BACKENDS
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_REGISTER_BASEDN_ENTRIES_IN_MULTIPLE_BACKENDSObject> Backend %s already contains entry %s which has just been registered as the base DN for backend %s. These conflicting entries can cause unexpected or errant search results, and both backends should be reinitialized to ensure that each has the correct content -
ERR_DEREGISTER_BASEDN_NOT_REGISTERED
Unable to de-register base DN %s with the Directory Server because that base DN is not registered for any active backend -
WARN_DEREGISTER_BASEDN_MISSING_HIERARCHY
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_DEREGISTER_BASEDN_MISSING_HIERARCHYBase DN %s has been deregistered from the Directory Server for backend %s. This base DN had both superior and subordinate entries in other backends, and there might be inconsistent or unexpected behavior when accessing entries in this portion of the hierarchy because of the missing entries that had been held in the de-registered backend -
ERR_REJECT_UNAUTHENTICATED_OPERATION
Rejecting the requested operation because the connection has not been authenticated -
WARN_ADD_ATTR_IS_OBSOLETE
Entry "%s" cannot be added because it contains attribute type %s which is declared OBSOLETE in the server schema -
WARN_ADD_OC_IS_OBSOLETE
Entry "%s" cannot be added because it contains objectclass %s which is declared OBSOLETE in the server schema -
ERR_MODIFY_ATTR_IS_OBSOLETE
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 -
ERR_ENTRY_ADD_OBSOLETE_OC
Object class %s added to entry %s is marked OBSOLETE in the server schema -
ERR_MODDN_NEWRDN_ATTR_IS_OBSOLETE
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 -
WARN_CLIENTCONNECTION_DISCONNECT_DUE_TO_DELETE
public static LocalizableMessageDescriptor.Arg1<Object> WARN_CLIENTCONNECTION_DISCONNECT_DUE_TO_DELETETerminating the client connection because its associated authentication or authorization entry %s has been deleted -
ERR_MODIFY_PWRESET_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to reset user passwords -
ERR_COMPARE_CONFIG_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to access the server configuration -
ERR_ADD_CHANGE_PRIVILEGE_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to add entries that include privileges -
ERR_MODIFY_CHANGE_PRIVILEGE_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to modify the set of privileges contained in an entry -
ERR_PROXYAUTH_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to use the proxied authorization control -
ERR_DSCORE_ERROR_NODETACH_AND_WINDOW_SERVICE
OpenDJ is configured to run as a Windows service and it cannot run in no-detach mode -
ERR_ENTRY_DECODE_UNRECOGNIZED_VERSION
Unable to decode an entry because it had an unsupported entry version byte value of %s -
ERR_ENTRY_DECODE_EXCEPTION
Unable to decode an entry because an unexpected exception was caught during processing: %s -
ERR_CONTROL_INSUFFICIENT_ACCESS_RIGHTS
The request control with Object Identifier (OID) "%s" cannot be used due to insufficient access rights -
ERR_HOST_PORT_ALREADY_SPECIFIED
The connection handler %s is trying to use the listener %s which is already in use by another connection handler -
ERR_NOT_AVAILABLE_CONNECTION_HANDLERS
No enabled connection handler available -
ERR_ERROR_STARTING_CONNECTION_HANDLERS
Could not start connection handlers -
ERR_BIND_REJECTED_LOCKDOWN_MODE
Unable to process the non-root bind because the server is in lockdown mode -
WARN_DIRECTORY_SERVER_ENTERING_LOCKDOWN_MODE
The Directory Server is entering lockdown mode, in which clients will only be allowed to connect via a loopback address, and only root users will be allowed to process operations -
NOTE_DIRECTORY_SERVER_LEAVING_LOCKDOWN_MODE
The Directory Server is leaving lockdown mode and will resume normal operation -
NOTE_REJECT_OPERATION_IN_LOCKDOWN_MODE
Rejecting the requested operation because the server is in lockdown mode and will only accept requests from root users over loopback connections -
ERR_COMPRESSEDSCHEMA_UNRECOGNIZED_AD_TOKEN
Unable to decode the provided attribute because it used an undefined attribute description token %s -
ERR_COMPRESSEDSCHEMA_UNKNOWN_OC_TOKEN
Unable to decode the provided object class set because it used an undefined token %s -
ERR_ENTRYENCODECFG_INVALID_LENGTH
Unable to decode the provided entry encode configuration element because it has an invalid length -
ERR_BIND_OPERATION_WRITABILITY_DISABLED
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 -
ERR_MODIFY_PW_IN_HISTORY
The provided new password was found in the password history for the user -
WARN_BIND_MULTIPLE_USER_IDLE_TIME_LIMITS
There are multiple user-specific idle time limit values contained in user entry %s. The default server idle time limit will be used -
WARN_BIND_CANNOT_PROCESS_USER_IDLE_TIME_LIMIT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_BIND_CANNOT_PROCESS_USER_IDLE_TIME_LIMITThe user-specific idle time limit value %s contained in user entry %s could not be parsed as an integer. The default server idle time limit will be used -
INFO_IDLETIME_LIMIT_EXCEEDED
This connection has been terminated because it has remained idle for too long -
ERR_PWPOLICY_WARNING_INTERVAL_LARGER_THAN_MAX_AGE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PWPOLICY_WARNING_INTERVAL_LARGER_THAN_MAX_AGEThe 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 -
ERR_PWPOLICY_MIN_AGE_PLUS_WARNING_GREATER_THAN_MAX_AGE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PWPOLICY_MIN_AGE_PLUS_WARNING_GREATER_THAN_MAX_AGEThe 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 -
ERR_IDLETIME_DISCONNECT_ERROR
An error occurred while attempting to disconnect client connection %d: %s -
ERR_DIRCFG_SERVER_ALREADY_RUNNING
The Directory Server is currently running. Environment configuration changes are not allowed with the server running -
ERR_DIRCFG_INVALID_SERVER_ROOT
The specified server root directory '%s' is invalid. The specified path must exist and must be a directory -
ERR_DIRCFG_INVALID_CONFIG_FILE
The specified config file path '%s' is invalid. The specified path must exist and must be a file -
ERR_DIRCFG_INVALID_SCHEMA_DIRECTORY
The specified schema configuration directory '%s' is invalid. The specified path must exist and must be a directory -
ERR_CANNOT_SET_ENVIRONMENT_CONFIG_WHILE_RUNNING
The Directory Server is currently running. The environment configuration can not be altered while the server is online -
ERR_CRYPTOMGR_SSL_CONTEXT_CANNOT_INITIALIZE
An error occurred while attempting to initialize a SSL context for server to server communication: %s -
INFO_DSCORE_DESCRIPTION_LASTKNOWNGOODCFG
Attempt to start using the configuration that was in place at the last successful startup (if it is available) rather than using the current active configuration -
INFO_TRUSTSTORESYNC_ADMIN_SUFFIX_SEARCH_FAILED
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_TRUSTSTORESYNC_ADMIN_SUFFIX_SEARCH_FAILEDError while searching base %s to synchronize the trust store: %s -
ERR_TRUSTSTORESYNC_EXCEPTION
An error occurred in the trust store synchronization thread: %s -
INFO_TRUSTSTORESYNC_ADD_FAILED
Error while trying to add entry %s to the trust store: %s -
ERR_PWPOLICY_SCHEME_DOESNT_SUPPORT_AUTH
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPOLICY_SCHEME_DOESNT_SUPPORT_AUTHThe password storage scheme defined in configuration entry %s does not support the auth password syntax, which is used by password attribute %s -
ERR_PWPOLICY_DEPRECATED_SCHEME_NOT_AUTH
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPOLICY_DEPRECATED_SCHEME_NOT_AUTHPassword policy configuration entry %s references deprecated password storage scheme DN %s which does not support the auth password syntax -
WARN_GROUP_FILTER_NOT_INDEXED
The search filter "%s" used by group implementation %s is not indexed in backend %s. Backend initialization for this group implementation might take a very long time to complete -
ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_DIGEST
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_DIGESTCryptoManager cannot get the requested digest %s: %s -
ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MAC_ENGINE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MAC_ENGINECryptoManager cannot get the requested MAC engine %s: %s -
ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_ENCRYPTION_CIPHER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_ENCRYPTION_CIPHERCryptoManager cannot get the requested encryption cipher %s: %s -
ERR_CRYPTOMGR_CANNOT_GET_PREFERRED_KEY_WRAPPING_CIPHER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_CANNOT_GET_PREFERRED_KEY_WRAPPING_CIPHERCryptoManager cannot get the preferred key wrapping cipher: %s -
ERR_CRYPTOMGR_FAILED_TO_RETRIEVE_ADS_TRUSTSTORE_CERTS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_FAILED_TO_RETRIEVE_ADS_TRUSTSTORE_CERTSCryptoManager failed to retrieve the collection of instance-key-pair public-key-certificates from ADS container "%s": %s -
ERR_CRYPTOMGR_FAILED_TO_ENCODE_SYMMETRIC_KEY_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_FAILED_TO_ENCODE_SYMMETRIC_KEY_ATTRIBUTECryptoManager failed to encode symmetric key attribute value: %s -
ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_FIELD_COUNT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_FIELD_COUNTCryptoManager symmetric key attribute value "%s" syntax is invalid: incorrect number of fields -
ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_SYNTAX
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_SYNTAXNumber> CryptoManager symmetric key attribute value "%s" syntax is invalid. Parsing failed in field "%s" at offset %d -
ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_DECIPHER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_DECIPHERCryptoManager failed to decipher the wrapped secret-key value: %s -
ERR_CRYPTOMGR_REWRAP_SYMMETRIC_KEY_ATTRIBUTE_NO_WRAPPER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_REWRAP_SYMMETRIC_KEY_ATTRIBUTE_NO_WRAPPERCryptoManager cannot find the public-key-certificate (identifier "%s") requested for symmetric key re-encoding -
ERR_CRYPTOMGR_INVALID_KEY_IDENTIFIER_SYNTAX
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_INVALID_KEY_IDENTIFIER_SYNTAXCryptoManager failed to decode the key entry identifier "%s": %s -
ERR_CRYPTOMGR_GET_MAC_ENGINE_INVALID_MAC_ALGORITHM
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_GET_MAC_ENGINE_INVALID_MAC_ALGORITHMCryptoManager passed invalid MAC algorithm "%s": %s -
ERR_CRYPTOMGR_GET_MAC_ENGINE_CANNOT_INITIALIZE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_GET_MAC_ENGINE_CANNOT_INITIALIZECryptoManager failed to initialize MAC engine: %s -
ERR_CRYPTOMGR_GET_CIPHER_INVALID_CIPHER_TRANSFORMATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_GET_CIPHER_INVALID_CIPHER_TRANSFORMATIONCryptoManager passed invalid Cipher transformation "%s": %s -
ERR_CRYPTOMGR_GET_CIPHER_CANNOT_INITIALIZE
CryptoManager cannot initialize Cipher: %s -
ERR_CRYPTOMGR_GET_CIPHER_STREAM_PROLOGUE_WRITE_ERROR
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_GET_CIPHER_STREAM_PROLOGUE_WRITE_ERRORCryptoManager failed to write the stream prologue: %s -
ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_KEY_IDENTIFIER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_KEY_IDENTIFIERCryptoManager failed to decrypt the supplied data because it could not read the symmetric key identifier in the data prologue: %s -
ERR_CRYPTOMGR_DECRYPT_UNKNOWN_KEY_IDENTIFIER
CryptoManager failed to decrypt the supplied data because the symmetric key identifier in the data prologue does not match any known key entries -
ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_IV
CryptoManager failed to decrypt the supplied data because it could not read the cipher initialization vector in the data prologue -
ERR_CRYPTOMGR_DECRYPT_CIPHER_INPUT_STREAM_ERROR
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_DECRYPT_CIPHER_INPUT_STREAM_ERRORCryptoManager failed to decrypt the supplied data because there was an error reading from the input stream: %s -
ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_DECODE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_DECODECryptoManager 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 -
ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FIELD_MISMATCH
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FIELD_MISMATCHCryptoManager detected a field mismatch between the key entry to be imported and an entry in the key cache that share the key identifier "%s" -
ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_OTHER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_OTHERCryptoManager failed to import the symmetric key entry "%s": %s -
ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_ADD_KEY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_ADD_KEYCryptoManager 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 -
ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_ALGORITHM
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_ALGORITHMCryptoManager failed to instantiate a KeyGenerator for algorithm "%s": %s -
ERR_CRYPTOMGR_SYMMETRIC_KEY_ENTRY_ADD_FAILED
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_SYMMETRIC_KEY_ENTRY_ADD_FAILEDCryptoManager failed to add locally produced symmetric key entry "%s": %s -
ERR_CRYPTOMGR_FULL_CIPHER_TRANSFORMATION_REQUIRED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_FULL_CIPHER_TRANSFORMATION_REQUIREDCryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding" -
ERR_CRYPTOMGR_FULL_KEY_WRAPPING_TRANSFORMATION_REQUIRED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_FULL_KEY_WRAPPING_TRANSFORMATION_REQUIREDCryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding" -
ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_PROLOGUE_VERSION
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_PROLOGUE_VERSIONCryptoManager failed to decrypt the supplied data because it could not read the version number in the data prologue: %s -
ERR_CRYPTOMGR_DECRYPT_UNKNOWN_PROLOGUE_VERSION
public static LocalizableMessageDescriptor.Arg1<Number> ERR_CRYPTOMGR_DECRYPT_UNKNOWN_PROLOGUE_VERSIONCryptoManager failed to decrypt the supplied data because the version "%d" in the data prologue is unknown -
ERR_CRYPTOMGR_CANNOT_SIGN_WRAPPED_KEY_ENTRY
CryptoManager failed to sign the wrapped key entry: %s -
ERR_CRYPTOMGR_MISSING_WRAPPED_KEY_ENTRY_ATTRIBUTES
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_MISSING_WRAPPED_KEY_ENTRY_ATTRIBUTESThe wrapped key entry is missing the following attributes: %s -
ERR_CRYPTOMGR_UNABLE_TO_FIND_MASTER_KEY_PAIR_TO_UNWRAP_KEY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_UNABLE_TO_FIND_MASTER_KEY_PAIR_TO_UNWRAP_KEYCryptoManager 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 -
ERR_CRYPTOMGR_WRAPPED_KEY_ENTRY_SIGNATURE_DOES_NOT_MATCH
public static LocalizableMessageDescriptor.Arg0 ERR_CRYPTOMGR_WRAPPED_KEY_ENTRY_SIGNATURE_DOES_NOT_MATCHThe wrapped key entry signature does not match the entry content -
ERR_CRYPTOMGR_CANNOT_VERIFY_WRAPPED_KEY_ENTRY_SIGNATURE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CRYPTOMGR_CANNOT_VERIFY_WRAPPED_KEY_ENTRY_SIGNATURECryptoManager failed to verify the wrapped key entry signature: %s -
ERR_ADD_ENTRY_UNKNOWN_SUFFIX
The provided entry %s cannot be added because its suffix is not defined as one of the suffixes within the Directory Server -
NOTE_VERSION
%s -
NOTE_BUILD_ID
Build ID: %s -
ERR_CANNOT_CANCEL_START_TLS
Start TLS extended operations cannot be canceled -
ERR_CANNOT_CANCEL_CANCEL
Cancel extended operations can not be canceled -
ERR_MODDN_NEW_SUPERIOR_IN_SUBTREE
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 -
INFO_ERROR_SEARCH_SCOPE_NOT_ALLOWED
Unable to process operation because this search scope is not allowed in this network group -
ERR_ADD_ATTR_IS_INVALID_OPTION
Entry %s can not be added because BER encoding of %s attribute is not supported -
INFO_ERGONOMIC_SIZING_OF_WORKER_THREAD_POOL
No worker queue thread pool size specified: sizing automatically to use %d threads -
INFO_DSCORE_DESCRIPTION_TIMEOUT
Maximum time (in seconds) to wait before the command returns (the server continues the startup process, regardless). A value of '0' indicates an infinite timeout, which means that the command returns only when the server startup is completed. The default value is 60 seconds. This option cannot be used with the -N, --nodetach option -
ERR_DSCORE_ERROR_NODETACH_TIMEOUT
In no-detach mode, the 'timeout' option cannot be used -
WARN_SUBENTRY_FILTER_NOT_INDEXED
The search filter "%s" used by subentry manager is not indexed in backend %s. Backend initialization for subentry manager processing might take a very long time to complete -
ERR_PWPOLICY_NO_PWDPOLICY_OC
The subentry %s must have either the pwdPolicy or ds-pwp-password-policy objectclasses, which is required for the Directory Server password policy -
ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_LENGTH
public static LocalizableMessageDescriptor.Arg2<Number,Number> ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_LENGTHCryptoManager failed to initialize because the specified cipher key length "%d" is beyond the allowed cryptography strength "%d" in jurisdiction policy files -
ERR_DISK_SPACE_MONITOR_UPDATE_FAILED
Failed to update free disk space for directory %s: %s -
ERR_MAX_PSEARCH_LIMIT_EXCEEDED
The directory server is not accepting a new persistent search request because the server has already reached its limit -
ERR_SUBENTRY_WRITE_INSUFFICIENT_PRIVILEGES
This operation involves LDAP subentries which you do not have sufficient privileges to administer -
INFO_DISCONNECT_DUE_TO_INVALID_CREDENTIALS
Invalid Credentials -
WARN_ADD_OP_INVALID_SYNTAX_NO_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_ADD_OP_INVALID_SYNTAX_NO_VALUEObject> Entry "%s" contains a value for attribute %s that is invalid according to the syntax for that attribute: %s -
ERR_MODIFY_ADD_INVALID_SYNTAX_NO_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_MODIFY_ADD_INVALID_SYNTAX_NO_VALUEObject> When attempting to modify entry %s, one value for attribute %s was found to be invalid according to the associated syntax: %s -
ERR_MODIFY_REPLACE_INVALID_SYNTAX_NO_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_MODIFY_REPLACE_INVALID_SYNTAX_NO_VALUEObject> 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 -
ERR_PWPOLICY_UNKNOWN_VALIDATOR
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PWPOLICY_UNKNOWN_VALIDATORObject> The password policy definition contained in configuration entry "%s" is invalid because the password validator "%s" specified in attribute "%s" cannot be found -
ERR_PWPOLICY_REJECT_DUE_TO_UNKNOWN_VALIDATOR_REASON
The password could not be validated because of misconfiguration. Please contact the administrator -
ERR_PWPOLICY_REJECT_DUE_TO_UNKNOWN_VALIDATOR_LOG
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PWPOLICY_REJECT_DUE_TO_UNKNOWN_VALIDATOR_LOGObject> 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 -
ERR_DISK_SPACE_GET_MOUNT_POINT
Could not get filesystem for directory %s: %s -
ERR_DISK_SPACE_LOW_THRESHOLD_REACHED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DISK_SPACE_LOW_THRESHOLD_REACHEDObject> 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 -
ERR_DISK_SPACE_FULL_THRESHOLD_REACHED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DISK_SPACE_FULL_THRESHOLD_REACHEDObject> 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 -
NOTE_DISK_SPACE_RESTORED
The free space (%s) on the disk containing directory "%s" is now above the low threshold for the following subsystems: %s -
ERR_CANNOT_HASH_DATA
Cannot properly use SHA-1 using the java provider. Verify java.security is properly configured -
ERR_MISSING_ADMIN_BACKENDS
Cannot complete initialization of server's backends because the root and administrative backends have not been initialized yet -
ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_ADD_MECHANISM
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_ADD_MECHANISMAn error occurred while adding Service Discovery Mechanism '%s': %s -
ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_LISTENER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_LISTENERRegistering Service Discovery Manager's listener failed : %s -
ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_INIT_MECHANISM
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_INIT_MECHANISMDiscovery mechanism '%s' initialization failed : %s -
WARN_SERVICE_DISCOVERY_REPLICATION_MECHANISM_WRONG_REPLICA
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_SERVICE_DISCOVERY_REPLICATION_MECHANISM_WRONG_REPLICAReplication server '%s' references server '%s' that could not be parsed correctly; the definition will be skipped -
ERR_SERVICE_DISCOVERY_MECHANISM_CANNOT_CREATE_SSL_CONTEXT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SERVICE_DISCOVERY_MECHANISM_CANNOT_CREATE_SSL_CONTEXTError occurred while creating an SSL context for service discovery mechanism '%s' : %s -
ERR_SERVICE_DISCOVERY_REPLICATION_MECHANISM_CANNOT_RETRIEVE_REPLICAS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SERVICE_DISCOVERY_REPLICATION_MECHANISM_CANNOT_RETRIEVE_REPLICASObject> Could not retrieve the list of replicas from replication server '%s' for replication server group '%s'. Exception : %s -
ERR_SERVICE_DISCOVERY_REPLICATION_MECHANISM_CANNOT_AUTO_CONFIGURE_REPLICA
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SERVICE_DISCOVERY_REPLICATION_MECHANISM_CANNOT_AUTO_CONFIGURE_REPLICAObject> Could not retrieve auto-configuration data from directory server '%s' for replication server group '%s'. Exception : %s" -
ERR_SERVICE_DISCOVERY_MECHANISM_PARTITION_CHANGE_REFRESH_FAILED
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SERVICE_DISCOVERY_MECHANISM_PARTITION_CHANGE_REFRESH_FAILEDService discovery mechanism '%s' failed to refresh the partition information. Exception : %s", -
WARN_SERVICE_DISCOVERY_REPLICATION_MECHANISM_MISSING_HOSTNAME
public static LocalizableMessageDescriptor.Arg1<Object> WARN_SERVICE_DISCOVERY_REPLICATION_MECHANISM_MISSING_HOSTNAMESettings for Replica '%s' should provide a hostname -
WARN_SERVICE_DISCOVERY_REPLICATION_MECHANISM_CANNOT_CONNECT_TO_REPLICA
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_SERVICE_DISCOVERY_REPLICATION_MECHANISM_CANNOT_CONNECT_TO_REPLICAObject> Cannot connect to replica '%s' for replication service discovery mechanism '%s'. The replica entry is: %s -
WARN_SERVICE_DISCOVERY_STATIC_MECHANISM_CANNOT_GATHER_NAMING_CONTEXTS
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_SERVICE_DISCOVERY_STATIC_MECHANISM_CANNOT_GATHER_NAMING_CONTEXTSCannot gather naming contexts from server %s: %s -
WARN_SERVICE_DISCOVERY_SCHEDULED_TASK_FAILURE
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_SERVICE_DISCOVERY_SCHEDULED_TASK_FAILUREScheduled discovery '%s' failed : %s -
ERR_SERVICE_DISCOVERY_MECHANISM_CONNECTION_OPTIONS_CHANGE_REFRESH_FAILED
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SERVICE_DISCOVERY_MECHANISM_CONNECTION_OPTIONS_CHANGE_REFRESH_FAILEDService discovery mechanism '%s' failed to refresh the connection options. Exception : %s", -
ERR_DISK_SPACE_THRESHOLDS_PER_SUBSYSTEM
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DISK_SPACE_THRESHOLDS_PER_SUBSYSTEMObject> "%s" (low=%s, full=%s) -
ERR_MONITOR_BACKEND_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to read directory server monitoring information -
WARN_BIND_MULTIPLE_USER_CURSOR_ENTRY_LIMITS
There are multiple user-specific cursor entry limit values contained in user entry '%s'. The default server cursor entry limit will be used -
WARN_BIND_CANNOT_PROCESS_USER_CURSOR_ENTRY_LIMIT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_BIND_CANNOT_PROCESS_USER_CURSOR_ENTRY_LIMITThe user-specific cursor entry limit value '%s' contained in user entry '%s' could not be parsed as an integer. The default server cursor entry limit will be used -
ERR_ADD_PARENT_IS_SUBENTRY
Entry %s cannot be added because its parent entry %s is a subentry -
INFO_DISCONNECT_LOCKDOWN_MODE
Server in lockdown mode -
ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MASTER_KEY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MASTER_KEYThe 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 -
ERR_CRYPTOMGR_CANNOT_ENCODE_DUE_TO_MISSING_MASTER_KEY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CRYPTOMGR_CANNOT_ENCODE_DUE_TO_MISSING_MASTER_KEYThe 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 -
ERR_CRYPTOMGR_UNABLE_TO_OBTAIN_DEPLOYMENT_PEPPER
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 -
ERR_PWPOLICY_UNKNOWN_STORAGE_SCHEMES
No enabled password storage schemes in '%s' in subentry '%s' -
ERR_PWPOLICY_CANT_MIX_VALIDATORS
Cannot use both pwdValidatorPolicy and ds-pwp-validator in subentry '%s' -
ERR_PWPOLICY_CANNOT_READ_DICTIONARY_DATA
The dictionary data could not be decompressed: %s -
ERR_PWPOLICY_INVALID_DICTIONARY_CONFIG
The dictionary validator configuration is invalid -
WARN_MULTIPLE_PWD_POLICY_SUBENTRIES
public static LocalizableMessageDescriptor.Arg3<Number,Object, WARN_MULTIPLE_PWD_POLICY_SUBENTRIESObject> Found %d conflicting password policy subentries for user %s, used %s -
ERR_CIPHERSERVICE_NULL_ENCRYPTION_KEY
Requested cipher for a non existing cipher key: cryptographic services were not properly initialized, programming error -
ERR_CIPHERSERVICE_DECODED_KEY_IS_NOT_SUPPORTED
public static LocalizableMessageDescriptor.Arg1<Number> ERR_CIPHERSERVICE_DECODED_KEY_IS_NOT_SUPPORTEDType %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 -
ERR_PWPOLICY_NO_MIXING_OCS
The subentry %s cannot use both %s and %s objectclasses -
ERR_PWPOLICY_OLD_VALIDATOR_OC
The subentry %s using the %s objectclass cannot define validators using the old %s objectclass -
ERR_PWPOLICY_NEW_VALIDATORS_OC
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PWPOLICY_NEW_VALIDATORS_OCObject> The subentry %s using the %s objectclass cannot define validators using the new %s objectclass -
ERR_PWPOLICY_INVALID_DURATION
The value for the '%s' attribute is not a valid duration -
ERR_PWPOLICY_INVALID_INTEGER
The value for the '%s' attribute is not a valid integer -
ERR_PWPOLICY_INVALID_BOOLEAN
The value for the '%s' attribute is not a valid boolean -
ERR_PWPOLICY_INVALID_GENERALIZEDTIME
The value for the '%s' attribute is not a valid time -
ERR_PWPOLICY_INVALID_STRING
The value for the '%s' attribute is not a valid string -
ERR_PWPOLICY_UNDEFINED_ATTRIBUTE
The value for the '%s' attribute is not a valid attribute -
ERR_PWPOLICY_INVALID_STRINGS
The values for the '%s' attribute are not valid strings -
ERR_PWPOLICY_INVALID_STATE_UPDATE_FAILURE_POLICY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PWPOLICY_INVALID_STATE_UPDATE_FAILURE_POLICYThe value for the '%s' attribute is not a valid state update failure policy -
ERR_PWPOLICY_UNDEFINED_ATTRIBUTES
A values for the '%s' attribute is not a valid attribute name -
ERR_ERROR_STARTING_CONNECTION_HANDLER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_ERROR_STARTING_CONNECTION_HANDLERObject> Could not start connection handler %s with listen addresses "%s". The error was: %s -
INFO_GROUP_MANAGER_STARTED
public static LocalizableMessageDescriptor.Arg4<Number,Number, INFO_GROUP_MANAGER_STARTEDNumber, Number> Registered %d static groups, %d dynamic groups and %d virtual static groups. The static group cache is using %d bytes of memory -
INFO_LIST_OF_LOGGING_CATEGORIES
The following logging categories are defined for the server: %s -
ERR_PWSCHEME_CANNOT_INITIALIZE_MESSAGE_DIGEST
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWSCHEME_CANNOT_INITIALIZE_MESSAGE_DIGESTAn error occurred while attempting to initialize the message digest generator for the %s algorithm: %s -
ERR_PWSCHEME_CANNOT_BASE64_DECODE_STORED_PASSWORD
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWSCHEME_CANNOT_BASE64_DECODE_STORED_PASSWORDAn error occurred while attempting to base64-decode the password value %s: %s -
ERR_PWSCHEME_NOT_REVERSIBLE
The %s password storage scheme is not reversible, so it is impossible to recover the plaintext version of an encoded password -
ERR_JMX_ALERT_HANDLER_CANNOT_REGISTER
An error occurred while trying to register the JMX alert handler with the MBean server: %s -
ERR_PWSCHEME_CANNOT_ENCODE_PASSWORD
An unexpected error occurred while attempting to encode a password using the storage scheme defined in class %s: %s -
ERR_CACHE_INVALID_INCLUDE_FILTER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CACHE_INVALID_INCLUDE_FILTERObject> 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 -
ERR_CACHE_INVALID_EXCLUDE_FILTER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CACHE_INVALID_EXCLUDE_FILTERObject> 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 -
ERR_FIFOCACHE_CANNOT_INITIALIZE
A fatal error occurred while trying to initialize fifo entry cache: %s -
ERR_SOFTREFCACHE_CANNOT_INITIALIZE
A fatal error occurred while trying to initialize soft reference entry cache: %s -
ERR_EXTOP_PASSMOD_CANNOT_DECODE_REQUEST
An unexpected error occurred while attempting to decode the password modify extended request sequence: %s -
ERR_EXTOP_PASSMOD_NO_AUTH_OR_USERID
The password modify extended request cannot be processed because it does not contain an authorization ID and the underlying connection is not authenticated -
ERR_EXTOP_PASSMOD_CANNOT_LOCK_USER_ENTRY
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 -
ERR_EXTOP_PASSMOD_CANNOT_DECODE_AUTHZ_DN
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 -
ERR_EXTOP_PASSMOD_INVALID_AUTHZID_STRING
The password modify extended request cannot be processed because it contained an invalid userIdentity field. The provided userIdentity string was "%s" -
ERR_EXTOP_PASSMOD_NO_USER_ENTRY_BY_AUTHZID
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" -
ERR_EXTOP_PASSMOD_INVALID_OLD_PASSWORD
The password modify extended operation cannot be processed because the current password provided for the user is invalid -
ERR_FILE_KEYMANAGER_NO_SUCH_FILE
The keystore file %s specified in attribute ds-cfg-key-store-file of configuration entry %s does not exist -
ERR_FILE_KEYMANAGER_CANNOT_LOAD
An error occurred while trying to load the keystore contents from file %s: %s -
ERR_FILE_KEYMANAGER_INVALID_TYPE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_FILE_KEYMANAGER_INVALID_TYPEObject> The keystore type %s specified in attribute ds-cfg-key-store-type of configuration entry %s is not valid: %s -
ERR_PKCS11_KEYMANAGER_CANNOT_LOAD
An error occurred while trying to access the PKCS#11 key manager: %s -
ERR_FILE_KEYMANAGER_CANNOT_CREATE_FACTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILE_KEYMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a key manager factory to access the contents of keystore file %s: %s -
ERR_PKCS11_KEYMANAGER_CANNOT_CREATE_FACTORY
An error occurred while trying to create a key manager factory to access the contents of the PKCS#11 keystore: %s -
ERR_FILE_TRUSTMANAGER_NO_SUCH_FILE
The trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not exist -
ERR_FILE_TRUSTMANAGER_CANNOT_LOAD
An error occurred while trying to load the trust store contents from file %s: %s -
ERR_FILE_TRUSTMANAGER_CANNOT_CREATE_FACTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_FILE_TRUSTMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %s -
ERR_FILE_TRUSTMANAGER_INVALID_TYPE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_FILE_TRUSTMANAGER_INVALID_TYPEObject> The trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s -
ERR_SEDCM_NO_PEER_CERTIFICATE
Could not map the provided certificate chain to a user entry because no peer certificate was available -
ERR_SEDCM_PEER_CERT_NOT_X509
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) -
ERR_SEDCM_CANNOT_DECODE_SUBJECT_AS_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SEDCM_CANNOT_DECODE_SUBJECT_AS_DNCould not map the provided certificate chain to a user because the peer certificate subject "%s" could not be decoded as an LDAP DN: %s -
ERR_SEDCM_CANNOT_GET_ENTRY
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 -
ERR_SEDCM_NO_USER_FOR_DN
Could not map the provided certificate chain to a user because no user entry exists with a DN of %s -
ERR_SASLEXTERNAL_NO_CLIENT_CONNECTION
The SASL EXTERNAL bind request could not be processed because the associated bind request does not have a reference to the client connection -
ERR_SASLEXTERNAL_NOT_LDAP_CLIENT_INSTANCE
The SASL EXTERNAL bind request could not be processed because the associated client connection instance is not an instance of LDAPClientConnection -
ERR_SASLEXTERNAL_NO_CLIENT_CERT
The SASL EXTERNAL bind request could not be processed because the client did not present a certificate chain during SSL/TLS negotiation -
ERR_SASLEXTERNAL_NO_MAPPING
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 -
ERR_STARTTLS_NOT_TLS_CAPABLE
StartTLS cannot be used on this client connection because this connection type is not capable of using StartTLS to protect its communication -
ERR_SASLEXTERNAL_NO_CERT_IN_ENTRY
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 -
ERR_SASLEXTERNAL_PEER_CERT_NOT_FOUND
Unable to authenticate via SASL EXTERNAL because the mapped user entry %s did not contain the peer certificate presented by the client -
ERR_SASLEXTERNAL_CANNOT_VALIDATE_CERT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SASLEXTERNAL_CANNOT_VALIDATE_CERTAn error occurred while attempting to validate the peer certificate presented by the client with a certificate from the user's entry %s: %s -
ERR_SASLPLAIN_NO_SASL_CREDENTIALS
SASL PLAIN authentication requires that SASL credentials be provided but none were included in the bind request -
ERR_SASLPLAIN_NO_NULLS_IN_CREDENTIALS
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 -
ERR_SASLPLAIN_NO_SECOND_NULL
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 -
ERR_SASLPLAIN_ZERO_LENGTH_AUTHCID
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 -
ERR_SASLPLAIN_ZERO_LENGTH_PASSWORD
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 -
ERR_SASLPLAIN_CANNOT_DECODE_AUTHCID_AS_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SASLPLAIN_CANNOT_DECODE_AUTHCID_AS_DNAn error occurred while attempting to decode the SASL PLAIN authentication ID "%s" because it appeared to contain a DN but DN decoding failed: %s -
ERR_SASLPLAIN_AUTHCID_IS_NULL_DN
The authentication ID in the SASL PLAIN bind request appears to be an empty DN. This is not allowed -
ERR_SASLPLAIN_CANNOT_GET_ENTRY_BY_DN
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 -
ERR_SASLPLAIN_NO_MATCHING_ENTRIES
The server was not able to find any user entries for the provided authentication ID of %s -
ERR_SASLPLAIN_INVALID_PASSWORD
The provided password is invalid -
INFO_SASL_UNSUPPORTED_CALLBACK
An unsupported or unexpected callback was provided to the SASL server for use during %s authentication: %s -
ERR_SASL_CANNOT_GET_SERVER_FQDN
An unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %s -
ERR_SASL_CONTEXT_CREATE_ERROR
An unexpected error occurred while trying to create an %s context: %s -
ERR_SASL_CANNOT_DECODE_USERNAME_AS_DN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SASL_CANNOT_DECODE_USERNAME_AS_DNObject> An error occurred while attempting to decode the SASL %s username "%s" because it appeared to contain a DN but DN decoding failed: %s -
ERR_SASL_USERNAME_IS_NULL_DN
The username in the SASL %s bind request appears to be an empty DN. This is not allowed -
ERR_SASL_CANNOT_GET_ENTRY_BY_DN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SASL_CANNOT_GET_ENTRY_BY_DNObject> An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL %s bind request: %s -
ERR_SASL_ZERO_LENGTH_USERNAME
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 -
ERR_SASL_NO_MATCHING_ENTRIES
The server was not able to find any user entries for the provided username of %s -
ERR_SASL_AUTHZID_INVALID_DN
The provided authorization ID %s contained an invalid DN: %s -
ERR_SASL_AUTHZID_NO_SUCH_ENTRY
The entry %s specified as the authorization identity does not exist -
ERR_SASL_AUTHZID_CANNOT_GET_ENTRY
The entry %s specified as the authorization identity could not be retrieved: %s -
ERR_SASL_AUTHZID_NO_MAPPED_ENTRY
The server was unable to find any entry corresponding to authorization ID %s -
ERR_SASL_CANNOT_GET_REVERSIBLE_PASSWORDS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SASL_CANNOT_GET_REVERSIBLE_PASSWORDSObject> An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL %s authentication: %s -
ERR_SASL_NO_REVERSIBLE_PASSWORDS
SASL %s authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form -
ERR_SASL_PROTOCOL_ERROR
SASL %s protocol error: %s -
ERR_SASL_AUTHZID_INSUFFICIENT_PRIVILEGES
The authenticating user %s does not have sufficient privileges to assume a different authorization identity -
ERR_SASL_AUTHZID_INSUFFICIENT_ACCESS
The authenticating user %s does not have sufficient access to assume a different authorization identity -
ERR_SASL_AUTHENTRY_NO_MAPPED_ENTRY
The server was unable to find any entry corresponding to authentication ID %s -
ERR_SASLGSSAPI_KDC_REALM_NOT_DEFINED
The server was unable to because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be defined or neither defined -
ERR_SASL_CANNOT_MAP_AUTHENTRY
An error occurred while attempting to map authorization ID %s to a user entry: %s -
ERR_SASLGSSAPI_CANNOT_CREATE_JAAS_CONFIG
An error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %s -
ERR_SASLGSSAPI_CANNOT_CREATE_LOGIN_CONTEXT
An error occurred while attempting to create the JAAS login context for GSSAPI authentication: %s -
INFO_GSSAPI_PRINCIPAL_NAME
GSSAPI mechanism using a principal name of: %s -
INFO_GSSAPI_SERVER_FQDN
GSSAPI SASL mechanism using a server fully qualified domain name of: %s -
INFO_DIGEST_MD5_REALM
DIGEST-MD5 SASL mechanism using a realm of: %s -
NOTE_DIGEST_MD5_SERVER_FQDN
DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: %s -
ERR_EXTOP_WHOAMI_PROXYAUTH_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to use the proxied authorization control -
ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_FOR_ADMIN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINObject> ID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s' -
ERR_EXACTMAP_INEFFICIENT_SEARCH
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 -
ERR_EXACTMAP_SEARCH_FAILED
An internal failure occurred while attempting to resolve ID string %s to a user entry: %s -
ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTID string %s mapped to multiple users -
ERR_SASLDIGESTMD5_CANNOT_MAP_USERNAME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SASLDIGESTMD5_CANNOT_MAP_USERNAMEAn error occurred while attempting to map username %s to a Directory Server entry: %s -
ERR_SASLPLAIN_CANNOT_MAP_USERNAME
An error occurred while attempting to map username %s to a Directory Server entry: %s -
ERR_EXTOP_CANCEL_NO_REQUEST_VALUE
Unable to process the cancel request because the extended operation did not include a request value -
ERR_EXTOP_CANCEL_CANNOT_DECODE_REQUEST_VALUE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_EXTOP_CANCEL_CANNOT_DECODE_REQUEST_VALUEAn error occurred while attempting to decode the value of the cancel extended request: %s -
INFO_EXTOP_CANCEL_REASON
Processing on this operation was terminated as a result of receiving a cancel request (message ID %d) -
ERR_PWSCHEME_DOES_NOT_SUPPORT_AUTH_PASSWORD
Password storage scheme %s does not support use with the authentication password attribute syntax -
ERR_PWLENGTHVALIDATOR_MIN_GREATER_THAN_MAX
public static LocalizableMessageDescriptor.Arg2<Number,Number> ERR_PWLENGTHVALIDATOR_MIN_GREATER_THAN_MAXThe configured minimum password length of %d characters is greater than the configured maximum password length of %d -
ERR_PWLENGTHVALIDATOR_TOO_SHORT
The provided password is shorter than the minimum required length of %d characters -
ERR_PWLENGTHVALIDATOR_TOO_LONG
The provided password is longer than the maximum allowed length of %d characters -
ERR_RANDOMPWGEN_NO_CHARSETS
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 -
ERR_RANDOMPWGEN_CHARSET_NAME_CONFLICT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_RANDOMPWGEN_CHARSET_NAME_CONFLICTConfiguration entry "%s" contains multiple definitions for the %s character set -
ERR_RANDOMPWGEN_CANNOT_DETERMINE_CHARSETS
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 -
ERR_RANDOMPWGEN_UNKNOWN_CHARSET
The password format string "%s" references an undefined character set "%s" -
ERR_RANDOMPWGEN_INVALID_PWFORMAT
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 -
ERR_RANDOMPWGEN_CANNOT_DETERMINE_PWFORMAT
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 -
ERR_EXTOP_PASSMOD_CANNOT_GET_PW_POLICY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EXTOP_PASSMOD_CANNOT_GET_PW_POLICYAn error occurred while attempting to get the password policy for user %s: %s -
ERR_EXTOP_PASSMOD_REQUIRE_CURRENT_PW
The current password must be provided for self password changes -
ERR_EXTOP_PASSMOD_SECURE_AUTH_REQUIRED
Password modify operations that supply the user's current password must be performed over a secure communication channel -
ERR_EXTOP_PASSMOD_USER_PW_CHANGES_NOT_ALLOWED
End users are not allowed to change their passwords -
ERR_EXTOP_PASSMOD_SECURE_CHANGES_REQUIRED
Password changes must be performed over a secure communication channel -
ERR_EXTOP_PASSMOD_IN_MIN_AGE
The password cannot be changed because the previous password change was too recent -
ERR_EXTOP_PASSMOD_PASSWORD_IS_EXPIRED
The password cannot be changed because it is expired -
ERR_EXTOP_PASSMOD_NO_PW_GENERATOR
No new password was provided, and no password generator has been defined that may be used to automatically create a new password -
ERR_EXTOP_PASSMOD_CANNOT_GENERATE_PW
An error occurred while attempting to create a new password using the password generator: %s -
ERR_EXTOP_PASSMOD_PRE_ENCODED_NOT_ALLOWED
The password policy does not allow users to supply pre-encoded passwords -
ERR_EXTOP_PASSMOD_UNACCEPTABLE_PW
The provided new password failed the validation checks defined in the server: %s -
ERR_EXTOP_PASSMOD_CANNOT_ENCODE_PASSWORD
Unable to encode the provided password using the default scheme(s): %s -
ERR_EXTOP_PASSMOD_CANNOT_DETERMINE_ID_MAPPER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EXTOP_PASSMOD_CANNOT_DETERMINE_ID_MAPPERAn 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 -
ERR_EXTOP_PASSMOD_CANNOT_MAP_USER
The provided authorization ID string "%s" could not be mapped to any user in the directory -
ERR_EXTOP_PASSMOD_ERROR_MAPPING_USER
An error occurred while attempting to map authorization ID string "%s" to a user entry: %s -
NOTE_ERRORLOG_ACCTNOTHANDLER_NOTIFICATION
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_ERRORLOG_ACCTNOTHANDLER_NOTIFICATIONNumber, Object> Account-Status-Notification type='%s' userdn='%s' id=%d msg='%s' -
ERR_SASLPLAIN_CANNOT_CHECK_PASSWORD_VALIDITY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SASLPLAIN_CANNOT_CHECK_PASSWORD_VALIDITYAn error occurred while attempting to verify the password for user %s during SASL PLAIN authentication: %s -
WARN_EXTOP_PASSMOD_NOOP
The password modify operation was not actually performed in the Directory Server because the LDAP no-op control was present in the request -
ERR_EXTOP_PASSMOD_ACCOUNT_DISABLED
The user account has been administratively disabled -
ERR_EXTOP_PASSMOD_ACCOUNT_LOCKED
The user account is locked -
ERR_STATICGROUP_NO_VALID_OC
Entry %s cannot be parsed as a valid static group because it does not contain the groupOfEntries, groupOfNames or groupOfUniqueNames object classes -
ERR_EXTOP_PASSMOD_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform password reset operations -
ERR_SASLDIGESTMD5_EMPTY_AUTHZID
The provided authorization ID was empty, which is not allowed for DIGEST-MD5 authentication -
ERR_SASLPLAIN_AUTHZID_INVALID_DN
The provided authorization ID %s contained an invalid DN: %s -
ERR_SASLPLAIN_AUTHZID_INSUFFICIENT_PRIVILEGES
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SASLPLAIN_AUTHZID_INSUFFICIENT_PRIVILEGESThe authenticating user %s does not have sufficient privileges to specify an alternate authorization ID -
ERR_SASLPLAIN_AUTHZID_NO_SUCH_ENTRY
The entry corresponding to authorization DN %s does not exist in the Directory Server -
ERR_SASLPLAIN_AUTHZID_CANNOT_GET_ENTRY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SASLPLAIN_AUTHZID_CANNOT_GET_ENTRYAn error occurred while attempting to retrieve entry %s specified as the authorization ID: %s -
ERR_SASLPLAIN_AUTHZID_NO_MAPPED_ENTRY
No entry corresponding to authorization ID %s was found in the server -
ERR_SASLPLAIN_AUTHZID_CANNOT_MAP_AUTHZID
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SASLPLAIN_AUTHZID_CANNOT_MAP_AUTHZIDAn error occurred while attempting to map authorization ID %s to a user entry: %s -
ERR_SDTUACM_NO_PEER_CERTIFICATE
Could not map the provided certificate chain to a user entry because no peer certificate was available -
ERR_SDTUACM_PEER_CERT_NOT_X509
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) -
ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMIN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINObject> The certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s' -
ERR_SATUACM_INVALID_MAP_FORMAT
Configuration entry %s has value '%s' which violates the format required for attribute mappings. The expected format is 'certattr:userattr' -
ERR_SATUACM_DUPLICATE_CERT_ATTR
Configuration entry %s contains multiple mappings for certificate attribute %s -
ERR_SATUACM_NO_SUCH_ATTR
Mapping %s in configuration entry %s references attribute %s which is not defined in the server schema -
ERR_SATUACM_DUPLICATE_USER_ATTR
Configuration entry %s contains multiple mappings for user attribute %s -
ERR_SATUACM_NO_PEER_CERTIFICATE
Could not map the provided certificate chain to a user entry because no peer certificate was available -
ERR_SATUACM_PEER_CERT_NOT_X509
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) -
ERR_SATUACM_CANNOT_DECODE_SUBJECT_AS_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SATUACM_CANNOT_DECODE_SUBJECT_AS_DNUnable to decode peer certificate subject %s as a DN: %s -
ERR_SATUACM_NO_MAPPABLE_ATTRIBUTES
Peer certificate subject %s does not contain any attributes for which a mapping has been established -
ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMIN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINObject> The certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s' -
ERR_FCM_NO_PEER_CERTIFICATE
Could not map the provided certificate chain to a user entry because no peer certificate was available -
ERR_FCM_PEER_CERT_NOT_X509
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) -
ERR_FCM_CANNOT_CALCULATE_FINGERPRINT
An error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %s -
ERR_FCM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMIN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_FCM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINObject> The certificate with fingerprint '%s' could not be mapped to exactly one user. It maps at least to both '%s' and '%s' -
ERR_DYNAMICGROUP_CANNOT_DECODE_MEMBERURL
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DYNAMICGROUP_CANNOT_DECODE_MEMBERURLObject> Unable to decode value "%s" in entry "%s" as an LDAP URL: %s -
ERR_DYNAMICGROUP_ALTERING_MEMBERS_NOT_SUPPORTED
Dynamic groups do not support explicitly altering their membership -
WARN_DYNAMICGROUP_NONEXISTENT_BASE_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_DYNAMICGROUP_NONEXISTENT_BASE_DNBase DN %s specified in dynamic group %s does not exist in the server -
ERR_DYNAMICGROUP_INTERNAL_SEARCH_FAILED
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_DYNAMICGROUP_INTERNAL_SEARCH_FAILEDObject, Object, Object> An error occurred while attempting to 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 -
ERR_PWDIFFERENCEVALIDATOR_TOO_SMALL
The provided password differs less than the minimum required difference of %d characters -
ERR_REPEATEDCHARS_VALIDATOR_TOO_MANY_CONSECUTIVE
public static LocalizableMessageDescriptor.Arg1<Number> ERR_REPEATEDCHARS_VALIDATOR_TOO_MANY_CONSECUTIVEThe 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 -
ERR_UNIQUECHARS_VALIDATOR_NOT_ENOUGH_UNIQUE_CHARS
public static LocalizableMessageDescriptor.Arg1<Number> ERR_UNIQUECHARS_VALIDATOR_NOT_ENOUGH_UNIQUE_CHARSThe provided password does not contain enough unique characters. The minimum number of unique characters that may appear in a user password is %d -
ERR_VATTR_NOT_SEARCHABLE
The %s attribute is not searchable and should not be included in otherwise unindexed search filters -
ERR_DICTIONARY_VALIDATOR_PASSWORD_IN_DICTIONARY
The provided password contained a word from the server's dictionary -
ERR_DICTIONARY_VALIDATOR_NO_SUCH_FILE
The specified dictionary file %s does not exist -
ERR_DICTIONARY_VALIDATOR_CANNOT_READ_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DICTIONARY_VALIDATOR_CANNOT_READ_FILEAn error occurred while attempting to load the dictionary from file %s: %s -
ERR_ATTRVALUE_VALIDATOR_PASSWORD_IN_ENTRY
The provided password was found in another attribute in the user entry -
ERR_CHARSET_VALIDATOR_ILLEGAL_CHARACTER
The provided password contained character '%s' which is not allowed for use in passwords -
ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_SET
public static LocalizableMessageDescriptor.Arg2<Object,Number> ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_SETThe 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 -
ERR_CHARSET_VALIDATOR_NO_SET_COLON
The provided character set definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character set -
ERR_CHARSET_VALIDATOR_NO_SET_CHARS
The provided character set definition '%s' is invalid because the provided character set is empty -
ERR_CHARSET_VALIDATOR_INVALID_SET_COUNT
The provided character set definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero -
ERR_CHARSET_VALIDATOR_DUPLICATE_CHAR
The provided character set definition '%s' is invalid because it contains character '%s' which has already been used -
ERR_VIRTUAL_STATIC_GROUP_MULTIPLE_TARGETS
The virtual static group defined in entry %s contains multiple target group DNs, but only one is allowed -
ERR_VIRTUAL_STATIC_GROUP_CANNOT_DECODE_TARGET
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_VIRTUAL_STATIC_GROUP_CANNOT_DECODE_TARGETObject> Unable to decode "%s" as the target DN for group %s: %s -
ERR_VIRTUAL_STATIC_GROUP_NO_TARGET
The virtual static group defined in entry %s does not contain a target group definition -
ERR_VIRTUAL_STATIC_GROUP_NO_TARGET_GROUP
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_VIRTUAL_STATIC_GROUP_NO_TARGET_GROUPTarget group %s referenced by virtual static group %s does not exist -
ERR_VIRTUAL_STATIC_GROUP_ALTERING_MEMBERS_NOT_SUPPORTED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_VIRTUAL_STATIC_GROUP_ALTERING_MEMBERS_NOT_SUPPORTEDAltering membership for virtual static group %s is not allowed -
ERR_VIRTUAL_STATIC_GROUP_TARGET_CANNOT_BE_VIRTUAL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_VIRTUAL_STATIC_GROUP_TARGET_CANNOT_BE_VIRTUALVirtual 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 -
ERR_PWPSTATE_EXTOP_NO_PRIVILEGE
You do not have sufficient privileges to use the password policy state extended operation -
ERR_PWPSTATE_EXTOP_NO_REQUEST_VALUE
The provided password policy state extended request did not include a request value -
ERR_PWPSTATE_EXTOP_DECODE_FAILURE
An unexpected error occurred while attempting to decode password policy state extended request value: %s -
ERR_PWPSTATE_EXTOP_INVALID_OP_ENCODING
An unexpected error occurred while attempting to decode an operation from the password policy state extended request: %s -
ERR_PWPSTATE_EXTOP_NO_DISABLED_VALUE
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 -
ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE
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' -
ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUEThe 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 -
ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUEThe 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 -
ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUEThe 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 -
ERR_PWPSTATE_EXTOP_BAD_ADD_FAILURE_TIME_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_AUTH_FAILURE_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_EXTOP_BAD_AUTH_FAILURE_TIMEThe 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 -
ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIMEThe 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 -
ERR_PWPSTATE_EXTOP_NO_RESET_STATE_VALUE
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 -
ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE
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' -
ERR_PWPSTATE_EXTOP_BAD_ADD_GRACE_LOGIN_TIME_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_GRACE_LOGIN_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_EXTOP_BAD_GRACE_LOGIN_TIMEThe 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 -
ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME_COUNT
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 -
ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIMEThe 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 -
ERR_PWPSTATE_EXTOP_UNKNOWN_OP_TYPE
The password policy state extended request included an operation with an invalid or unsupported operation type of %s -
WARN_EXTOP_PASSMOD_CANNOT_UPDATE_PWP_STATE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_EXTOP_PASSMOD_CANNOT_UPDATE_PWP_STATEObject> An error occurred while attempting to update the password policy state information for user %s as part of a password modify extended operation (result code='%s', error message='%s') -
ERR_EXTOP_PASSMOD_PW_IN_HISTORY
The provided new password was already contained in the password history -
ERR_SMTPALERTHANDLER_NO_SMTP_SERVERS
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 -
WARN_SMTPALERTHANDLER_ERROR_SENDING_MESSAGE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_SMTPALERTHANDLER_ERROR_SENDING_MESSAGEObject> An error occurred when trying to send an e-mail message for administrative alert with type %s and message %s: %s -
ERR_REGEXMAP_INVALID_MATCH_PATTERN
The provided match pattern "%s" could not be parsed as a regular expression: %s -
ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_FOR_ADMIN
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINObject> The processed ID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s' -
ERR_REGEXMAP_INEFFICIENT_SEARCH
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 -
ERR_REGEXMAP_SEARCH_FAILED
An internal failure occurred while attempting to resolve processed ID string %s to a user entry: %s -
ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe processed ID string %s mapped to multiple users -
ERR_STATICGROUP_GROUP_INSTANCE_INVALID
Group instance with DN %s has been deleted and is no longer valid -
ERR_SMTP_ASNH_NO_MAIL_SERVERS_CONFIGURED
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 -
ERR_SMTP_ASNH_NO_RECIPIENTS
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 -
ERR_SMTP_ASNH_SUBJECT_NO_COLON
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 -
ERR_SMTP_ASNH_SUBJECT_INVALID_NOTIFICATION_TYPE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SMTP_ASNH_SUBJECT_INVALID_NOTIFICATION_TYPEObject> Unable to parse message subject value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type -
ERR_SMTP_ASNH_SUBJECT_DUPLICATE_TYPE
The message subject definitions contained in configuration entry '%s' have multiple subjects defined for notification type %s -
ERR_SMTP_ASNH_TEMPLATE_NO_COLON
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 -
ERR_SMTP_ASNH_TEMPLATE_INVALID_NOTIFICATION_TYPE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SMTP_ASNH_TEMPLATE_INVALID_NOTIFICATION_TYPEObject> Unable to parse message template file path value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type -
ERR_SMTP_ASNH_TEMPLATE_DUPLICATE_TYPE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SMTP_ASNH_TEMPLATE_DUPLICATE_TYPEThe message template file path definitions contained in configuration entry '%s' have multiple template file paths defined for notification type %s -
ERR_SMTP_ASNH_TEMPLATE_NO_SUCH_FILE
The message template file '%s' referenced in configuration entry '%s' does not exist -
ERR_SMTP_ASNH_TEMPLATE_UNCLOSED_TOKEN
public static LocalizableMessageDescriptor.Arg2<Number,Number> ERR_SMTP_ASNH_TEMPLATE_UNCLOSED_TOKENAn unclosed token was found starting at column %d of line %d -
ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_ATTR_TYPE
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_ATTR_TYPEObject> The notification-user-attr token starting at column %d of line %d references undefined attribute type %s -
ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_PROPERTY
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_PROPERTYObject> The notification-property token starting at column %d of line %d references undefined notification property %s -
ERR_SMTP_ASNH_TEMPLATE_UNRECOGNIZED_TOKEN
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_SMTP_ASNH_TEMPLATE_UNRECOGNIZED_TOKENNumber> An unrecognized token %s was found at column %d of line %d -
ERR_SMTP_ASNH_TEMPLATE_CANNOT_PARSE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SMTP_ASNH_TEMPLATE_CANNOT_PARSEObject> An error occurred while attempting to parse message template file '%s' referenced in configuration entry '%s': %s -
INFO_SMTP_ASNH_DEFAULT_SUBJECT
Directory Account Status Notification -
ERR_SMTP_ASNH_CANNOT_SEND_MESSAGE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SMTP_ASNH_CANNOT_SEND_MESSAGEObject> An error occurred while attempting to send an account status notification message for notification type %s for user entry %s: %s -
ERR_PWSCHEME_CANNOT_ENCRYPT
An error occurred while trying to encrypt a value using password storage scheme %s: %s -
ERR_PWSCHEME_CANNOT_DECRYPT
An error occurred while trying to decrypt a value using password storage scheme %s: %s -
ERR_GET_SYMMETRIC_KEY_NO_VALUE
Cannot decode the provided symmetric key extended operation because it does not have a value -
ERR_GET_SYMMETRIC_KEY_ASN1_DECODE_EXCEPTION
Cannot decode the provided symmetric key extended request: %s -
ERR_GET_SYMMETRIC_KEY_DECODE_EXCEPTION
An unexpected error occurred while attempting to decode the symmetric key extended request sequence: %s -
WARN_EXACTMAP_ATTR_UNINDEXED
The exact match identity mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %s -
WARN_REGEXMAP_ATTR_UNINDEXED
The regular expression identity mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %s -
WARN_SATUACM_ATTR_UNINDEXED
The subject attribute to user attribute certificate mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %s -
ERR_SASL_CREATE_SASL_SERVER_FAILED
Failed to create a SASL server for SASL mechanism %s -
ERR_SASL_GSSAPI_KEYTAB_INVALID
GSSAPI SASL mechanism handler initialization failed because the keytab file %s does not exist -
INFO_GSSAPI_STARTED
The GSSAPI SASL mechanism handler initialization was successful -
INFO_GSSAPI_STOPPED
The GSSAPI SASL mechanism handler has been stopped -
ERR_PWSCHEME_INVALID_BASE64_DECODED_STORED_PASSWORD
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PWSCHEME_INVALID_BASE64_DECODED_STORED_PASSWORDThe password value %s has been base64-decoded but is too short to be valid -
ERR_CHARSET_VALIDATOR_MIN_CHAR_SETS_TOO_SMALL
public static LocalizableMessageDescriptor.Arg1<Number> ERR_CHARSET_VALIDATOR_MIN_CHAR_SETS_TOO_SMALLThe provided minimum required number of character sets '%d' is invalid because it must at least include all mandatory character sets -
ERR_CHARSET_VALIDATOR_MIN_CHAR_SETS_TOO_BIG
The provided minimum required number of character sets '%d' is invalid because it is greater than the total number of defined character sets -
ERR_CHARSET_VALIDATOR_TOO_FEW_OPTIONAL_CHAR_SETS
public static LocalizableMessageDescriptor.Arg2<Number,Object> ERR_CHARSET_VALIDATOR_TOO_FEW_OPTIONAL_CHAR_SETSThe provided password did not contain characters from at least %d of the following character sets or ranges: %s -
ERR_SASL_ACCOUNT_NOT_LOCAL
SASL %s authentication is not supported for user %s because the account is not managed locally -
ERR_EXTOP_PASSMOD_ACCOUNT_NOT_LOCAL
Password modification is not supported for user %s because the account is not managed locally -
ERR_EXTOP_PWPSTATE_ACCOUNT_NOT_LOCAL
The password policy state extended operation is not supported for user %s because the account is not managed locally -
ERR_LDAP_PTA_MAPPING_ATTRIBUTE_NOT_FOUND
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDAP_PTA_MAPPING_ATTRIBUTE_NOT_FOUNDObject> 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 -
ERR_LDAP_PTA_MAPPED_SEARCH_TOO_MANY_CANDIDATES
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_LDAP_PTA_MAPPED_SEARCH_TOO_MANY_CANDIDATESObject, Object> 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" -
ERR_LDAP_PTA_MAPPED_SEARCH_NO_CANDIDATES
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDAP_PTA_MAPPED_SEARCH_NO_CANDIDATESObject> The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search did not return any entries matching the filter "%s" -
ERR_LDAP_PTA_MAPPED_SEARCH_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDAP_PTA_MAPPED_SEARCH_FAILEDObject> The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search failed unexpectedly for the following reason: %s -
ERR_LDAP_PTA_MAPPED_BIND_FAILED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDAP_PTA_MAPPED_BIND_FAILEDObject> The user "%s" could not be authenticated using LDAP PTA policy "%s" because the bind failed unexpectedly for the following reason: %s -
ERR_LDAP_PTA_NO_PWD
The configuration of LDAP PTA policy "%s" is invalid because it does not specify a means for obtaining the mapped search bind password -
ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe certificate with subject %s mapped to multiple users -
ERR_SATUACM_INEFFICIENT_SEARCH
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 -
ERR_SATUACM_SEARCH_FAILED
An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s -
ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe certificate with subject %s mapped to multiple users -
ERR_SDTUACM_INEFFICIENT_SEARCH
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 -
ERR_SDTUACM_SEARCH_FAILED
An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s -
ERR_FCM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_FCM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe certificate with fingerprint %s mapped to multiple users -
ERR_FCM_INEFFICIENT_SEARCH
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 -
ERR_FCM_SEARCH_FAILED
An internal failure occurred while attempting to map the certificate with fingerprint %s to a user entry: %s -
ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_RANGE
public static LocalizableMessageDescriptor.Arg2<Object,Number> ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_RANGEThe 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 -
ERR_CHARSET_VALIDATOR_NO_RANGE_COLON
The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range -
ERR_CHARSET_VALIDATOR_NO_RANGE_CHARS
The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range -
ERR_CHARSET_VALIDATOR_INVALID_RANGE_COUNT
The provided character range definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero -
ERR_CHARSET_VALIDATOR_UNSORTED_RANGE
The provided character range definition '%s' is invalid because the range '%s' is reversed -
ERR_CHARSET_VALIDATOR_MALFORMED_RANGE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHARSET_VALIDATOR_MALFORMED_RANGEThe provided character range definition '%s' is invalid because the range '%s' is missing the minus -
ERR_CHARSET_VALIDATOR_SHORT_RANGE
The provided character range definition '%s' is invalid because the range '%s' is too short -
ERR_NO_KEY_ENTRY_IN_KEYSTORE
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 -
ERR_PWSCHEME_INVALID_STORED_PASSWORD
An error occurred while attempting to match a bcrypt hashed password value: %s -
ERR_LDAP_PTA_INVALID_FILTER_TEMPLATE
The mapped search filter template "%s" could not be parsed as a valid LDAP filter -
ERR_LDAP_KEYMANAGER_CANNOT_CREATE_FACTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDAP_KEYMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a key manager factory to access the contents of LDAP keystore with base DN '%s': %s -
ERR_LDAP_TRUSTMANAGER_CANNOT_CREATE_FACTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDAP_TRUSTMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a trust manager factory to access the contents of LDAP keystore with base DN '%s': %s -
ERR_PKCS11_TRUSTMANAGER_CANNOT_CREATE_FACTORY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PKCS11_TRUSTMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a trust manager factory to access the contents of the PKCS#11 keystore: %s -
ERR_PKCS11_TRUSTMANAGER_CANNOT_LOAD
An error occurred while trying to access the PKCS#11 trust manager: %s -
ERR_LOADING_JVM_KEYSTORE_FROM_PROPERTIES
Unable to load JVM default keystore from system properties: %s -
ERR_KEY_MANAGER_PROVIDER_MONITOR_CERTIFICATE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_KEY_MANAGER_PROVIDER_MONITOR_CERTIFICATEAn error occurred while reading information contained within key manager provider from configuration: "%s" -
ERR_JVM_TRUSTSTORE_CANNOT_GET
Unable to get the JVM default truststore: %s -
ERR_CANNOT_DECODE_PRINCIPAL_AS_DN
Could not map the provided certificate chain to a user becausethe peer certificate issuer "%s" could not be decoded as an LDAP DN: %s -
ERR_CERTIFICATE_ISSUER_DOES_NOT_MATCH
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CERTIFICATE_ISSUER_DOES_NOT_MATCHCould 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' -
ERR_EXACTMAP_BACKEND_IS_NOT_LOCAL
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 -
ERR_REGEXMAP_BACKEND_IS_NOT_LOCAL
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 -
ERR_IDENTITY_MAPPERS_MULTIPLE_MATCHING_ENTRIES
public static LocalizableMessageDescriptor.Arg1<Object> ERR_IDENTITY_MAPPERS_MULTIPLE_MATCHING_ENTRIESThe processed ID string %s is mapped to multiple users -
ERR_NO_KEY_MANAGER_CREATED
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_NO_KEY_MANAGER_CREATEDObject, Object> 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' -
WARN_MULTIPLE_KEY_MANAGER_CREATED
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_MULTIPLE_KEY_MANAGER_CREATEDObject, Object> File based key manager provider '%s' has loaded multiple key manager from keystore file '%s'. Only one will be used for securing TLS connections which rely on this key manager provider. 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' -
ERR_NO_X509_EXTENDED_KEY_MANAGER_AVAILABLE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_NO_X509_EXTENDED_KEY_MANAGER_AVAILABLEObject, Object> 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' -
ERR_REFRESHING_KEY_MANAGER_PROVIDER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_REFRESHING_KEY_MANAGER_PROVIDERObject> 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 -
ERR_REFRESHING_TRUST_MANAGER_PROVIDER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_REFRESHING_TRUST_MANAGER_PROVIDERObject> 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 -
ERR_NO_TRUST_MANAGER_CREATED
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_NO_TRUST_MANAGER_CREATEDObject, Object> 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' -
WARN_MULTIPLE_TRUST_MANAGER_CREATED
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_MULTIPLE_TRUST_MANAGER_CREATEDObject, Object> File based trust manager provider '%s' has loaded multiple trust manager from truststore file '%s'. Only one will be used for securing TLS connections which rely on this trust manager provider. 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' -
ERR_NO_X509_EXTENDED_TRUST_MANAGER_AVAILABLE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_NO_X509_EXTENDED_TRUST_MANAGER_AVAILABLEObject, Object> 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' -
ERR_PWSCHEME_CANNOT_INITIALIZE_SCRAM_ALG
The %s SCRAM password storage scheme could not be initialized because the algorithm is not supported by the JVM -
ERR_PWSCHEME_CANNOT_DECODE_SCRAM_CREDENTIAL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWSCHEME_CANNOT_DECODE_SCRAM_CREDENTIALAn error occurred while attempting to decode the SCRAM credential value %s: %s -
ERR_SASL_NO_SCRAM_CREDENTIALS
SASL %s authentication is not possible for user '%s' because the user entry does not contain any SCRAM credentials -
ERR_SASL_CANNOT_GET_SCRAM_CREDENTIALS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SASL_CANNOT_GET_SCRAM_CREDENTIALSObject> An error occurred while attempting to retrieve the SCRAM credentials for user '%s' in order to perform SASL %s authentication: %s -
ERR_SASL_SCRAM_CANNOT_INITIALIZE_SCRAM_ALG
The %s SCRAM SASL mechanism handler could not be initialized because the algorithm is not supported by the JVM -
ERR_DICTIONARY_VALIDATOR_CANNOT_LOAD
Error loading dictionary: %s -
ERR_ADMIN_DATA_TRUSTMANAGER_CANNOT_CREATE_FACTORY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_ADMIN_DATA_TRUSTMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a trust manager factory to access the certificates in "cn=admin data": %s -
ERR_CANNOT_LIST_SECRET_FILES
'%s' cannot list the secret files in directory '%s', all the secrets will be ignored: %s -
WARN_CANNOT_READ_SECRET_FILE
'%s' cannot read the secret file '%s': %s -
ERR_SECRET_FILE_TOO_BIG
The file '%s' exceeds max size '%s' -
ERR_SECRET_FILE_CANNOT_BE_DECODED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SECRET_FILE_CANNOT_BE_DECODEDObject> '%s' cannot decode the secret file '%s': %s -
WARN_SECRET_FILE_NOT_SUITABLE_FOR_PURPOSE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_SECRET_FILE_NOT_SUITABLE_FOR_PURPOSEObject> '%s' has ignored the file '%s' either because the certificate does not contain the key usage extension '%s', or because the file does not contain the appropriate key types -
ERR_INVALID_PEM_FILE_GLOB_PATTERN
Invalid excluded file name pattern: %s -
ERR_PWSCHEME_ARGON2_NOT_ENOUGH_MEMORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PWSCHEME_ARGON2_NOT_ENOUGH_MEMORYThe Argon2 password storage scheme could not be configured because it requires %s kB of memory, exceeding the maximum available of %s kB. Configure a bigger heap or reduce the Argon2 memory requirements -
ERR_ADMIN_DATA_TRUSTMANAGER_KEYSTORE_READ_FAILURE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_ADMIN_DATA_TRUSTMANAGER_KEYSTORE_READ_FAILUREAn unexpected error occurred while accessing the instance keys in "cn=admin data": %s -
ERR_ADMIN_DATA_TRUSTMANAGER_KEYSTORE_READ_ALIAS_FAILURE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_ADMIN_DATA_TRUSTMANAGER_KEYSTORE_READ_ALIAS_FAILUREAn unexpected error occurred while attempting to read the instance key '%s' in "cn=admin data": %s -
ERR_PWSCHEME_ARGON2_ADD_NEW_SCHEME_OFFLINE
A new Argon2 password storage scheme can only be added by running dsconfig in offline mode -
INFO_EXTERNAL_LIB_MESSAGE
%s -
INFO_EXTERNAL_LIB_MESSAGE_WITH_EXCEPTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_EXTERNAL_LIB_MESSAGE_WITH_EXCEPTION%s with exception: %s -
ERR_LOGGER_ERROR_WRITING_RECORD
Error occurred while writing log record for logger %s: %s. Any further write errors will be ignored -
ERR_LOGGER_ERROR_OPENING_FILE
Error occurred while opening log file %s for logger %s: %s -
ERR_LOGGER_ERROR_CLOSING_FILE
Error occurred while closing log file for logger %s: %s -
ERR_LOGGER_ERROR_FLUSHING_BUFFER
Error occurred while flushing writer buffer for logger %s: %s -
WARN_ERROR_LOGGER_INVALID_SEVERITY
Invalid error log severity "%s" -
WARN_ERROR_LOGGER_INVALID_CATEGORY
Invalid error log category "%s" -
WARN_ERROR_LOGGER_INVALID_OVERRIDE_SEVERITY
Invalid override of severity level "%s" -
WARN_LOGGER_SET_PERMISSION_FAILED
Error occurred while setting file permissions for the log file %s: %s -
WARN_LOGGER_UNABLE_SET_PERMISSIONS
This platform does not support setting file permissions %s to the log file %s -
ERR_LOGGER_ERROR_LISTING_FILES
Error occurred while listing log files named by policy with initial file name %s -
ERR_LOGGER_ERROR_OBTAINING_FREE_SPACE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LOGGER_ERROR_OBTAINING_FREE_SPACEError occurred while obtaining free disk space in the partition containing log file %s: %s -
ERR_LOGGER_ERROR_ENFORCING_RETENTION_POLICY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LOGGER_ERROR_ENFORCING_RETENTION_POLICYObject> Error occurred while enforcing retention policy %s for logger %s: %s -
ERR_COMMON_AUDIT_ADD_OR_UPDATE_LOG_PUBLISHER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_ADD_OR_UPDATE_LOG_PUBLISHERError while creating or updating common audit log publisher %s: %s -
ERR_COMMON_AUDIT_UNSUPPORTED_HANDLER_TYPE
Error while adding common audit log publisher %s, the publisher has an unsupported handler type -
ERR_COMMON_AUDIT_EXTERNAL_HANDLER_JSON_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_COMMON_AUDIT_EXTERNAL_HANDLER_JSON_FILEObject> Error while reading JSON configuration file %s while creating common audit external log publisher %s: %s -
ERR_COMMON_AUDIT_EXTERNAL_HANDLER_CREATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_EXTERNAL_HANDLER_CREATIONError while creating common audit external log publisher %s: %s -
ERR_COMMON_AUDIT_FILE_BASED_HANDLER_CREATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_FILE_BASED_HANDLER_CREATIONError while creating common audit log publisher %s: %s -
ERR_COMMON_AUDIT_UNSUPPORTED_LOG_ROTATION_POLICY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_UNSUPPORTED_LOG_ROTATION_POLICYError while adding common audit log publisher %s, the publisher defines an unsupported log rotation policy %s -
ERR_COMMON_AUDIT_UNSUPPORTED_LOG_RETENTION_POLICY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_UNSUPPORTED_LOG_RETENTION_POLICYError while adding common audit log publisher %s, the publisher defines an unsupported log retention policy %s -
ERR_COMMON_AUDIT_UNSUPPORTED_LOG_PUBLISHER
Error while processing common audit log publisher %s, this type of log publisher is unsupported -
ERR_COMMON_AUDIT_CSV_HANDLER_DELIMITER_CHAR
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_CSV_HANDLER_DELIMITER_CHARError while processing common audit log publisher %s, delimiter char '%s' should not contain more than one character -
ERR_COMMON_AUDIT_CSV_HANDLER_QUOTE_CHAR
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_CSV_HANDLER_QUOTE_CHARError while processing common audit log publisher %s, quote char '%s' should not contain more than one character -
ERR_COMMON_AUDIT_INVALID_TIME_OF_DAY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_COMMON_AUDIT_INVALID_TIME_OF_DAYObject> 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 -
ERR_COMMON_AUDIT_UNABLE_TO_PROCESS_LOG_EVENT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_COMMON_AUDIT_UNABLE_TO_PROCESS_LOG_EVENTError while processing a log event for common audit: %s -
ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_MISSING
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_MISSINGError while processing common audit log publisher %s, the keystore pin file %s is missing -
ERR_COMMON_AUDIT_ERROR_READING_KEYSTORE_PIN_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_COMMON_AUDIT_ERROR_READING_KEYSTORE_PIN_FILEObject> Error while processing common audit log publisher %s, the keystore pin file %s could not be read: %s -
ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_CONTAINS_EMPTY_PIN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_CONTAINS_EMPTY_PINError while processing common audit log publisher %s, the keystore pin file %s contains an empty pin -
ERR_COMMON_AUDIT_KEYSTORE_FILE_MISSING
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_KEYSTORE_FILE_MISSINGError while processing common audit log publisher %s, the keystore file %s is missing -
ERR_COMMON_AUDIT_ERROR_READING_KEYSTORE_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_COMMON_AUDIT_ERROR_READING_KEYSTORE_FILEObject> Error while processing common audit log publisher %s, the keystore file %s could not be read: %s -
ERR_COMMON_AUDIT_KEYSTORE_FILE_IS_EMPTY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_COMMON_AUDIT_KEYSTORE_FILE_IS_EMPTYError while processing common audit log publisher %s, the keystore file %s is empty -
ERR_LOG_FILE_DISAPPEARED
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 -
ERR_LOG_AGGREGATOR_MESSAGE_LOGGED_TOO_OFTEN
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_LOG_AGGREGATOR_MESSAGE_LOGGED_TOO_OFTENObject> The message with ID %d has been generated %d times in the last second: %s -
WARN_ERROR_LOGGER_INVALID_SEVERITY_MULTIPLE_VALUES
public static LocalizableMessageDescriptor.Arg1<Object> WARN_ERROR_LOGGER_INVALID_SEVERITY_MULTIPLE_VALUESInvalid error log severity "%s", only one severity must be provided, the highest one at which logging should occur -
ERR_PLUGIN_ADLIST_NO_PLUGIN_TYPES
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 -
ERR_PLUGIN_ADLIST_INVALID_PLUGIN_TYPE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PLUGIN_ADLIST_INVALID_PLUGIN_TYPEThe 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 -
ERR_PLUGIN_STARTUP_PLUGIN_EXCEPTION
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 -
ERR_PLUGIN_STARTUP_PLUGIN_RETURNED_NULL
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 -
ERR_PLUGIN_STARTUP_PLUGIN_FAIL_ABORT
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_STARTUP_PLUGIN_FAIL_ABORTNumber> 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 -
ERR_PLUGIN_SHUTDOWN_PLUGIN_EXCEPTION
The shutdown plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server shutdown process: %s -
ERR_PLUGIN_POST_CONNECT_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_PLUGIN_POST_CONNECT_PLUGIN_EXCEPTIONObject, Object> 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 -
ERR_PLUGIN_POST_CONNECT_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_PLUGIN_POST_CONNECT_PLUGIN_RETURNED_NULLObject> 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 -
ERR_PLUGIN_POST_DISCONNECT_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_PLUGIN_POST_DISCONNECT_PLUGIN_EXCEPTIONObject, Object> The post-disconnect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %s -
ERR_PLUGIN_POST_DISCONNECT_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_PLUGIN_POST_DISCONNECT_PLUGIN_RETURNED_NULLObject> The post-disconnect plugin defined in configuration entry %s returned null when invoked for connection %d from %s. This is an illegal response -
ERR_PLUGIN_PRE_PARSE_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_PLUGIN_PRE_PARSE_PLUGIN_EXCEPTIONNumber, Number, Object> 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 -
ERR_PLUGIN_PRE_PARSE_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_PLUGIN_PRE_PARSE_PLUGIN_RETURNED_NULLNumber, Number> 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 -
ERR_PLUGIN_PRE_OPERATION_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_PLUGIN_PRE_OPERATION_PLUGIN_EXCEPTIONNumber, Number, Object> 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 -
ERR_PLUGIN_PRE_OPERATION_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_PLUGIN_PRE_OPERATION_PLUGIN_RETURNED_NULLNumber, Number> 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 -
ERR_PLUGIN_POST_OPERATION_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_PLUGIN_POST_OPERATION_PLUGIN_EXCEPTIONNumber, Number, Object> 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 -
ERR_PLUGIN_POST_OPERATION_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_PLUGIN_POST_OPERATION_PLUGIN_RETURNED_NULLNumber, Number> 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 -
ERR_PLUGIN_POST_RESPONSE_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_PLUGIN_POST_RESPONSE_PLUGIN_EXCEPTIONNumber, Number, Object> 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 -
ERR_PLUGIN_POST_RESPONSE_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_PLUGIN_POST_RESPONSE_PLUGIN_RETURNED_NULLNumber, Number> 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 -
ERR_PLUGIN_SEARCH_ENTRY_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Number, ERR_PLUGIN_SEARCH_ENTRY_PLUGIN_EXCEPTIONNumber, Object, Object> 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 -
ERR_PLUGIN_SEARCH_ENTRY_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_PLUGIN_SEARCH_ENTRY_PLUGIN_RETURNED_NULLNumber, Object> 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 -
ERR_PLUGIN_SEARCH_REFERENCE_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Number, ERR_PLUGIN_SEARCH_REFERENCE_PLUGIN_EXCEPTIONNumber, Object, Object> 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 -
ERR_PLUGIN_SEARCH_REFERENCE_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_PLUGIN_SEARCH_REFERENCE_PLUGIN_RETURNED_NULLNumber, Object> 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 -
ERR_PLUGIN_LASTMOD_INVALID_PLUGIN_TYPE
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 -
ERR_PLUGIN_LDIF_IMPORT_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_LDIF_IMPORT_PLUGIN_EXCEPTIONObject> The LDIF import plugin defined in configuration entry %s threw an exception when it was invoked on entry %s: %s -
ERR_PLUGIN_LDIF_IMPORT_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PLUGIN_LDIF_IMPORT_PLUGIN_RETURNED_NULLThe LDIF import plugin defined in configuration entry %s returned null when invoked on entry %s. This is an illegal response -
ERR_PLUGIN_ENTRYUUID_INVALID_PLUGIN_TYPE
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 -
ERR_PLUGIN_PWPIMPORT_INVALID_PLUGIN_TYPE
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 -
ERR_PLUGIN_PWPIMPORT_ERROR_ENCODING_PASSWORD
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_PWPIMPORT_ERROR_ENCODING_PASSWORDObject> 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 -
ERR_PLUGIN_TYPE_NOT_SUPPORTED
The plugin defined in configuration entry %s does not support the %s plugin type -
ERR_PLUGIN_PWIMPORT_NO_DEFAULT_AUTH_SCHEMES
The password policy import plugin is not configured any default auth password schemes, and the server does not support the %s auth password scheme -
ERR_PLUGIN_PWIMPORT_INVALID_DEFAULT_AUTH_SCHEME
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_PWIMPORT_INVALID_DEFAULT_AUTH_SCHEMEAuth password storage scheme %s referenced by the password policy import plugin is not configured for use in the server -
ERR_PLUGIN_PWIMPORT_NO_DEFAULT_USER_SCHEMES
The password policy import plugin is not configured any default user password schemes, and the server does not support the %s auth password scheme -
ERR_PLUGIN_PWIMPORT_INVALID_DEFAULT_USER_SCHEME
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_PWIMPORT_INVALID_DEFAULT_USER_SCHEMEUser password storage scheme %s referenced by the password policy import plugin is not configured for use in the server -
WARN_PLUGIN_PWIMPORT_NO_SUCH_POLICY
Entry '%s' indicates that it uses custom password policy '%s', but no such policy is defined in the server. Any passwords contained in the entry will be encoded using the default storage schemes, but authentication as this user might not be possible -
WARN_PLUGIN_PWIMPORT_CANNOT_DECODE_POLICY_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_PLUGIN_PWIMPORT_CANNOT_DECODE_POLICY_DNAn error occurred while attempting to decode the value of the custom password policy attribute in entry '%s': %s. Any passwords contained in the entry will be encoded using the default storage schemes, but authentication as this user might not be possible -
ERR_PLUGIN_SUBORDINATE_MODIFY_DN_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_PLUGIN_SUBORDINATE_MODIFY_DN_PLUGIN_EXCEPTIONNumber, Object> 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 -
ERR_PLUGIN_SUBORDINATE_MODIFY_DN_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_PLUGIN_SUBORDINATE_MODIFY_DN_PLUGIN_RETURNED_NULLObject> 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 -
ERR_PLUGIN_UNIQUEATTR_INVALID_PLUGIN_TYPE
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 -
ERR_PLUGIN_REFERENT_INVALID_PLUGIN_TYPE
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 -
ERR_PLUGIN_REFERENT_CREATE_LOGFILE
An error occurred during Referential Integrity plugin initialization because log file creation failed: %s -
ERR_PLUGIN_REFERENT_CLOSE_LOGFILE
An error occurred closing the Referential Integrity plugin update log file: %s -
ERR_PLUGIN_REFERENT_REPLACE_LOGFILE
An error occurred replacing the Referential Integrity plugin update log file: %s -
INFO_PLUGIN_REFERENT_LOGFILE_CHANGE_REQUIRES_RESTART
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_PLUGIN_REFERENT_LOGFILE_CHANGE_REQUIRES_RESTARTThe file name that the Referential Integrity plugin logs changes to during background processing has been changed from %s to %s, but this change will not take effect until the server is restarted -
INFO_PLUGIN_REFERENT_BACKGROUND_PROCESSING_UPDATE_INTERVAL_CHANGED
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_PLUGIN_REFERENT_BACKGROUND_PROCESSING_UPDATE_INTERVAL_CHANGEDThe Referential Integrity plugin background processing update interval has been changed from %s to %s, the new value will now be during background processing -
INFO_PLUGIN_REFERENT_BACKGROUND_PROCESSING_STOPPING
The Referential Integrity plugin background processing has been stopped -
INFO_PLUGIN_REFERENT_BACKGROUND_PROCESSING_STARTING
public static LocalizableMessageDescriptor.Arg1<Object> INFO_PLUGIN_REFERENT_BACKGROUND_PROCESSING_STARTINGThe Referential Integrity plugin has started background processing using the update interval %s -
ERR_PLUGIN_REFERENT_SEARCH_FAILED
The Referential Integrity plugin failed when performing an internal search: %s -
ERR_PLUGIN_REFERENT_MODIFY_FAILED
The Referential Integrity plugin failed when performing an internal modify on entry %s: %s -
ERR_PLUGIN_REFERENT_CANNOT_DECODE_STRING_AS_DN
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_REFERENT_CANNOT_DECODE_STRING_AS_DNThe Referential Integrity plugin failed to decode a entry DN from the update log: %s -
INFO_PLUGIN_REFERENT_SEARCH_NO_SUCH_OBJECT
The Referential Integrity plugin failed when performing a search because the base DN %s does not exist -
ERR_PLUGIN_REFERENT_INVALID_ATTRIBUTE_SYNTAX
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PLUGIN_REFERENT_INVALID_ATTRIBUTE_SYNTAXAn 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) -
ERR_PLUGIN_7BIT_INVALID_PLUGIN_TYPE
The 7-bit clean plugin is configured with invalid plugin type %s. Only the ldifImport, preOperationAdd, preOperationModify, and preOperationModifyDN plugin types are allowed -
ERR_PLUGIN_7BIT_MODIFYDN_ATTR_NOT_CLEAN
The modify DN operation would have resulted in a value for attribute %s that was not 7-bit clean -
ERR_PLUGIN_7BIT_IMPORT_ATTR_NOT_CLEAN
The entry included a value for attribute %s that was not 7-bit clean -
ERR_PLUGIN_PWIMPORT_NO_SUCH_DEFAULT_AUTH_SCHEME
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_PWIMPORT_NO_SUCH_DEFAULT_AUTH_SCHEMEThe password policy import plugin references default auth password storage scheme %s which is not available for use in the server -
ERR_PLUGIN_POST_SYNCHRONIZATION_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_PLUGIN_POST_SYNCHRONIZATION_PLUGIN_EXCEPTIONNumber, Number, Object> The post-synchronization %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s -
ERR_PLUGIN_UNIQUEATTR_ATTR_NOT_UNIQUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_UNIQUEATTR_ATTR_NOT_UNIQUEObject> A unique attribute conflict was detected for attribute %s: value %s already exists in entry %s -
ERR_PLUGIN_UNIQUEATTR_SYNC_NOT_UNIQUE
public static LocalizableMessageDescriptor.Arg6<Object,Number, ERR_PLUGIN_UNIQUEATTR_SYNC_NOT_UNIQUENumber, Object, Object, Object> 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 -
ERR_PLUGIN_UNIQUEATTR_INTERNAL_ERROR
An internal error occurred while attempting to determine whether the operation would have resulted in a unique attribute conflict (result %s, message %s) -
ERR_PLUGIN_UNIQUEATTR_INTERNAL_ERROR_SYNC
public static LocalizableMessageDescriptor.Arg5<Number,Number, ERR_PLUGIN_UNIQUEATTR_INTERNAL_ERROR_SYNCObject, Object, Object> 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) -
ERR_PLUGIN_REFERENT_ATTR_UNINDEXED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_REFERENT_ATTR_UNINDEXEDObject> 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 -
ERR_PLUGIN_UNIQUEATTR_ATTR_UNINDEXED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_UNIQUEATTR_ATTR_UNINDEXEDObject> 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 -
ERR_PLUGIN_CHANGE_NUMBER_INVALID_PLUGIN_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_CHANGE_NUMBER_INVALID_PLUGIN_TYPEAn 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 -
ERR_PLUGIN_CHANGE_NUMBER_INVALID_PLUGIN_TYPE_LIST
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_PLUGIN_CHANGE_NUMBER_INVALID_PLUGIN_TYPE_LISTAn 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 -
ERR_PLUGIN_SUBORDINATE_DELETE_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_PLUGIN_SUBORDINATE_DELETE_PLUGIN_EXCEPTIONNumber, Object> 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 -
ERR_PLUGIN_SUBORDINATE_DELETE_PLUGIN_RETURNED_NULL
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_PLUGIN_SUBORDINATE_DELETE_PLUGIN_RETURNED_NULLObject> 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 -
ERR_PLUGIN_SAMBA_SYNC_INVALID_PLUGIN_TYPE
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 -
ERR_PLUGIN_SAMBA_SYNC_ENCODING
The Samba password synchronization plugin could not encode a password for the following reasons: %s -
ERR_PLUGIN_SAMBA_SYNC_MODIFICATION_PROCESSING
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_SAMBA_SYNC_MODIFICATION_PROCESSINGThe Samba password synchronization plugin could not process a modification for the following reason: %s -
ERR_PLUGIN_ATTR_CLEANUP_INITIALIZE_PLUGIN
Invalid plugin type '%s' for the Attribute Cleanup plugin -
ERR_PLUGIN_ATTR_CLEANUP_ATTRIBUTE_MISSING
Attribute '%s' is not defined in the directory schema -
ERR_PLUGIN_ATTR_CLEANUP_DUPLICATE_VALUE
The attribute '%s' has already been defined in the configuration -
ERR_PLUGIN_ATTR_CLEANUP_EQUAL_VALUES
The mapping '%s:%s' maps the attribute to itself -
ERR_PLUGIN_REFERENT_ATTR_NOT_LISTED
The property 'check-references-filter-criteria' specifies filtering criteria for attribute '%s', but this attribute is not listed in the 'attribute-type' property -
ERR_PLUGIN_REFERENT_BAD_FILTER
The filtering criteria '%s' specified in property 'check-references-filter-criteria' is invalid because the filter could not be decoded: '%s' -
ERR_PLUGIN_REFERENT_ENTRY_MISSING
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_REFERENT_ENTRY_MISSINGObject> 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 -
ERR_PLUGIN_REFERENT_FILTER_MISMATCH
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_PLUGIN_REFERENT_FILTER_MISMATCHObject, Object> The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not match the filter '%s' -
ERR_PLUGIN_REFERENT_NAMINGCONTEXT_MISMATCH
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_PLUGIN_REFERENT_NAMINGCONTEXT_MISMATCHObject> 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 -
ERR_PLUGIN_REFERENT_EXCEPTION
The operation could not be processed due to an unexpected exception: '%s' -
ERR_PLUGIN_GRAPHITE_REPORTER_INVALID_PLUGIN_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_GRAPHITE_REPORTER_INVALID_PLUGIN_TYPEAn 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 -
ERR_PLUGIN_GRAPHITE_REPORTER_UNREACHABLE_GRAPHITE_SERVER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_GRAPHITE_REPORTER_UNREACHABLE_GRAPHITE_SERVERUnable 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 -
ERR_PLUGIN_REFERENT_ATTR_MATCHING_RULE_UNINDEXED
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_PLUGIN_REFERENT_ATTR_MATCHING_RULE_UNINDEXEDObject, Object> 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 -
ERR_PLUGIN_ENTITY_TAG_INVALID_PLUGIN_TYPE
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 -
ERR_PLUGIN_POST_COMMIT_PLUGIN_EXCEPTION
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_PLUGIN_POST_COMMIT_PLUGIN_EXCEPTIONNumber, Number, Object> The post-commit %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s -
ERR_LDAP_CLIENT_SEND_RESPONSE_NO_RESULT_CODE
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_LDAP_CLIENT_SEND_RESPONSE_NO_RESULT_CODENumber> 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 -
ERR_LDAP_CLIENT_SEND_RESPONSE_INVALID_OP
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_LDAP_CLIENT_SEND_RESPONSE_INVALID_OPNumber, Object> 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 -
INFO_LDAP_CLIENT_GENERIC_NOTICE_OF_DISCONNECTION
The Directory Server is closing the connection to this client -
WARN_CLIENT_DISCONNECT_IN_PROGRESS
The Directory Server is currently in the process of closing this client connection -
ERR_CONNHANDLER_DENIED_CLIENT
The connection attempt from client %s to %s has been rejected because the client was included in one of the denied address ranges -
ERR_CONNHANDLER_DISALLOWED_CLIENT
The connection attempt from client %s to %s has been rejected because the client was not included in one of the allowed address ranges -
INFO_CONNHANDLER_UNABLE_TO_REGISTER_CLIENT
public static LocalizableMessageDescriptor.Arg3<Object,Object, INFO_CONNHANDLER_UNABLE_TO_REGISTER_CLIENTObject> An internal error prevented the Directory Server from properly registering the client connection from %s to %s with an appropriate request handler: %s -
ERR_LDAP_DISCONNECT_DUE_TO_INVALID_REQUEST_TYPE
public static LocalizableMessageDescriptor.Arg2<Object,Number> ERR_LDAP_DISCONNECT_DUE_TO_INVALID_REQUEST_TYPETerminating this connection because the client sent an invalid message of type %s (LDAP message ID %d) that is not allowed for request messages -
ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILUREObject> An unexpected failure occurred while trying to process a request of type %s (LDAP message ID %d): %s. The client connection will be terminated -
ERR_LDAP_DISCONNECT_DUE_TO_BIND_PROTOCOL_ERROR
public static LocalizableMessageDescriptor.Arg2<Number,Object> ERR_LDAP_DISCONNECT_DUE_TO_BIND_PROTOCOL_ERRORThis 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 -
ERR_LDAPV2_SKIPPING_EXTENDED_RESPONSE
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_LDAPV2_SKIPPING_EXTENDED_RESPONSEObject> 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 -
ERR_LDAPV2_SKIPPING_SEARCH_REFERENCE
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_LDAPV2_SKIPPING_SEARCH_REFERENCEObject> 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 -
ERR_LDAPV2_REFERRAL_RESULT_CHANGED
The original result code for this message was 10 but this result is not allowed for LDAPv2 clients -
ERR_LDAPV2_REFERRALS_OMITTED
The response included one or more referrals, which are not allowed for LDAPv2 clients. The referrals included were: %s -
ERR_LDAPV2_CLIENTS_NOT_ALLOWED
The Directory Server has been configured to deny access to LDAPv2 clients. This connection will be closed -
ERR_LDAPV2_EXTENDED_REQUEST_NOT_ALLOWED
public static LocalizableMessageDescriptor.Arg2<Number,Number> ERR_LDAPV2_EXTENDED_REQUEST_NOT_ALLOWEDThe 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 -
ERR_CONNHANDLER_REJECTED_BY_SERVER
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 -
INFO_UPGRADE_REBUILD_INDEXES_DECLINED
You have to rebuild the '%s' index(es) manually to get a fully functional server -
NOTE_CONNHANDLER_STARTED_LISTENING
Started listening for new connections on %s -
NOTE_CONNHANDLER_STOPPED_LISTENING
Stopped listening for new connections on %s -
ERR_PROXYAUTH1_NO_SUCH_USER
User %s specified in the proxied authorization V1 control does not exist in the Directory Server -
ERR_PROXYAUTH2_NO_IDENTITY_MAPPER
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 -
ERR_PROXYAUTH2_INVALID_AUTHZID
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 -
ERR_PROXYAUTH2_NO_SUCH_USER
User %s specified in the proxied authorization V2 control does not exist in the Directory Server -
WARN_LDAP_CLIENT_DUPLICATE_MESSAGE_ID
The Directory Server is already processing another request on the same client connection with the same message ID of %d -
ERR_PROXYAUTH1_UNUSABLE_ACCOUNT
Use of the proxied authorization V1 control for user %s is not allowed by the password policy configuration -
INFO_SORTREQ_CONTROL_NO_ORDERING_RULE_FOR_ATTR
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SORTREQ_CONTROL_NO_ORDERING_RULE_FOR_ATTRUnable to process the provided server-side sort request control because it included attribute %s which does not have a default ordering matching rule and no ordering rule was specified in the sort key -
ERR_LDAPV2_CONTROLS_NOT_ALLOWED
LDAPv2 clients are not allowed to use request controls -
ERR_JMX_SEARCH_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform search operations through JMX -
ERR_JMX_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to establish the connection through JMX. At least JMX_READ privilege is required -
ERR_INTERNALCONN_NO_SUCH_USER
User %s does not exist in the directory -
WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORYThe value %s specified as the LDIF directory path for the LDIF connection handler defined in configuration entry %s exists but is not a directory. The specified path must be a directory. The LDIF connection handler will start, but will not be able to proces any changes until this path is changed to a directory -
WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_MISSING
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_MISSINGThe directory %s referenced by the LDIF connection handler defined in configuration entry %s does not exist. The LDIF connection handler will start, but will not be able to process any changes until this directory is created -
ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_NONFATAL
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_NONFATALAn 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 -
ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_FATAL
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_FATALAn error occurred while trying to read a change record from the LDIF file: %s. No further processing on this LDIF file can be performed -
INFO_LDIF_CONNHANDLER_RESULT_CODE
Result Code: %d (%s) -
INFO_LDIF_CONNHANDLER_ERROR_MESSAGE
Additional Info: %s -
INFO_LDIF_CONNHANDLER_MATCHED_DN
Matched DN: %s -
INFO_LDIF_CONNHANDLER_REFERRAL_URL
Referral URL: %s -
ERR_LDIF_CONNHANDLER_IO_ERROR
An I/O error occurred while the LDIF connection handler was processing LDIF file %s: %s -
ERR_LDIF_CONNHANDLER_CANNOT_RENAME
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_LDIF_CONNHANDLER_CANNOT_RENAMEObject> An error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %s -
ERR_LDIF_CONNHANDLER_CANNOT_DELETE
An error occurred while the LDIF connection handler was attempting to delete processed file %s: %s -
ERR_CONNHANDLER_SSL_CANNOT_INITIALIZE
An error occurred while attempting to initialize the SSL context for use in the LDAP Connection Handler: %s -
ERR_LDAP_UNSUPPORTED_PROTOCOL_VERSION
The Directory Server does not support LDAP protocol version %d. This connection will be closed -
ERR_CANNOT_DECODE_CONTROL_VALUE
Cannot decode the provided control %s because an error occurred while attempting to decode the control value: %s -
ERR_ECLN_NO_CONTROL_VALUE
Cannot decode the provided entry changelog notification control because it does not have a value -
ERR_ECLN_CANNOT_DECODE_VALUE
Cannot decode the provided entry changelog notification control because an error occurred while attempting to decode the control value: %s -
INFO_ERGONOMIC_SIZING_OF_REQUEST_HANDLER_THREADS
public static LocalizableMessageDescriptor.Arg2<Object,Number> INFO_ERGONOMIC_SIZING_OF_REQUEST_HANDLER_THREADSConnection handler '%s' does not specify the number of request handler threads: defaulting to %d threads -
ERR_CONNHANDLER_CONFIG_CHANGES_REQUIRE_RESTART
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONNHANDLER_CONFIG_CHANGES_REQUIRE_RESTARTThe server received configuration changes that require a restart of the %s connection handler to take effect -
ERR_PROXYAUTH_AUTHZ_NOT_PERMITTED
Authorization as '%s' specified in the proxied authorization control is not permitted -
ERR_KEYSTORE_DOES_NOT_CONTAIN_ALIAS
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 -
ERR_INVALID_KEYSTORE
No usable key was found for '%s', which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configured -
ERR_PROXYAUTH2_ACCOUNT_DISABLED
Use of the proxied authorization V2 control for user %s is not allowed: the account is disabled -
ERR_PROXYAUTH2_ACCOUNT_EXPIRED
Use of the proxied authorization V2 control for user %s is not allowed: the account is expired -
ERR_PROXYAUTH2_ACCOUNT_LOCKED
Use of the proxied authorization V2 control for user %s is not allowed: the account is locked -
ERR_PROXYAUTH2_PASSWORD_EXPIRED
Use of the proxied authorization V2 control for user %s is not allowed: the account's password is expired -
ERR_INTERNAL_MOD_CONTROL_NO_ORIGIN
Unable to process the provided internal modifications request control because it did not contain an origin -
ERR_INTERNAL_MOD_CONTROL_NO_MODS
Unable to process the provided internal modifications request control because it did not contain modifications -
ERR_REPLICATION_CTX_CONTROL_NO_CSN
Unable to process the provided replication context request control because it did not contain a CSN -
ERR_REPLICATION_CTX_CONTROL_NO_ENTRY_UUID
Unable to process the provided replication context request control because it did not contain an entry UUID -
ERR_HTTP_CONNECTION_HANDLE_EXCEPTION
Unable to process request '%s' received for HTTP client connection: %s -
ERR_INTERNAL_CONNECTION_HANDLE_EXCEPTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_INTERNAL_CONNECTION_HANDLE_EXCEPTIONUnable to process request '%s' received for internal client connection: %s -
ERR_INTERNAL_CONNECTION_NO_RESULT
No result received after completion for request '%s' received for internal client connection -
INFO_INTERNAL_CONNECTION_CANNOT_BE_CANCELLED
Internal operations can't be cancelled -
ERR_JMX_CONNECTION_UNEXPECTED_REQUEST_TYPE
Unable to process request '%s' received for JMX client because this type of request is not supported for JMX -
ERR_JMX_CONNECTION_UNEXPECTED_RESPONSE_TYPE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_JMX_CONNECTION_UNEXPECTED_RESPONSE_TYPEUnable to process response received for JMX client connection for request '%s' because the response '%s' is not of any of the expected types -
ERR_JMX_CONNECTION_NO_RESULT
No result received after completion for request '%s' received for JMX client connection -
ERR_JMX_CONNECTION_HANDLE_EXCEPTION
Unable to process request '%s' received for JMX client connection: %s -
ERR_ACCESS_MONITORING_INFORMATION_NOT_AUTHENTICATED
User authentication is mandatory to access server monitoring information -
ERR_MAX_BLOCKED_WRITE_LIMIT_EXCEEDED
Could not write data to the client for %s -
ERR_CONNHANDLER_RESTRICTED_CLIENT
The connection attempt from client %s to %s has been rejected because there are too many open connections from this client -
ERR_SORTREQ_CONTROL_CANNOT_PROCESS
Unable to process the provided server-side sort request control: %s -
ERR_SASL_BIND_MULTI_STAGE
An error occurred during multi-stage authentication: '%s' -
ERR_HTTP_REQUEST_PROCESSING_EXCEPTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_HTTP_REQUEST_PROCESSING_EXCEPTIONUnable to process HTTP request '%s': %s -
ERR_HTTP_WRITING_RESPONSE_EXCEPTION
Unable to write HTTP response to the client '%s': %s -
ERR_HTTP_APPLICATION_START_EXCEPTION
Error while starting the HTTP application: %s -
ERR_LDAP_CLIENT_CANCEL_INVOKED
cancel() invoked -
ERR_JMX_CONNECTION_FINALIZED
JMX connection %s with JMX connection ID '%s' has been disconnected because it was finalized by GC -
ERR_JMX_CONNECTION_NOTIFICATION_CLOSED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_JMX_CONNECTION_NOTIFICATION_CLOSEDObject> JMX connection %s with JMX connection ID '%s' has been disconnected because it received a '%s' notification -
ERR_LDAP_CONNECTION_CLOSED
LDAP connection %s has been closed because the LDAP connection handler %s is shutting down -
ERR_KEYSTORE_INVALID_KEY_NOT_YET_VALID
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_KEYSTORE_INVALID_KEY_NOT_YET_VALIDThe 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 -
ERR_KEYSTORE_INVALID_KEY_EXPIRED
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 -
ERR_CONNHANDLER_MISSING_CIPHER
The connection attempt from client '%s' to '%s' has been rejected because the proxy protocol header indicated that the client used SSL but the header does not specify which SSL cipher was used. The proxy should be configured to transmit all SSL headers -
ERR_SYNC_INVALID_DN
The configured DN is already used by another domain -
ERR_COULD_NOT_BIND_CHANGELOG
Replication Server failed to start : could not bind to the listen port : %d. Error : %s -
ERR_UNKNOWN_TYPE
Unknown operation type : %s -
ERR_OPERATION_NOT_FOUND_IN_PENDING
Internal Error : Operation %s change number %s was not found in local change list -
ERR_OPERATION_NOT_FOUND_IN_REMOTE
Internal Error : Operation %s change number %s was not found in remote change list -
ERR_COULD_NOT_READ_DB
The replication server failed to start because the database %s could not be read : %s -
ERR_EXCEPTION_REPLAYING_OPERATION
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_EXCEPTION_REPLAYING_OPERATIONObject, Object> An Exception was caught while replaying operation %s %s (%s) : %s -
DEBUG_ERROR_UPDATING_RUV
public static LocalizableMessageDescriptor.Arg4<Object,Object, DEBUG_ERROR_UPDATING_RUVObject, Object> Error %s when updating server state %s : %s base dn : %s -
ERR_ERROR_SEARCHING_RUV
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_ERROR_SEARCHING_RUVObject, Object> Error %s when searching for server state %s : %s base dn : %s -
ERR_EXCEPTION_SENDING_TOPO_INFO
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_EXCEPTION_SENDING_TOPO_INFOObject, Object> Caught IOException while sending topology info (for update) on domain %s for %s server %s : %s -
ERR_CANNOT_RECOVER_CHANGES
Error when searching old changes from the database for base DN %s: %s -
ERR_EXCEPTION_DECODING_OPERATION
Error trying to replay %s, operation could not be decoded: %s -
ERR_EXCEPTION_CHANGELOG_TRIM_FLUSH
Error during the Replication Server database trimming or flush process. The Changelog service is going to shutdown: %s -
ERR_WRITER_UNEXPECTED_EXCEPTION
An unexpected error happened handling connection with %s. This connection is going to be closed -
ERR_LOOP_REPLAYING_OPERATION
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_LOOP_REPLAYING_OPERATIONObject, Object> A loop was detected while replaying operation: %s %s (%s) error %s -
ERR_FILE_CHECK_CREATE_FAILED
An Exception was caught while testing existence or trying to create the directory for the Replication Server database : %s %s -
ERR_SIMULTANEOUS_IMPORT_EXPORT_REJECTED
The current request is rejected due to an import or an export already in progress for the same data -
ERR_INVALID_IMPORT_SOURCE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_INVALID_IMPORT_SOURCEObject, Object> On domain %s, initialization of server with serverId:%s has been requested from a server with an invalid serverId:%s. %s -
ERR_INVALID_EXPORT_TARGET
Invalid target for the export -
ERR_NO_REACHABLE_PEER_IN_THE_DOMAIN
Domain %s: the server with serverId=%s is unreachable -
ERR_NO_MATCHING_DOMAIN
No domain matches the provided base DN '%s' -
ERR_MULTIPLE_MATCHING_DOMAIN
Multiple domains match the base DN provided -
ERR_INVALID_PROVIDER
The provider class does not allow the operation requested -
NOTE_READER_EXCEPTION
Exception when reading messages from %s: %s -
ERR_DUPLICATE_SERVER_ID
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_DUPLICATE_SERVER_IDObject, Object, Object> 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 -
ERR_DUPLICATE_REPLICATION_SERVER_ID
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_DUPLICATE_REPLICATION_SERVER_IDObject, Object> 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 -
ERR_BAD_HISTORICAL
Entry %s was containing some unknown historical information, This may cause some inconsistency for this entry -
ERR_CANNOT_ADD_CONFLICT_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_CANNOT_ADD_CONFLICT_ATTRIBUTEObject, Object> A conflict was detected but the conflict information could not be added to entry %s. Conflict with %s %s, Result: %s -
ERR_CANNOT_RENAME_CONFLICT_ENTRY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CANNOT_RENAME_CONFLICT_ENTRYObject> An error happened trying to rename a conflicting entry. DN: %s, Operation: %s, Result: %s -
ERR_REPLICATION_COULD_NOT_CONNECT
The Replication is configured for suffix %s but was not able to connect to any Replication Server -
ERR_CHANGELOG_ERROR_SENDING_ERROR
An unexpected error occurred while sending an Error Message to %s. This connection is going to be closed and reopened -
ERR_CHANGELOG_ERROR_SENDING_MSG
An unexpected error occurred while sending a Message to %s. This connection is going to be closed and reopened -
ERR_ERROR_REPLAYING_OPERATION
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_ERROR_REPLAYING_OPERATIONObject, Object, Object> Could not replay operation %s %s with ChangeNumber %s error %s %s -
ERR_UNKNOWN_ATTRIBUTE_IN_HISTORICAL
The entry %s has historical information for attribute %s which is not defined in the schema. This information will be ignored -
ERR_COULD_NOT_CLOSE_THE_SOCKET
The Replication Server socket could not be closed : %s -
ERR_COULD_NOT_STOP_LISTEN_THREAD
The thread listening on the replication server port could not be stopped : %s -
ERR_SEARCHING_GENERATION_ID
An unexpected error occurred when loading the generation id of domain "%s": %s -
ERR_SEARCHING_DOMAIN_BACKEND
An unexpected error occurred when looking for the replicated backend : %s. It may be not configured or disabled -
ERR_LOADING_GENERATION_ID
An unexpected error occurred when searching in %s for the generation ID : %s -
ERR_UPDATING_GENERATION_ID
An unexpected error occurred when updating generation ID for domain "%s": %s -
ERR_ERROR_MSG_RECEIVED
The following error has been received : %s -
ERR_INIT_IMPORT_NOT_SUPPORTED
Initialization cannot be done because import is not supported by the backend %s -
ERR_INIT_EXPORT_NOT_SUPPORTED
Initialization cannot be done because export is not supported by the backend %s -
ERR_INIT_CANNOT_LOCK_BACKEND
Initialization cannot be done because the following error occurred while locking the backend %s : %s -
ERR_EXCEPTION_LISTENING
Replication server caught exception while listening for client connections: %s -
ERR_ERROR_CLEARING_DB
While clearing the database %s, the following error happened: %s -
ERR_CHECK_CREATE_REPL_BACKEND_FAILED
An unexpected error occurred when testing existence or creating the replication backend : %s -
ERR_BACKEND_SEARCH_ENTRY
An error occurred when searching for %s : %s -
ERR_UNKNOWN_DN
The base DN %s is not stored by any of the Directory Server backend -
ERR_EXCEPTION_REPLAYING_REPLICATION_MESSAGE
An Exception was caught while replaying replication message : %s -
ERR_PUBLISHING_FAKE_OPS
Caught exception publishing fake operations for domain %s : %s -
NOTE_SERVER_STATE_RECOVERY
ServerState recovery for domain %s, updated with changeNumber %s -
ERR_RESET_GENERATION_CONN_ERR_ID
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_RESET_GENERATION_CONN_ERR_IDObject> 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 -
ERR_RS_DN_DOES_NOT_MATCH
DN sent by remote replication server: %s does not match local replication server one: %s -
ERR_DS_DN_DOES_NOT_MATCH
DN sent by replication server: %s does not match local directory server one: %s -
ERR_EXCEPTION_FORWARDING_RESET_GEN_ID
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EXCEPTION_FORWARDING_RESET_GEN_IDCaught IOException while forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %s -
ERR_RS_INVALID_INIT_STATUS
Replication server received invalid initial status: %s for replication domain %s from server id %s -
ERR_DS_INVALID_REQUESTED_STATUS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DS_INVALID_REQUESTED_STATUSObject> Received invalid requested status %s in DS replication domain %s with server id %s -
ERR_RS_CANNOT_CHANGE_STATUS
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_RS_CANNOT_CHANGE_STATUSObject, Object> Could not compute new status in RS replication domain %s for server id %s. Was in %s status and received %s event -
ERR_DS_CANNOT_CHANGE_STATUS
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_DS_CANNOT_CHANGE_STATUSObject, Object> Could not compute new status in DS replication domain %s with server id %s. Was in %s status and received %s event -
ERR_EXCEPTION_CHANGING_STATUS_AFTER_RESET_GEN_ID
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_EXCEPTION_CHANGING_STATUS_AFTER_RESET_GEN_IDObject> Caught IOException while changing status for domain %s and serverId: %s after reset for generation id: %s -
ERR_RECEIVED_CHANGE_STATUS_NOT_FROM_DS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_RECEIVED_CHANGE_STATUS_NOT_FROM_DSObject> Received change status message does not come from a directory server (dn: %s, server id: %s, msg: %s) -
ERR_RS_INVALID_NEW_STATUS
Received invalid new status %s in RS for replication domain %s and directory server id %s -
WARN_CONNECTED_TO_SERVER_WITH_WRONG_GROUP_ID
public static LocalizableMessageDescriptor.Arg6<Object,Object, WARN_CONNECTED_TO_SERVER_WITH_WRONG_GROUP_IDObject, Object, Object, Object> Connected to a replication server with wrong group id. We have group id %s and replication server id %s %s has group id %s. This is for domain %s in directory server %s -
ERR_EXCEPTION_SENDING_CS
Replication broker with dn %s and server id %s failed to signal status change because of: %s -
ERR_EXCEPTION_CHANGING_STATUS_FROM_STATUS_ANALYZER
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_EXCEPTION_CHANGING_STATUS_FROM_STATUS_ANALYZERObject> Caught IOException while changing status for domain %s and serverId: %s from status analyzer: %s -
NOTE_BAD_DATA_IN_FULL_UPDATE
Ignoring reset generation ID request from '%s' to '%s' for replica '%s' because the replica is being re-initialized -
ERR_RESET_GENERATION_ID_FAILED
The generation ID could not be reset for domain %s -
NOTE_ERR_CANNOT_CHANGE_CONFIG_DURING_TOTAL_UPDATE
Cannot change the configuration while a total update is in progress -
ERR_COULD_NOT_START_REPLICATION
The Replication was not started on base-dn %s : %s -
ERR_REPLICATION_PROTOCOL_MESSAGE_TYPE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_REPLICATION_PROTOCOL_MESSAGE_TYPEReplication protocol error. Bad message type. %s received, %s required -
NOTE_ERR_FRACTIONAL_CONFIG_UNKNOWN_OBJECT_CLASS
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_ERR_FRACTIONAL_CONFIG_UNKNOWN_OBJECT_CLASSWrong fractional replication configuration: could not find object class definition for %s in schema -
NOTE_ERR_FRACTIONAL_CONFIG_UNKNOWN_ATTRIBUTE_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_ERR_FRACTIONAL_CONFIG_UNKNOWN_ATTRIBUTE_TYPEWrong fractional replication configuration : could not find attribute type definition for %s in schema -
NOTE_ERR_FRACTIONAL_CONFIG_NOT_OPTIONAL_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_ERR_FRACTIONAL_CONFIG_NOT_OPTIONAL_ATTRIBUTEWrong fractional replication configuration : attribute %s is not optional in class %s -
NOTE_ERR_FRACTIONAL_CONFIG_WRONG_FORMAT
Wrong fractional replication configuration : wrong format : %s (need at least [<className>|*],attributeName) -
NOTE_ERR_FRACTIONAL_CONFIG_BOTH_MODES
Wrong fractional replication configuration : cannot use both exclusive and inclusive modes -
NOTE_ERR_FRACTIONAL_CONFIG_PROHIBITED_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_ERR_FRACTIONAL_CONFIG_PROHIBITED_ATTRIBUTEWrong fractional replication configuration : prohibited attribute %s usage -
NOTE_ERR_FRACTIONAL
Fractional replication : exception for domain : %s : %s -
NOTE_FRACTIONAL_BAD_DATA_SET_NEED_RESYNC
Warning : domain %s fractional replication configuration is inconsistent with backend data set : need resynchronization or fractional configuration to be changed -
ERR_PLUGIN_FRACTIONAL_LDIF_IMPORT_INVALID_PLUGIN_TYPE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_PLUGIN_FRACTIONAL_LDIF_IMPORT_INVALID_PLUGIN_TYPEThe fractional replication ldif import plugin is configured with invalid plugin type %s. Only the ldifImport plugin type is allowed -
NOTE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_BAD_REMOTE
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_BAD_REMOTEThe online full update for importing suffix %s data from remote directory server %s has been stopped due to fractional configuration inconsistency between destination and source server : imported data set has not the same fractional configuration -
NOTE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_REMOTE_IS_FRACTIONAL
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_REMOTE_IS_FRACTIONALThe online full update for importing suffix %s data from remote directory server %s has been stopped due to fractional configuration inconsistency between destination and source server : imported data set has some fractional configuration but not destination server -
NOTE_ERR_FRACTIONAL_FORBIDDEN_OPERATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_ERR_FRACTIONAL_FORBIDDEN_OPERATIONThe following operation has been forbidden in suffix %s due to inconsistency with the fractional replication configuration : %s -
NOTE_ERR_FRACTIONAL_FORBIDDEN_FULL_UPDATE_FRACTIONAL
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_ERR_FRACTIONAL_FORBIDDEN_FULL_UPDATE_FRACTIONALThe export of domain %s from server %s to all other servers of the topology is forbidden as the source server has some fractional configuration : only fractional servers in a replicated topology does not make sense -
ERR_CHANGENUMBER_DATABASE
An error occurred when accessing the change number database : %s -
ERR_INITIALIZATION_FAILED_NOCONN
The initialization failed because the domain %s is not connected to a replication server -
ERR_FRACTIONAL_COULD_NOT_RETRIEVE_CONFIG
Could not retrieve the configuration for a replication domain matching the entry %s -
NOTE_ERR_LDIF_IMPORT_FRACTIONAL_BAD_DATA_SET
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_ERR_LDIF_IMPORT_FRACTIONAL_BAD_DATA_SETThe LDIF import for importing suffix %s data has been stopped due to fractional configuration inconsistency : imported data set has not the same fractional configuration as local server -
NOTE_ERR_LDIF_IMPORT_FRACTIONAL_DATA_SET_IS_FRACTIONAL
public static LocalizableMessageDescriptor.Arg1<Object> NOTE_ERR_LDIF_IMPORT_FRACTIONAL_DATA_SET_IS_FRACTIONALThe LDIF import for importing suffix %s data has been stopped due to fractional configuration inconsistency : imported data set has some fractional configuration but not local server -
WARN_DS_DISCONNECTED_DURING_HANDSHAKE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_DS_DISCONNECTED_DURING_HANDSHAKEObject> A transient problem occurred while Directory Server %s was connecting to this Replication Server %s. The peer server may try to establish a connection again. The problem was: %s -
WARN_RS_DISCONNECTED_DURING_HANDSHAKE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_RS_DISCONNECTED_DURING_HANDSHAKEObject> A transient problem occurred while Replication Server %s was connecting to this Replication Server %s. The Replication Server should try to reconnect later. The problem was: %s -
NOTE_ERR_UNABLE_TO_ENABLE_ECL_VIRTUAL_ATTR
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_ERR_UNABLE_TO_ENABLE_ECL_VIRTUAL_ATTRError when loading a virtual attribute for external change log: Attribute: %s , Error: %s -
ERR_RESYNC_REQUIRED_UNKNOWN_DOMAIN_IN_PROVIDED_COOKIE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_RESYNC_REQUIRED_UNKNOWN_DOMAIN_IN_PROVIDED_COOKIEFull resync required. Reason: The provided cookie contains unknown replicated domain %s. Current starting cookie <%s> -
ERR_RESYNC_REQUIRED_TOO_OLD_DOMAIN_IN_PROVIDED_COOKIE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_RESYNC_REQUIRED_TOO_OLD_DOMAIN_IN_PROVIDED_COOKIEFull resync required. Reason: The provided cookie is older than the start of historical in the server for the replicated domain : %s -
ERR_INVALID_COOKIE_SYNTAX
Invalid syntax for the provided cookie '%s' -
ERR_INIT_EXPORTER_DISCONNECTION
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_INIT_EXPORTER_DISCONNECTIONObject> Domain %s (server id: %s) : remote exporter server disconnection (server id: %s ) detected during initialization -
ERR_INIT_IMPORT_FAILURE
During initialization from a remote server, the following error occurred : %s -
ERR_INIT_RS_DISCONNECTION_DURING_IMPORT
Connection failure with Replication Server %s during import -
ERR_INIT_BAD_MSG_ID_SEQ_DURING_IMPORT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_INIT_BAD_MSG_ID_SEQ_DURING_IMPORTBad msg id sequence during import. Expected:%s Actual:%s -
ERR_INIT_NO_SUCCESS_START_FROM_SERVERS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_INIT_NO_SUCCESS_START_FROM_SERVERSThe following servers did not acknowledge initialization in the expected time for domain %s. They are potentially down or too slow. Servers list: %s -
ERR_INIT_NO_SUCCESS_END_FROM_SERVERS
The following servers did not end initialization being connected with the right generation (%s). They are potentially stopped or too slow. Servers list: %s -
ERR_INIT_RS_DISCONNECTION_DURING_EXPORT
When initializing remote server(s), connection to Replication Server with serverId=%s is lost -
ERR_INIT_HEARTBEAT_LOST_DURING_EXPORT
When initializing remote server(s), the initialized server with serverId=%s is potentially stopped or too slow -
ERR_SENDING_NEW_ATTEMPT_INIT_REQUEST
When sending a new initialization request for an initialization from a remote server, the following error occurred %s. The initial error was : %s -
NOTE_RESENDING_INIT_FROM_REMOTE_REQUEST
Resending a new initialization request for an initialization from a remote server due to the root error : %s -
ERR_COULD_NOT_SOLVE_CONFLICT
Error while trying to solve conflict with DN : %s ERROR : %s -
NOTE_REPLICATION_SERVER_LISTENING
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_REPLICATION_SERVER_LISTENINGNumber> Replication server RS(%s) started listening for new connections on address %s port %d -
INFO_REPLICATION_SERVER_CONNECTION_TO_RS
public static LocalizableMessageDescriptor.Arg4<Object,Object, INFO_REPLICATION_SERVER_CONNECTION_TO_RSObject, Object> Replication server RS(%s) has connected to replication server RS(%s) for domain "%s" at %s -
INFO_REPLICATION_SERVER_CONNECTION_FROM_RS
public static LocalizableMessageDescriptor.Arg4<Object,Object, INFO_REPLICATION_SERVER_CONNECTION_FROM_RSObject, Object> Replication server RS(%s) has accepted a connection from replication server RS(%s) for domain "%s" at %s -
INFO_REPLICATION_SERVER_CONNECTION_FROM_DS
public static LocalizableMessageDescriptor.Arg4<Object,Object, INFO_REPLICATION_SERVER_CONNECTION_FROM_DSObject, Object> Replication server RS(%s) has accepted a connection from directory server DS(%s) for domain "%s" at %s -
NOTE_NOW_FOUND_SAME_GENERATION_CHANGELOG
public static LocalizableMessageDescriptor.Arg5<Object,Object, NOTE_NOW_FOUND_SAME_GENERATION_CHANGELOGObject, Object, Object> Directory server DS(%s) has connected to replication server RS(%s) for domain "%s" at %s with generation ID %s -
WARN_NOW_FOUND_BAD_GENERATION_CHANGELOG
public static LocalizableMessageDescriptor.Arg6<Object,Object, WARN_NOW_FOUND_BAD_GENERATION_CHANGELOGObject, Object, Object, Object> Directory server DS(%s) has connected to replication server RS(%s) for domain "%s" at %s, but the generation IDs do not match, indicating that a full re-initialization is required. The local (DS) generation ID is %s and the remote (RS) generation ID is %s -
WARN_COULD_NOT_FIND_CHANGELOG
Directory server DS(%s) was unable to connect to any of the following replication servers for domain "%s": %s -
WARN_NO_AVAILABLE_CHANGELOGS
Directory server DS(%s) was unable to connect to any replication servers for domain "%s" -
WARN_REPLICATION_SERVER_PROPERLY_DISCONNECTED
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_REPLICATION_SERVER_PROPERLY_DISCONNECTEDObject, Object> Replication server RS(%s) at %s has closed the connection to this directory server DS(%s). This directory server will now try to connect to another replication server in order to receive changes for the domain "%s" -
WARN_REPLICATION_SERVER_BADLY_DISCONNECTED
public static LocalizableMessageDescriptor.Arg5<Object,Object, WARN_REPLICATION_SERVER_BADLY_DISCONNECTEDObject, Object, Object> Directory server DS(%s) encountered an error while receiving changes for domain "%s" from replication server RS(%s) at %s. The connection will be closed, and this directory server will now try to connect to another replication server. The error was: %s -
NOTE_NEW_BEST_REPLICATION_SERVER
public static LocalizableMessageDescriptor.Arg7<Object,Object, NOTE_NEW_BEST_REPLICATION_SERVERObject, Object, Object, Object, Object> Directory Server DS(%s) is switching from replication server RS(%s) at %s to RS(%s) for domain "%s" because it is more suitable. The previous replication server evaluation was: "%s", and the new replication server evaluation was: "%s" -
NOTE_FULL_UPDATE_ENGAGED_FROM_REMOTE_START
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_FULL_UPDATE_ENGAGED_FROM_REMOTE_STARTObject> Starting total update: importing domain "%s" from remote directory server DS(%s) to this directory server DS(%s) -
NOTE_FULL_UPDATE_ENGAGED_FROM_REMOTE_END
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_FULL_UPDATE_ENGAGED_FROM_REMOTE_ENDObject, Object> Finished total update: imported domain "%s" from remote directory server DS(%s) to this directory server DS(%s). %s -
NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START
public static LocalizableMessageDescriptor.Arg4<Number,Object, NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_STARTObject, Object> Starting total update: exporting %d entries in domain "%s" from this directory server DS(%s) to remote directory server DS(%s) -
NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_ALL
public static LocalizableMessageDescriptor.Arg3<Number,Object, NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_ALLObject> Starting total update: exporting %d entries in domain "%s" from this directory server DS(%s) to all remote directory servers -
NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_ENDObject, Object> Finished total update: exported domain "%s" from this directory server DS(%s) to remote directory server DS(%s). %s -
NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_ALL
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_ALLObject> Finished total update: exported domain "%s" from this directory server DS(%s) to all remote directory servers. %s -
NOTE_DIRECTORY_SERVER_CHANGED_STATUS
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_DIRECTORY_SERVER_CHANGED_STATUSObject> Directory server DS(%s) for domain "%s" has changed its status to %s -
WARN_HEARTBEAT_FAILURE
Directory server DS(%s) is closing its connection to replication server RS(%s) at %s for domain "%s" because it could not detect a heart beat -
WARN_BAD_GENERATION_ID_FROM_RS
public static LocalizableMessageDescriptor.Arg6<Object,Object, WARN_BAD_GENERATION_ID_FROM_RSObject, Object, Object, Object> Replication server RS(%s) at %s presented generation ID %s for domain "%s", but the generation ID of this replication server RS(%s) is %s. This usually indicates that one or more directory servers in the replication topology have not been initialized with the same data, and re-initialization is required -
NOTE_RESET_GENERATION_ID
The generation ID for domain "%s" has been reset to %s -
WARN_TIMEOUT_WHEN_CROSS_CONNECTION
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_TIMEOUT_WHEN_CROSS_CONNECTIONObject, Object> Timed out while trying to acquire the domain lock for domain "%s". The connection attempt from replication server RS(%s) at %s to this replication server RS(%s) will be aborted. This is probably benign and a result of a simultaneous cross connection attempt -
WARN_BAD_GENERATION_ID_FROM_DS
public static LocalizableMessageDescriptor.Arg6<Object,Object, WARN_BAD_GENERATION_ID_FROM_DSObject, Object, Object, Object> Directory server DS(%s) at %s presented generation ID %s for domain "%s", but the generation ID of this replication server RS(%s) is %s. This usually indicates that one or more directory servers in the replication topology have not been initialized with the same data, and re-initialization is required -
ERROR_IGNORING_UPDATE_FROM_RS
public static LocalizableMessageDescriptor.Arg7<Object,Object, ERROR_IGNORING_UPDATE_FROM_RSObject, Object, Object, Object, Object> Replication server RS(%s) ignoring update %s for domain "%s" from replication server RS(%s) at %s because its generation ID %s is different to the local generation ID %s -
WARN_IGNORING_UPDATE_TO_RS
public static LocalizableMessageDescriptor.Arg7<Object,Object, WARN_IGNORING_UPDATE_TO_RSObject, Object, Object, Object, Object> Replication server RS(%s) not sending update %s for domain "%s" to replication server RS(%s) at %s because its generation ID %s is different to the local generation ID %s -
WARN_IGNORING_UPDATE_FROM_DS_BAD_DATA
public static LocalizableMessageDescriptor.Arg7<Object,Object, WARN_IGNORING_UPDATE_FROM_DS_BAD_DATAObject, Object, Object, Object, Object> Replication server RS(%s) ignoring update %s for domain "%s" from directory server DS(%s) at %s because its generation ID %s is different to the local generation ID %s -
WARN_IGNORING_UPDATE_TO_DS_BAD_DATA
public static LocalizableMessageDescriptor.Arg7<Object,Object, WARN_IGNORING_UPDATE_TO_DS_BAD_DATAObject, Object, Object, Object, Object> Replication server RS(%s) not sending update %s for domain "%s" to directory server DS(%s) at %s because its generation ID %s is different to the local generation ID %s -
WARN_IGNORING_UPDATE_FROM_DS_FULLUP
public static LocalizableMessageDescriptor.Arg5<Object,Object, WARN_IGNORING_UPDATE_FROM_DS_FULLUPObject, Object, Object> Replication server RS(%s) ignoring update %s for domain "%s" from directory server DS(%s) at %s because it is currently performing a full update -
WARN_IGNORING_UPDATE_TO_DS_FULLUP
public static LocalizableMessageDescriptor.Arg5<Object,Object, WARN_IGNORING_UPDATE_TO_DS_FULLUPObject, Object, Object> Replication server RS(%s) not sending update %s for domain "%s" to directory server DS(%s) at %s because it is currently performing a full update -
ERR_RS_BADLY_DISCONNECTED
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_RS_BADLY_DISCONNECTEDObject, Object> The connection from this replication server RS(%s) to replication server RS(%s) at %s for domain "%s" has failed -
ERR_DS_BADLY_DISCONNECTED
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_DS_BADLY_DISCONNECTEDObject, Object> The connection from this replication server RS(%s) to directory server DS(%s) at %s for domain "%s" has failed -
WARN_NO_CHANGELOG_SERVER_LISTENING
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_NO_CHANGELOG_SERVER_LISTENINGObject> Directory server DS(%s) was unable to connect to replication server %s for domain "%s". Please check that there is a replication server listening at this address -
WARN_TIMEOUT_CONNECTING_TO_RS
Directory server DS(%s) timed out while connecting to replication server %s for domain "%s" -
ERR_EXCEPTION_STARTING_SESSION_PHASE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_EXCEPTION_STARTING_SESSION_PHASEObject, Object> Directory server DS(%s) encountered an unexpected error while connecting to replication server %s for domain "%s": %s -
WARN_EXCEPTION_STARTING_SESSION_PHASE
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_EXCEPTION_STARTING_SESSION_PHASEObject, Object> Directory server DS(%s) encountered a transient problem while connecting to replication server %s for domain "%s". Directory server will try to connect to a replication server again. The problem was: %s -
INFO_SSL_SERVER_CON_ATTEMPT_ERROR
public static LocalizableMessageDescriptor.Arg3<Object,Object, INFO_SSL_SERVER_CON_ATTEMPT_ERRORObject> Replication server accepted a connection from %s to local address %s but the SSL handshake failed. This is probably benign, but may indicate a transient network outage or a misconfigured client application connecting to this replication server. The error was: %s -
NOTE_LOAD_BALANCE_REPLICATION_SERVER
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_LOAD_BALANCE_REPLICATION_SERVERObject, Object> Directory Server DS(%s) is disconnecting from replication server RS(%s) at %s for domain "%s" in order to find another replication server in the topology and distribute load more equally -
WARN_INVALID_SYNC_HIST_VALUE
The attribute value '%s' is not a valid synchronization history value -
WARN_CANNOT_OPEN_DATABASE_BECAUSE_SHUTDOWN_WAS_REQUESTED
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CANNOT_OPEN_DATABASE_BECAUSE_SHUTDOWN_WAS_REQUESTEDCannot open database %s because shutdown was requested from replication server RS(%s) -
NOTE_RS_HAS_NO_GENERATION_ID
RS(%s) has no generation Id, but at least one other RS has the same generation Id %s as DS(%s) -
NOTE_RS_HAS_DIFFERENT_GENERATION_ID_THAN_DS
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_RS_HAS_DIFFERENT_GENERATION_ID_THAN_DSObject, Object> RS(%s) generation Id %s does not match DS(%s) generation Id %s, but at least another RS does -
NOTE_RS_HAS_DIFFERENT_GROUP_ID_THAN_DS
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_RS_HAS_DIFFERENT_GROUP_ID_THAN_DSObject, Object> RS(%s) groupId '%s' does not match DS(%s) groupId '%s', but at least one other RS does -
NOTE_RS_LATER_THAN_LOCAL_DS
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_RS_LATER_THAN_LOCAL_DSObject, Object> RS(%s) newest change %s is behind DS(%s) newest change %s, but at least another RS is at the same point or ahead of the DS -
NOTE_RS_LATER_THAN_ANOTHER_RS_MORE_UP_TO_DATE_THAN_LOCAL_DS
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_RS_LATER_THAN_ANOTHER_RS_MORE_UP_TO_DATE_THAN_LOCAL_DSObject, Object> RS(%s) newest change %s is behind another RS which is ahead of DS(%s) newest change %s -
NOTE_RS_ON_DIFFERENT_VM_THAN_DS
RS(%s) is not on the same virtual machine as DS(%s) but another RS is -
NOTE_RS_ON_DIFFERENT_HOST_THAN_DS
RS(%s) is on a different host than DS(%s), but at least another RS is on the same host -
NOTE_DISCONNECT_DS_FROM_OVERLOADED_RS
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_DISCONNECT_DS_FROM_OVERLOADED_RSDS(%s) disconnected from overloaded RS(%s) -
NOTE_DO_NOT_DISCONNECT_DS_FROM_OVERLOADED_RS
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_DO_NOT_DISCONNECT_DS_FROM_OVERLOADED_RSDS(%s) not disconnected from overloaded RS(%s), other DSs will disconnect -
NOTE_NO_NEED_TO_REBALANCE_DSS_BETWEEN_RSS
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_NO_NEED_TO_REBALANCE_DSS_BETWEEN_RSSDS(%s) not disconnected from current RS(%s), since there is no need to rebalance all directory servers to other replication servers in the topology -
NOTE_DO_NOT_DISCONNECT_DS_FROM_ACCEPTABLE_LOAD_RS
public static LocalizableMessageDescriptor.Arg2<Object,Object> NOTE_DO_NOT_DISCONNECT_DS_FROM_ACCEPTABLE_LOAD_RSDS(%s) not disconnected from current RS(%s), because RS is underloaded or its load goal is reached -
NOTE_BIGGEST_WEIGHT_RS
DS(%s) will connect to RS(%s) because it has the biggest weight among all the replication servers -
NOTE_AVOID_YOYO_EFFECT
DS(%s) stayed connected to RS(%s) to avoid the yoyo effect -
NOTE_BEST_RS
RS(%s) has been evaluated to be the best replication server for DS(%s) to connect to because it was the only one standing after all tests -
NOTE_UNKNOWN_RS
RS(%s) could not be contacted by DS(%s) -
ERR_CANNOT_CREATE_REPLICA_DB_BECAUSE_CHANGELOG_DB_SHUTDOWN
public static LocalizableMessageDescriptor.Arg0 ERR_CANNOT_CREATE_REPLICA_DB_BECAUSE_CHANGELOG_DB_SHUTDOWNCould not create replica database because the changelog database is shutting down -
ERR_COULD_NOT_ADD_CHANGE_TO_SHUTTING_DOWN_REPLICA_DB
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_COULD_NOT_ADD_CHANGE_TO_SHUTTING_DOWN_REPLICA_DBObject> Could not add change %s to replicaDB %s %s because flushing thread is shutting down -
ERR_CHANGELOG_READ_STATE_CANT_READ_DOMAIN_DIRECTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_READ_STATE_CANT_READ_DOMAIN_DIRECTORYError when retrieving changelog state from root path '%s' : IO error on domain directory '%s' when retrieving list of server ids -
ERR_CHANGELOG_UNABLE_TO_CREATE_REPLICA_DB
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_CHANGELOG_UNABLE_TO_CREATE_REPLICA_DBObject, Object> Could not get or create replica DB for base DN '%s', serverId '%s', generationId '%s': %s -
ERR_CHANGELOG_UNABLE_TO_CREATE_CN_INDEX_DB
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_UNABLE_TO_CREATE_CN_INDEX_DBObject> Could not get or create change number index DB in root path '%s', using path '%s': %s -
ERR_CHANGELOG_UNABLE_TO_DELETE_GENERATION_ID_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_UNABLE_TO_DELETE_GENERATION_ID_FILEObject> Could not delete generation id file '%s' for DN '%s': %s -
ERR_CHANGELOG_UNABLE_TO_CREATE_SERVER_ID_DIRECTORY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_UNABLE_TO_CREATE_SERVER_ID_DIRECTORYObject> Could not create directory '%s' for server id %s: %s -
ERR_CHANGELOG_UNABLE_TO_CREATE_GENERATION_ID_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_CREATE_GENERATION_ID_FILECould not create generation id file '%s': %s -
ERR_CHANGELOG_SERVER_ID_FILENAME_WRONG_FORMAT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_SERVER_ID_FILENAME_WRONG_FORMATCould not read server id filename because it uses a wrong format, expecting '[id].server' where [id] is numeric but got '%s' -
ERR_CHANGELOG_GENERATION_ID_WRONG_FORMAT
Could not read generation id because it uses a wrong format, expecting a number but got '%s' -
ERR_CHANGELOG_UNABLE_TO_OPEN_LOG_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_OPEN_LOG_FILECould not open log file '%s' for write: %s -
ERR_CHANGELOG_UNABLE_TO_OPEN_READER_ON_LOG_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_OPEN_READER_ON_LOG_FILECould not open a reader on log file '%s': %s -
ERR_CHANGELOG_UNABLE_TO_DECODE_RECORD
Could not decode a record from data read in log file '%s' -
ERR_CHANGELOG_UNABLE_TO_DELETE_LOG_FILE
Could not delete log files: %s -
ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_FILECould not create log file '%s': %s -
WARN_CHANGELOG_NOT_ENABLED_FOR_WRITE
The changelog '%s' has been opened in read-only mode, it is not enabled for write -
ERR_CHANGELOG_UNABLE_TO_ADD_RECORD
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_UNABLE_TO_ADD_RECORDObject> Could not add record '%s' in log file '%s': %s -
ERR_CHANGELOG_UNABLE_TO_SYNC
Could not synchronize written records to file system for log file '%s': %s -
ERR_CHANGELOG_UNABLE_TO_SEEK
Could not seek to position %d for reader on log file '%s' -
ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_DIRECTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_DIRECTORYCould not create root directory '%s' for log file: %s -
ERR_CHANGELOG_UNABLE_TO_DECODE_DN_FROM_DOMAIN_STATE_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_DECODE_DN_FROM_DOMAIN_STATE_FILECould not decode DN from domain state file '%s', from line '%s' -
ERR_CHANGELOG_UNABLE_TO_READ_DOMAIN_STATE_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_READ_DOMAIN_STATE_FILECould not read domain state file '%s'. The replication server cannot continue, it should be restored from a backup. Cause was : %s -
ERR_CHANGELOG_INCOHERENT_DOMAIN_STATE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_INCOHERENT_DOMAIN_STATEThere 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 -
ERR_CHANGELOG_UNABLE_TO_UPDATE_DOMAIN_STATE_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_UNABLE_TO_UPDATE_DOMAIN_STATE_FILEObject> 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 -
ERR_CHANGELOG_UNABLE_TO_DECODE_KEY_FROM_STRING
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_UNABLE_TO_DECODE_KEY_FROM_STRINGCould not decode the key from string [%s] -
ERR_CHANGELOG_UNABLE_TO_INITIALIZE_LOG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_INITIALIZE_LOGCould not initialize the log '%s' : %s -
ERR_CHANGELOG_UNABLE_TO_RETRIEVE_KEY_BOUNDS_FROM_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_RETRIEVE_KEY_BOUNDS_FROM_FILECould not retrieve key bounds from log file '%s': %s -
ERR_CHANGELOG_UNABLE_TO_RETRIEVE_READ_ONLY_LOG_FILES_LIST
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_RETRIEVE_READ_ONLY_LOG_FILES_LISTCould not retrieve read-only log files from log '%s': %s -
ERR_CHANGELOG_UNABLE_TO_DELETE_LOG_FILE_WHILE_PURGING
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_UNABLE_TO_DELETE_LOG_FILE_WHILE_PURGINGWhile purging log, could not delete log file(s): '%s' -
ERR_CHANGELOG_UNREFERENCED_LOG_WHILE_RELEASING
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_UNREFERENCED_LOG_WHILE_RELEASINGThe following log '%s' must be released but it is not referenced -
ERR_CHANGELOG_INVALID_REPLICA_OFFLINE_STATE_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_INVALID_REPLICA_OFFLINE_STATE_FILECould not read replica offline state file '%s' for domain %s, it should contain exactly one line corresponding to the offline CSN -
ERR_CHANGELOG_UNABLE_TO_READ_REPLICA_OFFLINE_STATE_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_READ_REPLICA_OFFLINE_STATE_FILECould not read content of replica offline state file '%s' for domain %s -
ERR_CHANGELOG_UNABLE_TO_RETRIEVE_FILE_LENGTH
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_UNABLE_TO_RETRIEVE_FILE_LENGTHCould not retrieve file length of log file '%s' -
ERR_CHANGELOG_UNABLE_TO_RECOVER_LOG_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_UNABLE_TO_RECOVER_LOG_FILEAn 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 -
INFO_CHANGELOG_LOG_FILE_RECOVERED
public static LocalizableMessageDescriptor.Arg3<Object,Number, INFO_CHANGELOG_LOG_FILE_RECOVEREDNumber> Log file '%s' was successfully recovered by removing unreadable records. The file changed size from %d to %d bytes. -
NOTE_SEARCH_CHANGELOG_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform a search request on cn=changelog -
ERR_CHANGELOG_BACKEND_SEARCH
An error occurred when searching base DN '%s' with filter '%s' in changelog backend : %s -
ERR_CHANGELOG_BACKEND_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_BACKEND_ATTRIBUTEObject> An error occurred when retrieving attribute value for attribute '%s' for entry DN '%s' in changelog backend : %s -
ERR_CHANGELOG_UNABLE_TO_CREATE_LAST_LOG_ROTATION_TIME_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Number> ERR_CHANGELOG_UNABLE_TO_CREATE_LAST_LOG_ROTATION_TIME_FILECould not create file '%s' to store last log rotation time %d -
ERR_CHANGELOG_UNABLE_TO_DELETE_LAST_LOG_ROTATION_TIME_FILE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_UNABLE_TO_DELETE_LAST_LOG_ROTATION_TIME_FILECould not delete file '%s' that stored the previous last log rotation time -
ERR_CHANGELOG_CURSOR_ABORTED_PURGE
Cursor on log '%s' has been aborted after a purge -
ERR_CHANGELOG_CANNOT_READ_NEWEST_RECORD
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_CANNOT_READ_NEWEST_RECORDObject> Could not position and read newest record from log file '%s'. Current thread is '%s'. Error was: %s -
ERR_CHANGELOG_RESET_CHANGE_NUMBER_CHANGE_NOT_PRESENT
public static LocalizableMessageDescriptor.Arg3<Number,Object, ERR_CHANGELOG_RESET_CHANGE_NUMBER_CHANGE_NOT_PRESENTObject> 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 -
ERR_CHANGELOG_RESET_CHANGE_NUMBER_CSN_TOO_OLD
public static LocalizableMessageDescriptor.Arg2<Number,Object> ERR_CHANGELOG_RESET_CHANGE_NUMBER_CSN_TOO_OLDThe 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 -
ERR_REPLICATION_CHANGE_NUMBER_DISABLED
Change number indexing is disabled for replication domain '%s' -
ERR_UNRECOGNIZED_RECORD_VERSION
Cannot decode change-log record with version %x -
ERR_FULL_UPDATE_NO_REMOTES
Cannot start total update in domain "%s" from this directory server DS(%s): no remote directory servers found -
ERR_FULL_UPDATE_MISSING_REMOTE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_FULL_UPDATE_MISSING_REMOTEObject> Cannot start total update in domain "%s" from this directory server DS(%s): cannot find remote directory server DS(%s) -
ERR_REPLICATION_UNEXPECTED_MESSAGE
New replication connection from %s started with unexpected message %s and is being closed -
ERR_WRITER_CHANGELOG_CURSOR_ABORTED_FOR_REMOTE_DS
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_WRITER_CHANGELOG_CURSOR_ABORTED_FOR_REMOTE_DSObject, Object> 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) -
ERR_WRITER_CHANGELOG_CURSOR_ABORTED_FOR_REMOTE_RS
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_WRITER_CHANGELOG_CURSOR_ABORTED_FOR_REMOTE_RSObject, Object> 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) -
WARN_CANNOT_SET_BROKER_SOCKET_TIMEOUT
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CANNOT_SET_BROKER_SOCKET_TIMEOUTError while setting replication listener socket timeout to 1 second for domain '%s', server state may be reported as being a bit late with respect to other servers. Cause was: %s -
ERR_INVALID_CSN_RANGE_COMPARISON_OPERATOR
Invalid operator '%s' specified in historicalCsnRangeMatch extensible matching rule assertion -
ERR_INVALID_CSN_RANGE_ASSERTION_SYNTAX
Specified assertion '%s' for historicalCsnRangeMatch extensible matching rule does not conform to expected syntax. The assertion must specify a CSN range -
ERR_CSN_RANGE_INCLUDES_MORE_THAN_ONE_SERVER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CSN_RANGE_INCLUDES_MORE_THAN_ONE_SERVERSpecified CSNs '%s' and '%s' have two different server ids. The historicalCsnRangeMatch extensible matching rule requires CSNs to have the same server id -
ERR_CSN_RANGE_SAME_OPERATOR_TYPE
Specified operators '%s' and '%s' do not specify a range for historicalCsnRangeMatch extensible matching rule -
ERR_COULD_NOT_RESTART_CHANGELOG
Could not restart the Replication Server, bind to listen port %d failed : %s -
ERR_DISK_FULL_CHANGELOG_DIRECTORY
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 -
WARN_DISK_LOW_CHANGELOG_DIRECTORY
Disk space for the replication changelog is getting low. The replication server will continue to operate, but will stop in the event of a full disk -
WARN_REPLICATION_SERVER_RESTARTED
The replication server has detected that the file system containing the changelog has sufficient disk space to resume operation. It is now reconnecting to the rest of the replication topology -
NOTE_READER_IO_EXCEPTION
An I/O error occurred while reading replication messages from %s. The connection will close and replication server (%s) will not process any more updates from it. Reported error is: %s -
NOTE_READER_RECEIVED_STOP
%s is disconnecting from this replication server %s -
ERR_COULD_NOT_STOP_CONNECT_THREAD
The replication server connector thread could not be stopped : %s -
ERR_CHANGELOG_READER_UNABLE_TO_POSITION
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_READER_UNABLE_TO_POSITIONObject> 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 -
ERR_ASSURED_REPLICATION_IS_NOT_SUPPORTED
Assured replication is not supported anymore, it should be disabled on the topology -
ERR_REPLICATION_PROTOCOL_UNEXPECTED_DS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_REPLICATION_PROTOCOL_UNEXPECTED_DSReplication Server '%s' expected to negotiate with another Replication Server but got information for Directory Server '%s' instead. The connection will be closed -
WARN_REPLICATION_DELAY_ABOVE_HEALTH_THRESHOLD
public static LocalizableMessageDescriptor.Arg3<Object,Number, WARN_REPLICATION_DELAY_ABOVE_HEALTH_THRESHOLDNumber> Replication delay for '%s' is above %dms, current delay: %dms -
WARN_DISK_NORMAL_CHANGELOG_DIRECTORY
The replication server has detected that the file system containing the changelog has sufficient disk space to resume operation -
ERR_CHANGELOG_DETECTED_CORRUPTED_FILE
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 -
ERR_CHANGELOG_LOG_FILE_IS_NOT_READABLE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_LOG_FILE_IS_NOT_READABLEAn error occurred while verifying integrity of log file '%s' : %s -
ERR_REPLICATION_SERVER_ID_INCOMPATIBLE_WITH_VERSION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_REPLICATION_SERVER_ID_INCOMPATIBLE_WITH_VERSIONCannot enable replication to server '%s' as this server's ID '%s' is not a number between 1 and 32767 -
ERR_SESSION_SEND_EXCEPTION
An error occurred in session '%s' when trying to send a message to the socket: %s -
ERR_CHANGELOG_BACKEND_CANNOT_CONVERT_TO_LONG
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_BACKEND_CANNOT_CONVERT_TO_LONGCould not convert value '%s' to long -
ERR_CHANGELOG_BACKEND_CANNOT_FIND_UPDATE
Could not find replica update message matching the index record. No more replica update messages with a csn newer than %s exist -
ERR_CHANGELOG_BACKEND_EXCEPTION_ENCODING_ENTRY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CHANGELOG_BACKEND_EXCEPTION_ENCODING_ENTRYObject> An exception was encountered while trying to encode a replication %s message for entry "%s" into an External Change Log entry: %s -
ERR_CHANGELOG_BACKEND_UNEXPECTED_MESSAGE_TYPE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_BACKEND_UNEXPECTED_MESSAGE_TYPEUnexpected message type when trying to create changelog entry for dn %s: '%s' -
ERR_UNROUTABLE_MESSAGE_BECAUSE_ROUTING_TABLE_IS_EMPTY
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_UNROUTABLE_MESSAGE_BECAUSE_ROUTING_TABLE_IS_EMPTYObject> %s in Replication Server=%s, an initialization message of type %s cannot be sent to its destination server. Details: routing table is empty -
ERR_UNROUTABLE_MESSAGE_CAUSED_BY_EXCEPTION
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_UNROUTABLE_MESSAGE_CAUSED_BY_EXCEPTIONObject> %s message of type %s cannot be routed. Details: %s -
ERR_RS_SESSION_PUBLISH_UNABLE_TO_PUSH_MSG_TO_SEND_QUEUE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_RS_SESSION_PUBLISH_UNABLE_TO_PUSH_MSG_TO_SEND_QUEUEError when trying to publish a message in '%s'. The connection is going to be closed and reopened -
ERR_RS_SESSION_PUBLISH_INTERRUPTED_EXCEPTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_RS_SESSION_PUBLISH_INTERRUPTED_EXCEPTIONError when trying to publish a message in '%s'. The connection is going to be closed and reopened. Error: %s -
ERR_RS_SESSION_WRITER_SUBSCRIPTION_WHILE_SESSION_IS_CLOSED
public static LocalizableMessageDescriptor.Arg1<Object> ERR_RS_SESSION_WRITER_SUBSCRIPTION_WHILE_SESSION_IS_CLOSEDError when initializing publisher of messages in '%s' -
ERR_RS_SESSION_WRITER_SUBSCRIPTION_ALREADY_EXISTING_SUBSCRIBER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_RS_SESSION_WRITER_SUBSCRIPTION_ALREADY_EXISTING_SUBSCRIBERError when initializing publisher of messages in '%s' -
ERR_DS_DURING_HANDSHAKE
Directory server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %s -
ERR_RS_DURING_HANDSHAKE
Replication server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %s -
ERR_CHANGELOB_BACKEND_ERROR_ENABLING_CN_CHANGELOG
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOB_BACKEND_ERROR_ENABLING_CN_CHANGELOGError when enabling external changelog: %s -
WARN_DS_DURING_HANDSHAKE_UNEXPECTED_MESSAGE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_DS_DURING_HANDSHAKE_UNEXPECTED_MESSAGEObject> Directory server %s stopped the handshake process with replication server %s because it received the unexpected message '%s' -
INFO_CHANGELOG_CURSOR_INVALIDATED
Cursor on replica '%s' invalidated -
ERR_CHANGELOG_CANNOT_WRITE_DOMAIN_STATE_FILE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_CANNOT_WRITE_DOMAIN_STATE_FILEThe domain state file cannot be written. The server will shutdown but it should be restored from backup. Cause was : %s -
ERR_CHANGELOG_MALFORMED_DOMAIN_STATE_FILE
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 -
INFO_INITIALIZE_WILL_RETRY
Task '%s' to initialize domain '%s' failed to contact the source server. The task will be retried because the current server may be in the process of re-connecting to the best replication server for itself -
INFO_TEMPORARILY_UNREACHABLE_SERVER
public static LocalizableMessageDescriptor.Arg3<Object,Object, INFO_TEMPORARILY_UNREACHABLE_SERVERObject> The server '%s' may retry the initialization process because the server '%s' in domain '%s' is temporarily unreachable -
ERR_FAILED_TO_PURGE_HISTORICAL
Error when purging historical information for entry %s: %s -
ERR_COULD_NOT_SET_LISTEN_SOCKET_TIMEOUT
public static LocalizableMessageDescriptor.Arg2<Number,Object> ERR_COULD_NOT_SET_LISTEN_SOCKET_TIMEOUTReplication server failed to start because setting socket timeout on port %d caused error %s -
WARN_TRANSIENT_SOCKET_PROBLEM
A transient problem occurred while DS(%s) was connecting to RS(%s), Directory Server will try to connect again. Problem was: %s -
ERR_UNROUTABLE_MESSAGE_INITIALIZE_ALL
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_UNROUTABLE_MESSAGE_INITIALIZE_ALLObject> %s for domain %s cannot route message of type %s to all the replicas in the topology because none are reachable -
ERR_UNROUTABLE_MESSAGE_INITIALIZE_REPLICA
public static LocalizableMessageDescriptor.Arg5<Object,Object, ERR_UNROUTABLE_MESSAGE_INITIALIZE_REPLICAObject, Object, Object> %s for domain '%s' cannot route message of type %s to replica %s because it is unreachable. Reachable replicas: %s -
ERR_NOT_CONNECTED_EXPORT_TARGET
Server %s should be initialized but is not connected to the topology -
ERR_CHANGELOG_UNKNOWN_LOG_FILE_VERSION
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_CHANGELOG_UNKNOWN_LOG_FILE_VERSIONNumber> 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 -
NOTE_UNRESOLVED_CONFLICT_DELETE_CHILDREN
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_UNRESOLVED_CONFLICT_DELETE_CHILDRENObject, Object> An unresolved conflict was detected in CSN %s replaying a DELETE of "%s" as child entries exist (renaming child "%s" to "%s"). Consider restoring the parent entry, or deleting the renamed child entries -
NOTE_UNRESOLVED_CONFLICT_ADD_NO_PARENT
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_UNRESOLVED_CONFLICT_ADD_NO_PARENTObject> An unresolved conflict was detected in CSN %s replaying an ADD of "%s" as the parent entry is missing (adding as "%s"). Consider restoring the parent entry, or deleting the new entry -
NOTE_UNRESOLVED_CONFLICT_ADD_EXISTS
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_UNRESOLVED_CONFLICT_ADD_EXISTSObject> An unresolved conflict was detected in CSN %s replaying an ADD of "%s" which already exists (adding as "%s"). Consider reviewing both entries and either merge the contents manually or delete one -
NOTE_UNRESOLVED_CONFLICT_RENAME_NO_PARENT
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_UNRESOLVED_CONFLICT_RENAME_NO_PARENTObject> An unresolved conflict was detected in CSN %s replaying a MODIFYDN of "%s" as the new parent entry "%s" does not exist. Consider restoring the parent entry, or deleting this entry -
NOTE_UNRESOLVED_CONFLICT_RENAME_EXISTS
public static LocalizableMessageDescriptor.Arg4<Object,Object, NOTE_UNRESOLVED_CONFLICT_RENAME_EXISTSObject, Object> An unresolved conflict was detected in CSN %s replaying a MODIFYDN of "%s" to "%s" which already exists (renaming as "%s"). Consider merging the two entries manually, or deleting one of them -
NOTE_RS_HAS_GROUP_WITH_LOWER_PRIORITY
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_RS_HAS_GROUP_WITH_LOWER_PRIORITYObject> RS(%s) groupId '%s' has lower priority than groupId '%s' which matched at least one other RS -
ERR_SERVER_IS_NOT_ALLOWED_TO_SEND_UPDATES
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 -
ERR_CANNOT_VERIFY_CERTIFICATE
Replication peer certificate verification failed with error: %s -
ERR_UNKNOWN_FINGERPRINT_DIGEST
Digest algorithm '%s' of fingerprint '%s' is not supported by the JVM -
ERR_REPLICATION_DEAD_LISTENERS
The following replication server listener threads were unexpectedly stopped: %s. A server restart may be needed -
ERR_CHANGELOG_CURSOR_ABORTED_CLEAR
Cursor on log '%s' has been aborted after a clear -
ERR_REMOTE_EXPORTER_IDLE
Initialization of domain '%s' interrupted: no data received from the remote exporter '%s' for %s -
DEBUG_RECOVERY_SHUTDOWN_REQUESTED
Recovery interrupted because shutdown of replication domain has been requested -
WARN_FORCE_CLOSE_RS_ON_STUCK_CONNECTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_FORCE_CLOSE_RS_ON_STUCK_CONNECTIONThe replication server domain connection for '%s' will be forcibly closed because the peer replication server '%s' is unresponsive -
WARN_FORCE_CLOSE_DS_ON_STUCK_CONNECTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_FORCE_CLOSE_DS_ON_STUCK_CONNECTIONThe replication domain connection for '%s' will be forcibly closed because the peer replication server '%s' is unresponsive -
WARN_CTHEARTBEAT_JOIN_TIMEDOUT
ChangeTime Heartbeat publisher '%s' for domain '%s' will be forcibly stopped because the peer server is unresponsive -
ERR_UNEXPECTED_INTERRUPT_WHILE_PUBLISHING
Publish of a replication message to server '%s' was interrupted -
ERR_DS_STATE_IS_TOO_LATE
Changelog on replication server '%s' 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 -
WARN_IGNORING_UPDATE_TO_TOO_LATE_DS
public static LocalizableMessageDescriptor.Arg5<Object,Object, WARN_IGNORING_UPDATE_TO_TOO_LATE_DSObject, Object, Object> Replication server RS(%s) is not sending update %s for domain '%s' to directory server DS(%s) at %s because the replica is too late and must be re-initialized -
WARN_IGNORING_UPDATE_FROM_TOO_LATE_DS
public static LocalizableMessageDescriptor.Arg5<Object,Object, WARN_IGNORING_UPDATE_FROM_TOO_LATE_DSObject, Object, Object> Replication server RS(%s) is ignoring update %s for domain "%s" from directory server DS(%s) at %s because the replica is too late and must be re-initialized -
WARN_RS_HEARTBEAT_FAILURE
public static LocalizableMessageDescriptor.Arg7<Object,Object, WARN_RS_HEARTBEAT_FAILUREObject, Object, Object, Object, Object> Replication server RS(%s) is closing its connection to %s at %s for domain '%s' because it could not detect a heartbeat: time since last message (%s) is greater than the timeout interval %s ms (heartbeat interval is %s ms) -
WARN_CNI_CANNOT_ADVANCE_REPLICA_NOT_IN_TOPOLOGY
public static LocalizableMessageDescriptor.Arg1<Object> WARN_CNI_CANNOT_ADVANCE_REPLICA_NOT_IN_TOPOLOGYChange number indexing cannot advance because some replicas do not seem to be part of the topology anymore. The changelog will not be able to purge old files until replicas reconnect or their reference is deleted from user data. The following replicas are referenced by replication, but they are not connected to the topology or they have not been properly stopped: %s -
WARN_CNI_CANNOT_ADVANCE_MISSING_UPDATE_FROM_REPLICA
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_CNI_CANNOT_ADVANCE_MISSING_UPDATE_FROM_REPLICAChange number indexing cannot advance because replica '%s' has not sent any messages since '%s'. The changelog is temporarily unable to purge old files. Verify whether the replica is still running or is connected to a replication server -
ERR_INIT_REPLICA_DISCONNECTED_DURING_EXPORT
Replica '%s' seems to have disconnected from the topology while it was being re-initialized, initialization will stop -
ERR_INIT_DOMAIN_IS_STOPPING
Initialization of replication domain '%s' interrupted because the domain is shutting down. The domain still needs to be re-initialized -
INFO_CNI_CAN_INDEX_AGAIN
Change number indexing will resume since replica '%s' is now sending messages again -
WARN_CHANGELOG_SERVER_UNKNOWN_HOST
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_CHANGELOG_SERVER_UNKNOWN_HOSTObject> Directory server DS(%s) was unable to connect to replication server at %s for domain '%s': unknown host -
INFO_REPLICA_COMPUTING_GENERATION_ID
public static LocalizableMessageDescriptor.Arg3<Object,Object, INFO_REPLICA_COMPUTING_GENERATION_IDNumber> Directory server DS(%s) did not find a generation ID for domain '%s'. A new generation ID will be computed by exporting the first %d entries in the domain -
WARN_CONNECTION_FROM_SAME_REPLICA
Replica '%s' for domain '%s' tried to connect but the replication server is still processing messages from the previous replication session and considers the replica already connected. The connection will be closed, the replica will connect again -
INFO_OTHER_MESSAGE
%s: received message <%s> -
NOTE_DS_NOTIFIED_STATE_IS_BAD_DATA_GEN_ID
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_DS_NOTIFIED_STATE_IS_BAD_DATA_GEN_IDObject> This replica `%s` has received a notification from its replication server `%s` to stop processing updates for domain `%s` as part of a disaster recovery procedure. This replica must be reinitialized as part of the recovery procedure -
ERR_CHANGELOG_BACKEND_CHANGE_NUMBER_INDEXER_NOT_ENABLED
public static LocalizableMessageDescriptor.Arg0 ERR_CHANGELOG_BACKEND_CHANGE_NUMBER_INDEXER_NOT_ENABLEDThe search cannot be processed because the external changelog is not configured to generate change numbers. Change the replication server configuration if change numbers are needed -
INFO_PURGE_DELAY_MODIFIED
The purge delay has been set to: %s -
INFO_PURGE_DELAY_SET_TO_ZERO
Purging is disabled (delay set to 0) -
ERR_SEARCHING_FRACTIONAL_CONFIGURATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SEARCHING_FRACTIONAL_CONFIGURATIONAn unexpected error occurred when loading the fractional replication configuration of domain "%s": %s -
WARN_IGNORING_UPDATE_FROM_DS_BAD_FRACTIONAL_CONFIG
public static LocalizableMessageDescriptor.Arg7<Object,Object, WARN_IGNORING_UPDATE_FROM_DS_BAD_FRACTIONAL_CONFIGObject, Object, Object, Object, Object> Replication server RS(%s) ignoring update %s for domain "%s" from directory server DS(%s) at %s because the peer DS reported to be in BAD_DATA status. The generation ID matches, (DS is %s, RS is %s), there may be a problem with fractional replication configuration. Check the DS error logs for more details -
WARN_IGNORING_UPDATE_TO_DS_BAD_FRACTIONAL_CONFIG
public static LocalizableMessageDescriptor.Arg7<Object,Object, WARN_IGNORING_UPDATE_TO_DS_BAD_FRACTIONAL_CONFIGObject, Object, Object, Object, Object> Replication server RS(%s) not sending update %s for domain "%s" to directory server DS(%s) at %s because the peer DS reported to be in BAD_DATA status. The generation ID matches, (DS is %s, RS is %s), there may be a problem with fractional replication configuration. Check the DS error logs for more details -
NOTE_JAVA_VERSION
JAVA Version: %s -
NOTE_JAVA_VENDOR
JAVA Vendor: %s -
NOTE_JVM_VERSION
JVM Version: %s -
NOTE_JVM_VENDOR
JVM Vendor: %s -
NOTE_JAVA_HOME
JAVA Home: %s -
NOTE_JAVA_CLASSPATH
Class Path: %s -
NOTE_CURRENT_DIRECTORY
Current Directory: %s -
NOTE_OPERATING_SYSTEM
Operating System: %s -
NOTE_JVM_ARCH
JVM Architecture: %s -
NOTE_SYSTEM_NAME
System Name: %s -
NOTE_AVAILABLE_PROCESSORS
Available Processors: %d -
NOTE_MAX_MEMORY
Max Available Memory: %d -
NOTE_TOTAL_MEMORY
Currently Used Memory: %d -
NOTE_FREE_MEMORY
Currently Free Memory: %d -
NOTE_JVM_INFO
JVM Information: %s by %s, %s architecture, %d bytes heap size -
NOTE_JVM_HOST
JVM Host: %s, running %s, %d bytes physical memory size, number of processors available %d -
NOTE_JVM_ARGS
JVM Arguments: %s -
NOTE_JVM_HOST_WITH_UNKNOWN_PHYSICAL_MEM
public static LocalizableMessageDescriptor.Arg3<Object,Object, NOTE_JVM_HOST_WITH_UNKNOWN_PHYSICAL_MEMNumber> JVM Host: %s, running %s, unknown physical memory size, number of processors available %d -
NOTE_INSTALL_DIRECTORY
Installation Directory: %s -
NOTE_UNKNOWN_INSTALL_DIRECTORY
Installation Directory: unknown -
NOTE_INSTANCE_DIRECTORY
Instance Directory: %s -
NOTE_UNKNOWN_INSTANCE_DIRECTORY
Instance Directory: unknown -
ERR_ATTR_SYNTAX_DN_END_WITH_COMMA
The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was a comma or semicolon -
ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_CHAR
public static LocalizableMessageDescriptor.Arg3<Object,Character, ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_CHARNumber> 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 -
ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_INITIAL_DASH
public static LocalizableMessageDescriptor.Arg1<Object> ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_INITIAL_DASHThe 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 -
ERR_ATTR_SYNTAX_DN_ATTR_NO_NAME
The provided value "%s" could not be parsed as a valid distinguished name because it contained an RDN containing an empty attribute name -
ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_PERIOD
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_PERIODThe 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 -
ERR_ATTR_SYNTAX_DN_END_WITH_ATTR_NAME
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_ATTR_SYNTAX_DN_END_WITH_ATTR_NAMEThe 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' -
ERR_ATTR_SYNTAX_DN_NO_EQUAL
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_ATTR_SYNTAX_DN_NO_EQUALCharacter> 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' -
ERR_ATTR_SYNTAX_DN_INVALID_CHAR
public static LocalizableMessageDescriptor.Arg3<Object,Character, ERR_ATTR_SYNTAX_DN_INVALID_CHARNumber> The provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not valid -
ERR_ATTR_SYNTAX_DN_HEX_VALUE_TOO_SHORT
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 -
ERR_ATTR_SYNTAX_DN_INVALID_HEX_DIGIT
public static LocalizableMessageDescriptor.Arg2<Object,Character> ERR_ATTR_SYNTAX_DN_INVALID_HEX_DIGITThe 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 -
ERR_ATTR_SYNTAX_DN_ATTR_VALUE_DECODE_FAILURE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_ATTR_SYNTAX_DN_ATTR_VALUE_DECODE_FAILUREThe 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" -
ERR_ATTR_SYNTAX_DN_UNMATCHED_QUOTE
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 -
ERR_ATTR_SYNTAX_DN_ESCAPED_HEX_VALUE_INVALID
public static LocalizableMessageDescriptor.Arg1<Object> ERR_ATTR_SYNTAX_DN_ESCAPED_HEX_VALUE_INVALIDThe 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 -
ERR_ATTR_SYNTAX_SUBTREE_SPECIFICATION_INVALID
public static LocalizableMessageDescriptor.Arg1<Object> ERR_ATTR_SYNTAX_SUBTREE_SPECIFICATION_INVALIDThe provided value "%s" could not be parsed as a valid subtree specification -
NOTE_SCHEMA_IMPORT_FAILED
A schema element could not be imported: %s, %s -
ERR_SCHEMA_HAS_WARNINGS
There should be no warnings on the schema, but instead got %d warnings: %s -
ERR_PARSING_OBJECTCLASS_OID
Unable to parse the OID from the provided definition of objectclass: '%s' -
ERR_PARSING_ATTRIBUTE_TYPE_OID
Unable to parse the OID from the provided definition of attribute type: '%s' -
ERR_PARSING_LDAP_SYNTAX_OID
Unable to parse the OID from the provided definition of ldap syntax: '%s' -
ERR_PARSING_MATCHING_RULE_USE_OID
Unable to parse the OID from the provided definition of matching rule use: '%s' -
ERR_PARSING_NAME_FORM_OID
Unable to parse the OID from the provided definition of name form: '%s' -
ERR_PARSING_DIT_CONTENT_RULE_OID
Unable to parse the OID from the provided definition of DIT content rule: '%s' -
ERR_PARSING_DIT_STRUCTURE_RULE_RULEID
Unable to parse the rule ID from the provided definition of DIT structure rule: '%s' -
ERR_SETUP_INSTANCE_ALREADY_CONFIGURED
There is already a server instance configured in the directory %s. Please make sure there is no configuration (config) or data (db) directory in the server instance root path -
INFO_SETUP_EVAL_PROFILE_COMBINED_WITH_NON_EVAL_PROFILE
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_EVAL_PROFILE_COMBINED_WITH_NON_EVAL_PROFILEYou have chosen to combine an evaluation profile with another profile that is intended for production. Applying an evaluation profile after others can compromise the security of your server. Review the server configuration carefully before deployment -
ERR_SETUP_INSTANCE_LOC_FILE_FOUND
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_SETUP_INSTANCE_LOC_FILE_FOUNDObject, Object> The file '%s' is referring to an invalid instance (%s). You must remove this file before setting up a new instance in the directory %s. Please use either the --%s option in non interactive mode or the interactive mode to setup an instance elsewhere -
ERR_SETUP_INSTANCE_INSTALLED_FROM_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_INSTANCE_INSTALLED_FROM_FILEA server instance (%s) has already been setup in the directory %s -
WARN_SETUP_REMOVING_FILES_AFTER_FAILURE
Setup has failed, see the errors in the messages below. The process also failed to automatically remove the files that it created during setup. Please manually remove the 'db' and 'config' directories from the instance directory before trying to run the setup again -
WARN_SETUP_REMOVING_FILES_AFTER_FAILURE_WITH_INSTANCE_LOC
public static LocalizableMessageDescriptor.Arg1<Object> WARN_SETUP_REMOVING_FILES_AFTER_FAILURE_WITH_INSTANCE_LOCSetup has failed, see the errors in the messages below. The process also failed to automatically remove the files that it created during setup. Please manually remove the 'db' and 'config' directories from the instance directory and the '%s' file before trying to run the setup again -
ERR_SETUP_INTERACTIVE_EMPTY_FILE_BASED_KEYSTORE_PWD
The file based keystore password cannot be empty -
ERR_SETUP_FILE_BASED_KEYSTORE_PASSWORD_IS_MISSING
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_FILE_BASED_KEYSTORE_PASSWORD_IS_MISSINGYou must specify the keystore password of the file based keystore. You can use either --%s or --%s options to specify it -
INFO_SETUP_DESCRIPTION_USE_JCE_KEYSTORE
Path of a JCEKS keystore containing the certificate(s) that the server should use when negotiating secure connections using StartTLS or SSL -
INFO_SETUP_DESCRIPTION_USE_JKS_KEYSTORE
Path of a JKS keystore containing the certificate(s) that the server should use when negotiating secure connections using StartTLS or SSL -
ERR_SETUP_INTERACTIVE_EMPTY_SERVER_PORT
You must specify a valid port number -
INFO_SETUP_INTERACTIVE_SUMMARIZE_TRUST_METHOD
Trust remote server certificates -
INFO_SETUP_INTERACTIVE_SUMMARIZE_PKCS12_TRUSTSTORE
Use existing PKCS#12 truststore -
INFO_SETUP_INTERACTIVE_SUMMARIZE_JCE_TRUSTSTORE
Use existing JCEKS truststore -
INFO_SETUP_INTERACTIVE_SUMMARIZE_JKS_TRUSTSTORE
Use existing JKS truststore -
INFO_SETUP_INTERACTIVE_SUMMARIZE_TRUSTSTORE_FILE
Truststore file -
INFO_SETUP_INTERACTIVE_SUMMARIZE_TRUSTSTORE_PWD
Truststore password -
INFO_SETUP_INTERACTIVE_PKCS12_TRUSTSTORE_PATH
PKCS#12 truststore path: -
INFO_SETUP_INTERACTIVE_JCE_TRUSTSTORE_PATH
JCEKS truststore path: -
INFO_SETUP_INTERACTIVE_JKS_TRUSTSTORE_PATH
JKS truststore path: -
INFO_SETUP_INTERACTIVE_TRUSTSTORE_PASSWORD
Truststore password (leave empty if the truststore has no password): -
INFO_SETUP_INTERACTIVE_TRUST_METHOD_PROMPT
How should the server trust certificates from SSL peers? -
INFO_SETUP_INTERACTIVE_USE_JVM_TRUSTSTORE
Use the JVM truststore -
INFO_SETUP_INTERACTIVE_USE_PKCS12_TRUSTSTORE
Use a PKCS#12 truststore -
INFO_SETUP_INTERACTIVE_USE_JCE_TRUSTSTORE
Use a JCEKS truststore -
INFO_SETUP_INTERACTIVE_USE_JKS_TRUSTSTORE
Use a JKS truststore -
INFO_SETUP_INTERACTIVE_USE_BLIND_TRUST
Blindly trust all certificates (evaluation only - unsafe for production) -
INFO_SETUP_INTERACTIVE_NO_PASSWORD_PROVIDED
No password provided -
INFO_SETUP_DESCRIPTION_USE_PKCS12_TRUSTSTORE
Use existing PKCS12 truststore file for validating peer SSL certificates -
INFO_SETUP_DESCRIPTION_USE_JCE_TRUSTSTORE
Use existing JCEKS truststore file for validating peer SSL certificates -
INFO_SETUP_DESCRIPTION_USE_JKS_TRUSTSTORE
Use existing JKS truststore file for validating peer SSL certificates -
INFO_SETUP_DESCRIPTION_TRUST_ALL
Blindly trust peer SSL certificates -
ERR_SETUP_PASSWORD_FILE_INVALID
The provided password file '%s' must be an existing readable file -
ERR_SETUP_PASSWORD_FILE_NO_PASSWORD
Unable to read password in file '%s'. A password file must contain a single line with the keystore password, details: %s -
ERR_SETUP_PASSWORD_FILE_MULTIPLE_LINES
Invalid content for password file '%s'. A password file must contain a single line with the password -
ERR_SETUP_PASSWORD_FILE_EMPTY_PASSWORD
password is empty -
ERR_SETUP_WRITING_PASSWORD_INTERNAL_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_WRITING_PASSWORD_INTERNAL_FILEAn error occurred while storing provided password in the instance file '%s', details: %s -
ERR_SETUP_ACCESSING_TRUSTSTORE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SETUP_ACCESSING_TRUSTSTOREObject> Could not access the %s truststore '%s'. Check that the content of the file corresponds to a valid truststore, that you have access rights to it and that a valid password has been provided if needed. Error details: %s -
ERR_SETUP_CLEARTEXT_PASSWORD_EMPTY
clear-text password cannot be empty -
ERR_SETUP_CREATING_FILE_BASED_TRUST_MANAGER_PROVIDER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_CREATING_FILE_BASED_TRUST_MANAGER_PROVIDERAn error occurred while creating the file based trust manager provider: %s -
ERR_SETUP_ENABLING_TRUST_MANAGER_PROVIDER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_ENABLING_TRUST_MANAGER_PROVIDERAn error occurred while enabling the %s trust manager provider: %s -
ERR_SETUP_FILE_TRUSTSTORE
The provided truststore file '%s' must be an existing readable file -
ERR_SETUP_CANNOT_CREATE_PKCS11_KEYMANAGER
An error occurred while creating the PKCS#11 key manager provider: %s -
ERR_SETUP_ACCESSING_KEYSTORE_ENTRIES
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SETUP_ACCESSING_KEYSTORE_ENTRIESObject> Could not read the %s keystore '%s' entries. Check that the content of the file corresponds to a valid keystore, that you have access rights to it and that a valid password has been provided if needed. Error details: %s -
ERR_SETUP_ACCESSING_PKCS11_KEYSTORE
Could not access the PKCS#11 keystore. Check that the JVM security settings have been configured to use a PKCS#11 keystore and that a valid password has been provided if needed. Error details: %s -
ERR_SETUP_NO_PRIVATE_KEY_IN_KEYSTORE
No private key entry found in keystore '%s'. Keystores used for securing client connections must contain at least one private key entry. Beware: you may need to provide the keystore password to access keystore private entries -
INFO_SETUP_INTERACTIVE_HOST_NAME
Provide the server's fully qualified host name -
INFO_SETUP_INTERACTIVE_HOME_SCREEN
Welcome to the OpenDJ %s interactive setup.%n%nInteractive mode helps you quickly set up an OpenDJ server.%nProvide all required options to set up the server in non-interactive mode,%nor use the command shown at the end of your interactive session -
ERR_SETUP_INTERACTIVE_LICENSE_NOT_ACCEPTED
License not accepted, %s will exit -
ERR_SETUP_INTERACTIVE_KEYSTORE_FILE_EMPTY
Invalid input: keystore path cannot be empty -
ERR_SETUP_INTERACTIVE_NO_ALIAS_SELECTED
Invalid configuration: you must use at least one certificate nickname -
INFO_SETUP_INTERACTIVE_MULTI_ALIASES_KEYSTORE
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_MULTI_ALIASES_KEYSTOREThe keystore contains the following certificate nicknames: %s.%nYou will be prompted for the nickname(s) to use -
ERR_SETUP_NB_SAMPLE_DATA_NEGATIVE
The number of entries to import must be a positive integer -
ERR_INTERACTIVE_INVALID_INT
Value '%s' must be a valid number -
ERR_INTERACTIVE_INVALID_VERSION
Value '%s' must be a valid version (two or three digits separated with a dot) -
ERR_INTERACTIVE_VERSION_TOO_OLD
Please select at least version %s -
INFO_SETUP_INTERACTIVE_ENABLE_PORT
Listening on port %d -
INFO_SETUP_INTERACTIVE_PROFILES_GROUP
Customize Server With Profiles -
INFO_SETUP_INTERACTIVE_SUMMARIZE_CERTIFICATE
Server security -
INFO_SETUP_INTERACTIVE_SUMMARIZE_KEYSTORE_FILE
Keystore file -
INFO_SETUP_INTERACTIVE_SUMMARIZE_PKCS11_KEYSTORE
Use existing PKCS#11 keystore -
INFO_SETUP_INTERACTIVE_SUMMARIZE_PKCS12_KEYSTORE
Use existing PKCS#12 keystore -
INFO_SETUP_INTERACTIVE_SUMMARIZE_JCE_KEYSTORE
Use existing JCEKS keystore -
INFO_SETUP_INTERACTIVE_SUMMARIZE_JKS_KEYSTORE
Use existing JKS keystore -
INFO_SETUP_INTERACTIVE_SUMMARIZE_KEYSTORE_PWD
Keystore password -
INFO_SETUP_INTERACTIVE_SUMMARIZE_CERT_NICKNAMES
Certificate nickname(s) to use -
INFO_SETUP_INTERACTIVE_SUMMARY_LDAP
LDAP (cleartext) -
INFO_SETUP_INTERACTIVE_SUMMARY_LDAPS
LDAPS (secure) -
INFO_SETUP_INTERACTIVE_SUMMARY_HTTP
HTTP (cleartext) -
INFO_SETUP_INTERACTIVE_SUMMARY_HTTPS
HTTPS (secure) -
INFO_SETUP_INTERACTIVE_DEPLOYMENT_SECURITY
How would you like to secure your deployment? -
INFO_SETUP_INTERACTIVE_DEPLOYMENT_SECURITY_EXISTING_CERTS
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_INTERACTIVE_DEPLOYMENT_SECURITY_EXISTING_CERTSYou already have a CA certificate for the deployment and an SSL key-pair for this server -
INFO_SETUP_INTERACTIVE_KEYPAIR_PROMPT
Provide the SSL certificate that will be used for securing server connections: -
INFO_SETUP_INTERACTIVE_DEPLOYMENT_SECURITY_KEY
Generate a CA certificate and SSL key-pair using the deployment ID (easier to deploy, but not suitable for public facing services) -
INFO_SETUP_INTERACTIVE_EXISTING_DEPLOYMENT_ID
Provide the deployment ID: -
INFO_SETUP_INTERACTIVE_SUMMARY_INSTANCE_PATH
Server instance path -
INFO_SETUP_INTERACTIVE_PROMPT_INSTANCE_PATH
Provide the server instance path -
INFO_SETUP_INTERACTIVE_PROMPT_ROOT_USER_DN
Provide the directory root user DN -
INFO_SETUP_INTERACTIVE_PROMPT_ROOT_USER_PASSWORD
Provide the password for root user (leave empty to use the deployment ID password): -
INFO_SETUP_INTERACTIVE_CONFIRM_PROMPT_ROOT_USER_PASSWORD
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_INTERACTIVE_CONFIRM_PROMPT_ROOT_USER_PASSWORDConfirm the password for root user: -
INFO_SETUP_INTERACTIVE_ENABLE_HTTP
Enable HTTP? -
INFO_SETUP_INTERACTIVE_HTTP_PORT
HTTP port -
INFO_SETUP_INTERACTIVE_ENABLE_HTTPS
Enable HTTPS? -
INFO_SETUP_INTERACTIVE_HTTPS_PORT
HTTPS port -
INFO_SETUP_INTERACTIVE_SUMMARY_START_SERVER
Start server after setup -
INFO_SETUP_INTERACTIVE_SUMMARY_WINDOWS_SERVICE
Run as Windows service -
INFO_SETUP_INTERACTIVE_SUMMARY_HOSTNAME
Server's fully qualified host name -
INFO_SETUP_INTERACTIVE_SUMMARY_PWD
Root user password -
INFO_SETUP_INTERACTIVE_ENABLE_LDAP
Enable LDAP? -
INFO_SETUP_INTERACTIVE_LDAP_PORT
LDAP port -
INFO_SETUP_INTERACTIVE_ENABLE_LDAPS
Enable LDAPS? -
INFO_SETUP_INTERACTIVE_LDAPS_PORT
LDAPS port -
INFO_SETUP_INTERACTIVE_ADMIN_CONNECTOR_PORT
Administration connector port -
INFO_SETUP_INTERACTIVE_PROMPT_START_SERVER
Start the server when setup is complete? Note: starting with version 7.0, it is advised to only start the server once it is customized for the intended deployment. If more configuration is needed, then select 'no' -
INFO_SETUP_INTERACTIVE_GLOBAL_PARAMETERS_GROUP
Global Parameters -
INFO_SETUP_INTERACTIVE_NETWORK_PARAMETERS_GROUP
Network Parameters -
INFO_SETUP_INTERACTIVE_ALL_PARAMETERS
All Server Parameters -
INFO_SETUP_INTERACTIVE_RUN_SETUP_OPTION
Set up the server with the specified settings -
INFO_SETUP_INTERACTIVE_START_OVER_OPTION
Start over -
INFO_SETUP_INTERACTIVE_QUIT_OPTION
Quit -
INFO_SETUP_INTERACTIVE_EQUIVALENT_COMMAND_LINE
Equivalent non-interactive command: -
INFO_SETUP_CONFIRM_GROUP_DATA
Accept these choices and continue? -
ERR_SETUP_ENCODING_PASSWORD
Unable to encode provided password because '%s' -
ERR_SETUP_BLANK_HOST_NAME
The fully qualified host name must be a non blank string -
ERR_SETUP_UNABLE_TO_READ_KEYSTORE_FILE
The provided keystore file '%s' must be an existing readable file -
INFO_EXTERNAL_PROCESS_START
Launch external process: '%s' -
ERR_EXTERNAL_PROCESS_STDERR
External process contains errors: %s -
INFO_EXTERNAL_PROCESS_STDOUT
External process standard output: %s -
ERR_EXTERNAL_PROCESS_INTERRUPTED
External process has been interrupted: '%s' -
ERR_SETUP_DISPLAY_LICENSE_FILE
Unable to display license because '%s' -
ERR_SETUP_ENABLING_WINDOWS_SERVICE
Unable to enable windows service (return code '%d'): %s -
INFO_SETUP_ENABLING_WINDOWS_SERVICE_OUTPUT
public static LocalizableMessageDescriptor.Arg2<Number,Object> INFO_SETUP_ENABLING_WINDOWS_SERVICE_OUTPUTEnable windows service command (return code '%d') output: %s -
ERR_SETUP_CREATING_INSTANCE_DIRECTORY
Unable to create server instance directory '%s' -
ERR_SETUP_INSTANCE_PARENT_PATH_NOT_VALID_DIRECTORY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_INSTANCE_PARENT_PATH_NOT_VALID_DIRECTORYThe instance parent (%s) must be a valid existing directory -
ERR_SETUP_INSTANCE_PATH_MUST_BE_A_DIRECTORY
The instance path must be a directory -
ERR_SETUP_UNABLE_TO_READ_INSTANCE_PATH
An error occurred while trying to read instance.loc file: %s -
ERR_SETUP_CREATE_INSTANCE_LOC_FILE
An error occurred while trying to write instance.loc file: %s -
ERR_SETUP_KEYSTORE_PASSWORD_WITHOUT_KEYSTORE
You cannot provide a keystore password without providing an existing keystore -
ERR_SETUP_CERT_NICK_NAMES_WITHOUT_KEYSTORE
You cannot specify certificate aliases without providing an existing keystore -
ERR_SETUP_TRUSTSTORE_WITHOUT_KEYSTORE
You cannot specify truststore without providing an existing keystore -
ERR_SETUP_ENABLING_HTTP_ACCESS_LOGGER
Unable to enable the file based HTTP access logger because: %s -
ERR_SETUP_CONFIGURING_PASSWORD
An error occurred while writing password in configuration file: '%s' -
ERR_SETUP_UPDATING_HTTP_PORT
An error occurred while attempting to update the HTTP connector port: '%s' -
ERR_SETUP_UPDATING_HTTPS_PORT
An error occurred while attempting to update the HTTPS connector: '%s' -
ERR_SETUP_CANNOT_UPDATE_LDAP_PORT
An error occurred while attempting to update the port on which to listen for LDAP communication: %s -
ERR_SETUP_MANAGEMENT_CONTEXT_FROM_CONFIG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_MANAGEMENT_CONTEXT_FROM_CONFIGUnable to write configuration file '%s' (%s) -
ERR_SETUP_ADD_UPGRADE_VERSION_IN_CONFIG
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_ADD_UPGRADE_VERSION_IN_CONFIGUnable to write the upgrade version in '%s' file (%s) -
ERR_SETUP_DATA_VERSION_FROM_CONFIG_VERSION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_DATA_VERSION_FROM_CONFIG_VERSIONUnable to parse the version in '%s' file in order to initialize the content of the '%s' file -
ERR_SETUP_UNABLE_TO_WRITE_FILE
Unable to write file '%s' because: '%s' -
ERR_SETUP_UNABLE_TO_EDIT_JAVA_HOME
Unable to edit runtime settings file because '%s' -
ERR_SETUP_COPY_FILE
An error occurred while copying file '%s' into '%s': '%s' -
ERR_SETUP_CREATE_DIR
An error occurred while creating directory '%s' -
ERR_SETUP_COPY_FILE_CHANGE_RIGHTS
Unable to set access permissions to allow write operations on file '%s'. Ensure that you have enough rights to change the access permissions on instance files -
INFO_SETUP_CONFIGURE_SERVER
Configuring server -
INFO_SETUP_VALIDATE_INPUTS_START
Validating parameters -
ERR_SETUP_ENABLE_WINDOWS_SERVICE
The server can only be enabled as a windows service on a Windows operating system -
INFO_SETUP_HTTP_PORT_DESCRIPTION
Port on which the server should listen for HTTP communication -
INFO_SETUP_HTTPS_PORT_DESCRIPTION
Port on which the server should listen for HTTPS communication -
INFO_DESCRIPTION_INSTANCE_PATH
Path were the instance should be set up -
DOC_DEFAULT_INSTANCE_PATH
/path/to/opendj -
ERR_SETUP_CERTNICKNAME_NOT_FOUND
The provided certificate nickname '%s' could not be found. The keystore contains the following certificate nicknames: %s -
ERR_SETUP_MUST_PROVIDE_CERTNICKNAME
The keystore contains the following certificate nicknames: %s.%nYou have to provide the nickname of the certificate you want to use -
ERR_SETUP_ACCESSING_KEYSTORE
Could not access the %s keystore '%s'. Check that the content of the file corresponds to a valid keystore, that you have access rights to it and that a valid password has been provided if needed. Error details: %s -
ERR_SETUP_LICENSE_NOT_ACCEPTED_NON_INTERACTIVE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_LICENSE_NOT_ACCEPTED_NON_INTERACTIVEYou must accept the product license to run setup. Either use interactive mode or the '--%s' option -
ERR_SETUP_INVALID_INSTALL_PATH
The provided server install path '%s' must reference an existing directory -
ERR_SETUP_UNEXPECTED
An unexpected error has been raised during setup: '%s' -
ERR_SETUP_INVALID_ADMIN_PORT
Administration connector port '%d' is not in allowed range %d, %d -
ERR_SETUP_INVALID_LDAP_PORT
LDAP port '%d' is not in allowed range %d, %d -
ERR_SETUP_INVALID_LDAPS_PORT
LDAPS port '%d' is not in allowed range %d, %d -
ERR_SETUP_INVALID_HTTP_PORT
HTTP port '%d' is not in allowed range %d, %d -
ERR_SETUP_INVALID_HTTPS_PORT
HTTPS port '%d' is not in allowed range %d, %d -
ERR_SETUP_INVALID_REPLICATION_PORT
public static LocalizableMessageDescriptor.Arg3<Number,Number, ERR_SETUP_INVALID_REPLICATION_PORTNumber> Replication port '%d' is not in allowed range %d, %d -
ERR_SETUP_INVALID_PORT
Port '%d' is not in allowed range %d, %d -
ERR_SETUP_PORT_ALREADY_SPECIFIED
Value '%d' has been specified for different ports -
ERR_SETUP_ROOT_USER_INVALID_DN
The administrator user bind DN '%s' is invalid. %s -
ERR_SETUP_ROOT_USER_EMPTY_DN
The root user DN cannot be empty -
ERR_SETUP_MONITOR_USER_EMPTY_DN
DN for the monitor user cannot be empty -
ERR_SETUP_MONITOR_USER_INVALID_DN
Monitor user DN value '%s' is invalid because: %s -
SETUP_MAIN_COMMAND_DESCRIPTION
This utility sets up an OpenDJ server. Use the %s option to list available profiles -
INFO_PROGRESS_DONE
Done -
INFO_PROGRESS_ENABLING_WINDOWS_SERVICE
Enabling Windows service -
INFO_PROGRESS_ERROR
Error -
INFO_PROGRESS_POINTS
..... -
INFO_PROGRESS_STARTING_NON_VERBOSE
Starting directory server -
INFO_PROGRESS_UPDATING_CERTIFICATES
Configuring certificates -
INFO_ERROR_CREATING_TEMP_FILE
An error occurred creating the temporary file -
INFO_ERROR_ENABLING_WINDOWS_SERVICE
Error Enabling Windows service -
INFO_ERROR_STARTING_SERVER
Error Starting Directory Server -
INFO_ERROR_STARTING_SERVER_CODE
Error Starting Directory Server. Error code: %s -
INFO_GENERAL_PROVIDE_LOG_IN_ERROR
See %s for a detailed log of the failed operation.%nPlease report this error and provide the log file mentioned above -
INFO_ERROR_CONFIGURING_CERTIFICATE
An error occurred while configuring the certificates: %s -
INFO_ADMIN_CONNECTOR_PORT_LABEL
Administration connector port -
INFO_LICENSE_DETAILS_CLI_LABEL
Please read the License Agreement above.%nYou must accept the terms of the agreement before continuing with the installation -
INFO_SERVER_DIRECTORY_MANAGER_DN_LABEL
Root user DN -
ERR_SETUP_CLI_TRUSTSTORE_PASSWORD_WITHOUT_FILE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_CLI_TRUSTSTORE_PASSWORD_WITHOUT_FILEThe --%s option should only be provided when using a file based trust store option -
INFO_SETUP_INTERACTIVE_PROMPT_MONITOR_USER_DN
Provide the DN for the default monitor user -
INFO_SETUP_INTERACTIVE_PROMPT_MONITOR_USER_PASSWORD
Provide the password for the default monitor user: -
INFO_SETUP_INTERACTIVE_CONFIRM_PROMPT_MONITOR_USER_PASSWORD
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_INTERACTIVE_CONFIRM_PROMPT_MONITOR_USER_PASSWORDConfirm the password for the default monitor user: -
INFO_ASK_TO_ENABLE_MONITOR_USER
Define and enable a default user for querying monitoring information? -
INFO_SERVER_MONITOR_USER_DN_LABEL
Monitor user -
INFO_SERVER_MONITOR_USER_PASSWORD_LABEL
Monitor user password -
INFO_MONITOR_USER_DN_PLACEHOLDER
{monitorUserDn} -
INFO_MONITOR_USER_PWD_PLACEHOLDER
{monitorUserPassword} -
INFO_SETUP_DESCRIPTION_MONITOR_USER_DN
DN of the default user allowed to query monitoring information -
INFO_SETUP_DESCRIPTION_MONITOR_USER_PASSWORD
Password of the default user allowed to query monitoring information -
ERR_SPECIFIED_A_MONITOR_USER_WITHOUT_PASSWORD
When specifying a default user for monitoring a password should also be provided -
ERR_CONFIGDS_CANNOT_CREATE_MONITOR_USER
An error occurred while attempting to write the monitor user entry: %s -
ERR_CONFIGDS_CANNOT_CREATE_MONITOR_USER_BACKEND
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CONFIGDS_CANNOT_CREATE_MONITOR_USER_BACKENDAn error occurred while attempting to configure the backend for the monitor user: %s -
ERR_SETUP_PROFILE_INVALID_FOLDER
Folder '%s' of the setup profile '%s' must be a readable existing folder -
ERR_SETUP_PROFILE_INVALID_VERSION_FOLDER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_PROFILE_INVALID_VERSION_FOLDERLast folder of profile '%s' path '%s' must be the profile version (two or three digits separated by either dot or hyphen, e.g /path/to/profile/6.5.0) -
ERR_SETUP_PROFILE_MISSING_MANDATORY_SCRIPT_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_PROFILE_MISSING_MANDATORY_SCRIPT_FILEFolder of the setup profile '%s' must contain a '%s' readable regular file -
ERR_SETUP_PROFILE_INVALID_PARAMETERS_SCRIPT_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_PROFILE_INVALID_PARAMETERS_SCRIPT_FILEFile '%s' from the setup profile '%s' must be a readable regular file -
INFO_SETUP_RUN_PROFILE
Configuring profile %s -
ERR_SETUP_PROFILE_SCRIPT_EXECUTION
The '%s' setup profile failed: %s -
INFO_SETUP_PROFILE_PLACEHOLDER
{name[:version]} -
INFO_SETUP_DESCRIPTION_PROFILE
Setup profile to apply when initially configuring the server. If the version is not specified, the most recent version older or equal to this OpenDJ version is used. Use this option multiple times to apply multiple profiles. This option cannot be combined with data import options. %s -
INFO_SETUP_DESCRIPTION_NO_PROFILES_AVAILABLE
There are no setup profiles available for this OpenDJ version -
INFO_SETUP_DESCRIPTION_AVAILABLE_PROFILES
Available setup profiles: %s -
INFO_SETUP_PROFILE_PARAMETER_PLACEHOLDER
{[profileName/]parameterName:value} -
INFO_SETUP_DESCRIPTION_PROFILE_PARAMETER
Assign a value to a setup profile parameter. Profile name must be provided if multiple profiles are provided, indicate the profile that a parameter applies to by using the profileName/parameterName format -
INFO_SETUP_DESCRIPTION_HELP_PROFILES
Display all available profiles -
INFO_SETUP_DESCRIPTION_HELP_PROFILE_PARAMETERS
Display profile parameters -
INFO_HELP_SETUP_ALL_PROFILES_HEADER
Profiles available with this OpenDJ version are: -
INFO_HELP_SETUP_ALL_PROFILES_FOOTER
Use %s %s to list profile parameters -
ERROR_SETUP_PROFILE_PARAMETER_UNUSED
Parameter(s) '%s' provided for profile '%s' is (are) not used in the profile -
ERROR_SETUP_PROFILE_PARAMETER_WITHOUT_PROFILE
public static LocalizableMessageDescriptor.Arg1<Object> ERROR_SETUP_PROFILE_PARAMETER_WITHOUT_PROFILEParameter '%s' is provided without any profile specification which is not allowed when multiple profiles are used -
ERR_SETUP_DS_PROFILE_MISSING_PARAMETER_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_DS_PROFILE_MISSING_PARAMETER_VALUEThe parameter '%s' is required by profile '%s', but no value has been provided -
ERR_SETUP_DS_PROFILE_CONF_METHOD_NOT_FOUND
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SETUP_DS_PROFILE_CONF_METHOD_NOT_FOUNDObject> Error in profile '%s': the default value for parameter '%s' cannot be derived from the SetupConfiguration method '%s' because no such method exists -
ERR_SETUP_DS_PROFILE_CONF_METHOD_CALLED
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_SETUP_DS_PROFILE_CONF_METHOD_CALLEDObject, Object> Error in profile '%s': the default value for parameter '%s' cannot be derived from the SetupConfiguration method '%s' because the method invocation threw an error: %s -
ERR_SETUP_DS_INVALID_PROFILE_PARAMETER_VALUE_FORMAT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_DS_INVALID_PROFILE_PARAMETER_VALUE_FORMATInvalid profile parameter value '%s'. Supported format is '%s' -
ERR_SETUP_DS_MISSING_PROFILE_NAME
Option to setup profile parameters have been provided but not the profile name. If you want to use a setup profile, please provide its name with the '%s' option -
ERR_SETUP_DS_PROFILE_NOT_FOUND
Setup profile '%s' cannot be found. %s -
ERR_SETUP_DS_PROFILE_SAME_PROFILE_MULTIPLE_VERSIONS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_DS_PROFILE_SAME_PROFILE_MULTIPLE_VERSIONSProfile '%s' has been specified multiple times. It is not possible to configure the server for multiple versions of the same profile. Please choose one version for this profile -
ERR_SETUP_DS_PROFILE_SAME_PARAMETER_MULTIPLE_VALUES
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_DS_PROFILE_SAME_PARAMETER_MULTIPLE_VALUESSetup profile parameter '%s' has been provided multiple times with different values. Please either choose one value or prefix the option values with a profile name -
ERR_SETUP_DS_PROFILE_PARAMETER_WITH_PROFILE_NOT_PROVIDED
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SETUP_DS_PROFILE_PARAMETER_WITH_PROFILE_NOT_PROVIDEDObject> Setup profile parameter '%s' references the profile '%s' which has not been provided on the command line. Setup profiles can be added on the command line with the '%s' option -
ERR_SETUP_PROFILE_RESOURCE_FILE
Unable to read template file '%s'. Please ensure that the file exists and that you have appropriate permissions to read the file -
ERR_SETUP_PROFILE_FILE_NOT_FOUND
Unable to read file '%s'. Please ensure that the file exists and that you have appropriate permissions to read the file -
WARN_SETUP_DELETE_DIRECTORY
An error occurred while attempting to remove content of directory '%s': %s -
ERR_SETUP_PROFILE_RESOURCE_SUBSTITUTION
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SETUP_PROFILE_RESOURCE_SUBSTITUTIONObject> An error occurred while substituting properties from profile '%s' resource file '%s': %s -
ERR_SETUP_PROFILE_IMPORT_IO
An IO error occurred while running profile '%s': '%s' -
ERR_SETUP_PROFILE_ADD_BACKEND
Unable to create '%s' backend (%s) -
ERR_SETUP_PROFILE_CREATE_REPLICATION_DOMAIN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_PROFILE_CREATE_REPLICATION_DOMAINUnable to create replication domain for base DN '%s' (%s) -
ERR_SETUP_PROFILE_NO_BACKEND
No backend has been created in the profile -
ERR_SETUP_PROFILE_LOG_IMPORT_LDIF
public static LocalizableMessageDescriptor.Arg6<Object,Object, ERR_SETUP_PROFILE_LOG_IMPORT_LDIFObject, Object, Object, Object> '%s' setup profile failed to import data contained in '%s' file(s) into '%s' backend. Import LDIF tool options: '%s'. Exception message:'%s'. Tool output: %s -
ERR_SETUP_PROFILE_IMPORT_LDIF
Unable to import data -
ERR_SETUP_PROFILE_IMPORT_LDIF_WITH_DETAILS
Unable to import data (%s) -
ERR_SETUP_PROFILE_IMPORT_SAMPLE_ENTRIES_WITH_DETAILS
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_PROFILE_IMPORT_SAMPLE_ENTRIES_WITH_DETAILSUnable to import generated users (%s) -
ERR_SETUP_PROFILE_IMPORT_LDIF_REJECTED_ENTRIES
Unable to import data because some entries have been rejected -
ERR_SETUP_PROFILE_IMPORT_LDIF_SKIPPED_ENTRIES
Unable to import data because some entries have been skipped -
ERR_SETUP_PROFILE_LOG_IMPORT_REJECTED_ENTRIES
public static LocalizableMessageDescriptor.Arg6<Object,Object, ERR_SETUP_PROFILE_LOG_IMPORT_REJECTED_ENTRIESObject, Object, Object, Object> '%s' setup profile failed to import data contained in '%s' file(s) into '%s' backend because of rejected entries (listed in '%s'). Import LDIF tool options: '%s'. Tool output: %s -
ERR_SETUP_PROFILE_LOG_IMPORT_SKIPPED_ENTRIES
public static LocalizableMessageDescriptor.Arg6<Object,Object, ERR_SETUP_PROFILE_LOG_IMPORT_SKIPPED_ENTRIESObject, Object, Object, Object> '%s' setup profile failed to import data contained in '%s' file(s) into '%s' backend because of skipped entries (listed in '%s'). Import LDIF tool options: '%s'. Tool output: %s -
ERR_SETUP_PROFILE_DSCONFIG
Unable to update server configuration -
ERR_SETUP_PROFILE_LOG_DSCONFIG
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_SETUP_PROFILE_LOG_DSCONFIGObject, Object> '%s' setup profile failed to update server configuration file, dsconfig tool options: '%s'. Exception message:'%s'. Tool output: %s -
ERR_SETUP_PROFILE_ADD_INDEX
Unable to add index for attribute '%s' (%s) -
INFO_SETUP_INTERACTIVE_PROFILES_PROMPT_HEADER
Available profiles: -
INFO_SETUP_INTERACTIVE_PROFILES_PROMPT
Enter profile number(s) separated by comma (leave empty to skip this step): -
INFO_SETUP_INTERACTIVE_PROFILES_PROMPT_WITH_DEFAULT
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_PROFILES_PROMPT_WITH_DEFAULTEnter profile number(s) separated by comma [%s]: -
INFO_SETUP_INTERACTIVE_SUMMARIZE_DO_NOT_CONFIGURE_DS
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_INTERACTIVE_SUMMARIZE_DO_NOT_CONFIGURE_DSNo profiles configured or data to be imported -
INFO_SETUP_INTERACTIVE_PROFILE_CONFIRM_THE
Confirm the %s: -
INFO_SETUP_INTERACTIVE_PROFILE_PARAMETER_GENERIC_PROMPT
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_PROFILE_PARAMETER_GENERIC_PROMPTProvide a value for '%s' -
INFO_SETUP_INTERACTIVE_PROFILE_PARAMETER_GENERIC_DESC
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_PROFILE_PARAMETER_GENERIC_DESCValue set for '%s' -
INFO_SETUP_INTERACTIVE_CONFIGURE_PROFILE
Configure server for profile '%s' -
INFO_SETUP_INTERACTIVE_SUMMARIZE_PROFILE_VERSION
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_SETUP_INTERACTIVE_SUMMARIZE_PROFILE_VERSIONConfigure server for profile '%s (%s)' -
ERR_SETUP_INTERACTIVE_PROFILE_PARAMETER_INVALID
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_INTERACTIVE_PROFILE_PARAMETER_INVALIDPlease provide a value having the following syntax: %s -
ERR_SETUP_DS_INVALID_PROFILE_PARAM_VALUE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_SETUP_DS_INVALID_PROFILE_PARAM_VALUEObject, Object> The value '%s' for parameter '%s' in profile '%s' is invalid. Please provide a value having the following syntax: %s -
ERR_SETUP_PROFILE_INVALID_ENUM_PARAMETER_VALUE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_SETUP_PROFILE_INVALID_ENUM_PARAMETER_VALUEObject, Object> The value '%s' for parameter '%s' in profile '%s' is invalid because it does not match any allowed values (%s) -
ERR_SETUP_PROFILE_INVALID_PWD_PARAMETER_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SETUP_PROFILE_INVALID_PWD_PARAMETER_VALUEObject> The value for password parameter '%s' of profile '%s' is invalid (%s) -
ERR_SETUP_PROFILE_ENCODE_PWD_PARAMETER_VALUE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_SETUP_PROFILE_ENCODE_PWD_PARAMETER_VALUEObject> Unable to encode password associated to parameter '%s' of profile '%s' (%s) -
ERR_SETUP_PROFILE_PARAMETER_BLANK_DOMAIN_VALUE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_PROFILE_PARAMETER_BLANK_DOMAIN_VALUEThe value for domain parameter '%s' of profile '%s' cannot be blank -
ERR_SETUP_PROFILE_INVALID_DOMAIN_PARAMETER_VALUE
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_SETUP_PROFILE_INVALID_DOMAIN_PARAMETER_VALUEObject, Object> The value '%s' for domain parameter '%s' of profile '%s' is invalid (%s) -
ERR_SETUP_PROFILE_EMPTY_DN_PARAMETER
The value for DN parameter '%s' of profile '%s' cannot be empty -
WARN_PROFILE_PARAMETER_HELP_PROFILE_VERSION_NOT_FOUND
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_PROFILE_PARAMETER_HELP_PROFILE_VERSION_NOT_FOUNDVersion %s not found, best match is %s -
INFO_PROFILE_PARAMETER_NO_PARAMETERS
Profile '%s (%s)' does not have any parameters -
INFO_PROFILE_PARAMETER_HELP_HEADER
%s (%s) parameters -
INFO_PROFILE_PARAMETER_HELP_PARAMETER_VARIABLE_NAME
Parameter: -
INFO_SETUP_PROFILE_PARAMETER_SYNTAX
Syntax: -
INFO_SETUP_PROFILE_PARAMETER_SYNTAX_EXPRESSION_ALLOWED
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_PROFILE_PARAMETER_SYNTAX_EXPRESSION_ALLOWED%s or configuration expression -
INFO_SETUP_PROFILE_STRING_PARAMETER_SYNTAX
String -
INFO_SETUP_PROFILE_NUMBER_PARAMETER_SYNTAX
Number -
INFO_SETUP_PROFILE_DECIMAL_NUMBER_PARAMETER_SYNTAX
Decimal number -
INFO_SETUP_PROFILE_PASSWORD_PARAMETER_SYNTAX
Password -
INFO_SETUP_PROFILE_DOMAIN_PARAMETER_SYNTAX
Domain name -
INFO_SETUP_PROFILE_FILE_PARAMETER_SYNTAX
File or directory path -
INFO_SETUP_PROFILE_ENUM_PARAMETER_SYNTAX
One of the following values: -
INFO_SETUP_PROFILE_HOST_PORT_PARAMETER_SYNTAX
host:port -
INFO_SETUP_PROFILE_DN_PARAMETER_SYNTAX
DN -
INFO_PROFILE_PARAMETER_HELP_DESCRIPTION
Description: -
INFO_PROFILE_PARAMETER_HELP_DEFAULT
Default: -
INFO_PROFILE_PARAMETER_HELP_DEFAULT_DERIVED_FROM_SETUP
public static LocalizableMessageDescriptor.Arg0 INFO_PROFILE_PARAMETER_HELP_DEFAULT_DERIVED_FROM_SETUPDerived from the setup global options -
ERR_SETUP_CONFIG_FRAMEWORK_INIT
Unable to bootstrap the Directory Server configuration because of the following error: %s -
ERR_SETUP_PROFILE_SEARCH_RESOURCE_IN_OTHER_VERSIONS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_PROFILE_SEARCH_RESOURCE_IN_OTHER_VERSIONSUnable to find resource '%s' of profile '%s' in profile version folders -
INFO_SETUP_INTERACTIVE_PROFILE_VERSION_PROMPT
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_SETUP_INTERACTIVE_PROFILE_VERSION_PROMPTWhich version of '%s' do you want to use (minimum %s)? -
INFO_SETUP_DESCRIPTION_SERVER_ID
Specify the server ID for this server. An acceptable ID is an ASCII alpha-numeric string; it may also contain underscore and hyphen characters provided they are not the first character -
INFO_SETUP_SERVER_ID_PLACEHOLDER
{serverId} -
INFO_SETUP_INTERACTIVE_PROMPT_SERVER_ID
Unique server ID (used for identifying the server in the topology) -
INFO_SERVER_ID_LABEL
Server ID -
ERR_SETUP_CANNOT_CONFIGURE_GLOBAL_CONFIG_PROPERTY
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_CANNOT_CONFIGURE_GLOBAL_CONFIG_PROPERTYAn error occurred while configuring the server ID or the advertised listen address in global configuration: %s -
ERR_SETUP_SERVER_ID_SYNTAX
Server ID '%s' is not valid. A Server ID is an ASCII alpha-numeric string possibly containing underscore and hyphen characters -
INFO_SETUP_INTERACTIVE_SET_OPTIONAL_PARAMETER_VALUE_DEFAULT_PROMPT
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_SET_OPTIONAL_PARAMETER_VALUE_DEFAULT_PROMPTDo you want to set a value for parameter '%s'? -
INFO_SETUP_INTERACTIVE_OPTIONAL_PARAMETER_NOT_SET_DEFAULT_DESCRIPTION
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_OPTIONAL_PARAMETER_NOT_SET_DEFAULT_DESCRIPTIONNo value specified for '%s' -
INFO_SETUP_INTERACTIVE_MULTIVALUED_PARAMETER_ADD_VALUE_DEFAULT_PROMPT
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_MULTIVALUED_PARAMETER_ADD_VALUE_DEFAULT_PROMPTDo you want to add another value for parameter '%s'? -
INFO_SETUP_INTERACTIVE_HOSTPORT_PARAMETER_HOSTNAME_DEFAULT_PROMPT
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_HOSTPORT_PARAMETER_HOSTNAME_DEFAULT_PROMPTProvide hostname for '%s' -
INFO_SETUP_INTERACTIVE_HOSTPORT_PARAMETER_PORT_DEFAULT_PROMPT
public static LocalizableMessageDescriptor.Arg1<Object> INFO_SETUP_INTERACTIVE_HOSTPORT_PARAMETER_PORT_DEFAULT_PROMPTProvide port for '%s' -
INFO_SETUP_PROFILE_CLI_USAGE_DESCRIPTION
This utility configures profiles in an offline OpenDJ server instance. %s -
INFO_SETUP_PROFILE_CLI_INSTANCE_PATH_DESCRIPTION
Path of the server instance where profiles should be setup -
INFO_SETUP_PROFILE_CLI_DESCRIPTION_PROFILE
Name of the profile to be configured. If the version is not specified, the most recent version older or equal to this OpenDJ version is used. Use this option multiple times to apply multiple profiles -
INFO_SETUP_PROFILE_CLI_SHORT_DESCRIPTION
configure profiles in an offline OpenDJ server instance -
ERR_SETUP_PROFILE_CLI_NO_PROFILE_PROVIDED
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_SETUP_PROFILE_CLI_NO_PROFILE_PROVIDEDYou must select at least one profile by using the option '%s'. %s -
ERR_SETUP_PROFILE_CLI_INSTANCE_PATH_NOT_VALID
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_PROFILE_CLI_INSTANCE_PATH_NOT_VALIDInstance path '%s' is not a valid existing directory -
ERR_SETUP_PROFILE_CLI_NO_DJ_IN_INSTANCE_PATH
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_PROFILE_CLI_NO_DJ_IN_INSTANCE_PATHInstance path '%s' does not contain an OpenDJ instance -
ERR_SETUP_PROFILE_CLI_INITIALIZE_CONFIG_FRAMEWORK
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_PROFILE_CLI_INITIALIZE_CONFIG_FRAMEWORKAn error occurred while initializing tool: %s -
ERR_SETUP_PROFILE_CLI_SERVER_ONLINE
Profiles can be setup only when the server is offline, please stop the server and retry -
ERR_READING_PROFILE_VERSION_FILE
An error occurred while reading file '%s': %s -
ERR_SETUP_PROFILE_CLI_PROFILE_ALREADY_SETUP
Unable to setup the profile '%s' because it is already configured in the server -
ERR_SETUP_PROFILE_CLI_PROFILES_ALREADY_SETUP
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_PROFILE_CLI_PROFILES_ALREADY_SETUPUnable to setup profiles '%s' because they are already configured in the server -
INFO_SETUP_DESCRIPTION_USE_DEPLOYMENT_ID
The deployment ID which should be used for securing the deployment. If no existing certificates are specified using the key-store and trust-store options then the deployment ID will also be used for securing all TLS network communication -
INFO_DEPLOYMENT_ID_PLACEHOLDER
{deploymentId} -
ERR_SETUP_DEPLOYMENT_ID_PROVIDER_NOT_FOUND
This deployment ID is using a key-pair generator which is not available in this Java environment. Retry the command with the Java environment that was used for generating this deployment ID -
ERR_SETUP_DEPLOYMENT_ID_ADD_KEYSTORE
Unable to add certificates derived from deployment ID in keystore: %s -
ERR_SETUP_REPLICATION_CONFIGURATION
An error occurred while configuring replication: %s -
INFO_SETUP_DESCRIPTION_DEPLOYMENT_ID_PASSWORD_ARG
Deployment ID password -
INFO_DEPLOYMENT_ID_PASSWORD_PLACEHOLDER
{deploymentIdPassword} -
INFO_SETUP_INTERACTIVE_PROMPT_DEPLOYMENT_ID_PASSWORD
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_INTERACTIVE_PROMPT_DEPLOYMENT_ID_PASSWORDProvide the deployment ID password: -
INFO_SETUP_INTERACTIVE_SUMMARY_USE_DEPLOYMENT_ID
Use deployment ID -
ERR_SETUP_CANNOT_UPDATE_ADMIN_CONNECTOR_PORT
public static LocalizableMessageDescriptor.Arg1<Object> ERR_SETUP_CANNOT_UPDATE_ADMIN_CONNECTOR_PORTAn error occurred while attempting to update the administration connector port: %s -
ERR_SETUP_CANNOT_UPDATE_CRYPTO_MANAGER
An error occurred while attempting to update the crypto manager in the Directory Server: %s -
ERR_SETUP_CANNOT_UPDATE_LDAPS_PORT
An error occurred while attempting to update the port on which to listen for LDAPS communication: %s -
ERR_SETUP_CANNOT_UPDATE_ROOT_USER
An error occurred while attempting to update the entry for the initial Directory Server root user: %s -
ERR_SETUP_CANNOT_BIND_TO_PORT
Unable to bind to port %d. This port may already be in use, or you may not have permission to bind to it -
ERR_SETUP_CANNOT_BIND_TO_PRIVILEGED_PORT
Unable to bind to port %d. This port may already be in use, or you may not have permission to bind to it. On UNIX-based operating systems, non-root users may not be allowed to bind to ports 1 through 1024 -
ERR_SETUP_CANNOT_WRITE_FILE
Unable to write a required file. Make sure that the %s tool has sufficient permissions to create and write the file: %s -
ERR_SETUP_NO_ROOT_PASSWORD
The root user password is missing, provide it with the --%s option -
INFO_SETUP_REF_SHORT_DESC
install OpenDJ server -
ERR_SETUP_INTERACTIVE_PASSWORDS_DONT_MATCH
The provided password values do not match -
INFO_SETUP_INTERACTIVE_CERT_OPTION_JCEKS
Use an existing certificate in a JCEKS keystore -
INFO_SETUP_INTERACTIVE_CERT_OPTION_JKS
Use an existing certificate in a JKS keystore -
INFO_SETUP_INTERACTIVE_CERT_OPTION_PKCS11
Use an existing certificate on a PKCS#11 token -
INFO_SETUP_INTERACTIVE_CERT_OPTION_PKCS12
Use an existing certificate in a PKCS#12 keystore -
INFO_SETUP_INTERACTIVE_CONFIRM_INSTALL_PROMPT
What would you like to do? -
INFO_SETUP_INTERACTIVE_PROMPT_CERTNICKNAME
Use nickname %s? -
INFO_SETUP_INTERACTIVE_PROMPT_ENABLE_SERVICE
Enable the server to run as a Windows Service? -
INFO_SETUP_INTERACTIVE_PROMPT_JCEKS_PATH
JCEKS keystore path: -
INFO_SETUP_INTERACTIVE_PROMPT_JKS_PATH
Java keystore (JKS) path: -
INFO_SETUP_INTERACTIVE_PROMPT_KEYSTORE_PASSWORD
Keystore password: -
INFO_SETUP_INTERACTIVE_PROMPT_PKCS12_PATH
PKCS#12 keystore path: -
ERR_SETUP_INTERACTIVE_NB_TRIES_LIMIT_REACHED
public static LocalizableMessageDescriptor.Arg1<Number> ERR_SETUP_INTERACTIVE_NB_TRIES_LIMIT_REACHEDInput tries limit reached (%d) -
ERR_RESOLVE_INSTALL_PATH
Unable to resolve the server installation root directory -
ERR_SETUP_CANNOT_ENABLE_KEYMANAGER
An error occurred while attempting to enable key manager provider entry: %s -
INFO_SETUP_STATUS_COMMAND_LINE
To see basic server status and configuration, you can launch %s -
INFO_SETUP_INTERACTIVE_DISABLED_LABEL
Disabled -
INFO_SETUP_INTERACTIVE_ENABLED_LABEL
Enabled -
INFO_SETUP_DESCRIPTION_ADMIN_CONNECTOR_PORT
Port on which the Administration Connector should listen for communication -
INFO_SETUP_DESCRIPTION_CERT_NICKNAME
Nickname of a keystore entry containing a certificate that the server should use when negotiating secure connections using StartTLS or SSL. Multiple keystore entries may be provided by using this option multiple times -
INFO_SETUP_DESCRIPTION_START
Start the server when the configuration is completed -
INFO_SETUP_DESCRIPTION_ENABLE_START_TLS
Enable StartTLS to allow secure communication with the server using the LDAP port -
INFO_SETUP_DESCRIPTION_ENABLE_WINDOWS_SERVICE
Enable the server to run as a Windows Service -
INFO_SETUP_DESCRIPTION_HOST_NAME
The fully-qualified directory server host name that will be used when generating certificates for LDAP SSL/StartTLS, the administration connector, and replication -
INFO_SETUP_DESCRIPTION_LDAP_PORT
Port on which the Directory Server should listen for LDAP communication -
INFO_SETUP_DESCRIPTION_LDAPS_PORT
Port on which the Directory Server should listen for LDAPS communication. The LDAPS port will be configured and SSL will be enabled only if this option is explicitly specified -
INFO_SETUP_DESCRIPTION_ROOT_USER_DN
DN for the initial root user for the Directory Server -
INFO_SETUP_DESCRIPTION_ROOT_USER_PASSWORD
Password for the initial root user for the Directory Server -
INFO_SETUP_DESCRIPTION_SKIP_PORT_CHECK
Skip the check to determine whether the specified ports are usable -
INFO_SETUP_DESCRIPTION_USE_PKCS11
Use certificate(s) in a PKCS#11 token that the server should use when accepting SSL-based connections or performing StartTLS negotiation -
INFO_SETUP_DESCRIPTION_USE_PKCS12
Path of a PKCS#12 keystore containing the certificate(s) that the server should use when negotiating secure connections using StartTLS or SSL -
INFO_SETUP_KEYSTORE_PWD_FILEPATH_PLACEHOLDER
{path} -
INFO_SETUP_DESCRIPTION_KEYSTORE_PASSWORD_FILE_PATH
Path of the file containing the keystore password. The specified path will be used as the configuration value in the new server -
INFO_SETUP_CERT_NICKNAME_PLACEHOLDER
{nickname} -
INFO_SETUP_ROOT_USER_DN_PLACEHOLDER
{rootUserDN} -
INFO_SETUP_ROOT_USER_PASSWORD_PLACEHOLDER
{rootUserPassword} -
INFO_SETUP_TRUSTSTORE_PASSWORD_FILEPATH_PLACEHOLDER
{path} -
INFO_SETUP_DESCRIPTION_TRUSTSTORE_PASSWORD_FILE_PATH
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_DESCRIPTION_TRUSTSTORE_PASSWORD_FILE_PATHPath of the file containing the truststore password. The specified path will be used as the configuration value in the new server -
ERR_SETUP_NO_DEPLOYMENT_ID_PASSWORD
The deployment ID password is missing, provide it with the --%s option -
INFO_SETUP_INTERACTIVE_SUMMARIZE_USE_DEPLOYMENT_ID_PASSWORD
public static LocalizableMessageDescriptor.Arg0 INFO_SETUP_INTERACTIVE_SUMMARIZE_USE_DEPLOYMENT_ID_PASSWORDSame as deployment ID password -
INFO_SETUP_DESCRIPTION_BOOTSTRAP_RS
The addresses of one or more replication servers within the topology which the server should connect to for discovering the rest of the topology. Use syntax "hostname:port" or "[IPv6Address]:port" for IPv6 addresses -
INFO_SETUP_BOOTSTRAP_RS_PLACEHOLDER
{bootstrapReplicationServer} -
INFO_SETUP_DESCRIPTION_REPLICATION_PORT
Port used for replication protocol communications with other servers. Use this option to configure a local replication server. When this option is not used, this server is configured as a standalone DS (no local replication server) -
INFO_SETUP_INTERACTIVE_REPLICATION_PORT
Replication port -
INFO_SETUP_INTERACTIVE_SUMMARY_REPLICATION
Replication (secure) -
INFO_SETUP_INTERACTIVE_BOOTSTRAP_RS_INTRO
What are the hostname and port number of the server to replicate with? (e.g ds.example.com on port 8989) -
INFO_SETUP_INTERACTIVE_BOOTSTRAP_RS_HOST
Replication server hostname -
ERR_SETUP_INTERACTIVE_INVALID_HOST
'%s' is not a valid hostname -
INFO_SETUP_INTERACTIVE_BOOTSTRAP_RS_PORT
Replication port on %s -
INFO_SETUP_INTERACTIVE_ADD_ONE_BOOTSTRAP_RS
Do you want to add another replication server -
INFO_SETUP_INTERACTIVE_IS_BOOTSTRAP_SERVER_NEEDED
Do you want to specify a server to replicate with? This step can be skipped if this is the first server in the topology -
INFO_SETUP_INTERACTIVE_BOOTSTRAP_RS_SUMMARY
Replicate with server -
INFO_ERROR_INSTALLING_BACKUP_CLOUD_EXTENSIONS
public static LocalizableMessageDescriptor.Arg1<Object> INFO_ERROR_INSTALLING_BACKUP_CLOUD_EXTENSIONSError Installing Backup Cloud Extension for Directory Server: %s -
INFO_TASK_SHUTDOWN_DEFAULT_MESSAGE
The Directory Server shutdown process has been initiated by task %s -
INFO_TASK_SHUTDOWN_CUSTOM_MESSAGE
The Directory Server shutdown process has been initiated by task %s: %s -
ERR_TASK_ADDSCHEMAFILE_NO_FILENAME
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 -
ERR_TASK_ADDSCHEMAFILE_NO_SUCH_FILE
Unable to add one or more files to the server schema because the specified schema file %s does not exist in schema directory %s -
ERR_TASK_ADDSCHEMAFILE_ERROR_CHECKING_FOR_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_TASK_ADDSCHEMAFILE_ERROR_CHECKING_FOR_FILEObject> 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 -
ERR_TASK_ADDSCHEMAFILE_ERROR_LOADING_SCHEMA_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASK_ADDSCHEMAFILE_ERROR_LOADING_SCHEMA_FILEAn error occurred while attempting to load the contents of schema file %s into the server schema: %s -
ERR_TASK_ADDSCHEMAFILE_CANNOT_LOCK_SCHEMA
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 -
ERR_TASK_ADDSCHEMAFILE_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to modify the server schema -
ERR_TASK_BACKUP_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to initiate a Directory Server backup or backup purge -
ERR_TASK_RESTORE_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to initiate a Directory Server restore -
ERR_TASK_LDIFIMPORT_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to initiate an LDIF import -
ERR_TASK_LDIFEXPORT_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to initiate an LDIF export -
ERR_TASK_SHUTDOWN_INSUFFICIENT_RESTART_PRIVILEGES
You do not have sufficient privileges to initiate a Directory Server restart -
ERR_TASK_SHUTDOWN_INSUFFICIENT_SHUTDOWN_PRIVILEGES
You do not have sufficient privileges to initiate a Directory Server shutdown -
ERR_TASK_ADDSCHEMAFILE_CANNOT_NOTIFY_SYNC_PROVIDER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_TASK_ADDSCHEMAFILE_CANNOT_NOTIFY_SYNC_PROVIDERAn error occurred while attempting to notify a synchronization provider of type %s about the schema changes made by the add schema file task: %s -
ERR_TASK_INDEXREBUILD_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to initiate an index rebuild -
ERR_TASK_INITIALIZE_INVALID_DN
Invalid DN provided to the Initialize task: %s -
ERR_TASK_ENTERLOCKDOWN_NOT_ROOT
Only users with the SERVER_LOCKDOWN privilege may place the server in lockdown mode -
ERR_TASK_ENTERLOCKDOWN_NOT_LOOPBACK
Only users with the SERVER_LOCKDOWN privilege connected from a loopback address may place the server in lockdown mode -
ERR_TASK_LEAVELOCKDOWN_NOT_ROOT
Only users with the SERVER_LOCKDOWN privilege may cause the server to leave lockdown mode -
ERR_TASK_LEAVELOCKDOWN_NOT_LOOPBACK
Only users with the SERVER_LOCKDOWN privilege connected from a loopback address may cause the server to leave lockdown mode -
ERR_TASK_DISCONNECT_NO_PRIVILEGE
You do not have sufficient privileges to terminate client connections -
ERR_TASK_DISCONNECT_INVALID_CONN_ID
Unable to decode value %s as an integer connection ID -
ERR_TASK_DISCONNECT_NO_CONN_ID
Attribute %s must be provided to specify the connection ID for the client to disconnect -
ERR_TASK_DISCONNECT_INVALID_NOTIFY_CLIENT
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' -
INFO_TASK_DISCONNECT_GENERIC_MESSAGE
An administrator has terminated this client connection -
ERR_TASK_DISCONNECT_NO_SUCH_CONNECTION
There is no client connection with connection ID %s -
INFO_TASK_ADD_SCHEMA_FILE_NAME
Add Schema File -
INFO_TASK_BACKUP_NAME
Backup -
INFO_TASK_DISCONNECT_CLIENT_NAME
Disconnect Client -
INFO_TASK_ENTER_LOCKDOWN_MODE_NAME
Lockdown -
INFO_TASK_EXPORT_NAME
Export -
INFO_TASK_IMPORT_NAME
Import -
INFO_TASK_INITIALIZE_TARGET_NAME
Initialize Backend -
INFO_TASK_INITIALIZE_NAME
Initialize From Replica -
INFO_TASK_LEAVE_LOCKDOWN_MODE_NAME
Leave Lockdown -
INFO_TASK_REBUILD_NAME
Rebuild Index -
INFO_TASK_RESTORE_NAME
Restore -
INFO_TASK_SET_GENERATION_ID_NAME
Set Generation ID -
INFO_TASK_SHUTDOWN_NAME
Shutdown -
INFO_TASK_STATE_UNSCHEDULED
Unscheduled -
INFO_TASK_STATE_DISABLED
Disabled -
INFO_TASK_STATE_WAITING_ON_START_TIME
Waiting on start time -
INFO_TASK_STATE_WAITING_ON_DEPENDENCY
Waiting on dependency -
INFO_TASK_STATE_RUNNING
Running -
INFO_TASK_STATE_COMPLETED_SUCCESSFULLY
Completed successfully -
INFO_TASK_STATE_COMPLETED_WITH_ERRORS
Completed with errors -
INFO_TASK_STATE_STOPPED_BY_SHUTDOWN
Stopped by shutdown -
INFO_TASK_STATE_STOPPED_BY_ERROR
Stopped by error -
INFO_TASK_STATE_STOPPED_BY_ADMINISTRATOR
Stopped by administrator -
INFO_TASK_STATE_CANCELED_BEFORE_STARTING
Canceled before starting -
INFO_BACKUP_ARG_BACKEND_IDS
Backend ID(s) -
INFO_BACKUP_ARG_BACKUP_LOCATION
Backup Location -
INFO_EXPORT_ARG_LDIF_FILE
LDIF File -
INFO_EXPORT_ARG_BACKEND_ID
Backend ID -
INFO_EXPORT_ARG_APPEND_TO_LDIF
Append To LDIF -
INFO_EXPORT_ARG_COMPRESS_LDIF
Compress LDIF -
INFO_EXPORT_ARG_ENCRYPT_LDIF
Encrypt LDIF -
INFO_EXPORT_ARG_SIGN_HASH
Sign Hash -
INFO_EXPORT_ARG_INCL_ATTR
Include Attribute -
INFO_EXPORT_ARG_EXCL_ATTR
Exclude Attribute -
INFO_EXPORT_ARG_INCL_FILTER
Include Filter -
INFO_EXPORT_ARG_EXCL_FILTER
Exclude Filter -
INFO_EXPORT_ARG_INCL_BRANCH
Include Branch -
INFO_EXPORT_ARG_EXCL_BRANCH
Exclude Branch -
INFO_EXPORT_ARG_WRAP_COLUMN
Wrap Column -
INFO_RESTORE_ARG_BACKUP_DIR
Backup Directory -
INFO_RESTORE_ARG_BACKUP_ID
Backup ID -
INFO_IMPORT_ARG_LDIF_FILE
LDIF File -
INFO_IMPORT_ARG_BACKEND_ID
Backend ID -
INFO_IMPORT_ARG_INCL_ATTR
Include Attribute -
INFO_IMPORT_ARG_EXCL_ATTR
Exclude Attribute -
INFO_IMPORT_ARG_INCL_FILTER
Include Filter -
INFO_IMPORT_ARG_EXCL_FILTER
Exclude Filter -
INFO_IMPORT_ARG_INCL_BRANCH
Include Branch -
INFO_IMPORT_ARG_EXCL_BRANCH
Exclude Branch -
INFO_IMPORT_ARG_REJECT_FILE
Reject File -
INFO_IMPORT_ARG_SKIP_FILE
Skip File -
INFO_IMPORT_ARG_OVERWRITE
Overwrite -
INFO_IMPORT_ARG_SKIP_SCHEMA_VALIDATION
Skip Schema Validation -
INFO_IMPORT_ARG_IS_COMPRESSED
Is Compressed -
INFO_IMPORT_ARG_IS_ENCRYPTED
Is Encrypted -
INFO_IMPORT_ARG_CLEAR_BACKEND
Clear Backend -
INFO_FAILED_DEPENDENCY_ACTION_PROCESS
Process -
INFO_FAILED_DEPENDENCY_ACTION_CANCEL
Cancel -
INFO_FAILED_DEPENDENCY_ACTION_DISABLE
Disable -
INFO_TASK_STOPPED_BY_ADMIN
Task was stopped by an administrator: %s -
INFO_IMPORT_ARG_TEMPLATE_FILE
Template File -
INFO_IMPORT_ARG_RANDOM_SEED
Random Seed -
INFO_TASK_STATE_RECURRING
Recurring -
ERR_TASK_INDEXREBUILD_ALL_ERROR
Index option cannot be specified when the rebuildAll or rebuildDegraded option is used -
INFO_TASK_PURGE_CONFLICTS_HIST_NAME
Purge conflicts historical -
ERR_TASK_INVALID_ATTRIBUTE_VALUE
Attribute %s has an invalid value. Reason: %s -
INFO_TASK_RESET_CHANGE_NUMBER
Reset change number index to begin with a given number and change -
ERR_TASK_RESET_CHANGE_NUMBER_CHANGELOG_NOT_FOUND
public static LocalizableMessageDescriptor.Arg1<Object> ERR_TASK_RESET_CHANGE_NUMBER_CHANGELOG_NOT_FOUNDNo changelog database was found for baseDN '%s'. Either the baseDN is not replicated or its changelog has not been enabled in this server -
ERR_TASK_RESET_CHANGE_NUMBER_NO_RSES
The change number index cannot be reset because this OpenDJ instance does not appear to be a replication server -
ERR_TASK_RESET_CHANGE_NUMBER_INVALID
Invalid change number (%d) specified, it must be greater than zero -
ERR_TASK_RESET_CHANGE_NUMBER_FAILED
Unable to reset the change number index: %s -
ERR_TASK_ADDSCHEMAFILE_SCHEMA_VALIDATION_ERROR
public static LocalizableMessageDescriptor.Arg1<Object> ERR_TASK_ADDSCHEMAFILE_SCHEMA_VALIDATION_ERRORThe changes made by the add schema file task failed schema validation: %s -
INFO_TASK_WILL_BE_RETRIED
Retrying -
INFO_BACKUP_ARG_STORAGE_PROPERTY
Storage property -
INFO_BACKUP_PURGE_TASK_NAME
Purge backup(s) -
INFO_BACKUP_PURGE_ARG_BACKUP_LOCATION
Backup location -
INFO_BACKUP_PURGE_ARG_BACKUP_ID
Backup ID(s) -
INFO_BACKUP_PURGE_ARG_KEEP_COUNT
Keep count -
INFO_BACKUP_PURGE_ARG_REMOVE_OLDER_THAN
Remove older than -
INFO_BACKUP_PURGE_ARG_FORCE_OLDER_THAN
Force -
INFO_BACKUP_PURGE_BACKEND_NAME
Backend name(s) -
ERR_TASK_INITIALIZE_TARGET_INVALID_DN
Invalid DN provided to the Initialize Target task: %s -
ERR_TASK_PURGE_CONFLICTS_INVALID_DN
Invalid DN provided to the Purge Conflicts Historical task: %s -
ERR_TASK_RESET_GENERATION_ID_INVALID_DN
Invalid DN provided to the Reset Generation ID task: %s -
INFO_ENCPW_DESCRIPTION_LISTSCHEMES
List available password storage schemes -
INFO_ENCPW_DESCRIPTION_CLEAR_PW
Clear-text password to encode or to compare against an encoded password -
INFO_ENCPW_DESCRIPTION_ENCODED_PW
Encoded password to compare against the clear-text password -
INFO_ENCPW_DESCRIPTION_SCHEME
Scheme to use for the encoded password -
ERR_ERROR_PARSING_ARGS
An error occurred while parsing the command-line arguments: %s -
ERR_ENCPW_NO_CLEAR_PW
No clear-text password was specified. Use --%s, --%s or --%s to specify the password to encode -
ERR_ENCPW_NO_SCHEME
No password storage scheme was specified. Use the --%s argument to specify the storage scheme -
ERR_SERVER_BOOTSTRAP_ERROR
An unexpected error occurred while attempting to bootstrap the Directory Server client-side code: %s -
ERR_CANNOT_LOAD_CONFIG
An error occurred while trying to load the Directory Server configuration: %s -
ERR_CANNOT_LOAD_SCHEMA
An error occurred while trying to load the Directory Server schema: %s -
ERR_CANNOT_INITIALIZE_CORE_CONFIG
An error occurred while trying to initialize the core Directory Server configuration: %s -
ERR_CANNOT_INITIALIZE_STORAGE_SCHEMES
An error occurred while trying to initialize the Directory Server password storage schemes: %s -
ERR_ENCPW_NO_STORAGE_SCHEMES
No password storage schemes have been configured for use in the Directory Server -
ERR_ENCPW_NO_SUCH_SCHEME
Password storage scheme "%s" is not configured for use in the Directory Server -
INFO_ENCPW_PASSWORDS_MATCH
The provided clear-text and encoded passwords match -
INFO_ENCPW_PASSWORDS_DO_NOT_MATCH
The provided clear-text and encoded passwords do not match -
ERR_ENCPW_CANNOT_ENCODE
An error occurred while attempting to encode the clear-text password: %s -
INFO_LDIFEXPORT_DESCRIPTION_LDIF_FILE
Path to the LDIF file to write. All paths are relative to the server's installation directory, which can be remote -
INFO_LDIFEXPORT_DESCRIPTION_APPEND_TO_LDIF
Append an existing LDIF file rather than overwriting it -
INFO_LDIFEXPORT_DESCRIPTION_BACKEND_ID
Backend ID for the backend to export -
INFO_LDIFEXPORT_DESCRIPTION_EXCLUDE_BRANCH
Base DN of a branch to exclude from the LDIF export -
INFO_LDIFEXPORT_DESCRIPTION_INCLUDE_ATTRIBUTE
Attribute to include in the LDIF export -
INFO_LDIFEXPORT_DESCRIPTION_EXCLUDE_ATTRIBUTE
Attribute to exclude from the LDIF export -
INFO_LDIFEXPORT_DESCRIPTION_INCLUDE_FILTER
Filter to identify entries to include in the LDIF export -
INFO_LDIFEXPORT_DESCRIPTION_EXCLUDE_FILTER
Filter to identify entries to exclude from the LDIF export -
INFO_LDIFEXPORT_DESCRIPTION_WRAP_COLUMN
Column at which to wrap long lines (0 for no wrapping) -
INFO_LDIFEXPORT_DESCRIPTION_COMPRESS_LDIF
Compress the LDIF data as it is exported -
ERR_LDIFEXPORT_CANNOT_PARSE_EXCLUDE_FILTER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFEXPORT_CANNOT_PARSE_EXCLUDE_FILTERUnable to decode exclude filter string "%s" as a valid search filter: %s -
ERR_LDIFEXPORT_CANNOT_PARSE_INCLUDE_FILTER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFEXPORT_CANNOT_PARSE_INCLUDE_FILTERUnable to decode include filter string "%s" as a valid search filter: %s -
ERR_CANNOT_DECODE_BASE_DN
Unable to decode base DN string "%s" as a valid distinguished name: %s -
ERR_LDIFEXPORT_MULTIPLE_BACKENDS_FOR_ID
Multiple Directory Server backends are configured with the requested backend ID "%s" -
ERR_LDIFEXPORT_NO_BACKENDS_FOR_ID
None of the Directory Server backends are configured with the requested backend ID "%s" -
ERR_LDIFEXPORT_CANNOT_DECODE_EXCLUDE_BASE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFEXPORT_CANNOT_DECODE_EXCLUDE_BASEUnable to decode exclude branch string "%s" as a valid distinguished name: %s -
ERR_LDIFEXPORT_CANNOT_DECODE_WRAP_COLUMN_AS_INTEGER
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIFEXPORT_CANNOT_DECODE_WRAP_COLUMN_AS_INTEGERUnable to decode wrap column value "%s" as an integer -
ERR_LDIFEXPORT_ERROR_DURING_EXPORT
An error occurred while attempting to process the LDIF export: %s -
ERR_CANNOT_LOAD_BACKEND_CLASS
Unable to load class %s referenced in configuration entry %s for use as a Directory Server backend: %s -
ERR_CANNOT_INSTANTIATE_BACKEND_CLASS
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_CANNOT_INSTANTIATE_BACKEND_CLASSObject> Unable to create an instance of class %s referenced in configuration entry %s as a Directory Server backend: %s -
INFO_LDIFIMPORT_DESCRIPTION_LDIF_FILE
Path to the LDIF file to import. All paths are relative to the server's installation directory, which can be remote -
INFO_LDIFIMPORT_DESCRIPTION_BACKEND_ID
Backend ID for the backend to import -
INFO_LDIFIMPORT_DESCRIPTION_EXCLUDE_BRANCH
Base DN of a branch to exclude from the LDIF import -
INFO_LDIFIMPORT_DESCRIPTION_INCLUDE_ATTRIBUTE
Attribute to include in the LDIF import -
INFO_LDIFIMPORT_DESCRIPTION_EXCLUDE_ATTRIBUTE
Attribute to exclude from the LDIF import -
INFO_LDIFIMPORT_DESCRIPTION_INCLUDE_FILTER
Filter to identify entries to include in the LDIF import -
INFO_LDIFIMPORT_DESCRIPTION_EXCLUDE_FILTER
Filter to identify entries to exclude from the LDIF import -
INFO_LDIFIMPORT_DESCRIPTION_REJECT_FILE
Write rejected entries to the specified file -
INFO_LDIFIMPORT_DESCRIPTION_OVERWRITE
Overwrite an existing rejects and/or skip file rather than appending to it -
INFO_LDIFIMPORT_DESCRIPTION_IS_COMPRESSED
LDIF file is compressed -
ERR_LDIFIMPORT_CANNOT_PARSE_EXCLUDE_FILTER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_CANNOT_PARSE_EXCLUDE_FILTERUnable to decode exclude filter string "%s" as a valid search filter: %s -
ERR_LDIFIMPORT_CANNOT_PARSE_INCLUDE_FILTER
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_CANNOT_PARSE_INCLUDE_FILTERUnable to decode include filter string "%s" as a valid search filter: %s -
ERR_LDIFIMPORT_MULTIPLE_BACKENDS_FOR_ID
Imported branches or backend IDs can not span across multiple Directory Server backends -
ERR_LDIFIMPORT_NO_BACKENDS_FOR_ID
None of the Directory Server backends are configured with the requested backend ID or base DNs that include the specified branches -
ERR_LDIFIMPORT_CANNOT_DECODE_EXCLUDE_BASE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_CANNOT_DECODE_EXCLUDE_BASEUnable to decode exclude branch string "%s" as a valid distinguished name: %s -
ERR_LDIFIMPORT_CANNOT_OPEN_REJECTS_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_CANNOT_OPEN_REJECTS_FILEAn error occurred while trying to open the rejects file %s for writing: %s -
ERR_LDIFIMPORT_ERROR_DURING_IMPORT
An error occurred while attempting to process the LDIF import: %s -
INFO_VERIFYINDEX_DESCRIPTION_BASE_DN
Base DN of a backend supporting indexing. Verification is performed on indexes within the scope of the given base DN -
INFO_VERIFYINDEX_DESCRIPTION_INDEX_NAME
Name of an index to be verified. For an attribute index this is simply an attribute name. Multiple indexes may be verified for completeness, or all indexes if no indexes are specified. An index is complete if each index value references all entries containing that value -
INFO_VERIFYINDEX_DESCRIPTION_VERIFY_CLEAN
Specifies that a single index should be verified to ensure it is clean. An index is clean if each index value references only entries containing that value. Only one index at a time may be verified in this way -
ERR_VERIFYINDEX_ERROR_DURING_VERIFY
An error occurred while attempting to perform index verification: %s -
ERR_VERIFYINDEX_VERIFY_CLEAN_REQUIRES_SINGLE_INDEX
Only one index at a time may be verified for cleanliness -
ERR_BACKEND_NO_INDEXING_SUPPORT
The backend does not support indexing -
ERR_LDIFEXPORT_CANNOT_EXPORT_BACKEND
The Directory Server backend with backend ID "%s" does not provide a mechanism for performing LDIF exports -
ERR_LDIFIMPORT_CANNOT_IMPORT
The Directory Server backend with backend ID %s does not provide a mechanism for performing LDIF imports -
INFO_LDIFIMPORT_DESCRIPTION_INCLUDE_BRANCH
Base DN of a branch to include in the LDIF import -
ERR_LDIFIMPORT_CANNOT_DECODE_INCLUDE_BASE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_CANNOT_DECODE_INCLUDE_BASEUnable to decode include branch string "%s" as a valid distinguished name: %s -
ERR_LDIFIMPORT_INVALID_INCLUDE_BASE
Provided include base DN "%s" is not handled by the backend with backend ID %s -
ERR_MULTIPLE_BACKENDS_FOR_BASE
Multiple Directory Server backends are configured to support base DN "%s" -
ERR_NO_BACKENDS_FOR_BASE
None of the Directory Server backends are configured to support the requested base DN "%s" -
INFO_LDIFEXPORT_DESCRIPTION_INCLUDE_BRANCH
Base DN of a branch to include in the LDIF export -
ERR_LDIFEXPORT_INVALID_INCLUDE_BASE
Provided include base DN "%s" is not handled by the backend with backend ID %s -
ERR_CANNOT_INITIALIZE_CRYPTO_MANAGER
An error occurred while attempting to initialize the crypto manager: %s -
ERR_CANNOT_INITIALIZE_SUBENTRY_MANAGER
An error occurred while attempting to initialize the subentry manager: %s -
ERR_LDIFIMPORT_CANNOT_LOCK_BACKEND
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 -
WARN_LDIFIMPORT_CANNOT_UNLOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_LDIFIMPORT_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the exclusive lock for backend %s: %s. This lock should automatically be cleared when the import process exits, so no further action should be required -
ERR_LDIFEXPORT_CANNOT_LOCK_BACKEND
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 -
WARN_LDIFEXPORT_CANNOT_UNLOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_LDIFEXPORT_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the export process exits, so no further action should be required -
ERR_VERIFYINDEX_CANNOT_LOCK_BACKEND
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 -
WARN_VERIFYINDEX_CANNOT_UNLOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_VERIFYINDEX_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the verification process exits, so no further action should be required -
INFO_LDIFIMPORT_DESCRIPTION_SKIP_SCHEMA_VALIDATION
Skip schema validation during the LDIF import -
INFO_ENCPW_DESCRIPTION_AUTHPW
Use the authentication password syntax rather than the user password syntax -
ERR_ENCPW_NO_SUCH_AUTH_SCHEME
Authentication password storage scheme "%s" is not configured for use in the Directory Server -
ERR_ENCPW_INVALID_ENCODED_AUTHPW
The provided password is not a valid encoded authentication password value: %s -
ERR_CANNOT_INITIALIZE_PWPOLICY
An error occurred while attempting to initialize the password policy components: %s -
INFO_STOPDS_DESCRIPTION_STOP_REASON
Reason the server is being stopped or restarted -
INFO_STOPDS_DESCRIPTION_STOP_TIME
Indicates the date/time at which the shutdown operation will begin as a server task expressed in format YYYYMMDDhhmmssZ for UTC time or YYYYMMDDhhmmss for local time. A value of '0' will cause the shutdown to be scheduled for immediate execution. When this option is specified the operation will be scheduled to start at the specified time after which this utility will exit immediately -
ERR_STOPDS_CANNOT_DECODE_STOP_TIME
ERROR: Unable to decode the provided stop time. It should be in the form YYYYMMDDhhmmssZ for UTC time or YYYYMMDDhhmmss for local time -
ERR_STOPDS_IO_ERROR
ERROR: An I/O error occurred while attempting to communicate with the Directory Server: %s -
INFO_LDIFIMPORT_DESCRIPTION_QUIET
Use quiet mode (no output) -
INFO_LDIFIMPORT_DESCRIPTION_TEMPLATE_FILE
Path to a MakeLDIF template to use to generate the import data -
ERR_LDIFIMPORT_MISSING_REQUIRED_ARGUMENT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_MISSING_REQUIRED_ARGUMENTNeither the %s nor the %s argument was provided. One of these arguments must be given to specify the source for the LDIF data to be imported -
ERR_LDIFIMPORT_CANNOT_PARSE_TEMPLATE_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_CANNOT_PARSE_TEMPLATE_FILEUnable to parse the specified file %s as a MakeLDIF template file: %s -
INFO_LDIFIMPORT_DESCRIPTION_RANDOM_SEED
Seed for the MakeLDIF random number generator. To always generate the same data with the same command, use the same non-zero seed value. A value of zero (the default) results in different data each time the tool is run -
INFO_WAIT4DEL_DESCRIPTION_TARGET_FILE
Path to the file to watch for deletion -
INFO_WAIT4DEL_DESCRIPTION_LOG_FILE
Path to a file containing log output to monitor -
INFO_WAIT4DEL_DESCRIPTION_TIMEOUT
Maximum length of time in seconds to wait for the target file to be deleted before exiting -
WARN_WAIT4DEL_CANNOT_OPEN_LOG_FILE
WARNING: Unable to open log file %s for reading: %s -
INFO_ENCPW_TOOL_DESCRIPTION
This utility can be used to encode user passwords with a specified storage scheme, or to determine whether a given clear-text value matches a provided encoded password -
INFO_LDIFEXPORT_TOOL_DESCRIPTION
This utility can be used to export data from a Directory Server backend in LDIF form -
INFO_LDIFIMPORT_TOOL_DESCRIPTION
This utility can be used to import LDIF data into a Directory Server backend, overwriting existing data. It cannot be used to append data to the backend database -
INFO_STOPDS_TOOL_DESCRIPTION
This utility can be used to request that the Directory Server stop running or perform a restart. When run without explicit connection options, this utility sends a signal to the OpenDJ process to stop the server. When run with explicit connection options, this utility connects to the OpenDJ administration port and creates a shutdown task to stop the server -
INFO_VERIFYINDEX_TOOL_DESCRIPTION
This utility ensures that index data is consistent within an indexed backend database. Stop the server before running this tool -
INFO_WAIT4DEL_TOOL_DESCRIPTION
This utility can be used to wait for a file to be removed from the filesystem -
ERR_ENCPW_INVALID_ENCODED_USERPW
The provided password is not a valid encoded user password value: %s -
INFO_ENCPW_DESCRIPTION_USE_COMPARE_RESULT
Use the LDAP compare result as an exit code for the password comparison -
INFO_LDIFEXPORT_DESCRIPTION_EXCLUDE_OPERATIONAL
Exclude operational attributes from the LDIF export -
INFO_STOPDS_SERVER_ALREADY_STOPPED
Server already stopped -
INFO_STOPDS_GOING_TO_STOP
Stopping Server... -
ERR_WINDOWS_SERVICE_NOT_FOUND
Could not find the service name for the server -
ERR_WINDOWS_SERVICE_START_ERROR
An unexpected error occurred starting the server as a windows service -
ERR_WINDOWS_SERVICE_STOP_ERROR
An unexpected error occurred stopping the server windows service -
INFO_CONFIGURE_WINDOWS_SERVICE_TOOL_DESCRIPTION
This utility can be used to configure the server as a Windows service -
INFO_CONFIGURE_WINDOWS_SERVICE_DESCRIPTION_ENABLE
Enables the server as a Windows service -
INFO_CONFIGURE_WINDOWS_SERVICE_DESCRIPTION_DISABLE
Disables the server as a Windows service and stops the server -
INFO_CONFIGURE_WINDOWS_SERVICE_DESCRIPTION_STATE
Provides information about the state of the server as a Windows service -
ERR_CONFIGURE_WINDOWS_SERVICE_TOO_MANY_ARGS
You can only provide one of the following arguments: enableService, disableService, serviceState or cleanupService -
ERR_CONFIGURE_WINDOWS_SERVICE_TOO_FEW_ARGS
You must provide at least one of the following arguments: enableService, disableService or serviceState or cleanupService -
INFO_WINDOWS_SERVICE_NAME
%s -
INFO_WINDOWS_SERVICE_DESCRIPTION
Next Generation Directory Server. Installation path: %s -
INFO_WINDOWS_SERVICE_SUCCESSULLY_ENABLED
The server was successfully enabled to run as a Windows service -
INFO_WINDOWS_SERVICE_ALREADY_ENABLED
The server was already enabled to run as a Windows service -
ERR_WINDOWS_SERVICE_NAME_ALREADY_IN_USE
The server could not be enabled to run as a Windows service. The service name is already in use -
ERR_WINDOWS_SERVICE_ENABLE_ERROR
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) -
INFO_WINDOWS_SERVICE_SUCCESSULLY_DISABLED
The server was successfully disabled as a Windows service -
INFO_WINDOWS_SERVICE_ALREADY_DISABLED
The server was already disabled as a Windows service -
WARN_WINDOWS_SERVICE_MARKED_FOR_DELETION
The server has been marked for deletion as a Windows Service -
ERR_WINDOWS_SERVICE_DISABLE_ERROR
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) -
INFO_WINDOWS_SERVICE_ENABLED
The server is enabled as a Windows service. The service name for the server is: %s -
INFO_WINDOWS_SERVICE_DISABLED
The server is disabled as a Windows service -
ERR_WINDOWS_SERVICE_STATE_ERROR
An unexpected error occurred trying to retrieve the state of the server as a Windows service -
INFO_WAIT4DEL_DESCRIPTION_OUTPUT_FILE
Path to a file to which the command will write the output -
WARN_WAIT4DEL_CANNOT_OPEN_OUTPUT_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_WAIT4DEL_CANNOT_OPEN_OUTPUT_FILEWARNING: Unable to open output file %s for writing: %s -
INFO_CONFIGURE_WINDOWS_SERVICE_DESCRIPTION_CLEANUP
Disables the server as a Windows service and removes the Windows registry information associated with the specified service -
INFO_WINDOWS_SERVICE_CLEANUP_SUCCESS
Clean up of service %s was successful -
ERR_WINDOWS_SERVICE_CLEANUP_NOT_FOUND
Could not find the service with name %s -
WARN_WINDOWS_SERVICE_CLEANUP_MARKED_FOR_DELETION
public static LocalizableMessageDescriptor.Arg1<Object> WARN_WINDOWS_SERVICE_CLEANUP_MARKED_FOR_DELETIONService %s has been marked for deletion -
ERR_WINDOWS_SERVICE_CLEANUP_ERROR
An unexpected error occurred cleaning up the service %s -
INFO_REBUILDINDEX_TOOL_DESCRIPTION
This utility can be used to rebuild index data within an indexed backend database -
INFO_REBUILDINDEX_DESCRIPTION_BASE_DN
Base DN of a backend supporting indexing. Rebuild is performed on indexes within the scope of the given base DN -
INFO_REBUILDINDEX_DESCRIPTION_INDEX_NAME
Names of index(es) to rebuild. For an attribute index this is simply an attribute name. At least one index must be specified for rebuild. Cannot be used with the "--rebuildAll" option -
ERR_REBUILDINDEX_ERROR_DURING_REBUILD
An error occurred while attempting to perform index rebuild: %s -
ERR_REBUILDINDEX_WRONG_BACKEND_TYPE
The backend does not support rebuilding of indexes -
ERR_REBUILDINDEX_REQUIRES_AT_LEAST_ONE_INDEX
At least one index must be specified for the rebuild process -
ERR_REBUILDINDEX_CANNOT_EXCLUSIVE_LOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_REBUILDINDEX_CANNOT_EXCLUSIVE_LOCK_BACKENDAn 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 -
WARN_REBUILDINDEX_CANNOT_UNLOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_REBUILDINDEX_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the rebuild process exits, so no further action should be required -
ERR_REBUILDINDEX_CANNOT_SHARED_LOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_REBUILDINDEX_CANNOT_SHARED_LOCK_BACKENDAn 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 -
ERR_LDIFIMPORT_CANNOT_READ_FILE
The specified LDIF file %s cannot be read -
INFO_LDIFIMPORT_DESCRIPTION_COUNT_REJECTS
Count the number of entries rejected by the server and return that value as the exit code (values > 255 will be reduced to 255 due to exit code restrictions) -
INFO_LDIFIMPORT_DESCRIPTION_SKIP_FILE
Write skipped entries to the specified file -
ERR_LDIFIMPORT_CANNOT_OPEN_SKIP_FILE
An error occurred while trying to open the skip file %s for writing: %s -
INFO_VERIFYINDEX_DESCRIPTION_COUNT_ERRORS
Count the number of errors found during the verification and return that value as the exit code (values > 255 will be reduced to 255 due to exit code restrictions) -
INFO_LDIFIMPORT_DESCRIPTION_CLEAR_BACKEND
Remove all entries for all base DNs in the backend before importing -
ERR_LDIFIMPORT_MISSING_BACKEND_ARGUMENT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_MISSING_BACKEND_ARGUMENTNeither the %s nor the %s argument was provided. One of these arguments must be given to specify the backend for the LDIF data to be imported to -
INFO_TASK_TOOL_TASK_SCHEDULED_NOW
%s task %s scheduled to start immediately -
ERR_CREATERC_ONLY_RUNS_ON_UNIX
This tool may only be used on UNIX-based systems -
INFO_CREATERC_TOOL_DESCRIPTION
Create an RC script or systemd service that may be used to start, stop, and restart the Directory Server on UNIX-based systems -
INFO_CREATERC_RCSCRIPT_DESCRIPTION
The path to the RC script to create -
ERR_CREATERC_UNABLE_TO_DETERMINE_SERVER_ROOT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CREATERC_UNABLE_TO_DETERMINE_SERVER_ROOTUnable 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 -
ERR_CREATERC_CANNOT_WRITE
An error occurred while attempting to generate the RC script: %s -
INFO_DESCRIPTION_BACKEND_DEBUG_SUBCMD_LIST_ENTRY_CONTAINERS
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_BACKEND_DEBUG_SUBCMD_LIST_ENTRY_CONTAINERSList the base DNs in a backend -
INFO_DESCRIPTION_BACKEND_DEBUG_BACKEND_ID
The backend ID of the backend -
INFO_DESCRIPTION_BACKEND_DEBUG_BASE_DN
The base DN within the backend -
INFO_DESCRIPTION_BACKEND_DEBUG_INDEX_NAME
The name of the index -
INFO_DESCRIPTION_BACKEND_DEBUG_SKIP_DECODE
Do not try to decode backend data to their appropriate types -
INFO_DESCRIPTION_BACKEND_DEBUG_SUBCMD_LIST_INDEX_STATUS
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_BACKEND_DEBUG_SUBCMD_LIST_INDEX_STATUSShows the status of indexes for a backend base DN. This subcommand can take a long time to complete, as it reads all indexes for all backends -
INFO_DESCRIPTION_BACKEND_DEBUG_MAX_KEY_VALUE
Only show records with keys that should be ordered before the provided value using the comparator for the database container -
INFO_DESCRIPTION_BACKEND_DEBUG_MIN_KEY_VALUE
Only show records with keys that should be ordered after the provided value using the comparator for the database container -
INFO_DESCRIPTION_BACKEND_DEBUG_MAX_DATA_SIZE
Only show records whose data is no larger than the provided value -
INFO_DESCRIPTION_BACKEND_DEBUG_MIN_DATA_SIZE
Only show records whose data is no smaller than the provided value -
INFO_LABEL_BACKEND_DEBUG_BACKEND_ID
Backend ID -
INFO_LABEL_BACKEND_DEBUG_BASE_DN
Base DN -
ERR_BACKEND_DEBUG_NO_BACKENDS_FOR_ID
None of the Directory Server JE backends are configured with the requested backend ID %s -
ERR_BACKEND_DEBUG_NO_ENTRY_CONTAINERS_FOR_BASE_DN
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_BACKEND_DEBUG_NO_ENTRY_CONTAINERS_FOR_BASE_DNNone of the entry containers are configured with the requested base DN %s in backend %s -
ERR_BACKEND_DEBUG_DECODE_BASE_DN
Unable to decode base DN string "%s" as a valid distinguished name: %s -
INFO_LABEL_BACKEND_DEBUG_INDEX_MEDIAN
Median -
INFO_LABEL_BACKEND_DEBUG_INDEX_KEY_COUNT
Key Count -
INFO_LABEL_BACKEND_DEBUG_INDEX_SIZE
Size -
INFO_LABEL_BACKEND_DEBUG_RECORD_COUNT
Records -
INFO_LABEL_BACKEND_DEBUG_INDEX_NAME
Index Name -
INFO_LABEL_BACKEND_DEBUG_INDEX_TYPE
Type -
INFO_LABEL_BACKEND_DEBUG_INDEX_SECURE
Secure -
INFO_LABEL_BACKEND_DEBUG_INDEX_ENTRY_LIMIT
Entry Limit -
INFO_LABEL_BACKEND_DEBUG_INDEX_MEAN
Mean -
WARN_BACKEND_DEBUG_CANNOT_UNLOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_BACKEND_DEBUG_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the process exits, so no further action should be required -
ERR_BACKEND_DEBUG_CANNOT_LOCK_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_BACKEND_DEBUG_CANNOT_LOCK_BACKENDAn 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) -
INFO_LABEL_BACKEND_DEBUG_INDEX_KEY_OVER_LIMIT
Over -
INFO_LABEL_BACKEND_DEBUG_INDEX_80TH_PERCENTILE
80th -
INFO_LABEL_BACKEND_DEBUG_INDEX_95TH_PERCENTILE
95th -
INFO_LABEL_BACKEND_DEBUG_INDEX_99TH_PERCENTILE
99th -
ERR_MISSING_SUBCOMMAND
A sub-command must be specified -
INFO_CREATERC_USER_DESCRIPTION
The name of the user account under which the server should run -
INFO_CREATERC_JAVA_HOME_DESCRIPTION
The path to the Java installation that should be used to run the server -
INFO_CREATERC_JAVA_ARGS_DESCRIPTION
A set of arguments that should be passed to the JVM when running the server -
ERR_CREATERC_JAVA_HOME_DOESNT_EXIST
The directory %s specified as the OPENDJ_JAVA_HOME path does not exist or is not a directory -
ERR_UPGRADE_INCOMPATIBLE_ARGS
The argument '%s' is incompatible with '%s' -
INFO_TASKINFO_TOOL_DESCRIPTION
This utility can be used to obtain a list of tasks scheduled to run within the Directory Server as well as information about individual tasks -
INFO_TASKINFO_SUMMARY_ARG_DESCRIPTION
Print a summary of tasks -
INFO_TASKINFO_TASK_ARG_DESCRIPTION
ID of a particular task about which this tool will display information -
INFO_TASKINFO_CMD_REFRESH
refresh -
INFO_TASKINFO_CMD_CANCEL
cancel task -
INFO_TASKINFO_CMD_VIEW_LOGS
view logs -
INFO_TASKINFO_CMD_CANCEL_NUMBER_PROMPT
Enter the number of a task to cancel -
ERR_TASKINFO_INVALID_MENU_KEY
Invalid menu item or task number '%s' -
INFO_TASKINFO_FIELD_ID
ID -
INFO_TASKINFO_FIELD_TYPE
Type -
INFO_TASKINFO_FIELD_STATUS
Status -
INFO_TASKINFO_FIELD_SCHEDULED_START
Scheduled Start Time -
INFO_TASKINFO_FIELD_ACTUAL_START
Actual Start Time -
INFO_TASKINFO_FIELD_COMPLETION_TIME
Completion Time -
INFO_TASKINFO_FIELD_DEPENDENCY
Dependencies -
INFO_TASKINFO_FIELD_FAILED_DEPENDENCY_ACTION
Failed Dependency Action -
INFO_TASKINFO_FIELD_LOG
Log Message(s) -
INFO_TASKINFO_FIELD_LAST_LOG
Last Log Message -
INFO_TASKINFO_FIELD_NOTIFY_ON_COMPLETION
Email Upon Completion -
INFO_TASKINFO_FIELD_NOTIFY_ON_ERROR
Email Upon Error -
INFO_TASKINFO_CMD_CANCEL_SUCCESS
Task %s canceled -
ERR_TASKINFO_RETRIEVING_TASK_ENTRY
Error retrieving task entry %s: %s -
ERR_TASKINFO_UNKNOWN_TASK_ENTRY
There are no tasks with ID %s -
INFO_TASKINFO_DETAILS
Task Details -
INFO_TASKINFO_OPTIONS
%s Options -
INFO_TASKINFO_NO_TASKS
No tasks exist -
INFO_TASKINFO_NONE
None -
INFO_TASKINFO_NONE_SPECIFIED
None Specified -
INFO_TASKINFO_IMMEDIATE_EXECUTION
Immediate execution -
INFO_TASKINFO_LDAP_EXCEPTION
Error connecting to the directory server: '%s'. Verify that the connection options are correct and that the server is running -
INFO_TASKINFO_TASK_ARG_CANCEL
ID of a particular task to cancel -
INFO_TASKINFO_TYPE_ARG_DESCRIPTION
Show only tasks of this type -
INFO_TASK_TYPE_PLACEHOLDER
{taskType} -
INFO_TASKINFO_STATUS_ARG_DESCRIPTION
Show only tasks with this status -
INFO_TASK_STATUS_PLACEHOLDER
{taskStatus} -
ERR_TASKINFO_CANCELING_TASK
Error canceling task '%s': %s -
ERR_TASKINFO_ACCESSING_LOGS
Error accessing logs for task '%s': %s -
ERR_TASKINFO_NOT_CANCELABLE_TASK_INDEX
Task at index %d is not cancelable -
INFO_TASKINFO_NO_CANCELABLE_TASKS
There are currently no cancelable tasks -
ERR_TASK_CLIENT_UNKNOWN_TASK
There are no tasks defined with ID '%s' -
ERR_TASK_CLIENT_UNCANCELABLE_TASK
Task '%s' has finished and cannot be canceled -
ERR_TASK_CLIENT_TASK_STATE_UNKNOWN
State for task '%s' cannot be determined -
INFO_DESCRIPTION_START_DATETIME
Indicates the date/time at which this operation will start when scheduled as a server task expressed in YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time. A value of '0' will cause the task to be scheduled for immediate execution. When this option is specified the operation will be scheduled to start at the specified time after which this utility will exit immediately -
ERR_START_DATETIME_FORMAT
The start date/time must in YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time -
INFO_TASK_TOOL_TASK_SCHEDULED_FUTURE
public static LocalizableMessageDescriptor.Arg3<Object,Object, INFO_TASK_TOOL_TASK_SCHEDULED_FUTUREObject> %s task %s scheduled to start %s -
ERR_TASK_TOOL_START_TIME_NO_LDAP
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' -
INFO_DESCRIPTION_TASK_TASK_ARGS
Task Scheduling Options -
INFO_DESCRIPTION_TASK_LDAP_ARGS
Task Backend Connection Options -
INFO_DESCRIPTION_TASK_COMPLETION_NOTIFICATION
Email address of a recipient to be notified when the task completes. This option may be specified more than once -
INFO_DESCRIPTION_TASK_ERROR_NOTIFICATION
Email address of a recipient to be notified if an error occurs when this task executes. This option may be specified more than once -
INFO_DESCRIPTION_TASK_DEPENDENCY_ID
ID of a task upon which this task depends. A task will not start execution until all its dependencies have completed execution -
INFO_DESCRIPTION_TASK_FAILED_DEPENDENCY_ACTION
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_DESCRIPTION_TASK_FAILED_DEPENDENCY_ACTIONAction this task will take should one if its dependent tasks fail. The value must be one of %s. If not specified defaults to %s -
ERR_TASKTOOL_OPTIONS_FOR_TASK_ONLY
The option %s is only applicable when scheduling this operation as a task -
ERR_TASKTOOL_INVALID_EMAIL_ADDRESS
The value %s for option %s is not a valid email address -
ERR_TASKTOOL_INVALID_FDA
The failed dependency action value %s is invalid. The value must be one of %s -
ERR_TASKTOOL_FDA_WITH_NO_DEPENDENCY
The failed dependency action option is to be used in conjunction with one or more dependencies -
ERR_TASKINFO_TASK_NOT_CANCELABLE_TASK
Error: task %s is not in a cancelable state -
INFO_LDIFFILE_PLACEHOLDER
{ldifFile} -
INFO_SEED_PLACEHOLDER
{seed} -
INFO_HOST_PLACEHOLDER
{host} -
INFO_BASEDN_PLACEHOLDER
{baseDN} -
INFO_PATH_PLACEHOLDER
{path} -
INFO_FILTER_PLACEHOLDER
{filter} -
INFO_BACKENDNAME_PLACEHOLDER
{backendName} -
INFO_START_DATETIME_PLACEHOLDER
{startTime} -
INFO_EMAIL_ADDRESS_PLACEHOLDER
{emailAddress} -
INFO_TASK_ID_PLACEHOLDER
{taskID} -
INFO_ACTION_PLACEHOLDER
{action} -
INFO_SERVICE_NAME_PLACEHOLDER
{serviceName} -
INFO_USER_NAME_PLACEHOLDER
{userName} -
INFO_ARGS_PLACEHOLDER
{args} -
INFO_DATABASE_NAME_PLACEHOLDER
{databaseName} -
INFO_MAX_KEY_VALUE_PLACEHOLDER
{maxKeyValue} -
INFO_MIN_KEY_VALUE_PLACEHOLDER
{minKeyValue} -
INFO_MAX_DATA_SIZE_PLACEHOLDER
{maxDataSize} -
INFO_MIN_DATA_SIZE_PLACEHOLDER
{minDataSize} -
INFO_CLEAR_PWD
{clearPW} -
INFO_ENCODED_PWD_PLACEHOLDER
{encodedPW} -
INFO_STORAGE_SCHEME_PLACEHOLDER
{scheme} -
INFO_BRANCH_DN_PLACEHOLDER
{branchDN} -
INFO_ATTRIBUTE_PLACEHOLDER
{attribute} -
INFO_WRAP_COLUMN_PLACEHOLDER
{wrapColumn} -
INFO_TEMPLATE_FILE_PLACEHOLDER
{templateFile} -
INFO_REJECT_FILE_PLACEHOLDER
{rejectFile} -
INFO_SKIP_FILE_PLACEHOLDER
{skipFile} -
INFO_INDEX_PLACEHOLDER
{index} -
INFO_STOP_REASON_PLACEHOLDER
{stopReason} -
INFO_STOP_TIME_PLACEHOLDER
{stopTime} -
INFO_SECONDS_PLACEHOLDER
{seconds} -
INFO_TASK_TOOL_TASK_SUCCESSFULL
%s task %s has been successfully completed -
INFO_TASK_TOOL_TASK_NOT_SUCCESSFULL
%s task %s did not complete successfully -
INFO_RECURRING_TASK_PLACEHOLDER
{schedulePattern} -
ERR_CANNOT_INITIALIZE_SERVER_COMPONENTS
An error occurred while attempting to initialize server components to run the tool: %s -
ERR_LDIFIMPORT_COUNT_REJECTS_REQUIRES_OFFLINE
public static LocalizableMessageDescriptor.Arg1<Object> ERR_LDIFIMPORT_COUNT_REJECTS_REQUIRES_OFFLINEThe %s argument is not supported for online imports -
INFO_DESCRIPTION_RECURRING_TASK
Indicates the task is recurring and will be scheduled according to the value argument expressed in crontab(5) compatible time/date pattern -
INFO_TASK_TOOL_RECURRING_TASK_SCHEDULED
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_TASK_TOOL_RECURRING_TASK_SCHEDULEDRecurring %s task %s scheduled successfully -
INFO_LDIFEXPORT_PATH_TO_LDIF_FILE
Exporting to %s -
INFO_PROMPT_YES_COMPLETE_ANSWER
yes -
INFO_PROMPT_YES_FIRST_LETTER_ANSWER
y -
INFO_PROMPT_NO_COMPLETE_ANSWER
no -
INFO_PROMPT_NO_FIRST_LETTER_ANSWER
n -
ERR_START_DATETIME_ALREADY_PASSED
The specified start time '%s' has already passed -
ERR_STOPDS_DATETIME_ALREADY_PASSED
The specified stop time '%s' has already passed -
INFO_TASKINFO_CMD_REFRESH_CHAR
r -
INFO_TASKINFO_CMD_CANCEL_CHAR
c -
INFO_TASKINFO_CMD_VIEW_LOGS_CHAR
l -
ERR_TIMEOUT_DURING_STARTUP
The timeout of '%d' seconds has been reached. You can use the argument '--%s' to increase this timeout -
INFO_LDIFIMPORT_DESCRIPTION_TEMP_DIRECTORY
Path to temporary directory for index scratch files during LDIF import -
INFO_LDIFIMPORT_TEMP_DIR_PLACEHOLDER
{directory} -
INFO_LDIFIMPORT_DESCRIPTION_THREAD_COUNT
Number of threads used to read LDIF files during import. If 0, the number of threads will be set to twice the number of CPUs -
INFO_LDIFIMPORT_THREAD_COUNT_PLACEHOLDER
{count} -
ERR_LDIFIMPORT_CANNOT_PARSE_THREAD_COUNT
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_LDIFIMPORT_CANNOT_PARSE_THREAD_COUNTThe value %s for threadCount cannot be parsed: %s -
INFO_ENCPW_DESCRIPTION_INPUT_PW
The password to encode or to compare against an encoded password is interactively asked to the user -
INFO_ENCPW_INPUT_PWD_1
Please enter the password : -
INFO_ENCPW_INPUT_PWD_2
Please renter the password: -
ERR_ENCPW_NOT_SAME_PW
Provided passwords don't matched -
ERR_ENCPW_CANNOT_READ_PW
Cannot read password from the input: %s -
INFO_REBUILDINDEX_DESCRIPTION_REBUILD_ALL
Rebuild all indexes, including any DN2ID, DN2URI, VLV and extensible indexes. Cannot be used with the "-i" option or the "--rebuildDegraded" option -
INFO_REBUILDINDEX_TEMP_DIR_PLACEHOLDER
{directory} -
INFO_REBUILDINDEX_DESCRIPTION_TEMP_DIRECTORY
Path to temporary directory for index scratch files during index rebuilding -
INFO_PERIOD_PLACEHOLDER
{period} -
INFO_DESCRIPTION_REFRESH_PERIOD
When this argument is specified, the status command will display its contents periodically. Used to specify the period (in seconds) between two displays of the status -
ERR_WINDOWS_SERVICE_ENABLING_ERROR_STARTING_SERVER
public static LocalizableMessageDescriptor.Arg1<Number> ERR_WINDOWS_SERVICE_ENABLING_ERROR_STARTING_SERVERThe Windows Service was successfully configured but there was an error starting it. Error code starting Windows Service: %d -
INFO_DESCRIPTION_BACKEND_DEBUG_STATS_ONLY
Do not display backend data, just statistics -
ERR_RECURRING_SCHEDULE_FORMAT_ERROR
The provided schedule value has an invalid format. The schedule must be expressed using a crontab(5) format. Error details: %s -
INFO_REBUILDINDEX_DESCRIPTION_REBUILD_DEGRADED
Rebuild all degraded indexes, including any DN2ID, DN2URI, VLV and extensible indexes. Cannot be used with the "-i" option or the "--rebuildAll" option -
INFO_REBUILDINDEX_DESCRIPTION_CLEAR_DEGRADED_STATE
Indicates that indexes do not need rebuilding because they are known to be empty and forcefully marks them as valid. This is an advanced option which must only be used in cases where a degraded index is known to be empty and does not therefore need rebuilding -
ERR_VERSION_NOT_FOUND
The version of the installed OpenDJ could not be determined because the version file '%s' could not be found. Restore it from backup before continuing -
ERR_VERSION_MALFORMED
The version of the installed OpenDJ could not be determined because the version file '%s' exists but contains invalid data. Restore it from backup before continuing -
ERR_CONFIG_VERSION_MISMATCH
The OpenDJ binary version '%s' does not match the installed configuration version '%s'. Please run upgrade before continuing -
INFO_UPGRADE_OPTION_IGNORE_ERRORS
Ignores any errors which occur during the upgrade. This option should be used with caution and may be useful in automated deployments where potential errors are known in advance and resolved after the upgrade has completed -
INFO_UPGRADE_OPTION_FORCE
Forces a non-interactive upgrade to continue even if it requires user interaction. In particular, long running or critical upgrade tasks, such as re-indexing, which require user confirmation will be performed automatically. This option may only be used with the '%s' option -
INFO_UPGRADE_OPTION_DATA_ONLY
Upgrades only application data. OpenDJ configuration must have been upgraded before -
INFO_UPGRADE_DESCRIPTION_CLI
Upgrades OpenDJ configuration and application data so that it is compatible with the installed binaries.%n%nThis tool should be run immediately after upgrading the OpenDJ binaries and before restarting the server.%n%nNOTE: this tool does not provide backup or restore capabilities. Therefore, it is the responsibility of the OpenDJ administrator to take necessary precautions before performing the upgrade -
ERR_UPGRADE_MAIN_UPGRADE_PROCESS
The upgrade failed to complete for the following reason: %s -
INFO_UPGRADE_PERFORMING_TASKS
Performing upgrade -
INFO_UPGRADE_TITLE
OpenDJ Upgrade Utility -
ERR_UPGRADE_REQUIRES_SERVER_OFFLINE
OpenDJ cannot be upgraded because the server is currently running. Please stop the server and try again -
ERR_UPGRADE_VERSION_UP_TO_DATE
OpenDJ has already been upgraded to version %s -
ERR_UPGRADE_DISPLAY_NOTIFICATION_ERROR
An unexpected error occurred while attempting to display a notification: %s -
ERR_UPGRADE_DISPLAY_CONFIRM_ERROR
An unexpected error occurred while attempting to display a confirmation : %s -
INFO_UPGRADE_CHANGE_DONE_IN_SPECIFIC_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_UPGRADE_CHANGE_DONE_IN_SPECIFIC_FILE...Change(s) done in %s (x%s) -
INFO_UPGRADE_NO_CHANGE_DONE_IN_SPECIFIC_FILE
public static LocalizableMessageDescriptor.Arg1<Object> INFO_UPGRADE_NO_CHANGE_DONE_IN_SPECIFIC_FILE...No change applied in %s -
ERR_UPGRADE_TASKS_FAIL
An error occurred while performing an upgrade task: %s -
INFO_UPGRADE_TASK_NEEDS_USER_CONFIRM
%s.%nDo you want to make this change? -
INFO_UPGRADE_DISPLAY_CONFIRM_START
The upgrade is ready to proceed. Do you wish to continue? -
INFO_UPGRADE_ABORTED_BY_USER
The upgrade has been canceled -
ERR_UPGRADE_UNKNOWN_OC_ATT
No %s with OID %s exists in the schema -
ERR_UPGRADE_CONFIG_ERROR_UPGRADE_FOLDER
An error occurred when trying to upgrade the config/upgrade folder: %s -
INFO_UPGRADE_REQUIREMENTS
Preparing to upgrade -
INFO_UPGRADE_VERSION_IS_NOT_SUPPORTED
This tool cannot be used for upgrading versions of OpenDJ which are older than '%s'. Please upgrade to the latest 6.5 revision first before attempting further upgrades -
INFO_LICENSE_ACCEPT
Do you accept the License Agreement? -
INFO_ERROR_COPYING_FILE
An error occurred while copying the file '%s' to '%s' -
INFO_ERROR_DELETING_DIRECTORY
An error occurred while deleting directory '%s'. Check that you have the rights to delete this directory and that there is no other application using it. Error was: %s -
INFO_ERROR_DELETING_FILE
An error occurred while deleting file '%s': %s. Check that you have the rights to delete this file and that there is no other application using it -
ERR_UPGRADE_FAILS
The upgrade failed because %d errors were encountered. Please check log for further details -
ERR_UPGRADE_COPYSCHEMA_FAILS
An error occurred while copying the schema file '%s': %s -
ERR_UPGRADE_ADDATTRIBUTE_FAILS
An error occurred while adding one or more attributes to the schema file '%s': %s -
INFO_UPGRADE_GENERAL_SEE_FOR_DETAILS
See '%s' for a detailed log of this operation -
INFO_UPGRADE_TASK_REPLACE_SCHEMA_FILE
Replacing schema file '%s' -
INFO_UPGRADE_TASK_REFRESH_UPGRADE_DIRECTORY
Archiving concatenated schema -
INFO_UPGRADE_TASK_ADD_CONFIG_FILE
Adding '%s' configuration file -
ERR_UPGRADE_ADD_CONFIG_FILE_FAILS
An error occurred while adding configuration file '%s': %s -
INFO_UPGRADE_REBUILD_INDEX_STARTS
Rebuilding index(es) %s for base dn(s): %s -
INFO_UPGRADE_REBUILD_INDEX_ENDS
Rebuild index task ends -
INFO_UPGRADE_PERFORMING_POST_TASKS
Performing post upgrade tasks -
INFO_UPGRADE_POST_TASKS_COMPLETE
Post upgrade tasks complete -
ERR_UPGRADE_PERFORMING_POST_TASKS_FAIL
An error occurred during post upgrade task. Process aborted. Please check log for further details -
INFO_UPGRADE_ALL_REBUILD_INDEX_DECLINED
You have to rebuild all indexes manually to get a fully functional server -
ERR_UPGRADE_INVALID_LOG_FILE
Invalid log file %s -
INFO_UPGRADE_REBUILD_INDEX_ARGUMENTS
The rebuild index tool arguments are %s -
INFO_UPGRADE_REBUILD_ALL
Rebuilding all indexes -
INFO_UPGRADE_PROCESS_END
End of the upgrade process -
ERR_UPGRADE_CORRUPTED_TEMPLATE
'%s' is missing or empty, it is probably corrupted -
INFO_UPGRADE_NO_INDEX_TO_REBUILD_FOR_BACKEND
public static LocalizableMessageDescriptor.Arg1<Object> INFO_UPGRADE_NO_INDEX_TO_REBUILD_FOR_BACKENDNo indexes to rebuild for backend '%s' -
INFO_UPGRADE_CLASSES_FOLDER_RENAMED
The classes folder has been renamed to '%s' to avoid compatibility issues -
INFO_DESCRIPTION_BACKEND_TOOL_SUBCMD_LIST_BACKENDS
List the pluggable backends -
INFO_DESCRIPTION_BACKEND_TOOL_SUBCMD_LIST_RAW_DBS
List the low-level databases within a pluggable backend's storage engine. This subcommand may take a long time to complete depending on the size of the backend -
INFO_DESCRIPTION_BACKEND_TOOL_SUBCMD_LIST_INDEXES
List the indexes associated with a pluggable backend. This subcommand may take a long time to complete depending on the size of the backend -
INFO_DESCRIPTION_BACKEND_TOOL_SUBCMD_DUMP_INDEX
Dump records from an index, decoding keys and values. Depending on index size, this subcommand can generate lots of output -
INFO_DESCRIPTION_BACKEND_TOOL_SUBCMD_DUMP_RAW_DB
Dump the raw records in hexadecimal format for a low-level database within the pluggable backend's storage engine. Depending on index size, this subcommand can generate lots of output -
INFO_LABEL_BACKEND_TOOL_RAW_DB_NAME
Raw DB Name -
ERR_BACKEND_TOOL_ERROR_LISTING_BASE_DNS
An error occurred while listing the base DNs: %s -
ERR_BACKEND_TOOL_ERROR_LISTING_TREES
An error occurred while listing indexes: %s -
ERR_BACKEND_TOOL_ERROR_INITIALIZING_BACKEND
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_BACKEND_TOOL_ERROR_INITIALIZING_BACKENDAn unexpected error occurred while attempting to initialize the backend '%s': %s -
ERR_BACKEND_TOOL_ERROR_READING_TREE
An unexpected error occurred while attempting to read and/or decode records from an index: %s -
ERR_BACKEND_TOOL_NO_TREE_FOR_NAME
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_BACKEND_TOOL_NO_TREE_FOR_NAMEObject> No index exists with the requested name '%s' in base DN '%s' and backend '%s' -
ERR_BACKEND_TOOL_ONLY_ONE_MIN_KEY
Cannot specify a minimum key both as a string and as an hexadecimal string -
ERR_BACKEND_TOOL_ONLY_ONE_MAX_KEY
Cannot specify a maximum key both as a string and as an hexadecimal string -
ERR_BACKEND_TOOL_PROCESSING_ARGUMENT
An error occurred while processing arguments: %s -
ERR_BACKEND_TOOL_EXECUTING_COMMAND
An error occurred while trying to execute %s: %s -
INFO_LABEL_BACKEND_TOOL_TOTAL_KEYS
Total Keys -
INFO_LABEL_BACKEND_TOOL_KEYS_SIZE
Keys Size -
INFO_LABEL_BACKEND_TOOL_VALUES_SIZE
Values Size -
INFO_LABEL_BACKEND_TOOL_TOTAL_SIZES
Total Size -
INFO_DESCRIPTION_BACKEND_TOOL_USE_SI_UNITS
Uses SI Units for printing sizes -
INFO_DESCRIPTION_BACKEND_TOOL_SUBCMD_SINGLE_LINE
Write hexadecimal data on a single line instead of pretty format -
INFO_LABEL_BACKEND_TOOL_TOTAL
%nTotal: %d%n -
INFO_LABEL_BACKEND_TOOL_INDEX
%nIndex: %s%n -
INFO_LABEL_BACKEND_TOOL_OVER_INDEX_LIMIT_KEYS
public static LocalizableMessageDescriptor.Arg1<Object> INFO_LABEL_BACKEND_TOOL_OVER_INDEX_LIMIT_KEYSOver index-entry-limit keys: %s%n -
INFO_LABEL_BACKEND_TOOL_TOTAL_RECORDS
%nTotal Records: %d%n -
INFO_LABEL_BACKEND_TOOL_TOTAL_KEY_SIZE_AND_AVG
public static LocalizableMessageDescriptor.Arg2<Number,Number> INFO_LABEL_BACKEND_TOOL_TOTAL_KEY_SIZE_AND_AVGTotal / Average Key Size: %d bytes / %d bytes%n -
INFO_LABEL_BACKEND_TOOL_TOTAL_DATA_SIZE_AND_AVG
public static LocalizableMessageDescriptor.Arg2<Number,Number> INFO_LABEL_BACKEND_TOOL_TOTAL_DATA_SIZE_AND_AVGTotal / Average Data Size: %d bytes / %d bytes%n -
ERR_BACKEND_TOOL_CURSOR_AT_KEY_NUMBER
public static LocalizableMessageDescriptor.Arg2<Number,Object> ERR_BACKEND_TOOL_CURSOR_AT_KEY_NUMBERAt key number %d, %s: -
INFO_LABEL_BACKEND_TOOL_KEY_FORMAT
Key (len %d): -
INFO_LABEL_BACKEND_TOOL_VALUE_FORMAT
Value (len %d): -
ERR_BACKEND_TOOL_DECODER_NOT_AVAILABLE
Data decoder for printing is not available, should use hex dump -
ERR_BACKEND_TOOL_NO_TREE_FOR_NAME_IN_STORAGE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_BACKEND_TOOL_NO_TREE_FOR_NAME_IN_STORAGENo storage index exists with the requested name %s in backend %s -
INFO_DESCRIPTION_BACKEND_TOOL
This utility can be used to debug a backend -
INFO_INDEX_NAME_PLACEHOLDER
{indexName} -
INFO_DESCRIPTION_BACKEND_DEBUG_RAW_DB_NAME
The raw database name -
ERR_CANNOT_INITIALIZE_BACKENDS
An error occurred while initializing server backends: %s -
ERR_CANNOT_INITIALIZE_SERVER_PLUGINS
An error occurred while initializing plugins: %s -
ERR_CANNOT_SUBSYSTEM_NOT_INITIALIZED
Subsystem %s should be initialized first -
INFO_CONFIG_UPGRADE_SUMMARY
OpenDJ configuration will be upgraded from version %s to %s -
INFO_UPGRADE_CONFIG_IS_REQUIRED
OpenDJ data can't be upgraded because the configuration has not been upgraded yet. Upgrade the configuration first before upgrading the data -
INFO_DATA_UPGRADE_SUMMARY
OpenDJ data will be upgraded from version %s to %s -
INFO_DATA_UPGRADE_FROM_DEFAULT_VERSION_SUMMARY
public static LocalizableMessageDescriptor.Arg1<Object> INFO_DATA_UPGRADE_FROM_DEFAULT_VERSION_SUMMARYOpenDJ data will be upgraded to version %s -
INFO_DATA_UPGRADE_SUCCESSFUL
OpenDJ data was successfully upgraded to version %s -
ERR_UPGRADE_DATA_UP_TO_DATE
OpenDJ data has already been upgraded to version %s -
INFO_CONFIG_UPGRADE_SUCCESSFUL
OpenDJ configuration was successfully upgraded to version %s -
ERR_DATA_VERSION_MISMATCH
The OpenDJ binary version '%s' does not match the installed data version '%s'. Please run 'upgrade --dataOnly' before continuing -
INFO_CANNOT_DELETE_OBSOLETE_FILE
Upgrade failed to delete the obsolete file '%s'. Reason: %s -
INFO_DESCRIPTION_CHANGELOG_STAT
This utility can be used to debug changelog and changenumber files -
INFO_DESCRIPTION_CHANGELOG_STAT_SUBCMD_DUMP_CHANGE_NUMBER_DB
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_CHANGELOG_STAT_SUBCMD_DUMP_CHANGE_NUMBER_DBDump the change number DB -
INFO_DESCRIPTION_CHANGELOG_STAT_SUBCMD_DUMP_REPLICA_DB
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_CHANGELOG_STAT_SUBCMD_DUMP_REPLICA_DBDump the replica DB for a given domain and replica -
INFO_DESCRIPTION_CHANGELOG_STAT_SUBCMD_DUMP_REPLICA_DB_FILE
public static LocalizableMessageDescriptor.Arg0 INFO_DESCRIPTION_CHANGELOG_STAT_SUBCMD_DUMP_REPLICA_DB_FILEDump a replica DB file -
INFO_DESCRIPTION_CHANGELOG_STAT_OUTPUT_DIR
The output directory for the dump files -
INFO_DESCRIPTION_CHANGELOG_STAT_FROM_CN
The lower bound of the range of change numbers to dump -
INFO_DESCRIPTION_CHANGELOG_STAT_TO_CN
The upper bound of the range of change numbers to dump -
INFO_DESCRIPTION_CHANGELOG_STAT_FROM_CSN
The lower bound of the range of changes to dump -
INFO_DESCRIPTION_CHANGELOG_STAT_TO_CSN
The upper bound of the range of changes to dump -
INFO_CHANGELOG_STAT_OUTPUT_DIR_PLACEHOLDER
{directory} -
INFO_CHANGELOG_STAT_CHANGE_NUMBER_PLACEHOLDER
{change number} -
INFO_CHANGELOG_STAT_CSN_PLACEHOLDER
{csn} -
INFO_DESCRIPTION_CHANGELOG_STAT_BASE_DN
The base-dn of the changes contained in the provided replica DB file -
INFO_CHANGELOG_STAT_BASE_DN_PLACEHOLDER
{base dn} -
ERR_CHANGELOG_STAT_ERROR_WHEN_READING_RS_ENTRY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_STAT_ERROR_WHEN_READING_RS_ENTRYAn error occurred when reading the replication server configuration entry '%s': %s -
ERR_CHANGELOG_STAT_DOMAIN_NOT_FOUND
The replication domain '%s' is not found. Make sure the domain is replicated -
ERR_CHANGELOG_STAT_REPLICA_FOLDER_NOT_FOUND
Replica DB folder '%s' not found -
ERR_CHANGELOG_STAT_PROVIDED_CN_NOT_VALID
The provided change number '%s' is not valid -
ERR_CHANGELOG_STAT_PROVIDED_CSN_NOT_VALID
The provided CSN '%s' is not valid -
ERR_CHANGELOG_STAT_CANNOT_CREATE_OUTPUT_DIR
The output folder '%s' cannot be created -
ERR_CHANGELOG_STAT_PROVIDED_FILE_DOESNT_EXIST
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_STAT_PROVIDED_FILE_DOESNT_EXISTThe provided output folder '%s' doesn't exist -
ERR_CHANGELOG_STAT_PROVIDED_DN_IS_INVALID
The provided DN '%s' is invalid -
ERR_CHANGELOG_STAT_CANNOT_LIST_CHANGELOG_FILES
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_STAT_CANNOT_LIST_CHANGELOG_FILESCannot list the changelog files in '%s': %s -
ERR_CHANGELOG_STAT_CANNOT_CONVERT_FILENAME_TO_CN
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_STAT_CANNOT_CONVERT_FILENAME_TO_CNCannot convert the filename '%s' to a valid change number -
ERR_CHANGELOG_STAT_CANNOT_CONVERT_FILENAME_TO_CSN
public static LocalizableMessageDescriptor.Arg1<Object> ERR_CHANGELOG_STAT_CANNOT_CONVERT_FILENAME_TO_CSNCannot convert the filename '%s' to a valid CSN -
ERR_CHANGELOG_STAT_ERROR_WHEN_DECODING_CHANGELOG_FILE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_CHANGELOG_STAT_ERROR_WHEN_DECODING_CHANGELOG_FILEError while decoding the changelog file '%s' : %s -
INFO_CHANGELOG_STAT_ARGUMENTS
Arguments for changelogstat: %s -
ERR_UPGRADE_TO_PREVIOUS_CONF_VERSION
The OpenDJ binary version '%s' is older than the configuration version '%s', it usually means that an older version has been unzipped over the previous binaries. Unzip a more recent version than the configuration version and run upgrade again -
ERR_UPGRADE_TO_PREVIOUS_DATA_VERSION
The OpenDJ binary version '%s' is older than the data version '%s', it usually means that an older version has been unzipped over the previous binaries. Unzip a more recent version than the data version and run upgrade again -
INFO_CONFIG_AND_DATA_UPGRADE_SUMMARY
OpenDJ will be upgraded from version %s to %s -
INFO_UPGRADE_SUCCESSFUL
OpenDJ was successfully upgraded to version %s -
INFO_UPGRADE_TASK_MIGRATE_CONFIG_READ_FAIL
The upgrade will not be performed because the configuration file config.ldif could not be parsed -
INFO_UPGRADE_TASK_DELETE_FILE
Removing file '%s' -
ERR_LDIFIMPORT_LDIF_FILE_DOESNT_EXIST
Unable to access the LDIF file %s to import. Please check that the file is local to the server and the path correct -
INFO_UPGRADE_TASK_REMOVE_MONITOR_PROVIDERS_CFG_ENTRIES
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_REMOVE_MONITOR_PROVIDERS_CFG_ENTRIESRemoving configuration entries for the monitor providers -
INFO_UPGRADE_TASK_SET_GLOBAL_SERVER_ID
Setting global server ID -
INFO_UPGRADE_TASK_SET_NEW_GLOBAL_SERVER_ID
Setting new global server ID -
ERR_UPGRADE_TASK_NO_ADMIN_DATA
Could not find a server ID to set for the server. Verify the configuration references a valid server ID for domain cn=admin data -
INFO_UPGRADE_TASK_SET_GLOBAL_GROUP_ID_FROM_REPLICATION
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_SET_GLOBAL_GROUP_ID_FROM_REPLICATIONSetting global group ID and removing per domain values -
WARN_TRUSTSTORE_BACKEND_NOT_FOUND_USE_DEFAULT
public static LocalizableMessageDescriptor.Arg1<Object> WARN_TRUSTSTORE_BACKEND_NOT_FOUND_USE_DEFAULTUnable to find configuration for truststore backend "%s", using default values instead -
WARN_CRYPTO_MGR_NOT_FOUND_USE_DEFAULT
Unable to find configuration for crypto manager "%s", replication SSL configuration will use default values -
INFO_UPGRADE_TASK_UPDATE_REPLICATION_SSL_CONFIGURATION_VERBOSE
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_UPDATE_REPLICATION_SSL_CONFIGURATION_VERBOSEUpdate replication SSL configuration from crypto manager and trust store backend to dedicated key and trust manager provider configuration elements -
INFO_UPGRADE_TASK_UPDATE_REPLICATION_SSL_CONFIGURATION
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_UPDATE_REPLICATION_SSL_CONFIGURATIONUpdate replication SSL configuration -
INFO_UPGRADE_TASK_MOVE_SSL_PROTOCOLS_AND_CIPHER_SUITES
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_MOVE_SSL_PROTOCOLS_AND_CIPHER_SUITESMove SSL protocols and cipher suites configuration from crypto manager into each configuration element where they are used -
INFO_UPGRADE_TASK_REMOVE_SERVER_ID_FROM_REPLICATION
Removing global server ID from replication domains and replication server -
INFO_UPGRADE_TASK_ADD_MAILSERVERS
Adding Mail Servers -
INFO_UPGRADE_TASK_CONSOLIDATE_BOOTSTRAP_REPLICATION_SERVERS
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_CONSOLIDATE_BOOTSTRAP_REPLICATION_SERVERSConsolidating bootstrap replication servers from replication server and replication domains into Multimaster Synchronization provider -
INFO_UPGRADE_TASK_MIGRATE_TRUST_STORE_BACKEND_VERBOSE
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_MIGRATE_TRUST_STORE_BACKEND_VERBOSEMigrating truststore backend configuration to crypto manager -
INFO_UPGRADE_TASK_MIGRATE_TRUST_STORE_BACKEND
Migrating truststore backend configuration -
INFO_UPGRADE_TASK_UPDATE_DEFAULT_SECURITY_SETTINGS
Migrating security settings -
ERR_UPRADE_CRYPTO_MANAGER_NOT_FOUND
Crypto manager configuration entry not found -
REF_SHORT_DESC_CREATE_RC_SCRIPT
script to manage OpenDJ as a service on UNIX -
REF_SHORT_DESC_ENCODE_PASSWORD
encode a password with a storage scheme -
REF_SHORT_DESC_EXPORT_LDIF
export directory data in LDIF -
REF_SHORT_DESC_IMPORT_LDIF
import directory data from LDIF -
REF_SHORT_DESC_MANAGE_TASKS
manage server administration tasks -
REF_SHORT_DESC_REBUILD_INDEX
rebuild index after configuration change -
REF_SHORT_DESC_START_DS
start OpenDJ server -
REF_SHORT_DESC_STATUS
display basic OpenDJ server information -
REF_SHORT_DESC_STOP_DS
stop OpenDJ server -
REF_SHORT_DESC_UPGRADE
upgrade OpenDJ configuration and application data -
REF_SHORT_DESC_VERIFY_INDEX
check index for consistency or errors -
REF_SHORT_DESC_WINDOWS_SERVICE
register OpenDJ server as a Windows Service -
REF_SHORT_DESC_BACKEND_TOOL
gather OpenDJ backend debugging information -
REF_SHORT_DESC_CHANGELOG_TOOL
debug changelog and changenumber files -
SUPPLEMENT_DESCRIPTION_UPGRADE_CLI
<xinclude:include href="description-upgrade.xml" /> -
ERR_INSTANCE_NOT_CONFIGURED
The server has not been configured. Please run the 'setup' command first -
SUPPLEMENT_DESCRIPTION_BACKEND_TOOL_SUBCMD_LIST_INDEX_STATUS
public static LocalizableMessageDescriptor.Arg0 SUPPLEMENT_DESCRIPTION_BACKEND_TOOL_SUBCMD_LIST_INDEX_STATUS<xinclude:include href="variablelist-backendstat-index-status.xml" /> -
ERR_REBUILDINDEX_FOR_DN
Rebuild index aborted: an error has occurred while rebuilding indexes for base DN '%s' -
SUPPLEMENT_DESCRIPTION_RECURRING_TASK_INFO
<xinclude:include href="description-recurring-task-info.xml" /> -
ERR_UPGRADE_READING_CONF_FILE
An error occurred while reading configuration file: %s -
ERR_UPGRADE_COPY_FILES_FROM_TEMPLATE
An error occurred while copying data from '%s' to the server instance configuration directory. Error details: %s -
INFO_UPGRADE_TASK_PDB_TO_JE_1_SUMMARY
WARNING: OpenDJ %s removes support for the PDB Backends. The upgrade tool will reconfigure all PDB backends as JE backends. After the upgrade the new JE backend(s) will be empty. It is therefore very strongly recommended that any data that was in the PDB backends be exported to LDIF so that it can be re-imported once the upgrade completes -
INFO_UPGRADE_TASK_PDB_TO_JE_2_SUMMARY
Reconfiguring PDB backends to JE backends -
INFO_UPGRADE_TASK_RENAME_PDB_DIR
Renaming PDB backend directory '%s' to '%s' -
INFO_UPGRADE_TASK_PDB_TO_JE_WARNING
You must reimport all your data into the JE backends in order to have a fully functional server -
INFO_UPGRADE_TASK_JE_LOW_DURABILITY_SUMMARY
Replacing low durability settings in JE backends -
INFO_UPGRADE_TASK_JE_HIGH_DURABILITY_SUMMARY
Replacing high durability settings in JE backends -
INFO_UPGRADE_TASK_JE_MEDIUM_DURABILITY_SUMMARY
Replacing medium durability settings in JE backends -
INFO_UPGRADE_TASK_RENAME_JSON_SCHEMA
Renaming 'ds-cfg-json-schema' object class to 'ds-cfg-json-query-equality-matching-rule' -
ERR_UPGRADE_COPY_OPENDMK_JAR_FILE_TO_EXTLIB
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_UPGRADE_COPY_OPENDMK_JAR_FILE_TO_EXTLIBObject> An error occurred while copying OpenDMK jar file '%s' to '%s': %s -
INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_SUMMARY
Migrating root DN '%s' -
INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CLEANUP
Removing root DN users from configuration -
ERR_UPGRADE_TASK_MIGRATE_ROOT_DN_CANNOT_CREATE_DB_DIR
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_UPGRADE_TASK_MIGRATE_ROOT_DN_CANNOT_CREATE_DB_DIRRoot DNs could not be migrated because the '%s' directory could not be created: %s -
INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CONFIRM_RENAME
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CONFIRM_RENAMEOpenDJ 6.0.0 drops support for Root DNs and replaces them with standard user entries which are stored in LDIF backends. The root DN '%s' does not have an alias name so it must be renamed to '%s' so that it no longer resides inside the configuration. Do you want to proceed with the upgrade? -
INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CONFIRM_ALIAS_REMOVAL
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CONFIRM_ALIAS_REMOVALOpenDJ 6.0.0 drops support for Root DNs and replaces them with standard user entries which are stored in LDIF backends. The root DN '%s' has multiple alias names, but only the alias name '%s' will be kept. Do you want to proceed with the upgrade? -
INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CANCELLED
The upgrade will not be performed because some Root DNs need to be migrated -
INFO_UPGRADE_TASK_SEGREGATE_MUTABLE_IMMUTABLE_FILES
Segregating mutable and immutable files -
ERR_UPGRADE_TASK_CANNOT_CREATE_DIR
The directory '%s' could not be created: %s -
ERR_UPGRADE_TASK_CANNOT_RENAME_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_UPGRADE_TASK_CANNOT_RENAME_FILEObject> The file '%s' could not be renamed to '%s': %s -
INFO_UPGRADE_TASK_UPDATE_ADMIN_BACKEND_LOCATION
Update admin-backend.ldif file location -
INFO_UPGRADE_TASK_UPDATE_TASKS_BACKEND_LOCATION
Update tasks backend file location -
INFO_UPGRADE_TASK_REPLACE_PIN_OPTION
Replacing all pin related configuration attributes by a single pin configuration attribute -
INFO_UPGRADE_TASK_REMOVE_PIN_FILE_WARNING
The attribute has been removed because it was referring to a file that does not exist. You should replace it with the attribute %s before being able to enable the object corresponding to the configuration entry -
INFO_UPGRADE_TASK_REMOVE_WINDOW_SIZE_FROM_REPLICATION
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_REMOVE_WINDOW_SIZE_FROM_REPLICATIONRemoving send and receive window size configuration in replication -
ERR_TASK_TOOL_ERROR_CODE
tool exit with error return code '%d' -
INFO_UPGRADE_TASK_MIGRATE_CHANGELOG_65_FORMAT
Migrating replication changelog files to 6.5.0 format -
ERR_UPGRADE_TASK_CANNOT_READ_CHANGELOG_FILES
public static LocalizableMessageDescriptor.Arg1<Object> ERR_UPGRADE_TASK_CANNOT_READ_CHANGELOG_FILESAn error occurred reading the changelog files: %s -
ERR_UPGRADE_TASK_CANNOT_RENAME_CHANGELOG_FILES
public static LocalizableMessageDescriptor.Arg1<Object> ERR_UPGRADE_TASK_CANNOT_RENAME_CHANGELOG_FILESAn error occurred while renaming the changelog files: %s -
ERR_UPGRADE_TASK_MIGRATE_OFFLINE
An error occurred while migrating replicas' offline states to the changelog files: %s -
INFO_UPGRADE_TASK_ADD_CONFIG_ENTRY
Adding configuration entry '%s' -
ERR_UPGRADE_TASK_MODIFY_CONFIG_FILE
An error occurred while trying to modify %s : %s -
INFO_UPGRADE_TASK_COMPUTE_CHANGE_NUMBER_SUMMARY
Replacing compute change number setting in replication server -
INFO_UPGRADE_TASK_REBUILD_DS_SYNCH_HIST_OMR
OpenDJ 6.5.0 changed the indexing algorithm for replication metadata. Its index must be rebuilt which may take a long time; without a working index every server start will take longer than normal. Do you want to rebuild the index automatically at the end of the upgrade? -
INFO_UPGRADE_TASK_REJECT_UNAUTHENTICATED_REQUESTS_SUMMARY
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_REJECT_UNAUTHENTICATED_REQUESTS_SUMMARYReplacing "reject unauthenticated requests" policy in global configuration -
INFO_UPGRADE_TASK_REMOVE_ASSURED_REPLICATION
Removing configuration for assured replication -
INFO_UPGRADE_TASK_REMOVE_REDUNDANT_GENERATION_ID
Removing generation-id data from configuration -
INFO_UPGRADE_TASK_REMOVE_REDUNDANT_SYNC_STATE
Removing synchronization state data from configuration -
INFO_UPGRADE_TASK_RENAME_SERVICE_DISCOVERY_MECHANISM_TO_SHARD
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_RENAME_SERVICE_DISCOVERY_MECHANISM_TO_SHARDRenaming the proxy backend configuration property 'service discovery mechanism' to 'shard' -
INFO_UPGRADE_TASK_UPDATE_CAUD_LOGGERS
Adding objectClass to JSON, CSV, and External access logger configurations -
ERR_SERVER_MUST_NOT_BE_ONLINE
Server is running. Please stop the server before running this tool -
INFO_UPGRADE_TASK_REMOVE_MONITORING_PERIOD
Removing configuration for replication monitoring -
ERR_CANNOT_READ_CONFIG_VERSION
An error occurred when trying to read the configuration version in %s : %s -
ERR_CANNOT_READ_UPGRADE_NUMBER
An error occurred when trying to read the upgrade version in second line of file '%s' (%s) -
INFO_UPGRADE_TASK_PROXY_HASH_FUNCTION
Set the proxy backend configuration property 'hash-function' to MD5 -
INFO_UPGRADE_TASK_DISABLE_SHARED_CACHE
Use the old JE backend caches instead of the new shared cache -
INFO_UPGRADE_TASK_RENAME_CONNECTION_POOL_ATTRIBUTES
Renaming ds-cfg-connection-pool-* attributes to ds-cfg-bind-connection-pool-* -
INFO_UPGRADE_TASK_DB_CACHE_MODE
Set the database cache mode 'ds-cfg-db-cache-mode' to 'cache-ln' -
INFO_UPGRADE_TASK_INHERIT_FROM_DN_PARENT
Add 'inheritFromDNParent' attribute type to the 'inheritedCollectiveAttributeSubentry' object class -
ERROR_COULD_NOT_FIND_ADS_CERTIFICATE
Could not find 'ads-certificate' entry in the truststore '%s'. This entry is required for the correct behavior of the directory server -
WARN_COULD_NOT_RETRIEVE_KEYS_FROM_TRUSTSTORE
Unable to retrieve the keys from the truststore -
WARN_COULD_NOT_READ_ADMIN_BACKEND
Unable to look up server key id '%s' in the admin backend -
WARN_COULD_NOT_RETRIEVE_HOSTNAME_FROM_ADMIN_BACKEND
public static LocalizableMessageDescriptor.Arg1<Object> WARN_COULD_NOT_RETRIEVE_HOSTNAME_FROM_ADMIN_BACKENDUnable to retrieve the hostname from the admin backend using the truststore as source of keys; 'advertised-listen-address' attribute in global configuration will use the local hostname as value. Cause: %s -
ERROR_COULD_NOT_RETRIEVE_LOCAL_HOSTNAME
Unable to retrieve the local hostname, the 'advertised-listen-address' attribute in global configuration must be set manually -
INFO_UPGRADE_TASK_SET_GLOBAL_ADDRESSES
Adding 'listen-address' and 'advertised-listen-address' attributes to the global configuration -
INFO_UPGRADE_TASK_REMOVE_REDUNDANT_LISTEN_ADDRESS
Removing 'listen-address' attributes that are redundant with default value provided by the global configuration -
ERROR_UNABLE_TO_UPDATE_LISTEN_ADDRESS_ATTR
An error occurred while removing some 'listen-address' attribute values from the configuration -
INFO_UPGRADE_REBUILD_INDEXES_TELEPHONENUMBER_EMR_SMR
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_REBUILD_INDEXES_TELEPHONENUMBER_EMR_SMROpenDJ 7.0.0 changed the indexing algorithm for TelephoneNumber equality and substring matching rules. All TelephoneNumber syntax based attribute indexes must be rebuilt which may take a long time. Do you want to rebuild the indexes automatically at the end of the upgrade? -
INFO_UPGRADE_ADD_FULL_VENDOR_VERSION_ACI
Add ACI to make Root DSE fullVendorVersion operational attribute user visible -
INFO_UPGRADE_REMOVE_REFERENCES_TO_BACKUP_BACKEND
Removing references to 'backup' backend -
INFO_UPGRADE_REMOVE_BACKUP_BACKEND
Removing 'backup' backend -
INFO_UPGRADE_TASK_MIGRATE_ECL_DOMAIN_CONFIG
Remove External change log domain configuration entries and migrate information to the domains and the replication server configuration entries -
INFO_UPGRADE_TASK_MIGRATE_SOURCE_ADDRESS_TO_REPL_SYNC_PROVIDER_CONFIG
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_MIGRATE_SOURCE_ADDRESS_TO_REPL_SYNC_PROVIDER_CONFIGMigrate source address attribute from replication server configuration to replication synchronization provider configuration -
INFO_UPGRADE_TASK_MIGRATE_REPLICATION_DOMAIN_CONFIG_ATTRIBUTES
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_MIGRATE_REPLICATION_DOMAIN_CONFIG_ATTRIBUTESMigrate common replication domain configuration attributes to replication synchronization provider configuration -
WARNING_UPGRADE_MULTIPLE_VALUES_TO_MIGRATE_FOR_REPLICATION_DOMAIN_CONFIG_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARNING_UPGRADE_MULTIPLE_VALUES_TO_MIGRATE_FOR_REPLICATION_DOMAIN_CONFIG_ATTRIBUTEObject> Configuration attribute %s has distinct values in replication domain configuration entries. Migration to replication synchronization provider configuration will keep only one value, '%s' and discarded '%s' -
INFO_UPGRADE_REMOVE_REFERENCES_TO_DS_TASK_BACKUP_ALL
public static LocalizableMessageDescriptor.Arg1<Object> INFO_UPGRADE_REMOVE_REFERENCES_TO_DS_TASK_BACKUP_ALLRemoving '%s' attribute(s) from backup tasks -
ERR_UPGRADE_CANNOT_REMOVE_REFERENCES_TO_DS_TASK_BACKUP_ALL
public static LocalizableMessageDescriptor.Arg1<Object> ERR_UPGRADE_CANNOT_REMOVE_REFERENCES_TO_DS_TASK_BACKUP_ALL'%s' attributes couldn't be removed from backup tasks -
INFO_UPGRADE_REMOVE_RESTORE_TASKS
Removing restore tasks -
ERR_UPGRADE_CANNOT_REMOVE_RESTORE_TASKS
The restore tasks couldn't be removed -
INFO_UPGRADE_RESTORE_TASKS_SUMMARY
DS 7.0.0 breaks restore tasks compatibility, all existing restore tasks will be removed -
INFO_UPGRADE_TASK_MIGRATE_ISOLATION_POLICY_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_MIGRATE_ISOLATION_POLICY_ATTRIBUTEMigrate isolation policy attribute to replication synchronization provider configuration -
INFO_UPGRADE_TASK_MIGRATE_PURGE_DELAY_ATTRIBUTES
Merge replication-purge-delay and conflicts-historical-purge-delay attribute into a single replication-purge-delay attribute in replication synchronizer provider configuration -
ERR_UPGRADE_CANNOT_READ_CONFIG_FILE
An error occured when trying to read the configuration file %s: %s -
WARN_UPGRADE_CANNOT_FIND_TASK_BACKEND_FILE
public static LocalizableMessageDescriptor.Arg3<Object,Object, WARN_UPGRADE_CANNOT_FIND_TASK_BACKEND_FILEObject> Unable to find the task backend file location in the configuration file %s, entry '%s' or attribute '%s' is missing -
INFO_UPGRADE_TASK_REMOVE_PROFILER_PLUGIN
Removing profiler plugins -
INFO_UPGRADE_REMOVE_WORKQUEUE_CAPACITY
Removing max-work-queue-capacity -
INFO_UPGRADE_TASK_MIGRATE_ENCRYPTED_CHANGELOG
Migrating encrypted replication changelog files -
ERR_UPGRADE_TASK_CANNOT_UPGRADE_ENCRYPTED_CHANGELOG
public static LocalizableMessageDescriptor.Arg1<Object> ERR_UPGRADE_TASK_CANNOT_UPGRADE_ENCRYPTED_CHANGELOGAn error occurred while migrating encrypted changelog files: %s -
INFO_UPGRADE_TASK_RENAME_BACKUP_DIRECTORY_PATH_INTO_BACKUP_LOCATION
public static LocalizableMessageDescriptor.Arg1<Object> INFO_UPGRADE_TASK_RENAME_BACKUP_DIRECTORY_PATH_INTO_BACKUP_LOCATIONRename attribute 'ds-backup-directory-path' to 'ds-backup-location' in entries of objectClass '%s' -
ERR_UPGRADE_CANNOT_RENAME_BACKUP_DIRECTORY_PATH_INTO_BACKUP_LOCATION
public static LocalizableMessageDescriptor.Arg1<Object> ERR_UPGRADE_CANNOT_RENAME_BACKUP_DIRECTORY_PATH_INTO_BACKUP_LOCATIONAttribute 'ds-backup-directory-path' could not be renamed to 'ds-backup-location' in entries of objectclass '%s' -
INFO_UPGRADE_TASK_RENAME_MUTUAL_TLS_TO_SASL_EXTERNAL
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_RENAME_MUTUAL_TLS_TO_SASL_EXTERNALRenaming the 'use-mutual-tls' configuration property to 'use-sasl-external' -
INFO_UPGRADE_TASK_RENAME_REPL_SERVER_TO_BOOTSTRAP_REPL_SERVER
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_RENAME_REPL_SERVER_TO_BOOTSTRAP_REPL_SERVERRenaming the 'replication-server' configuration property to 'bootstrap-replication-server' -
INFO_CREATERC_SYSTEMD_DESCRIPTION
The path to the systemd service file to create -
ERR_CREATERC_CANNOT_WRITE_SYSTEMD
An error occurred while attempting to generate the systemd service file: %s -
INFO_DESCRIPTION_TASK_ID
Gives an ID to the task -
INFO_TASK_DESCRIPTION_PLACEHOLDER
{description} -
INFO_DESCRIPTION_TASK_DESCRIPTION
Gives a description to the task -
INFO_TASKINFO_FIELD_DESCRIPTION
Description -
INFO_UPGRADE_ALLOW_BACKUP_PURGE_TASKS
Allowing dsbackup purge tasks -
INFO_UPGRADE_REMOVE_EMPTY_GROUP_CONFIGURATIONS
Removing empty configuration for groups -
INFO_REPLACE_COMMAS_IN_GROUPID
Replacing non allowed comma in groupID definition with a dot -
INFO_UPGRADE_TASK_REMOVE_PROXY_BACKEND_LOAD_BALANCER_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_REMOVE_PROXY_BACKEND_LOAD_BALANCER_ATTRIBUTERemoving 'ds-cfg-load-balancing-algorithm' attribute from the proxy backend -
INFO_UPGRADE_TASK_RENAME_BIND_CONNECTION_POOL_ATTRIBUTES
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_RENAME_BIND_CONNECTION_POOL_ATTRIBUTESRenaming 'ds-cfg-bind-connection-pool-*' attributes to 'ds-cfg-connection-pool-*' -
INFO_UPGRADE_TASK_REMOVE_REQUEST_CONNECTION_POOL
Removing 'ds-cfg-request-connection-pool-size' attribute,'ds-cfg-connection-pool-size' will be used instead -
INFO_UPGRADE_ALLOW_LDAP_SYNTAXES
Add 'ldapSyntaxes' to attribute list which can be read in the schema access global access control policies -
INFO_UPGRADE_TASK_RENAME_CHANGELOG_FILES
Renaming replication changelog files from .log to .cdb suffix -
ERR_UPGRADE_INVALID_SEQUENCE_FOR_TASKS_VERSION
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_UPGRADE_INVALID_SEQUENCE_FOR_TASKS_VERSIONObject> Invalid sequence for task version: task %s tried to register for version %s but the previous task used a higher version: %s. This suggests there is a copy/paste error in the version number -
INFO_UPGRADE_TASK_RENAME_PROXY_HEARTBEAT_ATTRIBUTES
Renaming proxy 'ds-cfg-heartbeat-*' attributes to 'ds-cfg-keep-alive-*` -
ERR_UPGRADE_CONFIG_SCHEMA_FILE
"Error parsing existing schema file '%s' - %s" -
INFO_UPGRADE_TASK_REBUILD_DUE_TO_DUPLICATE_ENTRY_IDS
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_REBUILD_DUE_TO_DUPLICATE_ENTRY_IDSOpenDJ 7.2.0 fixed an indexing bug that may cause searches to return duplicate entries in certain circumstances. All indexes have to be rebuilt. This could take a long time to proceed. Do you want to launch this process automatically at the end of the upgrade? -
INFO_UPGRADE_DELETE_LOOKTHROUGH_LIMIT
Removing look through limit from the configuration -
INFO_UPGRADE_RENAME_CURSOR_LIMIT
Renaming 'ds-cfg-cursor-entry-limit' to 'ds-cfg-max-candidate-set-size' -
INFO_UPGRADE_DELETE_VLV_WITH_BASE_OBJECT_SCOPE_CONFIG
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_DELETE_VLV_WITH_BASE_OBJECT_SCOPE_CONFIGRemoving VLV indexes with base-object scope from the configuration -
INFO_UPGRADE_JE_BACKEND_PROPERTIES
Migrating JE environment properties to configuration attributes -
INFO_UPGRADE_DELETE_DEGRADED_STATUS_THRESHOLD
Removing replica degraded status threshold configuration -
INFO_DELETE_LDIF_CHANGERECORD_REMNANTS
Remove LDIF change record remnants from the configuration -
INFO_UPGRADE_REBUILD_ALL_DUE_TO_STRING_PREP_CHANGES
Changes in Unicode string normalization require that all indexes are rebuilt. Do you want to rebuild the indexes automatically at the end of the upgrade? -
INFO_UPGRADE_DELETE_SEND_REJECT_NOTIFICATION
Removing LDAP send reject notification configuration -
INFO_UPGRADE_DELETE_DEBUG_LOG_CONFIG
Removing debug logging configuration -
INFO_UPGRADE_REPLACE_SEVERITY_VALUES
Replace multiple severity values by a single one in logging configurations -
INFO_UPGRADE_TASK_INHERIT_ATTRIBUTE_SYNTAX_CHANGE
Changing syntax for 'inheritAttribute' attribute type to IA5String -
INFO_UPGRADE_REBUILD_ENTRYUUID_INDEX_DUE_TO_DATA_CORRUPTION
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_REBUILD_ENTRYUUID_INDEX_DUE_TO_DATA_CORRUPTIONOPENDJ-9550 on 7.3.0 caused static groups to lose their operational attributes on modify operations, corrupting data and the entryUUID index which needs to be rebuilt. Do you want to rebuild the indexes automatically at the end of the upgrade? -
INFO_CREATERC_GROUP_DESCRIPTION
The name of the group account under which the server should run -
INFO_GROUP_NAME_PLACEHOLDER
{groupName} -
ERR_CREATERC_PROVIDE_ONE_ARG
You must provide either the --%s or the --%s argument -
INFO_UPGRADE_TASK_MAKE_FILE_BASED_ERROR_LOGGERS_ASYNCHRONOUS
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_MAKE_FILE_BASED_ERROR_LOGGERS_ASYNCHRONOUSMake the File-Based Error Loggers perform asynchronous logging for optimal performance after merging the debug and error logger -
INFO_UPGRADE_ENABLE_CHANGE_NUMBER_INDEXER
Enabling change numbers in the replication changelog -
INFO_UPGRADE_ARGON2_MEMORY
Removing 'ds-cfg-argon2-migration-memory' and adding 'ds-cfg-argon2-memory-pool-size' which specifies the size of the memory pool allocated for concurrent Argon2 password hashing computations -
INFO_UPGRADE_ADD_JSON_ACCESS_LOG_PUBLISHER_EXCLUDE_VALUES_OF_ATTRIBUTES
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_ADD_JSON_ACCESS_LOG_PUBLISHER_EXCLUDE_VALUES_OF_ATTRIBUTESAdding 'ds-cfg-exclude-values-of-attributes' with the list the attribute names which values will be excluded from the list of requested modifications -
INFO_UPGRADE_DISABLE_CERTLIST_VALIDATION
Continue to allow invalid certificate lists, certificate pairs and postal addresses -
INFO_UPGRADE_TASK_RENAME_BIG_INDEX_MATCHING_RULE_ATTRIBUTE
public static LocalizableMessageDescriptor.Arg0 INFO_UPGRADE_TASK_RENAME_BIG_INDEX_MATCHING_RULE_ATTRIBUTERenaming 'ds-cfg-big-index-matching-rule' attribute to 'ds-cfg-big-index-extensible-matching-rule` -
ERR_HEX_DECODE_INVALID_LENGTH
The value %s cannot be decoded as a hexadecimal string because it does not have a length that is a multiple of two bytes -
ERR_HEX_DECODE_INVALID_CHARACTER
The value %s cannot be decoded as a hexadecimal string because it contains an illegal character %c that is not a valid hexadecimal digit -
ERR_LDIF_INVALID_LEADING_SPACE
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 -
ERR_LDIF_NO_ATTR_NAME
Unable to parse LDIF entry starting at line %d because the line "%s" does not include an attribute name -
ERR_LDIF_NO_DN
Unable to parse LDIF entry starting at line %d because the first line does not contain a DN (the first line was "%s" -
ERR_LDIF_INVALID_DN
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 -
ERR_LDIF_COULD_NOT_BASE64_DECODE_DN
public static LocalizableMessageDescriptor.Arg3<Number,Object, ERR_LDIF_COULD_NOT_BASE64_DECODE_DNObject> Unable to parse LDIF entry starting at line %d because it was not possible to base64-decode the DN on line "%s": %s -
ERR_LDIF_COULD_NOT_BASE64_DECODE_ATTR
public static LocalizableMessageDescriptor.Arg4<Object,Number, ERR_LDIF_COULD_NOT_BASE64_DECODE_ATTRObject, Object> Unable to parse LDIF entry %s starting at line %d because it was not possible to base64-decode the attribute on line "%s": %s -
WARN_LDIF_DUPLICATE_ATTR
public static LocalizableMessageDescriptor.Arg4<Object,Number, WARN_LDIF_DUPLICATE_ATTRObject, Object> Entry %s read from LDIF starting at line %d includes a duplicate attribute %s with value %s. The second occurrence of that attribute value has been skipped -
ERR_LDIF_MULTIPLE_VALUES_FOR_SINGLE_VALUED_ATTR
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_LDIF_MULTIPLE_VALUES_FOR_SINGLE_VALUED_ATTRObject> Entry %s starting at line %d includes multiple values for single-valued attribute %s -
ERR_LDIF_SCHEMA_VIOLATION
Entry %s read from LDIF starting at line %d is not valid because it violates the server's schema configuration: %s -
ERR_LDIF_FILE_EXISTS
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 -
ERR_LDIF_INVALID_URL
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 -
ERR_LDIF_URL_IO_ERROR
public static LocalizableMessageDescriptor.Arg5<Object,Number, ERR_LDIF_URL_IO_ERRORObject, Object, Object> 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 -
ERR_REJECT_FILE_EXISTS
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 -
ERR_LDIF_COULD_NOT_EVALUATE_FILTERS_FOR_IMPORT
public static LocalizableMessageDescriptor.Arg3<Object,Number, ERR_LDIF_COULD_NOT_EVALUATE_FILTERS_FOR_IMPORTObject> 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 -
ERR_EMAILMSG_INVALID_SENDER_ADDRESS
The provided sender address %s is invalid: %s -
ERR_EMAILMSG_INVALID_RECIPIENT_ADDRESS
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EMAILMSG_INVALID_RECIPIENT_ADDRESSThe provided recipient address %s is invalid: %s -
ERR_EMAILMSG_CANNOT_SEND
The specified e-mail message could not be sent using any of the configured mail servers -
ERR_LDAPURL_NO_COLON_SLASH_SLASH
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 -
ERR_LDAPURL_NO_SCHEME
The provided string "%s" cannot be decoded as an LDAP URL because it does not contain a protocol scheme -
ERR_LDAPURL_NO_HOST
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 -
ERR_LDAPURL_NO_PORT
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 -
ERR_LDAPURL_CANNOT_DECODE_PORT
The provided string "%s" cannot be decoded as an LDAP URL because the port number portion %s cannot be decoded as an integer -
ERR_LDAPURL_INVALID_PORT
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 -
ERR_LDAPURL_INVALID_SCOPE_STRING
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 -
ERR_LDAPURL_PERCENT_TOO_CLOSE_TO_END
The provided URL component "%s" could not be decoded because the percent character at byte %d was not followed by two hexadecimal digits -
ERR_LDAPURL_INVALID_HEX_BYTE
The provided URL component "%s" could not be decoded because the character at byte %d was not a valid hexadecimal digit -
ERR_CHARSET_NO_COLON
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 -
ERR_CHARSET_CONSTRUCTOR_NO_NAME
The named character set is invalid because it does not contain a name -
ERR_CHARSET_CONSTRUCTOR_INVALID_NAME_CHAR
public static LocalizableMessageDescriptor.Arg2<Object,Number> ERR_CHARSET_CONSTRUCTOR_INVALID_NAME_CHARThe 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 -
ERR_CHARSET_NO_NAME
Cannot decode value "%s" as a named character set because it does not contain a name to use for the character set -
ERR_CHARSET_NO_CHARS
Cannot decode value "%s" as a named character set because there are no characters to include in the set -
INFO_TIME_IN_SECONDS
%d seconds -
INFO_TIME_IN_MINUTES_SECONDS
%d minutes, %d seconds -
INFO_TIME_IN_HOURS_MINUTES_SECONDS
public static LocalizableMessageDescriptor.Arg3<Number,Number, INFO_TIME_IN_HOURS_MINUTES_SECONDSNumber> %d hours, %d minutes, %d seconds -
INFO_TIME_IN_DAYS_HOURS_MINUTES_SECONDS
public static LocalizableMessageDescriptor.Arg4<Number,Number, INFO_TIME_IN_DAYS_HOURS_MINUTES_SECONDSNumber, Number> %d days, %d hours, %d minutes, %d seconds -
ERR_FILEPERM_SET_NO_SUCH_FILE
Unable to set permissions for file %s because it does not exist -
ERR_FILEPERM_SET_JAVA_EXCEPTION
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 -
ERR_FILEPERM_INVALID_UNIX_MODE_STRING
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 -
WARN_LDIF_VALUE_VIOLATES_SYNTAX
public static LocalizableMessageDescriptor.Arg5<Object,Number, WARN_LDIF_VALUE_VIOLATES_SYNTAXObject, Object, Object> Entry %s read from LDIF starting at line %d includes value "%s" for attribute %s that is invalid according to the associated syntax: %s -
ERR_SKIP_FILE_EXISTS
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 -
ERR_LDIF_SKIP
Skipping entry %s because the DN is not one that should be included based on the include and exclude branches/filters -
ERR_EMBEDUTILS_SERVER_ALREADY_RUNNING
The embedded server with server root '%s' cannot be started because it is already running -
ERR_LDIF_SKIP_EXCLUDE_BRANCH
Skipping entry %s because the DN is excluded by the exclude branch "%s" -
ERR_LDIF_SKIP_EXCLUDE_FILTER
Skipping entry %s because the DN is excluded by the exclude filter "%s" -
ERR_LDIF_SKIP_NOT_IN_INCLUDED_BRANCHES
Skipping entry %s because the DN is not included by any include branches -
ERR_LDIF_SKIP_NOT_IN_INCLUDED_FILTERS
Skipping entry %s because the DN is not included by any include filters -
ERR_LDIF_REJECTED_BY_PLUGIN_NOMESSAGE
Rejecting entry %s because it was rejected by a plugin -
ERR_LDIF_REJECTED_BY_PLUGIN
Rejecting entry %s because it was rejected by a plugin: %s -
ERR_LDIF_INVALID_ATTR_OPTION
Unable to parse LDIF entry %s starting at line %d because it has an invalid binary option for attribute %s -
ERR_LDIF_READ_ATTR_SKIP
Skipping entry %s because the following error was received when reading its attributes: %s -
ERR_BACKUP_CANNOT_LIST_LOG_FILES
An error occurred while attempting to obtain a list of the files in directory %s to include in the backup: %s -
ERR_EMBEDDED_SERVER_SETUP_EXTRACT_ARCHIVE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_EMBEDDED_SERVER_SETUP_EXTRACT_ARCHIVEObject> An error occurred while attempting to extract server archive '%s' before setup of embedded server with server root '%s': %s -
ERR_EMBEDDED_SERVER_REBUILD_INDEX_FAILURE
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EMBEDDED_SERVER_REBUILD_INDEX_FAILUREAn error occurred while attempting to rebuild index of embedded server with server root '%s': %s -
ERR_EMBEDDED_SERVER_START
An error occurred while attempting to start the embedded server with server root '%s' : %s -
ERR_EMBEDDED_SERVER_UPGRADE
An error occurred while attempting to upgrade the embedded server with server root '%s' : %s -
ERR_EMBEDDED_SERVER_INTERNAL_CONNECTION
An error occurred while attempting to retrieve an internal connection to the server with the user DN '%s' -
ERR_EMBEDDED_SERVER_ARCHIVE_SETUP_WRONG_ROOT_DIRECTORY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EMBEDDED_SERVER_ARCHIVE_SETUP_WRONG_ROOT_DIRECTORYThe 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' -
ERR_EMBEDDED_SERVER_LDIF_MANAGEMENT_CONTEXT
An error occurred while attempting to initialize the configuration framework or to read the configuration file '%s' -
ERR_EMBEDDED_SERVER_IMPORT_DATA_NOT_SUCCESSFUL
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_EMBEDDED_SERVER_IMPORT_DATA_NOT_SUCCESSFULObject> 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 -
ERR_EMBEDDED_SERVER_IMPORT_DATA_FAILURE
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_EMBEDDED_SERVER_IMPORT_DATA_FAILUREObject> An error occurred while attempting to import LDIF file '%s' into embedded server with server root '%s': '%s' -
ERR_EMBEDDED_SERVER_REBUILD_INDEX_NOT_SUCCESSFUL
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EMBEDDED_SERVER_REBUILD_INDEX_NOT_SUCCESSFULAn 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 -
ERR_EMBEDDED_SERVER_CONFIG_VERSION
An error occurred while attempting to retrieve the configuration version of the directory server: '%s' -
ERR_EMBEDDED_SERVER_DATA_VERSION
An error occurred while attempting to retrieve the data version of the directory server: '%s' -
ERR_EMBEDDED_SERVER_INITIALIZE_CONFIGURATION
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_EMBEDDED_SERVER_INITIALIZE_CONFIGURATIONAn error occurred while initializing configuration of embedded server with server root '%s': %s -
ERR_MOVEDIR_SOURCE_NOT_EXIST
The directory to move %s does not exist -
ERR_MOVEDIR_SOURCE_NOT_DIRECTORY
The directory to move %s exists but is a file -
ERR_MOVEDIR_TARGET_EXISTS
The target directory %s already exists -
ERR_EMBEDDED_SERVER_SETUP_REQUIRE_LDAP_OR_LDAPS_PORT
public static LocalizableMessageDescriptor.Arg0 ERR_EMBEDDED_SERVER_SETUP_REQUIRE_LDAP_OR_LDAPS_PORTConfiguration error: an LDAP port or an LDAPS port must be configured before finishing configuring the embedded server -
WARN_EMBEDDED_SERVER_NOT_FOR_PRODUCTION
Embedded Directory Servers are NOT SUPPORTED in production -
ERR_DIFFERENT_DATA_SET_NEED_RESYNC
public static LocalizableMessageDescriptor.Arg4<Object,Object, ERR_DIFFERENT_DATA_SET_NEED_RESYNCObject, Object> The Directory server DS(%s) and Replication server RS(%s) are working on different dataset regarding the domain '%s' : the Directory server DS(%s) will reject all modification operations and must be re-initialized -
ERR_SORT_UNINDEXED_SEARCH_INSUFFICIENT_PRIVILEGES
You do not have sufficient privileges to perform the sort request -
INFO_UPGRADE_TASK_RENAME_LOG_CONTROLS
Renaming 'ds-cfg-log-control-oids' attribute to 'ds-cfg-log-controls' -
INFO_UPGRADE_REMOVE_SNMP
Removing SNMP support -
INFO_DESCRIPTION_DSREPL_DR_SUBCMD
Performs disaster recovery on the local server. The subcommand has two forms. The first form verifies each replica has the same data after recovery: on a replica, run dsrepl disaster-recovery --baseDn dc=example,dc=com --generate-recovery-id The command prints the identifier to use on all other servers with the --generated-id option: dsrepl disaster-recovery --baseDn dc=example,dc=com --generated-id {identifier} The second form uses an identifier you provide. It lets you automate the recovery process when you cannot use the first form. Do not use this form if the topology has standalone replication servers. With this form of the subcommand, you must ensure you recover each replica with the same data. Run the same subcommand on all servers. Example: dsrepl disaster-recovery --baseDn dc=example,dc=com --user-generated-id Recovery_Date_20240101 Read the documentation on disaster recovery carefully before using this command -
INFO_DSREPL_GENERATE_DRID_DESCRIPTION
Generate a disaster recovery identifier during recovery. Use this for the first directory server in a replication topology with standalone RS servers. For all subsequent servers to recover, omit this option and use --generated-id {generatedRecoveryId} with the generated identifier -
INFO_DSREPL_GENERATED_DRID_DESCRIPTION
Use the disaster recovery identifier generated on the first server. You must use the same identifier for all servers involved in the same disaster recovery procedure -
ERROR_DSREPL_DR_MISSING_ARGUMENT
A mandatory argument is missing. Choose one and only one argument from '--generate-recovery-id', '--generated-id' and '--user-generated-id' -
INFO_DSREPL_DR_ID_PLACEHOLDER
{generatedRecoveryId} -
ERR_DSREPL_DR_INIT_NEED_DS
Disaster recovery must be started on a directory server or a combined directory/replication server -
ERR_DSREPL_DR_CANNOT_COMPUTE_DR_ID
An error occurred while computing the disaster recovery id for base DN '%s': %s -
INFO_DSREPL_DR_ENDED_SUCCESSFULLY
Disaster recovery for base DN '%s' ended successfully on this server -
INFO_DSREPL_DR_COMPUTED_ID_INTRO
The disaster recovery process completed successfully for the first server. The next step is to restore the same data using the same procedure on all the remaining servers in the topology and run the following command on each server: -
ERR_DSREPL_DR_BAD_DATA
The disaster recovery procedure cannot be continued on this server because the domain '%s' does not contain the expected data. Make sure the server has been restored using exactly the same procedure used on the first server -
ERR_DSREPL_DR_CANNOT_REWRITE_BASE_DN
An error occurred while rewriting the base entry of the domain '%s'. This server will not be able to connect to the servers which already have received the disaster recovery procedure. Make sure the filesystem is writeable and there is some free disk space, and try again. The error is: %s -
ERR_DSREPL_DR_CANNOT_CLEAR_CHANGELOG
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_DR_CANNOT_CLEAR_CHANGELOGObject> An error occurred while clearing the changelog for the domain '%s'. This server will not be able to connect to the servers which have already completed the disaster recovery procedure. Make sure the filesystem at '%s' is readable with delete permissions and try again. The error is: %s -
ERR_DSREPL_DR_CANNOT_REWRITE_REPLICATION_DATA
public static LocalizableMessageDescriptor.Arg3<Object,Object, ERR_DSREPL_DR_CANNOT_REWRITE_REPLICATION_DATAObject> An error occurred while rewriting replication data for the domain '%s'. This server will not be able to connect to the servers which already have received the disaster recovery procedure. Make sure the filesystem at %s is writeable and there is some free disk space and try again. The error is: %s -
ERR_DSREPL_DR_CANNOT_CLEAR_CNI
An error occurred while clearing the change number index. The change number index on this server will expose erroneous data. Make sure the filesystem at '%s' is readable with delete permissions and try again. The error is: %s -
ERR_DSREPL_DR_WRONG_SERVER
The server is neither a replica nor a replication server for base DN '%s' -
ERR_DSREPL_DR_FAILED
Disaster recovery for base DN '%s' failed on this server -
WARN_DSREPL_DR_UNKNOWN_DOMAIN_FOR_RS
The local replication server never received changes for base DN '%s'. Make sure you are running the disaster recovery on the right server -
INFO_DSREPL_DR_BASE_DN_DESCRIPTION
Base DN of the domain to be recovered -
ERR_DSREPL_DR_INVALID_ID
The disaster recovery id '%s' is invalid. Verify the value of the disaster recovery id parameter matches the value printed when '--generate-recovery-id' was run on the first server -
ERR_DSREPL_DOMAIN_DR_ID_INCONSISTENCY
public static LocalizableMessageDescriptor.Arg2<Object,Object> ERR_DSREPL_DOMAIN_DR_ID_INCONSISTENCYThe provided base DN '%s' does not match the disaster recovery id '%s'. Please verify that the base DN and disaster recovery id correspond to the base DN and id from the first recovered server -
INFO_DSREPL_DR_STARTED
Starting disaster recovery on local server for base DN '%s' -
ERR_DSREPL_CANNOT_DELETE_CNI_FILE
The replication changelog file '%s' could not be deleted. Check file permissions and filesystem status. The error is: %s -
ERR_DSREPL_CANNOT_LIST_CNI_FILES
The replication changelog files could not be retrieved. Check file permissions and filesystem status. The error is: %s -
INFO_DSREPL_INIT_ASK_CONFIRMATION_INTRO
Disaster recovery will erase replication metadata on this server. This server will then only be able to replicate changes with other recovered servers. You will have to run the recovery procedure on every other server of the topology. Servers which have not been recovered will not be able to connect to recovered servers anymore -
INFO_DSREPL_INIT_ASK_CONFIRMATION
Continue the disaster recovery procedure -
INFO_DSREPL_DR_COMPUTED_ID_FULL_COMMAND
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_DSREPL_DR_COMPUTED_ID_FULL_COMMANDdsrepl disaster-recovery --baseDn '%s' --generated-id %s -
INFO_DSREPL_DR_COMPUTED_ID_NO_PROMPT
Disaster recovery id: %s -
INFO_DSREPL_DR_CANCELED_PROCESS
The disaster recovery process has been canceled, no operation was performed. This server may still not be operational -
INFO_DESCRIPTION_SUBCMD_DECODE_CSN
Decodes one or more CSNs and displays them in a human readable JSON format -
INFO_DSREPL_CSN_PLACEHOLDER
csn [csn ...] -
ERR_DSREPL_DECODE_CSN_INVALID_CSN
The CSN cannot be parsed as a valid CSN -
ERROR_UPGRADE_FROM_INCOMPATIBLE_7_4_0
The current 7.4.0 server is configured to use an incompatible confidentiality setting which prevents automated upgrade from working. Follow the procedure detailed in the Upgrade Guide to upgrade this server -
WARN_PEER_REPLICA_IS_TOO_LATE
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_PEER_REPLICA_IS_TOO_LATEObject, Object> Peer replica '%s' is too late compared to changelog '%s' for domain '%s'. It asked for changes that are not present in the changelog or have been purged. The peer replica will no longer receive replicated changes and must be re-initialized. Diagnostic information follows: %s -
WARN_REPLICA_NEWEST_CSN_IS_NO_LONGER_IN_REPLICA_DB
Peer replica asked for changes from replica '%1$s' starting from %2$s (CSN '%3$s'), but changelog DB only contains changes starting from %4$s (CSN '%5$s'). The last recorded purge information in 'domains.state' is: last update CSN: %6$s, last message CSN: %7$s. The replica DB description is: number of files: %8$d, replica offline: %9$b. The replica DB newest file content is: oldest CSN: %10$s, newest CSN: %11$s, number of updates: %12$d, number of ReplicaOfflineMsg: %13$d -
WARN_REPLICA_NEWEST_CSN_IS_OLDER_THAN_RECORDED_PURGED_CSNS
public static LocalizableMessageDescriptor.Arg7<Object,Object, WARN_REPLICA_NEWEST_CSN_IS_OLDER_THAN_RECORDED_PURGED_CSNSObject, Object, Object, Object, Object> Peer replica asked for changes from replica '%s' starting from %s (CSN '%s'), but the changelog DB has purged this change, and the last known generated change timestamp is %s (CSN '%s'). The last recorded purge information in 'domains.state' is: last update CSN: %s, last message CSN: %s -
WARN_REPLICA_NEWEST_CSN_IS_OLDER_THAN_OLDEST_CSN_IGNORING_RECORDED_STATE
public static LocalizableMessageDescriptor.ArgN WARN_REPLICA_NEWEST_CSN_IS_OLDER_THAN_OLDEST_CSN_IGNORING_RECORDED_STATEPeer replica asked for changes from replica '%1$s' starting from %2$s (CSN '%3$s'), but changelog DB only contains changes starting from %4$s (CSN '%5$s'). The administrator explicitly decided to ignore the recorded purge information in 'domains.state' by setting the 'org.forgerock.opendj.allowReplicaPastPurgeDelay' system property to 'true'. The replica DB description is: number of files: %6$d, replica offline: %7$b. The replica DB newest file content is: oldest CSN: %8$s, newest CSN: %9$s, number of updates: %10$d, number of ReplicaOfflineMsg: %11$d -
ERR_DSREPL_DR_INVALID_VERSION
The provided disaster recovery id had version %d, but only version 1 is supported. Verify the value of the disaster recovery id parameter matches the value printed when '--generate-recovery-id' was run on the first server -
WARN_REPLICATION_DOMAIN_STATUS_NOT_HEALTHY
public static LocalizableMessageDescriptor.Arg2<Object,Object> WARN_REPLICATION_DOMAIN_STATUS_NOT_HEALTHYReplication domain '%s' status '%s' is not healthy -
INFO_UPGRADE_TASK_PROMETHEUS_COMPLIANT_FORMAT
Updating existing Prometheus endpoints to keep using the legacy format -
WARN_DEPRECATED_PROPERTY
public static LocalizableMessageDescriptor.Arg4<Object,Object, WARN_DEPRECATED_PROPERTYObject, Object> Property '%s' in %s '%s' is DEPRECATED for removal since %s. Its usage is highly discouraged -
WARN_LEGACY_PROPERTY
Property '%s' in %s '%s' is LEGACY since %s. Its usage is highly discouraged -
ERR_DR_NO_DATA_IN_BACKEND
There is no data in domain '%s' to run disaster recovery on -
INFO_DSREPL_USER_GENERATED_ID_DESCRIPTION
Set the identifier for this recovery to {userGeneratedRecoveryId}, a string of your choice. Do not use this option if the replication topology has standalone RS servers. You must use the same identifier for all servers involved in the same disaster recovery procedure. -
INFO_DSREPL_USER_GENERATED_ID_PLACEHOLDER
{userGeneratedRecoveryId} -
ERR_DSREPL_DR_WITH_VERSION_NEED_DS
Base Dn '%s' is not a replicated domain on this server. Disaster recovery must be run on a directory server or a combined directory/replication server -
INFO_DSREPL_DR_WITH_VERSION_ALREADY_RUN
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_DSREPL_DR_WITH_VERSION_ALREADY_RUNDisaster recovery for domain '%s' has already been run with recovery ID '%s'. Verify all servers in the topology are being recovered with the same recovery ID -
WARN_DECODING_REPLICATED_REQUEST_CONTROL
An error occurred while decoding a replicated request control: %s -
WARN_DECODING_INTERNAL_MODIFICATION_CONTROL
An error occurred while decoding a internal modification control: %s -
INFO_UPGRADE_ADD_HDAP_AUTH_MECHANISM_CONFIG
Add a new HDAP authorization mechanism '%s' -
INFO_UPGRADE_REPLACE_HDAP_ENDPOINT_AUTH_MECHANISM_CONFIG
public static LocalizableMessageDescriptor.Arg2<Object,Object> INFO_UPGRADE_REPLACE_HDAP_ENDPOINT_AUTH_MECHANISM_CONFIGReplace the authentication mechanism of the '/hdap' endpoint '%s' with the new HDAP authorization mechanism '%s' -
INFO_UPGRADE_DELETE_HTTP_AUTH_MECHANISMS_CONFIG
public static LocalizableMessageDescriptor.Arg1<Object> INFO_UPGRADE_DELETE_HTTP_AUTH_MECHANISMS_CONFIGRemoving deprecated HTTP Basic DN and JWT authorization mechanisms. The HDAP authorization mechanism '%s' replaces them -
ERR_REQUEST_DN_DOES_NOT_EXIST
The entry '%s' specified in the request does not exist in the Directory Server -
ERR_SEARCH_CANNOT_MIX_PAGING_AND_PERSISTENT_SEARCHES
public static LocalizableMessageDescriptor.Arg0 ERR_SEARCH_CANNOT_MIX_PAGING_AND_PERSISTENT_SEARCHESThe requested search operation included the persistent search control together with either the simple paged results control or the virtual list view control. These controls are mutually exclusive and cannot be used together -
WARN_USING_VIRTUAL_THREADS
EXPERIMENTAL virtual threads support has been enabled. DO NOT USE in production -
DSBACKUP_ERROR_RESTORE_READING_BACKUP_LIST
Cannot continue the restore process, errors were encountered while reading the list of available backups: %s -
DSBACKUP_ERROR_PURGE_READING_BACKUP_LIST
Cannot continue purging backups, errors were encountered while reading the list of available backups: %s -
ERR_DEPRECATED_DR_TOOLS_USAGE
This server received a replication message to signal a disaster recovery. This means that this server is part of a mixed topology where the deprecated start-disaster-recovery command is used. The operation will continue, but it is not supported anymore and the disaster recovery procedure for mixed topologies must be used instead. -
INFO_DSREPL_STATUS_HEADING_HOSTNAME
Hostname
-
-
Method Details
-
resourceName
Returns the name of the resource associated with the messages contained in this class. The resource name may be used for obtaining named loggers, e.g. using SLF4J'sorg.slf4j.LoggerFactory#getLogger(String name).- Returns:
- The name of the resource associated with the messages contained in this class.
-