# CDDL HEADER START
|
#
|
# The contents of this file are subject to the terms of the
|
# Common Development and Distribution License, Version 1.0 only
|
# (the "License"). You may not use this file except in compliance
|
# with the License.
|
#
|
# You can obtain a copy of the license at
|
# trunk/opends/resource/legal-notices/OpenDS.LICENSE
|
# or https://OpenDS.dev.java.net/OpenDS.LICENSE.
|
# See the License for the specific language governing permissions
|
# and limitations under the License.
|
#
|
# When distributing Covered Code, include this CDDL HEADER in each
|
# file and include the License file at
|
# trunk/opends/resource/legal-notices/OpenDS.LICENSE. If applicable,
|
# add the following below this CDDL HEADER, with the fields enclosed
|
# by brackets "[]" replaced with your own identifying information:
|
# Portions Copyright [yyyy] [name of copyright owner]
|
#
|
# CDDL HEADER END
|
#
|
# Copyright 2006-2010 Sun Microsystems, Inc.
|
|
|
|
#
|
# Global directives
|
#
|
global.category=CORE
|
|
#
|
# Format string definitions
|
#
|
# Keys must be formatted as follows:
|
#
|
# [SEVERITY]_[DESCRIPTION]_[ORDINAL]
|
#
|
# where:
|
#
|
# SEVERITY is one of:
|
# [INFO, MILD_WARN, SEVERE_WARN, MILD_ERR, SEVERE_ERR, FATAL_ERR, DEBUG, NOTICE]
|
#
|
# DESCRIPTION is an upper case string providing a hint as to the context of
|
# the message in upper case with the underscore ('_') character serving as
|
# word separator
|
#
|
# ORDINAL is an integer unique among other ordinals in this file
|
#
|
MILD_ERR_CANNOT_CANCEL_ABANDON_1=Abandon requests cannot be canceled
|
MILD_ERR_CANNOT_CANCEL_BIND_2=Bind requests cannot be canceled
|
MILD_ERR_CANNOT_CANCEL_UNBIND_3=Unbind requests cannot be canceled
|
INFO_DISCONNECT_DUE_TO_UNBIND_4=Client Unbind
|
INFO_DISCONNECT_DUE_TO_CLIENT_CLOSURE_5=Client Disconnect
|
INFO_DISCONNECT_DUE_TO_REJECTED_CLIENT_6=Client Connection Rejected
|
INFO_DISCONNECT_DUE_TO_IO_ERROR_7=I/O Error
|
INFO_DISCONNECT_DUE_TO_PROTOCOL_ERROR_8=Protocol Error
|
INFO_DISCONNECT_DUE_TO_SERVER_SHUTDOWN_9=Server Shutdown
|
INFO_DISCONNECT_BY_ADMINISTRATOR_10=Administrative Termination
|
INFO_DISCONNECT_DUE_TO_SECURITY_PROBLEM_11=Security Problem
|
INFO_DISCONNECT_DUE_TO_MAX_REQUEST_SIZE_12=Maximum Request Size Exceeded
|
INFO_DISCONNECT_DUE_TO_ADMIN_LIMIT_13=Administrative Limit Exceeded
|
INFO_DISCONNECT_DUE_TO_IDLE_TIME_LIMIT_14=Idle Time Limit Exceeded
|
INFO_DISCONNECT_DUE_TO_IO_TIMEOUT_15=I/O Timeout
|
INFO_DISCONNECT_BY_PLUGIN_16=Connection Closed by Plugin
|
INFO_DISCONNECT_OTHER_17=Unknown Closure Reason
|
INFO_ERROR_CATEGORY_ACCESS_CONTROL_39=access-control
|
INFO_ERROR_CATEGORY_BACKEND_40=backend
|
INFO_ERROR_CATEGORY_CONFIG_41=config
|
INFO_ERROR_CATEGORY_CONNECTION_HANDLING_42=connection
|
INFO_ERROR_CATEGORY_CORE_SERVER_43=core
|
INFO_ERROR_CATEGORY_EXTENDED_OPERATION_45=extended-op
|
INFO_ERROR_CATEGORY_PLUGIN_46=plugin
|
INFO_ERROR_CATEGORY_REQUEST_HANDLING_47=request
|
INFO_ERROR_CATEGORY_SASL_MECHANISM_48=sasl
|
INFO_ERROR_CATEGORY_SHUTDOWN_49=shutdown
|
INFO_ERROR_CATEGORY_STARTUP_50=startup
|
INFO_ERROR_CATEGORY_SYNCHRONIZATION_51=sync
|
INFO_ERROR_SEVERITY_FATAL_ERROR_54=fatal-error
|
INFO_ERROR_SEVERITY_INFORMATIONAL_56=info
|
INFO_ERROR_SEVERITY_MILD_ERROR_57=mild-error
|
INFO_ERROR_SEVERITY_MILD_WARNING_58=mild-warning
|
INFO_ERROR_SEVERITY_SEVERE_ERROR_59=severe-error
|
INFO_ERROR_SEVERITY_SEVERE_WARNING_60=severe-warning
|
INFO_RESULT_SUCCESS_63=Success
|
INFO_RESULT_OPERATIONS_ERROR_64=Operations Error
|
INFO_RESULT_PROTOCOL_ERROR_65=Protocol Error
|
INFO_RESULT_TIME_LIMIT_EXCEEDED_66=Time Limit Exceeded
|
INFO_RESULT_SIZE_LIMIT_EXCEEDED_67=Size Limit Exceeded
|
INFO_RESULT_COMPARE_FALSE_68=Compare False
|
INFO_RESULT_COMPARE_TRUE_69=Compare True
|
INFO_RESULT_AUTH_METHOD_NOT_SUPPORTED_70=Authentication Method Not Supported
|
INFO_RESULT_STRONG_AUTH_REQUIRED_71=Strong Authentication Required
|
INFO_RESULT_REFERRAL_72=Referral
|
INFO_RESULT_ADMIN_LIMIT_EXCEEDED_73=Administrative Limit Exceeded
|
INFO_RESULT_UNAVAILABLE_CRITICAL_EXTENSION_74=Unavailable Critical Extension
|
INFO_RESULT_CONFIDENTIALITY_REQUIRED_75=Confidentiality Required
|
INFO_RESULT_SASL_BIND_IN_PROGRESS_76=SASL Bind in Progress
|
INFO_RESULT_NO_SUCH_ATTRIBUTE_77=No Such Attribute
|
INFO_RESULT_UNDEFINED_ATTRIBUTE_TYPE_78=Undefined Attribute Type
|
INFO_RESULT_INAPPROPRIATE_MATCHING_79=Inappropriate Matching
|
INFO_RESULT_CONSTRAINT_VIOLATION_80=Constraint Violation
|
INFO_RESULT_ATTRIBUTE_OR_VALUE_EXISTS_81=Attribute or Value Exists
|
INFO_RESULT_INVALID_ATTRIBUTE_SYNTAX_82=Invalid Attribute Syntax
|
INFO_RESULT_NO_SUCH_OBJECT_83=No Such Entry
|
INFO_RESULT_ALIAS_PROBLEM_84=Alias Problem
|
INFO_RESULT_INVALID_DN_SYNTAX_85=Invalid DN Syntax
|
INFO_RESULT_ALIAS_DEREFERENCING_PROBLEM_86=Alias Dereferencing Problem
|
INFO_RESULT_INAPPROPRIATE_AUTHENTICATION_87=Inappropriate Authentication
|
INFO_RESULT_INVALID_CREDENTIALS_88=Invalid Credentials
|
INFO_RESULT_INSUFFICIENT_ACCESS_RIGHTS_89=Insufficient Access Rights
|
INFO_RESULT_BUSY_90=Busy
|
INFO_RESULT_UNAVAILABLE_91=Unavailable
|
INFO_RESULT_UNWILLING_TO_PERFORM_92=Unwilling to Perform
|
INFO_RESULT_LOOP_DETECT_93=Loop Detected
|
INFO_RESULT_NAMING_VIOLATION_94=Naming Violation
|
INFO_RESULT_OBJECTCLASS_VIOLATION_95=Object Class Violation
|
INFO_RESULT_NOT_ALLOWED_ON_NONLEAF_96=Not Allowed on Non-Leaf
|
INFO_RESULT_NOT_ALLOWED_ON_RDN_97=Not Allowed on RDN
|
INFO_RESULT_ENTRY_ALREADY_EXISTS_98=Entry Already Exists
|
INFO_RESULT_OBJECTCLASS_MODS_PROHIBITED_99=Object Class Modifications \
|
Prohibited
|
INFO_RESULT_AFFECTS_MULTIPLE_DSAS_100=Affects Multiple DSAs
|
INFO_RESULT_CANCELED_101=Canceled
|
INFO_RESULT_NO_SUCH_OPERATION_102=No Such Operation
|
INFO_RESULT_TOO_LATE_103=Too Late
|
INFO_RESULT_CANNOT_CANCEL_104=Cannot Cancel
|
INFO_RESULT_OTHER_105=Other
|
MILD_WARN_UNKNOWN_ATTRIBUTE_USAGE_106=Unable to determine the attribute usage \
|
type for attribute %s. The server will assume that it is user-defined
|
INFO_CANCELED_BY_SHUTDOWN_107=Processing on this operation has been canceled \
|
because the Directory Server is shutting down
|
MILD_ERR_UNCAUGHT_WORKER_THREAD_EXCEPTION_108=%s encountered an uncaught \
|
exception while processing operation %s: %s
|
SEVERE_WARN_UNEXPECTED_WORKER_THREAD_EXIT_109=%s is unexpectedly exiting when \
|
the Directory Server is not in the process of shutting down. This likely \
|
indicates that the thread encountered an unexpected error
|
SEVERE_ERR_CANNOT_CREATE_WORKER_THREAD_110=An unexpected error occurred while \
|
trying to create a worker thread: %s
|
MILD_WARN_OP_REJECTED_BY_SHUTDOWN_111=The request to process this operation \
|
has been rejected because the Directory Server has already started its \
|
shutdown process
|
SEVERE_WARN_OP_REJECTED_BY_QUEUE_FULL_112=The request to process this \
|
operation has been rejected because the work queue has already reached its \
|
maximum capacity of %d pending operations
|
SEVERE_WARN_WORKER_INTERRUPTED_WITHOUT_SHUTDOWN_113=%s was interrupted while \
|
waiting for new work: %s. This should not happen, but the thread will \
|
resume waiting for new work so there should be no adverse effects
|
SEVERE_WARN_WORKER_WAITING_UNCAUGHT_EXCEPTION_114=An unexpected exception was \
|
caught while %s was waiting for new work: %s. This should not happen, but \
|
the thread will resume waiting for new work so there should be no adverse \
|
effects
|
MILD_WARN_QUEUE_UNABLE_TO_CANCEL_115=The work queue caught an exception while \
|
trying to cancel pending operation %s when the Directory Server was shutting \
|
down: %s
|
MILD_WARN_QUEUE_UNABLE_TO_NOTIFY_THREAD_116=The work queue caught an \
|
exception while trying to notify %s that the Directory Server was shutting \
|
down: %s
|
INFO_DISCONNECT_DUE_TO_SERVER_ERROR_117=Server Error
|
FATAL_ERR_CANNOT_BOOTSTRAP_WHILE_RUNNING_118=The Directory Server is \
|
currently running. The configuration may not be bootstrapped while the \
|
server is online
|
FATAL_ERR_CANNOT_LOAD_CONFIG_HANDLER_CLASS_119=Unable to load class %s to \
|
serve as the Directory Server configuration handler: %s
|
FATAL_ERR_CANNOT_INSTANTIATE_CONFIG_HANDLER_120=Unable to create an instance \
|
of class %s to serve as the Directory Server configuration handler: %s
|
FATAL_ERR_CANNOT_INITIALIZE_CONFIG_HANDLER_121=An error occurred while trying \
|
to initialize the configuration handler %s using configuration file %s: %s
|
FATAL_ERR_CANNOT_START_BEFORE_BOOTSTRAP_122=The Directory Server may not be \
|
started before the configuration has been bootstrapped
|
FATAL_ERR_CANNOT_START_WHILE_RUNNING_123=The Directory Server may not be \
|
started while it is already running. Please stop the running instance \
|
before attempting to start it again
|
INFO_ERROR_CATEGORY_SCHEMA_124=schema
|
MILD_ERR_ATTR_TYPE_NORMALIZE_NO_MR_125=Unable to normalize value %s for \
|
attribute type %s because no equality matching rule is defined for that \
|
attribute
|
MILD_ERR_ENTRY_SCHEMA_MISSING_REQUIRED_ATTR_FOR_OC_126=Entry %s violates the \
|
Directory Server schema configuration because it is missing attribute %s \
|
which is required by objectclass %s
|
MILD_ERR_ENTRY_SCHEMA_DISALLOWED_USER_ATTR_FOR_OC_127=Entry %s violates the \
|
Directory Server schema configuration because it includes attribute %s which \
|
is not allowed by any of the objectclasses defined in that entry
|
SEVERE_ERR_CANNOT_BOOTSTRAP_MATCHING_RULE_129=An error occurred while \
|
attempting to bootstrap the matching rule defined in class %s: %s
|
SEVERE_ERR_CANNOT_BOOTSTRAP_SYNTAX_130=An error occurred while attempting to \
|
bootstrap the attribute syntax defined in class %s: %s
|
INFO_ERROR_SEVERITY_NOTICE_131=notice
|
INFO_DIRECTORY_BOOTSTRAPPING_132=The Directory Server is beginning the \
|
configuration bootstrapping process
|
INFO_DIRECTORY_BOOTSTRAPPED_133=The Directory Server has completed the \
|
configuration bootstrapping process
|
NOTICE_DIRECTORY_SERVER_STARTING_134=%s (build %s, R%d) starting up
|
NOTICE_DIRECTORY_SERVER_STARTED_135=The Directory Server has started \
|
successfully
|
INFO_ERROR_CATEGORY_EXTENSIONS_137=extensions
|
FATAL_ERR_CANNOT_CREATE_MBEAN_SERVER_138=An error occurred while attempting \
|
to create the JMX MBean server that will be used for monitoring, \
|
notification, and configuration interaction within the Directory Server: %s
|
NOTICE_SENT_ALERT_NOTIFICATION_139=The Directory Server has sent an alert \
|
notification generated by class %s (alert type %s, alert ID %s): %s
|
FATAL_ERR_UNCAUGHT_THREAD_EXCEPTION_140=An uncaught exception during \
|
processing for thread %s has caused it to terminate abnormally. The stack \
|
trace for that exception is: %s
|
NOTICE_SERVER_SHUTDOWN_141=The Directory Server has started the shutdown \
|
process. The shutdown was initiated by an instance of class %s and the \
|
reason provided for the shutdown was %s
|
FATAL_ERR_SHUTDOWN_DUE_TO_SHUTDOWN_HOOK_142=The Directory Server shutdown \
|
hook detected that the JVM is shutting down. This generally indicates that \
|
JVM received an external request to stop (e.g., through a kill signal)
|
MILD_ERR_SEARCH_FILTER_NULL_143=Unable to decode the provided filter string \
|
as a search filter because the provided string was empty or null
|
MILD_ERR_SEARCH_FILTER_UNCAUGHT_EXCEPTION_144=An unexpected error occurred \
|
while attempting to decode the string "%s" as a search filter: %s
|
MILD_ERR_SEARCH_FILTER_MISMATCHED_PARENTHESES_145=The provided search filter \
|
"%s" had mismatched parentheses around the portion between positions %d and \
|
%d
|
MILD_ERR_SEARCH_FILTER_NO_EQUAL_SIGN_146=The provided search filter "%s" was \
|
missing an equal sign in the suspected simple filter component between \
|
positions %d and %d
|
MILD_ERR_SEARCH_FILTER_INVALID_ESCAPED_BYTE_147=The provided search filter \
|
"%s" had an invalid escaped byte value at position %d. A backslash in a \
|
value must be followed by two hexadecimal characters that define the byte \
|
that has been encoded
|
MILD_ERR_SEARCH_FILTER_COMPOUND_MISSING_PARENTHESES_148=The provided search \
|
filter "%s" could not be decoded because the compound filter between \
|
positions %d and %d did not start with an open parenthesis and end with a \
|
close parenthesis (they may be parentheses for different filter components)
|
MILD_ERR_SEARCH_FILTER_NO_CORRESPONDING_OPEN_PARENTHESIS_149=The provided \
|
search filter "%s" could not be decoded because the closing parenthesis at \
|
position %d did not have a corresponding open parenthesis
|
MILD_ERR_SEARCH_FILTER_NO_CORRESPONDING_CLOSE_PARENTHESIS_150=The provided \
|
search filter "%s" could not be decoded because the opening parenthesis at \
|
position %d did not have a corresponding close parenthesis
|
MILD_ERR_SEARCH_FILTER_SUBSTRING_NO_ASTERISKS_151=The provided search filter \
|
"%s" could not be decoded because the assumed substring filter value between \
|
positions %d and %d did not have any asterisk wildcard characters
|
MILD_ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_COLON_152=The provided search \
|
filter "%s" could not be decoded because the extensible match component \
|
starting at position %d did not have a colon to denote the end of the \
|
attribute type name
|
MILD_ERR_SEARCH_FILTER_INVALID_FILTER_TYPE_153=Unable to determine whether \
|
entry "%s" matches filter "%s" because it contained an unknown filter type %s
|
MILD_ERR_SEARCH_FILTER_INVALID_RESULT_TYPE_154=Unable to determine whether \
|
entry "%s" matches filter "%s" because the internal check returned an unknown \
|
result type "%s"
|
MILD_ERR_SEARCH_FILTER_COMPOUND_COMPONENTS_NULL_155=Unable to determine \
|
whether entry "%s" matches filter "%s" because the set of filter components \
|
for an %s component was NULL
|
MILD_ERR_SEARCH_FILTER_NESTED_TOO_DEEP_156=Unable to determine whether entry \
|
"%s" matches filter "%s" because the filter was nested beyond the maximum \
|
allowed depth of 100 levels
|
MILD_ERR_SEARCH_FILTER_NOT_COMPONENT_NULL_157=Unable to determine whether \
|
entry "%s" matches filter "%s" because the NOT filter component did not \
|
include a subcomponent
|
MILD_ERR_SEARCH_FILTER_EQUALITY_NO_ATTRIBUTE_TYPE_158=Unable to determine \
|
whether entry "%s" matches filter "%s" because an equality component had a \
|
NULL attribute type
|
MILD_ERR_SEARCH_FILTER_EQUALITY_NO_ASSERTION_VALUE_159=Unable to determine \
|
whether entry "%s" matches filter "%s" because an equality component for \
|
attribute %s had a NULL assertion value
|
MILD_ERR_SEARCH_FILTER_SUBSTRING_NO_ATTRIBUTE_TYPE_160=Unable to determine \
|
whether entry "%s" matches filter "%s" because a substring component had a \
|
NULL attribute type
|
MILD_ERR_SEARCH_FILTER_SUBSTRING_NO_SUBSTRING_COMPONENTS_161=Unable to \
|
determine whether entry "%s" matches filter "%s" because a substring \
|
component for attribute %s did not have any subInitial, subAny, or subFinal \
|
elements
|
MILD_ERR_SEARCH_FILTER_GREATER_OR_EQUAL_NO_ATTRIBUTE_TYPE_162=Unable to \
|
determine whether entry "%s" matches filter "%s" because a greater-or-equal \
|
component had a NULL attribute type
|
MILD_ERR_SEARCH_FILTER_GREATER_OR_EQUAL_NO_VALUE_163=Unable to determine \
|
whether entry "%s" matches filter "%s" because a greater-or-equal component \
|
for attribute %s had a NULL assertion value
|
MILD_ERR_SEARCH_FILTER_LESS_OR_EQUAL_NO_ATTRIBUTE_TYPE_164=Unable to \
|
determine whether entry "%s" matches filter "%s" because a less-or-equal \
|
component had a NULL attribute type
|
MILD_ERR_SEARCH_FILTER_LESS_OR_EQUAL_NO_ASSERTION_VALUE_165=Unable to \
|
determine whether entry "%s" matches filter "%s" because a less-or-equal \
|
component for attribute %s had a NULL assertion value
|
MILD_ERR_SEARCH_FILTER_PRESENCE_NO_ATTRIBUTE_TYPE_166=Unable to determine \
|
whether entry "%s" matches filter "%s" because a presence component had a \
|
NULL attribute type
|
MILD_ERR_SEARCH_FILTER_APPROXIMATE_NO_ATTRIBUTE_TYPE_167=Unable to determine \
|
whether entry "%s" matches filter "%s" because an approximate component had a \
|
NULL attribute type
|
MILD_ERR_SEARCH_FILTER_APPROXIMATE_NO_ASSERTION_VALUE_168=Unable to determine \
|
whether entry "%s" matches filter "%s" because an approximate component for \
|
attribute %s had a NULL assertion value
|
MILD_ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_ASSERTION_VALUE_169=Unable to \
|
determine whether entry "%s" matches filter "%s" because a contained \
|
extensible match filter did not have an assertion value
|
MILD_ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_RULE_OR_TYPE_170=Unable to \
|
determine whether entry "%s" matches filter "%s" because a contained \
|
extensible match filter did not have either an attribute type or a matching \
|
rule ID
|
MILD_ERR_RDN_DECODE_NULL_171=Unable to decode the provided string as a \
|
relative distinguished name because the provided string was empty or null
|
MILD_ERR_RDN_END_WITH_ATTR_NAME_172=Unable to decode the provided string "%s" \
|
as a relative distinguished name because the string ended with an attribute \
|
type name (%s)
|
MILD_ERR_RDN_NO_EQUAL_173=Unable to decode the provided string "%s" as a \
|
relative distinguished name because the first non-blank character after the \
|
attribute type %s was not an equal sign (character read was %c)
|
MILD_ERR_RDN_UNEXPECTED_COMMA_174=Unable to decode the provided string "%s" \
|
as a relative distinguished name because it contained an unexpected plus, \
|
comma, or semicolon at position %d, which is not allowed in an RDN
|
MILD_ERR_RDN_ILLEGAL_CHARACTER_175=Unable to decode the provided string "%s" \
|
as a relative distinguished name because an illegal character %c was found at \
|
position %d, where either the end of the string or a '+' sign were expected
|
FATAL_ERR_CANNOT_CREATE_WORK_QUEUE_176=An error occurred while trying to \
|
create the Directory Server work queue: %s. This is an unrecoverable error \
|
and the startup process will not be able to continue
|
SEVERE_ERR_CANNOT_REGISTER_DUPLICATE_SUFFIX_180=The suffix "%s" is already \
|
registered with the Directory Server with a backend of type %s
|
SEVERE_ERR_CANNOT_REGISTER_DUPLICATE_SUBSUFFIX_181=The suffix "%s" is already \
|
registered with the Directory Server as a sub-suffix of the backend for \
|
suffix "%s"
|
SEVERE_ERR_CANNOT_REGISTER_PRIVATE_SUFFIX_BELOW_USER_PARENT_182=The private \
|
suffix "%s" is below a non-private suffix defined with a base DN of "%s". A \
|
private sub-suffix may not exist below a non-private suffix
|
SEVERE_ERR_CANNOT_GET_ROOT_DSE_CONFIG_ENTRY_183=An error occurred while \
|
trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) \
|
from the Directory Server configuration: %s
|
MILD_ERR_SCHEMA_CONFLICTING_ATTRIBUTE_OID_184=Unable to register attribute \
|
type %s with the server schema because its OID %s conflicts with the OID of \
|
an existing attribute type %s
|
MILD_ERR_SCHEMA_CONFLICTING_ATTRIBUTE_NAME_185=Unable to register attribute \
|
type %s with the server schema because its name %s conflicts with the name of \
|
an existing attribute type %s
|
MILD_ERR_SCHEMA_CONFLICTING_OBJECTCLASS_OID_186=Unable to register \
|
objectclass %s with the server schema because its OID %s conflicts with the \
|
OID of an existing objectclass %s
|
MILD_ERR_SCHEMA_CONFLICTING_OBJECTCLASS_NAME_187=Unable to register \
|
objectclass %s with the server schema because its name %s conflicts with the \
|
name of an existing objectclass %s
|
MILD_ERR_SCHEMA_CONFLICTING_SYNTAX_OID_188=Unable to register attribute \
|
syntax %s with the server schema because its OID %s conflicts with the OID of \
|
an existing syntax %s
|
MILD_ERR_SCHEMA_CONFLICTING_MR_OID_189=Unable to register matching rule %s \
|
with the server schema because its OID %s conflicts with the OID of an \
|
existing matching rule %s
|
MILD_ERR_SCHEMA_CONFLICTING_MR_NAME_190=Unable to register matching rule %s \
|
with the server schema because its name %s conflicts with the name of an \
|
existing matching rule %s
|
MILD_ERR_SCHEMA_CONFLICTING_MATCHING_RULE_USE_191=Unable to register matching \
|
rule use %s with the server schema because its matching rule %s conflicts \
|
with the matching rule for an existing matching rule use %s
|
MILD_ERR_SCHEMA_CONFLICTING_DIT_CONTENT_RULE_192=Unable to register DIT \
|
content rule %s with the server schema because its structural objectclass %s \
|
conflicts with the structural objectclass for an existing DIT content rule %s
|
MILD_ERR_SCHEMA_CONFLICTING_DIT_STRUCTURE_RULE_NAME_FORM_193=Unable to \
|
register DIT structure rule %s with the server schema because its name form \
|
%s conflicts with the name form for an existing DIT structure rule %s
|
MILD_ERR_SCHEMA_CONFLICTING_DIT_STRUCTURE_RULE_ID_194=Unable to register DIT \
|
structure rule %s with the server schema because its rule ID %d conflicts \
|
with the rule ID for an existing DIT structure rule %s
|
MILD_ERR_SCHEMA_CONFLICTING_NAME_FORM_OC_195=Unable to register name form %s \
|
with the server schema because its structural objectclass %s conflicts with \
|
the structural objectclass for an existing name form %s
|
MILD_ERR_SCHEMA_CONFLICTING_NAME_FORM_OID_196=Unable to register name form %s \
|
with the server schema because its OID %s conflicts with the OID for an \
|
existing name form %s
|
MILD_ERR_SCHEMA_CONFLICTING_NAME_FORM_NAME_197=Unable to register name form \
|
%s with the server schema because its name %s conflicts with the name for an \
|
existing name form %s
|
MILD_ERR_ENTRY_SCHEMA_MULTIPLE_STRUCTURAL_CLASSES_198=Entry %s violates the \
|
Directory Server schema configuration because it includes multiple \
|
conflicting structural objectclasses %s and %s. Only a single structural \
|
objectclass is allowed in an entry
|
MILD_ERR_ENTRY_SCHEMA_NO_STRUCTURAL_CLASS_199=Entry %s violates the Directory \
|
Server schema configuration because it does not include a structural \
|
objectclass. All entries must contain a structural objectclass
|
SEVERE_WARN_ADD_OP_INVALID_SYNTAX_200=Entry "%s" contains a value "%s" for \
|
attribute %s that is invalid according to the syntax for that attribute: %s
|
SEVERE_WARN_COMPARE_OP_NO_SUCH_ATTR_201=Entry "%s" does not contain any \
|
values for attribute "%s"
|
SEVERE_WARN_COMPARE_OP_NO_SUCH_ATTR_WITH_OPTIONS_202=Entry "%s" does not \
|
contain any values for attribute "%s" with the specified set of options
|
NOTICE_SERVER_STOPPED_203=The Directory Server is now stopped
|
INFO_WORKER_STOPPED_BY_REDUCED_THREADNUMBER_204=%s has been stopped because \
|
the total number of worker threads in the Directory Server was reduced
|
MILD_ERR_ENTRY_SCHEMA_ATTR_SINGLE_VALUED_205=Entry %s violates the Directory \
|
Server schema configuration because it includes multiple values for attribute \
|
%s, which is defined as a single-valued attribute
|
MILD_ERR_ENTRY_SCHEMA_RDN_MISSING_REQUIRED_ATTR_206=Entry %s violates the \
|
Directory Server schema configuration because its RDN does not contain \
|
attribute %s that is required by name form %s
|
MILD_ERR_ENTRY_SCHEMA_RDN_DISALLOWED_ATTR_207=Entry %s violates the Directory \
|
Server schema configuration because its RDN contains attribute %s that is not \
|
allowed by name form %s
|
MILD_ERR_ENTRY_SCHEMA_MISSING_REQUIRED_ATTR_FOR_DCR_208=Entry %s violates the \
|
Directory Server schema configuration because it is missing attribute %s \
|
which is required by DIT content rule %s
|
MILD_ERR_ENTRY_SCHEMA_PROHIBITED_ATTR_FOR_DCR_209=Entry %s violates the \
|
Directory Server schema configuration because it contains attribute %s which \
|
is prohibited by DIT content rule %s
|
MILD_ERR_ENTRY_SCHEMA_DISALLOWED_USER_ATTR_FOR_DCR_210=Entry %s violates the \
|
Directory Server schema configuration because it includes attribute %s which \
|
is not in the list of allowed or required attributes for DIT content rule %s
|
MILD_ERR_ENTRY_SCHEMA_DISALLOWED_AUXILIARY_CLASS_211=Entry %s violates the \
|
Directory Server schema configuration because it includes auxiliary \
|
objectClass %s that is not allowed by DIT content rule %s
|
MILD_ERR_ENTRY_SCHEMA_DSR_COULD_NOT_LOCK_PARENT_212=The Directory Server was \
|
unable to evaluate entry %s to determine whether it was compliant with the \
|
DIT structure rule configuration because it was unable to obtain a read lock \
|
on parent entry %s
|
MILD_ERR_ENTRY_SCHEMA_DSR_NO_PARENT_ENTRY_213=The Directory Server was unable \
|
to evaluate entry %s to determine whether it was compliant with the DIT \
|
structure rule configuration because parent entry %s either does not exist or \
|
could not be retrieved
|
MILD_ERR_ENTRY_SCHEMA_DSR_NO_PARENT_OC_214=The Directory Server was unable to \
|
evaluate entry %s to determine whether it was compliant with the DIT rule \
|
configuration because the parent entry %s does not appear to contain a valid \
|
structural objectclass
|
MILD_ERR_ENTRY_SCHEMA_DSR_DISALLOWED_SUPERIOR_OC_215=Entry %s violates the \
|
Directory Server schema configuration because DIT structure rule %s does not \
|
allow entries of type %s to be placed immediately below entries of type %s
|
MILD_ERR_ENTRY_SCHEMA_COULD_NOT_CHECK_DSR_216=An unexpected error occurred \
|
while attempting to check entry %s against DIT structure rule %s: %s
|
INFO_CANCELED_BY_BIND_REQUEST_217=Processing on this operation has been \
|
canceled because the Directory Server received a bind request on this \
|
connection, which requires that all operations in progress to be abandoned
|
MILD_ERR_BIND_OPERATION_UNKNOWN_USER_218=Unable to bind to the Directory \
|
Server as user %s because no such user exists in the server
|
SEVERE_ERR_BIND_OPERATION_CANNOT_LOCK_USER_219=Unable to process the bind \
|
because the server was unable to obtain a read lock on the entry %s
|
FATAL_ERR_STARTUP_PLUGIN_ERROR_220=A fatal error occurred when executing one \
|
of the Directory Server startup plugins: %s (error ID %d). The Directory \
|
Server startup process has been aborted
|
MILD_ERR_BIND_OPERATION_NO_PASSWORD_221=Unable to bind to the Directory \
|
Server as user %s using simple authentication because that user does not have \
|
a password
|
MILD_ERR_BIND_OPERATION_UNKNOWN_SASL_MECHANISM_222=Unable to process the bind \
|
request because it attempted to use an unknown SASL mechanism %s that is not \
|
available in the Directory Server
|
MILD_ERR_ABANDON_OP_NO_SUCH_OPERATION_223=Unable to abandon the operation \
|
with message ID %d because no information is available about that operation. \
|
This could mean that the target operation has already completed or was never \
|
requested
|
SEVERE_ERR_CANCELED_BY_PREPARSE_DISCONNECT_224=The operation was canceled \
|
because the client connection was terminated by a pre-parse plugin
|
SEVERE_ERR_CANCELED_BY_PREOP_DISCONNECT_225=The operation was canceled \
|
because the client connection was terminated by a pre-operation plugin
|
SEVERE_ERR_CANCELED_BY_POSTOP_DISCONNECT_226=The operation was canceled \
|
because the client connection was terminated by a post-operation plugin
|
SEVERE_ERR_COMPARE_CANNOT_LOCK_ENTRY_227=The Directory Server was unable to \
|
obtain a read lock on entry %s after multiple attempts. Processing on this \
|
operation cannot continue
|
MILD_ERR_COMPARE_NO_SUCH_ENTRY_228=The specified entry %s does not exist in \
|
the Directory Server
|
INFO_CANCELED_BY_ABANDON_REQUEST_229=The operation was canceled because the \
|
client issued an abandon request (message ID %d) for this operation
|
MILD_ERR_ADD_CANNOT_ADD_ROOT_DSE_230=The provided entry cannot be added \
|
because it contains a null DN. This DN is reserved for the root DSE, and \
|
that entry may not be added over protocol
|
MILD_ERR_ADD_ENTRY_NOT_SUFFIX_231=The provided entry %s cannot be added \
|
because it does not have a parent and is not defined as one of the suffixes \
|
within the Directory Server
|
SEVERE_ERR_ADD_CANNOT_LOCK_PARENT_232=Entry %s cannot be added because the \
|
server failed to obtain a read lock on the parent entry %s after multiple \
|
attempts
|
MILD_ERR_ADD_NO_PARENT_233=Entry %s cannot be added because its parent entry \
|
%s does not exist in the server
|
SEVERE_ERR_ADD_CANNOT_LOCK_ENTRY_234=Entry %s cannot be added because the \
|
server failed to obtain a write lock for this entry after multiple attempts
|
SEVERE_ERR_DELETE_CANNOT_LOCK_ENTRY_235=Entry %s cannot be removed because \
|
the server failed to obtain a write lock for this entry after multiple \
|
attempts
|
SEVERE_ERR_CANCELED_BY_SEARCH_ENTRY_DISCONNECT_236=The operation was canceled \
|
because the client connection was terminated by a search result entry plugin \
|
working on entry %s
|
SEVERE_ERR_CANCELED_BY_SEARCH_REF_DISCONNECT_237=The operation was canceled \
|
because the client connection was terminated by a search result reference \
|
plugin working on referral %s
|
MILD_ERR_SEARCH_TIME_LIMIT_EXCEEDED_238=The maximum time limit of %d seconds \
|
for processing this search operation has expired
|
MILD_ERR_SEARCH_SIZE_LIMIT_EXCEEDED_239=This search operation has sent the \
|
maximum of %d entries to the client
|
MILD_ERR_SEARCH_BASE_DOESNT_EXIST_240=The entry %s specified as the search \
|
base does not exist in the Directory Server
|
MILD_ERR_DELETE_NO_SUCH_ENTRY_241=Entry %s does not exist in the Directory \
|
Server
|
MILD_ERR_DELETE_HAS_SUB_BACKEND_242=Entry %s cannot be removed because the \
|
backend that should contain that entry has a subordinate backend with a base \
|
DN of %s that is below the target DN
|
MILD_ERR_MODDN_NO_PARENT_243=A modify DN operation cannot be performed on \
|
entry %s because the new RDN would not have a parent DN
|
MILD_ERR_MODDN_NO_BACKEND_FOR_CURRENT_ENTRY_244=The modify DN operation for \
|
entry %s cannot be performed because no backend is registered to handle that \
|
DN
|
MILD_ERR_MODDN_NO_BACKEND_FOR_NEW_ENTRY_245=The modify DN operation for entry \
|
%s cannot be performed because no backend is registered to handle the new DN \
|
%s
|
MILD_ERR_MODDN_DIFFERENT_BACKENDS_246=The modify DN operation for entry %s \
|
cannot be performed because the backend holding the current entry is \
|
different from the backend used to handle the new DN %s. Modify DN \
|
operations may not span multiple backends
|
SEVERE_ERR_MODDN_CANNOT_LOCK_CURRENT_DN_247=The modify DN operation for entry \
|
%s cannot be performed because the server was unable to obtain a write lock \
|
for that DN
|
SEVERE_ERR_MODDN_EXCEPTION_LOCKING_NEW_DN_248=The modify DN operation for \
|
entry %s cannot be performed because an exception was caught while attempting \
|
to obtain a write lock for new DN %s: %s
|
SEVERE_ERR_MODDN_CANNOT_LOCK_NEW_DN_249=The modify DN operation for entry %s \
|
cannot be performed because the server was unable to obtain a write lock for \
|
the new DN %s
|
MILD_ERR_MODDN_NO_CURRENT_ENTRY_250=The modify DN operation for entry %s \
|
cannot be performed because that entry does not exist in the server
|
SEVERE_ERR_MODIFY_CANNOT_LOCK_ENTRY_251=Entry %s cannot be modified because \
|
the server failed to obtain a write lock for this entry after multiple \
|
attempts
|
MILD_ERR_MODIFY_NO_SUCH_ENTRY_252=Entry %s cannot be modified because no such \
|
entry exists in the server
|
MILD_ERR_MODIFY_ADD_NO_VALUES_253=Entry %s cannot be modified because the \
|
modification contained an add component for attribute %s but no values were \
|
provided
|
MILD_ERR_MODIFY_ADD_INVALID_SYNTAX_254=When attempting to modify entry %s to \
|
add one or more values for attribute %s, value "%s" was found to be invalid \
|
according to the associated syntax: %s
|
MILD_ERR_MODIFY_ADD_DUPLICATE_VALUE_255=Entry %s cannot be modified because \
|
it would have resulted in one or more duplicate values for attribute %s: %s
|
MILD_ERR_MODIFY_DELETE_RDN_ATTR_256=Entry %s cannot be modified because the \
|
change to attribute %s would have removed a value used in the RDN
|
MILD_ERR_MODIFY_DELETE_MISSING_VALUES_257=Entry %s cannot be modified because \
|
the attempt to update attribute %s would have removed one or more values from \
|
the attribute that were not present: %s
|
MILD_ERR_MODIFY_DELETE_NO_SUCH_ATTR_258=Entry %s cannot be modified because \
|
an attempt was made to remove one or more values from attribute %s but this \
|
attribute is not present in the entry
|
MILD_ERR_MODIFY_REPLACE_INVALID_SYNTAX_259=When attempting to modify entry %s \
|
to replace the set of values for attribute %s, value "%s" was found to be \
|
invalid according to the associated syntax: %s
|
MILD_ERR_MODIFY_INCREMENT_RDN_260=Entry %s cannot be modified because an \
|
attempt was made to increment the value of attribute %s which is used as an \
|
RDN attribute for the entry
|
MILD_ERR_MODIFY_INCREMENT_REQUIRES_VALUE_261=Entry %s cannot be modified \
|
because an attempt was made to increment the value of attribute %s but the \
|
request did not include a value for that attribute specifying the amount by \
|
which to increment the value
|
MILD_ERR_MODIFY_INCREMENT_REQUIRES_SINGLE_VALUE_262=Entry %s cannot be \
|
modified because an attempt was made to increment the value of attribute %s \
|
but the request contained multiple values, where only a single integer value \
|
is allowed
|
MILD_ERR_MODIFY_INCREMENT_PROVIDED_VALUE_NOT_INTEGER_263=Entry %s cannot be \
|
modified because an attempt was made to increment the value of attribute %s \
|
but the value "%s" contained in the request could not be parsed as an integer
|
MILD_ERR_MODIFY_INCREMENT_REQUIRES_EXISTING_VALUE_264=Entry %s cannot be \
|
modified because an attempt was made to increment the value of attribute %s \
|
but that attribute did not have any values in the target entry
|
MILD_ERR_MODIFY_INCREMENT_REQUIRES_INTEGER_VALUE_265=Entry %s cannot be \
|
modified because an attempt was made to increment the value of attribute %s \
|
but the value "%s" could not be parsed as an integer
|
MILD_ERR_MODIFY_VIOLATES_SCHEMA_266=Entry %s cannot not be modified because \
|
the resulting entry would have violated the server schema: %s
|
MILD_ERR_MODIFY_NO_BACKEND_FOR_ENTRY_267=Entry %s cannot be modified because \
|
there is no backend registered to handle operations for that entry
|
MILD_ERR_EXTENDED_NO_HANDLER_268=There is no extended operation handler \
|
registered with the Directory Server for handling extended operations with a \
|
request OID of %s
|
MILD_ERR_ENTRY_SCHEMA_UNKNOWN_OC_269=Entry %s violates the Directory Server \
|
schema configuration because it contains an unknown objectclass %s
|
MILD_ERR_SEARCH_BACKEND_EXCEPTION_270=An unexpected error was encountered \
|
while processing a search in one of the Directory Server backends: %s
|
MILD_ERR_MODDN_VIOLATES_SCHEMA_271=The modify DN operation for entry %s \
|
cannot be performed because the change would have violated the server schema: \
|
%s
|
INFO_CONNHANDLER_CLOSED_BY_SHUTDOWN_272=The Directory Server is shutting down
|
INFO_CONNHANDLER_CLOSED_BY_DISABLE_273=The connection handler that accepted \
|
this connection has been disabled
|
INFO_CONNHANDLER_CLOSED_BY_DELETE_274=The connection handler that accepted \
|
this connection has been removed from the server
|
MILD_ERR_ENTRY_SET_UNKNOWN_OC_275=Object class %s cannot be used in entry %s \
|
because that class is not defined in the Directory Server schema
|
MILD_ERR_ENTRY_ADD_UNKNOWN_OC_276=Object class %s cannot be added to entry %s \
|
because that class is not defined in the Directory Server schema
|
MILD_ERR_ENTRY_ADD_DUPLICATE_OC_277=Object class %s is already present in \
|
entry %s and cannot be added a second time
|
MILD_ERR_BIND_OPERATION_UNKNOWN_STORAGE_SCHEME_278=Password with unknown \
|
storage scheme %s included in user entry %s will be ignored
|
MILD_ERR_BIND_OPERATION_WRONG_PASSWORD_279=The password provided by the user \
|
did not match any password(s) stored in the user's entry
|
MILD_ERR_BIND_OPERATION_PASSWORD_VALIDATION_EXCEPTION_280=An unexpected error \
|
occurred while attempting to validate the provided password: %s
|
INFO_DSCORE_DESCRIPTION_CONFIG_CLASS_281=Fully-qualified name \
|
of the Java class to use as the Directory Server configuration handler
|
INFO_DSCORE_DESCRIPTION_CONFIG_FILE_282=Path to the file \
|
containing the information needed by the configuration handler to obtain the \
|
Directory Server configuration
|
INFO_DSCORE_DESCRIPTION_FULLVERSION_284=Display extended Directory Server \
|
version information
|
INFO_DSCORE_DESCRIPTION_SYSINFO_285=Display general system information
|
INFO_DSCORE_DESCRIPTION_DUMPMESSAGES_286=Dump a list of all defined messages
|
INFO_DSCORE_DESCRIPTION_USAGE_287=Display this usage information
|
FATAL_ERR_DSCORE_CANNOT_INITIALIZE_ARGS_288=An error occurred while \
|
attempting to initialize the command-line arguments: %s
|
FATAL_ERR_DSCORE_ERROR_PARSING_ARGS_289=An error occurred while attempting to \
|
parse the provided set of command line arguments: %s
|
FATAL_ERR_DSCORE_CANNOT_BOOTSTRAP_290=An error occurred while attempting to \
|
bootstrap the Directory Server: %s
|
FATAL_ERR_DSCORE_CANNOT_START_291=An error occurred while trying to start the \
|
Directory Server: %s
|
SEVERE_ERR_BACKUPINFO_NO_DELIMITER_292=The line "%s" associated with the \
|
backup information in directory %s could not be parsed because it did not \
|
contain an equal sign to delimit the property name from the value
|
SEVERE_ERR_BACKUPINFO_NO_NAME_293=The line "%s" associated with the backup \
|
information in directory %s could not be parsed because it did not include a \
|
property name
|
SEVERE_ERR_BACKUPINFO_MULTIPLE_BACKUP_IDS_294=The backup information \
|
structure in directory %s could not be parsed because it contained multiple \
|
backup IDs (%s and %s)
|
SEVERE_ERR_BACKUPINFO_UNKNOWN_PROPERTY_295=The backup information structure \
|
in directory %s could not be parsed because it contained an unknown property \
|
%s with value %s
|
SEVERE_ERR_BACKUPINFO_CANNOT_DECODE_296=An unexpected error occurred while \
|
trying to decode a backup information structure in directory %s: %s
|
SEVERE_ERR_BACKUPINFO_NO_BACKUP_ID_297=Unable to decode a backup information \
|
structure in directory %s because the structure did not include a backup ID
|
SEVERE_ERR_BACKUPINFO_NO_BACKUP_DATE_298=The backup information structure \
|
with backup ID %s in directory %s was not valid because it did not contain \
|
the backup date
|
SEVERE_ERR_BACKUPDIRECTORY_ADD_DUPLICATE_ID_299=Cannot add a backup with ID \
|
%s to backup directory %s because another backup already exists with that ID
|
SEVERE_ERR_BACKUPDIRECTORY_NO_SUCH_BACKUP_300=Cannot remove backup %s from \
|
backup directory %s because no backup with that ID exists in that directory
|
SEVERE_ERR_BACKUPDIRECTORY_UNRESOLVED_DEPENDENCY_301=Cannot remove backup %s \
|
from backup directory %s because it is listed as a dependency for backup %s
|
SEVERE_ERR_BACKUPDIRECTORY_CANNOT_CREATE_DIRECTORY_302=Backup directory %s \
|
does not exist and an error occurred while attempting to create it: %s
|
SEVERE_ERR_BACKUPDIRECTORY_NOT_DIRECTORY_303=The path %s specifies as a \
|
backup directory exists but does not reference a directory
|
SEVERE_ERR_BACKUPDIRECTORY_CANNOT_DELETE_SAVED_DESCRIPTOR_304=An error \
|
occurred while trying to remove saved backup descriptor file %s: %s. The \
|
new backup descriptor has been written to %s but will not be used until it is \
|
manually renamed to %s
|
SEVERE_ERR_BACKUPDIRECTORY_CANNOT_RENAME_CURRENT_DESCRIPTOR_305=An error \
|
occurred while trying to rename the current backup descriptor file %s to %s: \
|
%s. The new backup descriptor has been written to %s but will not be used \
|
until it is manually renamed to %s
|
SEVERE_ERR_BACKUPDIRECTORY_CANNOT_RENAME_NEW_DESCRIPTOR_306=An error occurred \
|
while trying to rename the new backup descriptor file %s to %s: %s. The new \
|
backup descriptor will not be used until it is manually renamed
|
SEVERE_ERR_BACKUPDIRECTORY_NO_DESCRIPTOR_FILE_307=No backup directory \
|
descriptor file was found at %s
|
SEVERE_ERR_BACKUPDIRECTORY_CANNOT_READ_CONFIG_ENTRY_DN_308=The backup \
|
descriptor file %s is invalid because the first line should have contained \
|
the DN of the backend configuration entry but was blank
|
SEVERE_ERR_BACKUPDIRECTORY_FIRST_LINE_NOT_DN_309=The backup descriptor file \
|
%s is invalid because the first line of the file was "%s", but the DN of the \
|
backend configuration entry was expected
|
SEVERE_ERR_BACKUPDIRECTORY_CANNOT_DECODE_DN_310=An error occurred while \
|
trying to decode the value "%s" read from the first line of %s as the DN of \
|
the backend configuration entry: %s
|
MILD_ERR_FILELOCKER_LOCK_SHARED_REJECTED_BY_EXCLUSIVE_311=The attempt to \
|
obtain a shared lock on file %s was rejected because an exclusive lock was \
|
already held on that file
|
MILD_ERR_FILELOCKER_LOCK_SHARED_FAILED_CREATE_312=The attempt to obtain a \
|
shared lock on file %s was rejected because the attempt to create the lock \
|
file failed: %s
|
MILD_ERR_FILELOCKER_LOCK_SHARED_FAILED_OPEN_313=The attempt to obtain a \
|
shared lock on file %s was rejected because the attempt to open the lock file \
|
failed: %s
|
MILD_ERR_FILELOCKER_LOCK_SHARED_FAILED_LOCK_314=The attempt to obtain a \
|
shared lock on file %s was rejected because an error occurred while \
|
attempting to acquire the lock: %s
|
MILD_ERR_FILELOCKER_LOCK_SHARED_NOT_GRANTED_315=The shared lock requested for \
|
file %s was not granted, which indicates that another process already holds \
|
an exclusive lock on that file
|
MILD_ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_EXCLUSIVE_316=The attempt to \
|
obtain an exclusive lock on file %s was rejected because an exclusive lock \
|
was already held on that file
|
MILD_ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_SHARED_317=The attempt to \
|
obtain an exclusive lock on file %s was rejected because a shared lock was \
|
already held on that file
|
MILD_ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_CREATE_318=The attempt to obtain an \
|
exclusive lock on file %s was rejected because the attempt to create the lock \
|
file failed: %s
|
MILD_ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_OPEN_319=The attempt to obtain an \
|
exclusive lock on file %s was rejected because the attempt to open the lock \
|
file failed: %s
|
MILD_ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_LOCK_320=The attempt to obtain an \
|
exclusive lock on file %s was rejected because an error occurred while \
|
attempting to acquire the lock: %s
|
MILD_ERR_FILELOCKER_LOCK_EXCLUSIVE_NOT_GRANTED_321=The exclusive lock \
|
requested for file %s was not granted, which indicates that another process \
|
already holds a shared or exclusive lock on that file
|
MILD_ERR_FILELOCKER_UNLOCK_EXCLUSIVE_FAILED_RELEASE_322=The attempt to \
|
release the exclusive lock held on %s failed: %s
|
MILD_ERR_FILELOCKER_UNLOCK_SHARED_FAILED_RELEASE_323=The attempt to release \
|
the shared lock held on %s failed: %s
|
MILD_ERR_FILELOCKER_UNLOCK_UNKNOWN_FILE_324=The attempt to release the lock \
|
held on %s failed because no record of a lock on that file was found
|
INFO_RESULT_CLIENT_SIDE_SERVER_DOWN_325=Server Connection Closed
|
INFO_RESULT_CLIENT_SIDE_LOCAL_ERROR_326=Local Error
|
INFO_RESULT_CLIENT_SIDE_ENCODING_ERROR_327=Encoding Error
|
INFO_RESULT_CLIENT_SIDE_DECODING_ERROR_328=Decoding Error
|
INFO_RESULT_CLIENT_SIDE_TIMEOUT_329=Client-Side Timeout
|
INFO_RESULT_CLIENT_SIDE_AUTH_UNKNOWN_330=Unknown Authentication Mechanism
|
INFO_RESULT_CLIENT_SIDE_FILTER_ERROR_331=Filter Error
|
INFO_RESULT_CLIENT_SIDE_USER_CANCELLED_332=Cancelled by User
|
INFO_RESULT_CLIENT_SIDE_PARAM_ERROR_333=Parameter Error
|
INFO_RESULT_CLIENT_SIDE_NO_MEMORY_334=Out of Memory
|
INFO_RESULT_CLIENT_SIDE_CONNECT_ERROR_335=Connect Error
|
INFO_RESULT_CLIENT_SIDE_NOT_SUPPORTED_336=Operation Not Supported
|
INFO_RESULT_CLIENT_SIDE_CONTROL_NOT_FOUND_337=Control Not Found
|
INFO_RESULT_CLIENT_SIDE_NO_RESULTS_RETURNED_338=No Results Returned
|
INFO_RESULT_CLIENT_SIDE_MORE_RESULTS_TO_RETURN_339=More Results to Return
|
INFO_RESULT_CLIENT_SIDE_CLIENT_LOOP_340=Referral Loop Detected
|
INFO_RESULT_CLIENT_SIDE_REFERRAL_LIMIT_EXCEEDED_341=Referral Hop Limit \
|
Exceeded
|
SEVERE_WARN_SHUTDOWN_CANNOT_RELEASE_SHARED_BACKEND_LOCK_342=An error occurred \
|
while attempting to release a shared lock for backend %s: %s. This lock \
|
should be automatically cleaned when the Directory Server process exits, so \
|
no additional action should be necessary
|
FATAL_ERR_CANNOT_ACQUIRE_EXCLUSIVE_SERVER_LOCK_343=The Directory Server could \
|
not acquire an exclusive lock on file %s: %s. This generally means that \
|
another instance of this server is already running
|
INFO_ERROR_CATEGORY_TASK_345=task
|
MILD_ERR_MODIFY_ATTR_IS_NO_USER_MOD_346=Entry %s cannot be modified because \
|
the modification attempted to update attribute %s which is defined as \
|
NO-USER-MODIFICATION in the server schema
|
MILD_ERR_ADD_ATTR_IS_NO_USER_MOD_347=Entry %s cannot be added because it \
|
includes attribute %s which is defined as NO-USER-MODIFICATION in the server \
|
schema
|
MILD_ERR_MODDN_OLD_RDN_ATTR_IS_NO_USER_MOD_348=Entry %s cannot be renamed \
|
because the current DN includes attribute %s which is defined as \
|
NO-USER-MODIFICATION in the server schema and the deleteOldRDN flag was set \
|
in the modify DN request
|
MILD_ERR_MODDN_NEW_RDN_ATTR_IS_NO_USER_MOD_349=Entry %s cannot be renamed \
|
because the new RDN includes attribute %s which is defined as \
|
NO-USER-MODIFICATION in the server schema, and the target value for that \
|
attribute is not already included in the entry
|
MILD_ERR_MODDN_PREOP_INCREMENT_NO_ATTR_350=The modify DN operation for entry \
|
%s cannot be performed because a pre-operation plugin attempted to increment \
|
attribute %s but that attribute does not exist in the target entry
|
MILD_ERR_MODDN_PREOP_INCREMENT_MULTIPLE_VALUES_351=The modify DN operation \
|
for entry %s cannot be performed because a pre-operation plugin attempted to \
|
increment attribute %s but that attribute has multiple values in the target \
|
entry
|
MILD_ERR_MODDN_PREOP_INCREMENT_VALUE_NOT_INTEGER_352=The modify DN operation \
|
for entry %s cannot be performed because a pre-operation plugin attempted to \
|
increment attribute %s but the value of that attribute is not an integer
|
MILD_ERR_MODDN_PREOP_INCREMENT_NO_AMOUNT_353=The modify DN operation for \
|
entry %s cannot be performed because a pre-operation plugin attempted to \
|
increment attribute %s but no increment amount was provided
|
MILD_ERR_MODDN_PREOP_INCREMENT_MULTIPLE_AMOUNTS_354=The modify DN operation \
|
for entry %s cannot be performed because a pre-operation plugin attempted to \
|
increment attribute %s but multiple increment amount values were provided
|
MILD_ERR_MODDN_PREOP_INCREMENT_AMOUNT_NOT_INTEGER_355=The modify DN operation \
|
for entry %s cannot be performed because a pre-operation plugin attempted to \
|
increment attribute %s but the increment amount value was not an integer
|
MILD_ERR_MODDN_PREOP_VIOLATES_SCHEMA_356=The modify DN operation for entry %s \
|
cannot be performed because a pre-operation plugin modified the entry in a \
|
way that caused it to violate the server schema: %s
|
MILD_ERR_MODIFY_ASSERTION_FAILED_357=Entry %s cannot be modified because the \
|
request contained an LDAP assertion control and the associated filter did not \
|
match the contents of the that entry
|
MILD_ERR_MODIFY_CANNOT_PROCESS_ASSERTION_FILTER_358=Entry %s cannot be \
|
modified because the request contained an LDAP assertion control, but an \
|
error occurred while attempting to compare the target entry against the \
|
filter contained in that control: %s
|
MILD_ERR_MODIFY_UNSUPPORTED_CRITICAL_CONTROL_359=Entry %s cannot be modified \
|
because the request contained a critical control with OID %s that is not \
|
supported by the Directory Server for this type of operation
|
MILD_ERR_DELETE_CANNOT_GET_ENTRY_FOR_ASSERTION_360=Entry %s cannot be removed \
|
because the delete request contains an LDAP assertion control and an error \
|
occurred while trying to retrieve the target entry to compare it against the \
|
associated filter: %s
|
MILD_ERR_DELETE_NO_SUCH_ENTRY_FOR_ASSERTION_361=Entry %s cannot be removed \
|
because it was determined that the target entry does not exist while \
|
attempting to process it against the LDAP assertion control contained in the \
|
request
|
MILD_ERR_DELETE_ASSERTION_FAILED_362=Entry %s cannot be removed because the \
|
request contained an LDAP assertion control and the associated filter did not \
|
match the contents of the that entry
|
MILD_ERR_DELETE_CANNOT_PROCESS_ASSERTION_FILTER_363=Entry %s cannot be \
|
removed because the request contained an LDAP assertion control, but an error \
|
occurred while attempting to compare the target entry against the filter \
|
contained in that control: %s
|
MILD_ERR_DELETE_UNSUPPORTED_CRITICAL_CONTROL_364=Entry %s cannot be removed \
|
because the request contained a critical control with OID %s that is not \
|
supported by the Directory Server for this type of operation
|
MILD_ERR_MODDN_ASSERTION_FAILED_365=Entry %s cannot be renamed because the \
|
request contained an LDAP assertion control and the associated filter did not \
|
match the contents of the that entry
|
MILD_ERR_MODDN_CANNOT_PROCESS_ASSERTION_FILTER_366=Entry %s cannot be renamed \
|
because the request contained an LDAP assertion control, but an error \
|
occurred while attempting to compare the target entry against the filter \
|
contained in that control: %s
|
MILD_ERR_MODDN_UNSUPPORTED_CRITICAL_CONTROL_367=Entry %s cannot be renamed \
|
because the request contained a critical control with OID %s that is not \
|
supported by the Directory Server for this type of operation
|
MILD_ERR_ADD_ASSERTION_FAILED_368=Entry %s cannot be added because the \
|
request contained an LDAP assertion control and the associated filter did not \
|
match the contents of the provided entry
|
MILD_ERR_ADD_CANNOT_PROCESS_ASSERTION_FILTER_369=Entry %s cannot be added \
|
because the request contained an LDAP assertion control, but an error \
|
occurred while attempting to compare the provided entry against the filter \
|
contained in that control: %s
|
MILD_ERR_ADD_UNSUPPORTED_CRITICAL_CONTROL_370=Entry %s cannot be added \
|
because the request contained a critical control with OID %s that is not \
|
supported by the Directory Server for this type of operation
|
MILD_ERR_SEARCH_CANNOT_GET_ENTRY_FOR_ASSERTION_371=The search request cannot \
|
be processed because it contains an LDAP assertion control and an error \
|
occurred while trying to retrieve the base entry to compare it against the \
|
assertion filter: %s
|
MILD_ERR_SEARCH_NO_SUCH_ENTRY_FOR_ASSERTION_372=The search request cannot be \
|
processed because it contains an LDAP assertion control but the search base \
|
entry does not exist
|
MILD_ERR_SEARCH_ASSERTION_FAILED_373=The search request cannot be processed \
|
because it contains an LDAP assertion control and the assertion filter did \
|
not match the contents of the base entry
|
MILD_ERR_SEARCH_CANNOT_PROCESS_ASSERTION_FILTER_374=The search request cannot \
|
be processed because it contains an LDAP assertion control, but an error \
|
occurred while attempting to compare the base entry against the assertion \
|
filter: %s
|
MILD_ERR_SEARCH_UNSUPPORTED_CRITICAL_CONTROL_375=The search request cannot be \
|
processed because it contains a critical control with OID %s that is not \
|
supported by the Directory Server for this type of operation
|
MILD_ERR_COMPARE_ASSERTION_FAILED_376=Cannot perform the compare operation on \
|
entry %s because the request contained an LDAP assertion control and the \
|
associated filter did not match the contents of the that entry
|
MILD_ERR_COMPARE_CANNOT_PROCESS_ASSERTION_FILTER_377=Cannot perform the \
|
compare operation on entry %s because the request contained an LDAP assertion \
|
control, but an error occurred while attempting to compare the target entry \
|
against the filter contained in that control: %s
|
MILD_ERR_COMPARE_UNSUPPORTED_CRITICAL_CONTROL_378=Cannot perform the compare \
|
operation on entry %s because the request contained a critical control with \
|
OID %s that is not supported by the Directory Server for this type of \
|
operation
|
INFO_ADD_NOOP_379=The add operation was not actually performed in the \
|
Directory Server backend because the LDAP no-op control was present in the \
|
request
|
INFO_DELETE_NOOP_380=The delete operation was not actually performed in the \
|
Directory Server backend because the LDAP no-op control was present in the \
|
request
|
INFO_MODIFY_NOOP_381=The modify operation was not actually performed in the \
|
Directory Server backend because the LDAP no-op control was present in the \
|
request
|
INFO_MODDN_NOOP_382=The modify DN operation was not actually performed in the \
|
Directory Server backend because the LDAP no-op control was present in the \
|
request
|
MILD_ERR_DELETE_PREREAD_NO_ENTRY_383=Entry %s cannot be removed because it \
|
was determined that the target entry does not exist while attempting to \
|
process it against the LDAP pre-read request control
|
INFO_RESULT_AUTHORIZATION_DENIED_384=Authorization Denied
|
SEVERE_ERR_ADD_MISSING_RDN_ATTRIBUTE_385=Entry %s cannot be added because it \
|
is missing attribute %s that is contained in the entry's RDN. All attributes \
|
used in the RDN must also be provided in the attribute list for the entry
|
SEVERE_ERR_ADD_ERROR_NOTIFYING_CHANGE_LISTENER_386=An unexpected error \
|
occurred while notifying a change notification listener of an add operation: \
|
%s
|
SEVERE_ERR_ADD_ERROR_NOTIFYING_PERSISTENT_SEARCH_387=An unexpected error \
|
occurred while notifying persistent search %s of an add operation: %s. The \
|
persistent search has been terminated
|
SEVERE_ERR_DELETE_ERROR_NOTIFYING_CHANGE_LISTENER_388=An unexpected error \
|
occurred while notifying a change notification listener of a delete \
|
operation: %s
|
SEVERE_ERR_DELETE_ERROR_NOTIFYING_PERSISTENT_SEARCH_389=An unexpected error \
|
occurred while notifying persistent search %s of a delete operation: %s. \
|
The persistent search has been terminated
|
SEVERE_ERR_MODIFY_ERROR_NOTIFYING_CHANGE_LISTENER_390=An unexpected error \
|
occurred while notifying a change notification listener of a modify \
|
operation: %s
|
SEVERE_ERR_MODIFY_ERROR_NOTIFYING_PERSISTENT_SEARCH_391=An unexpected error \
|
occurred while notifying persistent search %s of a modify operation: %s. \
|
The persistent search has been terminated
|
SEVERE_ERR_MODDN_ERROR_NOTIFYING_CHANGE_LISTENER_392=An unexpected error \
|
occurred while notifying a change notification listener of a modify DN \
|
operation: %s
|
SEVERE_ERR_MODDN_ERROR_NOTIFYING_PERSISTENT_SEARCH_393=An unexpected error \
|
occurred while notifying persistent search %s of a modify DN operation: %s. \
|
The persistent search has been terminated
|
SEVERE_ERR_BIND_UNSUPPORTED_CRITICAL_CONTROL_394=Unable to process the bind \
|
request because it contained a control with OID %s that was marked critical \
|
but this control is not supported for the bind operation
|
SEVERE_WARN_BIND_MULTIPLE_USER_SIZE_LIMITS_395=There are multiple \
|
user-specific size limit values contained in user entry %s. The default \
|
server size limit will be used
|
SEVERE_WARN_BIND_CANNOT_PROCESS_USER_SIZE_LIMIT_396=The user-specific size \
|
limit value %s contained in user entry %s could not be parsed as an integer. \
|
The default server size limit will be used
|
SEVERE_WARN_BIND_MULTIPLE_USER_TIME_LIMITS_397=There are multiple \
|
user-specific time limit values contained in user entry %s. The default \
|
server time limit will be used
|
SEVERE_WARN_BIND_CANNOT_PROCESS_USER_TIME_LIMIT_398=The user-specific time \
|
limit value %s contained in user entry %s could not be parsed as an integer. \
|
The default server time limit will be used
|
INFO_RESULT_ASSERTION_FAILED_399=Assertion Failed
|
SEVERE_ERR_ADD_ENTRY_ALREADY_EXISTS_400=The entry %s cannot be added because \
|
an entry with that name already exists
|
SEVERE_ERR_ADD_SYNCH_PREOP_FAILED_401=An error occurred during preoperation \
|
synchronization processing for the add operation with connection ID %d and \
|
operation ID %d: %s
|
SEVERE_ERR_ADD_SYNCH_POSTOP_FAILED_402=An error occurred during postoperation \
|
synchronization processing for the add operation with connection ID %d and \
|
operation ID %d: %s
|
SEVERE_ERR_DELETE_SYNCH_PREOP_FAILED_403=An error occurred during \
|
preoperation synchronization processing for the delete operation with \
|
connection ID %d and operation ID %d: %s
|
SEVERE_ERR_DELETE_SYNCH_POSTOP_FAILED_404=An error occurred during \
|
postoperation synchronization processing for the delete operation with \
|
connection ID %d and operation ID %d: %s
|
SEVERE_ERR_MODIFY_SYNCH_PREOP_FAILED_405=An error occurred during \
|
preoperation synchronization processing for the modify operation with \
|
connection ID %d and operation ID %d: %s
|
SEVERE_ERR_MODIFY_SYNCH_POSTOP_FAILED_406=An error occurred during \
|
postoperation synchronization processing for the modify operation with \
|
connection ID %d and operation ID %d: %s
|
SEVERE_ERR_MODDN_SYNCH_PREOP_FAILED_407=An error occurred during preoperation \
|
synchronization processing for the modify DN operation with connection ID %d \
|
and operation ID %d: %s
|
SEVERE_ERR_MODDN_SYNCH_POSTOP_FAILED_408=An error occurred during \
|
postoperation synchronization processing for the modify DN operation with \
|
connection ID %d and operation ID %d: %s
|
SEVERE_ERR_ADD_SYNCH_CONFLICT_RESOLUTION_FAILED_409=An error occurred during \
|
conflict resolution synchronization processing for the add operation with \
|
connection ID %d and operation ID %d: %s
|
SEVERE_ERR_DELETE_SYNCH_CONFLICT_RESOLUTION_FAILED_410=An error occurred \
|
during conflict resolution synchronization processing for the delete \
|
operation with connection ID %d and operation ID %d: %s
|
SEVERE_ERR_MODIFY_SYNCH_CONFLICT_RESOLUTION_FAILED_411=An error occurred \
|
during conflict resolution synchronization processing for the modify \
|
operation with connection ID %d and operation ID %d: %s
|
SEVERE_ERR_MODDN_SYNCH_CONFLICT_RESOLUTION_FAILED_412=An error occurred \
|
during conflict resolution synchronization processing for the modify DN \
|
operation with connection ID %d and operation ID %d: %s
|
SEVERE_ERR_ADD_SERVER_READONLY_413=Unable to add entry %s because the \
|
Directory Server is configured in read-only mode
|
SEVERE_ERR_ADD_BACKEND_READONLY_414=Unable to add entry %s because the \
|
backend that should hold that entry is configured in read-only mode
|
SEVERE_ERR_DELETE_SERVER_READONLY_415=Unable to delete entry %s because the \
|
Directory Server is configured in read-only mode
|
SEVERE_ERR_DELETE_BACKEND_READONLY_416=Unable to delete entry %s because the \
|
backend that holds that entry is configured in read-only mode
|
SEVERE_ERR_MODIFY_SERVER_READONLY_417=Unable to modify entry %s because the \
|
Directory Server is configured in read-only mode
|
SEVERE_ERR_MODIFY_BACKEND_READONLY_418=Unable to modify entry %s because the \
|
backend that holds that entry is configured in read-only mode
|
SEVERE_ERR_MODDN_SERVER_READONLY_419=Unable to rename entry %s because the \
|
Directory Server is configured in read-only mode
|
SEVERE_ERR_MODDN_BACKEND_READONLY_420=Unable to rename entry %s because the \
|
backend that holds that entry is configured in read-only mode
|
SEVERE_ERR_BIND_DN_BUT_NO_PASSWORD_421=Unable to process the simple bind \
|
request because it contained a bind DN but no password, which is forbidden by \
|
the server configuration
|
SEVERE_ERR_PWPOLICY_NO_PASSWORD_ATTRIBUTE_422=The password policy \
|
configuration entry "%s" does not contain a value for attribute \
|
ds-cfg-password-attribute, which specifies the attribute to hold user \
|
passwords
|
SEVERE_ERR_PWPOLICY_NO_DEFAULT_STORAGE_SCHEMES_423=The password policy \
|
configuration entry "%s" does not contain any values for attribute \
|
ds-cfg-default-password-storage-scheme, which specifies the set of default \
|
password storage schemes
|
INFO_PWPOLICY_DESCRIPTION_PW_ATTR_424=Attribute type used to \
|
hold user passwords. This attribute type must be defined in the server \
|
schema. Changes to this configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_UNDEFINED_PASSWORD_ATTRIBUTE_425=The password policy \
|
definition contained in configuration entry "%s" is invalid because the \
|
specified password attribute "%s" is not defined in the server schema
|
SEVERE_ERR_PWPOLICY_INVALID_PASSWORD_ATTRIBUTE_SYNTAX_426=The password policy \
|
definition contained in configuration entry "%s" is invalid because the \
|
specified password attribute "%s" has a syntax OID of %s. The password \
|
attribute must have a syntax OID of either 1.3.6.1.4.1.26027.1.3.1 (for the \
|
user password syntax) or 1.3.6.1.4.1.4203.1.1.2 (for the authentication \
|
password syntax)
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PASSWORD_ATTRIBUTE_427=An error occurred \
|
while attempting to determine the value of attribute \
|
ds-cfg-password-attribute in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_DEFAULT_STORAGE_SCHEMES_428=Password \
|
storage scheme (or set of schemes) that will be used to encode clear-text \
|
passwords. If multiple default storage schemes are defined for a password \
|
policy, then the same password will be encoded using all of those schemes. \
|
Changes to this configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_NO_SUCH_DEFAULT_SCHEME_429=The password policy definition \
|
contained in configuration entry "%s" is invalid because it references a \
|
default password storage scheme "%s" that is not defined in the server \
|
configuration
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_DEFAULT_STORAGE_SCHEMES_430=An error \
|
occurred while attempting to determine the values for attribute \
|
ds-cfg-default-password-storage-scheme in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_DEPRECATED_STORAGE_SCHEMES_431=Password storage \
|
scheme (or set of schemes) that should be considered \
|
deprecated. If an authenticating user has a password encoded with one of \
|
these schemes, those passwords will be removed and replaced with passwords \
|
encoded using the default schemes. Changes to this configuration attribute \
|
will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_DEPRECATED_STORAGE_SCHEMES_432=An error \
|
occurred while attempting to determine the values for attribute \
|
ds-cfg-deprecated-password-storage-scheme in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_PASSWORD_VALIDATORS_433=DN(s) of the \
|
password validator(s) that should be used with the associated password \
|
storage scheme. Changes to this configuration attribute will take effect \
|
immediately
|
SEVERE_ERR_PWPOLICY_NO_SUCH_VALIDATOR_434=The password policy definition \
|
contained in configuration entry "%s" is invalid because it references a \
|
password validator "%s" that is not defined in the server configuration
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PASSWORD_VALIDATORS_435=An error \
|
occurred while attempting to determine the values for attribute \
|
ds-cfg-password-validator in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_NOTIFICATION_HANDLERS_436=DN(s) of \
|
the account status notification handler(s) that should be used with the \
|
associated password storage scheme. Changes to this configuration attribute \
|
will take effect immediately
|
SEVERE_ERR_PWPOLICY_NO_SUCH_NOTIFICATION_HANDLER_437=The password policy \
|
definition contained in configuration entry "%s" is invalid because it \
|
references account status notification handler "%s" that is not defined in \
|
the server configuration
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_NOTIFICATION_HANDLERS_438=An error \
|
occurred while attempting to determine the values for attribute \
|
ds-cfg-account-status-notification-handler in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_ALLOW_USER_PW_CHANGES_439=Indicates whether users \
|
will be allowed to change their own passwords. This check is made in \
|
addition to access control evaluation, and therefore both must allow the \
|
password change for it to occur. Changes to this configuration attribute \
|
will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_USER_PW_CHANGES_440=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-allow-user-password-changes in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_REQUIRE_CURRENT_PW_441=Indicates whether user \
|
password changes will be required to use the password modify extended \
|
operation and include the user's current password before the change will be \
|
allowed. Changes to this configuration attribute will take effect \
|
immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CURRENT_PW_442=An error occurred \
|
while attempting to determine the value for attribute \
|
ds-cfg-allow-user-password-changes in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_FORCE_CHANGE_ON_RESET_443=Indicates whether users \
|
will be forced to change their passwords if they are reset by an \
|
administrator. For this purpose, anyone with permission to change a given \
|
user's password other than that user will be considered an administrator. \
|
Changes to this configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_FORCE_CHANGE_ON_RESET_444=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-force-change-on-reset in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_SKIP_ADMIN_VALIDATION_445=Indicates whether \
|
passwords set by administrators (in add, modify, or password modify \
|
operations) will be allowed to bypass the password validation process that \
|
will be required for user password changes. Changes to this configuration \
|
attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_SKIP_ADMIN_VALIDATION_446=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-skip-validation-for-administrators in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_PASSWORD_GENERATOR_447=DN of the \
|
configuration entry that references the password generator for use with the \
|
associated password policy. This will be used in conjunction with the \
|
password modify extended operation to generate a new password for a user when \
|
none was provided in the request. Changes to this configuration attribute \
|
will take effect immediately
|
SEVERE_ERR_PWPOLICY_NO_SUCH_GENERATOR_448=The password policy definition \
|
contained in configuration entry "%s" is invalid because it references \
|
password generator "%s" that is not defined in the server configuration
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PASSWORD_GENERATOR_449=An error occurred \
|
while attempting to determine the value for attribute \
|
ds-cfg-password-generator in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_REQUIRE_SECURE_AUTH_450=Indicates whether users \
|
with the associated password policy will be required to authenticate in a \
|
secure manner. This could mean either using a secure communication channel \
|
between the client and the server, or using a SASL mechanism that does not \
|
expose the credentials. Changes to this configuration attribute will take \
|
effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_SECURE_AUTH_451=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-require-secure-authentication in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_REQUIRE_SECURE_CHANGES_452=Indicates whether users \
|
with the associated password policy will be required to change their password \
|
in a secure manner that does not expose the credentials. Changes to this \
|
configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_SECURE_CHANGES_453=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-require-secure-password-changes in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_ALLOW_PREENCODED_454=Indicates whether users will \
|
be allowed to change their passwords by providing a pre-encoded value. This \
|
can cause a security risk because the clear-text version of the password is \
|
not known and therefore validation checks cannot be applied to it. Changes \
|
to this configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_PREENCODED_455=An error occurred \
|
while attempting to determine the value for attribute \
|
ds-cfg-allow-pre-encoded-passwords in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_MIN_AGE_456=Minimum length of time \
|
that must pass after a password change before the user will be allowed to \
|
change the password again. The value of this attribute should be an integer \
|
followed by a unit of seconds, minutes, hours, days, or weeks. This setting \
|
can be used to prevent users from changing their passwords repeatedly over a \
|
short period of time to flush and old password from the history so that it \
|
may be re-used. Changes to this configuration attribute will take effect \
|
immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_MIN_AGE_457=An error occurred while \
|
attempting to determine the value for attribute ds-cfg-min-password-age \
|
in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_MAX_AGE_458=Maximum length of time \
|
that a user may continue using the same password before it must be changed \
|
(i.e., the password expiration interval). The value of this attribute should \
|
be an integer followed by a unit of seconds, minutes, hours, days, or weeks. \
|
A value of 0 seconds will disable password expiration. Changes to this \
|
configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_MAX_AGE_459=An error occurred while \
|
attempting to determine the value for attribute ds-cfg-max-password-age \
|
in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_MAX_RESET_AGE_460=Maximum length of \
|
time that users have to change passwords after they have been reset by an \
|
administrator before they become locked. The value of this attribute should \
|
be an integer followed by a unit of seconds, minutes, hours, days, or weeks. \
|
A value of 0 seconds will disable this feature. Changes to this \
|
configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_MAX_RESET_AGE_461=An error occurred \
|
while attempting to determine the value for attribute \
|
ds-cfg-max-password-reset-age in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_WARNING_INTERVAL_462=Maximum length \
|
of time before a user's password actually expires that the server will begin \
|
to include warning notifications in bind responses for that user. The value \
|
of this attribute should be an integer followed by a unit of seconds, \
|
minutes, hours, days, or weeks. A value of 0 seconds will disable the \
|
warning interval. Changes to this configuration attribute will take effect \
|
immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_WARNING_INTERVAL_463=An error occurred \
|
while attempting to determine the value for attribute \
|
ds-cfg-password-expiration-warning-interval in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_EXPIRE_WITHOUT_WARNING_464=Indicates whether the \
|
Directory Server should allow a user's password to expire even if that user \
|
has never seen an expiration warning notification. If this setting is \
|
enabled, then accounts will always be expired when the expiration time \
|
arrives. If it is disabled, then the user will always receive at least one \
|
warning notification, and the password expiration will be set to the warning \
|
time plus the warning interval. Changes to this configuration attribute will \
|
take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_EXPIRE_WITHOUT_WARNING_465=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-expire-passwords-without-warning in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_ALLOW_EXPIRED_CHANGES_466=Indicates whether a user \
|
whose password is expired will still be allowed to change that password using \
|
the password modify extended operation. Changes to this configuration \
|
attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_EXPIRED_CHANGES_467=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-allow-expired-password-changes in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_GRACE_LOGIN_COUNT_468=Number of grace \
|
logins that a user will be allowed after the account has expired to allow \
|
that user to choose a new password. A value of 0 indicates that no grace \
|
logins will be allowed. Changes to this configuration attribute will take \
|
effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_GRACE_LOGIN_COUNT_469=An error occurred \
|
while attempting to determine the value for attribute \
|
ds-cfg-grace-login-count in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_LOCKOUT_FAILURE_COUNT_470=Maximum \
|
number of authentication failures that a user should be allowed before the \
|
account is locked out. A value of 0 indicates that accounts should never be \
|
locked out due to failed attempts. changes to this configuration attribute \
|
will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LOCKOUT_FAILURE_COUNT_471=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-lockout-failure-count in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_LOCKOUT_DURATION_472=Length of time \
|
that an account should be locked after too many authentication failures. The \
|
value of this attribute should be an integer followed by a unit of seconds, \
|
minutes, hours, days, or weeks. A value of 0 seconds indicates that the \
|
account should remain locked until an administrator resets the password. \
|
Changes to this configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LOCKOUT_DURATION_473=An error occurred \
|
while attempting to determine the value for attribute ds-cfg-lockout-duration \
|
in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_FAILURE_EXPIRATION_474=Length of time \
|
that should pass before an authentication failure is no longer counted \
|
against a user for the purposes of account lockout. The value of this \
|
attribute should be an integer followed by a unit of seconds, minutes, hours, \
|
days, or weeks. A value of 0 seconds indicates that the authentication \
|
failures should never expire. The failure count will always be cleared upon \
|
a successful authentication. Changes to this configuration attribute will \
|
take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_FAILURE_EXPIRATION_475=An error occurred \
|
while attempting to determine the value for attribute \
|
ds-cfg-lockout-failure-expiration-interval in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_REQUIRE_CHANGE_BY_TIME_476=Time by \
|
which all users with the associated password policy must change their \
|
passwords. The value should be expressed in a generalized time format. If \
|
this time is equal to the current time or is in the past, then all users will \
|
be required to change their passwords immediately. The behavior of the \
|
server in this mode will be identical to the behavior observed when users are \
|
forced to change their passwords after an administrative reset. Changes to \
|
this configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CHANGE_BY_TIME_477=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-require-change-by-time in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_LAST_LOGIN_TIME_ATTR_478=Name or OID \
|
of the attribute type that should be used to hold the last login time for \
|
users with the associated password policy. This attribute type must be \
|
defined in the Directory Server schema and must either be defined as an \
|
operational attribute or must be allowed by the set of object classes for all \
|
users with the associated password policy. Changes to this configuration \
|
attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_UNDEFINED_LAST_LOGIN_TIME_ATTRIBUTE_479=The password \
|
policy definition contained in configuration entry "%s" is invalid because \
|
the specified last login time attribute "%s" is not defined in the server \
|
schema
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LAST_LOGIN_TIME_ATTR_480=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-last-login-time-attribute in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_LAST_LOGIN_TIME_FORMAT_481=Format \
|
string that should be used to generate the last login time value for users \
|
with the associated password policy. This format string should conform to \
|
the syntax described in the API documentation for the \
|
<CODE>java.text.SimpleDateFormat</CODE> class. Changes to this configuration \
|
attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_INVALID_LAST_LOGIN_TIME_FORMAT_482=The password policy \
|
definition contained in configuration entry "%s" is invalid because the \
|
specified last login time format "%s" is not a valid format string The last \
|
login time format string should conform to the syntax described in the API \
|
documentation for the <CODE>java.text.SimpleDateFormat</CODE> class
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LAST_LOGIN_TIME_FORMAT_483=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-last-login-time-format in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_PREVIOUS_LAST_LOGIN_TIME_FORMAT_484=Format \
|
string(s) that may have been used with the last login time at any \
|
point in the past for users associated with the password policy. These \
|
values are used to make it possible to parse previous values, but will not be \
|
used to set new values. These format strings should conform to the syntax \
|
described in the API documentation for the \
|
<CODE>java.text.SimpleDateFormat</CODE> class. Changes to this configuration \
|
attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_INVALID_PREVIOUS_LAST_LOGIN_TIME_FORMAT_485=The password \
|
policy definition contained in configuration entry "%s" is invalid because \
|
the specified previous last login time format "%s" is not a valid format \
|
string The previous last login time format strings should conform to the \
|
syntax described in the API documentation for the \
|
<CODE>java.text.SimpleDateFormat</CODE> class
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PREVIOUS_LAST_LOGIN_TIME_FORMAT_486=An \
|
error occurred while attempting to determine the values for attribute \
|
ds-cfg-previous-last-login-time-format in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_IDLE_LOCKOUT_INTERVAL_487=Maximum \
|
length of time that an account may remain idle (i.e., the associated user \
|
does not authenticate to the server) before that user is locked out. The \
|
value of this attribute should be an integer followed by a unit of seconds, \
|
minutes, hours, days, or weeks. A value of 0 seconds indicates that idle \
|
accounts should not automatically be locked out. This feature will only be \
|
available if the last login time is maintained. Changes to this \
|
configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_IDLE_LOCKOUT_INTERVAL_488=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-idle-lockout-interval in configuration entry %s: %s
|
INFO_PWPOLICY_UPDATED_POLICY_489=The password policy defined in configuration \
|
entry %s has been successfully updated
|
MILD_ERR_ADD_INVALID_PWPOLICY_DN_SYNTAX_490=Entry "%s" cannot be added \
|
because it contains an invalid password policy subentry DN: %s
|
MILD_ERR_ADD_NO_SUCH_PWPOLICY_491=Entry "%s" cannot be added because it \
|
references password policy subentry %s that does not exist or does not \
|
contain a valid password policy subentry definition
|
INFO_PWPOLICY_DESCRIPTION_FORCE_CHANGE_ON_ADD_492=Indicates whether users \
|
will be forced to change their passwords upon first authenticating to the \
|
Directory Server after their account has been created. Changes to this \
|
configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_FORCE_CHANGE_ON_ADD_493=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-force-change-on-add in configuration entry %s: %s
|
INFO_PWPOLICY_DESCRIPTION_ALLOW_MULTIPLE_PW_VALUES_494=Indicates whether user \
|
entries will be allowed to have multiple distinct values for the password \
|
attribute. This is potentially dangerous because many mechanisms used to \
|
change the password do not work well with such a configuration. If multiple \
|
password values are allowed, then any of them may be used to authenticate, \
|
and they will all be subject to the same policy constraints. Changes to this \
|
configuration attribute will take effect immediately
|
SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_MULTIPLE_PW_VALUES_495=An error \
|
occurred while attempting to determine the value for attribute \
|
ds-cfg-allow-multiple-password-values in configuration entry %s: %s
|
MILD_ERR_PWPOLICY_ATTRIBUTE_OPTIONS_NOT_ALLOWED_496=Attribute options are not \
|
allowed for the password attribute %s
|
MILD_ERR_PWPOLICY_MULTIPLE_PW_VALUES_NOT_ALLOWED_497=Only a single value may \
|
be provided for the password attribute %s
|
MILD_ERR_PWPOLICY_PREENCODED_NOT_ALLOWED_498=Pre-encoded passwords are not \
|
allowed for the password attribute %s
|
MILD_ERR_PWPOLICY_VALIDATION_FAILED_499=The password value for attribute %s \
|
was found to be unacceptable: %s
|
SEVERE_ERR_PWPOLICY_MUST_HAVE_WARNING_IF_NOT_EXPIRE_WITHOUT_WARNING_500=The \
|
password policy defined in configuration entry %s is configured to always \
|
send at least one warning notification before the password is expired, but no \
|
warning interval has been set. If configuration attribute \
|
ds-cfg-expire-passwords-without-warning is set to "false", then configuration \
|
attribute ds-cfg-password-expiration-warning-interval must have a positive \
|
value
|
MILD_ERR_ENQUEUE_BIND_IN_PROGRESS_501=A bind operation is currently in \
|
progress on the associated client connection. No other requests may be made \
|
on this client connection until the bind processing has completed
|
MILD_ERR_ENQUEUE_MUST_CHANGE_PASSWORD_502=You must change your password \
|
before you will be allowed to request any other operations
|
MILD_ERR_PWPSTATE_CANNOT_DECODE_SUBENTRY_VALUE_AS_DN_504=An error occurred \
|
while attempting to decode the ds-pwp-password-policy-dn value "%s" in user \
|
entry "%s" as a DN: %s
|
MILD_ERR_PWPSTATE_NO_SUCH_POLICY_505=User entry %s is configured to use a \
|
password policy subentry of %s but no such password policy has been defined \
|
in the server configuration
|
MILD_ERR_PWPSTATE_CANNOT_DECODE_GENERALIZED_TIME_506=An error occurred while \
|
attempting to decode value "%s" for attribute %s in user entry %s in \
|
accordance with the generalized time format: %s
|
MILD_ERR_PWPSTATE_CANNOT_DECODE_BOOLEAN_507=Unable to decode value "%s" for \
|
attribute %s in user entry %s as a Boolean value
|
SEVERE_ERR_ADD_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_508=The entry %s cannot be \
|
added due to insufficient access rights
|
SEVERE_ERR_BIND_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_509=The user %s cannot bind \
|
due to insufficient access rights
|
SEVERE_ERR_COMPARE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_510=The entry %s cannot \
|
be compared due to insufficient access rights
|
SEVERE_ERR_DELETE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_511=The entry %s cannot be \
|
deleted due to insufficient access rights
|
SEVERE_ERR_EXTENDED_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_512=The extended \
|
operation %s cannot be performed due to insufficient access rights
|
SEVERE_ERR_MODDN_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_513=The entry %s cannot be \
|
renamed due to insufficient access rights
|
SEVERE_ERR_MODIFY_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_514=The entry %s cannot be \
|
modified due to insufficient access rights
|
SEVERE_ERR_SEARCH_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_515=The entry %s cannot be \
|
searched due to insufficient access rights
|
MILD_ERR_BIND_OPERATION_INSECURE_SIMPLE_BIND_516=Rejecting a simple bind \
|
request for user %s because the password policy requires secure \
|
authentication
|
MILD_ERR_BIND_OPERATION_ACCOUNT_DISABLED_517=Rejecting a bind request for \
|
user %s because the account has been administrative disabled
|
MILD_ERR_BIND_OPERATION_ACCOUNT_FAILURE_LOCKED_518=Rejecting a bind request \
|
for user %s because the account has been locked due to too many failed \
|
authentication attempts
|
MILD_ERR_BIND_OPERATION_ACCOUNT_RESET_LOCKED_519=Rejecting a bind request for \
|
user %s because the account has been locked after the user's password was not \
|
changed in a timely manner after an administrative reset
|
MILD_ERR_BIND_OPERATION_ACCOUNT_IDLE_LOCKED_520=Rejecting a bind request for \
|
user %s because the account has been locked after remaining idle for too long
|
MILD_ERR_BIND_OPERATION_PASSWORD_EXPIRED_521=Rejecting a bind request for \
|
user %s because that user's password is expired
|
MILD_ERR_PWPSTATE_CANNOT_UPDATE_USER_ENTRY_522=An error occurred while \
|
attempting to update password policy state information for user %s: %s
|
MILD_ERR_BIND_OPERATION_INSECURE_SASL_BIND_523=Rejecting a SASL %s bind \
|
request for user %s because the password policy requires secure \
|
authentication
|
SEVERE_ERR_WORKQ_CANNOT_PARSE_DN_524=An error occurred while attempting to \
|
parse string %s as the DN of the work queue configuration entry: %s
|
SEVERE_ERR_WORKQ_NO_CONFIG_525=Work queue configuration entry %s does not \
|
exist in the server configuration
|
INFO_WORKQ_DESCRIPTION_CLASS_526=Fully-qualified name of the \
|
Java class that provides the core work queue logic for the Directory Server. \
|
Changes to this configuration attribute require that the server be restarted \
|
for the change to take effect
|
SEVERE_ERR_WORKQ_NO_CLASS_ATTR_527=Configuration entry %s does not contain \
|
required attribute %s that specifies the fully-qualified class name for the \
|
work queue implementation
|
SEVERE_ERR_WORKQ_CANNOT_LOAD_528=An error occurred while trying to load class \
|
%s to use as the Directory Server work queue implementation: %s
|
SEVERE_ERR_WORKQ_CANNOT_INSTANTIATE_529=An error occurred while trying to \
|
create an instance of class %s to use as the Directory Server work queue: %s
|
SEVERE_ERR_CANNOT_REGISTER_DUPLICATE_ALTERNATE_ROOT_BIND_DN_530=The alternate \
|
root bind DN "%s" is already registered with the Directory Server for actual \
|
root entry DN "%s"
|
MILD_ERR_BIND_OPERATION_ACCOUNT_EXPIRED_531=Rejecting a bind request for user \
|
%s because the account has expired
|
MILD_ERR_MODIFY_PASSWORDS_CANNOT_HAVE_OPTIONS_532=Attributes used to hold \
|
user passwords are not allowed to have any attribute options
|
MILD_ERR_MODIFY_NO_USER_PW_CHANGES_533=Users are not allowed to change their \
|
own passwords
|
MILD_ERR_MODIFY_REQUIRE_SECURE_CHANGES_534=Password changes must be performed \
|
over a secure authentication channel
|
MILD_ERR_MODIFY_WITHIN_MINIMUM_AGE_535=The password cannot be changed because \
|
it has not been long enough since the last password change
|
MILD_ERR_MODIFY_MULTIPLE_VALUES_NOT_ALLOWED_536=Multiple password values are \
|
not allowed in user entries
|
MILD_ERR_MODIFY_NO_PREENCODED_PASSWORDS_537=User passwords may not be \
|
provided in pre-encoded form
|
MILD_ERR_MODIFY_INVALID_MOD_TYPE_FOR_PASSWORD_538=Invalid modification type \
|
%s attempted on password attribute %s
|
MILD_ERR_MODIFY_NO_EXISTING_VALUES_539=The user entry does not have any \
|
existing passwords to remove
|
MILD_ERR_MODIFY_CANNOT_DECODE_PW_540=An error occurred while attempting to \
|
decode an existing user password: %s
|
MILD_ERR_MODIFY_INVALID_PASSWORD_541=The provided user password does not \
|
match any password in the user's entry
|
MILD_ERR_MODIFY_PW_CHANGE_REQUIRES_CURRENT_PW_542=The password policy \
|
requires that user password changes include the current password in the \
|
request
|
MILD_ERR_MODIFY_MULTIPLE_PASSWORDS_NOT_ALLOWED_543=The password change would \
|
result in multiple password values in the user entry, which is not allowed
|
MILD_ERR_MODIFY_PW_VALIDATION_FAILED_544=The provided password value was \
|
rejected by a password validator: %s
|
MILD_ERR_MODIFY_MUST_CHANGE_PASSWORD_545=You must change your password before \
|
you will be allowed to perform any other operations
|
INFO_ERROR_CATEGORY_PASSWORD_POLICY_546=pw-policy
|
MILD_WARN_BIND_PASSWORD_EXPIRING_547=The user password is about to expire \
|
(time to expiration: %s)
|
MILD_ERR_BIND_ACCOUNT_TEMPORARILY_LOCKED_548=The account has been locked as a \
|
result of too many failed authentication attempts (time to unlock: %s)
|
MILD_ERR_BIND_ACCOUNT_PERMANENTLY_LOCKED_549=The account has been locked as a \
|
result of too many failed authentication attempts. It may only be unlocked \
|
by an administrator
|
MILD_ERR_MODIFY_INVALID_DISABLED_VALUE_550=Invalid value provided for \
|
operational attribute %s: %s
|
INFO_MODIFY_PASSWORD_CHANGED_551=The user password has been changed
|
INFO_MODIFY_PASSWORD_RESET_552=The user password has been administratively \
|
reset
|
INFO_MODIFY_ACCOUNT_ENABLED_553=The user account has been administratively \
|
enabled
|
INFO_MODIFY_ACCOUNT_DISABLED_554=The user account has been administratively \
|
disabled
|
INFO_MODIFY_ACCOUNT_UNLOCKED_555=The user account has been administratively \
|
unlocked
|
MILD_ERR_MODIFY_PASSWORD_EXISTS_556=The specified password value already \
|
exists in the user entry
|
SEVERE_WARN_BIND_MULTIPLE_USER_LOOKTHROUGH_LIMITS_557=There are multiple \
|
user-specific lookthrough limit values contained in user entry %s. The \
|
default server lookthrough limit will be used
|
SEVERE_WARN_BIND_CANNOT_PROCESS_USER_LOOKTHROUGH_LIMIT_558=The user-specific \
|
lookthrough limit value %s contained in user entry %s could not be parsed as \
|
an integer. The default server lookthrough limit will be used
|
MILD_ERR_ENTRY_DUPLICATE_VALUES_559=Unable to add one or more values to \
|
attribute %s because at least one of the values already exists
|
MILD_ERR_ENTRY_NO_SUCH_VALUE_560=Unable to remove one or more values from \
|
attribute %s because at least one of the attributes does not exist in the \
|
entry
|
MILD_ERR_ENTRY_OC_INCREMENT_NOT_SUPPORTED_561=The increment operation is not \
|
supported for the objectClass attribute
|
MILD_ERR_ENTRY_UNKNOWN_MODIFICATION_TYPE_562=Unknown modification type %s \
|
requested
|
MILD_ERR_ENTRY_INCREMENT_MULTIPLE_VALUES_563=Unable to increment the value of \
|
attribute %s because there are multiple values for that attribute
|
MILD_ERR_ENTRY_INCREMENT_INVALID_VALUE_COUNT_564=Unable to increment the \
|
value of attribute %s because the provided modification did not have exactly \
|
one value to use as the increment
|
MILD_ERR_ENTRY_INCREMENT_CANNOT_PARSE_AS_INT_565=Unable to increment the \
|
value of attribute %s because either the current value or the increment could \
|
not be parsed as an integer
|
SEVERE_ERR_MODIFY_NO_MODIFICATIONS_566=Entry %s cannot be updated because the \
|
request did not contain any modifications
|
INFO_DSCORE_DESCRIPTION_NODETACH_567=Do not detach from the terminal and \
|
continue running in the foreground. This option cannot be used with the \
|
-t, --timeout option
|
MILD_ERR_ENTRY_INCREMENT_NO_SUCH_ATTRIBUTE_568=Unable to increment the value \
|
of attribute %s because that attribute does not exist in the entry
|
INFO_DSCORE_TOOL_DESCRIPTION_569=This utility can be used to start the \
|
Directory Server, as well as to obtain the server version and other forms of \
|
general server information
|
MILD_ERR_EXTENDED_UNSUPPORTED_CRITICAL_CONTROL_570=Unable to process the \
|
request for extended operation %s because it contained an unsupported \
|
critical control with OID %s
|
SEVERE_ERR_REGISTER_BACKEND_ALREADY_EXISTS_571=Unable to register backend %s \
|
with the Directory Server because another backend with the same backend ID is \
|
already registered
|
SEVERE_ERR_REGISTER_BASEDN_ALREADY_EXISTS_572=Unable to register base DN %s \
|
with the Directory Server for backend %s because that base DN is already \
|
registered for backend %s
|
SEVERE_ERR_REGISTER_BASEDN_HIERARCHY_CONFLICT_573=Unable to register base DN \
|
%s with the Directory Server for backend %s because that backend already \
|
contains another base DN %s that is within the same hierarchical path
|
SEVERE_ERR_REGISTER_BASEDN_DIFFERENT_PARENT_BASES_574=Unable to register base \
|
DN %s with the Directory Server for backend %s because that backend already \
|
contains another base DN %s that is not subordinate to the same base DN in \
|
the parent backend
|
SEVERE_ERR_REGISTER_BASEDN_NEW_BASE_NOT_SUBORDINATE_575=Unable to register \
|
base DN %s with the Directory Server for backend %s because that backend \
|
already contains one or more other base DNs that are subordinate to backend \
|
%s but the new base DN is not
|
SEVERE_WARN_REGISTER_BASEDN_ENTRIES_IN_MULTIPLE_BACKENDS_576=Backend %s \
|
already contains entry %s which has just been registered as the base DN for \
|
backend %s. These conflicting entries can cause unexpected or errant search \
|
results, and both backends should be reinitialized to ensure that each has \
|
the correct content
|
SEVERE_ERR_DEREGISTER_BASEDN_NOT_REGISTERED_577=Unable to de-register base DN \
|
%s with the Directory Server because that base DN is not registered for any \
|
active backend
|
SEVERE_WARN_DEREGISTER_BASEDN_MISSING_HIERARCHY_578=Base DN %s has been \
|
deregistered from the Directory Server for backend %s. This base DN had both \
|
superior and subordinate entries in other backends, and there might be \
|
inconsistent or unexpected behavior when accessing entries in this portion of \
|
the hierarchy because of the missing entries that had been held in the \
|
de-registered backend
|
MILD_ERR_SCHEMA_CIRCULAR_DEPENDENCY_REFERENCE_579=Unable to update the schema \
|
element with definition "%s" because a circular reference was identified when \
|
attempting to rebuild other schema elements dependent upon it
|
MILD_ERR_REJECT_UNAUTHENTICATED_OPERATION_580=Rejecting the requested \
|
operation because the connection has not been authenticated
|
SEVERE_WARN_ADD_ATTR_IS_OBSOLETE_581=Entry "%s" cannot be added because it \
|
contains attribute type %s which is declared OBSOLETE in the server schema
|
SEVERE_WARN_ADD_OC_IS_OBSOLETE_582=Entry "%s" cannot be added because it \
|
contains objectclass %s which is declared OBSOLETE in the server schema
|
MILD_ERR_MODIFY_ATTR_IS_OBSOLETE_583=Entry %s cannot be modified because the \
|
modification attempted to set one or more new values for attribute %s which \
|
is marked OBSOLETE in the server schema
|
MILD_ERR_ENTRY_ADD_OBSOLETE_OC_584=Object class %s added to entry %s is marked \
|
OBSOLETE in the server schema
|
MILD_ERR_MODDN_NEWRDN_ATTR_IS_OBSOLETE_585=The modify DN operation for entry \
|
%s cannot be performed because the new RDN includes attribute type %s which \
|
is declared OBSOLETE in the server schema
|
MILD_ERR_ENTRY_SCHEMA_VIOLATES_PARENT_DSR_586=Entry %s is invalid according \
|
to the server schema because there is no DIT structure rule that applies to \
|
that entry, but there is a DIT structure rule for the parent entry %s
|
MILD_ERR_ENTRY_SCHEMA_COULD_NOT_CHECK_PARENT_DSR_587=An unexpected error \
|
occurred while attempting to perform DIT structure rule processing for the \
|
parent of entry %s: %s
|
MILD_WARN_CLIENTCONNECTION_DISCONNECT_DUE_TO_DELETE_588=Terminating the \
|
client connection because its associated authentication or authorization \
|
entry %s has been deleted
|
MILD_ERR_MODIFY_PWRESET_INSUFFICIENT_PRIVILEGES_589=You do not have \
|
sufficient privileges to reset user passwords
|
MILD_ERR_COMPARE_CONFIG_INSUFFICIENT_PRIVILEGES_590=You do not have \
|
sufficient privileges to access the server configuration
|
SEVERE_ERR_ADD_CHANGE_PRIVILEGE_INSUFFICIENT_PRIVILEGES_591=You do not have \
|
sufficient privileges to add entries that include privileges
|
MILD_ERR_MODIFY_CHANGE_PRIVILEGE_INSUFFICIENT_PRIVILEGES_592=You do not have \
|
sufficient privileges to modify the set of privileges contained in an entry
|
INFO_CLIENTCONNECTION_AUDIT_HASPRIVILEGE_593=hasPrivilege determination for \
|
connID=%d opID=%d requesterDN="%s" privilege="%s" result=%b
|
INFO_CLIENTCONNECTION_AUDIT_HASPRIVILEGES_594=hasPrivilege determination for \
|
connID=%d opID=%d requesterDN="%s" privilegeSet="%s" result=%b
|
MILD_ERR_PROXYAUTH_INSUFFICIENT_PRIVILEGES_595=You do not have sufficient \
|
privileges to use the proxied authorization control
|
INFO_DSCORE_DESCRIPTION_CHECK_STARTABILITY_596=Used to determine whether a \
|
server can be started or not and the mode to be used to start it
|
MILD_ERR_ENTRY_SCHEMA_ATTR_NO_VALUES_597=Entry %s violates the Directory \
|
Server schema configuration because it includes attribute %s without any \
|
values
|
FATAL_ERR_DSCORE_ERROR_NODETACH_AND_WINDOW_SERVICE_598=OpenDS is configured \
|
to run as a window service and it cannot run in no-detach mode
|
INFO_DSCORE_DESCRIPTION_WINDOWS_NET_START_599=Used by the window service code \
|
to inform that start-ds is being called from the window services after a call \
|
to net start
|
MILD_ERR_ENTRY_DECODE_UNRECOGNIZED_VERSION_600=Unable to decode an entry \
|
because it had an unsupported entry version byte value of %s
|
MILD_ERR_ENTRY_DECODE_EXCEPTION_601=Unable to decode an entry because an \
|
unexpected exception was caught during processing: %s
|
MILD_ERR_SEARCH_FILTER_NOT_EXACTLY_ONE_602=The provided search filter "%s" \
|
could not be decoded because the NOT filter between positions %d and %d did \
|
not contain exactly one filter component
|
MILD_ERR_SORTKEY_INVALID_ORDER_INDICATOR_603=The provided sort key value %s \
|
is invalid because it does not start with either '+' (to indicate sorting in \
|
ascending order) or '-' (to indicate sorting in descending order)
|
MILD_ERR_SORTKEY_UNDEFINED_TYPE_604=The provided sort key value %s is invalid \
|
because it references undefined attribute type %s
|
MILD_ERR_SORTKEY_NO_ORDERING_RULE_605=The provided sort key value %s is \
|
invalid because attribute type %s does not have a default ordering matching \
|
rule and no specific rule was provided
|
MILD_ERR_SORTKEY_UNDEFINED_ORDERING_RULE_606=The provided sort key value %s \
|
is invalid because it references undefined ordering matching rule %s
|
MILD_ERR_SORTORDER_DECODE_NO_KEYS_607=The provided sort order string "%s" is \
|
invalid because it does not contain any sort keys
|
INFO_RESULT_SORT_CONTROL_MISSING_608=Sort Control Missing
|
INFO_RESULT_OFFSET_RANGE_ERROR_609=Offset Range Error
|
INFO_RESULT_VIRTUAL_LIST_VIEW_ERROR_610=Virtual List View Error
|
SEVERE_ERR_CONTROL_INSUFFICIENT_ACCESS_RIGHTS_611=The request control with \
|
Object Identifier (OID) "%s" cannot be used due to insufficient access rights
|
SEVERE_ERR_HOST_PORT_ALREADY_SPECIFIED_612=The connection handler %s is \
|
trying to use the listener %s which is already in use by another connection \
|
handler
|
SEVERE_ERR_HOST_PORT_CANNOT_BE_USED_613=The server cannot use the listener %s \
|
of connection handler %s because it is already being used by another process \
|
or because it does not have the rights to use it
|
SEVERE_ERR_NOT_AVAILABLE_CONNECTION_HANDLERS_614=No enabled connection \
|
handler available
|
SEVERE_ERR_ERROR_STARTING_CONNECTION_HANDLERS_615=Could not start connection \
|
handlers
|
SEVERE_ERR_BIND_REJECTED_LOCKDOWN_MODE_616=Unable to process the non-root \
|
bind because the server is in lockdown mode
|
SEVERE_WARN_DIRECTORY_SERVER_ENTERING_LOCKDOWN_MODE_617=The Directory Server \
|
is entering lockdown mode, in which clients will only be allowed to connect \
|
via a loopback address, and only root users will be allowed to process \
|
operations
|
NOTICE_DIRECTORY_SERVER_LEAVING_LOCKDOWN_MODE_618=The Directory Server is \
|
leaving lockdown mode and will resume normal operation
|
NOTICE_REJECT_OPERATION_IN_LOCKDOWN_MODE_619=Rejecting the requested \
|
operation because the server is in lockdown mode and will only accept \
|
requests from root users over loopback connections
|
SEVERE_ERR_COMPRESSEDSCHEMA_UNRECOGNIZED_AD_TOKEN_620=Unable to decode the \
|
provided attribute because it used an undefined attribute description token \
|
%s
|
SEVERE_ERR_COMPRESSEDSCHEMA_UNKNOWN_OC_TOKEN_621=Unable to decode the \
|
provided object class set because it used an undefined token %s
|
SEVERE_ERR_COMPRESSEDSCHEMA_CANNOT_WRITE_UPDATED_DATA_622=Unable to write the \
|
updated compressed schema token data: %s
|
SEVERE_ERR_ENTRYENCODECFG_INVALID_LENGTH_623=Unable to decode the provided \
|
entry encode configuration element because it has an invalid length
|
INFO_RESULT_NO_OPERATION_624=No Operation
|
SEVERE_ERR_SEARCH_FILTER_CREATE_EXTENSIBLE_MATCH_NO_AT_OR_MR_625=Unable to \
|
create an extensible match search filter using the provided information \
|
because it did not contain either an attribute type or a matching rule ID. \
|
At least one of these must be provided
|
SEVERE_ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_AD_OR_MR_626=The provided search \
|
filter "%s" could not be decoded because the extensible match component \
|
starting at position %d did not contain either an attribute description or a \
|
matching rule ID. At least one of these must be provided
|
SEVERE_ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_SUCH_MR_627=The provided search \
|
filter "%s" could not be decoded because the extensible match component \
|
starting at position %d referenced an unknown matching rule %s
|
MILD_ERR_BIND_OPERATION_WRITABILITY_DISABLED_628=Rejecting a bind request for \
|
user %s because either the entire server or the user's backend has a \
|
writability mode of 'disabled' and password policy state updates would not be \
|
allowed
|
MILD_ERR_MODIFY_PW_IN_HISTORY_629=The provided new password was found in the \
|
password history for the user
|
SEVERE_WARN_BIND_MULTIPLE_USER_IDLE_TIME_LIMITS_630=There are multiple \
|
user-specific idle time limit values contained in user entry %s. The default \
|
server idle time limit will be used
|
SEVERE_WARN_BIND_CANNOT_PROCESS_USER_IDLE_TIME_LIMIT_631=The user-specific \
|
idle time limit value %s contained in user entry %s could not be parsed as an \
|
integer. The default server idle time limit will be used
|
INFO_IDLETIME_LIMIT_EXCEEDED_632=This connection has been terminated because \
|
it has remained idle for too long
|
SEVERE_ERR_PWPOLICY_WARNING_INTERVAL_LARGER_THAN_MAX_AGE_633=The password \
|
policy configuration entry "%s" is invalid because if a maximum password age \
|
is configured, then the password expiration warning interval must be shorter \
|
than the maximum password age
|
SEVERE_ERR_PWPOLICY_MIN_AGE_PLUS_WARNING_GREATER_THAN_MAX_AGE_634=The \
|
password policy configuration entry "%s" is invalid because if both a minimum \
|
password age and a maximum password age are configured, then the sum of the \
|
minimum password age and the password expiration warning interval must be \
|
shorter than the maximum password age
|
SEVERE_ERR_REGISTER_WORKFLOW_ALREADY_EXISTS_635=Unable to register workflow \
|
%s with the Directory Server because another workflow with the same workflow \
|
ID is already registered
|
SEVERE_ERR_REGISTER_WORKFLOW_NODE_ALREADY_EXISTS_636=Unable to register \
|
workflow node %s with the network group %s because another workflow node with \
|
the same workflow node ID is already registered
|
SEVERE_ERR_REGISTER_NETWORK_GROUP_ALREADY_EXISTS_637=Unable to register \
|
network group %s with the Directory Server because another network group with \
|
the same network group ID is already registered
|
MILD_ERR_IDLETIME_DISCONNECT_ERROR_638=An error occurred while attempting to \
|
disconnect client connection %d: %s
|
SEVERE_ERR_IDLETIME_UNEXPECTED_ERROR_639=An unexpected error occurred in the \
|
idle time limit thread: %s
|
SEVERE_ERR_DIRCFG_SERVER_ALREADY_RUNNING_640=The Directory Server is \
|
currently running. Environment configuration changes are not allowed with \
|
the server running
|
SEVERE_ERR_DIRCFG_INVALID_SERVER_ROOT_641=The specified server root directory \
|
'%s' is invalid. The specified path must exist and must be a directory
|
SEVERE_ERR_DIRCFG_INVALID_CONFIG_FILE_642=The specified config file path '%s' \
|
is invalid. The specified path must exist and must be a file
|
SEVERE_ERR_DIRCFG_INVALID_CONFIG_CLASS_643=The specified config handler class \
|
'%s' is invalid. The specified class must be a subclass of the \
|
org.opends.server.api.ConfigHandler superclass
|
SEVERE_ERR_DIRCFG_INVALID_SCHEMA_DIRECTORY_644=The specified schema \
|
configuration directory '%s' is invalid. The specified path must exist and \
|
must be a directory
|
SEVERE_ERR_DIRCFG_INVALID_LOCK_DIRECTORY_645=The specified lock directory \
|
'%s' is invalid. The specified path must exist and must be a directory
|
SEVERE_ERR_DIRCFG_INVALID_CONCURRENCY_LEVEL_646=The specified lock table \
|
concurrency level %d is invalid. It must be an integer value greater than \
|
zero
|
SEVERE_ERR_DIRCFG_INVALID_LOCK_TABLE_SIZE_647=The specified initial lock \
|
table size %d is invalid. It must be an integer value greater than zero
|
FATAL_ERR_CANNOT_SET_ENVIRONMENT_CONFIG_WHILE_RUNNING_648=The Directory \
|
Server is currently running. The environment configuration can not be \
|
altered while the server is online
|
SEVERE_ERR_CRYPTOMGR_SSL_CONTEXT_CANNOT_INITIALIZE_649=An error occurred \
|
while attempting to initialize a SSL context for server to server \
|
communication: %s
|
SEVERE_ERR_CRYPTOMGR_ADS_TRUST_STORE_BACKEND_NOT_ENABLED_650=The ADS trust \
|
store backend %s is not enabled
|
SEVERE_ERR_CRYPTOMGR_ADS_TRUST_STORE_BACKEND_WRONG_CLASS_651=The backend %s \
|
is not a trust store backend
|
INFO_DSCORE_DESCRIPTION_LASTKNOWNGOODCFG_652=Attempt to start using the \
|
configuration that was in place at the last successful startup (if it is \
|
available) rather than using the current active configuration
|
INFO_TRUSTSTORESYNC_ADMIN_SUFFIX_SEARCH_FAILED_653=Error while searching base \
|
%s to synchronize the trust store: %s
|
SEVERE_ERR_TRUSTSTORESYNC_EXCEPTION_654=An error occurred in the trust store \
|
synchronization thread: %s
|
INFO_TRUSTSTORESYNC_ADD_FAILED_655=Error while trying to add entry %s \
|
to the trust store: %s
|
INFO_TRUSTSTORESYNC_DELETE_FAILED_656=Error while trying to delete entry %s \
|
from the trust store: %s
|
SEVERE_ERR_PWPOLICY_SCHEME_DOESNT_SUPPORT_AUTH_657=The password storage \
|
scheme defined in configuration entry %s does not support the auth password \
|
syntax, which is used by password attribute %s
|
SEVERE_ERR_PWPOLICY_NO_SUCH_DEPRECATED_SCHEME_658=Password policy \
|
configuration entry %s references deprecated password storage scheme DN %s \
|
which is not available for use in the server
|
SEVERE_ERR_PWPOLICY_DEPRECATED_SCHEME_NOT_AUTH_659=Password policy \
|
configuration entry %s references deprecated password storage scheme DN %s \
|
which does not support the auth password syntax
|
SEVERE_WARN_GROUP_FILTER_NOT_INDEXED_660=The search filter "%s" used by group \
|
implementation %s is not indexed in backend %s. Backend initialization \
|
for this group implementation might take a very long time to complete
|
SEVERE_ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_DIGEST_661=CryptoManager cannot get \
|
the requested digest %s: %s
|
SEVERE_ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MAC_ENGINE_662=CryptoManager cannot \
|
get the requested MAC engine %s: %s
|
SEVERE_ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_ENCRYPTION_CIPHER_663=CryptoManager \
|
cannot get the requested encryption cipher %s: %s
|
SEVERE_ERR_CRYPTOMGR_CANNOT_GET_PREFERRED_KEY_WRAPPING_CIPHER_664=CryptoManager \
|
cannot get the preferred key wrapping cipher: %s
|
SEVERE_ERR_CRYPTOMGR_FAILED_TO_INITIATE_INSTANCE_KEY_GENERATION_665=CryptoManager \
|
failed to add entry "%s" to initiate instance key generation
|
SEVERE_ERR_CRYPTOMGR_FAILED_TO_RETRIEVE_INSTANCE_CERTIFICATE_666=CryptoManager \
|
failed to retrieve entry "%s" (the instance-key-pair public-key-certificate): %s
|
SEVERE_ERR_CRYPTOMGR_FAILED_TO_COMPUTE_INSTANCE_KEY_IDENTIFIER_667=CryptoManager \
|
failed to compute an instance key identifier: %s
|
SEVERE_ERR_CRYPTOMGR_FAILED_TO_ADD_INSTANCE_KEY_ENTRY_TO_ADS_668=Failed \
|
to add entry "%s"
|
SEVERE_ERR_CRYPTOMGR_FAILED_TO_PUBLISH_INSTANCE_KEY_ENTRY_669=CryptoManager \
|
failed to publish the instance-key-pair public-key-certificate entry in ADS: %s
|
SEVERE_ERR_CRYPTOMGR_FAILED_TO_RETRIEVE_ADS_TRUSTSTORE_CERTS_670=CryptoManager \
|
failed to retrieve the collection of instance-key-pair public-key-certificates \
|
from ADS container "%s": %s
|
SEVERE_ERR_CRYPTOMGR_FAILED_TO_ENCODE_SYMMETRIC_KEY_ATTRIBUTE_671=CryptoManager \
|
failed to encode symmetric key attribute value: %s
|
SEVERE_ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_FIELD_COUNT_672=CryptoManager \
|
symmetric key attribute value "%s" syntax is invalid: incorrect number of fields
|
SEVERE_ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_SYNTAX_673=CryptoManager \
|
symmetric key attribute value "%s" syntax is invalid. Parsing failed in field \
|
"%s" at offset %d
|
SEVERE_ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_NO_PRIVATE_674=CryptoManager \
|
failed to retrieve the instance-key-pair private-key: %s
|
SEVERE_ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_DECIPHER_675=CryptoManager \
|
failed to decipher the wrapped secret-key value: %s
|
MILD_ERR_CRYPTOMGR_REWRAP_SYMMETRIC_KEY_ATTRIBUTE_NO_WRAPPER_676=CryptoManager \
|
cannot find the public-key-certificate (identifier "%s") requested for symmetric \
|
key re-encoding
|
MILD_ERR_CRYPTOMGR_INVALID_KEY_IDENTIFIER_SYNTAX_677=CryptoManager failed to decode \
|
the key entry identifier "%s": %s
|
SEVERE_ERR_CRYPTOMGR_GET_MAC_ENGINE_INVALID_MAC_ALGORITHM_678=CrytpoManager \
|
passed invalid MAC algorithm "%s": %s
|
SEVERE_ERR_CRYPTOMGR_GET_MAC_ENGINE_CANNOT_INITIALIZE_679=CryptoManager \
|
failed to initialize MAC engine: %s
|
SEVERE_ERR_CRYPTOMGR_GET_CIPHER_INVALID_CIPHER_TRANSFORMATION_680=CryptoManager \
|
passed invalid Cipher transformation "%s": %s
|
SEVERE_ERR_CRYPTOMGR_GET_CIPHER_CANNOT_INITIALIZE_681=CryptoManager \
|
cannot initialize Cipher: %s
|
SEVERE_ERR_CRYPTOMGR_GET_CIPHER_STREAM_PROLOGUE_WRITE_ERROR_682=CryptoManager \
|
failed to write the stream prologue: %s
|
MILD_ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_KEY_IDENTIFIER_683=CryptoManager \
|
failed to decrypt the supplied data because it could not read the symmetric \
|
key identifier in the data prologue: %s
|
MILD_ERR_CRYPTOMGR_DECRYPT_UNKNOWN_KEY_IDENTIFIER_684=CryptoManager failed to \
|
decrypt the supplied data because the symmetric key identifier in the data \
|
prologue does not match any known key entries
|
MILD_ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_IV_685=CryptoManager failed to \
|
decrypt the supplied data because it could not read the cipher initialization \
|
vector in the data prologue
|
MILD_ERR_CRYPTOMGR_DECRYPT_CIPHER_INPUT_STREAM_ERROR_686=CryptoManager failed \
|
to decrypt the supplied data because there was an error reading from the \
|
input stream: %s
|
SEVERE_ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_DECODE_687=CryptoManager \
|
failed to import the symmetric key entry "%s" because it could not obtain a \
|
symmetric key attribute value that can be decoded by this instance
|
SEVERE_ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FIELD_MISMATCH_688=CryptoManager \
|
detected a field mismatch between the key entry to be imported and an entry \
|
in the key cache that share the key identifier "%s"
|
SEVERE_ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_OTHER_689=CryptoManager failed \
|
to import the symmetric key entry "%s": %s
|
SEVERE_ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_ADD_KEY_690=CryptoManager \
|
failed to import the symmetric key entry "%s" because it could not add \
|
a symmetric key attribute value that can be decoded by this instance
|
MILD_ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_ALGORITHM_691=CryptoManager failed \
|
to instantiate a KeyGenerator for algorithm "%s": %s
|
SEVERE_ERR_CRYPTOMGR_SYMMETRIC_KEY_ENTRY_ADD_FAILED_692=CryptoManager failed \
|
to add locally produced symmetric key entry "%s": %s
|
SEVERE_ERR_CRYPTOMGR_FULL_CIPHER_TRANSFORMATION_REQUIRED_693=CryptoManager \
|
cipher transformation specification "%s" is invalid: it must be of the form \
|
"algorithm/mode/padding"
|
SEVERE_ERR_CRYPTOMGR_FULL_KEY_WRAPPING_TRANSFORMATION_REQUIRED_694=CryptoManager \
|
cipher transformation specification "%s" is invalid: it must be of the form \
|
"algorithm/mode/padding"
|
MILD_ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_PROLOGUE_VERSION_695=CryptoManager \
|
failed to decrypt the supplied data because it could not read the version \
|
number in the data prologue: %s
|
MILD_ERR_CRYPTOMGR_DECRYPT_UNKNOWN_PROLOGUE_VERSION_696=CryptoManager failed to \
|
decrypt the supplied data because the version "%d" in the data prologue is \
|
unknown
|
MILD_ERR_ADD_ENTRY_UNKNOWN_SUFFIX_697=The provided entry %s cannot be added \
|
because its suffix is not defined as one of the suffixes within the \
|
Directory Server
|
NOTICE_VERSION_698=%s
|
NOTICE_BUILD_ID_699=Build ID: %s
|
MILD_ERR_CANNOT_CANCEL_START_TLS_700=Start TLS extended operations cannot be \
|
canceled
|
MILD_ERR_CANNOT_CANCEL_CANCEL_701=Cancel extended operations can not be \
|
canceled
|
MILD_ERR_MODDN_NEW_SUPERIOR_IN_SUBTREE_702=The modify DN operation \
|
for entry %s cannot be performed because the new superior entry %s is equal \
|
to or a subordinate of the entry to be moved
|
SEVERE_ERR_REGISTER_WORKFLOW_ELEMENT_ALREADY_EXISTS_703=Unable to register \
|
workflow element %s with the Directory Server because another workflow \
|
element with the same ID is already registered
|
INFO_ERROR_MAX_CONNECTIONS_LIMIT_EXCEEDED_704=Unable to process operation \
|
because the network group has already reached its maximum number of \
|
simultaneous connections
|
INFO_ERROR_MAX_CONNECTIONS_FROM_SAME_IP_LIMIT_EXCEEDED_705=Unable to process \
|
operation because the network group has already reached its maximum number \
|
of simultaneous connections from the same client
|
INFO_ERROR_MAX_OPERATIONS_PER_CONNECTION_LIMIT_EXCEEDED_706=Unable to process \
|
operation because the network group has already reached its maximum number \
|
of operations on this connection
|
INFO_ERROR_MAX_CONCURRENT_OPERATIONS_PER_CONNECTION_LIMIT_EXCEEDED_707=Unable \
|
to process operation because the network group has already reached its \
|
maximum number of concurrent operations on this connection
|
INFO_CHANGE_NETWORK_GROUP_708=Connection ConnID=%d moved from network group %s \
|
to %s
|
INFO_ERROR_MIN_SEARCH_SUBSTRING_LENGTH_LIMIT_EXCEEDED_709=Unable to process \
|
operation because the search substring length is less than the network \
|
group minimum search substring length
|
INFO_ERROR_OPERATION_NOT_ALLOWED_710=Unable to process operation because this \
|
type of operation is not allowed in this network group
|
INFO_ERROR_ATTRIBUTE_NOT_ALLOWED_711=Unable to process operation because this \
|
attribute is not allowed in this network group
|
INFO_ERROR_SEARCH_SCOPE_NOT_ALLOWED_712=Unable to process operation because \
|
this search scope is not allowed in this network group
|
INFO_ERROR_SUBTREE_NOT_ALLOWED_713=Unable to process operation because this \
|
subtree is not allowed in this network group
|
SEVERE_ERR_ROOT_WORKFLOW_ELEMENT_NOT_DEFINED_714=The workflow %s cannot \
|
process the operation because no root workflow element has been \
|
registered with the workflow
|
MILD_ERR_ADD_ATTR_IS_INVALID_OPTION_715=Entry %s can not be added because \
|
BER encoding of %s attribute is not supported
|
SEVERE_ERR_REGISTER_WORKFLOW_BASE_DN_ALREADY_EXISTS_716=Unable to register \
|
workflow node "%s" with the network group "%s" because another workflow node \
|
"%s" with the same base DN "%s" is already registered
|
INFO_ERR_WORKFLOW_IN_USE_717=\
|
Unable to remove the workflow "%s" because the workflow is still in use \
|
(there are still %d reference(s) to the workflow)
|
INFO_ERR_WORKFLOW_DOES_NOT_EXIST_718=\
|
Unable to register the workflow "%s" with the network group %s because \
|
the workflow does not exist
|
SEVERE_ERR_WORKFLOW_BASE_DN_DUPLICATED_IN_NG_719=\
|
Unable to register the workflow because the base DN '%s' is already \
|
registered with the network group '%s'
|
INFO_ERGONOMIC_SIZING_OF_WORKER_THREAD_POOL_720=No worker queue thread \
|
pool size specified: sizing automatically to use %d threads
|
SEVERE_ERR_CRYPTOMGR_FAILED_INSTANCE_CERTIFICATE_NULL_721=The CryptoManager \
|
entry "%s" (the instance-key-pair public-key-certificate) does not contain \
|
a public-key certificate
|
INFO_DSCORE_DESCRIPTION_TIMEOUT_722=Maximum time (in seconds) to wait before \
|
the command returns (the server continues the startup process, regardless). \
|
A value of '0' indicates an infinite timeout, which means that the command \
|
returns only when the server startup is completed. The default value is \
|
60 seconds. This option cannot be used with the -N, --nodetach option
|
FATAL_ERR_DSCORE_ERROR_NODETACH_TIMEOUT_723=In no-detach mode, the 'timeout' \
|
option cannot be used
|
SEVERE_WARN_SUBENTRY_FILTER_NOT_INDEXED_724=The search filter "%s" used by \
|
subentry manager is not indexed in backend %s. Backend initialization \
|
for subentry manager processing might take a very long time to complete
|
INFO_RESULT_UNDEFINED_725=Undefined
|
SEVERE_ERR_PWPOLICY_NO_PWDPOLICY_OC_726=The entry %s does not contain the \
|
pwdPolicy objectclass, which is required for Directory Server password policy
|
