mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git
opends/src/messages/messages/config.properties
@@ -153,37 +153,18 @@ trying to close the LDIF writer: %s SEVERE_ERR_CONFIG_FILE_UNWILLING_TO_IMPORT_41=The Directory Server \ configuration may not be altered by importing a new configuration from LDIF FATAL_ERR_CONFIG_LOGGER_CANNOT_GET_BASE_42=An error occurred while attempting \ to retrieve the base logger entry cn=Loggers,cn=config from the Directory \ Server configuration: %s SEVERE_WARN_CONFIG_LOGGER_BASE_DOES_NOT_EXIST_43=The logger configuration \ base cn=Loggers,cn=config does not exist in the Directory Server \ configuration. Logging facilities will not be available until this entry is \ created and the Directory Server is restarted SEVERE_WARN_CONFIG_LOGGER_NO_ACTIVE_ACCESS_LOGGERS_44=There are no active \ access loggers defined in the Directory Server configuration. No access \ logging will be performed SEVERE_WARN_CONFIG_LOGGER_NO_ACTIVE_ERROR_LOGGERS_45=There are no active \ error loggers defined in the Directory Server configuration. No error \ logging will be performed SEVERE_ERR_CONFIG_LOGGER_ENTRY_UNACCEPTABLE_47=Configuration entry %s does \ not contain a valid logger configuration: %s. It will be ignored INFO_CONFIG_UNKNOWN_UNACCEPTABLE_REASON_48=Unknown unacceptable reason SEVERE_ERR_CONFIG_LOGGER_CANNOT_CREATE_LOGGER_49=An error occurred while \ attempting to create a Directory Server logger from the information in \ configuration entry %s: %s SEVERE_ERR_CONFIG_LOGGER_INVALID_OBJECTCLASS_50=Configuration entry %s does \ not contain a valid objectclass for a Directory Server access, error, or \ debug logger definition INFO_CONFIG_LOGGER_DESCRIPTION_CLASS_NAME_51=The fully-qualified name of the \ Java class that defines the Directory Server logger. If this is altered \ while the associated logger is enabled, then that logger must be disabled and \ re-enabled for the change to take effect SEVERE_ERR_CONFIG_LOGGER_NO_CLASS_NAME_52=Configuration entry %s does not \ contain a valid value for configuration attribute ds-cfg-java-class which \ specifies the fully-qualified class name for the associated logger SEVERE_ERR_CONFIG_LOGGER_INVALID_CLASS_NAME_53=Configuration entry %s has an \ invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_LOGGER_INVALID_ACCESS_LOGGER_CLASS_54=Class %s specified in \ attribute ds-cfg-java-class of configuration entry %s cannot be \ instantiated as a Directory Server access logger: %s @@ -193,37 +174,6 @@ SEVERE_ERR_CONFIG_LOGGER_INVALID_DEBUG_LOGGER_CLASS_56=Class %s specified in \ attribute ds-cfg-java-class of configuration entry %s cannot be \ instantiated as a Directory Server debug logger: %s INFO_CONFIG_LOGGER_DESCRIPTION_ENABLED_57=Indicates whether this Directory \ Server logger should be enabled. Changes to this attribute will take effect \ immediately SEVERE_ERR_CONFIG_LOGGER_NO_ENABLED_ATTR_58=Configuration entry %s does not \ contain a valid value for configuration attribute ds-cfg-enabled which \ indicates whether the logger should be enabled for use in the Directory \ Server SEVERE_ERR_CONFIG_LOGGER_INVALID_ENABLED_VALUE_59=Configuration entry %s has \ an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_CORE_DESCRIPTION_ALLOW_ATTR_EXCEPTIONS_60=Indicates whether to \ allow some flexibility in the characters that may be used in attribute names. \ By default, attribute names may only contain ASCII alphabetic letters, \ numeric digits, and dashes, and they must begin with a letter. If attribute \ name exceptions are enabled, then the underscore character will also be \ allowed and the attribute name may also start with a digit. Changes to this \ configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_ALLOW_EXCEPTIONS_61=Configuration entry %s has \ an invalid value for configuration attribute \ ds-cfg-allow-attribute-name-exceptions (it should be a Boolean value of true \ or false): %s INFO_CONFIG_CORE_DESCRIPTION_INVALID_SYNTAX_BEHAVIOR_62=Behavior that the \ Directory Server should exhibit if it discovers an \ attribute whose value does not conform to the syntax for that attribute. \ Acceptable values for this attribute are "reject" to reject the invalid \ value, "warn" to accept the invalid value but log a warning message, or \ "accept" to accept the invalid value with no warning. Changes to this \ configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_ENFORCE_STRICT_SYNTAX_63=Configuration entry \ %s has an invalid value for configuration attribute \ ds-cfg-invalid-attribute-syntax-behavior (it should be one of "accept", \ "reject", or "warn" ): %s MILD_ERR_CONFIG_ATTR_MULTIPLE_PENDING_VALUE_SETS_64=Configuration attribute \ %s appears to contain multiple pending value sets MILD_ERR_CONFIG_ATTR_MULTIPLE_ACTIVE_VALUE_SETS_65=Configuration attribute %s \ @@ -247,70 +197,15 @@ MILD_ERR_CONFIG_ATTR_INT_WITH_UNIT_INVALID_TYPE_72=Unable to parse value %s \ for configuration attribute %s as an integer with unit value because the \ element was of an invalid type (%s) MILD_ERR_CONFIG_JMX_ATTR_NO_VALUE_73=Configuration entry %s does not contain \ a value for attribute %s MILD_ERR_CONFIG_JMX_ATTR_NO_ATTR_74=Configuration entry %s does not contain \ attribute %s (or that attribute exists but is not accessible using JMX) MILD_ERR_CONFIG_JMX_CANNOT_GET_CONFIG_ENTRY_75=Unable to retrieve \ configuration entry %s for access through JMX: %s MILD_ERR_CONFIG_JMX_ATTR_INVALID_VALUE_76=Attempted update to attribute %s of \ configuration entry %s over JMX would have resulted in an invalid value: %s MILD_ERR_CONFIG_JMX_UNACCEPTABLE_CONFIG_77=Update to configuration entry %s \ over JMX would have resulted in an invalid configuration: %s MILD_ERR_CONFIG_JMX_NO_METHOD_78=There is no method %s for any invokable \ component registered with configuration entry %s MILD_ERR_CONFIG_CANNOT_GET_CONFIG_ENTRY_79=An error occurred while attempting \ to retrieve configuration entry %s: %s INFO_CONFIG_SET_ATTRIBUTE_80=The value of configuration attribute %s has been \ set to %s in configuration entry %s MILD_ERR_CONFIG_CHANGE_NOT_SUCCESSFUL_81=The attempt to update configuration \ entry %s was not successful and one or more problems were encountered: %s SEVERE_ERR_CONFIG_LOGGER_NO_FILE_NAME_82=Configuration entry %s does not \ contain a valid value for configuration attribute ds-cfg-log-file which \ specifies the log file name for the associated logger SEVERE_ERR_CONFIG_JMX_CANNOT_REGISTER_MBEAN_83=The Directory Server could not \ register a JMX MBean for the component associated with configuration entry \ %s: %s SEVERE_ERR_CONFIG_LDIF_WRITE_ERROR_84=An unexpected error occurred while \ trying to export the Directory Server configuration to LDIF: %s INFO_CONFIG_WORK_QUEUE_DESCRIPTION_NUM_THREADS_85=Number of \ worker threads that should be used to process requests, which controls the \ number of operations that the server may process concurrently. The optimal \ value depends on the type of system on which the server is running and the \ workload it needs to handle, and may best be determined by performance \ testing. Changes to this attribute will take effect immediately INFO_CONFIG_WORK_QUEUE_DESCRIPTION_MAX_CAPACITY_86=Maximum \ number of pending requests that may be held in the work queue at any one time \ while all worker threads are busy processing other operations. If this limit \ is reached, then any new requests will be rejected. A value of 0 indicates \ that there is no limit. Changes to this attribute will take effect \ immediately SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_DETERMINE_NUM_WORKER_THREADS_87=An error \ occurred while attempting to retrieve the value of the \ ds-cfg-num-worker-threads attribute from the %s entry, which is used to \ specify the number of worker threads to service the work queue: %s. The \ Directory Server will use the default value of 24 SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_DETERMINE_QUEUE_CAPACITY_88=An error \ occurred while attempting to retrieve the value of the \ ds-cfg-max-work-queue-capacity attribute from the %s entry, which is used to \ specify the maximum number of pending operations that may be held in the work \ queue: %s. The Directory Server will use the default value of 0 SEVERE_WARN_CONFIG_WORK_QUEUE_NUM_THREADS_INVALID_VALUE_89=The value of \ configuration attribute ds-cfg-num-worker-threads in configuration entry %s \ has an invalid value (%d). This attribute requires an integer value greater \ than zero SEVERE_WARN_CONFIG_WORK_QUEUE_CAPACITY_INVALID_VALUE_90=The value of \ configuration attribute ds-cfg-max-work-queue-capacity in configuration entry \ %s has an invalid value (%d). This attribute requires an integer value \ greater than or equal to zero INFO_CONFIG_WORK_QUEUE_CREATED_THREADS_91=%d additional worker threads have \ been created to bring the total number of available threads to %d INFO_CONFIG_WORK_QUEUE_DESTROYING_THREADS_92=%d worker threads will terminate \ as soon as it is convenient to do so (it may take a couple of seconds for the \ threads to actually exit) to bring the total number of available threads to \ %d INFO_CONFIG_WORK_QUEUE_NEW_CAPACITY_93=The work queue capacity has been \ updated to use a new value of %d SEVERE_ERR_CONFIG_WORK_QUEUE_TOO_MANY_FAILURES_94=Worker thread "%s" has \ experienced too many repeated failures while attempting to retrieve the next \ operation from the work queue (%d failures experienced, maximum of %d \ @@ -319,10 +214,6 @@ while trying to create and start an instance of class %s to use as a monitor \ provider for the Directory Server work queue: %s. No monitor information \ will be available for the work queue INFO_CONFIG_DESCRIPTION_BACKEND_DIRECTORY_96=The name of the directory in \ which backend database files are stored SEVERE_ERR_CONFIG_BACKEND_NO_DIRECTORY_97=Configuration entry %s does not \ contain a valid value for configuration attribute ds-cfg-db-directory MILD_ERR_CONFIG_ATTR_DN_NULL_98=A null value was provided for DN \ configuration attribute %s MILD_ERR_CONFIG_ATTR_DN_CANNOT_PARSE_99=An error occurred while trying to \ @@ -344,38 +235,19 @@ SEVERE_ERR_CONFIG_BACKEND_BASE_DOES_NOT_EXIST_105=The entry \ cn=Backends,cn=config does not appear to exist in the Directory Server \ configuration. This is a required entry SEVERE_WARN_CONFIG_BACKEND_ENTRY_DOES_NOT_HAVE_BACKEND_CONFIG_106=Configuration \ entry %s exists below the backend configuration root of cn=Backends,cn=config \ but does not have objectclass ds-cfg-backend that is required for a Directory \ Server backend. This configuration entry will be ignored SEVERE_ERR_CONFIG_BACKEND_ERROR_INTERACTING_WITH_BACKEND_ENTRY_107=An \ unexpected error occurred while interacting with backend configuration entry \ %s: %s INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_ENABLED_108=Indicates whether this \ backend should be enabled for use in the Directory Server. This may be \ altered while the Directory Server is online, but if a backend is disabled, \ then it will not be available for use INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_CLASS_109=Fully-qualified \ name of the Java class that should provide the core logic for this backend \ implementation. Changes to this configuration attribute will not take effect \ until the backend is disabled and re-enabled or the server is restarted SEVERE_WARN_CONFIG_BACKEND_NO_ENABLED_ATTR_110=Backend configuration entry %s \ does not contain attribute ds-cfg-enabled, which is used to indicate \ whether the backend should be enabled or disabled. Without this attribute, \ it will default to being disabled INFO_CONFIG_BACKEND_DISABLED_111=The backend defined in configuration entry \ %s is marked as disabled and therefore will not be used SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_ENABLED_STATE_112=An unexpected \ error occurred while attempting to determine whether the backend associated \ with configuration entry %s should be enabled or disabled: %s. It will be \ disabled SEVERE_ERR_CONFIG_BACKEND_NO_CLASS_ATTR_113=Backend configuration entry %s \ does not contain attribute ds-cfg-java-class, which is used to specify the \ name of the class used to provide the backend implementation. The backend \ associated with this configuration entry will be disabled SEVERE_ERR_CONFIG_BACKEND_CANNOT_GET_CLASS_114=An unexpected error occurred \ while trying to determine the name of the Java class that contains the \ implementation for backend %s: %s. This backend will be disabled SEVERE_ERR_CONFIG_BACKEND_CANNOT_INSTANTIATE_115=The Directory Server was \ unable to load class %s and use it to create a backend instance as defined in \ configuration entry %s. The error that occurred was: %s. This backend will \ @@ -394,194 +266,13 @@ NOTICE_CONFIG_BACKEND_CANNOT_REMOVE_BACKEND_WITH_SUBORDINATES_119=The backend \ defined in configuration entry %s has one or more subordinate backends. A \ backend may not be removed if it has subordinate backends INFO_CONFIG_CORE_DESCRIPTION_MAX_ALLOWED_CONNECTIONS_120=The maximum number \ of client connections that may be established to the Directory Server at any \ given time. a value that is less than or equal to zero indicates that there \ should be no limit. Changes to this configuration attribute will take effect \ immediately INFO_CONFIG_LOGGER_CLASS_ACTION_REQUIRED_122=The requested change in the \ logger class name from %s to %s in configuration entry %s cannot be \ dynamically applied. This change will not take effect until the logger is \ disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_LOGGER_EXISTS_123=Unable to add a new logger entry with DN %s \ because there is already a logger registered with that DN MILD_ERR_CONFIG_LOGGER_ACCESS_INITIALIZATION_FAILED_124=An error occurred \ while trying to initialize an instance of class %s as an access logger as \ defined in configuration entry %s: %s MILD_ERR_CONFIG_LOGGER_ERROR_INITIALIZATION_FAILED_125=An error occurred \ while trying to initialize an instance of class %s as an error logger as \ defined in configuration entry %s: %s MILD_ERR_CONFIG_LOGGER_DEBUG_INITIALIZATION_FAILED_126=An error occurred \ while trying to initialize an instance of class %s as a debug logger as \ defined in configuration entry %s: %s FATAL_ERR_CONFIG_MONITOR_CANNOT_GET_BASE_127=An error occurred while \ attempting to retrieve the base monitor entry cn=Monitor Providers,cn=config \ from the Directory Server configuration: %s SEVERE_WARN_CONFIG_MONITOR_BASE_DOES_NOT_EXIST_128=The monitor configuration \ base cn=Monitor Providers,cn=config does not exist in the Directory Server \ configuration. Only limited monitoring information will be available SEVERE_ERR_CONFIG_MONITOR_ENTRY_UNACCEPTABLE_129=Configuration entry %s does \ not contain a valid monitor provider configuration: %s. It will be ignored SEVERE_ERR_CONFIG_MONITOR_CANNOT_CREATE_MONITOR_130=An error occurred while \ attempting to create a Directory Server monitor provider from the information \ in configuration entry %s: %s SEVERE_ERR_CONFIG_MONITOR_INVALID_OBJECTCLASS_131=Configuration entry %s does \ not contain the ds-cfg-monitor-provider objectclass, which is required for \ monitor provider definitions INFO_CONFIG_MONITOR_DESCRIPTION_CLASS_NAME_132=The fully-qualified name of \ the Java class that defines the Directory Server monitor provider. If this \ is altered while the associated monitor is enabled, then that monitor must be \ disabled and re-enabled for the change to take effect SEVERE_ERR_CONFIG_MONITOR_NO_CLASS_NAME_133=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class name \ for the associated monitor provider SEVERE_ERR_CONFIG_MONITOR_INVALID_CLASS_NAME_134=Configuration entry %s has \ an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_MONITOR_INVALID_CLASS_135=Class %s specified in \ configuration entry %s does not contain a valid monitor provider \ implementation: %s INFO_CONFIG_MONITOR_DESCRIPTION_ENABLED_136=Indicates whether this Directory \ Server monitor provider should be enabled. Changes to this attribute will \ take effect immediately SEVERE_ERR_CONFIG_MONITOR_NO_ENABLED_ATTR_137=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether the monitor provider \ should be enabled for use in the Directory Server SEVERE_ERR_CONFIG_MONITOR_INVALID_ENABLED_VALUE_138=Configuration entry %s \ has an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_MONITOR_CLASS_ACTION_REQUIRED_139=The requested change in the \ monitor class name from %s to %s in configuration entry %s cannot be \ dynamically applied. This change will not take effect until the monitor \ provider is disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_MONITOR_INITIALIZATION_FAILED_140=An error occurred while \ trying to initialize an instance of class %s as a monitor provider as defined \ in configuration entry %s: %s MILD_ERR_CONFIG_MONITOR_EXISTS_141=Unable to add a new monitor provider entry \ with DN %s because there is already a monitor provider registered with that \ DN SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_GET_CONFIG_BASE_142=An error occurred \ while trying to retrieve configuration entry cn=Connection Handlers,cn=config \ in order to initialize the Directory Server backends: %s SEVERE_ERR_CONFIG_CONNHANDLER_BASE_DOES_NOT_EXIST_143=The entry cn=Connection \ Handlers,cn=config does not appear to exist in the Directory Server \ configuration. This is a required entry SEVERE_WARN_CONFIG_CONNHANDLER_ENTRY_DOES_NOT_HAVE_CONNHANDLER_CONFIG_144=Configuration \ entry %s exists below the connection handler configuration root of \ cn=Connection Handlers,cn=config but does not have objectclass \ ds-cfg-connection-handler that is required for a Directory Server connection \ handler. This configuration entry will be ignored SEVERE_ERR_CONFIG_CONNHANDLER_ERROR_INTERACTING_WITH_CONNHANDLER_ENTRY_145=An \ unexpected error occurred while interacting with connection handler \ configuration entry %s: %s INFO_CONFIG_CONNHANDLER_ATTR_DESCRIPTION_ENABLED_146=Indicates whether this \ connection handler should be enabled for use in the Directory Server. This \ may be altered while the Directory Server is online, but if a connection \ handler is disabled, then it will not be available for use INFO_CONFIG_CONNHANDLER_ATTR_DESCRIPTION_CLASS_147=Fully-qualified name of the \ Java class that should provide the core logic for \ this connection handler implementation. Changes to this configuration \ attribute will not take effect until the connection handler is disabled and \ re-enabled or the server is restarted SEVERE_WARN_CONFIG_CONNHANDLER_NO_ENABLED_ATTR_148=Connection handler \ configuration entry %s does not contain attribute \ ds-cfg-enabled, which is used to indicate whether the \ connection handler should be enabled or disabled. Without this attribute, it \ will default to being disabled INFO_CONFIG_CONNHANDLER_DISABLED_149=The connection handler defined in \ configuration entry %s is marked as disabled and therefore will not be used SEVERE_ERR_CONFIG_CONNHANDLER_UNABLE_TO_DETERMINE_ENABLED_STATE_150=An \ unexpected error occurred while attempting to determine whether the \ connection handler associated with configuration entry %s should be enabled \ or disabled: %s. It will be disabled SEVERE_ERR_CONFIG_CONNHANDLER_NO_CLASS_ATTR_151=Connection handler \ configuration entry %s does not contain attribute \ ds-cfg-java-class, which is used to specify the name of the \ class used to provide the connection handler implementation. The connection \ handler associated with this configuration entry will be disabled SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_GET_CLASS_152=An unexpected error \ occurred while trying to determine the name of the Java class that contains \ the implementation for connection handler %s: %s. This connection handler \ will be disabled SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_INSTANTIATE_153=The Directory Server was \ unable to load class %s and use it to create a connection handler instance as \ defined in configuration entry %s. The error that occurred was: %s. This \ connection handler will be disabled SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_INITIALIZE_154=An error occurred while \ trying to initialize a connection handler loaded from class %s with the \ information in configuration entry %s: %s. This connection handler will be \ disabled SEVERE_ERR_CONFIG_CONNHANDLER_UNACCEPTABLE_CONFIG_155=The configuration for \ the connection handler defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry SEVERE_ERR_CONFIG_BACKEND_UNACCEPTABLE_CONFIG_156=The configuration for the \ backend defined in configuration entry %s was not acceptable according to its \ internal validation. However, no specific information is available regarding \ the problem(s) with the entry SEVERE_ERR_CONFIG_MONITOR_UNACCEPTABLE_CONFIG_157=The configuration for the \ monitor provider defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry SEVERE_ERR_CONFIG_LOGGER_UNACCEPTABLE_CONFIG_158=The configuration for the \ logger defined in configuration entry %s was not acceptable according to its \ internal validation. However, no specific information is available regarding \ the problem(s) with the entry SEVERE_ERR_CONFIG_CONNHANDLER_CLASS_NOT_CONNHANDLER_159=The class %s \ specified in configuration entry %s does not contain a valid Directory Server \ connection handler implementation SEVERE_ERR_CONFIG_SCHEMA_CANNOT_GET_MR_BASE_160=An error occurred while \ trying to retrieve configuration entry cn=Matching Rules,cn=config in order \ to initialize the Directory Server matching rules: %s SEVERE_ERR_CONFIG_SCHEMA_MR_BASE_DOES_NOT_EXIST_161=The entry cn=Matching \ Rules,cn=config does not appear to exist in the Directory Server \ configuration. This is a required entry SEVERE_ERR_CONFIG_SCHEMA_NO_MATCHING_RULES_162=No child entries were found \ below the entry cn=Matching Rules,cn=config to define the matching rules for \ use in the Directory Server. This is an error, because the Directory Server \ must have matching rules defined to function properly SEVERE_WARN_CONFIG_SCHEMA_ENTRY_DOES_NOT_HAVE_MR_CONFIG_163=Configuration \ entry %s exists below the matching rule configuration root of cn=Matching \ Rules,cn=config but does not have objectclass ds-cfg-matching-rule that is \ required for a Directory Server matching rule. This configuration entry will \ be ignored INFO_CONFIG_SCHEMA_MR_ATTR_DESCRIPTION_ENABLED_164=Indicates whether this \ matching rule should be enabled for use in the Directory Server. This may be \ altered while the Directory Server is online, but if a matching rule is \ disabled, after it has been used for one or more attributes then matching may \ no longer function as expected for those attributes INFO_CONFIG_SCHEMA_MR_ATTR_DESCRIPTION_CLASS_165=Fully-qualified name of the \ Java class that should provide the core logic for \ this matching rule implementation. Changes to this configuration attribute \ will not take effect until the matching rule is disabled and re-enabled or \ the server is restarted. Also, changes to the matching rule class for \ matching rules that have already been used for one or more attributes may \ cause unexpected results when performing matching for those attributes SEVERE_WARN_CONFIG_SCHEMA_MR_NO_ENABLED_ATTR_166=Matching rule configuration \ entry %s does not contain attribute ds-cfg-enabled, which is \ used to indicate whether the matching rule should be enabled or disabled. \ Without this attribute, it will default to being disabled INFO_CONFIG_SCHEMA_MR_DISABLED_167=The matching rule defined in configuration \ entry %s is marked as disabled and therefore will not be used. If it has \ been used in the past for one or more attributes, then matching may no longer \ function for values of those attributes SEVERE_ERR_CONFIG_SCHEMA_MR_UNABLE_TO_DETERMINE_ENABLED_STATE_168=An \ unexpected error occurred while attempting to determine whether the matching \ rule associated with configuration entry %s should be enabled or disabled: \ %s. It will be disabled SEVERE_ERR_CONFIG_SCHEMA_MR_NO_CLASS_ATTR_169=Matching rule configuration \ entry %s does not contain attribute ds-cfg-java-class, which is used \ to specify the name of the class used to provide the matching rule \ implementation. The matching rule associated with this configuration entry \ will be disabled SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_GET_CLASS_170=An unexpected error occurred \ while trying to determine the name of the Java class that contains the \ implementation for matching rule %s: %s. This matching rule will be \ disabled SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_INSTANTIATE_171=The Directory Server was \ unable to load class %s and use it to create a matching rule instance as \ defined in configuration entry %s. The error that occurred was: %s. This \ matching rule will be disabled SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_INITIALIZE_172=An error occurred while \ trying to initialize a matching rule loaded from class %s with the \ information in configuration entry %s: %s. This matching rule will be \ @@ -589,58 +280,6 @@ SEVERE_WARN_CONFIG_SCHEMA_MR_CONFLICTING_MR_173=The matching rule defined in \ configuration entry %s conflicts with another matching rule defined in the \ server configuration: %s. This matching rule will not be used SEVERE_ERR_CONFIG_SCHEMA_CANNOT_GET_SYNTAX_BASE_174=An error occurred while \ trying to retrieve configuration entry cn=Syntaxes,cn=config in order to \ initialize the Directory Server attribute syntaxes: %s SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_BASE_DOES_NOT_EXIST_175=The entry \ cn=Syntaxes,cn=config does not appear to exist in the Directory Server \ configuration. This is a required entry SEVERE_ERR_CONFIG_SCHEMA_NO_SYNTAXES_176=No child entries were found below \ the entry cn=Syntaxes,cn=config to define the attribute syntaxes for use in \ the Directory Server. This is an error, because the Directory Server must \ have syntaxes defined to function properly SEVERE_WARN_CONFIG_SCHEMA_ENTRY_DOES_NOT_HAVE_SYNTAX_CONFIG_177=Configuration \ entry %s exists below the attribute syntax configuration root of \ cn=Syntaxes,cn=config but does not have objectclass ds-cfg-attribute-syntax \ that is required for a Directory Server attribute syntax. This configuration \ entry will be ignored INFO_CONFIG_SCHEMA_SYNTAX_ATTR_DESCRIPTION_ENABLED_178=Indicates whether this \ attribute syntax should be enabled for use in the Directory Server. This may \ be altered while the Directory Server is online, but if a syntax is disabled, \ after it has been used for one or more attributes then matching may no longer \ function as expected for those attributes INFO_CONFIG_SCHEMA_SYNTAX_ATTR_DESCRIPTION_CLASS_179=Fully-qualified name of the \ Java class that should provide the core logic for \ this attribute syntax implementation. Changes to this configuration \ attribute will not take effect until the syntax is disabled and re-enabled or \ the server is restarted. Also, changes to the syntax class for attribute \ syntaxes that have already been used for one or more attributes may cause \ unexpected results when performing matching for those attributes SEVERE_WARN_CONFIG_SCHEMA_SYNTAX_NO_ENABLED_ATTR_180=Attribute syntax \ configuration entry %s does not contain attribute ds-cfg-enabled, \ which is used to indicate whether the syntax should be enabled or disabled. \ Without this attribute, it will default to being disabled INFO_CONFIG_SCHEMA_SYNTAX_DISABLED_181=The attribute syntax defined in \ configuration entry %s is marked as disabled and therefore will not be used. \ If it has been used in the past for one or more attributes, then matching may \ no longer function for values of those attributes SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_UNABLE_TO_DETERMINE_ENABLED_STATE_182=An \ unexpected error occurred while attempting to determine whether the attribute \ syntax associated with configuration entry %s should be enabled or disabled: \ %s. It will be disabled SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_NO_CLASS_ATTR_183=Matching rule configuration \ entry %s does not contain attribute ds-cfg-java-class, which is used to \ specify the name of the class that provides the attribute syntax \ implementation. The syntax associated with this configuration entry will be \ disabled SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_GET_CLASS_184=An unexpected error \ occurred while trying to determine the name of the Java class that contains \ the implementation for attribute syntax %s: %s. This syntax will be \ disabled SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_INSTANTIATE_185=The Directory Server \ was unable to load class %s and use it to create an attribute syntax instance \ as defined in configuration entry %s. The error that occurred was: %s. \ This syntax will be disabled SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_INITIALIZE_186=An error occurred while \ trying to initialize an attribute syntax loaded from class %s with the \ information in configuration entry %s: %s. This syntax will be disabled @@ -672,20 +311,6 @@ the schema: %s. The later objectclass definition will be used SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_OC_196=An objectclass read from schema \ configuration file %s could not be parsed: %s SEVERE_ERR_CONFIG_CORE_INVALID_STRUCTURAL_CLASS_BEHAVIOR_197=Configuration \ entry %s has an invalid value for configuration attribute \ ds-cfg-single-structural-objectclass-behavior (it should be one of "accept", \ "reject", or "warn" ): %s INFO_CONFIG_CORE_DESCRIPTION_CHECK_SCHEMA_198=Indicates whether the Directory \ Server should perform schema checking for update operations to ensure that \ entries are valid according to the server's schema configuration (e.g., all \ required attributes are included and no prohibited attributes are present). \ Disabling schema checking is generally not recommended because it may allow \ invalid entries to be included in the server. Changes to this configuration \ attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_CHECK_SCHEMA_199=Configuration entry %s has an \ invalid value for configuration attribute ds-cfg-check-schema (it should be a \ Boolean value of true or false): %s SEVERE_ERR_CONFIG_ENTRYCACHE_CANNOT_INSTALL_DEFAULT_CACHE_200=An unexpected \ error occurred that prevented the server from installing its default entry \ cache framework: %s @@ -733,143 +358,21 @@ schema configuration file %s conflicts with another matching rule use already \ read into the schema: %s. The later matching rule use definition will be \ used SEVERE_WARN_CONFIG_LOGGER_NO_ROTATION_POLICY_224=No file rotation policy has \ been defined in configuration entry %s. No log rotation will take place SEVERE_ERR_CONFIG_LOGGER_NO_SIZE_LIMIT_225=No size limit has been defined for \ the size based file rotation policy in the configuration entry %s SEVERE_ERR_CONFIG_LOGGER_NO_TIME_LIMIT_226=No time limit has been defined for \ the time based file rotation policy in the configuration entry %s SEVERE_ERR_CONFIG_LOGGER_INVALID_ROTATION_POLICY_227=An invalid file rotation \ policy %s has been defined in configuration entry %s MILD_ERR_CONFIG_ATTR_READ_ONLY_228=Configuration attribute %s is read-only \ and its values may not be altered SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_CONFIG_BASE_229=An error occurred while \ trying to retrieve configuration entry cn=Plugins,cn=config in order to \ initialize the Directory Server plugins: %s SEVERE_ERR_CONFIG_PLUGIN_BASE_DOES_NOT_EXIST_230=The entry \ cn=Plugins,cn=config does not appear to exist in the Directory Server \ configuration. This is a required entry SEVERE_WARN_CONFIG_PLUGIN_ENTRY_DOES_NOT_HAVE_PLUGIN_CONFIG_231=Configuration \ entry %s exists below the plugin configuration root of cn=Plugins,cn=config \ but does not have objectclass ds-cfg-backend that is required for a Directory \ Server plugin. This configuration entry will be ignored SEVERE_ERR_CONFIG_PLUGIN_ERROR_INTERACTING_WITH_PLUGIN_ENTRY_232=An \ unexpected error occurred while interacting with backend configuration entry \ %s: %s INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_ENABLED_233=Indicates whether this plugin \ should be enabled for use in the Directory Server. This may be altered while \ the Directory Server is online, and will take effect immediately SEVERE_WARN_CONFIG_PLUGIN_NO_ENABLED_ATTR_234=Plugin configuration entry %s \ does not contain attribute ds-cfg-enabled, which is used to indicate \ whether the plugin should be enabled or disabled. Without this attribute, it \ will default to being disabled INFO_CONFIG_PLUGIN_DISABLED_235=The plugin defined in configuration entry %s \ is marked as disabled and therefore will not be used SEVERE_ERR_CONFIG_PLUGIN_UNABLE_TO_DETERMINE_ENABLED_STATE_236=An unexpected \ error occurred while attempting to determine whether the plugin associated \ with configuration entry %s should be enabled or disabled: %s. It will be \ disabled INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_PLUGIN_TYPE_237=Plugin \ type(s) for this plugin, which control the times when this plugin will be \ invoked during processing. This value is only read when the plugin is loaded \ and initialized, so changes to this attribute will not take effect until the \ plugin is disabled and re-enabled, or until the server is restarted INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_CLASS_238=Fully-qualified \ name of the Java class that should provide the core logic for this plugin \ implementation. Changes to this configuration attribute will not take effect \ until the plugin is disabled and re-enabled or the server is restarted SEVERE_ERR_CONFIG_PLUGIN_NO_PLUGIN_TYPES_239=Plugin configuration entry %s \ does not contain attribute ds-cfg-plugin-type, which is used to specify the \ name(s) of the plugin type(s) for the plugin. This is a required attribute, \ so this plugin will be disabled SEVERE_ERR_CONFIG_PLUGIN_INVALID_PLUGIN_TYPE_240=Plugin configuration entry \ %s has an invalid value %s for attribute ds-cfg-plugin-type that does not \ name a valid plugin type. This plugin will be disabled SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_PLUGIN_TYPES_241=An unexpected error \ occurred while trying to determine the set of plugin types for the plugin \ defined in configuration entry %s: %s. This plugin will be disabled SEVERE_ERR_CONFIG_PLUGIN_NO_CLASS_ATTR_242=Plugin configuration entry %s does \ not contain attribute ds-cfg-java-class, which is used to specify the name \ of the class used to provide the plugin implementation. The plugin \ associated with this configuration entry will be disabled SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_CLASS_243=An unexpected error occurred \ while trying to determine the name of the Java class that contains the \ implementation for plugin %s: %s. This plugin will be disabled SEVERE_ERR_CONFIG_PLUGIN_CANNOT_INSTANTIATE_244=The Directory Server was \ unable to load class %s and use it to create a plugin instance as defined in \ configuration entry %s. The error that occurred was: %s. This plugin will \ be disabled SEVERE_ERR_CONFIG_PLUGIN_CANNOT_INITIALIZE_245=An error occurred while \ attempting to initialize an instance of class %s as a Directory Server plugin \ using the information in configuration entry %s: %s. This plugin will be \ disabled INFO_CONFIG_CORE_DESCRIPTION_NOTIFY_ABANDONED_OPERATIONS_246=Indicates \ whether the Directory Server should send a response to operations that have \ been abandoned to the client to know that the server has completed processing \ on them. The LDAP specification prohibits sending a response in such cases, \ but some clients may not behave properly if they are waiting on a response \ for an operation when there will not be one because it has been abandoned. \ Changes to this configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_NOTIFY_ABANDONED_OPERATIONS_247=Configuration \ entry %s has an invalid value for configuration attribute \ ds-cfg-notify-abandoned-operations (it should be a Boolean value of true or \ false): %s SEVERE_ERR_CONFIG_EXTOP_INVALID_CLASS_256=Class %s specified in configuration \ entry %s does not contain a valid extended operation handler implementation: \ %s MILD_ERR_CONFIG_EXTOP_INITIALIZATION_FAILED_261=An error occurred while \ trying to initialize an instance of class %s as an extended operation handler \ as defined in configuration entry %s: %s FATAL_ERR_CONFIG_SASL_CANNOT_GET_BASE_264=An error occurred while attempting \ to retrieve the SASL mechanism handler base entry cn=SASL \ Mechanisms,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_SASL_BASE_DOES_NOT_EXIST_265=The SASL mechanism \ configuration base cn=SASL Mechanisms,cn=config does not exist in the \ Directory Server configuration. This entry must be present for the server to \ function properly SEVERE_ERR_CONFIG_SASL_ENTRY_UNACCEPTABLE_266=Configuration entry %s does not \ contain a valid SASL mechanism handler configuration: %s. It will be \ ignored SEVERE_ERR_CONFIG_SASL_CANNOT_CREATE_HANDLER_267=An error occurred while \ attempting to create a Directory Server SASL mechanism handler from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_SASL_INVALID_OBJECTCLASS_268=Configuration entry %s does \ not contain the ds-cfg-sasl-mechanism-handler objectclass, which is required \ for SASL mechanism handler definitions INFO_CONFIG_SASL_DESCRIPTION_CLASS_NAME_269=The fully-qualified name of the \ Java class that defines the Directory Server SASL mechanism handler. If this \ is altered while the associated handler is enabled, then that handler must be \ disabled and re-enabled for the change to take effect SEVERE_ERR_CONFIG_SASL_NO_CLASS_NAME_270=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class \ name for the associated SASL mechanism handler SEVERE_ERR_CONFIG_SASL_INVALID_CLASS_NAME_271=Configuration entry %s has an \ invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_SASL_INVALID_CLASS_272=Class %s specified in configuration \ entry %s does not contain a valid SASL mechanism handler implementation: %s INFO_CONFIG_SASL_DESCRIPTION_ENABLED_273=Indicates whether this Directory \ Server SASL mechanism handler should be enabled. Changes to this attribute \ will take effect immediately SEVERE_ERR_CONFIG_SASL_NO_ENABLED_ATTR_274=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether the SASL \ mechanism handler should be enabled for use in the Directory Server SEVERE_ERR_CONFIG_SASL_INVALID_ENABLED_VALUE_275=Configuration entry %s has \ an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_SASL_CLASS_ACTION_REQUIRED_276=The requested change in the SASL \ mechanism handler class name from %s to %s in configuration entry %s cannot \ be dynamically applied. This change will not take effect until the handler \ is disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_SASL_INITIALIZATION_FAILED_277=An error occurred while trying \ to initialize an instance of class %s as a SASL mechanism handler as defined \ in configuration entry %s: %s MILD_ERR_CONFIG_SASL_EXISTS_278=Unable to add a new SASL mechanism handler \ entry with DN %s because there is already a handler registered with that DN SEVERE_ERR_CONFIG_SASL_UNACCEPTABLE_CONFIG_279=The configuration for the SASL \ mechanism handler defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry MILD_ERR_CONFIG_FILE_ADD_ALREADY_EXISTS_280=Entry %s cannot be added to the \ Directory Server configuration because another configuration entry already \ exists with that DN @@ -901,29 +404,10 @@ MILD_ERR_CONFIG_FILE_MODIFY_REJECTED_BY_CHANGE_LISTENER_291=Entry %s cannot \ be modified because one of the configuration change listeners registered for \ that entry rejected the change: %s MILD_ERR_CONFIG_FILE_MODIFY_REJECTED_BY_COMPONENT_292=Entry %s cannot be \ modified because one of the configurable components registered for that entry \ rejected the change: %s MILD_ERR_CONFIG_FILE_SEARCH_NO_SUCH_BASE_293=The search operation cannot be \ processed because base entry %s does not exist MILD_ERR_CONFIG_FILE_SEARCH_INVALID_SCOPE_294=The search operation cannot be \ processed because the specified search scope %s is invalid MILD_ERR_CONFIG_FILE_WRITE_CANNOT_CREATE_TEMP_ARCHIVE_295=An error occurred \ while attempting to create a temporary file %s to hold the archived versions \ of previous Directory Server configurations as a result of a configuration \ change: %s MILD_ERR_CONFIG_FILE_WRITE_CANNOT_COPY_EXISTING_ARCHIVE_296=An error occurred \ while attempting to copy the archived configurations from %s to temporary \ file %s: %s MILD_ERR_CONFIG_FILE_WRITE_CANNOT_COPY_CURRENT_CONFIG_297=An error occurred \ while attempting to update the archived configurations in file %s to include \ the running configuration from file %s: %s MILD_ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_TEMP_ARCHIVE_298=The attempt to \ rename the archived configuration data from %s to %s failed, but the \ underlying reason for the failure could not be determined MILD_ERR_CONFIG_FILE_WRITE_CANNOT_REPLACE_ARCHIVE_299=The updated archive \ containing previous Directory Server configurations could not be renamed from \ %s to %s: %s MILD_ERR_CONFIG_FILE_WRITE_CANNOT_EXPORT_NEW_CONFIG_300=An error occurred \ while attempting to export the new Directory Server configuration to file %s: \ %s @@ -932,151 +416,35 @@ %s to %s: %s MILD_ERR_CONFIG_FILE_MODDN_NOT_ALLOWED_302=Modify DN operations are not \ allowed in the Directory Server configuration INFO_CONFIG_LOGGER_SUPPRESS_INTERNAL_OPERATIONS_303=Indicates whether \ messages for internal operations should be excluded from the access log file SEVERE_ERR_CONFIG_LOGGER_INVALID_SUPPRESS_INT_OPERATION_VALUE_304=Invalid \ value specified for attribute %s. Allowed values are true or false INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_BASE_DNS_305=Set of base \ DNs that should be used for this backend. It is up to the backend \ implementation as to whether changes to this attribute will automatically \ take effect SEVERE_ERR_CONFIG_BACKEND_NO_BASE_DNS_306=Backend configuration entry %s does \ not contain attribute ds-cfg-base-dn, which is used to specify the \ set of base DNs for the backend. This is a required attribute, and therefore \ the backend will be disabled SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_BASE_DNS_307=An unexpected \ error occurred while attempting to determine the set of base DNs associated \ with the backend defined in configuration entry %s: %s. This backend will \ be disabled INFO_CONFIG_KEYMANAGER_DESCRIPTION_ENABLED_313=Indicates whether the \ Directory Server key manager provider should be enabled. A key manager \ provider is required for operations that require access to a key manager \ (e.g., communication over SSL). Changes to this configuration attribute will \ take effect immediately, but will only impact future attempts to access the \ key manager SEVERE_ERR_CONFIG_KEYMANAGER_NO_ENABLED_ATTR_314=Configuration entry "%s" \ does not contain a value for attribute ds-cfg-enabled, \ which indicates whether the key manager provider is enabled for use in the \ server SEVERE_ERR_CONFIG_KEYMANAGER_DESCRIPTION_CLASS_317=Fully-qualified name of the \ Java class that includes the key manager provider \ implementation. Changes to this configuration attribute will not take effect \ until the key manager provider has been disabled and then re-enabled, or \ until the server is restarted SEVERE_ERR_CONFIG_TRUSTMANAGER_DESCRIPTION_ENABLED_328=Indicates whether the \ Directory Server trust manager provider should be enabled. A trust manager \ provider is required for operations that require access to a trust manager \ (e.g., communication over SSL). Changes to this configuration attribute will \ take effect immediately, but will only impact future attempts to access the \ trust manager SEVERE_ERR_CONFIG_TRUSTMANAGER_NO_ENABLED_ATTR_329=Configuration entry "%s" \ does not contain a value for attribute ds-cfg-enabled, \ which indicates whether the trust manager provider is enabled for use in the \ server SEVERE_ERR_CONFIG_TRUSTMANAGER_DESCRIPTION_CLASS_332=Fully-qualified name of the \ Java class that includes the trust manager \ provider implementation. Changes to this configuration attribute will not \ take effect until the trust manager provider has been disabled and then \ re-enabled, or until the server is restarted SEVERE_ERR_CONFIG_CERTMAPPER_DESCRIPTION_ENABLED_347=Indicates whether the \ Directory Server certificate mapper should be enabled. A certificate mapper \ is used to establish a mapping between a client certificate chain and a user \ entry in the Directory Server for SASL EXTERNAL authentication and similar \ purposes. Changes to this configuration attribute will take effect \ immediately SEVERE_ERR_CONFIG_CERTMAPPER_NO_ENABLED_ATTR_348=Configuration entry "%s" \ does not contain a value for attribute ds-cfg-enabled, \ which indicates whether the certificate mapper is enabled for use in the \ server SEVERE_ERR_CONFIG_CERTMAPPER_DESCRIPTION_CLASS_351=Fully-qualified name of the \ Java class that includes the certificate mapper \ implementation. Changes to this configuration attribute will not take effect \ until the certificate mapper has been disabled and then re-enabled, or until \ the server is restarted MILD_WARN_CONFIG_LOGGER_NO_RETENTION_POLICY_357=No file retention policy has \ been defined in configuration entry %s. No log files will be deleted SEVERE_WARN_CONFIG_LOGGER_INVALID_RETENTION_POLICY_358=An invalid file \ retention policy %s has been defined in configuration entry %s SEVERE_WARN_CONFIG_LOGGER_NO_NUMBER_OF_FILES_359=No file number limit has \ been defined for the retention policy in the configuration entry %s SEVERE_WARN_CONFIG_LOGGER_NO_DISK_SPACE_USED_360=No disk space limit has been \ defined for the retention policy in the configuration entry %s FATAL_ERR_CONFIG_PWSCHEME_CANNOT_GET_BASE_363=An error occurred while \ attempting to retrieve the password storage scheme base entry cn=Password \ Storage Schemes,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_PWSCHEME_BASE_DOES_NOT_EXIST_364=The password storage \ scheme configuration base cn=Password Storage Schemes,cn=config does not \ exist in the Directory Server configuration. This entry must be present for \ the server to function properly SEVERE_ERR_CONFIG_PWSCHEME_ENTRY_UNACCEPTABLE_365=Configuration entry %s does \ not contain a valid password storage scheme configuration: %s. It will be \ ignored SEVERE_ERR_CONFIG_PWSCHEME_CANNOT_CREATE_SCHEME_366=An error occurred while \ attempting to create a Directory Server password storage scheme from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_PWSCHEME_INVALID_OBJECTCLASS_367=Configuration entry %s \ does not contain the ds-cfg-password-storage-scheme objectclass, which is \ required for password storage scheme definitions INFO_CONFIG_PWSCHEME_DESCRIPTION_CLASS_NAME_368=The fully-qualified name of \ the Java class that defines the Directory Server password storage scheme. If \ this is altered while the associated scheme is enabled, then that storage \ scheme must be disabled and re-enabled for the change to take effect SEVERE_ERR_CONFIG_PWSCHEME_NO_CLASS_NAME_369=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified \ class name for the associated password storage scheme SEVERE_ERR_CONFIG_PWSCHEME_INVALID_CLASS_NAME_370=Configuration entry %s has \ an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_PWSCHEME_INVALID_CLASS_371=Class %s specified in \ configuration entry %s does not contain a valid password storage scheme \ implementation: %s INFO_CONFIG_PWSCHEME_DESCRIPTION_ENABLED_372=Indicates whether this Directory \ Server password storage scheme should be enabled. Changes to this attribute \ will take effect immediately SEVERE_ERR_CONFIG_PWSCHEME_NO_ENABLED_ATTR_373=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether the password \ storage scheme should be enabled for use in the Directory Server SEVERE_ERR_CONFIG_PWSCHEME_INVALID_ENABLED_VALUE_374=Configuration entry %s \ has an invalid value for attribute ds-cfg-enabled: \ %s INFO_CONFIG_PWSCHEME_CLASS_ACTION_REQUIRED_375=The requested change in the \ password storage scheme class name from %s to %s in configuration entry %s \ cannot be dynamically applied. This change will not take effect until the \ storage scheme is disabled and re-enabled or the Directory Server is \ restarted MILD_ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILED_376=An error occurred while \ trying to initialize an instance of class %s as a password storage scheme as \ defined in configuration entry %s: %s MILD_ERR_CONFIG_PWSCHEME_EXISTS_377=Unable to add a new password storage \ scheme entry with DN %s because there is already a storage scheme registered \ with that DN SEVERE_ERR_CONFIG_PWSCHEME_UNACCEPTABLE_CONFIG_378=The configuration for the \ password storage scheme defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry INFO_CONFIG_PLUGIN_CLASS_ACTION_REQUIRED_379=The requested change in the \ plugin class name from %s to %s in configuration entry %s cannot be \ dynamically applied. This change will not take effect until the plugin is \ disabled and re-enabled or the Directory Server is restarted SEVERE_ERR_CONFIG_LOGGER_NO_FREE_DISK_SPACE_380=No disk space limit has been \ defined for the retention policy in the configuration entry %s SEVERE_ERR_CONFIG_LOGGER_INVALID_JAVA5_POLICY_381=The free disk space based \ retention policy in the configuration entry %s. is not allowed for the \ Directory Server when running on pre Java 6 VMs INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_BACKEND_ID_382=Unique \ identifier for this backend. Changes to this configuration attribute will \ not take effect until the backend is disabled and re-enabled or the server is \ restarted SEVERE_WARN_CONFIG_BACKEND_NO_BACKEND_ID_383=Backend configuration entry %s \ does not contain attribute ds-cfg-backend-id, which is used to provide a \ unique identifier for the backend. The backend will be disabled SEVERE_WARN_CONFIG_BACKEND_DUPLICATE_BACKEND_ID_384=The backend defined in \ configuration entry %s has a backend ID of %s that conflicts with the backend \ ID for another backend in the server. The backend will be disabled SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_BACKEND_ID_385=An unexpected \ error occurred while attempting to determine the backend ID for the backend \ defined in configuration entry %s: %s. The backend will be disabled SEVERE_ERR_CONFIG_BACKUP_CANNOT_GET_MAC_386=An error occurred while \ attempting to obtain the %s MAC provider to create the signed hash for the \ backup: %s @@ -1189,87 +557,9 @@ configuration. It must not be directly edited while the server is online. \ The server configuration should only be managed using the administration \ utilities provided with the Directory Server INFO_CONFIG_CORE_DESCRIPTION_ADD_MISSING_RDN_ATTRS_425=Indicates whether the \ Directory Server should automatically add missing RDN attributes to an entry \ when it is added. By default, entries added that do not contain the RDN \ attribute values in their attribute lists will be rejected because they are \ in violation of the LDAP specification. Changes to this configuration \ attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_ADD_MISSING_RDN_ATTRS_426=Configuration entry \ %s has an invalid value for configuration attribute \ ds-cfg-add-missing-rdn-attributes (it should be a Boolean value of true or \ false): %s INFO_CONFIG_CORE_DESCRIPTION_SERVER_ERROR_RESULT_CODE_427=Result code that \ should be used for responses in which the operation fails \ because of an internal server error. The value should be the integer \ equivalent of the corresponding LDAP result code. Changes to this \ configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_SERVER_ERROR_RESULT_CODE_428=Configuration \ entry %s has an invalid value for configuration attribute \ ds-cfg-server-error-result-code (it should be an integer value greater than \ or equal to 1): %s FATAL_ERR_CONFIG_IDMAPPER_CANNOT_GET_BASE_429=An error occurred while \ attempting to retrieve the identity mapper base entry cn=Identity \ Mappers,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_IDMAPPER_BASE_DOES_NOT_EXIST_430=The identity mapper \ configuration base cn=Identity Mappers,cn=config does not exist in the \ Directory Server configuration. This entry must be present for the server to \ function properly SEVERE_ERR_CONFIG_IDMAPPER_ENTRY_UNACCEPTABLE_431=Configuration entry %s does \ not contain a valid identity mapper configuration: %s. It will be ignored SEVERE_ERR_CONFIG_IDMAPPER_CANNOT_CREATE_MAPPER_432=An error occurred while \ attempting to create a Directory Server identity mapper from the information \ in configuration entry %s: %s SEVERE_ERR_CONFIG_IDMAPPER_INVALID_OBJECTCLASS_433=Configuration entry %s \ does not contain the ds-cfg-identity-mapper objectclass, which is required \ for identity mapper definitions INFO_CONFIG_IDMAPPER_DESCRIPTION_CLASS_NAME_434=The fully-qualified name of \ the Java class that defines a Directory Server identity mapper. If this is \ altered while the associated identity mapper is enabled, then that mapper \ must be disabled and re-enabled for the change to take effect SEVERE_ERR_CONFIG_IDMAPPER_NO_CLASS_NAME_435=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class name \ for the associated identity mapper SEVERE_ERR_CONFIG_IDMAPPER_INVALID_CLASS_NAME_436=Configuration entry %s has \ an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_IDMAPPER_INVALID_CLASS_437=Class %s specified in \ configuration entry %s does not contain a valid identity mapper \ implementation: %s INFO_CONFIG_IDMAPPER_DESCRIPTION_ENABLED_438=Indicates whether this Directory \ Server identity mapper should be enabled. Changes to this attribute will \ take effect immediately SEVERE_ERR_CONFIG_IDMAPPER_NO_ENABLED_ATTR_439=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether the identity mapper \ should be enabled for use in the Directory Server SEVERE_ERR_CONFIG_IDMAPPER_INVALID_ENABLED_VALUE_440=Configuration entry %s \ has an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_IDMAPPER_CLASS_ACTION_REQUIRED_441=The requested change in the \ identity mapper class name from %s to %s in configuration entry %s cannot be \ dynamically applied. This change will not take effect until the identity \ mapper is disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILED_442=An error occurred while \ trying to initialize an instance of class %s as an identity mapper as defined \ in configuration entry %s: %s MILD_ERR_CONFIG_IDMAPPER_EXISTS_443=Unable to add a new identity mapper entry \ with DN %s because there is already an identity mapper registered with that \ DN SEVERE_ERR_CONFIG_IDMAPPER_UNACCEPTABLE_CONFIG_444=The configuration for the \ identity mapper defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry INFO_CONFIG_CORE_DESCRIPTION_PROXY_MAPPER_DN_445=DN of the \ configuration entry for the identity mapper that the Directory Server should \ use in conjunction with the proxied authorization V2 control. Changes to \ this configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_PROXY_MAPPER_DN_446=Configuration entry %s has \ an invalid value for configuration attribute \ ds-cfg-proxied-authorization-identity-mapper (it should be the DN of a \ valid identity mapper configuration entry): %s SEVERE_ERR_CONFIG_CORE_NO_PROXY_MAPPER_FOR_DN_447=The proxied authorization \ identity mapper DN %s specified in configuration entry %s does not refer to a \ valid identity mapper configuration entry SEVERE_ERR_CONFIG_IDMAPPER_NO_PROXY_MAPPER_DN_448=The Directory Server does \ not have any identity mapper configured for use in conjunction with proxied \ authorization V2 operations. The Directory Server will not be able to \ @@ -1279,56 +569,6 @@ authorization identity mapper DN %s does not refer to an active identity \ mapper. The Directory Server will not be able to process requests containing \ the proxied authorization control with a username-based authorization ID INFO_CONFIG_CORE_DESCRIPTION_SIZE_LIMIT_450=Default maximum \ number of entries that should be returned to a client when processing a \ search operation. This may be overridden on a per-user basis by including \ the ds-rlim-size-limit operational attribute in the user's entry. Changes to \ this configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_SIZE_LIMIT_451=Configuration entry %s has an \ invalid value for configuration attribute ds-cfg-size-limit (It should be a \ positive integer value specifying the size limit to use, or a value of 0 or \ -1 to indicate that no limit should be enforced): %s FATAL_ERR_CONFIG_SYNCH_CANNOT_GET_CONFIG_BASE_452=An error occurred while \ attempting to retrieve the Directory Server synchronization provider \ configuration base entry cn=Synchronization Providers,cn=config: %s FATAL_ERR_CONFIG_SYNCH_BASE_DOES_NOT_EXIST_453=The Directory Server \ synchronization provider base entry cn=Synchronization Providers,cn=config \ does not exist. This entry must be present in the Directory Server \ configuration FATAL_ERR_CONFIG_SYNCH_ENTRY_DOES_NOT_HAVE_PROVIDER_CONFIG_454=Configuration \ entry %s exists below the Directory Server synchronization provider root but \ does not contain attribute ds-cfg-synchronization-provider which must be \ present in all synchronization provider configuration entries FATAL_ERR_CONFIG_SYNCH_CANNOT_CHECK_FOR_PROVIDER_CONFIG_OC_455=An error \ occurred while attempting to determine whether configuration entry %s was a \ valid Directory Server synchronization provider: %s INFO_CONFIG_SYNCH_DESCRIPTION_PROVIDER_ENABLED_456=Indicates whether the \ associated Directory Server synchronization provider is enabled and should be \ used by the server. This attribute must be present in all synchronization \ provider entries and may not be changed while the Directory Server is running FATAL_ERR_CONFIG_SYNCH_PROVIDER_NO_ENABLED_ATTR_457=Synchronization provider \ configuration entry %s does not contain attribute \ ds-cfg-enabled which indicates whether the \ synchronization provider is enabled for use SEVERE_WARN_CONFIG_SYNCH_PROVIDER_DISABLED_458=The Directory Server \ synchronization provider defined in configuration entry %s is disabled. This \ provider will not be used FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_DETERMINE_ENABLED_STATE_459=An error \ occurred while attempting to determine whether the Directory Server \ synchronization provider defined in configuration entry %s should be enabled: \ %s INFO_CONFIG_SYNCH_DESCRIPTION_PROVIDER_CLASS_460=Fully-qualified name of the \ Java class that will provide the logic for the \ Directory Server synchronization provider. This attribute must be present in \ all synchronization provider entries and may not be changed while the \ Directory Server is running FATAL_ERR_CONFIG_SYNCH_NO_CLASS_ATTR_461=Synchronization provider \ configuration entry %s does not contain attribute \ ds-cfg-java-class which specifies the name of the class \ that implements the synchronization provider logic FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_DETERMINE_CLASS_462=An error occurred while \ attempting to determine the name of the class used to provide the Directory \ Server synchronization provider logic from configuration entry %s: %s FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_LOAD_PROVIDER_CLASS_463=An error occurred \ while attempting to load class %s referenced in synchronization provider \ configuration entry %s: %s @@ -1338,174 +578,12 @@ FATAL_ERR_CONFIG_SYNCH_ERROR_INITIALIZING_PROVIDER_465=An error occurred \ while attempting to initialize the Directory Server synchronization provider \ referenced in configuration entry %s: %s INFO_CONFIG_SYNCH_PROVIDER_HAS_BEEN_DISABLED_466=The synchronization provider \ defined in configuration entry %s is currently enabled but the configuration \ has changed so that it should be disabled. This will not take effect until \ the Directory Server is restarted FATAL_ERR_CONFIG_SYNCH_PROVIDER_CLASS_CHANGED_467=The Java class providing \ the logic for the synchronization provider defined in configuration entry %s \ has changed from %s to %s. This will not take effect until the Directory \ Server is restarted INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_WRITABILITY_468=Writability mode for \ this backend. The value may be "enabled" if all write \ operations will be allowed, "disabled" if all write operations will be \ rejected, or "internal-only" if only internal write operations and \ synchronization updates will be allowed. Changes to this configuration \ attribute will take effect immediately SEVERE_ERR_CONFIG_BACKEND_NO_WRITABILITY_MODE_469=The backend defined in \ configuration entry %s does not have a value for configuration attribute \ ds-cfg-writability-mode which indicates the writability mode for that \ backend. The backend will be disabled SEVERE_ERR_CONFIG_BACKEND_INVALID_WRITABILITY_MODE_470=The backend defined in \ configuration entry %s has an invalid writability mode of %s. The backend \ will be disabled SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_WRITABILITY_471=An unexpected \ error occurred while attempting to determine the writability mode for the \ backend defined in configuration entry %s: %s. The backend will be disabled INFO_CONFIG_CORE_DESCRIPTION_WRITABILITY_MODE_472=Writability \ mode for the Directory Server. The value may be one of "enabled", \ "disabled", or "internal-only". Changes to this configuration attribute will \ take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_WRITABILITY_MODE_473=Configuration entry %s \ has an invalid value for configuration attribute ds-cfg-writability-mode (the \ value should be one of "enabled", "disabled", or "internal-only"): %s INFO_CONFIG_CORE_DESCRIPTION_BIND_WITH_DN_REQUIRES_PW_474=Indicates whether \ simple binds that contain a DN will also be required to contain a password. \ If this is disabled, then binds with no password will always be treated as \ anonymous, even if they contain a bind DN, which can create a security hole \ for some kinds of applications. With this option enabled, then any simple \ bind request that contains a DN but no password will be rejected rather than \ defaulting to anonymous authentication. Changes to this configuration \ attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_BIND_WITH_DN_REQUIRES_PW_475=Configuration \ entry %s has an invalid value for configuration attribute \ ds-cfg-bind-with-dn-requires-password (the value should be either "TRUE" or \ "FALSE"): %s FATAL_ERR_CONFIG_PWVALIDATOR_CANNOT_GET_BASE_476=An error occurred while \ attempting to retrieve the password validator base entry cn=Password \ Validators,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_PWVALIDATOR_BASE_DOES_NOT_EXIST_477=The password validator \ configuration base cn=Password Validators,cn=config does not exist in the \ Directory Server configuration. This entry must be present for the server to \ function properly SEVERE_ERR_CONFIG_PWVALIDATOR_ENTRY_UNACCEPTABLE_478=Configuration entry %s \ does not contain a valid password validator configuration: %s. It will be \ ignored SEVERE_ERR_CONFIG_PWVALIDATOR_CANNOT_CREATE_VALIDATOR_479=An error occurred \ while attempting to create a Directory Server password validator from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_OBJECTCLASS_480=Configuration entry %s \ does not contain the ds-cfg-password-validator objectclass, which is required \ for password validator definitions INFO_CONFIG_PWVALIDATOR_DESCRIPTION_CLASS_NAME_481=The fully-qualified name \ of the Java class that defines the Directory Server password validator. If \ this is altered while the associated validator is enabled, then that \ validator must be disabled and re-enabled for the change to take effect SEVERE_ERR_CONFIG_PWVALIDATOR_NO_CLASS_NAME_482=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class \ name for the associated password validator SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_CLASS_NAME_483=Configuration entry %s \ has an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_CLASS_484=Class %s specified in \ configuration entry %s does not contain a valid password validator \ implementation: %s INFO_CONFIG_PWVALIDATOR_DESCRIPTION_ENABLED_485=Indicates whether this \ Directory Server password validator should be enabled. Changes to this \ attribute will take effect immediately SEVERE_ERR_CONFIG_PWVALIDATOR_NO_ENABLED_ATTR_486=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether the password \ validator should be enabled for use in the Directory Server SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_ENABLED_VALUE_487=Configuration entry \ %s has an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_PWVALIDATOR_CLASS_ACTION_REQUIRED_488=The requested change in the \ password validator class name from %s to %s in configuration entry %s cannot \ be dynamically applied. This change will not take effect until the validator \ is disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILED_489=An error occurred while \ trying to initialize an instance of class %s as a password validator as \ defined in configuration entry %s: %s MILD_ERR_CONFIG_PWVALIDATOR_EXISTS_490=Unable to add a new password validator \ entry with DN %s because there is already a validator registered with that DN SEVERE_ERR_CONFIG_PWVALIDATOR_UNACCEPTABLE_CONFIG_491=The configuration for \ the password validator defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry FATAL_ERR_CONFIG_PWGENERATOR_CANNOT_GET_BASE_492=An error occurred while \ attempting to retrieve the password generator base entry cn=Password \ Generators,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_PWGENERATOR_BASE_DOES_NOT_EXIST_493=The password generator \ configuration base cn=Password Generators,cn=config does not exist in the \ Directory Server configuration. This entry must be present for the server to \ function properly SEVERE_ERR_CONFIG_PWGENERATOR_ENTRY_UNACCEPTABLE_494=Configuration entry %s \ does not contain a valid password generator configuration: %s. It will be \ ignored SEVERE_ERR_CONFIG_PWGENERATOR_CANNOT_CREATE_GENERATOR_495=An error occurred \ while attempting to create a Directory Server password generator from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_OBJECTCLASS_496=Configuration entry %s \ does not contain the ds-cfg-password-generator objectclass, which is required \ for password generator definitions INFO_CONFIG_PWGENERATOR_DESCRIPTION_CLASS_NAME_497=The fully-qualified name \ of the Java class that defines the Directory Server password generator. If \ this is altered while the associated generator is enabled, then that \ generator must be disabled and re-enabled for the change to take effect SEVERE_ERR_CONFIG_PWGENERATOR_NO_CLASS_NAME_498=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class \ name for the associated password generator SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_CLASS_NAME_499=Configuration entry %s \ has an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_CLASS_500=Class %s specified in \ configuration entry %s does not contain a valid password generator \ implementation: %s INFO_CONFIG_PWGENERATOR_DESCRIPTION_ENABLED_501=Indicates whether this \ Directory Server password generator should be enabled. Changes to this \ attribute will take effect immediately SEVERE_ERR_CONFIG_PWGENERATOR_NO_ENABLED_ATTR_502=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether the password \ generator should be enabled for use in the Directory Server SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_ENABLED_VALUE_503=Configuration entry \ %s has an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_PWGENERATOR_CLASS_ACTION_REQUIRED_504=The requested change in the \ password generator class name from %s to %s in configuration entry %s cannot \ be dynamically applied. This change will not take effect until the generator \ is disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILED_505=An error occurred while \ trying to initialize an instance of class %s as a password generator as \ defined in configuration entry %s: %s MILD_ERR_CONFIG_PWGENERATOR_EXISTS_506=Unable to add a new password generator \ entry with DN %s because there is already a generator registered with that DN SEVERE_ERR_CONFIG_PWGENERATOR_UNACCEPTABLE_CONFIG_507=The configuration for \ the password generator defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry INFO_CONFIG_CORE_DESCRIPTION_DEFAULT_PWPOLICY_DN_508=DN of the \ configuration entry that defines the default password policy for the \ Directory Server, which will be applied for all users for which a custom \ password policy is not defined. This entry must exist and must specify a \ valid password policy configuration. Changes to this configuration attribute \ will take effect immediately SEVERE_ERR_CONFIG_CORE_NO_DEFAULT_PWPOLICY_509=No default password policy was \ configured for the Directory Server. This must be specified by the \ ds-cfg-default-password-policy attribute in configuration entry %s SEVERE_ERR_CONFIG_CORE_INVALID_DEFAULT_PWPOLICY_DN_510=Configuration entry %s \ has an invalid value for configuration attribute \ ds-cfg-default-password-policy (the value should a DN specifying the default \ password policy configuration entry): %s SEVERE_ERR_CONFIG_CORE_NO_SUCH_PWPOLICY_511=The value %s for configuration \ attribute ds-cfg-default-password-policy does not refer to a valid password \ policy configuration entry FATAL_ERR_CONFIG_PWPOLICY_CANNOT_GET_BASE_512=An error occurred while \ attempting to retrieve the password policy base entry cn=Password \ Policies,cn=config from the Directory Server configuration: %s SEVERE_ERR_CONFIG_PWPOLICY_BASE_DOES_NOT_EXIST_513=The password policy \ configuration base cn=Password Policies,cn=config does not exist in the \ Directory Server configuration. This entry must be present for the server to \ function properly SEVERE_ERR_CONFIG_PWPOLICY_NO_POLICIES_514=No password policies have been \ defined below the cn=Password Policies,cn=config entry in the Directory \ Server configuration. At least one password policy configuration must be \ @@ -1524,64 +602,12 @@ removed from the Directory Server configuration. Any user entries that \ explicitly reference this password policy will no longer be allowed to \ authenticate FATAL_ERR_CONFIG_AUTHZ_CANNOT_GET_ENTRY_519=An error occurred while \ attempting to retrieve the Directory Server access control configuration \ entry cn=Access Control Handler,cn=config: %s FATAL_ERR_CONFIG_AUTHZ_ENTRY_DOES_NOT_EXIST_520=The Directory Server access \ control configuration entry cn=Access Control Handler,cn=config does not \ exist. This entry must be present in the Directory Server configuration FATAL_ERR_CONFIG_AUTHZ_ENTRY_DOES_NOT_HAVE_OBJECT_CLASS_521=The Directory \ Server access control configuration entry cn=Access Control Handler,cn=config \ does not have the correct object class. This entry must have the object \ class ds-cfg-access-control-handler in order to be valid INFO_CONFIG_AUTHZ_DESCRIPTION_ENABLED_523=Indicates whether access control is \ enabled and should be used by the server. This attribute is mandatory FATAL_ERR_CONFIG_AUTHZ_NO_ENABLED_ATTR_524=The access control configuration \ entry %s does not contain attribute ds-cfg-enabled which \ indicates whether the access control is enabled for use SEVERE_WARN_CONFIG_AUTHZ_DISABLED_525=Access control has been disabled NOTICE_CONFIG_AUTHZ_ENABLED_526=Access control has been enabled and will use \ the %s implementation FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_DETERMINE_ENABLED_STATE_527=An error \ occurred while attempting to determine whether the Directory Server access \ control as defined in configuration entry %s should be enabled: %s INFO_CONFIG_AUTHZ_DESCRIPTION_CLASS_528=Fully-qualified name of \ the Java class that will provide the access control implementation for the \ Directory Server. This attribute is mandatory FATAL_ERR_CONFIG_AUTHZ_NO_CLASS_ATTR_529=The access control configuration \ entry %s does not contain attribute ds-cfg-java-class which specifies \ the name of the Java class providing the access control implementation for \ the Directory Server FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_DETERMINE_CLASS_530=An error occurred while \ attempting to determine the name of the class used to provide the Directory \ Server access control implementation from configuration entry %s: %s FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_LOAD_CLASS_531=An error occurred while \ attempting to load class %s referenced in the access control configuration \ entry %s: %s FATAL_ERR_CONFIG_AUTHZ_BAD_CLASS_532=The access control implementation class \ %s referenced in the access control configuration entry %s does not implement \ the %s interface: %s FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_INSTANTIATE_HANDLER_533=An error occurred \ while attempting to instantiate class %s referenced in the access control \ configuration entry %s: %s FATAL_ERR_CONFIG_AUTHZ_ERROR_INITIALIZING_HANDLER_534=An error occurred while \ attempting to initialize the Directory Server access control implementation \ referenced in configuration entry %s: %s FATAL_ERR_CONFIG_ROOTDN_CANNOT_GET_BASE_535=An error occurred while \ attempting to retrieve the root DN base entry cn=Root DNs,cn=config from the \ Directory Server configuration: %s SEVERE_ERR_CONFIG_ROOTDN_BASE_DOES_NOT_EXIST_536=The password policy \ configuration base cn=Root DNs,cn=config does not exist in the Directory \ Server configuration. This entry must be present for the server to function \ properly SEVERE_ERR_CONFIG_ROOTDN_ENTRY_UNACCEPTABLE_537=Configuration entry %s does \ not contain a valid root DN configuration: %s. It will be ignored SEVERE_ERR_CONFIG_ROOTDN_CANNOT_CREATE_538=An error occurred while attempting \ to create a Directory Server root DN from the information in configuration \ entry %s: %s SEVERE_ERR_CONFIG_ROOTDN_INVALID_OBJECTCLASS_539=Configuration entry %s does \ not contain the ds-cfg-root-dn-user objectclass, which is required for Directory \ Server root DN definitions INFO_CONFIG_ROOTDN_DESCRIPTION_ALTERNATE_BIND_DN_540=Specifies one or more \ alternate bind DNs that may be used to authenticate as the associated root \ DN, in addition to the actual DN of the root DN configuration entry. \ @@ -1592,83 +618,12 @@ SEVERE_ERR_CONFIG_ROOTDN_CONFLICTING_MAPPING_541=Unable to register "%s" as \ an alternate bind DN for user "%s" because it is already registered as an \ alternate bind DN for root user "%s" SEVERE_ERR_CONFIG_ROOTDN_CANNOT_PARSE_ALTERNATE_BIND_DNS_542=An error \ occurred while trying to parse the set of alternate bind DNs for root user \ %s: %s SEVERE_ERR_CONFIG_ROOTDN_CANNOT_REGISTER_ALTERNATE_BIND_DN_543=An error \ occurred while trying to register"%s" as an alternate bind DN for root user \ "%s": %s SEVERE_ERR_CONFIG_ROOTDN_EXISTS_544=Unable to add root DN entry %s because \ another root user is already registered with that DN FATAL_ERR_CONFIG_ACCTNOTHANDLER_CANNOT_GET_BASE_545=An error occurred while \ attempting to retrieve the account status notification handler base entry \ cn=Account Status Notification Handlers,cn=config from the Directory Server \ configuration: %s SEVERE_WARN_CONFIG_ACCTNOTHANDLER_BASE_DOES_NOT_EXIST_546=The account status \ notification handler configuration base cn=Account Status Notification \ Handlers,cn=config does not exist in the Directory Server configuration. \ This entry must be present for the server to function properly SEVERE_ERR_CONFIG_ACCTNOTHANDLER_ENTRY_UNACCEPTABLE_547=Configuration entry \ %s does not contain a valid account status notification handler \ configuration: %s. It will be ignored SEVERE_ERR_CONFIG_ACCTNOTHANDLER_CANNOT_CREATE_HANDLER_548=An error occurred \ while attempting to create a Directory Server account status notification \ handler from the information in configuration entry %s: %s SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_OBJECTCLASS_549=Configuration entry \ %s does not contain the ds-cfg-account-status-notification-handler \ objectclass, which is required for account status notification handler \ definitions INFO_CONFIG_ACCTNOTHANDLER_DESCRIPTION_CLASS_NAME_550=The fully-qualified \ name of the Java class that defines the Directory Server account status \ notification handler. If this is altered while the associated notification \ handler is enabled, then that handler must be disabled and re-enabled for the \ change to take effect SEVERE_ERR_CONFIG_ACCTNOTHANDLER_NO_CLASS_NAME_551=Configuration entry %s \ does not contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the \ fully-qualified class name for the associated account status notification \ handler SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_CLASS_NAME_552=Configuration entry \ %s has an invalid value for attribute \ ds-cfg-java-class: %s SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_CLASS_553=Class %s specified in \ configuration entry %s does not contain a valid account status notification \ handler implementation: %s INFO_CONFIG_ACCTNOTHANDLER_DESCRIPTION_ENABLED_554=Indicates whether this \ Directory Server account status notification handler should be enabled. \ Changes to this attribute will take effect immediately SEVERE_ERR_CONFIG_ACCTNOTHANDLER_NO_ENABLED_ATTR_555=Configuration entry %s \ does not contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether \ the account status notification handler should be enabled for use in the \ Directory Server SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_ENABLED_VALUE_556=Configuration \ entry %s has an invalid value for attribute \ ds-cfg-enabled: %s INFO_CONFIG_ACCTNOTHANDLER_CLASS_ACTION_REQUIRED_557=The requested change in \ the account status notification handler class name from %s to %s in \ configuration entry %s cannot be dynamically applied. This change will not \ take effect until the notification handler is disabled and re-enabled or the \ Directory Server is restarted MILD_ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILED_558=An error occurred \ while trying to initialize an instance of class %s as an account status \ notification handler as defined in configuration entry %s: %s MILD_ERR_CONFIG_ACCTNOTHANDLER_EXISTS_559=Unable to add a new account status \ notification handler entry with DN %s because there is already a notification \ handler registered with that DN SEVERE_ERR_CONFIG_ACCTNOTHANDLER_UNACCEPTABLE_CONFIG_560=The configuration \ for the account status notification handler defined in configuration entry %s \ was not acceptable according to its internal validation. However, no \ specific information is available regarding the problem(s) with the entry INFO_CONFIG_CORE_DESCRIPTION_LOOKTHROUGH_LIMIT_561=Default \ maximum number of candidate entries checked for matches when processing a \ search operation. This may be overridden on a per-user basis by including \ the ds-rlim-lookthrough-limit operational attribute in the user's entry. \ Changes to this configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_LOOKTHROUGH_LIMIT_562=Configuration entry %s \ has an invalid value for configuration attribute ds-cfg-lookthrough-limit (It \ should be a positive integer value specifying the lookthrough limit to use, \ or a value of 0 or -1 to indicate that no limit should be enforced): %s FATAL_ERR_CONFIG_UNABLE_TO_APPLY_STARTUP_CHANGES_563=An error occurred while \ attempting to apply the changes contained in file %s to the server \ configuration at startup: %s @@ -1676,23 +631,12 @@ at server startup: %s FATAL_ERR_CONFIG_UNABLE_TO_APPLY_CHANGES_FILE_565=One or more errors occurred \ while applying changes on server startup INFO_CONFIG_DESCRIPTION_BACKEND_MODE_566=The permissions used for the \ directory containing the backend database files SEVERE_ERR_CONFIG_BACKEND_MODE_INVALID_567=Configuration entry %s does not \ contain a valid value for configuration attribute ds-cfg-db-directory-permissions (It \ should be an UNIX permission mode in three-digit octal notation.) SEVERE_ERR_CONFIG_BACKEND_INSANE_MODE_568=Invalid UNIX file permissions %s \ does not allow read and write access to the backend database directory by \ the backend INFO_CONFIG_CORE_DESCRIPTION_TIME_LIMIT_569=Default maximum \ length of time that should be allowed when processing a search operation. \ This may be overridden on a per-user basis by including the \ ds-rlim-time-limit operational attribute in the user's entry. Changes to \ this configuration attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_INVALID_TIME_LIMIT_570=Configuration entry %s has an \ invalid value for configuration attribute ds-cfg-time-limit (it should be an \ integer value followed by a space and a time unit of seconds, minutes, hours, \ days, or weeks): %s SEVERE_ERR_CONFIG_PWPOLICY_NO_DEFAULT_POLICY_571=No default password policy \ is configured for the Directory Server. The default password policy must be \ specified by the ds-cfg-default-password-policy attribute in the cn=config \ @@ -1706,80 +650,9 @@ SEVERE_ERR_CONFIG_FILE_CANNOT_WRITE_CONFIG_ARCHIVE_575=An error occurred \ while trying to write the current configuration to the configuration archive: \ %s INFO_CONFIG_CORE_DESCRIPTION_REJECT_UNAUTHENTICATED_REQUESTS_576=Indicates \ whether the Directory Server should reject requests from unauthenticated \ clients. If this is set to "true", then unauthenticated clients will only be \ allowed to send bind and StartTLS requests. Changes to this configuration \ attribute will take effect immediately SEVERE_ERR_CONFIG_CORE_REJECT_UNAUTHENTICATED_REQUESTS_INVALID_577=Configuration \ entry %s has an invalid value for configuration attribute \ ds-cfg-reject-unauthenticated-requests(the value should be either true or \ false) FATAL_ERR_CONFIG_GROUP_CANNOT_GET_BASE_578=An error occurred while attempting \ to retrieve the group implementation base entry cn=Group \ Implementations,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_GROUP_BASE_DOES_NOT_EXIST_579=The group implementation \ configuration base cn=Group Implementations,cn=config does not exist in the \ Directory Server configuration. This entry must be present for the server to \ function properly SEVERE_ERR_CONFIG_GROUP_ENTRY_UNACCEPTABLE_580=Configuration entry %s does \ not contain a valid group implementation configuration: %s. It will be \ ignored SEVERE_ERR_CONFIG_GROUP_CANNOT_CREATE_IMPLEMENTATION_581=An error occurred \ while attempting to create a Directory Server group implementation from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_GROUP_INVALID_OBJECTCLASS_582=Configuration entry %s does \ not contain the ds-cfg-group-implementation objectclass, which is required \ for group implementation definitions INFO_CONFIG_GROUP_DESCRIPTION_CLASS_NAME_583=The fully-qualified name of the \ Java class that defines the Directory Server group implementation. If this \ is while the associated implementation is enabled, then that group \ implementation must be disabled and re-enabled for the change to take effect SEVERE_ERR_CONFIG_GROUP_NO_CLASS_NAME_584=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class \ name for the associated group implementation SEVERE_ERR_CONFIG_GROUP_INVALID_CLASS_NAME_585=Configuration entry %s has an \ invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_GROUP_INVALID_CLASS_586=Class %s specified in configuration \ entry %s does not contain a valid group implementation: %s INFO_CONFIG_GROUP_DESCRIPTION_ENABLED_587=Indicates whether this Directory \ Server group implementation should be enabled. Changes to this attribute \ will take effect immediately SEVERE_ERR_CONFIG_GROUP_NO_ENABLED_ATTR_588=Configuration entry %s does not \ contain a valid value for configuration attribute \ ds-cfg-enabled which indicates whether the group \ implementation should be enabled for use in the Directory Server SEVERE_ERR_CONFIG_GROUP_INVALID_ENABLED_VALUE_589=Configuration entry %s has \ an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_GROUP_CLASS_ACTION_REQUIRED_590=The requested change in the group \ implementation class name from %s to %s in configuration entry %s cannot be \ dynamically applied. This change will not take effect until the group \ implementation is disabled and re-enabled or the Directory Server is \ restarted MILD_ERR_CONFIG_GROUP_INITIALIZATION_FAILED_591=An error occurred while \ trying to initialize an instance of class %s as a group implementation as in \ configuration entry %s: %s MILD_ERR_CONFIG_GROUP_EXISTS_592=Unable to add a new group implementation \ entry with DN %s because there is already a group implementation registered \ with that DN SEVERE_ERR_CONFIG_GROUP_UNACCEPTABLE_CONFIG_593=The configuration for the \ group implementation defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry SEVERE_ERR_CONFIG_ROOTDN_DESCRIPTION_ROOT_PRIVILEGE_594=Set of \ privileges that should automatically be assigned to root users when they \ authenticate to the server SEVERE_WARN_CONFIG_ROOTDN_UNRECOGNIZED_PRIVILEGE_595=The set of default root \ privileges contained in configuration attribute %s of entry %s contains an \ unrecognized privilege %s SEVERE_ERR_CONFIG_ROOTDN_ERROR_DETERMINING_ROOT_PRIVILEGES_596=An error \ occurred while attempting to determine the set of privileges that root users \ should be granted by default: %s INFO_CONFIG_ROOTDN_UPDATED_PRIVILEGES_597=The set of privileges that will \ automatically be assigned to root users has been updated. This new privilege \ set will not apply to any existing connection already authenticated as a root \ user, but will used for any subsequent root user authentications MILD_ERR_CONFIG_FILE_ADD_INSUFFICIENT_PRIVILEGES_598=You do not have \ sufficient privileges to perform add operations in the Directory Server \ configuration @@ -1797,134 +670,23 @@ configuration MILD_ERR_CONFIG_FILE_MODIFY_PRIVS_INSUFFICIENT_PRIVILEGES_603=You do not have \ sufficient privileges to change the set of default root privileges FATAL_ERR_CONFIG_CERTMAPPER_CANNOT_GET_BASE_604=An error occurred while \ attempting to retrieve the certificate mapper base entry cn=Certificate \ Mappers,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_CERTMAPPER_BASE_DOES_NOT_EXIST_605=The certificate mapper \ configuration base cn=Certificate Mappers,cn=config does not exist in the \ Directory Server configuration. This entry must be present for the server to \ function properly SEVERE_ERR_CONFIG_CERTMAPPER_ENTRY_UNACCEPTABLE_606=Configuration entry %s \ does not contain a valid certificate mapper configuration: %s. It will be \ ignored SEVERE_ERR_CONFIG_CERTMAPPER_CANNOT_CREATE_MAPPER_607=An error occurred while \ attempting to create a Directory Server certificate mapper from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_OBJECTCLASS_608=Configuration entry %s \ does not contain the ds-cfg-certificate-mapper objectclass, which is required \ for certificate mapper definitions SEVERE_ERR_CONFIG_CERTMAPPER_NO_CLASS_NAME_609=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class \ name for the associated certificate mapper SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_CLASS_NAME_610=Configuration entry %s \ has an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_CLASS_611=Class %s specified in \ configuration entry %s does not contain a valid certificate mapper \ implementation: %s SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_ENABLED_VALUE_612=Configuration entry %s \ has an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_CERTMAPPER_CLASS_ACTION_REQUIRED_613=The requested change in the \ certificate mapper class name from %s to %s in configuration entry %s cannot \ be dynamically applied. This change will not take effect until the mapper is \ disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILED_614=An error occurred while \ trying to initialize an instance of class %s as a certificate mapper as \ defined in configuration entry %s: %s MILD_ERR_CONFIG_CERTMAPPER_EXISTS_615=Unable to add a new certificate mapper \ entry with DN %s because there is already a mapper registered with that DN SEVERE_ERR_CONFIG_CERTMAPPER_UNACCEPTABLE_CONFIG_616=The configuration for \ the certificate mapper defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry FATAL_ERR_CONFIG_KEYMANAGER_CANNOT_GET_BASE_617=An error occurred while \ attempting to retrieve the key manager provider base entry cn=Key Manager \ Providers,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_KEYMANAGER_BASE_DOES_NOT_EXIST_618=The key manager \ provider configuration base cn=Key Manager Providers,cn=config does not exist \ in the Directory Server configuration. This entry must be present for the \ server to function properly SEVERE_ERR_CONFIG_KEYMANAGER_ENTRY_UNACCEPTABLE_619=Configuration entry %s \ does not contain a valid key manager provider configuration: %s. It will be \ ignored SEVERE_ERR_CONFIG_KEYMANAGER_CANNOT_CREATE_PROVIDER_620=An error occurred \ while attempting to create a Directory Server key manager provider from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_OBJECTCLASS_621=Configuration entry %s \ does not contain the ds-cfg-key-manager-provider objectclass, which is \ required for key manager provider definitions SEVERE_ERR_CONFIG_KEYMANAGER_NO_CLASS_NAME_622=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class \ name for the associated key manager provider SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_CLASS_NAME_623=Configuration entry %s \ has an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_CLASS_624=Class %s specified in \ configuration entry %s does not contain a valid key manager provider \ implementation: %s SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_ENABLED_VALUE_625=Configuration entry %s \ has an invalid value for attribute ds-cfg-enabled: %s INFO_CONFIG_KEYMANAGER_CLASS_ACTION_REQUIRED_626=The requested change in the \ key manager provider class name from %s to %s in configuration entry %s \ cannot be dynamically applied. This change will not take effect until the \ provider is disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILED_627=An error occurred while \ trying to initialize an instance of class %s as a key manager provider as \ defined in configuration entry %s: %s MILD_ERR_CONFIG_KEYMANAGER_EXISTS_628=Unable to add a new key manager \ provider entry with DN %s because there is already a provider registered with \ that DN SEVERE_ERR_CONFIG_KEYMANAGER_UNACCEPTABLE_CONFIG_629=The configuration for \ the key manager provider defined in configuration entry %s was not acceptable \ according to its internal validation. However, no specific information is \ available regarding the problem(s) with the entry FATAL_ERR_CONFIG_TRUSTMANAGER_CANNOT_GET_BASE_630=An error occurred while \ attempting to retrieve the trust manager provider base entry cn=Trust Manager \ Providers,cn=config from the Directory Server configuration: %s SEVERE_WARN_CONFIG_TRUSTMANAGER_BASE_DOES_NOT_EXIST_631=The trust manager \ provider configuration base cn=Trust Manager Providers,cn=config does not \ exist in the Directory Server configuration. This entry must be present for \ the server to function properly SEVERE_ERR_CONFIG_TRUSTMANAGER_ENTRY_UNACCEPTABLE_632=Configuration entry %s \ does not contain a valid trust manager provider configuration: %s. It will \ be ignored SEVERE_ERR_CONFIG_TRUSTMANAGER_CANNOT_CREATE_PROVIDER_633=An error occurred \ while attempting to create a Directory Server trust manager provider from the \ information in configuration entry %s: %s SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_OBJECTCLASS_634=Configuration entry %s \ does not contain the ds-cfg-trust-manager-provider objectclass, which is \ required for trust manager provider definitions SEVERE_ERR_CONFIG_TRUSTMANAGER_NO_CLASS_NAME_635=Configuration entry %s does \ not contain a valid value for configuration attribute \ ds-cfg-java-class which specifies the fully-qualified class \ name for the associated trust manager provider SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_CLASS_NAME_636=Configuration entry %s \ has an invalid value for attribute ds-cfg-java-class: %s SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_CLASS_637=Class %s specified in \ configuration entry %s does not contain a valid trust manager provider \ implementation: %s SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_ENABLED_VALUE_638=Configuration entry \ %s has an invalid value for attribute ds-cfg-enabled: \ %s INFO_CONFIG_TRUSTMANAGER_CLASS_ACTION_REQUIRED_639=The requested change in \ the trust manager provider class name from %s to %s in configuration entry %s \ cannot be dynamically applied. This change will not take effect until the \ provider is disabled and re-enabled or the Directory Server is restarted MILD_ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILED_640=An error occurred \ while trying to initialize an instance of class %s as a trust manager \ provider as defined in configuration entry %s: %s MILD_ERR_CONFIG_TRUSTMANAGER_EXISTS_641=Unable to add a new trust manager \ provider entry with DN %s because there is already a provider registered with \ that DN SEVERE_ERR_CONFIG_TRUSTMANAGER_UNACCEPTABLE_CONFIG_642=The configuration for \ the trust manager provider defined in configuration entry %s was not \ acceptable according to its internal validation. However, no specific \ information is available regarding the problem(s) with the entry SEVERE_ERR_CONFIG_JMX_CANNOT_GET_ATTRIBUTE_643=Unable to retrieve JMX \ attribute %s associated with configuration entry %s: %s SEVERE_ERR_CONFIG_JMX_SET_ATTR_NO_CONNECTION_644=Unable to set the value of \ JMX attribute %s associated with configuration entry %s because no JMX \ connection is available SEVERE_ERR_CONFIG_CHANGE_NO_RESULT_645=%s.%s returned a result of null for \ entry %s SEVERE_ERR_CONFIG_CHANGE_RESULT_ERROR_646=%s.%s failed for entry %s: result \ @@ -2119,9 +881,6 @@ while trying to initialize a workflow element from class %s with the \ information in configuration entry %s: %s. This workflow element will be \ disabled MILD_ERR_CONFIG_WORKFLOW_ELEMENT_ALREADY_REGISTERED_712=The workflow \ element %s is already registered with the Directory Server. This workflow \ element will be ignored SEVERE_ERR_CONFIG_WORKFLOW_CANNOT_CONFIGURE_MANUAL_713=An error occurred \ while trying to configure in manual mode the workflows in the \ Directory Server, and rollback to automatic configuration mode has failed \ @@ -2158,9 +917,6 @@ SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_LDAP_SYNTAX_724=An ldap syntax read \ from schema configuration file %s conflicts with another ldap syntax already \ read into the schema: %s. The later ldap syntax description will be used MILD_ERR_CONFIG_CORE_INVALID_MAX_PSEARCH_LIMIT_725=The provided maximum allowed \ simultaneous persistent searches '%d' is invalid. The maximum allowed \ value must be between 0 and '%d' where '%d' is the number of worker threads SEVERE_ERR_CONFIG_PWPOLICY_DEFAULT_POLICY_IS_WRONG_TYPE_726=The configuration \ entry '%s' is currently defined to be the default password policy, however it \ is not a password policy @@ -2187,4 +943,3 @@ MILD_WARN_CONFIG_LOGGING_UNSUPPORTED_FIELDS_IN_LOG_FORMAT_734=The log format \ for %s contains the folowing unsupported fields: %s. Their output will be \ replaced with a dash ("-") character NOTICE_DIRECTORY_CONFIGURATION_CHANGED_735=The server configuration has been changed
