Uses of Class
org.forgerock.i18n.LocalizableMessageDescriptor.Arg2
Packages that use LocalizableMessageDescriptor.Arg2
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 various classes that comprise the core of the Directory Server codebase.
Contains implementations for various Directory Server tasks.
-
Uses of LocalizableMessageDescriptor.Arg2 in org.forgerock.i18n.slf4j
Methods in org.forgerock.i18n.slf4j with parameters of type LocalizableMessageDescriptor.Arg2Modifier and TypeMethodDescription<T1,T2> void LocalizedLogger.error(LocalizableMessageDescriptor.Arg2<T1, T2> d, T1 a1, T2 a2) Logs an error message.<T1,T2> void LocalizedLogger.info(LocalizableMessageDescriptor.Arg2<T1, T2> d, T1 a1, T2 a2) Logs a message at INFO level.<T1,T2> void LocalizedLogger.note(LocalizableMessageDescriptor.Arg2<T1, T2> d, T1 a1, T2 a2) Logs a message at NOTICE level.<T1,T2> void LocalizedLogger.warn(LocalizableMessageDescriptor.Arg2<T1, T2> d, T1 a1, T2 a2) Logs a warning message. -
Uses of LocalizableMessageDescriptor.Arg2 in org.forgerock.opendj.rest2ldap
Fields in org.forgerock.opendj.rest2ldap declared as LocalizableMessageDescriptor.Arg2Modifier and TypeFieldDescriptionRest2ldapMessages.ERR_ABSTRACT_AUXILIARY_TYPE_IN_CREATEThe resource cannot be created because it specified the abstract auxiliary resource type '%s'. Please specify one of the following non-abstract auxiliary types: %sRest2ldapMessages.ERR_ABSTRACT_TYPE_IN_CREATEThe resource cannot be created because it specified the abstract resource type '%s'. Please specify one of the following non-abstract types: %sRest2ldapMessages.ERR_BAD_API_RESOURCE_VERSIONThe requested resource API version '%s' is unsupported. This endpoint only supports the following resource API version(s): %sRest2ldapMessages.ERR_CONFIG_INVALID_AUTHZID_TEMPLATEInvalid authorization ID template: '%s'.Templates must start with one of the following elements: %sRest2ldapMessages.ERR_CONFIG_INVALID_KEY_MANAGERThe key-manager defined in '%s' is invalid: %sRest2ldapMessages.ERR_CONFIG_INVALID_TRUST_MANAGERThe trust-manager defined in '%s' is invalid: %sRest2ldapMessages.ERR_CONFIG_OAUTH2_INVALID_INTROSPECT_URLThe token introspection endpoint '%s' is not a valid URL: '%s'Rest2ldapMessages.ERR_CONFIG_OAUTH2_UNSUPPORTED_ACCESS_TOKEN_RESOLVER'%s'is not a supported access token resolver. Must be one of '%s'Rest2ldapMessages.ERR_CONFIG_UNSUPPORTED_BIND_STRATEGYUnsupported bind strategy '%s'. Must be one of '%s'Rest2ldapMessages.ERR_ENCODING_VALUES_FOR_FIELDThe request cannot be processed because an error occurred while encoding the values for the field '%s': '%s'Rest2ldapMessages.ERR_HDAP_JWT_CLAIM_DOES_NOT_CONTAINThe given JWT claim '%s' does not contain the value '%s'Rest2ldapMessages.ERR_HDAP_JWT_DEFAULT_SECRET_STOREUnable to create a secret store for the purposes '%s' with the default JWS algorithm '%s'Rest2ldapMessages.ERR_HDAP_JWT_NO_KEY_FOUNDThe key '%s' is configured as valid but is not found: %sRest2ldapMessages.ERR_HDAP_JWT_REQUIRES_KEYSTORE_CONFIGA keystore is required: as a keyAlias '%s' is defined in the servlet JWT configuration, the configuration should also declare a 'security/keyManager' with one of these values: %sRest2ldapMessages.ERR_HDAP_UNKNOWN_BIND_MECHANISMUnknown bindMechanism '%s' declared in the HDAP configuration '%s'Rest2ldapMessages.ERR_ILLEGAL_FILTER_ASSERTION_VALUEThe request cannot be processed because it contained an illegal filter assertion value '%s' for field '%s'Rest2ldapMessages.ERR_JSON_QUERY_PARSE_ERROR_UNRECOGNIZED_FILTER_OPERATORThe value '%s' could not be parsed as a valid JSON query filter because it contained an unrecognized or unsupported filter operator '%s'Rest2ldapMessages.ERR_LOCAL_SORT_AND_PAGE_INVALID_PAGINATIONLocal sorting and pagination fails: the resulting ordered page '%s' has more elements than '%d' (pageSize + 1)Rest2ldapMessages.ERR_MODIFY_READ_ONLY_FIELDThe %s request cannot be processed because it attempts to modify the read-only field '%s'Rest2ldapMessages.ERR_MVCC_VERSIONS_MISMATCHThe resource could not be accessed because the expected version '%s' does not match the current version '%s'Rest2ldapMessages.ERR_OAUTH2_CTS_INVALID_TOKEN_TYPEThe token '%s' must be an access token, but it is a '%s'Rest2ldapMessages.ERR_OAUTH2_CTS_TOKEN_NOT_FOUNDUnable to find the token '%s' in the CTS because: '%s'Rest2ldapMessages.ERR_OAUTH2_CTS_TOKEN_RESOLUTIONUnable to resolve access token '%s' due to the following reason: '%s'Rest2ldapMessages.ERR_OAUTH2_FILE_INVALID_JSON_TOKENMalformed token file '%s'. Details: '%s'Rest2ldapMessages.ERR_REFERENCE_CANNOT_BE_UPDATEDThe request cannot be processed because it attempts to update the properties of referenced resource(s) '%s' through the resource '%s'. Update the referenced resource with these values through a direct request.Rest2ldapMessages.ERR_REFERENCE_FIELD_AMBIGUOUSThe request cannot be processed because the resource '%s' referenced in field '%s' is ambiguousRest2ldapMessages.ERR_REFERENCE_FIELD_DOES_NOT_EXISTThe request cannot be processed because the resource '%s' referenced in field '%s' does not existRest2ldapMessages.ERR_REMOVE_REQUIRED_FIELDThe %s request cannot be processed because it attempts to remove the required field '%s'Rest2ldapMessages.ERR_REVERSE_PROPERTY_NOT_FOUNDThe reverseReference property mapper for property "%s" specifies a property which is not a "reference" property in the resource "%s"Rest2ldapMessages.ERR_RUNTIME_EXCEPTIONA runtime exception occurred while processing the request '%s': '%s'Rest2ldapMessages.ERR_SCHEMA_UNRECOGNIZED_NAMEThe schema element requested for '%s' is not recognized: '%s'Rest2ldapMessages.ERR_UNABLE_LOAD_SCHEMAUnable to load the LDAP schema: %s. Next attempt at %sRest2ldapMessages.ERR_UNRECOGNIZED_AUXILIARY_TYPE_IN_CREATEThe resource cannot be created because it specified an auxiliary resource type '%s' which is not permitted by this resource. Please specify one of the following auxiliary types: %sRest2ldapMessages.ERR_UNRECOGNIZED_FILTER_OPERATORThe query request cannot be processed because its query filter '%s' contained an unrecognized or unsupported filter operator '%s'Rest2ldapMessages.ERR_UNRECOGNIZED_RESOURCE_AUXILIARY_TYPEThe resource '%s' has an unrecognized auxiliary type '%s'Rest2ldapMessages.ERR_UNRECOGNIZED_RESOURCE_SUPER_TYPEThe resource '%s' has an unrecognized super-type '%s'Rest2ldapMessages.ERR_UNRECOGNIZED_SUB_RESOURCE_TYPEThe resource '%s' references an unrecognized sub-resource '%s'Rest2ldapMessages.ERR_UNRECOGNIZED_TYPE_IN_CREATEThe resource cannot be created because it specified an unrecognized resource type '%s'. Please specify one of the following types: %sRest2ldapMessages.INFO_HDAP_CREATING_ENDPOINTHDAP created endpoint '%s' version %sRest2ldapMessages.INFO_REST2LDAP_CREATING_ENDPOINTRest2Ldap created endpoint '%s' version %s -
Uses of LocalizableMessageDescriptor.Arg2 in org.opends.messages
Fields in org.opends.messages declared as LocalizableMessageDescriptor.Arg2Modifier and TypeFieldDescriptionServerMessages.DSBACKUP_BACKEND_NAME_OR_BACKUP_ID_ARG_MISSINGEither the --%s or --%s argument must be providedServerMessages.DSBACKUP_BACKUP_SUCCESSFULBackup completed for backend '%s' with backup ID '%s'The attempt to remove backend files from directory '%s' has failed, backend '%s' may contain corrupted data, please remove the files manuallyServerMessages.DSBACKUP_CANNOT_COMPUTE_BACKEND_FILE_FINGERPRINTCannot compute the fingerprint for backend file '%s': %sServerMessages.DSBACKUP_CANNOT_CREATE_BACKEND_DIRECTORYCannot create the backend directory '%s' before restoring: %sServerMessages.DSBACKUP_CANNOT_DELETE_BACKEND_FILESCannot delete backend files from directory '%s': %sServerMessages.DSBACKUP_CANNOT_DELETE_LOCK_FILECannot delete the backup lock file '%s', please remove this file manually: %sServerMessages.DSBACKUP_CANNOT_READ_BACKEND_FILESCannot read backend files in directory '%s': %sServerMessages.DSBACKUP_CREATE_CANNOT_LOCK_BACKENDCannot acquire a shared lock for backend '%s': %s. This generally means that some other process has exclusive access to this backend (e.g., a restore or an LDIF import)ServerMessages.DSBACKUP_CREATE_CANNOT_UNLOCK_BACKENDCannot release the shared lock for backend '%s': %s. This lock should automatically be cleared when the backup process exits, so no further action should be requiredServerMessages.DSBACKUP_CREATE_REQUESTED_BACKENDS_DO_NOT_SUPPORT_BACKUPThe following backends do not support backups: %s. Here is the list of enabled backends that support backups: %sServerMessages.DSBACKUP_CREATE_REQUESTED_BACKENDS_NOT_ENABLEDThe following backends do not exist or are disabled: %s. Here is the list of enabled backends that support backups: %sServerMessages.DSBACKUP_ERROR_DURING_BACKUPAn error occurred while attempting to backup backend '%s': %sServerMessages.DSBACKUP_FILE_IS_CORRUPTEDFile '%s' is corrupted: %sServerMessages.DSBACKUP_IO_EXCEPTION_WITH_FILEProblem with file '%s' : %sServerMessages.DSBACKUP_PURGE_ARG_CAN_ONLY_BE_USED_WITH_OTHER_ARGThe option '--%s' can only be used with the option '--%s'ServerMessages.DSBACKUP_PURGE_BACKEND_FILES_ERRORAn error occurred while attempting to purge backup files starting with '%s': %sServerMessages.DSBACKUP_PURGE_BACKEND_NAME_DESCRIPTIONPurge only backups of the specified backend. Specify this option multiple times to allow purging backups of different backends. Skip this option to allow purging backups of all backends. This can only be used with options '--%s' or '--%s'ServerMessages.DSBACKUP_PURGE_ERRORAn error occurred while attempting to purge the backup '%s': %sServerMessages.DSBACKUP_PURGE_KEEPCOUNT_ARG_EXCEPTIONInvalid value for '%s': %sServerMessages.DSBACKUP_RESTORE_CANNOT_LOCK_BACKENDCannot acquire an exclusive lock for backend '%s': %s. This generally means some other process is still using this backend (e.g., it is in use by the Directory Server or a backup or LDIF export is in progress)ServerMessages.DSBACKUP_RESTORE_CANNOT_UNLOCK_BACKENDCannot release the exclusive lock for backend '%s': %s. This lock should automatically be cleared when the restore process exits, so no further action should be requiredServerMessages.DSBACKUP_RESTORE_STARTSStarting restore for backend '%s' with backup ID '%s'ServerMessages.DSBACKUP_RESTORE_SUCCESSFULRestore completed for backend '%s' with backup ID '%s'ServerMessages.DSBACKUP_RESTORE_WARN_CANNOT_ACTIVATE_BACKENDCannot enable backend '%s' after restoring: %sServerMessages.DSBACKUP_STORAGE_PROPERTY_ARG_ONLY_ONE_VALUEThe storage property '%s' has several values while it can have only one. The provided properties string was: "%s"ServerMessages.ERR_ADD_ATTR_IS_INVALID_OPTIONEntry %s can not be added because BER encoding of %s attribute is not supportedServerMessages.ERR_ADD_ATTR_IS_NO_USER_MODEntry %s cannot be added because it includes attribute %s which is defined as NO-USER-MODIFICATION in the server schemaServerMessages.ERR_ADD_MISSING_RDN_ATTRIBUTEEntry %s cannot be added because it is missing attribute %s that is contained in the entry's RDN. All attributes used in the RDN must also be provided in the attribute list for the entryServerMessages.ERR_ADD_NO_PARENTEntry %s cannot be added because its parent entry %s does not exist in the serverServerMessages.ERR_ADD_PARENT_IS_SUBENTRYEntry %s cannot be added because its parent entry %s is a subentryServerMessages.ERR_ADD_UNSUPPORTED_CRITICAL_CONTROLEntry %s cannot be added because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operationServerMessages.ERR_ADMIN_DATA_TRUSTMANAGER_KEYSTORE_READ_ALIAS_FAILUREAn unexpected error occurred while attempting to read the instance key '%s' in "cn=admin data": %sServerMessages.ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_PERIODThe provided value "%s" could not be parsed as a valid distinguished name because the parsed attribute name %s included a period but that name did not appear to be a valid OIDServerMessages.ERR_ATTR_SYNTAX_DN_ATTR_VALUE_DECODE_FAILUREThe provided value "%s" could not be parsed as a valid distinguished name because an unexpected failure occurred while attempting to parse an attribute value from one of the RDN components: "%s"ServerMessages.ERR_ATTR_SYNTAX_DN_END_WITH_ATTR_NAMEThe provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was part of the attribute name '%s'ServerMessages.ERR_ATTR_SYNTAX_DN_INVALID_HEX_DIGITThe provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with an octothorpe (#) but contained a character %c that was not a valid hexadecimal digitServerMessages.ERR_BACKEND_ADD_NOT_SUPPORTEDUnwilling to add entry "%s" because add operations are not supported in the "%s" backendServerMessages.ERR_BACKEND_CANNOT_CHANGE_CONFIDENTIALITYConfidentiality cannot be disabled on suffix '%s' because the following indexes have confidentiality still enabled: %sServerMessages.ERR_BACKEND_CANNOT_REGISTER_BASEDNSAn error occurred while attempting to register the base DNs %s in the Directory Server: %sServerMessages.ERR_BACKEND_CONFIG_CACHE_PERCENT_GREATER_THAN_JVM_HEAPConfiguration attribute ds-cfg-db-cache-percent has a value of %d%% but the JVM has only %d%% availableServerMessages.ERR_BACKEND_CONFIG_CACHE_SIZE_GREATER_THAN_JVM_HEAPConfiguration attribute ds-cfg-db-cache-size has a value of %d but the JVM has only %d available. Consider using ds-cfg-db-cache-percentServerMessages.ERR_BACKEND_DEBUG_CANNOT_LOCK_BACKENDAn error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has exclusive access to this backend (e.g., a restore or an LDIF import)ServerMessages.ERR_BACKEND_DEBUG_DECODE_BASE_DNUnable to decode base DN string "%s" as a valid distinguished name: %sServerMessages.ERR_BACKEND_DEBUG_NO_ENTRY_CONTAINERS_FOR_BASE_DNNone of the entry containers are configured with the requested base DN %s in backend %sServerMessages.ERR_BACKEND_DELETE_NOT_SUPPORTEDUnwilling to remove entry "%s" because delete operations are not supported in the "%s" backendServerMessages.ERR_BACKEND_ENTRY_DOESNT_EXISTEntry %s does not exist in the "%s" backendServerMessages.ERR_BACKEND_LIST_FILES_TO_BACKUPAn error occurred while trying to list the files to backup for backend '%s': %sServerMessages.ERR_BACKEND_MODIFY_DN_NOT_SUPPORTEDUnwilling to rename entry "%s" because modify DN operations are not supported in the "%s" backendServerMessages.ERR_BACKEND_MODIFY_NOT_SUPPORTEDUnwilling to update entry "%s" because modify operations are not supported in the "%s" backendServerMessages.ERR_BACKEND_SEARCH_ENTRYAn error occurred when searching for %s : %sServerMessages.ERR_BACKEND_TOOL_CURSOR_AT_KEY_NUMBERAt key number %d, %s:ServerMessages.ERR_BACKEND_TOOL_ERROR_INITIALIZING_BACKENDAn unexpected error occurred while attempting to initialize the backend '%s': %sServerMessages.ERR_BACKEND_TOOL_EXECUTING_COMMANDAn error occurred while trying to execute %s: %sServerMessages.ERR_BACKEND_TOOL_NO_TREE_FOR_NAME_IN_STORAGENo storage index exists with the requested name %s in backend %sServerMessages.ERR_BACKUP_CANNOT_LIST_LOG_FILESAn error occurred while attempting to obtain a list of the files in directory %s to include in the backup: %sServerMessages.ERR_BAD_ADMIN_API_RESOURCE_VERSIONThe requested admin API version '%s' is unsupported. This endpoint only supports the following admin API version(s): %sServerMessages.ERR_BIND_OPERATION_INSECURE_SASL_BINDRejecting a SASL %s bind request for user %s because the password policy requires secure authenticationServerMessages.ERR_CANNOT_ACQUIRE_EXCLUSIVE_SERVER_LOCKThe Directory Server could not acquire an exclusive lock on file %s: %s. This generally means that another instance of this server is already runningServerMessages.ERR_CANNOT_DECODE_BASE_DNUnable to decode base DN string "%s" as a valid distinguished name: %sServerMessages.ERR_CANNOT_DECODE_CONTROL_VALUECannot decode the provided control %s because an error occurred while attempting to decode the control value: %sServerMessages.ERR_CANNOT_DECODE_PRINCIPAL_AS_DNCould not map the provided certificate chain to a user becausethe peer certificate issuer "%s" could not be decoded as an LDAP DN: %sServerMessages.ERR_CANNOT_READ_CONFIG_VERSIONAn error occurred when trying to read the configuration version in %s : %sServerMessages.ERR_CANNOT_READ_UPGRADE_NUMBERAn error occurred when trying to read the upgrade version in second line of file '%s' (%s)ServerMessages.ERR_CANNOT_RECOVER_CHANGESError when searching old changes from the database for base DN %s: %sServerMessages.ERR_CANT_LOCATE_JAVA_CMDCould not find the "%s" command in "%s"ServerMessages.ERR_CERTIFICATE_ISSUER_DOES_NOT_MATCHCould not map the provided certificate chain to a user because the matching user entry with DN '%s' does not contain an issuer DN matching the certificate issuer DN '%s'ServerMessages.ERR_CHANGELOG_BACKEND_UNEXPECTED_MESSAGE_TYPEUnexpected message type when trying to create changelog entry for dn %s: '%s'ServerMessages.ERR_CHANGELOG_INCOHERENT_DOMAIN_STATEThere is a mismatch between domain state file and actual domain directories found in file system. Expected domain ids : %s. Actual domain ids found in file system: %sServerMessages.ERR_CHANGELOG_INVALID_REPLICA_OFFLINE_STATE_FILECould not read replica offline state file '%s' for domain %s, it should contain exactly one line corresponding to the offline CSNServerMessages.ERR_CHANGELOG_LOG_FILE_IS_NOT_READABLEAn error occurred while verifying integrity of log file '%s' : %sServerMessages.ERR_CHANGELOG_READ_STATE_CANT_READ_DOMAIN_DIRECTORYError when retrieving changelog state from root path '%s' : IO error on domain directory '%s' when retrieving list of server idsServerMessages.ERR_CHANGELOG_RESET_CHANGE_NUMBER_CSN_TOO_OLDThe change number could not be reset to %d because the associated change with CSN '%s' has already been purged from the change log. Try resetting to a more recent changeServerMessages.ERR_CHANGELOG_STAT_CANNOT_LIST_CHANGELOG_FILESCannot list the changelog files in '%s': %sServerMessages.ERR_CHANGELOG_STAT_ERROR_WHEN_DECODING_CHANGELOG_FILEError while decoding the changelog file '%s' : %sServerMessages.ERR_CHANGELOG_STAT_ERROR_WHEN_READING_RS_ENTRYAn error occurred when reading the replication server configuration entry '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_CREATE_GENERATION_ID_FILECould not create generation id file '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_CREATE_LAST_LOG_ROTATION_TIME_FILECould not create file '%s' to store last log rotation time %dServerMessages.ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_DIRECTORYCould not create root directory '%s' for log file: %sServerMessages.ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_FILECould not create log file '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_DECODE_DN_FROM_DOMAIN_STATE_FILECould not decode DN from domain state file '%s', from line '%s'ServerMessages.ERR_CHANGELOG_UNABLE_TO_INITIALIZE_LOGCould not initialize the log '%s' : %sServerMessages.ERR_CHANGELOG_UNABLE_TO_OPEN_LOG_FILECould not open log file '%s' for write: %sServerMessages.ERR_CHANGELOG_UNABLE_TO_OPEN_READER_ON_LOG_FILECould not open a reader on log file '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_READ_DOMAIN_STATE_FILECould not read domain state file '%s'. The replication server cannot continue, it should be restored from a backup. Cause was : %sServerMessages.ERR_CHANGELOG_UNABLE_TO_READ_REPLICA_OFFLINE_STATE_FILECould not read content of replica offline state file '%s' for domain %sServerMessages.ERR_CHANGELOG_UNABLE_TO_RECOVER_LOG_FILEAn error occurred while recovering the replication change log file '%s'. The recovery has been aborted and this replication server will be removed from the replication topology. The change log file system may be read-only, full, or corrupt and must be fixed before this replication server can be used. The underlying error was: %sServerMessages.ERR_CHANGELOG_UNABLE_TO_RETRIEVE_KEY_BOUNDS_FROM_FILECould not retrieve key bounds from log file '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_RETRIEVE_READ_ONLY_LOG_FILES_LISTCould not retrieve read-only log files from log '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_SEEKCould not seek to position %d for reader on log file '%s'ServerMessages.ERR_CHANGELOG_UNABLE_TO_SYNCCould not synchronize written records to file system for log file '%s': %sServerMessages.ERR_CHARSET_CONSTRUCTOR_INVALID_NAME_CHARThe named character set is invalid because the provide name "%s" has an invalid character at position %d. Only ASCII alphabetic characters are allowed in the nameServerMessages.ERR_CHARSET_VALIDATOR_DUPLICATE_CHARThe provided character set definition '%s' is invalid because it contains character '%s' which has already been usedServerMessages.ERR_CHARSET_VALIDATOR_MALFORMED_RANGEThe provided character range definition '%s' is invalid because the range '%s' is missing the minusServerMessages.ERR_CHARSET_VALIDATOR_SHORT_RANGEThe provided character range definition '%s' is invalid because the range '%s' is too shortServerMessages.ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_RANGEThe provided password did not contain enough characters from the character range '%s'. The minimum number of characters from that range that must be present in user passwords is %dServerMessages.ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_SETThe provided password did not contain enough characters from the character set '%s'. The minimum number of characters from that set that must be present in user passwords is %dServerMessages.ERR_CHARSET_VALIDATOR_TOO_FEW_OPTIONAL_CHAR_SETSThe provided password did not contain characters from at least %d of the following character sets or ranges: %sServerMessages.ERR_CHARSET_VALIDATOR_UNSORTED_RANGEThe provided character range definition '%s' is invalid because the range '%s' is reversedServerMessages.ERR_COMMON_AUDIT_ADD_OR_UPDATE_LOG_PUBLISHERError while creating or updating common audit log publisher %s: %sServerMessages.ERR_COMMON_AUDIT_CSV_HANDLER_DELIMITER_CHARError while processing common audit log publisher %s, delimiter char '%s' should not contain more than one characterServerMessages.ERR_COMMON_AUDIT_CSV_HANDLER_QUOTE_CHARError while processing common audit log publisher %s, quote char '%s' should not contain more than one characterServerMessages.ERR_COMMON_AUDIT_EXTERNAL_HANDLER_CREATIONError while creating common audit external log publisher %s: %sServerMessages.ERR_COMMON_AUDIT_FILE_BASED_HANDLER_CREATIONError while creating common audit log publisher %s: %sServerMessages.ERR_COMMON_AUDIT_KEYSTORE_FILE_IS_EMPTYError while processing common audit log publisher %s, the keystore file %s is emptyServerMessages.ERR_COMMON_AUDIT_KEYSTORE_FILE_MISSINGError while processing common audit log publisher %s, the keystore file %s is missingServerMessages.ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_CONTAINS_EMPTY_PINError while processing common audit log publisher %s, the keystore pin file %s contains an empty pinServerMessages.ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_MISSINGError while processing common audit log publisher %s, the keystore pin file %s is missingServerMessages.ERR_COMMON_AUDIT_UNSUPPORTED_LOG_RETENTION_POLICYError while adding common audit log publisher %s, the publisher defines an unsupported log retention policy %sServerMessages.ERR_COMMON_AUDIT_UNSUPPORTED_LOG_ROTATION_POLICYError while adding common audit log publisher %s, the publisher defines an unsupported log rotation policy %sServerMessages.ERR_COMPARE_UNSUPPORTED_CRITICAL_CONTROLCannot perform the compare operation on entry %s because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operationServerMessages.ERR_CONFIG_ACCTNOTHANDLER_CONFIG_NOT_ACCEPTABLEThe configuration for the account status notification handler defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_ALERTHANDLER_CONFIG_NOT_ACCEPTABLEThe configuration for the alert handler defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_ATTR_INVALID_BOOLEAN_VALUEUnable to set the value for Boolean configuration attribute %s because the provided value %s was not either 'true' or 'false'ServerMessages.ERR_CONFIG_AUTHZ_CONFIG_NOT_ACCEPTABLEThe configuration for the trust manager provider defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_AUTHZ_REFERENCED_DN_DOESNT_EXISTSThe authorization mechanism defined in %s is referencing a non existing DN: %sServerMessages.ERR_CONFIG_BACKEND_CANNOT_ACQUIRE_SHARED_LOCKThe Directory Server was unable to acquire a shared lock for backend %s: %s. This generally means that the backend is in use by a process that requires an exclusive lock (e.g., importing from LDIF or restoring a backup). This backend will be disabledServerMessages.ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_ENABLED_STATEAn unexpected error occurred while attempting to determine whether the backend associated with configuration entry %s should be enabled or disabled: %s. It will be disabledServerMessages.ERR_CONFIG_BIG_INDEX_EQUALITY_MATCHING_RULE_REQUIREDBig index for attribute '%s' cannot be created for matching rule '%s' because it is not an equality matching ruleServerMessages.ERR_CONFIG_CANNOT_CALCULATE_DIGESTAn error occurred while attempting to calculate a SHA-1 digest of file %s: %sServerMessages.ERR_CONFIG_CANNOT_REGISTER_AS_PRIVATE_SUFFIXAn unexpected error occurred while trying to register the configuration handler base DN "%s" as a private suffix with the Directory Server: %sServerMessages.ERR_CONFIG_CERTMAPPER_CONFIG_NOT_ACCEPTABLEThe configuration for the certificate mapper defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_ENTRYCACHE_CANNOT_INITIALIZE_CACHEAn error occurred while attempting to initialize an instance of class %s for use as the Directory Server entry cache: %s. As a result, the entry cache will be disabledServerMessages.ERR_CONFIG_ENTRYCACHE_CONFIG_LEVEL_NOT_ACCEPTABLEThe configuration for the entry cache defined in configuration entry %s was not acceptable: the entry cache level %d is already in useServerMessages.ERR_CONFIG_ENTRYCACHE_CONFIG_NOT_ACCEPTABLEThe configuration for the entry cache defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_FILE_ADD_NO_PARENTEntry %s cannot be added to the Directory Server configuration because its parent entry %s does not existServerMessages.ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIRAn error occurred while trying to create the configuration archive directory %s: %sServerMessages.ERR_CONFIG_FILE_CANNOT_OPEN_FOR_READAn error occurred while attempting to open the configuration file %s for reading: %sServerMessages.ERR_CONFIG_FILE_GENERIC_ERRORAn unexpected error occurred while attempting to process the Directory Server configuration file %s: %sServerMessages.ERR_CONFIG_FILE_MODIFY_REJECTED_BY_CHANGE_LISTENEREntry %s cannot be modified because one of the configuration change listeners registered for that entry rejected the change: %sServerMessages.ERR_CONFIG_FILE_WRITE_CANNOT_EXPORT_NEW_CONFIGAn error occurred while attempting to export the new Directory Server configuration to file %s: %sServerMessages.ERR_CONFIG_FILE_WRITE_ERRORAn unexpected error occurred while trying to write configuration entry %s to LDIF: %sServerMessages.ERR_CONFIG_HTTPENDPOINT_INVALID_AUTHZ_DNThe HTTP endpoint configuration defined in %s is referencing a non existing authorization DN %sServerMessages.ERR_CONFIG_HTTPENDPOINT_INVALID_CONFIGURATIONThe HTTP endpoint configuration defined in %s is invalid: %sServerMessages.ERR_CONFIG_HTTPENDPOINT_UNABLE_TO_STARTAn error occurred while starting the HTTP endpoint as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_IDMAPPER_CONFIG_NOT_ACCEPTABLEThe configuration for the identity mapper defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_INDEX_TYPE_NEEDS_MATCHING_RULEIndex for attribute '%s' cannot be created for matching rule '%s' because it cannot be found in the schema. Fix the matching rule name in the config or add the matching rule to the schemaServerMessages.ERR_CONFIG_INVALID_REGEXP_EXCLUSION_PATTERNThe metric name pattern to exclude '%s' cannot be parsed as a valid regular expression due to the following error: '%s'ServerMessages.ERR_CONFIG_INVALID_REGEXP_INCLUSION_PATTERNThe metric name pattern to include '%s' cannot be parsed as a valid regular expression due to the following error: '%s'ServerMessages.ERR_CONFIG_INVALID_SMTP_HOSTPORTThe smtp-server value '%s' is invalid: %sServerMessages.ERR_CONFIG_JE_PROPERTY_INVALIDAn error occurred while trying to parse and validate Berkeley DB JE property %s: %sServerMessages.ERR_CONFIG_JE_PROPERTY_SHADOWS_CONFIGAn error occurred while trying to parse and validate Berkeley DB JE property %s: the property shadows configuration attribute %sServerMessages.ERR_CONFIG_JEB_CACHE_SIZE_TOO_SMALLConfiguration attribute ds-cfg-db-cache-size has a value of %d which is less than the minimum: %dServerMessages.ERR_CONFIG_JMX_ATTR_NO_ATTRConfiguration entry %s does not contain attribute %s (or that attribute exists but is not accessible using JMX)ServerMessages.ERR_CONFIG_JMX_CANNOT_REGISTER_MBEANThe Directory Server could not register a JMX MBean for the component associated with configuration entry %s: %sServerMessages.ERR_CONFIG_JMX_NO_METHODThere is no method %s for any invokable component registered with configuration entry %sServerMessages.ERR_CONFIG_KEYMANAGER_CONFIG_NOT_ACCEPTABLEThe configuration for the key manager provider defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_LOGGER_CANNOT_CREATE_LOGGERAn error occurred while attempting to create a Directory Server logger from the information in configuration entry %s: %sServerMessages.ERR_CONFIG_LOGGER_CANNOT_UPDATE_LOGGERAn error occurred while attempting to update a Directory Server logger from the information in configuration entry %s: %sServerMessages.ERR_CONFIG_LOGGING_CANNOT_CREATE_WRITERAn error occurred while attempting to create a text writer for a Directory Server logger from the information in configuration entry %s: %sServerMessages.ERR_CONFIG_LOGGING_INVALID_TARGET_DN_PATTERNThe access log filtering criteria defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s"ServerMessages.ERR_CONFIG_LOGGING_INVALID_USER_DN_PATTERNThe access log filtering criteria defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s"ServerMessages.ERR_CONFIG_LOGGING_MODE_INVALIDInvalid UNIX file permissions %s: %sServerMessages.ERR_CONFIG_MANUAL_CHANGES_LOSTThe Directory Server encountered an error while attempting to determine whether the configuration file %s has been externally edited with the server online, and/or trying to preserve such changes: %s. Any manual changes made to that file may have been lostServerMessages.ERR_CONFIG_OAUTH2_CONFIG_ERRORUnable to configure the authorization mechanism defined in %s: %sServerMessages.ERR_CONFIG_OAUTH2_NON_EXISTING_DIRECTORYThe authorization mechanism defined in %s is referencing a non-existing or non-readable directory: %sServerMessages.ERR_CONFIG_PLUGIN_CONFIG_NOT_ACCEPTABLEThe configuration for the plugin defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_PWGENERATOR_CONFIG_NOT_ACCEPTABLEThe configuration for the password generator defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_PWPOLICY_INVALID_POLICY_CONFIGThe password policy defined in configuration entry %s is invalid: %sServerMessages.ERR_CONFIG_PWSCHEME_CONFIG_NOT_ACCEPTABLEThe configuration for the password storage scheme defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_PWVALIDATOR_CONFIG_NOT_ACCEPTABLEThe configuration for the password validator defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_RETENTION_POLICY_CANNOT_CREATE_POLICYAn error occurred while attempting to create a Directory Server log retention policy from the information in configuration entry %s: %sServerMessages.ERR_CONFIG_ROTATION_POLICY_CANNOT_CREATE_POLICYAn error occurred while attempting to create a Directory Server log rotation policy from the information in configuration entry %s: %sServerMessages.ERR_CONFIG_SASL_CONFIG_NOT_ACCEPTABLEThe configuration for the SASL mechanism handler defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_SCHEMA_CANNOT_LIST_FILESUnable to read the Directory Server schema definitions from directory %s because an unexpected error occurred while trying to list the files in that directory: %sServerMessages.ERR_CONFIG_SCHEMA_PROVIDER_CONFIG_NOT_ACCEPTABLEThe configuration of schema provider '%s' is not acceptable for the following reasons: %sServerMessages.ERR_CONFIG_SYNCH_ERROR_INITIALIZING_PROVIDERAn error occurred while attempting to initialize the Directory Server synchronization provider referenced in configuration entry %s: %sServerMessages.ERR_CONFIG_TRUSTMANAGER_CONFIG_NOT_ACCEPTABLEThe configuration for the trust manager provider defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_UNABLE_TO_APPLY_STARTUP_CHANGESAn error occurred while attempting to apply the changes contained in file %s to the server configuration at startup: %sServerMessages.ERR_CONFIG_UNABLE_TO_RESOLVE_HOSTUnable to resolve the host for the listen address '%s' of the LDAP connection handler %sServerMessages.ERR_CONFIG_VATTR_CONFIG_NOT_ACCEPTABLEThe configuration for the virtual attribute provider defined in configuration entry %s was not acceptable: %sServerMessages.ERR_CONFIG_VATTR_SV_TYPE_WITH_MERGE_VALUESThe virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but the conflict behavior is configured to merge real and virtual valuesServerMessages.ERR_CONFIG_VERSION_MISMATCHThe OpenDJ binary version '%s' does not match the installed configuration version '%s'. Please run upgrade before continuingServerMessages.ERR_CONFIG_VLV_INDEX_UNDEFINED_ATTRSort attribute %s for VLV index %s is not defined in the server schemaServerMessages.ERR_CONNHANDLER_DENIED_CLIENTThe connection attempt from client %s to %s has been rejected because the client was included in one of the denied address rangesServerMessages.ERR_CONNHANDLER_DISALLOWED_CLIENTThe connection attempt from client %s to %s has been rejected because the client was not included in one of the allowed address rangesServerMessages.ERR_CONNHANDLER_MISSING_CIPHERThe connection attempt from client '%s' to '%s' has been rejected because the proxy protocol header indicated that the client used SSL but the header does not specify which SSL cipher was used. The proxy should be configured to transmit all SSL headersServerMessages.ERR_CONNHANDLER_RESTRICTED_CLIENTThe connection attempt from client %s to %s has been rejected because there are too many open connections from this clientServerMessages.ERR_COULD_NOT_BIND_CHANGELOGReplication Server failed to start : could not bind to the listen port : %d. Error : %sServerMessages.ERR_COULD_NOT_READ_DBThe replication server failed to start because the database %s could not be read : %sServerMessages.ERR_COULD_NOT_RESTART_CHANGELOGCould not restart the Replication Server, bind to listen port %d failed : %sServerMessages.ERR_COULD_NOT_SET_LISTEN_SOCKET_TIMEOUTReplication server failed to start because setting socket timeout on port %d caused error %sServerMessages.ERR_COULD_NOT_SOLVE_CONFLICTError while trying to solve conflict with DN : %s ERROR : %sServerMessages.ERR_COULD_NOT_START_REPLICATIONThe Replication was not started on base-dn %s : %sServerMessages.ERR_CREATERC_PROVIDE_ONE_ARGYou must provide either the --%s or the --%s argumentServerMessages.ERR_CREATERC_UNABLE_TO_DETERMINE_SERVER_ROOTUnable to determine the path to the server root directory. Please ensure that the %s system property or the %s environment variable is set to the path of the server root directoryServerMessages.ERR_CREDENTIALS_ISSUEA problem occurred while connecting to cloud provider '%s' using the provided credentials: %sServerMessages.ERR_CRYPTOMGR_CANNOT_ENCODE_DUE_TO_MISSING_MASTER_KEYThe CryptoManager could not encode a symmetric because the master key with alias '%s' does not exist in the '%s' key manager. Please check that the correct key manager has been configured and that it contains the specified master keysServerMessages.ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_DIGESTCryptoManager cannot get the requested digest %s: %sServerMessages.ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_ENCRYPTION_CIPHERCryptoManager cannot get the requested encryption cipher %s: %sServerMessages.ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MAC_ENGINECryptoManager cannot get the requested MAC engine %s: %sServerMessages.ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MASTER_KEYThe master key with alias '%s' does not exist in the '%s' key manager. Please check that the correct key manager has been configured and that it contains the specified master keysServerMessages.ERR_CRYPTOMGR_FAILED_TO_RETRIEVE_ADS_TRUSTSTORE_CERTSCryptoManager failed to retrieve the collection of instance-key-pair public-key-certificates from ADS container "%s": %sServerMessages.ERR_CRYPTOMGR_GET_CIPHER_INVALID_CIPHER_TRANSFORMATIONCryptoManager passed invalid Cipher transformation "%s": %sServerMessages.ERR_CRYPTOMGR_GET_MAC_ENGINE_INVALID_MAC_ALGORITHMCryptoManager passed invalid MAC algorithm "%s": %sServerMessages.ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_OTHERCryptoManager failed to import the symmetric key entry "%s": %sServerMessages.ERR_CRYPTOMGR_INVALID_KEY_IDENTIFIER_SYNTAXCryptoManager failed to decode the key entry identifier "%s": %sServerMessages.ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_ALGORITHMCryptoManager failed to instantiate a KeyGenerator for algorithm "%s": %sServerMessages.ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_LENGTHCryptoManager failed to initialize because the specified cipher key length "%d" is beyond the allowed cryptography strength "%d" in jurisdiction policy filesServerMessages.ERR_CRYPTOMGR_SYMMETRIC_KEY_ENTRY_ADD_FAILEDCryptoManager failed to add locally produced symmetric key entry "%s": %sServerMessages.ERR_CSN_RANGE_INCLUDES_MORE_THAN_ONE_SERVERSpecified CSNs '%s' and '%s' have two different server ids. The historicalCsnRangeMatch extensible matching rule requires CSNs to have the same server idServerMessages.ERR_CSN_RANGE_SAME_OPERATOR_TYPESpecified operators '%s' and '%s' do not specify a range for historicalCsnRangeMatch extensible matching ruleServerMessages.ERR_DATA_VERSION_MISMATCHThe OpenDJ binary version '%s' does not match the installed data version '%s'. Please run 'upgrade --dataOnly' before continuingServerMessages.ERR_DELETE_HAS_SUB_BACKENDEntry %s cannot be removed because the backend that should contain that entry has a subordinate backend with a base DN of %s that is below the target DNServerMessages.ERR_DELETE_UNSUPPORTED_CRITICAL_CONTROLEntry %s cannot be removed because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operationServerMessages.ERR_DICTIONARY_VALIDATOR_CANNOT_READ_FILEAn error occurred while attempting to load the dictionary from file %s: %sServerMessages.ERR_DISK_SPACE_GET_MOUNT_POINTCould not get filesystem for directory %s: %sServerMessages.ERR_DISK_SPACE_MONITOR_UPDATE_FAILEDFailed to update free disk space for directory %s: %sServerMessages.ERR_DS_DN_DOES_NOT_MATCHDN sent by replication server: %s does not match local directory server one: %sServerMessages.ERR_DSREPL_CANNOT_DELETE_CNI_FILEThe replication changelog file '%s' could not be deleted. Check file permissions and filesystem status. The error is: %sServerMessages.ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_DELETE_ADMIN_ENTRIESCannot delete entries under '%s' in admin backend. The error was: %sCannot obtain a connection to server '%s' from the topology. The error was: %sServerMessages.ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_READ_MONITOR_ENTRYCannot read monitor entries under '%s' on the local server. The error was: %sServerMessages.ERR_DSREPL_CLEANUP_MIGRATED_CANNOT_UPDATE_CONFIGURATIONCannot update configuration for server '%s'. The error was: %sServerMessages.ERR_DSREPL_DOMAIN_DR_ID_INCONSISTENCYThe provided base DN '%s' does not match the disaster recovery id '%s'. Please verify that the base DN and disaster recovery id correspond to the base DN and id from the first recovered serverServerMessages.ERR_DSREPL_DR_CANNOT_CLEAR_CNIAn error occurred while clearing the change number index. The change number index on this server will expose erroneous data. Make sure the filesystem at '%s' is readable with delete permissions and try again. The error is: %sServerMessages.ERR_DSREPL_DR_CANNOT_COMPUTE_DR_IDAn error occurred while computing the disaster recovery id for base DN '%s': %sServerMessages.ERR_DSREPL_DR_CANNOT_REWRITE_BASE_DNAn error occurred while rewriting the base entry of the domain '%s'. This server will not be able to connect to the servers which already have received the disaster recovery procedure. Make sure the filesystem is writeable and there is some free disk space, and try again. The error is: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_ADD_NEW_SERVER_TO_CN_ADMIN_DATACannot add an entry describing the new server to 'cn=admin data' in the remote server '%s' in the existing topology. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_OBTAIN_CONNECTION_TO_SERVERCannot obtain a connection to server '%s' from the existing topology. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_READ_CN_ADMIN_DATACannot read 'cn=admin data' in server '%s'. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_RETRIEVE_REPLICATION_PORTCannot retrieve the replication port from server '%s'. The error was: %sServerMessages.ERR_DSREPL_STATUS_CANNOT_READ_CN_MONITOR_ON_TARGET_SERVERAn error occurred while reading cn=monitor on server %s: %sServerMessages.ERR_EMAILMSG_INVALID_RECIPIENT_ADDRESSThe provided recipient address %s is invalid: %sServerMessages.ERR_EMAILMSG_INVALID_SENDER_ADDRESSThe provided sender address %s is invalid: %sServerMessages.ERR_EMBEDDED_SERVER_ARCHIVE_SETUP_WRONG_ROOT_DIRECTORYThe setup from an archive can only be done with a server root directory named after the root directory contained in the archive: '%s'. The provided server root was: '%s'ServerMessages.ERR_EMBEDDED_SERVER_INITIALIZE_CONFIGURATIONAn error occurred while initializing configuration of embedded server with server root '%s': %sServerMessages.ERR_EMBEDDED_SERVER_REBUILD_INDEX_FAILUREAn error occurred while attempting to rebuild index of embedded server with server root '%s': %sServerMessages.ERR_EMBEDDED_SERVER_REBUILD_INDEX_NOT_SUCCESSFULAn error occurred while attempting to rebuild index of embedded server with server root '%s'. Rebuild task state was '%s'. You can look at the task logs printed on the embedded server output stream for more detailsServerMessages.ERR_EMBEDDED_SERVER_STARTAn error occurred while attempting to start the embedded server with server root '%s' : %sServerMessages.ERR_EMBEDDED_SERVER_UPGRADEAn error occurred while attempting to upgrade the embedded server with server root '%s' : %sServerMessages.ERR_ENTRY_ADD_OBSOLETE_OCObject class %s added to entry %s is marked OBSOLETE in the server schemaServerMessages.ERR_ENTRY_ADD_UNKNOWN_OCObject class %s cannot be added to entry %s because that class is not defined in the Directory Server schemaServerMessages.ERR_ENTRY_CONTAINER_ALREADY_REGISTEREDAn entry container named '%s' is already registered for base DN '%s'ServerMessages.ERR_ENV_VAR_VALUE_NOT_FOUNDNo environment value '%s' found for property '%s'. If you are running the tool in offline mode, make sure the command has access to this variable, or else make sure the directory server has access to itServerMessages.ERR_ERROR_CLEARING_DBWhile clearing the database %s, the following error happened: %sServerMessages.ERR_EXACTMAP_BACKEND_IS_NOT_LOCALThe baseDN '%s' specified as match base DN in the exact match identity mapper defined in configuration entry '%s', does not belong to a local backendServerMessages.ERR_EXACTMAP_INEFFICIENT_SEARCHThe internal search based on ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searchesServerMessages.ERR_EXACTMAP_SEARCH_FAILEDAn internal failure occurred while attempting to resolve ID string %s to a user entry: %sServerMessages.ERR_EXCEPTION_DECODING_OPERATIONError trying to replay %s, operation could not be decoded: %sServerMessages.ERR_EXCEPTION_FORWARDING_RESET_GEN_IDCaught IOException while forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %sServerMessages.ERR_EXTENDED_UNSUPPORTED_CRITICAL_CONTROLUnable to process the request for extended operation %s because it contained an unsupported critical control with OID %sServerMessages.ERR_EXTOP_PASSMOD_CANNOT_DETERMINE_ID_MAPPERAn error occurred while attempting to determine the identity mapper to use in conjunction with the password modify extended operation defined in configuration entry %s: %s. The password modify extended operation will not be enabled for use in the serverServerMessages.ERR_EXTOP_PASSMOD_CANNOT_GET_PW_POLICYAn error occurred while attempting to get the password policy for user %s: %sServerMessages.ERR_EXTOP_PASSMOD_ERROR_MAPPING_USERAn error occurred while attempting to map authorization ID string "%s" to a user entry: %sServerMessages.ERR_FAILED_TO_PURGE_HISTORICALError when purging historical information for entry %s: %sServerMessages.ERR_FCM_CANNOT_CALCULATE_FINGERPRINTAn error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %sServerMessages.ERR_FCM_INEFFICIENT_SEARCHThe internal search based on the certificate with fingerprint %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searchesServerMessages.ERR_FCM_SEARCH_FAILEDAn internal failure occurred while attempting to map the certificate with fingerprint %s to a user entry: %sServerMessages.ERR_FILE_CHECK_CREATE_FAILEDAn Exception was caught while testing existence or trying to create the directory for the Replication Server database : %s %sServerMessages.ERR_FILE_KEYMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a key manager factory to access the contents of keystore file %s: %sServerMessages.ERR_FILE_KEYMANAGER_CANNOT_LOADAn error occurred while trying to load the keystore contents from file %s: %sServerMessages.ERR_FILE_KEYMANAGER_NO_SUCH_FILEThe keystore file %s specified in attribute ds-cfg-key-store-file of configuration entry %s does not existServerMessages.ERR_FILE_TRUSTMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %sServerMessages.ERR_FILE_TRUSTMANAGER_CANNOT_LOADAn error occurred while trying to load the trust store contents from file %s: %sServerMessages.ERR_FILE_TRUSTMANAGER_NO_SUCH_FILEThe trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not existServerMessages.ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_CREATEThe attempt to obtain an exclusive lock on file %s was rejected because the attempt to create the lock file failed: %sServerMessages.ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_LOCKThe attempt to obtain an exclusive lock on file %s was rejected because an error occurred while attempting to acquire the lock: %sServerMessages.ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_OPENThe attempt to obtain an exclusive lock on file %s was rejected because the attempt to open the lock file failed: %sServerMessages.ERR_FILELOCKER_LOCK_SHARED_FAILED_CREATEThe attempt to obtain a shared lock on file %s was rejected because the attempt to create the lock file failed: %sServerMessages.ERR_FILELOCKER_LOCK_SHARED_FAILED_LOCKThe attempt to obtain a shared lock on file %s was rejected because an error occurred while attempting to acquire the lock: %sServerMessages.ERR_FILELOCKER_LOCK_SHARED_FAILED_OPENThe attempt to obtain a shared lock on file %s was rejected because the attempt to open the lock file failed: %sServerMessages.ERR_FILELOCKER_UNLOCK_EXCLUSIVE_FAILED_RELEASEThe attempt to release the exclusive lock held on %s failed: %sServerMessages.ERR_FILELOCKER_UNLOCK_SHARED_FAILED_RELEASEThe attempt to release the shared lock held on %s failed: %sServerMessages.ERR_FULL_UPDATE_NO_REMOTESCannot start total update in domain "%s" from this directory server DS(%s): no remote directory servers foundServerMessages.ERR_GLOBAL_ACCESS_CONTROL_INVALID_TARGET_DN_PATTERNThe global access control policy defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s"ServerMessages.ERR_GLOBAL_ACCESS_CONTROL_INVALID_USER_DN_PATTERNThe global access control policy defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s"ServerMessages.ERR_GLOBAL_ACCESS_CONTROL_UNRECOGNIZED_CONTROL_ALIASThe global access control policy defined in "%s" could not be parsed because it contains an unrecognized control alias "%s"ServerMessages.ERR_GLOBAL_ACCESS_CONTROL_UNRECOGNIZED_EXTOP_ALIASThe global access control policy defined in "%s" could not be parsed because it contains an unrecognized extended operation alias "%s"ServerMessages.ERR_HEX_DECODE_INVALID_CHARACTERThe value %s cannot be decoded as a hexadecimal string because it contains an illegal character %c that is not a valid hexadecimal digitServerMessages.ERR_HOST_PORT_ALREADY_SPECIFIEDThe connection handler %s is trying to use the listener %s which is already in use by another connection handlerServerMessages.ERR_HTTP_CONNECTION_HANDLE_EXCEPTIONUnable to process request '%s' received for HTTP client connection: %sServerMessages.ERR_HTTP_REQUEST_PROCESSING_EXCEPTIONUnable to process HTTP request '%s': %sServerMessages.ERR_HTTP_WRITING_RESPONSE_EXCEPTIONUnable to write HTTP response to the client '%s': %sServerMessages.ERR_IDLETIME_DISCONNECT_ERRORAn error occurred while attempting to disconnect client connection %d: %sServerMessages.ERR_IMPORT_LDIF_LACK_MEMInsufficient free memory (%d bytes) to perform import. At least %d bytes of free memory is requiredServerMessages.ERR_INIT_BAD_MSG_ID_SEQ_DURING_IMPORTBad msg id sequence during import. Expected:%s Actual:%sServerMessages.ERR_INIT_CANNOT_LOCK_BACKENDInitialization cannot be done because the following error occurred while locking the backend %s : %sServerMessages.ERR_INIT_NO_SUCCESS_END_FROM_SERVERSThe following servers did not end initialization being connected with the right generation (%s). They are potentially stopped or too slow. Servers list: %sServerMessages.ERR_INIT_NO_SUCCESS_START_FROM_SERVERSThe following servers did not acknowledge initialization in the expected time for domain %s. They are potentially down or too slow. Servers list: %sServerMessages.ERR_INITIALIZE_PLUGINInvalid plugin type '%s', a backup plugin must be of type '%s'ServerMessages.ERR_INTERNAL_CONNECTION_HANDLE_EXCEPTIONUnable to process request '%s' received for internal client connection: %sServerMessages.ERR_INTERNAL_ERROR_WITH_EXCEPTIONAn internal error occurred when accessing backend '%s': %sServerMessages.ERR_INVALID_BACKUP_ID_CANNOT_PARSE_TIMESTAMPBackup id '%s' is invalid: cannot parse '%s' as a timestampServerMessages.ERR_JEB_INVALID_LOGGING_LEVELThe database logging level string '%s' provided for configuration entry '%s' is invalid. The value must be one of OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or ALL. Note that these values are case sensitiveServerMessages.ERR_JMX_CONNECTION_FINALIZEDJMX connection %s with JMX connection ID '%s' has been disconnected because it was finalized by GCServerMessages.ERR_JMX_CONNECTION_HANDLE_EXCEPTIONUnable to process request '%s' received for JMX client connection: %sServerMessages.ERR_JMX_CONNECTION_UNEXPECTED_RESPONSE_TYPEUnable to process response received for JMX client connection for request '%s' because the response '%s' is not of any of the expected typesServerMessages.ERR_KEYSTORE_DOES_NOT_CONTAIN_ALIASThe key with alias '%s' used by '%s' could not be found, which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configuredServerMessages.ERR_KEYSTORE_INVALID_KEY_EXPIREDThe key with alias '%s' used by '%s' has expired. The key will be used, but SSL connections may fail depending on the validation performed by the peer. Verify that the underlying keystore is properly configured with a valid keyServerMessages.ERR_KEYSTORE_INVALID_KEY_NOT_YET_VALIDThe key with alias '%s' used by '%s' is not valid yet. The key will be used, but SSL connections may fail depending on the validation performed by the peer. Verify that the underlying keystore is properly configured with a valid keyServerMessages.ERR_LDAP_CONNECTION_CLOSEDLDAP connection %s has been closed because the LDAP connection handler %s is shutting downServerMessages.ERR_LDAP_DISCONNECT_DUE_TO_BIND_PROTOCOL_ERRORThis client connection is being terminated because a protocol error occurred while trying to process a bind request. The LDAP message ID was %d and the error message for the bind response was %sServerMessages.ERR_LDAP_DISCONNECT_DUE_TO_INVALID_REQUEST_TYPETerminating this connection because the client sent an invalid message of type %s (LDAP message ID %d) that is not allowed for request messagesServerMessages.ERR_LDAP_KEYMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a key manager factory to access the contents of LDAP keystore with base DN '%s': %sServerMessages.ERR_LDAP_TRUSTMANAGER_CANNOT_CREATE_FACTORYAn error occurred while trying to create a trust manager factory to access the contents of LDAP keystore with base DN '%s': %sServerMessages.ERR_LDAPURL_CANNOT_DECODE_PORTThe provided string "%s" cannot be decoded as an LDAP URL because the port number portion %s cannot be decoded as an integerServerMessages.ERR_LDAPURL_INVALID_HEX_BYTEThe provided URL component "%s" could not be decoded because the character at byte %d was not a valid hexadecimal digitServerMessages.ERR_LDAPURL_INVALID_PORTThe provided string "%s" cannot be decoded as an LDAP URL because the provided port number %d is not within the valid range between 1 and 65535ServerMessages.ERR_LDAPURL_INVALID_SCOPE_STRINGThe provided string "%s" cannot be decoded as an LDAP URL because the scope string %s was not one of the allowed values of base, one, sub, or subordinateServerMessages.ERR_LDAPURL_PERCENT_TOO_CLOSE_TO_ENDThe provided URL component "%s" could not be decoded because the percent character at byte %d was not followed by two hexadecimal digitsServerMessages.ERR_LDAPV2_EXTENDED_REQUEST_NOT_ALLOWEDThe client with connection ID %d authenticated to the Directory Server using LDAPv2, but attempted to send an extended operation request (LDAP message ID %d), which is not allowed for LDAPv2 clients. The connection will be terminatedServerMessages.ERR_LDIF_BACKEND_CANNOT_WRITE_ENTRY_TO_LDIFAn error occurred while trying to write entry %s during the LDIF export: %sServerMessages.ERR_LDIF_BACKEND_ERROR_EMPTY_FILEThe file %s written for the LDIF backend defined in configuration entry %s is 0 bytes long and unusableServerMessages.ERR_LDIF_CONNHANDLER_CANNOT_DELETEAn error occurred while the LDIF connection handler was attempting to delete processed file %s: %sServerMessages.ERR_LDIF_CONNHANDLER_IO_ERRORAn I/O error occurred while the LDIF connection handler was processing LDIF file %s: %sServerMessages.ERR_LDIF_INVALID_LEADING_SPACEUnable to parse line %d ("%s") from the LDIF source because the line started with a space but there were no previous lines in the entry to which this line could be appendedServerMessages.ERR_LDIF_NO_ATTR_NAMEUnable to parse LDIF entry starting at line %d because the line "%s" does not include an attribute nameServerMessages.ERR_LDIF_NO_DNUnable to parse LDIF entry starting at line %d because the first line does not contain a DN (the first line was "%s"ServerMessages.ERR_LDIF_READ_ATTR_SKIPSkipping entry %s because the following error was received when reading its attributes: %sServerMessages.ERR_LDIF_REJECTED_BY_PLUGINRejecting entry %s because it was rejected by a plugin: %sServerMessages.ERR_LDIF_SKIP_EXCLUDE_BRANCHSkipping entry %s because the DN is excluded by the exclude branch "%s"ServerMessages.ERR_LDIF_SKIP_EXCLUDE_FILTERSkipping entry %s because the DN is excluded by the exclude filter "%s"ServerMessages.ERR_LDIFEXPORT_CANNOT_DECODE_EXCLUDE_BASEUnable to decode exclude branch string "%s" as a valid distinguished name: %sServerMessages.ERR_LDIFEXPORT_CANNOT_LOCK_BACKENDAn error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The LDIF export cannot continueServerMessages.ERR_LDIFEXPORT_CANNOT_PARSE_EXCLUDE_FILTERUnable to decode exclude filter string "%s" as a valid search filter: %sServerMessages.ERR_LDIFEXPORT_CANNOT_PARSE_INCLUDE_FILTERUnable to decode include filter string "%s" as a valid search filter: %sServerMessages.ERR_LDIFEXPORT_INVALID_INCLUDE_BASEProvided include base DN "%s" is not handled by the backend with backend ID %sServerMessages.ERR_LDIFIMPORT_CANNOT_DECODE_EXCLUDE_BASEUnable to decode exclude branch string "%s" as a valid distinguished name: %sServerMessages.ERR_LDIFIMPORT_CANNOT_DECODE_INCLUDE_BASEUnable to decode include branch string "%s" as a valid distinguished name: %sServerMessages.ERR_LDIFIMPORT_CANNOT_LOCK_BACKENDAn error occurred while attempting to acquire an exclusive lock for backend %s: %s. This generally means some other process is still using this backend (e.g., it is in use by the Directory Server or a backup or LDIF export is in progress). The LDIF import cannot continueServerMessages.ERR_LDIFIMPORT_CANNOT_OPEN_REJECTS_FILEAn error occurred while trying to open the rejects file %s for writing: %sServerMessages.ERR_LDIFIMPORT_CANNOT_OPEN_SKIP_FILEAn error occurred while trying to open the skip file %s for writing: %sServerMessages.ERR_LDIFIMPORT_CANNOT_PARSE_EXCLUDE_FILTERUnable to decode exclude filter string "%s" as a valid search filter: %sServerMessages.ERR_LDIFIMPORT_CANNOT_PARSE_INCLUDE_FILTERUnable to decode include filter string "%s" as a valid search filter: %sServerMessages.ERR_LDIFIMPORT_CANNOT_PARSE_TEMPLATE_FILEUnable to parse the specified file %s as a MakeLDIF template file: %sServerMessages.ERR_LDIFIMPORT_CANNOT_PARSE_THREAD_COUNTThe value %s for threadCount cannot be parsed: %sServerMessages.ERR_LDIFIMPORT_INVALID_INCLUDE_BASEProvided include base DN "%s" is not handled by the backend with backend ID %sServerMessages.ERR_LDIFIMPORT_MISSING_BACKEND_ARGUMENTNeither the %s nor the %s argument was provided. One of these arguments must be given to specify the backend for the LDIF data to be imported toServerMessages.ERR_LDIFIMPORT_MISSING_REQUIRED_ARGUMENTNeither the %s nor the %s argument was provided. One of these arguments must be given to specify the source for the LDIF data to be importedServerMessages.ERR_LOADING_GENERATION_IDAn unexpected error occurred when searching in %s for the generation ID : %sServerMessages.ERR_LOGGER_ERROR_CLOSING_FILEError occurred while closing log file for logger %s: %sServerMessages.ERR_LOGGER_ERROR_FLUSHING_BUFFERError occurred while flushing writer buffer for logger %s: %sServerMessages.ERR_LOGGER_ERROR_OBTAINING_FREE_SPACEError occurred while obtaining free disk space in the partition containing log file %s: %sServerMessages.ERR_LOGGER_ERROR_WRITING_RECORDError occurred while writing log record for logger %s: %s. Any further write errors will be ignoredServerMessages.ERR_MEMORYBACKEND_CANNOT_WRITE_ENTRY_TO_LDIFCannot write entry %s to LDIF: %sServerMessages.ERR_MEMORYBACKEND_PARENT_DOESNT_EXISTUnable to add entry %s because its parent entry %s does not exist in the memory-based backendServerMessages.ERR_MEMORYBACKEND_RENAME_PARENT_DOESNT_EXISTCannot rename entry %s because the new parent entry %s doesn't existServerMessages.ERR_MODDN_CANNOT_LOCK_NEW_DNThe modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for the new DN %sServerMessages.ERR_MODDN_DIFFERENT_BACKENDSThe modify DN operation for entry %s cannot be performed because the backend holding the current entry is different from the backend used to handle the new DN %s. Modify DN operations may not span multiple backendsServerMessages.ERR_MODDN_NEW_RDN_ATTR_IS_NO_USER_MODEntry %s cannot be renamed because the new RDN includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema, and the target value for that attribute is not already included in the entryServerMessages.ERR_MODDN_NEW_SUPERIOR_IN_SUBTREEThe modify DN operation for entry %s cannot be performed because the new superior entry %s is equal to or a subordinate of the entry to be movedServerMessages.ERR_MODDN_NEWRDN_ATTR_IS_OBSOLETEThe modify DN operation for entry %s cannot be performed because the new RDN includes attribute type %s which is declared OBSOLETE in the server schemaServerMessages.ERR_MODDN_NO_BACKEND_FOR_NEW_ENTRYThe modify DN operation for entry %s cannot be performed because no backend is registered to handle the new DN %sServerMessages.ERR_MODDN_OLD_RDN_ATTR_IS_NO_USER_MODEntry %s cannot be renamed because the current DN includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema and the deleteOldRDN flag was set in the modify DN requestServerMessages.ERR_MODDN_PREOP_VIOLATES_SCHEMAThe modify DN operation for entry %s cannot be performed because a pre-operation plugin modified the entry in a way that caused it to violate the server schema: %sServerMessages.ERR_MODDN_UNSUPPORTED_CRITICAL_CONTROLEntry %s cannot be renamed because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operationServerMessages.ERR_MODDN_VIOLATES_SCHEMAThe modify DN operation for entry %s cannot be performed because the change would have violated the server schema: %sServerMessages.ERR_MODIFY_ADD_NO_VALUESEntry %s cannot be modified because the modification contained an add component for attribute %s but no values were providedServerMessages.ERR_MODIFY_ATTR_IS_NO_USER_MODEntry %s cannot be modified because the modification attempted to update attribute %s which is defined as NO-USER-MODIFICATION in the server schemaServerMessages.ERR_MODIFY_ATTR_IS_OBSOLETEEntry %s cannot be modified because the modification attempted to set one or more new values for attribute %s which is marked OBSOLETE in the server schemaServerMessages.ERR_MODIFY_DELETE_NO_SUCH_ATTREntry %s cannot be modified because an attempt was made to remove one or more values from attribute %s but this attribute is not present in the entryServerMessages.ERR_MODIFY_DELETE_RDN_ATTREntry %s cannot be modified because the change to attribute %s would have removed a value used in the RDNServerMessages.ERR_MODIFY_INCREMENT_RDNEntry %s cannot be modified because an attempt was made to increment the value of attribute %s which is used as an RDN attribute for the entryServerMessages.ERR_MODIFY_INCREMENT_REQUIRES_EXISTING_VALUEEntry %s cannot be modified because an attempt was made to increment the value of attribute %s but that attribute did not have any values in the target entryServerMessages.ERR_MODIFY_INCREMENT_REQUIRES_SINGLE_VALUEEntry %s cannot be modified because an attempt was made to increment the value of attribute %s but the request contained multiple values, where only a single integer value is allowedServerMessages.ERR_MODIFY_INCREMENT_REQUIRES_VALUEEntry %s cannot be modified because an attempt was made to increment the value of attribute %s but the request did not include a value for that attribute specifying the amount by which to increment the valueServerMessages.ERR_MODIFY_INVALID_MOD_TYPE_FOR_PASSWORDInvalid modification type %s attempted on password attribute %sServerMessages.ERR_MODIFY_UNSUPPORTED_CRITICAL_CONTROLEntry %s cannot be modified because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operationServerMessages.ERR_MODIFY_VIOLATES_SCHEMAEntry %s cannot be modified because the resulting entry would have violated the server schema: %sServerMessages.ERR_MODIFYDN_ABORTED_BY_SUBORDINATE_PLUGINA plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %sServerMessages.ERR_MONITOR_INVALID_BASEUnable to retrieve the requested entry %s from the monitor backend because the DN is not below the monitor base of %sServerMessages.ERR_MONITOR_MODIFY_NOT_SUPPORTEDUnwilling to update entry "%s" because modify operations are not supported in the monitor backend. If you wish to alter the contents of the base monitor entry itself, then it may be possible to do so by modifying the "%s" entry in the configurationServerMessages.ERR_MONITOR_UNABLE_TO_EXPORT_PROVIDER_ENTRYAn error occurred while attempting to export the monitor entry for monitor provider %s: %sServerMessages.ERR_NO_CLOUD_FILE_FOUNDCould not find file '%s' in cloud bucket '%s'ServerMessages.ERR_NO_KEY_ENTRY_IN_KEYSTOREThere is no private key entry in keystore '%s' used by file based key manager provider '%s'. TLS connections which rely on this key manager provider may fail. Ensure that keystore file contains at least one private keyServerMessages.ERR_NO_REACHABLE_PEER_IN_THE_DOMAINDomain %s: the server with serverId=%s is unreachableServerMessages.ERR_OPERATION_NOT_FOUND_IN_PENDINGInternal Error : Operation %s change number %s was not found in local change listServerMessages.ERR_OPERATION_NOT_FOUND_IN_REMOTEInternal Error : Operation %s change number %s was not found in remote change listServerMessages.ERR_PLUGIN_ADLIST_INVALID_PLUGIN_TYPEThe LDAP attribute description list plugin instance defined in configuration entry %s lists an invalid plugin type %s. This plugin can only be used as a pre-parse search pluginServerMessages.ERR_PLUGIN_ATTR_CLEANUP_EQUAL_VALUESThe mapping '%s:%s' maps the attribute to itselfServerMessages.ERR_PLUGIN_CHANGE_NUMBER_INVALID_PLUGIN_TYPE_LISTAn attempt was made to register the Change Number Control plugin with the following plugin types : %s. However this plugin must be configured with all of the following plugin types : %sServerMessages.ERR_PLUGIN_LDIF_IMPORT_PLUGIN_RETURNED_NULLThe LDIF import plugin defined in configuration entry %s returned null when invoked on entry %s. This is an illegal responseServerMessages.ERR_PLUGIN_REFERENT_BAD_FILTERThe filtering criteria '%s' specified in property 'check-references-filter-criteria' is invalid because the filter could not be decoded: '%s'ServerMessages.ERR_PLUGIN_REFERENT_INVALID_ATTRIBUTE_SYNTAXAn error occurred in the Referential Integrity plugin while attempting to configure the attribute type %s which has a syntax OID of %s. A Referential Integrity attribute type must have a syntax OID of either 1.3.6.1.4.1.1466.115.121.1.12 (for the distinguished name syntax) or 1.3.6.1.4.1.1466.115.121.1.34 (for the name and optional uid syntax) or 1.3.6.1.4.1.36733.2.1.3.12 (for the name and json syntax)ServerMessages.ERR_PLUGIN_REFERENT_MODIFY_FAILEDThe Referential Integrity plugin failed when performing an internal modify on entry %s: %sServerMessages.ERR_PLUGIN_SHUTDOWN_PLUGIN_EXCEPTIONThe shutdown plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server shutdown process: %sServerMessages.ERR_PLUGIN_STARTUP_PLUGIN_EXCEPTIONThe startup plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server startup process: %s. The server startup process has been abortedServerMessages.ERR_PLUGIN_TYPE_NOT_SUPPORTEDThe plugin defined in configuration entry %s does not support the %s plugin typeServerMessages.ERR_PLUGIN_UNIQUEATTR_INTERNAL_ERRORAn internal error occurred while attempting to determine whether the operation would have resulted in a unique attribute conflict (result %s, message %s)ServerMessages.ERR_PROXY_CANNOT_DISCOVER_REMOTE_CAPABILITIESProxy backend '%s' could not discover remote servers capabilities: %sServerMessages.ERR_PROXY_NO_PRIMARY_NOR_SECONDARY_SERVERS_DISCOVEREDProxy backend '%s' is non functional because it could not find any primary nor secondary servers via the service discovery mechanism '%s'ServerMessages.ERR_PROXY_UNKNOWN_SERVICE_DISCOVERYProxy backend '%s' cannot find the configured service discovery mechanism '%s'ServerMessages.ERR_PUBLISHING_FAKE_OPSCaught exception publishing fake operations for domain %s : %sServerMessages.ERR_PWLENGTHVALIDATOR_MIN_GREATER_THAN_MAXThe configured minimum password length of %d characters is greater than the configured maximum password length of %dServerMessages.ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CHANGE_BY_TIMEAn error occurred while attempting to determine the value for attribute ds-cfg-require-change-by-time in configuration entry %s: %sServerMessages.ERR_PWPOLICY_DEPRECATED_SCHEME_NOT_AUTHPassword policy configuration entry %s references deprecated password storage scheme DN %s which does not support the auth password syntaxServerMessages.ERR_PWPOLICY_INVALID_LAST_LOGIN_TIME_FORMATThe password policy definition contained in configuration entry "%s" is invalid because the specified last login time format "%s" is not a valid format string The last login time format string should conform to the syntax described in the API documentation for the 'java.text.SimpleDateFormat' classServerMessages.ERR_PWPOLICY_INVALID_PREVIOUS_LAST_LOGIN_TIME_FORMATThe password policy definition contained in configuration entry "%s" is invalid because the specified previous last login time format "%s" is not a valid format string The previous last login time format strings should conform to the syntax described in the API documentation for the 'java.text.SimpleDateFormat' classServerMessages.ERR_PWPOLICY_SCHEME_DOESNT_SUPPORT_AUTHThe password storage scheme defined in configuration entry %s does not support the auth password syntax, which is used by password attribute %sServerMessages.ERR_PWPOLICY_UNDEFINED_PASSWORD_ATTRIBUTEThe password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" is not defined in the server schemaServerMessages.ERR_PWPOLICY_UNKNOWN_STORAGE_SCHEMESNo enabled password storage schemes in '%s' in subentry '%s'ServerMessages.ERR_PWPOLICY_VALIDATION_FAILEDThe password value for attribute %s was found to be unacceptable: %sServerMessages.ERR_PWPSTATE_CANNOT_UPDATE_USER_ENTRYAn error occurred while attempting to update password policy state information for user %s: %sServerMessages.ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUEThe value %s provided for the password policy state operation used to set the account expiration time was invalid: %s. The value should be specified using the generalized time formatServerMessages.ERR_PWPSTATE_EXTOP_BAD_AUTH_FAILURE_TIMEThe value %s provided for the password policy state operation used to update the authentication failure times was invalid: %s. The value should be specified using the generalized time formatServerMessages.ERR_PWPSTATE_EXTOP_BAD_GRACE_LOGIN_TIMEThe value %s provided for the password policy state operation used to update the grace login use times was invalid: %s. The value should be specified using the generalized time formatServerMessages.ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIMEThe value %s provided for the password policy state operation used to set the last login time was invalid: %s. The value should be specified using the generalized time formatServerMessages.ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUEThe value %s provided for the password policy state operation used to set the password changed time was invalid: %s. The value should be specified using the generalized time formatServerMessages.ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUEThe value %s provided for the password policy state operation used to set the password warned time was invalid: %s. The value should be specified using the generalized time formatServerMessages.ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIMEThe value %s provided for the password policy state operation used to set the required change time was invalid: %s. The value should be specified using the generalized time formatServerMessages.ERR_PWPSTATE_NO_SUCH_POLICYUser entry %s is configured to use a password policy subentry of %s but no such password policy has been defined in the server configurationServerMessages.ERR_PWSCHEME_ARGON2_NOT_ENOUGH_MEMORYThe Argon2 password storage scheme could not be configured because it requires %s kB of memory, exceeding the maximum available of %s kB. Configure a bigger heap or reduce the Argon2 memory requirementsServerMessages.ERR_PWSCHEME_CANNOT_BASE64_DECODE_STORED_PASSWORDAn error occurred while attempting to base64-decode the password value %s: %sServerMessages.ERR_PWSCHEME_CANNOT_DECODE_SCRAM_CREDENTIALAn error occurred while attempting to decode the SCRAM credential value %s: %sServerMessages.ERR_PWSCHEME_CANNOT_DECRYPTAn error occurred while trying to decrypt a value using password storage scheme %s: %sServerMessages.ERR_PWSCHEME_CANNOT_ENCODE_PASSWORDAn unexpected error occurred while attempting to encode a password using the storage scheme defined in class %s: %sServerMessages.ERR_PWSCHEME_CANNOT_ENCRYPTAn error occurred while trying to encrypt a value using password storage scheme %s: %sServerMessages.ERR_PWSCHEME_CANNOT_INITIALIZE_MESSAGE_DIGESTAn error occurred while attempting to initialize the message digest generator for the %s algorithm: %sServerMessages.ERR_RANDOMPWGEN_CHARSET_NAME_CONFLICTConfiguration entry "%s" contains multiple definitions for the %s character setServerMessages.ERR_RANDOMPWGEN_UNKNOWN_CHARSETThe password format string "%s" references an undefined character set "%s"ServerMessages.ERR_READING_PROFILE_VERSION_FILEAn error occurred while reading file '%s': %sServerMessages.ERR_REBUILDINDEX_CANNOT_EXCLUSIVE_LOCK_BACKENDAn error occurred while attempting to acquire a exclusive lock for backend %s: %s. This generally means that some other process has an lock on this backend or the server is running with this backend online. The rebuild process cannot continueServerMessages.ERR_REBUILDINDEX_CANNOT_SHARED_LOCK_BACKENDAn error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The rebuild process cannot continueServerMessages.ERR_RECURRINGTASK_CANNOT_INITIALIZE_INTERNALAn error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %sServerMessages.ERR_RECURRINGTASK_CANNOT_INSTANTIATE_CLASS_AS_TASKAn error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?ServerMessages.ERR_REGEXMAP_BACKEND_IS_NOT_LOCALThe baseDN '%s' specified as match base DN in the regular expression identity mapper defined in configuration entry '%s', does not belong to a local backendServerMessages.ERR_REGEXMAP_INEFFICIENT_SEARCHThe internal search based on processed ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searchesServerMessages.ERR_REGEXMAP_INVALID_MATCH_PATTERNThe provided match pattern "%s" could not be parsed as a regular expression: %sServerMessages.ERR_REGEXMAP_SEARCH_FAILEDAn internal failure occurred while attempting to resolve processed ID string %s to a user entry: %sServerMessages.ERR_REPLICATION_PROTOCOL_MESSAGE_TYPEReplication protocol error. Bad message type. %s received, %s requiredServerMessages.ERR_REPLICATION_PROTOCOL_UNEXPECTED_DSReplication Server '%s' expected to negotiate with another Replication Server but got information for Directory Server '%s' instead. The connection will be closedServerMessages.ERR_REPLICATION_SERVER_ID_INCOMPATIBLE_WITH_VERSIONCannot enable replication to server '%s' as this server's ID '%s' is not a number between 1 and 32767ServerMessages.ERR_REPLICATION_UNEXPECTED_MESSAGENew replication connection from %s started with unexpected message %s and is being closedServerMessages.ERR_RESYNC_REQUIRED_UNKNOWN_DOMAIN_IN_PROVIDED_COOKIEFull resync required. Reason: The provided cookie contains unknown replicated domain %s. Current starting cookie <%s>ServerMessages.ERR_ROOTDSE_MODIFY_NOT_SUPPORTEDUnwilling to update entry "%s" because modify operations are not supported in the root DSE backend. If you wish to alter the contents of the root DSE itself, then it may be possible to do so by modifying the "%s" entry in the configurationServerMessages.ERR_RS_DN_DOES_NOT_MATCHDN sent by remote replication server: %s does not match local replication server one: %sServerMessages.ERR_RS_SESSION_PUBLISH_INTERRUPTED_EXCEPTIONError when trying to publish a message in '%s'. The connection is going to be closed and reopened. Error: %sServerMessages.ERR_SASL_ACCOUNT_NOT_LOCALSASL %s authentication is not supported for user %s because the account is not managed locallyServerMessages.ERR_SASL_AUTHZID_CANNOT_GET_ENTRYThe entry %s specified as the authorization identity could not be retrieved: %sServerMessages.ERR_SASL_AUTHZID_INVALID_DNThe provided authorization ID %s contained an invalid DN: %sServerMessages.ERR_SASL_CANNOT_GET_SERVER_FQDNAn unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %sServerMessages.ERR_SASL_CANNOT_MAP_AUTHENTRYAn error occurred while attempting to map authorization ID %s to a user entry: %sServerMessages.ERR_SASL_CONTEXT_CREATE_ERRORAn unexpected error occurred while trying to create an %s context: %sServerMessages.ERR_SASL_NO_REVERSIBLE_PASSWORDSSASL %s authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible formServerMessages.ERR_SASL_NO_SCRAM_CREDENTIALSSASL %s authentication is not possible for user '%s' because the user entry does not contain any SCRAM credentialsServerMessages.ERR_SASL_PROTOCOL_ERRORSASL %s protocol error: %sServerMessages.ERR_SASL_ZERO_LENGTH_USERNAMEThe username contained in the SASL %s bind request had a length of zero characters, which is not allowed. %s authentication does not allow an empty string for use as the usernameServerMessages.ERR_SASLDIGESTMD5_CANNOT_MAP_USERNAMEAn error occurred while attempting to map username %s to a Directory Server entry: %sServerMessages.ERR_SASLEXTERNAL_CANNOT_VALIDATE_CERTAn error occurred while attempting to validate the peer certificate presented by the client with a certificate from the user's entry %s: %sServerMessages.ERR_SASLPLAIN_AUTHZID_CANNOT_GET_ENTRYAn error occurred while attempting to retrieve entry %s specified as the authorization ID: %sServerMessages.ERR_SASLPLAIN_AUTHZID_CANNOT_MAP_AUTHZIDAn error occurred while attempting to map authorization ID %s to a user entry: %sServerMessages.ERR_SASLPLAIN_AUTHZID_INVALID_DNThe provided authorization ID %s contained an invalid DN: %sServerMessages.ERR_SASLPLAIN_CANNOT_CHECK_PASSWORD_VALIDITYAn error occurred while attempting to verify the password for user %s during SASL PLAIN authentication: %sServerMessages.ERR_SASLPLAIN_CANNOT_DECODE_AUTHCID_AS_DNAn error occurred while attempting to decode the SASL PLAIN authentication ID "%s" because it appeared to contain a DN but DN decoding failed: %sServerMessages.ERR_SASLPLAIN_CANNOT_GET_ENTRY_BY_DNAn error occurred while attempting to retrieve user entry %s as specified in the DN-based authentication ID of a SASL PLAIN bind request: %sServerMessages.ERR_SASLPLAIN_CANNOT_MAP_USERNAMEAn error occurred while attempting to map username %s to a Directory Server entry: %sServerMessages.ERR_SATUACM_CANNOT_DECODE_SUBJECT_AS_DNUnable to decode peer certificate subject %s as a DN: %sServerMessages.ERR_SATUACM_DUPLICATE_CERT_ATTRConfiguration entry %s contains multiple mappings for certificate attribute %sServerMessages.ERR_SATUACM_DUPLICATE_USER_ATTRConfiguration entry %s contains multiple mappings for user attribute %sServerMessages.ERR_SATUACM_INEFFICIENT_SEARCHThe internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searchesServerMessages.ERR_SATUACM_INVALID_MAP_FORMATConfiguration entry %s has value '%s' which violates the format required for attribute mappings. The expected format is 'certattr:userattr'ServerMessages.ERR_SATUACM_SEARCH_FAILEDAn internal failure occurred while attempting to map the certificate with subject %s to a user entry: %sServerMessages.ERR_SCHEMA_CANNOT_WRITE_CONCAT_SCHEMA_FILEAn error occurred while attempting to write file %s containing a concatenated list of all server schema elements: %s. The server may not be able to accurately identify any schema changes made with the server offlineServerMessages.ERR_SCHEMA_HAS_WARNINGSThere should be no warnings on the schema, but instead got %d warnings: %sServerMessages.ERR_SCHEMA_MODIFY_CANNOT_DECODE_LDAP_SYNTAXAn error occurred while attempting to decode the ldapsyntax description "%s": %sServerMessages.ERR_SCHEMA_PARSE_LINEIgnoring schema definition '%s' because the following error occurred while it was being parsed: %sServerMessages.ERR_SDTUACM_INEFFICIENT_SEARCHThe internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searchesServerMessages.ERR_SDTUACM_SEARCH_FAILEDAn internal failure occurred while attempting to map the certificate with subject %s to a user entry: %sServerMessages.ERR_SEARCHING_FRACTIONAL_CONFIGURATIONAn unexpected error occurred when loading the fractional replication configuration of domain "%s": %sServerMessages.ERR_SEARCHING_GENERATION_IDAn unexpected error occurred when loading the generation id of domain "%s": %sServerMessages.ERR_SECRET_FILE_TOO_BIGThe file '%s' exceeds max size '%s'ServerMessages.ERR_SEDCM_CANNOT_DECODE_SUBJECT_AS_DNCould not map the provided certificate chain to a user because the peer certificate subject "%s" could not be decoded as an LDAP DN: %sServerMessages.ERR_SEDCM_CANNOT_GET_ENTRYCould not map the provided certificate chain to a user because an error occurred while attempting to retrieve the user entry with DN "%s": %sServerMessages.ERR_SENDING_NEW_ATTEMPT_INIT_REQUESTWhen sending a new initialization request for an initialization from a remote server, the following error occurred %s. The initial error was : %sServerMessages.ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_ADD_MECHANISMAn error occurred while adding Service Discovery Mechanism '%s': %sServerMessages.ERR_SERVICE_DISCOVERY_CONFIG_MANAGER_INIT_MECHANISMDiscovery mechanism '%s' initialization failed : %sServerMessages.ERR_SERVICE_DISCOVERY_MECHANISM_CANNOT_CREATE_SSL_CONTEXTError occurred while creating an SSL context for service discovery mechanism '%s' : %sService discovery mechanism '%s' failed to refresh the connection options. Exception : %s",Service discovery mechanism '%s' failed to refresh the partition information. Exception : %s",ServerMessages.ERR_SESSION_SEND_EXCEPTIONAn error occurred in session '%s' when trying to send a message to the socket: %sServerMessages.ERR_SETUP_ADD_UPGRADE_VERSION_IN_CONFIGUnable to write the upgrade version in '%s' file (%s)ServerMessages.ERR_SETUP_CANNOT_WRITE_FILEUnable to write a required file. Make sure that the %s tool has sufficient permissions to create and write the file: %sServerMessages.ERR_SETUP_CERTNICKNAME_NOT_FOUNDThe provided certificate nickname '%s' could not be found. The keystore contains the following certificate nicknames: %sServerMessages.ERR_SETUP_DATA_VERSION_FROM_CONFIG_VERSIONUnable to parse the version in '%s' file in order to initialize the content of the '%s' fileServerMessages.ERR_SETUP_DS_INVALID_PROFILE_PARAMETER_VALUE_FORMATInvalid profile parameter value '%s'. Supported format is '%s'ServerMessages.ERR_SETUP_DS_PROFILE_MISSING_PARAMETER_VALUEThe parameter '%s' is required by profile '%s', but no value has been providedServerMessages.ERR_SETUP_DS_PROFILE_NOT_FOUNDSetup profile '%s' cannot be found. %sServerMessages.ERR_SETUP_ENABLING_TRUST_MANAGER_PROVIDERAn error occurred while enabling the %s trust manager provider: %sServerMessages.ERR_SETUP_ENABLING_WINDOWS_SERVICEUnable to enable windows service (return code '%d'): %sServerMessages.ERR_SETUP_FILE_BASED_KEYSTORE_PASSWORD_IS_MISSINGYou must specify the keystore password of the file based keystore. You can use either --%s or --%s options to specify itServerMessages.ERR_SETUP_INSTANCE_INSTALLED_FROM_FILEA server instance (%s) has already been setup in the directory %sServerMessages.ERR_SETUP_MANAGEMENT_CONTEXT_FROM_CONFIGUnable to write configuration file '%s' (%s)ServerMessages.ERR_SETUP_MONITOR_USER_INVALID_DNMonitor user DN value '%s' is invalid because: %sServerMessages.ERR_SETUP_PASSWORD_FILE_NO_PASSWORDUnable to read password in file '%s'. A password file must contain a single line with the keystore password, details: %sServerMessages.ERR_SETUP_PROFILE_ADD_BACKENDUnable to create '%s' backend (%s)ServerMessages.ERR_SETUP_PROFILE_ADD_INDEXUnable to add index for attribute '%s' (%s)ServerMessages.ERR_SETUP_PROFILE_CLI_NO_PROFILE_PROVIDEDYou must select at least one profile by using the option '%s'. %sServerMessages.ERR_SETUP_PROFILE_CREATE_REPLICATION_DOMAINUnable to create replication domain for base DN '%s' (%s)ServerMessages.ERR_SETUP_PROFILE_EMPTY_DN_PARAMETERThe value for DN parameter '%s' of profile '%s' cannot be emptyServerMessages.ERR_SETUP_PROFILE_IMPORT_IOAn IO error occurred while running profile '%s': '%s'ServerMessages.ERR_SETUP_PROFILE_INVALID_FOLDERFolder '%s' of the setup profile '%s' must be a readable existing folderServerMessages.ERR_SETUP_PROFILE_INVALID_PARAMETERS_SCRIPT_FILEFile '%s' from the setup profile '%s' must be a readable regular fileServerMessages.ERR_SETUP_PROFILE_INVALID_VERSION_FOLDERLast folder of profile '%s' path '%s' must be the profile version (two or three digits separated by either dot or hyphen, e.g /path/to/profile/6.5.0)ServerMessages.ERR_SETUP_PROFILE_MISSING_MANDATORY_SCRIPT_FILEFolder of the setup profile '%s' must contain a '%s' readable regular fileServerMessages.ERR_SETUP_PROFILE_PARAMETER_BLANK_DOMAIN_VALUEThe value for domain parameter '%s' of profile '%s' cannot be blankServerMessages.ERR_SETUP_PROFILE_SCRIPT_EXECUTIONThe '%s' setup profile failed: %sServerMessages.ERR_SETUP_PROFILE_SEARCH_RESOURCE_IN_OTHER_VERSIONSUnable to find resource '%s' of profile '%s' in profile version foldersServerMessages.ERR_SETUP_ROOT_USER_INVALID_DNThe administrator user bind DN '%s' is invalid. %sServerMessages.ERR_SETUP_UNABLE_TO_WRITE_FILEUnable to write file '%s' because: '%s'ServerMessages.ERR_SETUP_WRITING_PASSWORD_INTERNAL_FILEAn error occurred while storing provided password in the instance file '%s', details: %sServerMessages.ERR_SMTP_ASNH_SUBJECT_DUPLICATE_TYPEThe message subject definitions contained in configuration entry '%s' have multiple subjects defined for notification type %sServerMessages.ERR_SMTP_ASNH_SUBJECT_NO_COLONUnable to parse message subject value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the subjectServerMessages.ERR_SMTP_ASNH_TEMPLATE_DUPLICATE_TYPEThe message template file path definitions contained in configuration entry '%s' have multiple template file paths defined for notification type %sServerMessages.ERR_SMTP_ASNH_TEMPLATE_NO_COLONUnable to parse message template file path value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the template file pathServerMessages.ERR_SMTP_ASNH_TEMPLATE_NO_SUCH_FILEThe message template file '%s' referenced in configuration entry '%s' does not existServerMessages.ERR_SMTP_ASNH_TEMPLATE_UNCLOSED_TOKENAn unclosed token was found starting at column %d of line %dServerMessages.ERR_STARTOK_CANNOT_OPEN_FOR_READINGAn error occurred while attempting to open the current configuration file %s for reading in order to copy it to the ".startok" file: %sServerMessages.ERR_STARTUP_PLUGIN_ERRORA fatal error occurred when executing one of the Directory Server startup plugins: %s (error ID %d). The Directory Server startup process has been abortedServerMessages.ERR_TASK_ADDSCHEMAFILE_CANNOT_NOTIFY_SYNC_PROVIDERAn error occurred while attempting to notify a synchronization provider of type %s about the schema changes made by the add schema file task: %sServerMessages.ERR_TASK_ADDSCHEMAFILE_ERROR_LOADING_SCHEMA_FILEAn error occurred while attempting to load the contents of schema file %s into the server schema: %sServerMessages.ERR_TASK_ADDSCHEMAFILE_NO_FILENAMEUnable to add one or more files to the server schema because no schema file names were provided in attribute %s of task entry %sServerMessages.ERR_TASK_ADDSCHEMAFILE_NO_SUCH_FILEUnable to add one or more files to the server schema because the specified schema file %s does not exist in schema directory %sServerMessages.ERR_TASK_CANNOT_PARSE_ACTUAL_START_TIMEAn error occurred while trying to parse the actual start time value %s from task entry %sServerMessages.ERR_TASK_CANNOT_PARSE_COMPLETION_TIMEAn error occurred while trying to parse the completion time value %s from task entry %sServerMessages.ERR_TASK_CANNOT_PARSE_SCHEDULED_START_TIMEAn error occurred while trying to parse the scheduled start time value %s from task entry %sServerMessages.ERR_TASK_EXECUTE_FAILEDAn error occurred while executing the task defined in entry %s: %sServerMessages.ERR_TASK_INVALID_ATTRIBUTE_VALUEAttribute %s has an invalid value. Reason: %sServerMessages.ERR_TASK_INVALID_STATEThe task defined in entry %s is invalid because it has an invalid state %sServerMessages.ERR_TASK_MISSING_ATTRTask entry %s is missing required attribute %sServerMessages.ERR_TASK_MULTIPLE_ATTRS_FOR_TYPEThere are multiple instances of attribute %s in task entry %sServerMessages.ERR_TASK_MULTIPLE_VALUES_FOR_ATTRThere are multiple values for attribute %s in task entry %sServerMessages.ERR_TASKBE_ADD_DISALLOWED_DNNew entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasksServerMessages.ERR_TASKBE_BACKING_FILE_MISSING_PARENTThe parent directory %s for the new task data backing file %s does not exist. Please create this directory before attempting to use this path for the new backing file or choose a new pathServerMessages.ERR_TASKBE_BACKING_FILE_PARENT_NOT_DIRECTORYThe parent directory %s for the new task data backing file %s exists but is not a directory. Please choose a new path for the task data backing fileServerMessages.ERR_TASKINFO_ACCESSING_LOGSError accessing logs for task '%s': %sServerMessages.ERR_TASKINFO_CANCELING_TASKError canceling task '%s': %sServerMessages.ERR_TASKINFO_RETRIEVING_TASK_ENTRYError retrieving task entry %s: %sServerMessages.ERR_TASKSCHED_CANNOT_CREATE_BACKING_FILEAn error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %sServerMessages.ERR_TASKSCHED_CANNOT_INITIALIZE_INTERNALAn error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %sServerMessages.ERR_TASKSCHED_CANNOT_INSTANTIATE_CLASS_AS_TASKAn error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?ServerMessages.ERR_TASKSCHED_CANNOT_SCHEDULE_RECURRING_TASK_FROM_ENTRYAn error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %sServerMessages.ERR_TASKSCHED_CANNOT_SCHEDULE_TASK_FROM_ENTRYAn error occurred while attempting to parse entry %s as a task and add it to the scheduler: %sServerMessages.ERR_TASKSCHED_CANNOT_WRITE_BACKING_FILEAn error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lostServerMessages.ERR_TASKSCHED_DEPENDENCY_MISSINGUnable to schedule task %s because its dependency task %s is missingServerMessages.ERR_TASKSCHED_ENTRY_HAS_NO_PARENTEntry %s read from the tasks backing file is invalid because it has no parent and does not match the task root DN of %sServerMessages.ERR_TASKSCHED_ERROR_READING_TASK_BACKING_FILEAn error occurred while attempting to read from the tasks data backing file %s: %sServerMessages.ERR_TASKSCHED_ERROR_SCHEDULING_RECURRING_ITERATIONAn error occurred while attempting to schedule the next iteration of recurring task %s: %sServerMessages.ERR_TASKSCHED_INVALID_TASK_ENTRY_DNEntry %s read from the tasks backing file %s has a DN which is not valid for a task or recurring task definition and will be ignoredServerMessages.ERR_TASKTOOL_INVALID_EMAIL_ADDRESSThe value %s for option %s is not a valid email addressServerMessages.ERR_TASKTOOL_INVALID_FDAThe failed dependency action value %s is invalid. The value must be one of %sServerMessages.ERR_TIMEOUT_DURING_STARTUPThe timeout of '%d' seconds has been reached. You can use the argument '--%s' to increase this timeoutServerMessages.ERR_UNCAUGHT_THREAD_EXCEPTIONAn uncaught exception during processing for thread "%s" has caused it to terminate abnormally. The stack trace for that exception is: %sServerMessages.ERR_UNKNOWN_ATTRIBUTE_IN_HISTORICALThe entry %s has historical information for attribute %s which is not defined in the schema. This information will be ignoredServerMessages.ERR_UNKNOWN_FINGERPRINT_DIGESTDigest algorithm '%s' of fingerprint '%s' is not supported by the JVMServerMessages.ERR_UPDATING_GENERATION_IDAn unexpected error occurred when updating generation ID for domain "%s": %sServerMessages.ERR_UPGRADE_ADD_CONFIG_FILE_FAILSAn error occurred while adding configuration file '%s': %sServerMessages.ERR_UPGRADE_ADDATTRIBUTE_FAILSAn error occurred while adding one or more attributes to the schema file '%s': %sServerMessages.ERR_UPGRADE_CANNOT_READ_CONFIG_FILEAn error occured when trying to read the configuration file %s: %sServerMessages.ERR_UPGRADE_CONFIG_SCHEMA_FILE"Error parsing existing schema file '%s' - %s"ServerMessages.ERR_UPGRADE_COPY_FILES_FROM_TEMPLATEAn error occurred while copying data from '%s' to the server instance configuration directory. Error details: %sServerMessages.ERR_UPGRADE_COPYSCHEMA_FAILSAn error occurred while copying the schema file '%s': %sServerMessages.ERR_UPGRADE_INCOMPATIBLE_ARGSThe argument '%s' is incompatible with '%s'ServerMessages.ERR_UPGRADE_TASK_CANNOT_CREATE_DIRThe directory '%s' could not be created: %sServerMessages.ERR_UPGRADE_TASK_MIGRATE_ROOT_DN_CANNOT_CREATE_DB_DIRRoot DNs could not be migrated because the '%s' directory could not be created: %sServerMessages.ERR_UPGRADE_TASK_MODIFY_CONFIG_FILEAn error occurred while trying to modify %s : %sServerMessages.ERR_UPGRADE_TO_PREVIOUS_CONF_VERSIONThe OpenDJ binary version '%s' is older than the configuration version '%s', it usually means that an older version has been unzipped over the previous binaries. Unzip a more recent version than the configuration version and run upgrade againServerMessages.ERR_UPGRADE_TO_PREVIOUS_DATA_VERSIONThe OpenDJ binary version '%s' is older than the data version '%s', it usually means that an older version has been unzipped over the previous binaries. Unzip a more recent version than the data version and run upgrade againServerMessages.ERR_UPGRADE_UNKNOWN_OC_ATTNo %s with OID %s exists in the schemaServerMessages.ERR_VERIFY_DN2ID_UNKNOWN_IDFile dn2id has DN <%s> referencing unknown ID %dServerMessages.ERR_VERIFY_DN2ID_WRONG_ENTRYFile dn2id has DN <%s> referencing entry with wrong DN <%s>ServerMessages.ERR_VERIFY_DUPLICATE_REFERENCEDuplicate reference to ID %d%n%sServerMessages.ERR_VERIFY_ENTRY_NON_MATCHING_KEYThe entry with ID %s is associated with the wrong key%n%sServerMessages.ERR_VERIFY_MISSING_ENTRYMissing entry %s in index %sServerMessages.ERR_VERIFY_MISSING_IDMissing ID %d%n%sServerMessages.ERR_VERIFY_UNEXPECTED_REFERENCEReference to entry <%s> which does not match the value%n%sServerMessages.ERR_VERIFY_UNKNOWN_IDReference to unknown entry ID %s%n%sServerMessages.ERR_VERIFY_UNKNOWN_REFERENCEReference to unknown ID %d%n%sServerMessages.ERR_VERIFY_WRONG_ENTRY_COUNTThe stored entry count in id2entry (%d) does not agree with the actual number of entry records found (%d)ServerMessages.ERR_VERIFYINDEX_CANNOT_LOCK_BACKENDAn error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The index verification cannot continueServerMessages.ERR_VIRTUAL_STATIC_GROUP_NO_TARGET_GROUPTarget group %s referenced by virtual static group %s does not existServerMessages.ERR_VIRTUAL_STATIC_GROUP_TARGET_CANNOT_BE_VIRTUALVirtual static group %s references target group %s which is itself a virtual static group. One virtual static group is not allowed to reference another as its target groupServerMessages.ERROR_DSREPL_INITIALIZATION_DURING_INIT_TASK_WITH_LOGAn error occurred during initialization. Last log details: %s. Task state: %sServerMessages.ERROR_DSREPL_INITIALIZATION_DURING_RESET_GENID_TASK_WITH_LOGError during the processing of the reset generationID task. Last log details: %s. Task state: %sServerMessages.ERROR_DSREPL_PURGE_METADATA_DURING_TASK_WITH_LOGAn error occurred while purging old replication meta-data. Last log details: %s. Task state: %sServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_DURING_TASK_WITH_LOGAn error occurred during the re-synchronization of the change number. Last log details: %s. Task state: %sServerMessages.ERROR_DSREPL_RESET_CHANGE_NUMBER_SEARCH_ERRORError when searching change number '%s' in the source server: %sServerMessages.ERROR_SETUP_PROFILE_PARAMETER_UNUSEDParameter(s) '%s' provided for profile '%s' is (are) not used in the profileServerMessages.INFO_ACI_ADD_FAILED_PRIVILEGEAn attempt to add the entry "%s" containing an aci attribute type failed, because the authorization DN "%s" lacked modify-acl privilegesServerMessages.INFO_ACI_ADD_LIST_ACISAdded %s Access Control Instruction (ACI) attribute types found in context "%s" to the access control evaluation engineServerMessages.INFO_ACI_HANDLER_FAIL_PROCESS_GLOBAL_ACIAn unexpected error occurred while processing the ds-cfg-global-aci attribute in configuration entry %s: %sServerMessages.INFO_ACI_MODIFY_FAILED_PRIVILEGEAn attempt to modify an aci attribute type in the entry "%s" failed, because the authorization DN "%s" lacked modify-acl privilegesServerMessages.INFO_CACHE_AND_MEMORY_REPORTFree memory = %d MB, Cache miss rate = %.1f/recordServerMessages.INFO_CANNOT_DELETE_OBSOLETE_FILEUpgrade failed to delete the obsolete file '%s'. Reason: %sServerMessages.INFO_CONFIG_AND_DATA_UPGRADE_SUMMARYOpenDJ will be upgraded from version %s to %sServerMessages.INFO_CONFIG_UPGRADE_SUMMARYOpenDJ configuration will be upgraded from version %s to %sServerMessages.INFO_CONFIG_WORK_QUEUE_CLASS_CHANGE_REQUIRES_RESTARTThe class used to provide the Directory Server work queue implementation has been changed from %s to %s, but this change will not take effect until the server is restartedServerMessages.INFO_DATA_UPGRADE_SUMMARYOpenDJ data will be upgraded from version %s to %sServerMessages.INFO_DESCRIPTION_TASK_FAILED_DEPENDENCY_ACTIONAction this task will take should one if its dependent tasks fail. The value must be one of %s. If not specified defaults to %sServerMessages.INFO_DSREPL_DR_COMPUTED_ID_FULL_COMMANDdsrepl disaster-recovery --baseDn '%s' --generated-id %sServerMessages.INFO_DSREPL_DR_WITH_VERSION_ALREADY_RUNDisaster recovery for domain '%s' has already been run with recovery ID '%s'. Verify all servers in the topology are being recovered with the same recovery IDServerMessages.INFO_DSREPL_PURGE_METADATA_START_MSGPurging old replication meta-data for server '%s' for base DNs: %sServerMessages.INFO_DSREPL_RESET_CHANGE_NUMBER_CSN_AND_DNChange number corresponds to start CSN '%s' and base DN '%s'ServerMessages.INFO_DSREPL_RESET_CHANGE_NUMBER_START_MSGStart to re-synchronize the change-log change number of server '%s' from the source server '%s'ServerMessages.INFO_DSREPL_START_INITIALIZATION_TO_ALL_REMOTEStarting initialization from '%s' to all replicas for base DNs: %sServerMessages.INFO_ERGONOMIC_SIZING_OF_JE_CLEANER_THREADSJE backend '%s' does not specify the number of cleaner threads: defaulting to %d threadsServerMessages.INFO_ERGONOMIC_SIZING_OF_JE_LOCK_TABLESJE backend '%s' does not specify the number of lock tables: defaulting to %dServerMessages.INFO_ERGONOMIC_SIZING_OF_REQUEST_HANDLER_THREADSConnection handler '%s' does not specify the number of request handler threads: defaulting to %d threadsServerMessages.INFO_ERROR_COPYING_FILEAn error occurred while copying the file '%s' to '%s'ServerMessages.INFO_ERROR_DELETING_DIRECTORYAn error occurred while deleting directory '%s'. Check that you have the rights to delete this directory and that there is no other application using it. Error was: %sServerMessages.INFO_ERROR_DELETING_FILEAn error occurred while deleting file '%s': %s. Check that you have the rights to delete this file and that there is no other application using itServerMessages.INFO_EXTERNAL_LIB_MESSAGE_WITH_EXCEPTION%s with exception: %sServerMessages.INFO_HELP_SETUP_ALL_PROFILES_FOOTERUse %s %s to list profile parametersServerMessages.INFO_INDEX_FILTER_INDEX_TYPE_DISABLED%s index type is disabled for the %s attributeServerMessages.INFO_INITIALIZE_PROGRESS_WITH_PERCENTAGE%s entries processed (%s %% complete)ServerMessages.INFO_INITIALIZE_WILL_RETRYTask '%s' to initialize domain '%s' failed to contact the source server. The task will be retried because the current server may be in the process of re-connecting to the best replication server for itselfServerMessages.INFO_JDKTOOLS_DIRECTORY_DEFAULT_VALUENo value was provided for %s, JDK tool directory is set to %sServerMessages.INFO_LABEL_BACKEND_TOOL_TOTAL_DATA_SIZE_AND_AVGTotal / Average Data Size: %d bytes / %d bytes%nServerMessages.INFO_LABEL_BACKEND_TOOL_TOTAL_KEY_SIZE_AND_AVGTotal / Average Key Size: %d bytes / %d bytes%nServerMessages.INFO_LDIF_CONNHANDLER_RESULT_CODEResult Code: %d (%s)ServerMessages.INFO_OTHER_MESSAGE%s: received message <%s>The Referential Integrity plugin background processing update interval has been changed from %s to %s, the new value will now be during background processingServerMessages.INFO_PLUGIN_REFERENT_LOGFILE_CHANGE_REQUIRES_RESTARTThe file name that the Referential Integrity plugin logs changes to during background processing has been changed from %s to %s, but this change will not take effect until the server is restartedServerMessages.INFO_PROFILE_PARAMETER_HELP_HEADER%s (%s) parametersServerMessages.INFO_PROFILE_PARAMETER_NO_PARAMETERSProfile '%s (%s)' does not have any parametersServerMessages.INFO_PROXY_DISCOVERY_RECONFIGURATION_IN_PROGRESSConfiguration of proxy backend '%s' with service discovery mechanism '%s' is in progress. Requests will not be proxied until configuration completesServerMessages.INFO_PROXY_SERVER_AVAILABLEThe server '%s' for proxy backend '%s' is available and will be used for proxying requestsServerMessages.INFO_ROOTDSE_UPDATED_SHOW_ALL_ATTRSThe root DSE configuration has been updated so that configuration attribute %s will now use a value of %sServerMessages.INFO_SASL_UNSUPPORTED_CALLBACKAn unsupported or unexpected callback was provided to the SASL server for use during %s authentication: %sServerMessages.INFO_SETUP_ENABLING_WINDOWS_SERVICE_OUTPUTEnable windows service command (return code '%d') output: %sServerMessages.INFO_SETUP_INTERACTIVE_PROFILE_VERSION_PROMPTWhich version of '%s' do you want to use (minimum %s)?ServerMessages.INFO_SETUP_INTERACTIVE_SUMMARIZE_PROFILE_VERSIONConfigure server for profile '%s (%s)'ServerMessages.INFO_TASK_SHUTDOWN_CUSTOM_MESSAGEThe Directory Server shutdown process has been initiated by task %s: %sServerMessages.INFO_TASK_TOOL_RECURRING_TASK_SCHEDULEDRecurring %s task %s scheduled successfullyServerMessages.INFO_TASK_TOOL_TASK_NOT_SUCCESSFULL%s task %s did not complete successfullyServerMessages.INFO_TASK_TOOL_TASK_SCHEDULED_NOW%s task %s scheduled to start immediatelyServerMessages.INFO_TASK_TOOL_TASK_SUCCESSFULL%s task %s has been successfully completedServerMessages.INFO_TIME_IN_MINUTES_SECONDS%d minutes, %d secondsServerMessages.INFO_TOP_NOT_SUPPORTED_ON_OSCannot extract process statistics (by running "top" command) on OS '%s'. Only %s dump samples will be collectedServerMessages.INFO_TRUSTSTORESYNC_ADD_FAILEDError while trying to add entry %s to the trust store: %sServerMessages.INFO_TRUSTSTORESYNC_ADMIN_SUFFIX_SEARCH_FAILEDError while searching base %s to synchronize the trust store: %sServerMessages.INFO_UPGRADE_CHANGE_DONE_IN_SPECIFIC_FILE...Change(s) done in %s (x%s)ServerMessages.INFO_UPGRADE_REBUILD_INDEX_STARTSRebuilding index(es) %s for base dn(s): %sServerMessages.INFO_UPGRADE_REPLACE_HDAP_ENDPOINT_AUTH_MECHANISM_CONFIGReplace the authentication mechanism of the '/hdap' endpoint '%s' with the new HDAP authorization mechanism '%s'ServerMessages.INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CONFIRM_ALIAS_REMOVALOpenDJ 6.0.0 drops support for Root DNs and replaces them with standard user entries which are stored in LDIF backends. The root DN '%s' has multiple alias names, but only the alias name '%s' will be kept. Do you want to proceed with the upgrade?ServerMessages.INFO_UPGRADE_TASK_MIGRATE_ROOT_DN_CONFIRM_RENAMEOpenDJ 6.0.0 drops support for Root DNs and replaces them with standard user entries which are stored in LDIF backends. The root DN '%s' does not have an alias name so it must be renamed to '%s' so that it no longer resides inside the configuration. Do you want to proceed with the upgrade?ServerMessages.INFO_UPGRADE_TASK_RENAME_PDB_DIRRenaming PDB backend directory '%s' to '%s'ServerMessages.NOTE_AVOID_YOYO_EFFECTDS(%s) stayed connected to RS(%s) to avoid the yoyo effectServerMessages.NOTE_BACKEND_STARTEDThe database backend %s containing %d entries has startedServerMessages.NOTE_BEST_RSRS(%s) has been evaluated to be the best replication server for DS(%s) to connect to because it was the only one standing after all testsServerMessages.NOTE_BIGGEST_WEIGHT_RSDS(%s) will connect to RS(%s) because it has the biggest weight among all the replication serversServerMessages.NOTE_CONFIG_DB_DIR_REQUIRES_RESTARTThe change to the DB directory will not take effect until the backend is restarted. The DB files from the previous directory %s must be moved to the new directory %s after shutting down the backend to retain the existing dataServerMessages.NOTE_CONFIG_FILE_USING_STARTOK_FILEThe Directory Server is starting using the last known good configuration file %s rather than the active configuration file %sServerMessages.NOTE_DISCONNECT_DS_FROM_OVERLOADED_RSDS(%s) disconnected from overloaded RS(%s)ServerMessages.NOTE_DO_NOT_DISCONNECT_DS_FROM_ACCEPTABLE_LOAD_RSDS(%s) not disconnected from current RS(%s), because RS is underloaded or its load goal is reachedServerMessages.NOTE_DO_NOT_DISCONNECT_DS_FROM_OVERLOADED_RSDS(%s) not disconnected from overloaded RS(%s), other DSs will disconnectServerMessages.NOTE_ERR_FRACTIONALFractional replication : exception for domain : %s : %sServerMessages.NOTE_ERR_FRACTIONAL_CONFIG_NOT_OPTIONAL_ATTRIBUTEWrong fractional replication configuration : attribute %s is not optional in class %sServerMessages.NOTE_ERR_FRACTIONAL_FORBIDDEN_FULL_UPDATE_FRACTIONALThe export of domain %s from server %s to all other servers of the topology is forbidden as the source server has some fractional configuration : only fractional servers in a replicated topology does not make senseServerMessages.NOTE_ERR_FRACTIONAL_FORBIDDEN_OPERATIONThe following operation has been forbidden in suffix %s due to inconsistency with the fractional replication configuration : %sServerMessages.NOTE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_BAD_REMOTEThe online full update for importing suffix %s data from remote directory server %s has been stopped due to fractional configuration inconsistency between destination and source server : imported data set has not the same fractional configurationServerMessages.NOTE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_REMOTE_IS_FRACTIONALThe online full update for importing suffix %s data from remote directory server %s has been stopped due to fractional configuration inconsistency between destination and source server : imported data set has some fractional configuration but not destination serverServerMessages.NOTE_ERR_UNABLE_TO_ENABLE_ECL_VIRTUAL_ATTRError when loading a virtual attribute for external change log: Attribute: %s , Error: %sServerMessages.NOTE_IMPORT_LDIF_DB_MEM_BUF_INFOSetting DB cache size to %d bytes and phase one buffer size to %d bytesServerMessages.NOTE_IMPORT_LDIF_TOT_MEM_BUFThe amount of free memory available to the import task is %d bytes. The number of phase one buffers required is %d buffersServerMessages.NOTE_NO_NEED_TO_REBALANCE_DSS_BETWEEN_RSSDS(%s) not disconnected from current RS(%s), since there is no need to rebalance all directory servers to other replication servers in the topologyServerMessages.NOTE_READER_EXCEPTIONException when reading messages from %s: %sServerMessages.NOTE_READER_RECEIVED_STOP%s is disconnecting from this replication server %sServerMessages.NOTE_REBUILD_STARTRebuild of index(es) %s started with %d total entries to processServerMessages.NOTE_RESET_GENERATION_IDThe generation ID for domain "%s" has been reset to %sServerMessages.NOTE_RS_ON_DIFFERENT_HOST_THAN_DSRS(%s) is on a different host than DS(%s), but at least another RS is on the same hostServerMessages.NOTE_RS_ON_DIFFERENT_VM_THAN_DSRS(%s) is not on the same virtual machine as DS(%s) but another RS isServerMessages.NOTE_SCHEMA_IMPORT_FAILEDA schema element could not be imported: %s, %sServerMessages.NOTE_SERVER_SHUTDOWNThe Directory Server has started the shutdown process. The shutdown was initiated by an instance of class %s and the reason provided for the shutdown was %sServerMessages.NOTE_SERVER_STATE_RECOVERYServerState recovery for domain %s, updated with changeNumber %sServerMessages.NOTE_TASK_STARTED%s task %s started executionServerMessages.NOTE_UNKNOWN_RSRS(%s) could not be contacted by DS(%s)ServerMessages.NOTE_UNNECESSARY_PRESENCE_INDEXBoth equality and presence index types are defined for attribute '%s'. When no presence index exists, presence search filters are processed using the equality index. Therefore, consider deleting the presence index for attribute '%s'ServerMessages.PROXY_DIAGNOSTIC_MESSAGE_WITH_CLIENT_SIDE_RESULT_CODEInitial result code was '%s', with diagnostic message: %sServerMessages.WARN_ACI_ADD_FAILED_DECODEAn attempt to add the entry "%s" containing an aci attribute type failed because of the following reason: %sServerMessages.WARN_ACI_ATTRIBUTE_NOT_INDEXEDBackend %s does not have a presence index defined for attribute type %s. Access control initialization may take a very long time to complete in this backendServerMessages.WARN_ACI_MODIFY_FAILED_DECODEAn attempt to modify an aci attribute type in the entry "%s" failed because of the following reason: %sServerMessages.WARN_ACI_SYNTAX_DOUBLE_PERIOD_IN_NUMERIC_OIDThe provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the numeric OID contained two consecutive periods at position %dServerMessages.WARN_ACI_SYNTAX_INVALID_BIND_RULE_KEYWORD_OPERATOR_COMBOThe provided Access Control Instruction (ACI) bind rule keyword string "%s" is invalid for the bind rule operator string "%s"ServerMessages.WARN_ACI_SYNTAX_INVALID_IPV6_FORMATThe provided Access Control Instruction (ACI) bind rule IP address expression "%s" failed to parse for the following reason: "%s"ServerMessages.WARN_ACI_SYNTAX_INVALID_SSF_FORMATThe provided Access Control Instruction (ACI) bind rule SSF expression "%s" failed to parse for the following reason: "%s"ServerMessages.WARN_ACI_SYNTAX_INVALID_TARGATTRFILTERS_FILTER_LISTS_FILTERThe provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because one or more of the specified filters are invalid for the following reason: %sServerMessages.WARN_ACI_SYNTAX_INVALID_TARGET_DUPLICATE_KEYWORDSThe provided Access Control Instruction (ACI) target keyword value "%s" was seen multiple times in the ACI "%s"ServerMessages.WARN_ACI_SYNTAX_INVALID_TARGET_NOT_OPERATORThe provided Access Control Instruction (ACI) target operator value "%s" is invalid. The only valid target operator value for the "%s" keyword is '='ServerMessages.WARN_ACI_SYNTAX_INVALID_TIMEOFDAY_FORMATThe provided Access Control Instruction (ACI) bind rule timeofday expression "%s" failed to parse for the following reason: "%s"ServerMessages.WARN_ACI_SYNTAX_MAX_USERATTR_INHERITANCE_LEVEL_EXCEEDEDThe provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid. The inheritance level value cannot exceed the max level limit of %sServerMessages.WARN_ACI_SYNTAX_TARGET_DN_NOT_DESCENDENTOFThe provided Access Control Instruction (ACI) target expression DN value "%s" is invalid. The target expression DN value must be a descendant of the ACI entry DN "%s", if no wild-card is specified in the target expression DNServerMessages.WARN_ADD_ATTR_IS_OBSOLETEEntry "%s" cannot be added because it contains attribute type %s which is declared OBSOLETE in the server schemaServerMessages.WARN_ADD_OC_IS_OBSOLETEEntry "%s" cannot be added because it contains objectclass %s which is declared OBSOLETE in the server schemaServerMessages.WARN_BACKEND_DEBUG_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the process exits, so no further action should be requiredServerMessages.WARN_BIND_CANNOT_PROCESS_USER_CURSOR_ENTRY_LIMITThe user-specific cursor entry limit value '%s' contained in user entry '%s' could not be parsed as an integer. The default server cursor entry limit will be usedServerMessages.WARN_BIND_CANNOT_PROCESS_USER_IDLE_TIME_LIMITThe user-specific idle time limit value %s contained in user entry %s could not be parsed as an integer. The default server idle time limit will be usedServerMessages.WARN_BIND_CANNOT_PROCESS_USER_SIZE_LIMITThe user-specific size limit value %s contained in user entry %s could not be parsed as an integer. The default server size limit will be usedServerMessages.WARN_BIND_CANNOT_PROCESS_USER_TIME_LIMITThe user-specific time limit value %s contained in user entry %s could not be parsed as an integer. The default server time limit will be usedServerMessages.WARN_CANNOT_OPEN_DATABASE_BECAUSE_SHUTDOWN_WAS_REQUESTEDCannot open database %s because shutdown was requested from replication server RS(%s)ServerMessages.WARN_CANNOT_SET_BROKER_SOCKET_TIMEOUTError while setting replication listener socket timeout to 1 second for domain '%s', server state may be reported as being a bit late with respect to other servers. Cause was: %sServerMessages.WARN_CNI_CANNOT_ADVANCE_MISSING_UPDATE_FROM_REPLICAChange number indexing cannot advance because replica '%s' has not sent any messages since '%s'. The changelog is temporarily unable to purge old files. Verify whether the replica is still running or is connected to a replication serverServerMessages.WARN_COMPARE_OP_NO_SUCH_ATTREntry "%s" does not contain any values for attribute "%s"ServerMessages.WARN_COMPARE_OP_NO_SUCH_ATTR_WITH_OPTIONSEntry "%s" does not contain any values for attribute "%s" with the specified set of optionsServerMessages.WARN_CONFIG_BACKEND_CANNOT_REGISTER_BACKENDAn error occurred while attempting to register backend %s with the Directory Server: %sServerMessages.WARN_CONFIG_BACKEND_CANNOT_RELEASE_SHARED_LOCKAn error occurred while attempting to release a shared lock for backend %s: %s. This may interfere with operations that require exclusive access, including LDIF import and restoring a backupServerMessages.WARN_CONFIG_BACKEND_DUPLICATE_BACKEND_IDThe backend defined in configuration entry %s has a backend ID of %s that conflicts with the backend ID for another backend in the server. The backend will be disabledServerMessages.WARN_CONFIG_FILE_NO_STARTOK_FILENo last known good configuration file %s exists. The server will attempt to start using the active configuration file %sServerMessages.WARN_CONFIG_LOGGING_UNSUPPORTED_FIELDS_IN_LOG_FORMATThe log format for %s contains the following unsupported fields: %s. Their output will be replaced with a dash ("-") characterServerMessages.WARN_CONFIG_MANUAL_CHANGES_DETECTEDThe Directory Server has detected that one or more external changes have been made to the configuration file %s while the server was online, but another change has caused the server configuration to be overwritten. The manual changes have not been applied, but they have been preserved in file %sServerMessages.WARN_CONFIG_PLUGIN_LISTED_MULTIPLE_TIMESThe plugin order definition for plugins of type %s includes multiple references to the '%s' plugin. This may cause the plugin order to be evaluated incorrectlyServerMessages.WARN_CONFIG_SCHEMA_FILE_HAS_SCHEMA_WARNINGThe config schema file '%s' generated warning when trying to update schema with its content: %sServerMessages.WARN_CONFIG_SCHEMA_FILE_HAS_SCHEMA_WARNING_WITH_OVERWRITEThe config schema file '%s' generated warning when trying to update schema with its content, despite allowing to overwrite definitions: %sServerMessages.WARN_CONFIG_SCHEMA_MULTIPLE_ENTRIES_IN_FILESchema configuration file %s in directory %s contains more than one entry. Only the first entry will be examined, and the additional entries will be ignoredServerMessages.WARN_CONNECTION_FROM_SAME_REPLICAReplica '%s' for domain '%s' tried to connect but the replication server is still processing messages from the previous replication session and considers the replica already connected. The connection will be closed, the replica will connect againServerMessages.WARN_CTHEARTBEAT_JOIN_TIMEDOUTChangeTime Heartbeat publisher '%s' for domain '%s' will be forcibly stopped because the peer server is unresponsiveServerMessages.WARN_DEPRECATED_CONFIGURATION'%s' is DEPRECATED for removal since %s. Its usage is highly discouragedServerMessages.WARN_DEREGISTER_BASEDN_MISSING_HIERARCHYBase DN %s has been deregistered from the Directory Server for backend %s. This base DN had both superior and subordinate entries in other backends, and there might be inconsistent or unexpected behavior when accessing entries in this portion of the hierarchy because of the missing entries that had been held in the de-registered backendServerMessages.WARN_DYNAMICGROUP_NONEXISTENT_BASE_DNBase DN %s specified in dynamic group %s does not exist in the serverServerMessages.WARN_FORCE_CLOSE_DS_ON_STUCK_CONNECTIONThe replication domain connection for '%s' will be forcibly closed because the peer replication server '%s' is unresponsiveServerMessages.WARN_FORCE_CLOSE_RS_ON_STUCK_CONNECTIONThe replication server domain connection for '%s' will be forcibly closed because the peer replication server '%s' is unresponsiveServerMessages.WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_MISSINGThe directory %s referenced by the LDIF connection handler defined in configuration entry %s does not exist. The LDIF connection handler will start, but will not be able to process any changes until this directory is createdServerMessages.WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORYThe value %s specified as the LDIF directory path for the LDIF connection handler defined in configuration entry %s exists but is not a directory. The specified path must be a directory. The LDIF connection handler will start, but will not be able to proces any changes until this path is changed to a directoryServerMessages.WARN_LDIFEXPORT_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the export process exits, so no further action should be requiredServerMessages.WARN_LDIFIMPORT_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the exclusive lock for backend %s: %s. This lock should automatically be cleared when the import process exits, so no further action should be requiredServerMessages.WARN_LEGACY_CONFIGURATION'%s' is LEGACY since %s. Its usage is highly discouragedServerMessages.WARN_LOGGER_SET_PERMISSION_FAILEDError occurred while setting file permissions for the log file %s: %sServerMessages.WARN_LOGGER_UNABLE_SET_PERMISSIONSThis platform does not support setting file permissions %s to the log file %sServerMessages.WARN_NO_AVAILABLE_CHANGELOGSDirectory server DS(%s) was unable to connect to any replication servers for domain "%s"ServerMessages.WARN_NON_ATOMIC_SUBTREE_DELETEThe subtree delete against '%s' is being performed non-atomically because it is deleting more than %s subordinate entries. To prevent inconsistency across replicas, the client must retry this same delete operation until it succeedsServerMessages.WARN_PLUGIN_PWIMPORT_CANNOT_DECODE_POLICY_DNAn error occurred while attempting to decode the value of the custom password policy attribute in entry '%s': %s. Any passwords contained in the entry will be encoded using the default storage schemes, but authentication as this user might not be possibleServerMessages.WARN_PLUGIN_PWIMPORT_NO_SUCH_POLICYEntry '%s' indicates that it uses custom password policy '%s', but no such policy is defined in the server. Any passwords contained in the entry will be encoded using the default storage schemes, but authentication as this user might not be possibleServerMessages.WARN_PROFILE_PARAMETER_HELP_PROFILE_VERSION_NOT_FOUNDVersion %s not found, best match is %sServerMessages.WARN_PROXY_PRIMARY_SERVERS_UNAVAILABLEThe primary servers for proxy backend '%s' are unavailable. The secondary servers, if available, will be used for processing requests until the primary servers become available again. The last failure that prevented the primary servers from being used was: %sServerMessages.WARN_PROXY_SECONDARY_SERVERS_UNAVAILABLEThe secondary servers for proxy backend '%s' are unavailable. If the primary servers are unavailable, or become unavailable, then it will no longer be possible to proxy requests. The last failure that prevented the secondary servers from being used was: %sServerMessages.WARN_QUEUE_UNABLE_TO_CANCELThe work queue caught an exception while trying to cancel pending operation %s when the Directory Server was shutting down: %sServerMessages.WARN_REBUILDINDEX_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the rebuild process exits, so no further action should be requiredServerMessages.WARN_REPLICATION_DOMAIN_STATUS_NOT_HEALTHYReplication domain '%s' status '%s' is not healthyServerMessages.WARN_SERVICE_DISCOVERY_REPLICATION_MECHANISM_WRONG_REPLICAReplication server '%s' references server '%s' that could not be parsed correctly; the definition will be skippedServerMessages.WARN_SERVICE_DISCOVERY_SCHEDULED_TASK_FAILUREScheduled discovery '%s' failed : %sCannot gather naming contexts from server %s: %sServerMessages.WARN_SET_PERMISSIONS_FAILEDAn error occurred while setting file permissions for the backend database directory %s: %sServerMessages.WARN_SETUP_DELETE_DIRECTORYAn error occurred while attempting to remove content of directory '%s': %sServerMessages.WARN_SHUTDOWN_CANNOT_RELEASE_SHARED_BACKEND_LOCKAn error occurred while attempting to release a shared lock for backend %s: %s. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessaryServerMessages.WARN_SUBENTRY_FILTER_NOT_INDEXEDThe search filter "%s" used by subentry manager is not indexed in backend %s. Backend initialization for subentry manager processing might take a very long time to completeServerMessages.WARN_TTL_INDEX_OVER_INDEX_ENTRY_LIMITUnable to locate all expired entries on backend '%s' because the ttl-enabled index '%s' has reached the configured index-entry-limitServerMessages.WARN_UNABLE_SET_PERMISSIONSThis platform does not support setting file permissions %s to the database directory %sServerMessages.WARN_VERIFYINDEX_CANNOT_UNLOCK_BACKENDAn error occurred while attempting to release the shared lock for backend %s: %s. This lock should automatically be cleared when the verification process exits, so no further action should be requiredServerMessages.WARN_WAIT4DEL_CANNOT_OPEN_LOG_FILEWARNING: Unable to open log file %s for reading: %sServerMessages.WARN_WAIT4DEL_CANNOT_OPEN_OUTPUT_FILEWARNING: Unable to open output file %s for writing: %sServerMessages.WARN_WORKER_INTERRUPTED_WITHOUT_SHUTDOWN%s was interrupted while waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effectsServerMessages.WARN_WORKER_WAITING_UNCAUGHT_EXCEPTIONAn unexpected exception was caught while %s was waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effects -
Uses of LocalizableMessageDescriptor.Arg2 in org.opends.server.core
Methods in org.opends.server.core with parameters of type LocalizableMessageDescriptor.Arg2Modifier and TypeMethodDescriptionstatic voidLockFileManager.acquireExclusiveLockForBackend(String backendID, LocalizableMessageDescriptor.Arg2<Object, Object> failureMsg, DirectoryEnvironmentConfig environmentConfig) Attempts to acquire an exclusive lock on the specified backend ID.static voidLockFileManager.acquireSharedLockForBackend(String backendID, LocalizableMessageDescriptor.Arg2<Object, Object> failureMsg, DirectoryEnvironmentConfig environmentConfig) Attempts to acquire an shared lock on the specified backend ID.static voidLockFileManager.releaseBackendLock(String backendID, LocalizableMessageDescriptor.Arg2<Object, Object> failureMsg, DirectoryEnvironmentConfig environmentConfig) Attempts to release a lock on the backend id. -
Uses of LocalizableMessageDescriptor.Arg2 in org.opends.server.tasks
Methods in org.opends.server.tasks with parameters of type LocalizableMessageDescriptor.Arg2Modifier and TypeMethodDescriptionvoidImportExportParams.validate(LocalizableMessageDescriptor.Arg2<Object, Object> includeBranchErrMsg, LocalizableMessageDescriptor.Arg2<Object, Object> excludeBranchErrMsg, LocalizableMessageDescriptor.Arg2<Object, Object> includeFilterErrMsg, LocalizableMessageDescriptor.Arg2<Object, Object> excludeFilterErrMsg) Validates the parameters provided in the constructor.