Uses of Class
org.forgerock.i18n.LocalizableMessageDescriptor.Arg1
Packages that use LocalizableMessageDescriptor.Arg1
Package
Description
This package provides an alternative localization mechanism to
org.slf4j.cal10n.APIs for implementing REST to LDAP gateways.
Defines all the messages that may be used in the Directory Server and tools.
Contains implementations for a number of Directory Server data types.
Contains implementations for various Directory Server utility classes and methods which may be used throughout the
server but do not necessarily fit in elsewhere.
-
Uses of LocalizableMessageDescriptor.Arg1 in org.forgerock.i18n.slf4j
Methods in org.forgerock.i18n.slf4j with parameters of type LocalizableMessageDescriptor.Arg1Modifier and TypeMethodDescription<T1> voidLocalizedLogger.error(LocalizableMessageDescriptor.Arg1<T1> d, T1 a1) Logs an error message.<T1> voidLocalizedLogger.info(LocalizableMessageDescriptor.Arg1<T1> d, T1 a1) Logs a message at INFO level.<T1> voidLocalizedLogger.note(LocalizableMessageDescriptor.Arg1<T1> d, T1 a1) Logs a message at NOTICE level.<T1> voidLocalizedLogger.warn(LocalizableMessageDescriptor.Arg1<T1> d, T1 a1) Logs a warning message. -
Uses of LocalizableMessageDescriptor.Arg1 in org.forgerock.opendj.rest2ldap
Fields in org.forgerock.opendj.rest2ldap declared as LocalizableMessageDescriptor.Arg1Modifier and TypeFieldDescriptionRest2ldapMessages.ERR_ACTION_NOT_SUPPORTEDThe action '%s' is not supportedRest2ldapMessages.ERR_ARRAY_FOR_SINGLE_VALUED_FIELDThe request cannot be processed because an array of values was provided for the single valued field '%s'Rest2ldapMessages.ERR_AUTHZID_DECODER_PRINCIPAL_CANNOT_BE_DETERMINEDThe request could not be authorized because the required security principal '%s' could not be determinedRest2ldapMessages.ERR_AUTHZID_DECODER_PRINCIPAL_INVALID_DATA_TYPEThe request could not be authorized because the required security principal '%s' had an invalid data typeRest2ldapMessages.ERR_CONFIG_INVALID_LDAP_SERVERS'%s' configuration must contain a json arrayRest2ldapMessages.ERR_CONFIG_NO_MAPPING_IN_CONFIGURATIONUnknown mapping. The configuration mapping must be one of '%s'Rest2ldapMessages.ERR_CONFIG_OAUTH2_CACHE_INVALID_DURATIONMalformed duration value '%s' for cache expiration. The duration syntax supports all human readable notations from day ('days'', 'day'', 'd'') to nanosecond ('nanoseconds', 'nanosecond', 'nanosec', 'nanos', 'nano', 'ns')Rest2ldapMessages.ERR_CONFIG_SERVER_CIRCULAR_DEPENDENCIESThe LDAP server configuration '%s' could not be parsed because of potential circular inheritance dependenciesRest2ldapMessages.ERR_CONFIGURE_REFERENCE_PROPERTY_MAPPER_WITH_OBJECT_PROPERTY_MAPPERA reference property mapper can only be configured with an object property mapper. Got a %s property mapper instead.Rest2ldapMessages.ERR_CREATION_READ_ONLY_FIELDThe create request cannot be processed because it attempts to create the read-only field '%s'Rest2ldapMessages.ERR_DECODING_CONTROLUnable to decode ldap control: '%s'Rest2ldapMessages.ERR_FAIL_PARSE_CONFIGURATIONUnable to start Rest2Ldap Http Application due to the configuration error: '%s'Rest2ldapMessages.ERR_FIELD_WRONG_TYPEThe request cannot be processed because it included the field '%s' whose value is the wrong type: an object is expectedRest2ldapMessages.ERR_HDAP_DIGEST_MECHANISM_NOT_SUPPORTEDThe algorithm '%s' is not supported as a digest mechanismRest2ldapMessages.ERR_HDAP_JWT_CLAIM_HAS_EXPIREDThe given JWT claim '%s' timestamp has expiredRest2ldapMessages.ERR_HDAP_JWT_CLAIM_INVALID_FORMATThe given JWT claim '%s' has not a valid formatRest2ldapMessages.ERR_HDAP_JWT_CLAIM_IS_IN_FUTUREThe given JWT claim '%s' timestamp should happen before the current datetimeRest2ldapMessages.ERR_HDAP_JWT_CLAIM_IS_MISSING_OR_IS_EMPTYThe given JWT misses the claim '%s' or is emptyRest2ldapMessages.ERR_HDAP_JWT_INVALID_BEARER_TOKENInvalid bearer token '%s'Rest2ldapMessages.ERR_HDAP_JWT_KEYSTORE_ACCESS_EXCEPTIONAn error occured while retrieving the keystore: %sRest2ldapMessages.ERR_HDAP_JWT_KEYSTORE_REFRESH_FAILRefreshing the keystore failed: %sRest2ldapMessages.ERR_HDAP_MALFORMED_RESOURCE_PATHMalformed RDN in resource path '%s'Rest2ldapMessages.ERR_INVALID_AUXILIARY_TYPE_PROPERTY_IN_CREATEThe resource cannot be created because the auxiliary type property '%s' is not an array containing a list of auxiliary typesRest2ldapMessages.ERR_INVALID_ENDPOINT_DIRECTORYThe endpoint configuration directory '%s' either does not exist, is not a directory or cannot be readRest2ldapMessages.ERR_INVALID_ENDPOINTS_DIRECTORYThe endpoints configuration directory '%s' either does not exist, is not a directory or cannot be readRest2ldapMessages.ERR_INVALID_JSON_BOOLEANCould not parse the JSON value '%s' as a booleanRest2ldapMessages.ERR_INVALID_JSON_INTEGERCould not parse the JSON value '%s' as an integerRest2ldapMessages.ERR_INVALID_JSON_ISO_8601Could not parse the JSON value '%s' as an ISO 8601 date and timeRest2ldapMessages.ERR_JSON_IO_ERRORThe value could not be parsed as valid JSON: %sRest2ldapMessages.ERR_JSON_QUERY_PARSE_ERRORThe value '%s' could not be parsed as a valid JSON query filterRest2ldapMessages.ERR_LOCAL_SORT_PAGE_SIZEThe query request cannot be processed because this sort directive requires the page size to be set to a value between 1 and %d.Rest2ldapMessages.ERR_MISSING_REQUIRED_FIELDThe create request cannot be processed because it does not include the required field '%s'Rest2ldapMessages.ERR_MISSING_TYPE_PROPERTY_IN_CREATEThe resource cannot be created because it does not contain the type property '%s'Rest2ldapMessages.ERR_MVCC_NO_VERSION_INFORMATIONThe resource could not be accessed because it did not contain any version information, when the version '%s' was expectedRest2ldapMessages.ERR_MVCC_VERSIONS_MISMATCH_UNKNOWN_CURRENT_VERSIONThe resource could not be accessed because the expected version '%s' does not match the current versionRest2ldapMessages.ERR_NAME_AND_JSON_SYNTAX_COULD_NOT_PARSE_VALUE_OF_UNDERSCORE_IDThe value of the key '_id' of '%s' could not be parsedRest2ldapMessages.ERR_NAME_AND_JSON_SYNTAX_MISSING_JSONThe value '%s' does not contain any JSONRest2ldapMessages.ERR_NAME_AND_JSON_SYNTAX_MISSING_UNDERSCORE_IDThe '_id' key is required in the JSON '%s'Rest2ldapMessages.ERR_NO_ARRAY_FOR_MULTI_VALUED_FIELDThe request cannot be processed because an array of values was not provided for the multi-valued field '%s'Rest2ldapMessages.ERR_OAUTH2_CTS_INVALID_JSON_TOKENJson of token '%s' is malformedRest2ldapMessages.ERR_OAUTH2_FILE_NO_TOKENUnable to find token file '%s'Rest2ldapMessages.ERR_PAGE_SIZE_LIMIT_REACHEDThe query request cannot be processed because this request requires the page size to be set to a value between 1 and %d.Rest2ldapMessages.ERR_PATCH_ADD_NO_VALUE_FOR_FIELDThe patch request cannot be processed because it included an add patch operation but no value(s) for field '%s'Rest2ldapMessages.ERR_PATCH_APPEND_IN_SINGLE_VALUED_FIELDThe patch request cannot be processed because it attempts to append a value to the single valued field '%s'Rest2ldapMessages.ERR_PATCH_INDEXED_APPEND_TO_MULTI_VALUED_FIELDThe patch request cannot be processed because it attempts to perform an indexed append of an array of values to the multi-valued field '%s'Rest2ldapMessages.ERR_PATCH_INDEXED_OPERATIONThe patch request cannot be processed because it included an indexed patch operation '%s' which is not supported by this resource providerRest2ldapMessages.ERR_PATCH_READ_ONLY_FIELDThe patch request cannot be processed because it attempts to patch the read-only field '%s'Rest2ldapMessages.ERR_PATCH_UNSUPPORTED_OPERATIONThe patch request cannot be processed because it included an unsupported type of patch operation '%s'Rest2ldapMessages.ERR_PRIMARY_KEY_NOT_FOUNDThe reference property mapper for property "%s" references a resource type that does not have an "_id" fieldRest2ldapMessages.ERR_QUERY_SORT_KEY_NOT_SUPPORTEDThe query request cannot be processed because it included an unrecognized sort key '%s'Rest2ldapMessages.ERR_REFERENCE_FIELD_MULTIPLE_PRIMARY_KEYSThe request cannot be processed because the reference field '%s' contains a value which contains multiple primary keysRest2ldapMessages.ERR_REFERENCE_FIELD_NO_PRIMARY_KEYThe request cannot be processed because the reference field '%s' contains a value which does not contain a primary keyRest2ldapMessages.ERR_RESOURCE_NOT_FOUNDResource '%s' not foundRest2ldapMessages.ERR_RESOURCE_REFERENCE_CANNOT_RESOLVE_TEMPLATE_VARIABLECannot resolve the referenced base DN for the resource path '%s' because it contains a template variable. To avoid this problem, change the rest2ldap configuration by removing the template variable from the resource pathRest2ldapMessages.ERR_SCHEMA_NEEDS_TWO_COMPONENTSThe schema request must be either 'attributeTypes/{type}' or 'objectClasses/{class}' instead of '%s'Rest2ldapMessages.ERR_TOO_MANY_ENTRIES_FOUNDThe query request cannot be processed because the number of resources found exceeded the limit of %d.Rest2ldapMessages.ERR_UNRECOGNIZED_FIELDThe request cannot be processed because it included an unrecognized field '%s'Rest2ldapMessages.ERR_UNRECOGNIZED_JSON_VALUEUnrecognized type of JSON value: '%s'Rest2ldapMessages.INFO_HDAP_STARTINGHDAP starting with configuration '%s'Rest2ldapMessages.INFO_REST2LDAP_STARTINGRest2Ldap starting with configuration directory '%s' -
Uses of LocalizableMessageDescriptor.Arg1 in org.opends.messages
Fields in org.opends.messages declared as LocalizableMessageDescriptor.Arg1Modifier and TypeFieldDescriptionServerMessages.DS_BACKUP_PLUGIN_NOT_FOUNDNo plugin found to handle the storage scheme '%s'ServerMessages.DSBACKUP_ACCESS_DENIEDAccess denied to file '%s'ServerMessages.DSBACKUP_BACKEND_FILES_REMOVED_AFTER_RESTORE_FAILUREThe '%s' backend files have been removed after restore failed. The backend is now emptyServerMessages.DSBACKUP_BACKUP_ID_ALREADY_EXISTSThe backup ID '%s' already existsServerMessages.DSBACKUP_BACKUP_STARTSStarting backup for backend '%s'ServerMessages.DSBACKUP_BACKUPS_DO_NOT_EXISTCannot find backup with ID %sServerMessages.DSBACKUP_CANNOT_DELETE_CORRUPTED_FILECannot delete corrupted file '%s'ServerMessages.DSBACKUP_CANNOT_FIND_BACKUP_FOR_BACKENDSThere are no backups for backends %sServerMessages.DSBACKUP_CANNOT_READ_BACKUP_DIRECTORY_CONTENTCannot read backup directory content: %sServerMessages.DSBACKUP_CANNOT_RESTORE_ONLINEThe backends %s cannot be restored while the server is running. Please stop the server first and try again with the --offline optionServerMessages.DSBACKUP_DIRECTORY_INVALID_NAME'%s' is not a valid name for a directoryServerMessages.DSBACKUP_ERROR_PURGE_READING_BACKUP_LISTCannot continue purging backups, errors were encountered while reading the list of available backups: %sServerMessages.DSBACKUP_ERROR_RESTORE_READING_BACKUP_LISTCannot continue the restore process, errors were encountered while reading the list of available backups: %sServerMessages.DSBACKUP_FILE_IS_MISSINGFile '%s' is missingServerMessages.DSBACKUP_IO_EXCEPTIONIO error: %sServerMessages.DSBACKUP_LIST_BACKEND_NAMEBackend name: %sServerMessages.DSBACKUP_LIST_BACKUP_IDBackup ID: %sServerMessages.DSBACKUP_LIST_BACKUPS_CANNOT_BE_RESTORED%s backup(s) cannot be restoredServerMessages.DSBACKUP_LIST_DATEBackup Date: %sServerMessages.DSBACKUP_LIST_ERRORError: %sServerMessages.DSBACKUP_LIST_ERROR_UNIDENTIFIED_BACKUPSFound %s backup(s) that cannot be fully identified due to the following error(s):ServerMessages.DSBACKUP_LIST_NUMBER_OF_BACKUPS_WITH_REQUESTED_PROPERTIESFound %s backup(s) with the requested characteristicsServerMessages.DSBACKUP_LIST_SERVER_IDServer ID: %sServerMessages.DSBACKUP_LIST_STATUSStatus: %sServerMessages.DSBACKUP_PURGE_AT_LEAST_ONE_ARG_PRESENTAt least one of these options must be declared: %sServerMessages.DSBACKUP_PURGE_FORCE_OLDER_THAN_DESCRIPTIONMust be used with the '--%s' option, indicates that the last backup of each backend can be deleted if older than the provided durationServerMessages.DSBACKUP_PURGE_KEEPCOUNT_ARG_ILLEGAL_VALUE'%d' is not allowed: the value must be equal or greater than 0ServerMessages.DSBACKUP_PURGE_OLDER_THAN_DESCRIPTIONDelete 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'ServerMessages.DSBACKUP_RESTORE_AMBIGUOUS_BACKUP_IDFound backup IDs that correspond to the same backend name: %s. Make sure each backup ID corresponds to a distinct backendServerMessages.DSBACKUP_RESTORE_NO_BACKENDS_WITH_NAMEThe backends %s cannot be restored because they do not exist or are disabledServerMessages.DSBACKUP_UNABLE_TO_ACCESS_BACKUP_STORAGEUnable to access the backup storage: %sServerMessages.ERR_ADD_ASSERTION_FAILEDEntry %s cannot be added because the request contained an LDAP assertion control and the associated filter did not match the contents of the provided entryServerMessages.ERR_ADD_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe entry %s cannot be added due to insufficient access rightsServerMessages.ERR_ADD_BACKEND_READONLYUnable to add entry %s because the backend that should hold that entry is configured in read-only modeServerMessages.ERR_ADD_CANNOT_LOCK_ENTRYEntry %s cannot be added because the server failed to obtain a write lock for this entry after multiple attemptsServerMessages.ERR_ADD_ENTRY_ALREADY_EXISTSThe entry '%s' cannot be added because an entry with that name already existsServerMessages.ERR_ADD_ENTRY_NOT_SUFFIXThe 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 ServerServerMessages.ERR_ADD_ENTRY_UNKNOWN_SUFFIXThe provided entry %s cannot be added because its suffix is not defined as one of the suffixes within the Directory ServerServerMessages.ERR_ADD_NO_SUCH_OBJECTThe entry '%s' cannot be added because its parent entry does not existServerMessages.ERR_ADD_SERVER_READONLYUnable to add entry %s because the Directory Server is configured in read-only modeServerMessages.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": %sServerMessages.ERR_ADMIN_DATA_TRUSTMANAGER_KEYSTORE_READ_FAILUREAn unexpected error occurred while accessing the instance keys in "cn=admin data": %sServerMessages.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 nameServerMessages.ERR_ATTR_SYNTAX_DN_ATTR_NO_NAMEThe provided value "%s" could not be parsed as a valid distinguished name because it contained an RDN containing an empty attribute nameServerMessages.ERR_ATTR_SYNTAX_DN_END_WITH_COMMAThe provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was a comma or semicolonServerMessages.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 digitServerMessages.ERR_ATTR_SYNTAX_DN_HEX_VALUE_TOO_SHORTThe 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 digitsServerMessages.ERR_ATTR_SYNTAX_DN_UNMATCHED_QUOTEThe 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 markServerMessages.ERR_ATTR_SYNTAX_SUBTREE_SPECIFICATION_INVALIDThe provided value "%s" could not be parsed as a valid subtree specificationServerMessages.ERR_ATTRIBUTE_INDEX_NOT_CONFIGUREDThere is no index configured for attribute type '%s'ServerMessages.ERR_BACKEND_CANNOT_LOCK_ENTRYThe 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 unlockedServerMessages.ERR_BACKEND_DEBUG_NO_BACKENDS_FOR_IDNone of the Directory Server JE backends are configured with the requested backend ID %sServerMessages.ERR_BACKEND_GET_ENTRY_NULLUnable to retrieve the requested entry from the "%s" backend because the provided DN was nullServerMessages.ERR_BACKEND_IMPORT_AND_EXPORT_NOT_SUPPORTEDLDIF import and export operations are not supported in the "%s" backendServerMessages.ERR_BACKEND_IMPORT_NOT_SUPPORTEDThe "%s" backend does not support LDIF import operationsServerMessages.ERR_BACKEND_TOOL_ERROR_LISTING_BASE_DNSAn error occurred while listing the base DNs: %sServerMessages.ERR_BACKEND_TOOL_ERROR_LISTING_TREESAn error occurred while listing indexes: %sServerMessages.ERR_BACKEND_TOOL_ERROR_READING_TREEAn unexpected error occurred while attempting to read and/or decode records from an index: %sServerMessages.ERR_BACKEND_TOOL_PROCESSING_ARGUMENTAn error occurred while processing arguments: %sServerMessages.ERR_BAD_HISTORICALEntry %s was containing some unknown historical information, This may cause some inconsistency for this entryServerMessages.ERR_BIND_ACCOUNT_TEMPORARILY_LOCKEDThe account has been locked as a result of too many failed authentication attempts (time to unlock: %s)ServerMessages.ERR_BIND_OPERATION_UNKNOWN_SASL_MECHANISMUnable to process the bind request because it attempted to use an unknown SASL mechanism %s that is not available in the Directory ServerServerMessages.ERR_BIND_OPERATION_WRITABILITY_DISABLEDRejecting 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 allowedServerMessages.ERR_BIND_UNSUPPORTED_CRITICAL_CONTROLUnable 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 operationServerMessages.ERR_CACHE_PRELOAD_NOT_SUPPORTEDBackend database cache preload for backend '%s' is not supported in this releaseServerMessages.ERR_CANNOT_CREATE_MBEAN_SERVERAn error occurred while attempting to create the JMX MBean server that will be used for monitoring, notification, and configuration interaction within the Directory Server: %sServerMessages.ERR_CANNOT_ENCODE_ENTRYCannot encode entry for writing on storage: %sServerMessages.ERR_CANNOT_GET_ROOT_DSE_CONFIG_ENTRYAn error occurred while trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) from the Directory Server configuration: %sServerMessages.ERR_CANNOT_INITIALIZE_BACKENDSAn error occurred while initializing server backends: %sServerMessages.ERR_CANNOT_INITIALIZE_CONFIGURATION_FRAMEWORKCannot initialize the configuration framework: %sServerMessages.ERR_CANNOT_INITIALIZE_CORE_CONFIGAn error occurred while trying to initialize the core Directory Server configuration: %sServerMessages.ERR_CANNOT_INITIALIZE_CRYPTO_MANAGERAn error occurred while attempting to initialize the crypto manager: %sServerMessages.ERR_CANNOT_INITIALIZE_PWPOLICYAn error occurred while attempting to initialize the password policy components: %sServerMessages.ERR_CANNOT_INITIALIZE_SERVER_COMPONENTSAn error occurred while attempting to initialize server components to run the tool: %sServerMessages.ERR_CANNOT_INITIALIZE_SERVER_PLUGINSAn error occurred while initializing plugins: %sServerMessages.ERR_CANNOT_INITIALIZE_STORAGE_SCHEMESAn error occurred while trying to initialize the Directory Server password storage schemes: %sServerMessages.ERR_CANNOT_INITIALIZE_SUBENTRY_MANAGERAn error occurred while attempting to initialize the subentry manager: %sServerMessages.ERR_CANNOT_LOAD_CONFIGAn error occurred while trying to load the Directory Server configuration: %sServerMessages.ERR_CANNOT_LOAD_SCHEMAAn error occurred while trying to load the Directory Server schema: %sServerMessages.ERR_CANNOT_SUBSYSTEM_NOT_INITIALIZEDSubsystem %s should be initialized firstServerMessages.ERR_CANNOT_VERIFY_CERTIFICATEReplication peer certificate verification failed with error: %sServerMessages.ERR_CHANGELOB_BACKEND_ERROR_ENABLING_CN_CHANGELOGError when enabling external changelog: %sServerMessages.ERR_CHANGELOG_BACKEND_CANNOT_CONVERT_TO_LONGCould not convert value '%s' to longServerMessages.ERR_CHANGELOG_BACKEND_CANNOT_FIND_UPDATECould not find replica update message matching the index record. No more replica update messages with a csn newer than %s existServerMessages.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 : %sServerMessages.ERR_CHANGELOG_CURSOR_ABORTED_CLEARCursor on log '%s' has been aborted after a clearServerMessages.ERR_CHANGELOG_CURSOR_ABORTED_PURGECursor on log '%s' has been aborted after a purgeServerMessages.ERR_CHANGELOG_DETECTED_CORRUPTED_FILEDetected 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 itServerMessages.ERR_CHANGELOG_ERROR_SENDING_ERRORAn unexpected error occurred while sending an Error Message to %s. This connection is going to be closed and reopenedServerMessages.ERR_CHANGELOG_ERROR_SENDING_MSGAn unexpected error occurred while sending a Message to %s. This connection is going to be closed and reopenedServerMessages.ERR_CHANGELOG_GENERATION_ID_WRONG_FORMATCould not read generation id because it uses a wrong format, expecting a number but got '%s'ServerMessages.ERR_CHANGELOG_MALFORMED_DOMAIN_STATE_FILESome 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 backupServerMessages.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'ServerMessages.ERR_CHANGELOG_STAT_CANNOT_CONVERT_FILENAME_TO_CNCannot convert the filename '%s' to a valid change numberServerMessages.ERR_CHANGELOG_STAT_CANNOT_CONVERT_FILENAME_TO_CSNCannot convert the filename '%s' to a valid CSNServerMessages.ERR_CHANGELOG_STAT_CANNOT_CREATE_OUTPUT_DIRThe output folder '%s' cannot be createdServerMessages.ERR_CHANGELOG_STAT_DOMAIN_NOT_FOUNDThe replication domain '%s' is not found. Make sure the domain is replicatedServerMessages.ERR_CHANGELOG_STAT_PROVIDED_CN_NOT_VALIDThe provided change number '%s' is not validServerMessages.ERR_CHANGELOG_STAT_PROVIDED_CSN_NOT_VALIDThe provided CSN '%s' is not validServerMessages.ERR_CHANGELOG_STAT_PROVIDED_DN_IS_INVALIDThe provided DN '%s' is invalidServerMessages.ERR_CHANGELOG_STAT_PROVIDED_FILE_DOESNT_EXISTThe provided output folder '%s' doesn't existServerMessages.ERR_CHANGELOG_STAT_REPLICA_FOLDER_NOT_FOUNDReplica DB folder '%s' not foundServerMessages.ERR_CHANGELOG_UNABLE_TO_DECODE_KEY_FROM_STRINGCould not decode the key from string [%s]ServerMessages.ERR_CHANGELOG_UNABLE_TO_DECODE_RECORDCould not decode a record from data read in log file '%s'ServerMessages.ERR_CHANGELOG_UNABLE_TO_DELETE_LAST_LOG_ROTATION_TIME_FILECould not delete file '%s' that stored the previous last log rotation timeServerMessages.ERR_CHANGELOG_UNABLE_TO_DELETE_LOG_FILECould not delete log files: %sServerMessages.ERR_CHANGELOG_UNABLE_TO_DELETE_LOG_FILE_WHILE_PURGINGWhile purging log, could not delete log file(s): '%s'ServerMessages.ERR_CHANGELOG_UNABLE_TO_RETRIEVE_FILE_LENGTHCould not retrieve file length of log file '%s'ServerMessages.ERR_CHANGELOG_UNREFERENCED_LOG_WHILE_RELEASINGThe following log '%s' must be released but it is not referencedServerMessages.ERR_CHANGENUMBER_DATABASEAn error occurred when accessing the change number database : %sServerMessages.ERR_CHARSET_NO_CHARSCannot decode value "%s" as a named character set because there are no characters to include in the setServerMessages.ERR_CHARSET_NO_COLONCannot decode value "%s" as a named character set because it does not contain a colon to separate the name from the set of charactersServerMessages.ERR_CHARSET_NO_NAMECannot decode value "%s" as a named character set because it does not contain a name to use for the character setServerMessages.ERR_CHARSET_VALIDATOR_ILLEGAL_CHARACTERThe provided password contained character '%s' which is not allowed for use in passwordsServerMessages.ERR_CHARSET_VALIDATOR_INVALID_RANGE_COUNTThe provided character range definition '%s' is invalid because the value before the colon must be an integer greater or equal to zeroServerMessages.ERR_CHARSET_VALIDATOR_INVALID_SET_COUNTThe provided character set definition '%s' is invalid because the value before the colon must be an integer greater or equal to zeroServerMessages.ERR_CHARSET_VALIDATOR_MIN_CHAR_SETS_TOO_BIGThe provided minimum required number of character sets '%d' is invalid because it is greater than the total number of defined character setsServerMessages.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 setsServerMessages.ERR_CHARSET_VALIDATOR_NO_RANGE_CHARSThe provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character rangeServerMessages.ERR_CHARSET_VALIDATOR_NO_RANGE_COLONThe provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character rangeServerMessages.ERR_CHARSET_VALIDATOR_NO_SET_CHARSThe provided character set definition '%s' is invalid because the provided character set is emptyServerMessages.ERR_CHARSET_VALIDATOR_NO_SET_COLONThe provided character set definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character setServerMessages.ERR_CHECK_CREATE_REPL_BACKEND_FAILEDAn unexpected error occurred when testing existence or creating the replication backend : %sServerMessages.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 neededServerMessages.ERR_CLEARTEXT_BACKEND_FOR_INDEX_CONFIDENTIALITYAttribute %s is set as confidential on a backend whose entries are still cleartext. Enable confidentiality on the backend firstServerMessages.ERR_COMMON_AUDIT_UNABLE_TO_PROCESS_LOG_EVENTError while processing a log event for common audit: %sServerMessages.ERR_COMMON_AUDIT_UNSUPPORTED_HANDLER_TYPEError while adding common audit log publisher %s, the publisher has an unsupported handler typeServerMessages.ERR_COMMON_AUDIT_UNSUPPORTED_LOG_PUBLISHERError while processing common audit log publisher %s, this type of log publisher is unsupportedServerMessages.ERR_COMPARE_ASSERTION_FAILEDCannot 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 entryServerMessages.ERR_COMPARE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe entry %s cannot be compared due to insufficient access rightsServerMessages.ERR_COMPARE_NO_SUCH_ENTRYThe specified entry %s does not exist in the Directory ServerServerMessages.ERR_COMPRESSEDSCHEMA_UNKNOWN_OC_TOKENUnable to decode the provided object class set because it used an undefined token %sServerMessages.ERR_COMPRESSEDSCHEMA_UNRECOGNIZED_AD_TOKENUnable to decode the provided attribute because it used an undefined attribute description token %sServerMessages.ERR_COMPSCHEMA_CANNOT_DECODE_AD_TOKENAn error occurred while attempting to decode an attribute description token from the compressed schema definitions: %sServerMessages.ERR_COMPSCHEMA_CANNOT_DECODE_OC_TOKENAn error occurred while attempting to decode an object class set token from the compressed schema definitions: %sServerMessages.ERR_COMPSCHEMA_CANNOT_STORE_EXAn error occurred while attempting to store compressed schema information in the database: %sServerMessages.ERR_CONFIG_ACCTNOTHANDLER_EXISTSUnable to add a new account status notification handler entry with DN %s because there is already a notification handler registered with that DNServerMessages.ERR_CONFIG_BACKEND_BASE_IS_EMPTYUnable to configure the backend '%s' because one of its base DNs is the empty DNServerMessages.ERR_CONFIG_BACKEND_CANNOT_DELETE_ENTRYBackend config error when trying to delete an entry: %sServerMessages.ERR_CONFIG_BACKEND_INSANE_MODEInvalid UNIX file permissions %s does not allow read and write access to the backend database directory by the backendServerMessages.ERR_CONFIG_BACKEND_MODE_INVALIDConfiguration 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.)ServerMessages.ERR_CONFIG_CANNOT_CONFIGURE_JUL_LOGGERCannot configure java.util.logging root logger level: %s. java.util.logging support is now disabledServerMessages.ERR_CONFIG_CANNOT_DETERMINE_SERVER_ROOTUnable 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 rootServerMessages.ERR_CONFIG_CORE_SCHEMA_PROVIDER_DISABLEDThe core schema provider defined by '%s' has been disabled. The core schema must always be enabledServerMessages.ERR_CONFIG_ENTRYCACHE_CANNOT_INSTALL_DEFAULT_CACHEAn unexpected error occurred that prevented the server from installing its default entry cache framework: %sServerMessages.ERR_CONFIG_ERROR_CREATING_MAILSSLSOCKETFACTORYError creating SSL socket factory: %sServerMessages.ERR_CONFIG_FILE_ADD_ALREADY_EXISTSEntry %s cannot be added to the Directory Server configuration because another configuration entry already exists with that DNServerMessages.ERR_CONFIG_FILE_ADD_APPLY_FAILEDThe 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: %sServerMessages.ERR_CONFIG_FILE_ADD_NO_PARENT_DNEntry %s cannot be added to the Directory Server configuration because that DN does not have a parentServerMessages.ERR_CONFIG_FILE_CANNOT_WRITE_CONFIG_ARCHIVEAn error occurred while trying to write the current configuration to the configuration archive: %sServerMessages.ERR_CONFIG_FILE_DELETE_APPLY_FAILEDThe 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: %sServerMessages.ERR_CONFIG_FILE_DELETE_HAS_CHILDRENEntry %s cannot be removed from the Directory Server configuration because the specified entry has one or more subordinate entriesServerMessages.ERR_CONFIG_FILE_DELETE_NO_PARENTEntry %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 allowedServerMessages.ERR_CONFIG_FILE_DELETE_NO_PARENT_DNEntry %s cannot be removed from the Directory Server configuration because that DN does not have a parentServerMessages.ERR_CONFIG_FILE_DELETE_NO_SUCH_ENTRYEntry %s cannot be removed from the Directory Server configuration because the specified entry does not existServerMessages.ERR_CONFIG_FILE_DOES_NOT_EXISTThe specified configuration file %s does not exist or is not readableServerMessages.ERR_CONFIG_FILE_MODIFY_APPLY_FAILEDThe 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: %sServerMessages.ERR_CONFIG_FILE_MODIFY_NO_SUCH_ENTRYEntry %s cannot be modified because the specified entry does not existServerMessages.ERR_CONFIG_FILE_MODIFY_STRUCTURAL_CHANGE_NOT_ALLOWEDConfiguration entry %s cannot be modified because the change would alter its structural object classServerMessages.ERR_CONFIG_INDEX_CANNOT_PROTECT_BOTHThe attribute '%s' cannot enable confidentiality for keys and values at the same timeServerMessages.ERR_CONFIG_JE_DUPLICATE_PROPERTYAn error occurred while trying to parse and validate Berkeley DB JE property %s: the property is already defined for this componentServerMessages.ERR_CONFIG_JE_PROPERTY_INVALID_FORMAn error occurred while trying to parse and validate Berkeley DB JE property %s: the property does not follow a singular property=value formServerMessages.ERR_CONFIG_LDIF_WRITE_ERRORAn unexpected error occurred while trying to export the Directory Server configuration to LDIF: %sServerMessages.ERR_CONFIG_LOGGER_INVALID_OBJECTCLASSConfiguration entry %s does not contain a valid objectclass for a Directory Server access, error, or debug logger definitionServerMessages.ERR_CONFIG_LOGGING_INSANE_MODEInvalid UNIX file permissions %s does not allow write access to the log file by the log publisherServerMessages.ERR_CONFIG_LOGGING_INVALID_TIME_FORMATThe 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" classServerMessages.ERR_CONFIG_MATCHING_RULE_INVALID_JSON_POINTERThe list of keys defined for the JSON matching rule contains an invalid JSON pointer : %sServerMessages.ERR_CONFIG_PROPERTY_RESOLVER_ERRORCannot create the property resolver due to the following error: '%s'ServerMessages.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 policyServerMessages.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 policyServerMessages.ERR_CONFIG_PWPOLICY_MISSING_DEFAULT_POLICYThe 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=configServerMessages.ERR_CONFIG_PWSCHEME_EXISTSUnable to add a new password storage scheme entry with DN %s because there is already a storage scheme registered with that DNServerMessages.ERR_CONFIG_SCHEMA_DIR_NOT_DIRECTORYUnable to read the Directory Server schema definitions because the schema directory %s exists but is not a directoryServerMessages.ERR_CONFIG_SCHEMA_NO_SCHEMA_DIRUnable to read the Directory Server schema definitions because the schema directory %s does not existServerMessages.ERR_CONFIG_UNABLE_TO_APPLY_CHANGES_FILEOne or more errors occurred while applying changes on server startup: %sServerMessages.ERR_CONFIG_UNSUPPORTED_SSL_CIPHER_SUITECannot configure new SSL cipher suites because the following cipher suites are not supported: %s. Look for supported cipher suites in 'cn=jvm,cn=monitor'ServerMessages.ERR_CONFIG_UNSUPPORTED_SSL_PROTOCOLCannot configure new SSL protocols because the following protocols are not supported: %s. Look for supported protocols in 'cn=jvm,cn=monitor'ServerMessages.ERR_CONFIG_VLV_INDEX_MISSING_SORT_KEYVLV index '%s' must be configured with at least one sort attributeServerMessages.ERR_CONFIGDS_CANNOT_CREATE_MONITOR_USERAn error occurred while attempting to write the monitor user entry: %sServerMessages.ERR_CONFIGDS_CANNOT_CREATE_MONITOR_USER_BACKENDAn error occurred while attempting to configure the backend for the monitor user: %sServerMessages.ERR_CONNHANDLER_CONFIG_CHANGES_REQUIRE_RESTARTThe server received configuration changes that require a restart of the %s connection handler to take effectServerMessages.ERR_CONNHANDLER_SSL_CANNOT_INITIALIZEAn error occurred while attempting to initialize the SSL context for use in the LDAP Connection Handler: %sServerMessages.ERR_CONTROL_INSUFFICIENT_ACCESS_RIGHTSThe request control with Object Identifier (OID) "%s" cannot be used due to insufficient access rightsServerMessages.ERR_COULD_NOT_CLOSE_THE_SOCKETThe Replication Server socket could not be closed : %sServerMessages.ERR_COULD_NOT_STOP_CONNECT_THREADThe replication server connector thread could not be stopped : %sServerMessages.ERR_COULD_NOT_STOP_LISTEN_THREADThe thread listening on the replication server port could not be stopped : %sServerMessages.ERR_CREATE_FAILThe backend database directory could not be created: %sServerMessages.ERR_CREATERC_CANNOT_WRITEAn error occurred while attempting to generate the RC script: %sServerMessages.ERR_CREATERC_CANNOT_WRITE_SYSTEMDAn error occurred while attempting to generate the systemd service file: %sServerMessages.ERR_CREATERC_JAVA_HOME_DOESNT_EXISTThe directory %s specified as the OPENDJ_JAVA_HOME path does not exist or is not a directoryServerMessages.ERR_CRYPTOMGR_CANNOT_GET_PREFERRED_KEY_WRAPPING_CIPHERCryptoManager cannot get the preferred key wrapping cipher: %sServerMessages.ERR_CRYPTOMGR_CANNOT_SIGN_WRAPPED_KEY_ENTRYCryptoManager failed to sign the wrapped key entry: %sServerMessages.ERR_CRYPTOMGR_CANNOT_VERIFY_WRAPPED_KEY_ENTRY_SIGNATURECryptoManager failed to verify the wrapped key entry signature: %sServerMessages.ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_DECIPHERCryptoManager failed to decipher the wrapped secret-key value: %sServerMessages.ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_FIELD_COUNTCryptoManager symmetric key attribute value "%s" syntax is invalid: incorrect number of fieldsServerMessages.ERR_CRYPTOMGR_DECRYPT_CIPHER_INPUT_STREAM_ERRORCryptoManager failed to decrypt the supplied data because there was an error reading from the input stream: %sServerMessages.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: %sServerMessages.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: %sServerMessages.ERR_CRYPTOMGR_DECRYPT_UNKNOWN_PROLOGUE_VERSIONCryptoManager failed to decrypt the supplied data because the version "%d" in the data prologue is unknownServerMessages.ERR_CRYPTOMGR_FAILED_TO_ENCODE_SYMMETRIC_KEY_ATTRIBUTECryptoManager failed to encode symmetric key attribute value: %sServerMessages.ERR_CRYPTOMGR_FULL_CIPHER_TRANSFORMATION_REQUIREDCryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding"ServerMessages.ERR_CRYPTOMGR_FULL_KEY_WRAPPING_TRANSFORMATION_REQUIREDCryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding"ServerMessages.ERR_CRYPTOMGR_GET_CIPHER_CANNOT_INITIALIZECryptoManager cannot initialize Cipher: %sServerMessages.ERR_CRYPTOMGR_GET_CIPHER_STREAM_PROLOGUE_WRITE_ERRORCryptoManager failed to write the stream prologue: %sServerMessages.ERR_CRYPTOMGR_GET_MAC_ENGINE_CANNOT_INITIALIZECryptoManager failed to initialize MAC engine: %sServerMessages.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 instanceServerMessages.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 instanceServerMessages.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"ServerMessages.ERR_CRYPTOMGR_MISSING_WRAPPED_KEY_ENTRY_ATTRIBUTESThe wrapped key entry is missing the following attributes: %sServerMessages.ERR_CRYPTOMGR_REWRAP_SYMMETRIC_KEY_ATTRIBUTE_NO_WRAPPERCryptoManager cannot find the public-key-certificate (identifier "%s") requested for symmetric key re-encodingServerMessages.ERR_CRYPTOMGR_SSL_CONTEXT_CANNOT_INITIALIZEAn error occurred while attempting to initialize a SSL context for server to server communication: %sServerMessages.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 keyServerMessages.ERR_DATABASE_EXCEPTIONDatabase exception: %sServerMessages.ERR_DELETE_ABORTED_BY_SUBORDINATE_PLUGINA plugin caused the delete operation to be aborted while deleting a subordinate entry %sServerMessages.ERR_DELETE_ASSERTION_FAILEDEntry %s cannot be removed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entryServerMessages.ERR_DELETE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe entry %s cannot be deleted due to insufficient access rightsServerMessages.ERR_DELETE_BACKEND_READONLYUnable to delete entry %s because the backend that holds that entry is configured in read-only modeServerMessages.ERR_DELETE_CANNOT_LOCK_ENTRYEntry %s cannot be removed because the server failed to obtain a write lock for this entry after multiple attemptsServerMessages.ERR_DELETE_NO_SUCH_ENTRYEntry %s does not exist in the Directory ServerServerMessages.ERR_DELETE_NO_SUCH_OBJECTThe entry '%s' cannot be removed because it does not existServerMessages.ERR_DELETE_NOT_ALLOWED_ON_NONLEAFThe entry '%s' cannot be removed because it has subordinate entriesServerMessages.ERR_DELETE_SERVER_READONLYUnable to delete entry %s because the Directory Server is configured in read-only modeServerMessages.ERR_DEREGISTER_BASEDN_NOT_REGISTEREDUnable to de-register base DN %s with the Directory Server because that base DN is not registered for any active backendServerMessages.ERR_DICTIONARY_VALIDATOR_CANNOT_LOADError loading dictionary: %sServerMessages.ERR_DICTIONARY_VALIDATOR_NO_SUCH_FILEThe specified dictionary file %s does not existServerMessages.ERR_DIRCFG_INVALID_CONFIG_FILEThe specified config file path '%s' is invalid. The specified path must exist and must be a fileServerMessages.ERR_DIRCFG_INVALID_SCHEMA_DIRECTORYThe specified schema configuration directory '%s' is invalid. The specified path must exist and must be a directoryServerMessages.ERR_DIRCFG_INVALID_SERVER_ROOTThe specified server root directory '%s' is invalid. The specified path must exist and must be a directoryServerMessages.ERR_DIRECTORY_INVALIDThe backend database directory '%s' is not a valid directoryServerMessages.ERR_DR_NO_DATA_IN_BACKENDThere is no data in domain '%s' to run disaster recovery onServerMessages.ERR_DSCORE_CANNOT_BOOTSTRAPAn error occurred while attempting to bootstrap the Directory Server: %sServerMessages.ERR_DSCORE_CANNOT_STARTAn error occurred while trying to start the Directory Server: %sServerMessages.ERR_DSCORE_ERROR_PARSING_ARGSAn error occurred while attempting to parse the provided set of command line arguments: %sServerMessages.ERR_DSREPL_CANNOT_LIST_CNI_FILESThe replication changelog files could not be retrieved. Check file permissions and filesystem status. The error is: %sServerMessages.ERR_DSREPL_CANNOT_READ_CONFIGURATIONCannot read the configuration of the local server. The error was: %sServerMessages.ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_DISABLE_ADMIN_BACKENDCannot 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: %sAn error occurred opening (or closing) a connection to read or change the configuration of the local server. The error was: %sServerMessages.ERR_DSREPL_CLEAR_CHANGELOG_DELETE_FAILEDA problem occurred while clearing the changelog data: %sServerMessages.ERR_DSREPL_DR_BAD_DATAThe 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 serverServerMessages.ERR_DSREPL_DR_FAILEDDisaster recovery for base DN '%s' failed on this serverServerMessages.ERR_DSREPL_DR_INVALID_IDThe 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 serverServerMessages.ERR_DSREPL_DR_INVALID_VERSIONThe 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 serverServerMessages.ERR_DSREPL_DR_WITH_VERSION_NEED_DSBase Dn '%s' is not a replicated domain on this server. Disaster recovery must be run on a directory server or a combined directory/replication serverServerMessages.ERR_DSREPL_DR_WRONG_SERVERThe server is neither a replica nor a replication server for base DN '%s'Cannot 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: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_DISCOVER_NEW_SERVER_CONFIGCannot discover the configuration of the local server. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_OBTAIN_CONNECTION_TO_ALL_SERVERSCannot obtain a connection for one of the servers in the existing topology. The error was: %sServerMessages.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: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_READ_SERVER_IDSError when reading the server IDs from all the servers in the old topology. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_ERROR_WHILE_ADDING_INSTANCE_KEYSCannot add server instance keys to the new server. The error was: %sServerMessages.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: %sAn error occurred opening (or closing) a connection to change the configuration of the local server. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_INAPPROPRIATE_GROUP_IDInappropriate 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 IDServerMessages.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 zerosServerMessages.ERR_DSREPL_STATUS_CANNOT_READ_CN_MONITOR_ON_SERVERError while reading cn=monitor: %sServerMessages.ERR_DSREPL_STATUS_GENERAL_ERROR_READING_CN_MONITORGeneral error: %sServerMessages.ERR_DSREPL_STATUS_NO_ADMIN_PORT_FOR_SERVERCannot contact server: no admin port could be discovered in its entry %sServerMessages.ERR_DSREPL_STATUS_UNHEALTHY_SERVERServer is not healthy: %sServerMessages.ERR_ECLN_CANNOT_DECODE_VALUECannot decode the provided entry changelog notification control because an error occurred while attempting to decode the control value: %sServerMessages.ERR_EMBEDDED_SERVER_CONFIG_VERSIONAn error occurred while attempting to retrieve the configuration version of the directory server: '%s'ServerMessages.ERR_EMBEDDED_SERVER_DATA_VERSIONAn error occurred while attempting to retrieve the data version of the directory server: '%s'ServerMessages.ERR_EMBEDDED_SERVER_INTERNAL_CONNECTIONAn error occurred while attempting to retrieve an internal connection to the server with the user DN '%s'ServerMessages.ERR_EMBEDDED_SERVER_LDIF_MANAGEMENT_CONTEXTAn error occurred while attempting to initialize the configuration framework or to read the configuration file '%s'ServerMessages.ERR_EMBEDUTILS_SERVER_ALREADY_RUNNINGThe embedded server with server root '%s' cannot be started because it is already runningServerMessages.ERR_ENCPW_CANNOT_ENCODEAn error occurred while attempting to encode the clear-text password: %sServerMessages.ERR_ENCPW_CANNOT_READ_PWCannot read password from the input: %sServerMessages.ERR_ENCPW_INVALID_ENCODED_AUTHPWThe provided password is not a valid encoded authentication password value: %sServerMessages.ERR_ENCPW_INVALID_ENCODED_USERPWThe provided password is not a valid encoded user password value: %sServerMessages.ERR_ENCPW_NO_SCHEMENo password storage scheme was specified. Use the --%s argument to specify the storage schemeServerMessages.ERR_ENCPW_NO_SUCH_AUTH_SCHEMEAuthentication password storage scheme "%s" is not configured for use in the Directory ServerServerMessages.ERR_ENCPW_NO_SUCH_SCHEMEPassword storage scheme "%s" is not configured for use in the Directory ServerServerMessages.ERR_ENQUEUE_MUST_CHANGE_PASSWORD%s must change their password before it will be allowed to request any other operationsServerMessages.ERR_ENTRY_DATABASE_CORRUPTThe entry database does not contain a valid record for ID %sServerMessages.ERR_ENTRY_DECODE_EXCEPTIONUnable to decode an entry because an unexpected exception was caught during processing: %sServerMessages.ERR_ENTRY_DECODE_UNRECOGNIZED_VERSIONUnable to decode an entry because it had an unsupported entry version byte value of %sServerMessages.ERR_ENV_VAR_PROPERTY_VALUE_NOT_FOUNDNo value found for property '%s'ServerMessages.ERR_ERROR_MSG_RECEIVEDThe following error has been received : %sServerMessages.ERR_ERROR_PARSING_ARGSAn error occurred while parsing the command-line arguments: %sServerMessages.ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTID string %s mapped to multiple usersServerMessages.ERR_EXCEPTION_CHANGELOG_TRIM_FLUSHError during the Replication Server database trimming or flush process. The Changelog service is going to shutdown: %sServerMessages.ERR_EXCEPTION_LISTENINGReplication server caught exception while listening for client connections: %sServerMessages.ERR_EXCEPTION_REPLAYING_REPLICATION_MESSAGEAn Exception was caught while replaying replication message : %sServerMessages.ERR_EXECUTION_ERRORExecution error during backend operation: %sServerMessages.ERR_EXPORT_IO_ERRORI/O error occurred while exporting entry: %sServerMessages.ERR_EXTENDED_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe extended operation %s cannot be performed due to insufficient access rightsServerMessages.ERR_EXTENDED_NO_HANDLERThere is no extended operation handler registered with the Directory Server for handling extended operations with a request OID of %sServerMessages.ERR_EXTERNAL_PROCESS_INTERRUPTEDExternal process has been interrupted: '%s'ServerMessages.ERR_EXTERNAL_PROCESS_STDERRExternal process contains errors: %sServerMessages.ERR_EXTOP_CANCEL_CANNOT_DECODE_REQUEST_VALUEAn error occurred while attempting to decode the value of the cancel extended request: %sServerMessages.ERR_EXTOP_PASSMOD_ACCOUNT_NOT_LOCALPassword modification is not supported for user %s because the account is not managed locallyServerMessages.ERR_EXTOP_PASSMOD_CANNOT_DECODE_AUTHZ_DNThe 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 operationServerMessages.ERR_EXTOP_PASSMOD_CANNOT_DECODE_REQUESTAn unexpected error occurred while attempting to decode the password modify extended request sequence: %sServerMessages.ERR_EXTOP_PASSMOD_CANNOT_ENCODE_PASSWORDUnable to encode the provided password using the default scheme(s): %sServerMessages.ERR_EXTOP_PASSMOD_CANNOT_GENERATE_PWAn error occurred while attempting to create a new password using the password generator: %sServerMessages.ERR_EXTOP_PASSMOD_CANNOT_LOCK_USER_ENTRYThe password modify extended request cannot be processed because the server was unable to obtain a write lock on user entry %s after multiple attemptsServerMessages.ERR_EXTOP_PASSMOD_CANNOT_MAP_USERThe provided authorization ID string "%s" could not be mapped to any user in the directoryServerMessages.ERR_EXTOP_PASSMOD_INVALID_AUTHZID_STRINGThe password modify extended request cannot be processed because it contained an invalid userIdentity field. The provided userIdentity string was "%s"ServerMessages.ERR_EXTOP_PASSMOD_NO_USER_ENTRY_BY_AUTHZIDThe 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"ServerMessages.ERR_EXTOP_PASSMOD_UNACCEPTABLE_PWThe provided new password failed the validation checks defined in the server: %sServerMessages.ERR_EXTOP_PWPSTATE_ACCOUNT_NOT_LOCALThe password policy state extended operation is not supported for user %s because the account is not managed locallyServerMessages.ERR_FCM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe certificate with fingerprint %s mapped to multiple usersServerMessages.ERR_FCM_PEER_CERT_NOT_X509Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)ServerMessages.ERR_FIFOCACHE_CANNOT_INITIALIZEA fatal error occurred while trying to initialize fifo entry cache: %sServerMessages.ERR_FILE_CREDENTIALS_FAILED_TO_PARSEFailed to parse the credential file '%s'ServerMessages.ERR_FILE_CREDENTIALS_NOT_FOUNDCredential file '%s' not foundServerMessages.ERR_FILELOCKER_LOCK_EXCLUSIVE_NOT_GRANTEDThe exclusive lock requested for file %s was not granted, which indicates that another process already holds a shared or exclusive lock on that fileServerMessages.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 fileServerMessages.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 fileServerMessages.ERR_FILELOCKER_LOCK_SHARED_NOT_GRANTEDThe shared lock requested for file %s was not granted, which indicates that another process already holds an exclusive lock on that fileServerMessages.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 fileServerMessages.ERR_FILELOCKER_UNLOCK_UNKNOWN_FILEThe attempt to release the lock held on %s failed because no record of a lock on that file was foundServerMessages.ERR_FILEPERM_INVALID_UNIX_MODE_STRINGThe 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 sevenServerMessages.ERR_FILEPERM_SET_JAVA_EXCEPTIONOne 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 alteredServerMessages.ERR_FILEPERM_SET_NO_SUCH_FILEUnable to set permissions for file %s because it does not existServerMessages.ERR_FRACTIONAL_COULD_NOT_RETRIEVE_CONFIGCould not retrieve the configuration for a replication domain matching the entry %sServerMessages.ERR_GET_SYMMETRIC_KEY_ASN1_DECODE_EXCEPTIONCannot decode the provided symmetric key extended request: %sServerMessages.ERR_GET_SYMMETRIC_KEY_DECODE_EXCEPTIONAn unexpected error occurred while attempting to decode the symmetric key extended request sequence: %sServerMessages.ERR_HEX_DECODE_INVALID_LENGTHThe value %s cannot be decoded as a hexadecimal string because it does not have a length that is a multiple of two bytesServerMessages.ERR_HTTP_APPLICATION_START_EXCEPTIONError while starting the HTTP application: %sServerMessages.ERR_IDENTITY_MAPPERS_MULTIPLE_MATCHING_ENTRIESThe processed ID string %s is mapped to multiple usersServerMessages.ERR_IMPORT_CREATE_TMPDIR_ERRORUnable to create the temporary directory %sServerMessages.ERR_IMPORT_DUPLICATE_ENTRYThe import has been aborted because the data to be imported contains duplicate copies of entry '%s'ServerMessages.ERR_IMPORT_PARENT_NOT_FOUNDThe import has been aborted because the entry '%s' does not have a parent entryServerMessages.ERR_INCOMPATIBLE_ENTRY_VERSIONEntry record is not compatible with this version of the backend database. Entry version: %xServerMessages.ERR_INDEX_CORRUPT_REQUIRES_REBUILDAn 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 operationServerMessages.ERR_INDEXES_NOT_SUPPORTEDIndexes are not supported in the "%s" backendServerMessages.ERR_INIT_DOMAIN_IS_STOPPINGInitialization of replication domain '%s' interrupted because the domain is shutting down. The domain still needs to be re-initializedServerMessages.ERR_INIT_EXPORT_NOT_SUPPORTEDInitialization cannot be done because export is not supported by the backend %sServerMessages.ERR_INIT_HEARTBEAT_LOST_DURING_EXPORTWhen initializing remote server(s), the initialized server with serverId=%s is potentially stopped or too slowServerMessages.ERR_INIT_IMPORT_FAILUREDuring initialization from a remote server, the following error occurred : %sServerMessages.ERR_INIT_IMPORT_NOT_SUPPORTEDInitialization cannot be done because import is not supported by the backend %sServerMessages.ERR_INIT_REPLICA_DISCONNECTED_DURING_EXPORTReplica '%s' seems to have disconnected from the topology while it was being re-initialized, initialization will stopServerMessages.ERR_INIT_RS_DISCONNECTION_DURING_EXPORTWhen initializing remote server(s), connection to Replication Server with serverId=%s is lostServerMessages.ERR_INIT_RS_DISCONNECTION_DURING_IMPORTConnection failure with Replication Server %s during importServerMessages.ERR_INITIALIZATION_FAILED_NOCONNThe initialization failed because the domain %s is not connected to a replication serverServerMessages.ERR_INTERACTIVE_INVALID_INTValue '%s' must be a valid numberServerMessages.ERR_INTERACTIVE_INVALID_VERSIONValue '%s' must be a valid version (two or three digits separated with a dot)ServerMessages.ERR_INTERACTIVE_VERSION_TOO_OLDPlease select at least version %sServerMessages.ERR_INTERNAL_CONNECTION_NO_RESULTNo result received after completion for request '%s' received for internal client connectionServerMessages.ERR_INTERNAL_ERROR_WITHOUT_EXCEPTIONAn internal error was detected when accessing backend '%s'ServerMessages.ERR_INTERNAL_PACKAGING_ERRORError: %sServerMessages.ERR_INTERNALCONN_NO_SUCH_USERUser %s does not exist in the directoryServerMessages.ERR_INVALID_BACKUP_ID_NO_UNDERSCOREBackup id '%s' is invalid: expected to find an underscore in itServerMessages.ERR_INVALID_COOKIE_SYNTAXInvalid syntax for the provided cookie '%s'ServerMessages.ERR_INVALID_CSN_RANGE_ASSERTION_SYNTAXSpecified assertion '%s' for historicalCsnRangeMatch extensible matching rule does not conform to expected syntax. The assertion must specify a CSN rangeServerMessages.ERR_INVALID_CSN_RANGE_COMPARISON_OPERATORInvalid operator '%s' specified in historicalCsnRangeMatch extensible matching rule assertionServerMessages.ERR_INVALID_KEYSTORENo usable key was found for '%s', which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configuredServerMessages.ERR_INVALID_PAGED_RESULTS_COOKIEThe following paged results control cookie value was not recognized: %sServerMessages.ERR_INVALID_PEM_FILE_GLOB_PATTERNInvalid excluded file name pattern: %sServerMessages.ERR_JMX_ALERT_HANDLER_CANNOT_REGISTERAn error occurred while trying to register the JMX alert handler with the MBean server: %sServerMessages.ERR_JMX_CONNECTION_NO_RESULTNo result received after completion for request '%s' received for JMX client connectionServerMessages.ERR_JMX_CONNECTION_UNEXPECTED_REQUEST_TYPEUnable to process request '%s' received for JMX client because this type of request is not supported for JMXServerMessages.ERR_JVM_TRUSTSTORE_CANNOT_GETUnable to get the JVM default truststore: %sServerMessages.ERR_KEY_MANAGER_PROVIDER_MONITOR_CERTIFICATEAn error occurred while reading information contained within key manager provider from configuration: "%s"ServerMessages.ERR_KEYMANAGERS_COULD_NOT_BE_RETRIEVEDAn error occurred while trying to retrieve the key managers from the key manager provider `%s`ServerMessages.ERR_LDAP_PTA_INVALID_FILTER_TEMPLATEThe mapped search filter template "%s" could not be parsed as a valid LDAP filterServerMessages.ERR_LDAP_PTA_NO_PWDThe configuration of LDAP PTA policy "%s" is invalid because it does not specify a means for obtaining the mapped search bind passwordServerMessages.ERR_LDAP_UNSUPPORTED_PROTOCOL_VERSIONThe Directory Server does not support LDAP protocol version %d. This connection will be closedServerMessages.ERR_LDAPURL_NO_COLON_SLASH_SLASHThe 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 URLServerMessages.ERR_LDAPURL_NO_HOSTThe provided string "%s" cannot be decoded as an LDAP URL because it does not contain a host before the colon to specify the port numberServerMessages.ERR_LDAPURL_NO_PORTThe provided string "%s" cannot be decoded as an LDAP URL because it does not contain a port number after the colon following the hostServerMessages.ERR_LDAPURL_NO_SCHEMEThe provided string "%s" cannot be decoded as an LDAP URL because it does not contain a protocol schemeServerMessages.ERR_LDAPV2_REFERRALS_OMITTEDThe response included one or more referrals, which are not allowed for LDAPv2 clients. The referrals included were: %sServerMessages.ERR_LDIF_BACKEND_ADD_ALREADY_EXISTSEntry %s already exists in the LDIF backendServerMessages.ERR_LDIF_BACKEND_ADD_MISSING_PARENTThe parent for entry %s does not existServerMessages.ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_READERAn error occurred while trying to create the reader for the LDIF import operation: %sServerMessages.ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_WRITERAn error occurred while trying to create the writer for the LDIF export operation: %sServerMessages.ERR_LDIF_BACKEND_DELETE_NO_SUCH_ENTRYEntry %s does not existServerMessages.ERR_LDIF_BACKEND_DELETE_NONLEAFEntry %s has one or more subordinate entries and cannot be deleted until all of its subordinate entries are removed firstServerMessages.ERR_LDIF_BACKEND_ERROR_READING_LDIFAn unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continueServerMessages.ERR_LDIF_BACKEND_HAS_SUBORDINATES_NO_SUCH_ENTRYThe target entry %s does not existServerMessages.ERR_LDIF_BACKEND_MODDN_NEW_PARENT_DOESNT_EXISTThe new parent DN %s does not existServerMessages.ERR_LDIF_BACKEND_MODDN_NO_SUCH_SOURCE_ENTRYSource entry %s does not existServerMessages.ERR_LDIF_BACKEND_MODDN_TARGET_ENTRY_ALREADY_EXISTSTarget entry %s already existsServerMessages.ERR_LDIF_BACKEND_MODIFY_NO_SUCH_ENTRYEntry %s does not existServerMessages.ERR_LDIF_BACKEND_MULTIPLE_BASE_DNSThe LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNsServerMessages.ERR_LDIF_BACKEND_NUM_SUBORDINATES_NO_SUCH_ENTRYThe target entry %s does not existServerMessages.ERR_LDIF_BACKEND_SEARCH_NO_SUCH_BASEEntry %s specified as the search base DN does not existServerMessages.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 performedServerMessages.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 continueServerMessages.ERR_LDIF_FILE_EXISTSThe specified LDIF file %s already exists and the export configuration indicates that no attempt should be made to append to or replace the fileServerMessages.ERR_LDIF_REJECTED_BY_PLUGIN_NOMESSAGERejecting entry %s because it was rejected by a pluginServerMessages.ERR_LDIF_SKIPSkipping entry %s because the DN is not one that should be included based on the include and exclude branches/filtersServerMessages.ERR_LDIF_SKIP_NOT_IN_INCLUDED_BRANCHESSkipping entry %s because the DN is not included by any include branchesServerMessages.ERR_LDIF_SKIP_NOT_IN_INCLUDED_FILTERSSkipping entry %s because the DN is not included by any include filtersServerMessages.ERR_LDIFEXPORT_CANNOT_DECODE_WRAP_COLUMN_AS_INTEGERUnable to decode wrap column value "%s" as an integerServerMessages.ERR_LDIFEXPORT_CANNOT_EXPORT_BACKENDThe Directory Server backend with backend ID "%s" does not provide a mechanism for performing LDIF exportsServerMessages.ERR_LDIFEXPORT_ERROR_DURING_EXPORTAn error occurred while attempting to process the LDIF export: %sServerMessages.ERR_LDIFEXPORT_MULTIPLE_BACKENDS_FOR_IDMultiple Directory Server backends are configured with the requested backend ID "%s"ServerMessages.ERR_LDIFEXPORT_NO_BACKENDS_FOR_IDNone of the Directory Server backends are configured with the requested backend ID "%s"ServerMessages.ERR_LDIFIMPORT_CANNOT_IMPORTThe Directory Server backend with backend ID %s does not provide a mechanism for performing LDIF importsServerMessages.ERR_LDIFIMPORT_CANNOT_READ_FILEThe specified LDIF file %s cannot be readServerMessages.ERR_LDIFIMPORT_COUNT_REJECTS_REQUIRES_OFFLINEThe %s argument is not supported for online importsServerMessages.ERR_LDIFIMPORT_ERROR_DURING_IMPORTAn error occurred while attempting to process the LDIF import: %sServerMessages.ERR_LDIFIMPORT_LDIF_FILE_DOESNT_EXISTUnable to access the LDIF file %s to import. Please check that the file is local to the server and the path correctServerMessages.ERR_LOADING_JVM_KEYSTORE_FROM_PROPERTIESUnable to load JVM default keystore from system properties: %sServerMessages.ERR_LOG_FILE_DISAPPEAREDThe 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 onlyServerMessages.ERR_LOGGER_ERROR_LISTING_FILESError occurred while listing log files named by policy with initial file name %sServerMessages.ERR_MAX_BLOCKED_WRITE_LIMIT_EXCEEDEDCould not write data to the client for %sServerMessages.ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_READERUnable to create an LDIF reader: %sServerMessages.ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_WRITERUnable to create an LDIF writer: %sServerMessages.ERR_MEMORYBACKEND_CANNOT_DELETE_ENTRY_WITH_CHILDRENCannot delete entry %s because it has one or more subordinate entriesServerMessages.ERR_MEMORYBACKEND_CANNOT_RENAME_ENRY_WITH_CHILDRENCannot rename entry %s because it has one or more subordinate entriesServerMessages.ERR_MEMORYBACKEND_CANNOT_RENAME_TO_ANOTHER_BACKENDCannot rename entry %s because the target entry is in a different backendServerMessages.ERR_MEMORYBACKEND_ENTRY_ALREADY_EXISTSEntry %s already exists in the memory-based backendServerMessages.ERR_MEMORYBACKEND_ENTRY_DOESNT_BELONGEntry %s does not belong in the memory-based backendServerMessages.ERR_MEMORYBACKEND_ERROR_DURING_IMPORTAn unexpected error occurred while processing the import: %sServerMessages.ERR_MEMORYBACKEND_ERROR_READING_LDIFAn unrecoverable error occurred while reading from LDIF: %sServerMessages.ERR_MISSING_ID2ENTRY_RECORDThe entry database does not contain a record for ID %sServerMessages.ERR_MODDN_ASSERTION_FAILEDEntry %s cannot be renamed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entryServerMessages.ERR_MODDN_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe entry %s cannot be renamed due to insufficient access rightsServerMessages.ERR_MODDN_BACKEND_READONLYUnable to rename entry %s because the backend that holds that entry is configured in read-only modeServerMessages.ERR_MODDN_CANNOT_LOCK_CURRENT_DNThe modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for that DNServerMessages.ERR_MODDN_NO_BACKEND_FOR_CURRENT_ENTRYThe modify DN operation for entry %s cannot be performed because no backend is registered to handle that DNServerMessages.ERR_MODDN_NO_CURRENT_ENTRYThe modify DN operation for entry %s cannot be performed because that entry does not exist in the serverServerMessages.ERR_MODDN_NO_PARENTA modify DN operation cannot be performed on entry %s because the new RDN would not have a parent DNServerMessages.ERR_MODDN_SERVER_READONLYUnable to rename entry %s because the Directory Server is configured in read-only modeServerMessages.ERR_MODIFY_ASSERTION_FAILEDEntry %s cannot be modified because the request contained an LDAP assertion control and the associated filter did not match the contents of the entryServerMessages.ERR_MODIFY_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe entry %s cannot be modified due to insufficient access rightsServerMessages.ERR_MODIFY_BACKEND_READONLYUnable to modify entry %s because the backend that holds that entry is configured in read-only modeServerMessages.ERR_MODIFY_CANNOT_LOCK_ENTRYEntry %s cannot be modified because the server failed to obtain a write lock for this entry after multiple attemptsServerMessages.ERR_MODIFY_MUST_CHANGE_PASSWORD%s must change their password before it will be allowed to perform any other operationsServerMessages.ERR_MODIFY_NO_MODIFICATIONSEntry %s cannot be updated because the request did not contain any modificationsServerMessages.ERR_MODIFY_NO_SUCH_ENTRYEntry %s cannot be modified because no such entry exists in the serverServerMessages.ERR_MODIFY_NO_SUCH_OBJECTThe entry '%s' cannot be modified because it does not existServerMessages.ERR_MODIFY_PW_VALIDATION_FAILEDThe provided password value was rejected by a password validator: %sServerMessages.ERR_MODIFY_SERVER_READONLYUnable to modify entry %s because the Directory Server is configured in read-only modeServerMessages.ERR_MODIFYDN_ALREADY_EXISTSThe entry cannot be renamed to '%s' because an entry with that name already existsServerMessages.ERR_MODIFYDN_NO_SUCH_OBJECTThe entry '%s' cannot be renamed because it does not existServerMessages.ERR_MONITOR_UNABLE_TO_EXPORT_BASEAn error occurred while attempting to export the base monitor entry: %sServerMessages.ERR_MONITORING_DATACould not collect monitoring data from the directory server: %sServerMessages.ERR_MOVEDIR_SOURCE_NOT_DIRECTORYThe directory to move %s exists but is a fileServerMessages.ERR_MOVEDIR_SOURCE_NOT_EXISTThe directory to move %s does not existServerMessages.ERR_MOVEDIR_TARGET_EXISTSThe target directory %s already existsServerMessages.ERR_MULTIPLE_BACKENDS_FOR_BASEMultiple Directory Server backends are configured to support base DN "%s"ServerMessages.ERR_NEW_SUPERIOR_NO_SUCH_OBJECTThe entry cannot be moved because the new parent entry '%s' does not existServerMessages.ERR_NO_BACKEND_FOUND_FOR_BASE_DNNo backend is associated with the base DN '%s'ServerMessages.ERR_NO_BACKENDS_FOR_BASENone of the Directory Server backends are configured to support the requested base DN "%s"ServerMessages.ERR_NO_MATCHING_DOMAINNo domain matches the provided base DN '%s'ServerMessages.ERR_NOT_CONNECTED_EXPORT_TARGETServer %s should be initialized but is not connected to the topologyServerMessages.ERR_OFFLINE_TOOL_TARGET_SERVER_MISSINGA target server must be specified either by using LDAP connection options or the --%s optionServerMessages.ERR_OPEN_ENV_FAILThe database environment could not be opened: %sServerMessages.ERR_OUTPUT_DIRECTORY_NOT_FOUNDThe output directory "%s" could not be foundServerMessages.ERR_PARSING_ATTRIBUTE_TYPE_OIDUnable to parse the OID from the provided definition of attribute type: '%s'ServerMessages.ERR_PARSING_DIT_CONTENT_RULE_OIDUnable to parse the OID from the provided definition of DIT content rule: '%s'ServerMessages.ERR_PARSING_DIT_STRUCTURE_RULE_RULEIDUnable to parse the rule ID from the provided definition of DIT structure rule: '%s'ServerMessages.ERR_PARSING_LDAP_SYNTAX_OIDUnable to parse the OID from the provided definition of ldap syntax: '%s'ServerMessages.ERR_PARSING_MATCHING_RULE_USE_OIDUnable to parse the OID from the provided definition of matching rule use: '%s'ServerMessages.ERR_PARSING_NAME_FORM_OIDUnable to parse the OID from the provided definition of name form: '%s'ServerMessages.ERR_PARSING_OBJECTCLASS_OIDUnable to parse the OID from the provided definition of objectclass: '%s'ServerMessages.ERR_PKCS11_KEYMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a key manager factory to access the contents of the PKCS#11 keystore: %sServerMessages.ERR_PKCS11_KEYMANAGER_CANNOT_LOADAn error occurred while trying to access the PKCS#11 key manager: %sServerMessages.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: %sServerMessages.ERR_PKCS11_TRUSTMANAGER_CANNOT_LOADAn error occurred while trying to access the PKCS#11 trust manager: %sServerMessages.ERR_PLUGIN_7BIT_IMPORT_ATTR_NOT_CLEANThe entry included a value for attribute %s that was not 7-bit cleanServerMessages.ERR_PLUGIN_7BIT_INVALID_PLUGIN_TYPEThe 7-bit clean plugin is configured with invalid plugin type %s. Only the ldifImport, preOperationAdd, preOperationModify, and preOperationModifyDN plugin types are allowedServerMessages.ERR_PLUGIN_7BIT_MODIFYDN_ATTR_NOT_CLEANThe modify DN operation would have resulted in a value for attribute %s that was not 7-bit cleanServerMessages.ERR_PLUGIN_ADLIST_NO_PLUGIN_TYPESThe 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 pluginServerMessages.ERR_PLUGIN_ATTR_CLEANUP_ATTRIBUTE_MISSINGAttribute '%s' is not defined in the directory schemaServerMessages.ERR_PLUGIN_ATTR_CLEANUP_DUPLICATE_VALUEThe attribute '%s' has already been defined in the configurationServerMessages.ERR_PLUGIN_ATTR_CLEANUP_INITIALIZE_PLUGINInvalid plugin type '%s' for the Attribute Cleanup pluginServerMessages.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 pluginServerMessages.ERR_PLUGIN_ENTITY_TAG_INVALID_PLUGIN_TYPEAn attempt was made to register the Entity Tag plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginServerMessages.ERR_PLUGIN_ENTRYUUID_INVALID_PLUGIN_TYPEAn attempt was made to register the EntryUUID plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginServerMessages.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 allowedServerMessages.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 pluginServerMessages.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 restartServerMessages.ERR_PLUGIN_LASTMOD_INVALID_PLUGIN_TYPEAn attempt was made to register the LastMod plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginServerMessages.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 serverServerMessages.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 serverServerMessages.ERR_PLUGIN_PWIMPORT_NO_DEFAULT_AUTH_SCHEMESThe password policy import plugin is not configured any default auth password schemes, and the server does not support the %s auth password schemeServerMessages.ERR_PLUGIN_PWIMPORT_NO_DEFAULT_USER_SCHEMESThe password policy import plugin is not configured any default user password schemes, and the server does not support the %s auth password schemeServerMessages.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 serverServerMessages.ERR_PLUGIN_PWPIMPORT_INVALID_PLUGIN_TYPEAn 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 pluginServerMessages.ERR_PLUGIN_REFERENT_ATTR_NOT_LISTEDThe property 'check-references-filter-criteria' specifies filtering criteria for attribute '%s', but this attribute is not listed in the 'attribute-type' propertyServerMessages.ERR_PLUGIN_REFERENT_CANNOT_DECODE_STRING_AS_DNThe Referential Integrity plugin failed to decode a entry DN from the update log: %sServerMessages.ERR_PLUGIN_REFERENT_CLOSE_LOGFILEAn error occurred closing the Referential Integrity plugin update log file: %sServerMessages.ERR_PLUGIN_REFERENT_CREATE_LOGFILEAn error occurred during Referential Integrity plugin initialization because log file creation failed: %sServerMessages.ERR_PLUGIN_REFERENT_EXCEPTIONThe operation could not be processed due to an unexpected exception: '%s'ServerMessages.ERR_PLUGIN_REFERENT_INVALID_PLUGIN_TYPEAn attempt was made to register the Referential Integrity plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginServerMessages.ERR_PLUGIN_REFERENT_REPLACE_LOGFILEAn error occurred replacing the Referential Integrity plugin update log file: %sServerMessages.ERR_PLUGIN_REFERENT_SEARCH_FAILEDThe Referential Integrity plugin failed when performing an internal search: %sServerMessages.ERR_PLUGIN_SAMBA_SYNC_ENCODINGThe Samba password synchronization plugin could not encode a password for the following reasons: %sServerMessages.ERR_PLUGIN_SAMBA_SYNC_INVALID_PLUGIN_TYPEAn 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 pluginServerMessages.ERR_PLUGIN_SAMBA_SYNC_MODIFICATION_PROCESSINGThe Samba password synchronization plugin could not process a modification for the following reason: %sServerMessages.ERR_PLUGIN_STARTUP_PLUGIN_RETURNED_NULLThe 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 abortedServerMessages.ERR_PLUGIN_UNIQUEATTR_INVALID_PLUGIN_TYPEAn attempt was made to register the Unique Attribute plugin to be invoked as a %s plugin. This plugin type is not allowed for this pluginServerMessages.ERR_PROXYAUTH_AUTHZ_NOT_PERMITTEDAuthorization as '%s' specified in the proxied authorization control is not permittedServerMessages.ERR_PROXYAUTH1_NO_SUCH_USERUser %s specified in the proxied authorization V1 control does not exist in the Directory ServerServerMessages.ERR_PROXYAUTH1_UNUSABLE_ACCOUNTUse of the proxied authorization V1 control for user %s is not allowed by the password policy configurationServerMessages.ERR_PROXYAUTH2_ACCOUNT_DISABLEDUse of the proxied authorization V2 control for user %s is not allowed: the account is disabledServerMessages.ERR_PROXYAUTH2_ACCOUNT_EXPIREDUse of the proxied authorization V2 control for user %s is not allowed: the account is expiredServerMessages.ERR_PROXYAUTH2_ACCOUNT_LOCKEDUse of the proxied authorization V2 control for user %s is not allowed: the account is lockedServerMessages.ERR_PROXYAUTH2_INVALID_AUTHZIDThe 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 usernameServerMessages.ERR_PROXYAUTH2_NO_SUCH_USERUser %s specified in the proxied authorization V2 control does not exist in the Directory ServerServerMessages.ERR_PROXYAUTH2_PASSWORD_EXPIREDUse of the proxied authorization V2 control for user %s is not allowed: the account's password is expiredServerMessages.ERR_PWDIFFERENCEVALIDATOR_TOO_SMALLThe provided password differs less than the minimum required difference of %d charactersServerMessages.ERR_PWLENGTHVALIDATOR_TOO_LONGThe provided password is longer than the maximum allowed length of %d charactersServerMessages.ERR_PWLENGTHVALIDATOR_TOO_SHORTThe provided password is shorter than the minimum required length of %d charactersServerMessages.ERR_PWPOLICY_ATTRIBUTE_OPTIONS_NOT_ALLOWEDAttribute options are not allowed for the password attribute %sServerMessages.ERR_PWPOLICY_CANNOT_READ_DICTIONARY_DATAThe dictionary data could not be decompressed: %sServerMessages.ERR_PWPOLICY_CANT_MIX_VALIDATORSCannot use both pwdValidatorPolicy and ds-pwp-validator in subentry '%s'ServerMessages.ERR_PWPOLICY_INVALID_BOOLEANThe value for the '%s' attribute is not a valid booleanServerMessages.ERR_PWPOLICY_INVALID_DURATIONThe value for the '%s' attribute is not a valid durationServerMessages.ERR_PWPOLICY_INVALID_GENERALIZEDTIMEThe value for the '%s' attribute is not a valid timeServerMessages.ERR_PWPOLICY_INVALID_INTEGERThe value for the '%s' attribute is not a valid integerServerMessages.ERR_PWPOLICY_INVALID_STATE_UPDATE_FAILURE_POLICYThe value for the '%s' attribute is not a valid state update failure policyServerMessages.ERR_PWPOLICY_INVALID_STRINGThe value for the '%s' attribute is not a valid stringServerMessages.ERR_PWPOLICY_INVALID_STRINGSThe values for the '%s' attribute are not valid stringsServerMessages.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 ageServerMessages.ERR_PWPOLICY_MULTIPLE_PW_VALUES_NOT_ALLOWEDOnly a single value may be provided for the password attribute %sServerMessages.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 valueServerMessages.ERR_PWPOLICY_NO_PWDPOLICY_OCThe subentry %s must have either the pwdPolicy or ds-pwp-password-policy objectclasses, which is required for the Directory Server password policyServerMessages.ERR_PWPOLICY_PREENCODED_NOT_ALLOWEDPre-encoded passwords are not allowed for the password attribute %sServerMessages.ERR_PWPOLICY_UNDEFINED_ATTRIBUTEThe value for the '%s' attribute is not a valid attributeServerMessages.ERR_PWPOLICY_UNDEFINED_ATTRIBUTESA values for the '%s' attribute is not a valid attribute nameServerMessages.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 ageServerMessages.ERR_PWPSTATE_EXTOP_DECODE_FAILUREAn unexpected error occurred while attempting to decode password policy state extended request value: %sServerMessages.ERR_PWPSTATE_EXTOP_INVALID_OP_ENCODINGAn unexpected error occurred while attempting to decode an operation from the password policy state extended request: %sServerMessages.ERR_PWPSTATE_EXTOP_UNKNOWN_OP_TYPEThe password policy state extended request included an operation with an invalid or unsupported operation type of %sServerMessages.ERR_PWSCHEME_CANNOT_INITIALIZE_SCRAM_ALGThe %s SCRAM password storage scheme could not be initialized because the algorithm is not supported by the JVMServerMessages.ERR_PWSCHEME_DOES_NOT_SUPPORT_AUTH_PASSWORDPassword storage scheme %s does not support use with the authentication password attribute syntaxServerMessages.ERR_PWSCHEME_INVALID_BASE64_DECODED_STORED_PASSWORDThe password value %s has been base64-decoded but is too short to be validServerMessages.ERR_PWSCHEME_INVALID_STORED_PASSWORDAn error occurred while attempting to match a bcrypt hashed password value: %sServerMessages.ERR_PWSCHEME_NOT_REVERSIBLEThe %s password storage scheme is not reversible, so it is impossible to recover the plaintext version of an encoded passwordServerMessages.ERR_RANDOMPWGEN_CANNOT_DETERMINE_CHARSETSAn 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: %sServerMessages.ERR_RANDOMPWGEN_CANNOT_DETERMINE_PWFORMATAn 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: %sServerMessages.ERR_RANDOMPWGEN_INVALID_PWFORMATThe 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 setServerMessages.ERR_RANDOMPWGEN_NO_CHARSETSConfiguration 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 attributeServerMessages.ERR_REBUILDINDEX_ERROR_DURING_REBUILDAn error occurred while attempting to perform index rebuild: %sServerMessages.ERR_REBUILDINDEX_FOR_DNRebuild index aborted: an error has occurred while rebuilding indexes for base DN '%s'ServerMessages.ERR_RECURRING_SCHEDULE_FORMAT_ERRORThe provided schedule value has an invalid format. The schedule must be expressed using a crontab(5) format. Error details: %sServerMessages.ERR_RECURRINGTASK_INVALID_DAY_TOKENThe provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month tokenServerMessages.ERR_RECURRINGTASK_INVALID_HOUR_TOKENThe provided recurring task entry attribute %s holding the recurring task schedule has invalid hour tokenServerMessages.ERR_RECURRINGTASK_INVALID_MINUTE_TOKENThe provided recurring task entry attribute %s holding the recurring task schedule has invalid minute tokenServerMessages.ERR_RECURRINGTASK_INVALID_MONTH_TOKENThe provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year tokenServerMessages.ERR_RECURRINGTASK_INVALID_N_TOKENSThe provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokensServerMessages.ERR_RECURRINGTASK_INVALID_TOKENS_COMBOThe provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar dateServerMessages.ERR_RECURRINGTASK_INVALID_WEEKDAY_TOKENThe provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week tokenServerMessages.ERR_RECURRINGTASK_MULTIPLE_ID_TYPESThe 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 allowedServerMessages.ERR_RECURRINGTASK_MULTIPLE_ID_VALUESThe 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 allowedServerMessages.ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_TYPESThe provided recurring task entry contains multiple attributes with type %s, which is used to hold recurring task schedule, but only a single instance is allowedServerMessages.ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_VALUESThe 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 allowedServerMessages.ERR_RECURRINGTASK_NO_IDThe provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task IDServerMessages.ERR_RECURRINGTASK_NO_ID_ATTRIBUTEThe provided recurring task entry does not contain attribute %s which is needed to hold the recurring task IDServerMessages.ERR_RECURRINGTASK_NO_SCHEDULE_ATTRIBUTEThe provided recurring task entry does not contain attribute %s which is needed to specify recurring task scheduleServerMessages.ERR_RECURRINGTASK_NO_SCHEDULE_VALUESThe provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task scheduleServerMessages.ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe processed ID string %s mapped to multiple usersServerMessages.ERR_REGISTER_BACKEND_ALREADY_EXISTSUnable to register backend %s with the Directory Server because another backend with the same backend ID is already registeredServerMessages.ERR_REINDEX_CANNOT_LOCK_ENTRYThe index(es) cannot be rebuilt because the server failed to obtain a write lock for the entry '%s' after multiple attemptsServerMessages.ERR_REJECT_FILE_EXISTSThe specified reject file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the fileServerMessages.ERR_REMOVE_FAILThe backend database files could not be removed: %sServerMessages.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 %dServerMessages.ERR_REPLICATION_CHANGE_NUMBER_DISABLEDChange number indexing is disabled for replication domain '%s'ServerMessages.ERR_REPLICATION_COULD_NOT_CONNECTThe Replication is configured for suffix %s but was not able to connect to any Replication ServerServerMessages.ERR_REPLICATION_DEAD_LISTENERSThe following replication server listener threads were unexpectedly stopped: %s. A server restart may be neededServerMessages.ERR_REQUEST_DN_DOES_NOT_EXISTThe entry '%s' specified in the request does not exist in the Directory ServerServerMessages.ERR_RESET_GENERATION_ID_FAILEDThe generation ID could not be reset for domain %sServerMessages.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 : %sServerMessages.ERR_ROOT_CONTAINER_NOT_INITIALIZEDThe root container for backend %s has not been initialized preventing this backend from processing the requested operationServerMessages.ERR_ROOTDSE_UNABLE_TO_CREATE_LDIF_WRITERAn unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %sServerMessages.ERR_ROOTDSE_UNABLE_TO_EXPORT_DSEAn unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %sServerMessages.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 reopenedError when initializing publisher of messages in '%s'ServerMessages.ERR_RS_SESSION_WRITER_SUBSCRIPTION_WHILE_SESSION_IS_CLOSEDError when initializing publisher of messages in '%s'ServerMessages.ERR_SASL_AUTHENTRY_NO_MAPPED_ENTRYThe server was unable to find any entry corresponding to authentication ID %sServerMessages.ERR_SASL_AUTHZID_INSUFFICIENT_ACCESSThe authenticating user %s does not have sufficient access to assume a different authorization identityServerMessages.ERR_SASL_AUTHZID_INSUFFICIENT_PRIVILEGESThe authenticating user %s does not have sufficient privileges to assume a different authorization identityServerMessages.ERR_SASL_AUTHZID_NO_MAPPED_ENTRYThe server was unable to find any entry corresponding to authorization ID %sServerMessages.ERR_SASL_AUTHZID_NO_SUCH_ENTRYThe entry %s specified as the authorization identity does not existServerMessages.ERR_SASL_BIND_MULTI_STAGEAn error occurred during multi-stage authentication: '%s'ServerMessages.ERR_SASL_CREATE_SASL_SERVER_FAILEDFailed to create a SASL server for SASL mechanism %sServerMessages.ERR_SASL_GSSAPI_KEYTAB_INVALIDGSSAPI SASL mechanism handler initialization failed because the keytab file %s does not existServerMessages.ERR_SASL_NO_MATCHING_ENTRIESThe server was not able to find any user entries for the provided username of %sServerMessages.ERR_SASL_SCRAM_CANNOT_INITIALIZE_SCRAM_ALGThe %s SCRAM SASL mechanism handler could not be initialized because the algorithm is not supported by the JVMServerMessages.ERR_SASL_USERNAME_IS_NULL_DNThe username in the SASL %s bind request appears to be an empty DN. This is not allowedServerMessages.ERR_SASLEXTERNAL_NO_CERT_IN_ENTRYUnable to authenticate via SASL EXTERNAL because the mapped user entry %s does not have any certificates with which to verify the presented peer certificateServerMessages.ERR_SASLEXTERNAL_PEER_CERT_NOT_FOUNDUnable to authenticate via SASL EXTERNAL because the mapped user entry %s did not contain the peer certificate presented by the clientServerMessages.ERR_SASLGSSAPI_CANNOT_CREATE_JAAS_CONFIGAn error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %sServerMessages.ERR_SASLGSSAPI_CANNOT_CREATE_LOGIN_CONTEXTAn error occurred while attempting to create the JAAS login context for GSSAPI authentication: %sServerMessages.ERR_SASLPLAIN_AUTHZID_INSUFFICIENT_PRIVILEGESThe authenticating user %s does not have sufficient privileges to specify an alternate authorization IDServerMessages.ERR_SASLPLAIN_AUTHZID_NO_MAPPED_ENTRYNo entry corresponding to authorization ID %s was found in the serverServerMessages.ERR_SASLPLAIN_AUTHZID_NO_SUCH_ENTRYThe entry corresponding to authorization DN %s does not exist in the Directory ServerServerMessages.ERR_SASLPLAIN_NO_MATCHING_ENTRIESThe server was not able to find any user entries for the provided authentication ID of %sServerMessages.ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe certificate with subject %s mapped to multiple usersServerMessages.ERR_SATUACM_NO_MAPPABLE_ATTRIBUTESPeer certificate subject %s does not contain any attributes for which a mapping has been establishedServerMessages.ERR_SATUACM_PEER_CERT_NOT_X509Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)ServerMessages.ERR_SCHEMA_ERROR_DETERMINING_SCHEMA_CHANGESAn error occurred while attempting to determine whether any schema changes had been made by directly editing the schema files with the server offline: %sServerMessages.ERR_SCHEMA_INVALID_BASEUnable to retrieve the requested entry %s from the schema backend because the DN is equal to one of the schema entry DNsServerMessages.ERR_SCHEMA_INVALID_MODIFICATION_TYPEThe schema backend does not support the %s modification typeServerMessages.ERR_SCHEMA_INVALID_REPLACE_MODIFICATIONThe schema backend does not support the Replace modification type for the %s attribute typeServerMessages.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 cleanupServerMessages.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 requiredServerMessages.ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_SCHEMAAn error occurred while attempting to write the updated schema: %sServerMessages.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 requiredServerMessages.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 cleanupServerMessages.ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_ATCircular reference detected for attribute type %s in which the superior type chain references the attribute type itselfServerMessages.ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_DSRCircular reference detected for DIT structure rule %s in which the superior rule chain references the DIT structure rule itselfServerMessages.ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_OCCircular reference detected for objectclass %s in which the superior class chain references the objectclass itselfServerMessages.ERR_SCHEMA_MODIFY_DELETE_NO_VALUESThe server will not allow removing all values for the %s attribute type in the server schemaServerMessages.ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_ATTRIBUTE_TYPEUnable to remove attribute type %s from the server schema because no such attribute type is definedServerMessages.ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DCRUnable to remove DIT content rule %s from the server schema because no such DIT content rule is definedServerMessages.ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DSRUnable to remove DIT structure rule %s from the server schema because no such DIT structure rule is definedServerMessages.ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_LSDUnable to remove ldap syntax description %s from the server schema because no such ldap syntax description is definedServerMessages.ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_MR_USEUnable to remove matching rule use %s from the server schema because no such matching rule use is definedServerMessages.ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_NAME_FORMUnable to remove name form %s from the server schema because no such name form is definedServerMessages.ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_OBJECTCLASSUnable to remove objectclass %s from the server schema because no such objectclass is definedServerMessages.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 modifiedServerMessages.ERR_SCHEMA_UNABLE_TO_CREATE_LDIF_WRITERAn unexpected error occurred while trying to open the LDIF writer for the schema backend: %sServerMessages.ERR_SCHEMA_UNABLE_TO_EXPORT_BASEAn error occurred while attempting to export the base schema entry: %sServerMessages.ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_FOR_CLIENTThe certificate with subject %s mapped to multiple usersServerMessages.ERR_SDTUACM_PEER_CERT_NOT_X509Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)ServerMessages.ERR_SEARCH_AUTHZ_INSUFFICIENT_ACCESS_RIGHTSThe entry %s cannot be searched due to insufficient access rightsServerMessages.ERR_SEARCH_BACKEND_EXCEPTIONAn unexpected error was encountered while processing a search in one of the Directory Server backends: %sServerMessages.ERR_SEARCH_BASE_DOESNT_EXISTThe entry %s specified as the search base does not exist in the Directory ServerServerMessages.ERR_SEARCH_CANNOT_GET_ENTRY_FOR_ASSERTIONThe 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: %sServerMessages.ERR_SEARCH_NO_SUCH_OBJECTThe search base entry '%s' does not existServerMessages.ERR_SEARCH_SIZE_LIMIT_EXCEEDEDThis search operation has sent the maximum of %d entries to the clientServerMessages.ERR_SEARCH_TIME_LIMIT_EXCEEDEDThe maximum time limit of %d seconds for processing this search operation has expiredServerMessages.ERR_SEARCH_UNSUPPORTED_CRITICAL_CONTROLThe 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 operationServerMessages.ERR_SEARCHING_DOMAIN_BACKENDAn unexpected error occurred when looking for the replicated backend : %s. It may be not configured or disabledServerMessages.ERR_SEDCM_NO_USER_FOR_DNCould not map the provided certificate chain to a user because no user entry exists with a DN of %sServerMessages.ERR_SEDCM_PEER_CERT_NOT_X509Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s)ServerMessages.ERR_SERVER_BOOTSTRAP_ERRORAn unexpected error occurred while attempting to bootstrap the Directory Server client-side code: %sServerMessages.ERR_SERVER_IS_NOT_ALLOWED_TO_SEND_UPDATESPeer '%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 adjustedServerMessages.ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_LISTENERRegistering Service Discovery Manager's listener failed : %sServerMessages.ERR_SETUP_ACCESSING_PKCS11_KEYSTORECould 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: %sServerMessages.ERR_SETUP_CANNOT_BIND_TO_PORTUnable to bind to port %d. This port may already be in use, or you may not have permission to bind to itServerMessages.ERR_SETUP_CANNOT_BIND_TO_PRIVILEGED_PORTUnable 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 1024ServerMessages.ERR_SETUP_CANNOT_CONFIGURE_GLOBAL_CONFIG_PROPERTYAn error occurred while configuring the server ID or the advertised listen address in global configuration: %sServerMessages.ERR_SETUP_CANNOT_CREATE_PKCS11_KEYMANAGERAn error occurred while creating the PKCS#11 key manager provider: %sServerMessages.ERR_SETUP_CANNOT_ENABLE_KEYMANAGERAn error occurred while attempting to enable key manager provider entry: %sServerMessages.ERR_SETUP_CANNOT_UPDATE_ADMIN_CONNECTOR_PORTAn error occurred while attempting to update the administration connector port: %sServerMessages.ERR_SETUP_CANNOT_UPDATE_CRYPTO_MANAGERAn error occurred while attempting to update the crypto manager in the Directory Server: %sServerMessages.ERR_SETUP_CANNOT_UPDATE_LDAP_PORTAn error occurred while attempting to update the port on which to listen for LDAP communication: %sServerMessages.ERR_SETUP_CANNOT_UPDATE_LDAPS_PORTAn error occurred while attempting to update the port on which to listen for LDAPS communication: %sServerMessages.ERR_SETUP_CANNOT_UPDATE_ROOT_USERAn error occurred while attempting to update the entry for the initial Directory Server root user: %sServerMessages.ERR_SETUP_CLI_TRUSTSTORE_PASSWORD_WITHOUT_FILEThe --%s option should only be provided when using a file based trust store optionServerMessages.ERR_SETUP_CONFIG_FRAMEWORK_INITUnable to bootstrap the Directory Server configuration because of the following error: %sServerMessages.ERR_SETUP_CONFIGURING_PASSWORDAn error occurred while writing password in configuration file: '%s'ServerMessages.ERR_SETUP_COPY_FILE_CHANGE_RIGHTSUnable to set access permissions to allow write operations on file '%s'. Ensure that you have enough rights to change the access permissions on instance filesServerMessages.ERR_SETUP_CREATE_DIRAn error occurred while creating directory '%s'ServerMessages.ERR_SETUP_CREATE_INSTANCE_LOC_FILEAn error occurred while trying to write instance.loc file: %sServerMessages.ERR_SETUP_CREATING_FILE_BASED_TRUST_MANAGER_PROVIDERAn error occurred while creating the file based trust manager provider: %sServerMessages.ERR_SETUP_CREATING_INSTANCE_DIRECTORYUnable to create server instance directory '%s'ServerMessages.ERR_SETUP_DEPLOYMENT_ID_ADD_KEYSTOREUnable to add certificates derived from deployment ID in keystore: %sServerMessages.ERR_SETUP_DISPLAY_LICENSE_FILEUnable to display license because '%s'ServerMessages.ERR_SETUP_DS_MISSING_PROFILE_NAMEOption 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' optionServerMessages.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 nameServerMessages.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 profileServerMessages.ERR_SETUP_ENABLING_HTTP_ACCESS_LOGGERUnable to enable the file based HTTP access logger because: %sServerMessages.ERR_SETUP_ENCODING_PASSWORDUnable to encode provided password because '%s'ServerMessages.ERR_SETUP_FILE_TRUSTSTOREThe provided truststore file '%s' must be an existing readable fileServerMessages.ERR_SETUP_INSTANCE_ALREADY_CONFIGUREDThere 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 pathServerMessages.ERR_SETUP_INSTANCE_PARENT_PATH_NOT_VALID_DIRECTORYThe instance parent (%s) must be a valid existing directoryServerMessages.ERR_SETUP_INTERACTIVE_INVALID_HOST'%s' is not a valid hostnameServerMessages.ERR_SETUP_INTERACTIVE_LICENSE_NOT_ACCEPTEDLicense not accepted, %s will exitServerMessages.ERR_SETUP_INTERACTIVE_NB_TRIES_LIMIT_REACHEDInput tries limit reached (%d)ServerMessages.ERR_SETUP_INTERACTIVE_PROFILE_PARAMETER_INVALIDPlease provide a value having the following syntax: %sServerMessages.ERR_SETUP_INVALID_INSTALL_PATHThe provided server install path '%s' must reference an existing directoryServerMessages.ERR_SETUP_LICENSE_NOT_ACCEPTED_NON_INTERACTIVEYou must accept the product license to run setup. Either use interactive mode or the '--%s' optionServerMessages.ERR_SETUP_MUST_PROVIDE_CERTNICKNAMEThe keystore contains the following certificate nicknames: %s.%nYou have to provide the nickname of the certificate you want to useServerMessages.ERR_SETUP_NO_DEPLOYMENT_ID_PASSWORDThe deployment ID password is missing, provide it with the --%s optionServerMessages.ERR_SETUP_NO_PRIVATE_KEY_IN_KEYSTORENo 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 entriesServerMessages.ERR_SETUP_NO_ROOT_PASSWORDThe root user password is missing, provide it with the --%s optionServerMessages.ERR_SETUP_PASSWORD_FILE_INVALIDThe provided password file '%s' must be an existing readable fileServerMessages.ERR_SETUP_PASSWORD_FILE_MULTIPLE_LINESInvalid content for password file '%s'. A password file must contain a single line with the passwordServerMessages.ERR_SETUP_PORT_ALREADY_SPECIFIEDValue '%d' has been specified for different portsServerMessages.ERR_SETUP_PROFILE_CLI_INITIALIZE_CONFIG_FRAMEWORKAn error occurred while initializing tool: %sServerMessages.ERR_SETUP_PROFILE_CLI_INSTANCE_PATH_NOT_VALIDInstance path '%s' is not a valid existing directoryServerMessages.ERR_SETUP_PROFILE_CLI_NO_DJ_IN_INSTANCE_PATHInstance path '%s' does not contain an OpenDJ instanceServerMessages.ERR_SETUP_PROFILE_CLI_PROFILE_ALREADY_SETUPUnable to setup the profile '%s' because it is already configured in the serverServerMessages.ERR_SETUP_PROFILE_CLI_PROFILES_ALREADY_SETUPUnable to setup profiles '%s' because they are already configured in the serverServerMessages.ERR_SETUP_PROFILE_FILE_NOT_FOUNDUnable to read file '%s'. Please ensure that the file exists and that you have appropriate permissions to read the fileServerMessages.ERR_SETUP_PROFILE_IMPORT_LDIF_WITH_DETAILSUnable to import data (%s)ServerMessages.ERR_SETUP_PROFILE_IMPORT_SAMPLE_ENTRIES_WITH_DETAILSUnable to import generated users (%s)ServerMessages.ERR_SETUP_PROFILE_RESOURCE_FILEUnable to read template file '%s'. Please ensure that the file exists and that you have appropriate permissions to read the fileServerMessages.ERR_SETUP_REPLICATION_CONFIGURATIONAn error occurred while configuring replication: %sServerMessages.ERR_SETUP_SERVER_ID_SYNTAXServer ID '%s' is not valid. A Server ID is an ASCII alpha-numeric string possibly containing underscore and hyphen charactersServerMessages.ERR_SETUP_UNABLE_TO_EDIT_JAVA_HOMEUnable to edit runtime settings file because '%s'ServerMessages.ERR_SETUP_UNABLE_TO_READ_INSTANCE_PATHAn error occurred while trying to read instance.loc file: %sServerMessages.ERR_SETUP_UNABLE_TO_READ_KEYSTORE_FILEThe provided keystore file '%s' must be an existing readable fileServerMessages.ERR_SETUP_UNEXPECTEDAn unexpected error has been raised during setup: '%s'ServerMessages.ERR_SETUP_UPDATING_HTTP_PORTAn error occurred while attempting to update the HTTP connector port: '%s'ServerMessages.ERR_SETUP_UPDATING_HTTPS_PORTAn error occurred while attempting to update the HTTPS connector: '%s'ServerMessages.ERR_SKIP_FILE_EXISTSThe specified skip file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the fileServerMessages.ERR_SKIPPING_LOG_FILESkipping log "%s" (unsupported config)ServerMessages.ERR_SMTP_ASNH_NO_MAIL_SERVERS_CONFIGUREDThe 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 serversServerMessages.ERR_SMTP_ASNH_NO_RECIPIENTSSMTP 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 providedServerMessages.ERR_SOFTREFCACHE_CANNOT_INITIALIZEA fatal error occurred while trying to initialize soft reference entry cache: %sServerMessages.ERR_SORTREQ_CONTROL_CANNOT_PROCESSUnable to process the provided server-side sort request control: %sServerMessages.ERR_START_DATETIME_ALREADY_PASSEDThe specified start time '%s' has already passedServerMessages.ERR_STATICGROUP_GROUP_INSTANCE_INVALIDGroup instance with DN %s has been deleted and is no longer validServerMessages.ERR_STATICGROUP_NO_VALID_OCEntry %s cannot be parsed as a valid static group because it does not contain the groupOfEntries, groupOfNames or groupOfUniqueNames object classesServerMessages.ERR_STATUS_PRINT_SCRIPT_FRIENDLY_OUTPUTAn error occurred while printing server status script friendly output: %sServerMessages.ERR_STATUS_READ_LOCAL_SERVER_CONFIGURATIONAn error occurred while reading the server configuration: %sServerMessages.ERR_STOPDS_DATETIME_ALREADY_PASSEDThe specified stop time '%s' has already passedServerMessages.ERR_STOPDS_IO_ERRORERROR: An I/O error occurred while attempting to communicate with the Directory Server: %sServerMessages.ERR_SUPPORT_EXTRACT_TASK_ERRORSThere was at least one error during the tasks execution: %sServerMessages.ERR_TASK_ADDSCHEMAFILE_CANNOT_LOCK_SCHEMAUnable 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 attemptsServerMessages.ERR_TASK_ADDSCHEMAFILE_SCHEMA_VALIDATION_ERRORThe changes made by the add schema file task failed schema validation: %sServerMessages.ERR_TASK_CLIENT_TASK_STATE_UNKNOWNState for task '%s' cannot be determinedServerMessages.ERR_TASK_CLIENT_UNCANCELABLE_TASKTask '%s' has finished and cannot be canceledServerMessages.ERR_TASK_CLIENT_UNKNOWN_TASKThere are no tasks defined with ID '%s'ServerMessages.ERR_TASK_DISCONNECT_INVALID_CONN_IDUnable to decode value %s as an integer connection IDServerMessages.ERR_TASK_DISCONNECT_INVALID_NOTIFY_CLIENTUnable 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'ServerMessages.ERR_TASK_DISCONNECT_NO_CONN_IDAttribute %s must be provided to specify the connection ID for the client to disconnectServerMessages.ERR_TASK_DISCONNECT_NO_SUCH_CONNECTIONThere is no client connection with connection ID %sServerMessages.ERR_TASK_INITIALIZE_INVALID_DNInvalid DN provided to the Initialize task: %sServerMessages.ERR_TASK_INITIALIZE_TARGET_INVALID_DNInvalid DN provided to the Initialize Target task: %sServerMessages.ERR_TASK_PURGE_CONFLICTS_INVALID_DNInvalid DN provided to the Purge Conflicts Historical task: %sServerMessages.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 serverServerMessages.ERR_TASK_RESET_CHANGE_NUMBER_FAILEDUnable to reset the change number index: %sServerMessages.ERR_TASK_RESET_CHANGE_NUMBER_INVALIDInvalid change number (%d) specified, it must be greater than zeroServerMessages.ERR_TASK_RESET_GENERATION_ID_INVALID_DNInvalid DN provided to the Reset Generation ID task: %sServerMessages.ERR_TASK_TOOL_ERROR_CODEtool exit with error return code '%d'ServerMessages.ERR_TASK_TOOL_START_TIME_NO_LDAPYou 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'ServerMessages.ERR_TASKBE_BACKING_FILE_EXISTSThe 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 pathServerMessages.ERR_TASKBE_DELETE_INVALID_ENTRYUnable 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 entryServerMessages.ERR_TASKBE_DELETE_NO_SUCH_RECURRING_TASKUnable to remove entry %s from the task backend because there is no recurring task associated with that entry DNServerMessages.ERR_TASKBE_DELETE_NO_SUCH_TASKUnable to remove entry %s from the task backend because there is no scheduled task associated with that entry DNServerMessages.ERR_TASKBE_DELETE_RUNNINGUnable to delete entry %s from the task backend because the associated task is currently runningServerMessages.ERR_TASKBE_ERROR_GETTING_BACKING_FILEAn error occurred while attempting to determine the new path to the task data backing file: %sServerMessages.ERR_TASKBE_INVALID_BACKING_FILE_PATHThe 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 fileServerMessages.ERR_TASKBE_MODIFY_COMPLETEDEntry %s cannot be modified because the associated task has completed running. Completed tasks cannot be modifiedServerMessages.ERR_TASKBE_MODIFY_INVALID_ENTRYEntry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backendServerMessages.ERR_TASKBE_MODIFY_NO_SUCH_TASKEntry %s cannot be modified because it does not represent a valid task in the serverServerMessages.ERR_TASKBE_MODIFY_RECURRINGEntry %s cannot be modified because the server does not currently support modifying recurring task entriesServerMessages.ERR_TASKBE_MODIFY_RUNNINGThe 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"ServerMessages.ERR_TASKBE_SEARCH_INVALID_BASEUnable to process the search operation in the task backend because the provided base DN %s is not valid for entries in the task backendServerMessages.ERR_TASKBE_SEARCH_NO_SUCH_RECURRING_TASKUnable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %sServerMessages.ERR_TASKBE_SEARCH_NO_SUCH_TASKUnable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %sServerMessages.ERR_TASKINFO_INVALID_MENU_KEYInvalid menu item or task number '%s'ServerMessages.ERR_TASKINFO_NOT_CANCELABLE_TASK_INDEXTask at index %d is not cancelableServerMessages.ERR_TASKINFO_TASK_NOT_CANCELABLE_TASKError: task %s is not in a cancelable stateServerMessages.ERR_TASKINFO_UNKNOWN_TASK_ENTRYThere are no tasks with ID %sServerMessages.ERR_TASKS_CANNOT_EXPORT_TO_FILEAn error occurred while attempting to export task backend data: %sServerMessages.ERR_TASKSCHED_DUPLICATE_RECURRING_IDUnable to add recurring task %s to the task scheduler because another recurring task already exists with the same IDServerMessages.ERR_TASKSCHED_DUPLICATE_TASK_IDUnable to schedule task %s because another task already exists with the same IDServerMessages.ERR_TASKSCHED_MULTIPLE_CLASS_TYPESThe provided task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowedServerMessages.ERR_TASKSCHED_MULTIPLE_CLASS_VALUESThe 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 allowedServerMessages.ERR_TASKSCHED_NO_CLASS_ATTRIBUTEThe provided task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logicServerMessages.ERR_TASKSCHED_NO_CLASS_VALUESThe 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 logicServerMessages.ERR_TASKSCHED_NOT_ALLOWED_TASKThe Directory Server is not configured to allow task %s to be invokedServerMessages.ERR_TASKSCHED_REMOVE_COMPLETED_NO_SUCH_TASKUnable to remove completed task %s because no such task exists in the list of completed tasksServerMessages.ERR_TASKSCHED_REMOVE_PENDING_NO_SUCH_TASKUnable to remove pending task %s because no such task existsServerMessages.ERR_TASKSCHED_REMOVE_PENDING_NOT_PENDINGUnable to remove pending task %s because the task is no longer pendingServerMessages.ERR_TASKTOOL_OPTIONS_FOR_TASK_ONLYThe option %s is only applicable when scheduling this operation as a taskServerMessages.ERR_TRUSTSTORESYNC_EXCEPTIONAn error occurred in the trust store synchronization thread: %sServerMessages.ERR_UNABLE_TO_LOAD_CONFIGURATION_ENABLED_SCHEMAUnable to load the configuration-enabled schema: %sServerMessages.ERR_UNABLE_TO_PURGE_ENTRIESAn unexpected error occurred while purging expired entries: %sServerMessages.ERR_UNABLE_TO_RETRIEVE_CHILDREN_OF_CONFIGURATION_ENTRYUnable to retrieve children of configuration entry with dn: %sServerMessages.ERR_UNCHECKED_EXCEPTIONUnchecked exception during database transaction: %sServerMessages.ERR_UNEXPECTED_INTERRUPT_WHILE_PUBLISHINGPublish of a replication message to server '%s' was interruptedServerMessages.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 %dServerMessages.ERR_UNKNOWN_DNThe base DN %s is not stored by any of the Directory Server backendServerMessages.ERR_UNKNOWN_EXCEPTION_DURING_TOOL_EXECUTIONAn unexpected error has been raised during execution of the tool: '%s'ServerMessages.ERR_UNKNOWN_TYPEUnknown operation type : %sServerMessages.ERR_UNRECOGNIZED_RECORD_VERSIONCannot decode change-log record with version %xServerMessages.ERR_UPGRADE_CANNOT_REMOVE_REFERENCES_TO_DS_TASK_BACKUP_ALL'%s' attributes couldn't be removed from backup tasksAttribute 'ds-backup-directory-path' could not be renamed to 'ds-backup-location' in entries of objectclass '%s'ServerMessages.ERR_UPGRADE_CONFIG_ERROR_UPGRADE_FOLDERAn error occurred when trying to upgrade the config/upgrade folder: %sServerMessages.ERR_UPGRADE_CORRUPTED_TEMPLATE'%s' is missing or empty, it is probably corruptedServerMessages.ERR_UPGRADE_DATA_UP_TO_DATEOpenDJ data has already been upgraded to version %sServerMessages.ERR_UPGRADE_DISPLAY_CONFIRM_ERRORAn unexpected error occurred while attempting to display a confirmation : %sServerMessages.ERR_UPGRADE_DISPLAY_NOTIFICATION_ERRORAn unexpected error occurred while attempting to display a notification: %sServerMessages.ERR_UPGRADE_FAILSThe upgrade failed because %d errors were encountered. Please check log for further detailsServerMessages.ERR_UPGRADE_INVALID_LOG_FILEInvalid log file %sServerMessages.ERR_UPGRADE_MAIN_UPGRADE_PROCESSThe upgrade failed to complete for the following reason: %sServerMessages.ERR_UPGRADE_READING_CONF_FILEAn error occurred while reading configuration file: %sServerMessages.ERR_UPGRADE_TASK_CANNOT_READ_CHANGELOG_FILESAn error occurred reading the changelog files: %sServerMessages.ERR_UPGRADE_TASK_CANNOT_RENAME_CHANGELOG_FILESAn error occurred while renaming the changelog files: %sServerMessages.ERR_UPGRADE_TASK_CANNOT_UPGRADE_ENCRYPTED_CHANGELOGAn error occurred while migrating encrypted changelog files: %sServerMessages.ERR_UPGRADE_TASK_MIGRATE_OFFLINEAn error occurred while migrating replicas' offline states to the changelog files: %sServerMessages.ERR_UPGRADE_TASKS_FAILAn error occurred while performing an upgrade task: %sServerMessages.ERR_UPGRADE_VERSION_UP_TO_DATEOpenDJ has already been upgraded to version %sServerMessages.ERR_UPLOAD_CLOUD_PROVIDER_MESSAGEAn error occurred while uploading the file to the cloud storage. The cloud provider returned the following error message: '%s'ServerMessages.ERR_UPLOAD_UNKNOWN_HOSTAn error occurred while uploading the file to the cloud storage: the host '%s' is an unknown hostServerMessages.ERR_VATTR_NOT_SEARCHABLEThe %s attribute is not searchable and should not be included in otherwise unindexed search filtersServerMessages.ERR_VERIFY_DN2ID_MISSING_KEYFile dn2id is missing key %sServerMessages.ERR_VERIFY_EMPTY_IDSETEmpty ID set: %n%sServerMessages.ERR_VERIFY_ID2COUNT_WRONG_IDFile id2ChildrenCount references non-existing EntryID <%d>ServerMessages.ERR_VERIFYINDEX_ERROR_DURING_VERIFYAn error occurred while attempting to perform index verification: %sServerMessages.ERR_VERSION_MALFORMEDThe version of the installed OpenDJ could not be determined because the version file '%s' exists but contains invalid data. Restore it from backup before continuingServerMessages.ERR_VERSION_NOT_FOUNDThe version of the installed OpenDJ could not be determined because the version file '%s' could not be found. Restore it from backup before continuingServerMessages.ERR_VIRTUAL_STATIC_GROUP_ALTERING_MEMBERS_NOT_SUPPORTEDAltering membership for virtual static group %s is not allowedServerMessages.ERR_VIRTUAL_STATIC_GROUP_MULTIPLE_TARGETSThe virtual static group defined in entry %s contains multiple target group DNs, but only one is allowedServerMessages.ERR_VIRTUAL_STATIC_GROUP_NO_TARGETThe virtual static group defined in entry %s does not contain a target group definitionServerMessages.ERR_VLV_BAD_ASSERTIONUnable to process the virtual list view request because the target assertion could not be decoded as a valid value for the '%s' attribute typeServerMessages.ERR_VLV_INDEX_NOT_CONFIGUREDThere is no VLV index configured with name '%s'ServerMessages.ERR_WINDOWS_SERVICE_CLEANUP_ERRORAn unexpected error occurred cleaning up the service %sServerMessages.ERR_WINDOWS_SERVICE_CLEANUP_NOT_FOUNDCould not find the service with name %sServerMessages.ERR_WINDOWS_SERVICE_ENABLING_ERROR_STARTING_SERVERThe Windows Service was successfully configured but there was an error starting it. Error code starting Windows Service: %dServerMessages.ERR_WRITER_UNEXPECTED_EXCEPTIONAn unexpected error happened handling connection with %s. This connection is going to be closedServerMessages.ERROR_COULD_NOT_FIND_ADS_CERTIFICATECould not find 'ads-certificate' entry in the truststore '%s'. This entry is required for the correct behavior of the directory serverServerMessages.ERROR_DSREPL_ERROR_LAUNCHING_INITIALIZATIONAn error occurred when launching initialization: %sServerMessages.ERROR_DSREPL_INITIALIZATION_DURING_INIT_TASK_WITHOUT_LOGAn error occurred during initialization. Task state: %sError during the processing of the reset generationID task. Task state: %sServerMessages.ERROR_DSREPL_POLLING_TASKAn error occurred while attempting to monitor the task progress. The error was: %sServerMessages.ERROR_DSREPL_PURGE_METADATA_DURING_TASK_WITHOUT_LOGAn error occurred while purging old replication meta-data. Task state: %sServerMessages.ERROR_DSREPL_PURGE_METADATA_ERROR_LAUNCHINGAn error occurred while purging old replication meta-data: %sServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_DURING_TASK_WITHOUT_LOGAn error occurred during the re-synchronization of the change number. Task state: %sServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_ERROR_LAUNCHINGAn error occurred when re-synchronizing the change number: %sServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_ERROR_WHEN_SEARCHING_DOMAINAn error occurred when searching replicated domains in server: %sServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_BASE_DN_FOUNDNo base DN found for the change number '%s' in the source serverServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_CSN_FOUNDNo CSN found for the change number '%s' in the source serverServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_NO_MATCHING_DOMAIN_FOUNDUnable to find a replicated domain matching the DN '%s' corresponding to the change numberServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_UNKNOWN_CNUnable to retrieve change number '%s' in the source serverAn error occurred when searching replicated domains in server. Result code was: '%s'ServerMessages.ERROR_LOADING_JAVA_PROPERTIESError while loading "java.properties": %sServerMessages.ERROR_SETUP_PROFILE_PARAMETER_WITHOUT_PROFILEParameter '%s' is provided without any profile specification which is not allowed when multiple profiles are usedServerMessages.INFO_ACI_ADD_LIST_GLOBAL_ACISAdded %s Global Access Control Instruction (ACI) attribute types to the access control evaluation engineServerMessages.INFO_ACI_HANDLER_FAIL_PROCESS_ACIAn unexpected error occurred while processing the aci attributes in the configuration system: %sServerMessages.INFO_ADDING_FILEAdding %sServerMessages.INFO_ARCHIVE_HAS_BEEN_WRITTENThe following archive has been created : %sServerMessages.INFO_CANCELED_BY_ABANDON_REQUESTThe operation was canceled because the client issued an abandon request (message ID %d) for this operationServerMessages.INFO_CHANGELOG_CURSOR_INVALIDATEDCursor on replica '%s' invalidatedServerMessages.INFO_CHANGELOG_STAT_ARGUMENTSArguments for changelogstat: %sServerMessages.INFO_CNI_CAN_INDEX_AGAINChange number indexing will resume since replica '%s' is now sending messages againServerMessages.INFO_COLLECTING_JVM_HEAPDUMPCollecting JVM heap dump : using %sServerMessages.INFO_COLLECTING_PROCESS_THREAD_INFOCollecting process thread information, sample number : %dServerMessages.INFO_CONFIG_BACKEND_DISABLEDThe backend defined in configuration entry %s is marked as disabled and therefore will not be usedServerMessages.INFO_CONFIG_PWPOLICY_REMOVED_POLICYPassword 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 authenticateServerMessages.INFO_CONFIG_UPGRADE_SUCCESSFULOpenDJ configuration was successfully upgraded to version %sServerMessages.INFO_CONTINUING_PROCESSINGContinuing data gathering though there was an error: %sServerMessages.INFO_COPYING_SERVEROUT_FILEMaking copy of the %s file before collecting process statisticsServerMessages.INFO_DATA_UPGRADE_FROM_DEFAULT_VERSION_SUMMARYOpenDJ data will be upgraded to version %sServerMessages.INFO_DATA_UPGRADE_SUCCESSFULOpenDJ data was successfully upgraded to version %sServerMessages.INFO_DELETING_SERVEROUTCOPY_FILERemoving file copy %sServerMessages.INFO_DESCRIPTION_DS_REPL_TOOLThis 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' subcommandServerMessages.INFO_DIGEST_MD5_REALMDIGEST-MD5 SASL mechanism using a realm of: %sServerMessages.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:ServerMessages.INFO_DSREPL_CLEANUP_MIGRATED_CLEANUP_CONFIGURATIONCleaning and updating configuration of server %sServerMessages.INFO_DSREPL_CLEANUP_MIGRATED_DISABLE_ADMIN_BACKENDDisable admin backend for server %sServerMessages.INFO_DSREPL_CLEANUP_MIGRATED_SECONDARY_CLEANUP_DONEThe server %s has now been cleanedServerMessages.INFO_DSREPL_CLEANUP_MIGRATED_SET_BOOTSTRAP_SERVERS_CONFIGSet bootstrap servers configuration for server %sServerMessages.INFO_DSREPL_CLEANUP_MIGRATED_WRONG_BIND_DNThe 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 serverServerMessages.INFO_DSREPL_DR_COMPUTED_ID_NO_PROMPTDisaster recovery id: %sServerMessages.INFO_DSREPL_DR_ENDED_SUCCESSFULLYDisaster recovery for base DN '%s' ended successfully on this serverServerMessages.INFO_DSREPL_DR_STARTEDStarting disaster recovery on local server for base DN '%s'ServerMessages.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 valueServerMessages.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 certificatesServerMessages.INFO_DSREPL_MIGRATION_CONFIGURING_REPLICATION_DOMAINUpdating replication configuration for baseDN '%s' on local serverServerMessages.INFO_DSREPL_MIGRATION_CREATE_REPLICATION_TRUST_MANAGERCreating the trust manager '%s' to be used by replication connections in the local serverServerMessages.INFO_DSREPL_RESET_CHANGE_NUMBER_SELECTED_CNRe-synchronizing with change number '%s'ServerMessages.INFO_DSREPL_START_BASE_DN_INITIALIZATIONStarting initialization for base DN: '%s'ServerMessages.INFO_ERGONOMIC_SIZING_OF_WORKER_THREAD_POOLNo worker queue thread pool size specified: sizing automatically to use %d threadsServerMessages.INFO_ERROR_CONFIGURING_CERTIFICATEAn error occurred while configuring the certificates: %sServerMessages.INFO_ERROR_INSTALLING_BACKUP_CLOUD_EXTENSIONSError Installing Backup Cloud Extension for Directory Server: %sServerMessages.INFO_ERROR_STARTING_SERVER_CODEError Starting Directory Server. Error code: %sServerMessages.INFO_EXTERNAL_LIB_MESSAGE%sServerMessages.INFO_EXTERNAL_PROCESS_STARTLaunch external process: '%s'ServerMessages.INFO_EXTERNAL_PROCESS_STDOUTExternal process standard output: %sServerMessages.INFO_EXTOP_CANCEL_REASONProcessing on this operation was terminated as a result of receiving a cancel request (message ID %d)ServerMessages.INFO_GENERAL_PROVIDE_LOG_IN_ERRORSee %s for a detailed log of the failed operation.%nPlease report this error and provide the log file mentioned aboveServerMessages.INFO_GSSAPI_PRINCIPAL_NAMEGSSAPI mechanism using a principal name of: %sServerMessages.INFO_GSSAPI_SERVER_FQDNGSSAPI SASL mechanism using a server fully qualified domain name of: %sServerMessages.INFO_INDEX_FILTER_INDEX_LIMIT_EXCEEDEDThe filter value exceeded the index entry limit for the %s indexServerMessages.INFO_INDEX_FILTER_INDEX_NOT_TRUSTED%s index is invalid and needs to be rebuiltServerMessages.INFO_INITIALIZE_PROGRESS_WITH_PROCESSED%s entries processedServerMessages.INFO_INITIALIZE_PROGRESS_WITH_UNPROCESSED%s remaining to be processedServerMessages.INFO_LABEL_BACKEND_TOOL_INDEX%nIndex: %s%nServerMessages.INFO_LABEL_BACKEND_TOOL_KEY_FORMATKey (len %d):ServerMessages.INFO_LABEL_BACKEND_TOOL_OVER_INDEX_LIMIT_KEYSOver index-entry-limit keys: %s%nServerMessages.INFO_LABEL_BACKEND_TOOL_TOTAL%nTotal: %d%nServerMessages.INFO_LABEL_BACKEND_TOOL_TOTAL_RECORDS%nTotal Records: %d%nServerMessages.INFO_LABEL_BACKEND_TOOL_VALUE_FORMATValue (len %d):ServerMessages.INFO_LDIF_CONNHANDLER_ERROR_MESSAGEAdditional Info: %sServerMessages.INFO_LDIF_CONNHANDLER_MATCHED_DNMatched DN: %sServerMessages.INFO_LDIF_CONNHANDLER_REFERRAL_URLReferral URL: %sServerMessages.INFO_LDIFEXPORT_PATH_TO_LDIF_FILEExporting to %sServerMessages.INFO_LIST_OF_LOGGING_CATEGORIESThe following logging categories are defined for the server: %sServerMessages.INFO_PLUGIN_REFERENT_BACKGROUND_PROCESSING_STARTINGThe Referential Integrity plugin has started background processing using the update interval %sServerMessages.INFO_PLUGIN_REFERENT_SEARCH_NO_SUCH_OBJECTThe Referential Integrity plugin failed when performing a search because the base DN %s does not existServerMessages.INFO_PROXY_PRIMARY_SERVERS_AVAILABLEThe primary servers for proxy backend '%s' are now available and will be used for proxying requestsServerMessages.INFO_PROXY_SECONDARY_SERVERS_AVAILABLEThe secondary servers for proxy backend '%s' are now available and will be used if the primary servers are unavailableServerMessages.INFO_PURGE_DELAY_MODIFIEDThe purge delay has been set to: %sServerMessages.INFO_SERVEROUT_NOT_FOUND_ERRSkipping backup of %s log (file not found)ServerMessages.INFO_SETUP_DESCRIPTION_AVAILABLE_PROFILESAvailable setup profiles: %sServerMessages.INFO_SETUP_DESCRIPTION_PROFILESetup 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. %sServerMessages.INFO_SETUP_INTERACTIVE_BOOTSTRAP_RS_PORTReplication port on %sServerMessages.INFO_SETUP_INTERACTIVE_CONFIGURE_PROFILEConfigure server for profile '%s'ServerMessages.INFO_SETUP_INTERACTIVE_ENABLE_PORTListening on port %dServerMessages.INFO_SETUP_INTERACTIVE_HOME_SCREENWelcome 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 hostname for '%s'Provide port for '%s'ServerMessages.INFO_SETUP_INTERACTIVE_MULTI_ALIASES_KEYSTOREThe 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'?No value specified for '%s'ServerMessages.INFO_SETUP_INTERACTIVE_PROFILE_CONFIRM_THEConfirm the %s:ServerMessages.INFO_SETUP_INTERACTIVE_PROFILE_PARAMETER_GENERIC_DESCValue set for '%s'ServerMessages.INFO_SETUP_INTERACTIVE_PROFILE_PARAMETER_GENERIC_PROMPTProvide a value for '%s'ServerMessages.INFO_SETUP_INTERACTIVE_PROFILES_PROMPT_WITH_DEFAULTEnter profile number(s) separated by comma [%s]:ServerMessages.INFO_SETUP_INTERACTIVE_PROMPT_CERTNICKNAMEUse nickname %s?Do you want to set a value for parameter '%s'?ServerMessages.INFO_SETUP_PROFILE_CLI_USAGE_DESCRIPTIONThis utility configures profiles in an offline OpenDJ server instance. %sServerMessages.INFO_SETUP_PROFILE_PARAMETER_SYNTAX_EXPRESSION_ALLOWED%s or configuration expressionServerMessages.INFO_SETUP_RUN_PROFILEConfiguring profile %sServerMessages.INFO_SETUP_STATUS_COMMAND_LINETo see basic server status and configuration, you can launch %sServerMessages.INFO_SKIPPING_FILESkipping %sServerMessages.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 keyServerMessages.INFO_TASK_SHUTDOWN_DEFAULT_MESSAGEThe Directory Server shutdown process has been initiated by task %sServerMessages.INFO_TASK_STOPPED_BY_ADMINTask was stopped by an administrator: %sServerMessages.INFO_TASKBE_UPDATED_BACKING_FILEThe 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 updatesServerMessages.INFO_TASKBE_UPDATED_RETENTION_TIMEThe completed task retention time has been updated to %d seconds. This will take effect immediatelyServerMessages.INFO_TASKINFO_CMD_CANCEL_SUCCESSTask %s canceledServerMessages.INFO_TASKINFO_LDAP_EXCEPTIONError connecting to the directory server: '%s'. Verify that the connection options are correct and that the server is runningServerMessages.INFO_TASKINFO_OPTIONS%s OptionsServerMessages.INFO_TIME_IN_SECONDS%d secondsServerMessages.INFO_UPGRADE_ADD_HDAP_AUTH_MECHANISM_CONFIGAdd a new HDAP authorization mechanism '%s'ServerMessages.INFO_UPGRADE_CLASSES_FOLDER_RENAMEDThe classes folder has been renamed to '%s' to avoid compatibility issuesServerMessages.INFO_UPGRADE_DELETE_HTTP_AUTH_MECHANISMS_CONFIGRemoving deprecated HTTP Basic DN and JWT authorization mechanisms. The HDAP authorization mechanism '%s' replaces themServerMessages.INFO_UPGRADE_GENERAL_SEE_FOR_DETAILSSee '%s' for a detailed log of this operationServerMessages.INFO_UPGRADE_NO_CHANGE_DONE_IN_SPECIFIC_FILE...No change applied in %sServerMessages.INFO_UPGRADE_NO_INDEX_TO_REBUILD_FOR_BACKENDNo indexes to rebuild for backend '%s'ServerMessages.INFO_UPGRADE_OPTION_FORCEForces 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' optionServerMessages.INFO_UPGRADE_REBUILD_INDEX_ARGUMENTSThe rebuild index tool arguments are %sServerMessages.INFO_UPGRADE_REBUILD_INDEXES_DECLINEDYou have to rebuild the '%s' index(es) manually to get a fully functional serverServerMessages.INFO_UPGRADE_REMOVE_REFERENCES_TO_DS_TASK_BACKUP_ALLRemoving '%s' attribute(s) from backup tasksServerMessages.INFO_UPGRADE_SUCCESSFULOpenDJ was successfully upgraded to version %sServerMessages.INFO_UPGRADE_TASK_ADD_CONFIG_ENTRYAdding configuration entry '%s'ServerMessages.INFO_UPGRADE_TASK_ADD_CONFIG_FILEAdding '%s' configuration fileServerMessages.INFO_UPGRADE_TASK_DELETE_FILERemoving file '%s'ServerMessages.INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_SUMMARYMigrating root DN '%s'ServerMessages.INFO_UPGRADE_TASK_NEEDS_USER_CONFIRM%s.%nDo you want to make this change?ServerMessages.INFO_UPGRADE_TASK_PDB_TO_JE_1_SUMMARYWARNING: 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 completesServerMessages.INFO_UPGRADE_TASK_REMOVE_PIN_FILE_WARNINGThe 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 entryRename attribute 'ds-backup-directory-path' to 'ds-backup-location' in entries of objectClass '%s'ServerMessages.INFO_UPGRADE_TASK_REPLACE_SCHEMA_FILEReplacing schema file '%s'ServerMessages.INFO_UPGRADE_VERSION_IS_NOT_SUPPORTEDThis 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 upgradesServerMessages.INFO_VERIFY_AVERAGE_REFERENCE_COUNTAverage number of entries referenced is %.2f/recordServerMessages.INFO_VERIFY_ENTRY_LIMIT_EXCEEDED_COUNTNumber of records that exceed the entry limit: %dServerMessages.INFO_VERIFY_MAX_REFERENCE_COUNTMaximum number of entries referenced by any record is %dServerMessages.INFO_VERIFY_MULTIPLE_REFERENCE_COUNTNumber of records referencing more than one entry: %dServerMessages.INFO_WINDOWS_SERVICE_CLEANUP_SUCCESSClean up of service %s was successfulServerMessages.INFO_WINDOWS_SERVICE_DESCRIPTIONNext Generation Directory Server. Installation path: %sServerMessages.INFO_WINDOWS_SERVICE_ENABLEDThe server is enabled as a Windows service. The service name for the server is: %sServerMessages.INFO_WINDOWS_SERVICE_NAME%sServerMessages.INFO_WORKER_STOPPED_BY_REDUCED_THREADNUMBER%s has been stopped because the total number of worker threads in the Directory Server was reducedServerMessages.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 serverServerMessages.NOTE_AVAILABLE_PROCESSORSAvailable Processors: %dServerMessages.NOTE_BACKEND_OFFLINEThe backend %s is now taken offlineServerMessages.NOTE_BUILD_IDBuild ID: %sServerMessages.NOTE_CONFIG_AUTHZ_ENABLEDAccess control has been enabled and will use the %s implementationServerMessages.NOTE_CONFIG_INDEX_CONFIDENTIALITY_REQUIRES_REBUILDChanging confidentiality for index '%s' requires the index to be rebuilt before it can be used againServerMessages.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 limitServerMessages.NOTE_CONNHANDLER_STARTED_LISTENINGStarted listening for new connections on %sServerMessages.NOTE_CONNHANDLER_STOPPED_LISTENINGStopped listening for new connections on %sServerMessages.NOTE_CURRENT_DIRECTORYCurrent Directory: %sServerMessages.NOTE_DIGEST_MD5_SERVER_FQDNDIGEST-MD5 SASL mechanism using a server fully qualified domain name of: %sServerMessages.NOTE_ERR_FRACTIONAL_CONFIG_PROHIBITED_ATTRIBUTEWrong fractional replication configuration : prohibited attribute %s usageServerMessages.NOTE_ERR_FRACTIONAL_CONFIG_UNKNOWN_ATTRIBUTE_TYPEWrong fractional replication configuration : could not find attribute type definition for %s in schemaServerMessages.NOTE_ERR_FRACTIONAL_CONFIG_UNKNOWN_OBJECT_CLASSWrong fractional replication configuration: could not find object class definition for %s in schemaServerMessages.NOTE_ERR_FRACTIONAL_CONFIG_WRONG_FORMATWrong fractional replication configuration : wrong format : %s (need at least [<className>|*],attributeName)ServerMessages.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 serverServerMessages.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 serverServerMessages.NOTE_FRACTIONAL_BAD_DATA_SET_NEED_RESYNCWarning : domain %s fractional replication configuration is inconsistent with backend data set : need resynchronization or fractional configuration to be changedServerMessages.NOTE_FREE_MEMORYCurrently Free Memory: %dServerMessages.NOTE_IMPORT_LDIF_INDEX_CLOSEIndex %s phase two processing completedServerMessages.NOTE_IMPORT_LDIF_ROOTCONTAINER_CLOSEImport LDIF environment close took %d secondsServerMessages.NOTE_IMPORT_THREAD_COUNTImport Thread Count: %d threadsServerMessages.NOTE_INDEX_ADD_REQUIRES_REBUILDDue to changes in the configuration, index %s is currently operating in a degraded state and must be rebuilt before it can be usedServerMessages.NOTE_INSTALL_DIRECTORYInstallation Directory: %sServerMessages.NOTE_INSTANCE_DIRECTORYInstance Directory: %sServerMessages.NOTE_JAVA_CLASSPATHClass Path: %sServerMessages.NOTE_JAVA_HOMEJAVA Home: %sServerMessages.NOTE_JAVA_VENDORJAVA Vendor: %sServerMessages.NOTE_JAVA_VERSIONJAVA Version: %sServerMessages.NOTE_JVM_ARCHJVM Architecture: %sServerMessages.NOTE_JVM_ARGSJVM Arguments: %sServerMessages.NOTE_JVM_VENDORJVM Vendor: %sServerMessages.NOTE_JVM_VERSIONJVM Version: %sServerMessages.NOTE_MAX_MEMORYMax Available Memory: %dServerMessages.NOTE_OPERATING_SYSTEMOperating System: %sServerMessages.NOTE_PROXY_CONNECTION_OPTIONS_CHANGEDConnection options have changed for the proxy backend '%s'. The existing connections are being closed immediately. New ones are being openedServerMessages.NOTE_PROXY_CONNECTION_POOL_OPTIONS_CHANGEDConnection pool options have changed for the proxy backend '%s'. The existing connections are being closed and re-openedServerMessages.NOTE_REBUILD_ALL_STARTRebuild of all indexes started with %d total entries to processServerMessages.NOTE_REBUILD_CLEARDEGRADEDSTATE_FINAL_STATUSDegraded state of index(es) %s has been clearedServerMessages.NOTE_REBUILD_DEGRADED_STARTRebuild of all degraded indexes started with %d total entries to processServerMessages.NOTE_REFERRAL_RESULT_MESSAGEA referral entry %s indicates that the operation must be processed at a different serverServerMessages.NOTE_RESENDING_INIT_FROM_REMOTE_REQUESTResending a new initialization request for an initialization from a remote server due to the root error : %sServerMessages.NOTE_SYSTEM_NAMESystem Name: %sServerMessages.NOTE_TOTAL_MEMORYCurrently Used Memory: %dServerMessages.NOTE_VERSION%sServerMessages.NOTICE_GLOBAL_ACCESS_CONTROL_ADDEDThe global access control policy '%s' has been addedServerMessages.NOTICE_GLOBAL_ACCESS_CONTROL_CHANGEDThe global access control policy '%s' has been modifiedServerMessages.NOTICE_GLOBAL_ACCESS_CONTROL_DELETEDThe global access control policy '%s' has been removedServerMessages.NOTICE_GLOBAL_ACCESS_CONTROL_INITIALIZEDThe global access control engine has been initialized with %d policiesServerMessages.SETUP_MAIN_COMMAND_DESCRIPTIONThis utility sets up an OpenDJ server. Use the %s option to list available profilesServerMessages.WARN_ACI_NOT_VALID_DNSelfwrite check skipped because an attribute "%s" with a distinguished name syntax was not a valid DNServerMessages.WARN_ACI_SERVER_DECODE_FAILEDFailed to decode the Access Control Instruction (ACI)%sServerMessages.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 parenthesisServerMessages.WARN_ACI_SYNTAX_GENERAL_PARSE_FAILEDThe provided string "%s" could not be parsed as a valid Access Control Instruction (ACI) because it failed general ACI syntax evaluationServerMessages.WARN_ACI_SYNTAX_INVALID_ACCESS_TYPE_VERSIONThe provided Access Control Instruction access type value "%s" is invalid. A valid access type value is either allow or denyServerMessages.WARN_ACI_SYNTAX_INVALID_ATTRIBUTE_TYPE_NAMEThe 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 "-" characterServerMessages.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 GSSAPIServerMessages.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"ServerMessages.WARN_ACI_SYNTAX_INVALID_BIND_RULE_KEYWORDThe 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 authmethodServerMessages.WARN_ACI_SYNTAX_INVALID_BIND_RULE_OPERATORThe provided Access Control Instruction (ACI) bind rule operator value "%s" is invalid. A valid bind rule operator value is either '=' or "!="ServerMessages.WARN_ACI_SYNTAX_INVALID_BIND_RULE_SYNTAXThe 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"ServerMessages.WARN_ACI_SYNTAX_INVALID_DAYOFWEEKThe 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 satServerMessages.WARN_ACI_SYNTAX_INVALID_DNS_EXPRESSIONThe 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 nameServerMessages.WARN_ACI_SYNTAX_INVALID_DNS_WILDCARDThe 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 nameServerMessages.WARN_ACI_SYNTAX_INVALID_GROUPDN_EXPRESSIONThe 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]ServerMessages.WARN_ACI_SYNTAX_INVALID_GROUPDN_URLThe provided Access Control Instruction (ACI) bind rule groupdn expression value failed to URL decode for the following reason: %sServerMessages.WARN_ACI_SYNTAX_INVALID_INHERITANCE_VALUEThe provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid because it is non-numericServerMessages.WARN_ACI_SYNTAX_INVALID_IP_EXPRESSIONThe 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 expressionServerMessages.WARN_ACI_SYNTAX_INVALID_IPV4_FORMATThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" format was invalidServerMessages.WARN_ACI_SYNTAX_INVALID_IPV4_VALUEThe 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 255ServerMessages.WARN_ACI_SYNTAX_INVALID_NETMASKThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid valueServerMessages.WARN_ACI_SYNTAX_INVALID_NETMASK_FORMATThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid formatServerMessages.WARN_ACI_SYNTAX_INVALID_PREFIX_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 formatServerMessages.WARN_ACI_SYNTAX_INVALID_PREFIX_VALUEThe 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 addressesServerMessages.WARN_ACI_SYNTAX_INVALID_RIGHTS_KEYWORDThe 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 allServerMessages.WARN_ACI_SYNTAX_INVALID_RIGHTS_SYNTAXThe 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 parenthesesServerMessages.WARN_ACI_SYNTAX_INVALID_SSF_RANGEThe 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 1024ServerMessages.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"ServerMessages.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: 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 filterServerMessages.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 statementsServerMessages.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 listsServerMessages.WARN_ACI_SYNTAX_INVALID_TARGET_KEYWORDThe 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 targattrfiltersServerMessages.WARN_ACI_SYNTAX_INVALID_TARGET_SYNTAXThe 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"ServerMessages.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 supportedServerMessages.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]ServerMessages.WARN_ACI_SYNTAX_INVALID_TARGETFILTERKEYWORD_EXPRESSIONThe provided Access Control Instruction (ACI) targetfilter expression value "%s" is invalid because it is not a valid LDAP filterServerMessages.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_patternServerMessages.WARN_ACI_SYNTAX_INVALID_TARGETS_OPERATORThe provided Access Control Instruction (ACI) target keyword operator value "%s" is invalid. A valid target keyword operator value is either '=' or "!="ServerMessages.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 subordinateServerMessages.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]ServerMessages.WARN_ACI_SYNTAX_INVALID_TIMEOFDAYThe 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)ServerMessages.WARN_ACI_SYNTAX_INVALID_TIMEOFDAY_RANGEThe 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)ServerMessages.WARN_ACI_SYNTAX_INVALID_USERATTR_ATTR_URLThe 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 emptyServerMessages.WARN_ACI_SYNTAX_INVALID_USERATTR_BASEDN_URLThe provided Access Control Instruction (ACI) bind rule userattr expression value failed to parse because the ldap URL "%s" contains an empty base DNServerMessages.WARN_ACI_SYNTAX_INVALID_USERATTR_EXPRESSIONThe provided Access Control Instruction (ACI) bind rule userattr expression value "%s" is invalidServerMessages.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#bindTypeServerMessages.WARN_ACI_SYNTAX_INVALID_USERATTR_URLThe provided Access Control Instruction (ACI) bind rule userattr expression value failed to URL decode for the following reason: %sServerMessages.WARN_ACI_SYNTAX_INVALID_USERDN_URLThe provided Access Control Instruction (ACI) bind rule userdn expression failed to URL decode for the following reason: %sServerMessages.WARN_ACI_SYNTAX_INVALID_VERSIONThe provided Access Control Instruction (ACI) version value "%s" is invalid, only the version 3.0 is supportedServerMessages.WARN_ACI_SYNTAX_IPV4_NOT_NUMERICThe provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" contains a non-numeric valueServerMessages.WARN_ACI_SYNTAX_IPV6_WILDCARD_INVALIDThe 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 expressionServerMessages.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"ServerMessages.WARN_ACI_SYNTAX_PREFIX_NOT_NUMERICThe 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 valueServerMessages.WARN_ACI_SYNTAX_ROLEDN_NOT_SUPPORTEDThe 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 keywordServerMessages.WARN_ACI_TARGETATTR_INVALID_ATTR_TOKENThe provided Access Control Instruction (ACI) targetattr expression value "%s" is invalid because the expression contains invalid or duplicate tokensServerMessages.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 storageServerMessages.WARN_BIND_MULTIPLE_USER_CURSOR_ENTRY_LIMITSThere are multiple user-specific cursor entry limit values contained in user entry '%s'. The default server cursor entry limit will be usedServerMessages.WARN_BIND_MULTIPLE_USER_IDLE_TIME_LIMITSThere are multiple user-specific idle time limit values contained in user entry %s. The default server idle time limit will be usedServerMessages.WARN_BIND_MULTIPLE_USER_SIZE_LIMITSThere are multiple user-specific size limit values contained in user entry %s. The default server size limit will be usedServerMessages.WARN_BIND_MULTIPLE_USER_TIME_LIMITSThere are multiple user-specific time limit values contained in user entry %s. The default server time limit will be usedServerMessages.WARN_BIND_PASSWORD_EXPIRINGThe user password is about to expire (time to expiration: %s)ServerMessages.WARN_CHANGELOG_NOT_ENABLED_FOR_WRITEThe changelog '%s' has been opened in read-only mode, it is not enabled for writeServerMessages.WARN_CLIENTCONNECTION_DISCONNECT_DUE_TO_DELETETerminating the client connection because its associated authentication or authorization entry %s has been deletedServerMessages.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: %sServerMessages.WARN_CONFIG_ARCHIVE_FILE_INVALIDThe latest archived configuration file %s appears to be invalid. Forcing creation of a new oneServerMessages.WARN_CONFIG_PLUGIN_EMPTY_ELEMENT_IN_ORDERThe plugin order definition for plugins of type %s contains an empty element. This may cause the plugin order to be evaluated incorrectlyServerMessages.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 incorrectlyServerMessages.WARN_CONFIG_PLUGIN_ORDER_NO_WILDCARDThe 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 pluginsServerMessages.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 removedServerMessages.WARN_COULD_NOT_READ_ADMIN_BACKENDUnable to look up server key id '%s' in the admin backendServerMessages.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: %sServerMessages.WARN_CRYPTO_MGR_NOT_FOUND_USE_DEFAULTUnable to find configuration for crypto manager "%s", replication SSL configuration will use default valuesServerMessages.WARN_DECODING_INTERNAL_MODIFICATION_CONTROLAn error occurred while decoding a internal modification control: %sServerMessages.WARN_DECODING_REPLICATED_REQUEST_CONTROLAn error occurred while decoding a replicated request control: %sServerMessages.WARN_DSREPL_DR_UNKNOWN_DOMAIN_FOR_RSThe local replication server never received changes for base DN '%s'. Make sure you are running the disaster recovery on the right serverServerMessages.WARN_ERROR_LOGGER_INVALID_CATEGORYInvalid error log category "%s"ServerMessages.WARN_ERROR_LOGGER_INVALID_OVERRIDE_SEVERITYInvalid override of severity level "%s"ServerMessages.WARN_ERROR_LOGGER_INVALID_SEVERITYInvalid error log severity "%s"ServerMessages.WARN_ERROR_LOGGER_INVALID_SEVERITY_MULTIPLE_VALUESInvalid error log severity "%s", only one severity must be provided, the highest one at which logging should occurServerMessages.WARN_GET_ENTRY_COUNT_FAILEDUnable to determine the total number of entries in the container: %sServerMessages.WARN_INVALID_SYNC_HIST_VALUEThe attribute value '%s' is not a valid synchronization history valueServerMessages.WARN_LDAP_CLIENT_DUPLICATE_MESSAGE_IDThe Directory Server is already processing another request on the same client connection with the same message ID of %dServerMessages.WARN_PATTERN_DN_CONSECUTIVE_WILDCARDS_IN_VALUEThe pattern DN %s is not valid because it contains two consecutive wildcards in an attribute valueServerMessages.WARN_PATTERN_DN_TYPE_CONTAINS_SUBSTRINGSThe 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 typeServerMessages.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 RDNServerMessages.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 usedSettings for Replica '%s' should provide a hostnameServerMessages.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 againServerMessages.WARN_TASKSCHED_DUPLICATE_TASK_IDUnable to add completed task %s to the task scheduler because another task already exists with the same IDServerMessages.WARN_TRUSTSTORE_BACKEND_NOT_FOUND_USE_DEFAULTUnable to find configuration for truststore backend "%s", using default values insteadServerMessages.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 errorServerMessages.WARN_WINDOWS_SERVICE_CLEANUP_MARKED_FOR_DELETIONService %s has been marked for deletion -
Uses of LocalizableMessageDescriptor.Arg1 in org.opends.server.types
Methods in org.opends.server.types with parameters of type LocalizableMessageDescriptor.Arg1Modifier and TypeMethodDescriptionprotected voidOperation.checkAttributeConformsToSyntax(Entry entry, Attribute attribute, LocalizableMessageDescriptor.Arg4<Object, Object, Object, Object> invalidSyntaxErrorMsg, LocalizableMessageDescriptor.Arg3<Object, Object, Object> invalidSyntaxNoValueErrorMsg, LocalizableMessageDescriptor.Arg1<Object> rejectErrorMsg) Checks whether an attribute's values conform to its syntax.protected voidOperation.checkIfBackendIsWritable(Dn entryDN, LocalizableMessageDescriptor.Arg1<Object> serverMsg, LocalizableMessageDescriptor.Arg1<Object> backendMsg) Checks if an update operation can be performed against a backend. -
Uses of LocalizableMessageDescriptor.Arg1 in org.opends.server.util
Methods in org.opends.server.util with parameters of type LocalizableMessageDescriptor.Arg1Modifier and TypeMethodDescriptionstatic Collection<LocalizableMessage>SslUtils.verifySslCiphersAndProtocols(Collection<String> cipherSuites, Collection<String> protocols, LocalizableMessageDescriptor.Arg1<Object> cipherError, LocalizableMessageDescriptor.Arg1<Object> protocolError) Verifies all the specified SSL cipher suites and protocols are available in the current JVM.