////
  The contents of this file are subject to the terms of the Common Development and
  Distribution License (the License). You may not use this file except in compliance with the
  License.
 
  You can obtain a copy of the License at legal/CDDLv1.0.txt. See the License for the
  specific language governing permission and limitations under the License.
 
  When distributing Covered Software, include this CDDL Header Notice in each file and include
  the License file at legal/CDDLv1.0.txt. If applicable, add the following below the CDDL
  Header, with the fields enclosed by brackets [] replaced by your own identifying
  information: "Portions copyright [year] [name of copyright owner]".
 
  Copyright 2017 ForgeRock AS.
  Portions Copyright 2024 3A Systems LLC.
////

:figure-caption!:
:example-caption!:
:table-caption!:


[appendix]
[#appendix-log-messages]
== Log Message Reference

xref:../admin-guide/chap-monitoring.adoc#logging["Server Logs"] in the __Administration Guide__ describes logs. Access and audit logs concern client operations rather than OpenDJ directory server and tools, and so are not listed here. Instead, this appendix covers severe and fatal error messages for the directory server and its tools, such as those logged in `/path/to/opendj/logs/errors`, and `/path/to/opendj/logs/replication`.

[#ADMIN]
=== Log Message Category: ADMIN

--

[#log-ref-log-ref-ERR_ADMIN_CANNOT_GET_LISTENER_BASE_1]
ID: 1::
Severity: ERROR

+
Message: An error occurred while trying to retrieve relation configuration entry %s: %s.

[#log-ref-log-ref-ERR_ADMIN_CANNOT_GET_MANAGED_OBJECT_3]
ID: 3::
Severity: ERROR

+
Message: An error occurred while trying to retrieve the managed object configuration entry %s: %s.

[#log-ref-log-ref-ERR_ADMIN_MANAGED_OBJECT_DOES_NOT_EXIST_4]
ID: 4::
Severity: ERROR

+
Message: The managed object configuration entry %s does not appear to exist in the Directory Server configuration. This is a required entry.

[#log-ref-log-ref-ERR_ADMIN_MANAGED_OBJECT_DECODING_PROBLEM_5]
ID: 5::
Severity: ERROR

+
Message: An error occurred while trying to decode the managed object configuration entry %s: %s.

[#log-ref-log-ref-ERR_ADMIN_CANNOT_INSTANTIATE_CLASS_6]
ID: 6::
Severity: ERROR

+
Message: The Directory Server was unable to load class %s and use it to create a component instance as defined in configuration entry %s. The error that occurred was: %s. This component will be disabled.

[#log-ref-log-ref-ERR_ADMIN_CANNOT_OPEN_JAR_FILE_9]
ID: 9::
Severity: ERROR

+
Message: The Directory Server jar file %s in directory %s cannot be loaded because an unexpected error occurred while trying to open the file for reading: %s.

[#log-ref-log-ref-ERR_ADMIN_EXTENSIONS_DIR_NOT_DIRECTORY_13]
ID: 13::
Severity: ERROR

+
Message: Unable to read the Directory Server extensions because the extensions directory %s exists but is not a directory.

[#log-ref-log-ref-ERR_ADMIN_EXTENSIONS_CANNOT_LIST_FILES_14]
ID: 14::
Severity: ERROR

+
Message: Unable to read the Directory Server extensions from directory %s because an unexpected error occurred while trying to list the files in that directory: %s.

[#log-ref-log-ref-ERR_ADMIN_CANNOT_FIND_CORE_MANIFEST_15]
ID: 15::
Severity: ERROR

+
Message: The core administration manifest file %s cannot be located.

[#log-ref-log-ref-ERR_ADMIN_CANNOT_READ_EXTENSION_MANIFEST_17]
ID: 17::
Severity: ERROR

+
Message: The administration manifest file %s associated with the extension %s cannot be loaded because an unexpected error occurred while trying to read it: %s.

[#log-ref-log-ref-ERR_ADMIN_UNABLE_TO_REGISTER_LISTENER_57]
ID: 57::
Severity: ERROR

+
Message: Unable to register an add/delete listener against the entry "%s" because it does not exist in the configuration.

[#log-ref-log-ref-ERR_OPERATION_REJECTED_DEFAULT_74]
ID: 74::
Severity: ERROR

+
Message: Reason unknown.

[#log-ref-log-ref-ERR_SERVER_CONSTRAINT_EXCEPTION_75]
ID: 75::
Severity: ERROR

+
Message: A configuration exception occurred while evaluating a constraint: %s.

[#log-ref-log-ref-ERR_DECODING_EXCEPTION_NO_TYPE_INFO_82]
ID: 82::
Severity: ERROR

+
Message: The %s could be found but did not contain any type information (e.g. missing object classes in LDAP).

[#log-ref-log-ref-ERR_DECODING_EXCEPTION_WRONG_TYPE_INFO_83]
ID: 83::
Severity: ERROR

+
Message: The %s could be found but did not contain the expected type information (e.g. incorrect object classes in LDAP).

[#log-ref-log-ref-ERR_DECODING_EXCEPTION_ABSTRACT_TYPE_INFO_84]
ID: 84::
Severity: ERROR

+
Message: The %s could be found but its type resolved to an abstract managed object definition.

[#log-ref-log-ref-ERR_DEFAULT_BEHAVIOR_PROPERTY_EXCEPTION_86]
ID: 86::
Severity: ERROR

+
Message: The default values for the "%s" property could not be determined.

[#log-ref-log-ref-ERR_ILLEGAL_PROPERTY_VALUE_EXCEPTION_87]
ID: 87::
Severity: ERROR

+
Message: The value "%s" is not a valid value for the "%s" property, which must have the following syntax: %s.

[#log-ref-log-ref-ERR_PROPERTY_IS_MANDATORY_EXCEPTION_89]
ID: 89::
Severity: ERROR

+
Message: The "%s" property must be specified as it is mandatory.

[#log-ref-log-ref-ERR_PROPERTY_IS_READ_ONLY_EXCEPTION_90]
ID: 90::
Severity: ERROR

+
Message: The "%s" property must not be modified as it is read-only.

[#log-ref-log-ref-ERR_PROPERTY_IS_SINGLE_VALUED_EXCEPTION_91]
ID: 91::
Severity: ERROR

+
Message: The "%s" property must not contain more than one value.

[#log-ref-log-ref-ERR_UNKNOWN_PROPERTY_DEFINITION_EXCEPTION_92]
ID: 92::
Severity: ERROR

+
Message: An internal error occurred while processing property "%s": unknown property type "%s".

[#log-ref-log-ref-ERR_AUTHENTICATION_EXCEPTION_DEFAULT_93]
ID: 93::
Severity: ERROR

+
Message: Authentication failure.

[#log-ref-log-ref-ERR_AUTHENTICATION_NOT_SUPPORTED_EXCEPTION_DEFAULT_94]
ID: 94::
Severity: ERROR

+
Message: The requested authentication mechanism is not supported by the server.

[#log-ref-log-ref-ERR_AUTHORIZATION_EXCEPTION_DEFAULT_95]
ID: 95::
Severity: ERROR

+
Message: Authorization failure.

[#log-ref-log-ref-ERR_COMMUNICATION_EXCEPTION_DEFAULT_96]
ID: 96::
Severity: ERROR

+
Message: A communication problem occurred while contacting the server.

[#log-ref-log-ref-ERR_OPERATION_REJECTED_EXCEPTION_SINGLE_97]
ID: 97::
Severity: ERROR

+
Message: The operation was rejected for the following reason: %s.

[#log-ref-log-ref-ERR_OPERATION_REJECTED_EXCEPTION_PLURAL_98]
ID: 98::
Severity: ERROR

+
Message: The operation was rejected for the following reasons: %s.

[#log-ref-log-ref-ERR_CONCURRENT_MODIFICATION_EXCEPTION_DEFAULT_99]
ID: 99::
Severity: ERROR

+
Message: The operation could not be performed because a conflicting change has already occurred. There may be another client administration tool in use.

[#log-ref-log-ref-ERR_MANAGED_OBJECT_DECODING_EXCEPTION_SINGLE_100]
ID: 100::
Severity: ERROR

+
Message: The %s could not be decoded due to the following reason: %s.

[#log-ref-log-ref-ERR_MANAGED_OBJECT_DECODING_EXCEPTION_PLURAL_101]
ID: 101::
Severity: ERROR

+
Message: The %s could not be decoded due to the following reasons: %s.

[#log-ref-log-ref-ERR_ILLEGAL_MANAGED_OBJECT_NAME_EXCEPTION_EMPTY_102]
ID: 102::
Severity: ERROR

+
Message: Empty managed object names are not permitted.

[#log-ref-log-ref-ERR_ILLEGAL_MANAGED_OBJECT_NAME_EXCEPTION_BLANK_103]
ID: 103::
Severity: ERROR

+
Message: Blank managed object names are not permitted.

[#log-ref-log-ref-ERR_ILLEGAL_MANAGED_OBJECT_NAME_EXCEPTION_SYNTAX_104]
ID: 104::
Severity: ERROR

+
Message: The managed object name "%s" is not a valid value for the naming property "%s", which must have the following syntax: %s.

[#log-ref-log-ref-ERR_ILLEGAL_MANAGED_OBJECT_NAME_EXCEPTION_OTHER_105]
ID: 105::
Severity: ERROR

+
Message: The managed object name "%s" is not permitted.

[#log-ref-log-ref-ERR_MANAGED_OBJECT_ALREADY_EXISTS_EXCEPTION_106]
ID: 106::
Severity: ERROR

+
Message: The managed object could not be created because there is an existing managed object with the same name.

[#log-ref-log-ref-ERR_MANAGED_OBJECT_NOT_FOUND_EXCEPTION_107]
ID: 107::
Severity: ERROR

+
Message: The requested managed object could not be found.

[#log-ref-log-ref-ERR_MISSING_MANDATORY_PROPERTIES_EXCEPTION_SINGLE_108]
ID: 108::
Severity: ERROR

+
Message: The "%s" property is mandatory.

[#log-ref-log-ref-ERR_MISSING_MANDATORY_PROPERTIES_EXCEPTION_PLURAL_109]
ID: 109::
Severity: ERROR

+
Message: The following properties are mandatory: %s.

[#log-ref-log-ref-ERR_PROPERTY_NOT_FOUND_EXCEPTION_110]
ID: 110::
Severity: ERROR

+
Message: The property "%s" was not recognized.

[#log-ref-log-ref-ERR_COMMUNICATION_EXCEPTION_DEFAULT_CAUSE_111]
ID: 111::
Severity: ERROR

+
Message: A communication problem occurred while contacting the server: %s.

[#log-ref-log-ref-ERR_CONSTRAINT_VIOLATION_EXCEPTION_SINGLE_112]
ID: 112::
Severity: ERROR

+
Message: The following constraint violation occurred: %s.

[#log-ref-log-ref-ERR_CONSTRAINT_VIOLATION_EXCEPTION_PLURAL_113]
ID: 113::
Severity: ERROR

+
Message: The following constraint violations occurred: %s.

[#log-ref-log-ref-ERR_SERVER_REFINT_DANGLING_REFERENCE_114]
ID: 114::
Severity: ERROR

+
Message: The value "%s" in property "%s" in the %s in entry "%s" refers to a non-existent %s in entry "%s".

[#log-ref-log-ref-ERR_SERVER_REFINT_TARGET_DISABLED_116]
ID: 116::
Severity: ERROR

+
Message: The value "%s" in property "%s" in the %s in entry "%s" refers to a disabled %s in entry "%s".

[#log-ref-log-ref-ERR_SERVER_REFINT_CANNOT_DELETE_117]
ID: 117::
Severity: ERROR

+
Message: The %s in entry "%s" cannot be deleted because it is referenced by the "%s" property of the %s in entry "%s".

[#log-ref-log-ref-ERR_SERVER_REFINT_CANNOT_DISABLE_118]
ID: 118::
Severity: ERROR

+
Message: The %s in entry "%s" cannot be disabled because it is referenced by the "%s" property of the %s in entry "%s".

[#log-ref-log-ref-ERR_CLASS_LOADER_CANNOT_READ_MANIFEST_FILE_120]
ID: 120::
Severity: ERROR

+
Message: An unexpected error occurred while reading the manifest file: %s.

[#log-ref-log-ref-ERR_CLASS_LOADER_CANNOT_LOAD_CLASS_121]
ID: 121::
Severity: ERROR

+
Message: An error occurred while attempting to load class "%s": %s.

[#log-ref-log-ref-ERR_CLASS_LOADER_CANNOT_FIND_GET_INSTANCE_METHOD_122]
ID: 122::
Severity: ERROR

+
Message: Unable to to find the getInstance() method in the managed object definition class "%s": %s.

[#log-ref-log-ref-ERR_CLASS_LOADER_CANNOT_INVOKE_GET_INSTANCE_METHOD_123]
ID: 123::
Severity: ERROR

+
Message: Unable to to invoke the getInstance() method in the managed object definition class "%s": %s.

[#log-ref-log-ref-ERR_CLASS_LOADER_CANNOT_INITIALIZE_DEFN_124]
ID: 124::
Severity: ERROR

+
Message: Unable initialize the "%s" managed object definition in class "%s": %s.

[#log-ref-log-ref-ERR_CLASS_LOADER_CANNOT_LOAD_EXTENSION_125]
ID: 125::
Severity: ERROR

+
Message: The extension "%s" with manifest file %s cannot be loaded because an unexpected error occurred while trying to initialize it: %s.

[#log-ref-log-ref-ERR_CLASS_LOADER_CANNOT_LOAD_CORE_126]
ID: 126::
Severity: ERROR

+
Message: The core administration classes could not be loaded from manifest file %s because an unexpected error occurred: %s.

[#log-ref-log-ref-ERR_CLIENT_REFINT_TARGET_DANGLING_REFERENCE_127]
ID: 127::
Severity: ERROR

+
Message: The %s "%s" referenced in property "%s" does not exist.

[#log-ref-log-ref-ERR_CLIENT_REFINT_TARGET_INVALID_128]
ID: 128::
Severity: ERROR

+
Message: The %s "%s" referenced in property "%s" exists but has an invalid configuration: %s.

[#log-ref-log-ref-ERR_CLIENT_REFINT_TARGET_DISABLED_129]
ID: 129::
Severity: ERROR

+
Message: The %s "%s" referenced in property "%s" is disabled.

[#log-ref-log-ref-ERR_CLIENT_REFINT_CANNOT_DELETE_WITH_NAME_130]
ID: 130::
Severity: ERROR

+
Message: The "%s" property in the %s called "%s" references this %s.

[#log-ref-log-ref-ERR_CLIENT_REFINT_CANNOT_DELETE_WITHOUT_NAME_131]
ID: 131::
Severity: ERROR

+
Message: The "%s" property in the %s references this %s.

[#log-ref-log-ref-ERR_CLIENT_REFINT_CANNOT_DISABLE_WITH_NAME_132]
ID: 132::
Severity: ERROR

+
Message: This %s cannot be disabled because it is referenced by the "%s" property in the %s called "%s".

[#log-ref-log-ref-ERR_CLIENT_REFINT_CANNOT_DISABLE_WITHOUT_NAME_133]
ID: 133::
Severity: ERROR

+
Message: This %s cannot be disabled because it is referenced by the "%s" property in the %s.

[#log-ref-log-ref-ERR_REFINT_UNABLE_TO_EVALUATE_TARGET_CONDITION_134]
ID: 134::
Severity: ERROR

+
Message: An error occurred while attempting to determine if the %s in entry %s is enabled: %s.

[#log-ref-log-ref-ERR_ADMIN_CERTIFICATE_GENERATION_135]
ID: 135::
Severity: ERROR

+
Message: The administration connector self-signed certificate cannot be generated because the following error occurred: %s.

[#log-ref-log-ref-ERR_ADMIN_CERTIFICATE_GENERATION_MISSING_FILES_136]
ID: 136::
Severity: ERROR

+
Message: The administration connector self-signed certificate cannot be generated because the following files are missing: %s.

--


[#ADMIN_TOOL]
=== Log Message Category: ADMIN_TOOL

--

[#log-ref-log-ref-ERR_BACKEND_ALREADY]
ID: N/A::
Severity: ERROR

+
Message: There is already an existing backend with name: %s.

--


[#BACKEND]
=== Log Message Category: BACKEND

--

[#log-ref-log-ref-ERR_ROOTDSE_CONFIG_ENTRY_NULL_2]
ID: 2::
Severity: ERROR

+
Message: An attempt was made to configure the root DSE backend without providing a configuration entry. This is not allowed.

[#log-ref-log-ref-ERR_ROOTDSE_MODIFY_NOT_SUPPORTED_9]
ID: 9::
Severity: ERROR

+
Message: Unwilling to update entry "%s" because modify operations are not supported in the root DSE backend. If you wish to alter the contents of the root DSE itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

[#log-ref-log-ref-ERR_ROOTDSE_INVALID_SEARCH_BASE_11]
ID: 11::
Severity: ERROR

+
Message: Unwilling to perform a search (connection ID %d, operation ID %d) with a base DN of "%s" in the root DSE backend. The base DN for searches in this backend must be the DN of the root DSE itself.

[#log-ref-log-ref-ERR_ROOTDSE_UNEXPECTED_SEARCH_FAILURE_12]
ID: 12::
Severity: ERROR

+
Message: An unexpected failure occurred while trying to process a search operation (connection ID %d, operation ID %d) in the root DSE backend: %s.

[#log-ref-log-ref-ERR_ROOTDSE_INVALID_SEARCH_SCOPE_13]
ID: 13::
Severity: ERROR

+
Message: Unable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %s.

[#log-ref-log-ref-ERR_ROOTDSE_UNABLE_TO_CREATE_LDIF_WRITER_14]
ID: 14::
Severity: ERROR

+
Message: An unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %s.

[#log-ref-log-ref-ERR_ROOTDSE_UNABLE_TO_EXPORT_DSE_15]
ID: 15::
Severity: ERROR

+
Message: An unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %s.

[#log-ref-log-ref-ERR_ROOTDSE_BACKUP_AND_RESTORE_NOT_SUPPORTED_17]
ID: 17::
Severity: ERROR

+
Message: The root DSE backend does not provide a facility for backup and restore operations. The contents of the root DSE should be backed up as part of the Directory Server configuration.

[#log-ref-log-ref-ERR_MONITOR_CONFIG_ENTRY_NULL_21]
ID: 21::
Severity: ERROR

+
Message: An attempt was made to configure the monitor backend without providing a configuration entry. This is not allowed, and no monitor information will be available over protocol.

[#log-ref-log-ref-ERR_MONITOR_CANNOT_DECODE_MONITOR_ROOT_DN_22]
ID: 22::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to decode cn=monitor as the base DN for the Directory Server monitor information: %s. No monitor information will be available over protocol.

[#log-ref-log-ref-ERR_BACKEND_ADD_NOT_SUPPORTED_23]
ID: 23::
Severity: ERROR

+
Message: Unwilling to add entry "%s" because add operations are not supported in the "%s" backend.

[#log-ref-log-ref-ERR_BACKEND_DELETE_NOT_SUPPORTED_24]
ID: 24::
Severity: ERROR

+
Message: Unwilling to remove entry "%s" because delete operations are not supported in the "%s" backend.

[#log-ref-log-ref-ERR_MONITOR_MODIFY_NOT_SUPPORTED_25]
ID: 25::
Severity: ERROR

+
Message: Unwilling to update entry "%s" because modify operations are not supported in the monitor backend. If you wish to alter the contents of the base monitor entry itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

[#log-ref-log-ref-ERR_BACKEND_MODIFY_DN_NOT_SUPPORTED_26]
ID: 26::
Severity: ERROR

+
Message: Unwilling to rename entry "%s" because modify DN operations are not supported in the "%s" backend.

[#log-ref-log-ref-ERR_MONITOR_UNABLE_TO_EXPORT_BASE_27]
ID: 27::
Severity: ERROR

+
Message: An error occurred while attempting to export the base monitor entry: %s.

[#log-ref-log-ref-ERR_MONITOR_UNABLE_TO_EXPORT_PROVIDER_ENTRY_28]
ID: 28::
Severity: ERROR

+
Message: An error occurred while attempting to export the monitor entry for monitor provider %s: %s.

[#log-ref-log-ref-ERR_BACKEND_IMPORT_NOT_SUPPORTED_29]
ID: 29::
Severity: ERROR

+
Message: The "%s" backend does not support LDIF import operations.

[#log-ref-log-ref-ERR_BACKEND_GET_ENTRY_NULL_32]
ID: 32::
Severity: ERROR

+
Message: Unable to retrieve the requested entry from the "%s" backend because the provided DN was null.

[#log-ref-log-ref-ERR_BACKEND_CANNOT_DECODE_BACKEND_ROOT_DN_33]
ID: 33::
Severity: ERROR

+
Message: Unable to initialize the "%s" backend because an error occurred while attempting to decode the base DN for this backend: %s.

[#log-ref-log-ref-ERR_MONITOR_INVALID_BASE_34]
ID: 34::
Severity: ERROR

+
Message: Unable to retrieve the requested entry %s from the monitor backend because the DN is not below the monitor base of %s.

[#log-ref-log-ref-ERR_SCHEMA_CONFIG_ENTRY_NULL_38]
ID: 38::
Severity: ERROR

+
Message: An attempt was made to configure the schema backend without providing a configuration entry. This is not allowed, and no schema information will be available over protocol.

[#log-ref-log-ref-ERR_SCHEMA_CANNOT_DETERMINE_BASE_DN_40]
ID: 40::
Severity: ERROR

+
Message: An error occurred while trying to determine the base DNs to use when publishing the Directory Server schema information, as specified in the ds-cfg-schema-entry-dn attribute of configuration entry %s: %s. The default schema base DN of cn=schema will be used.

[#log-ref-log-ref-ERR_SCHEMA_UNABLE_TO_EXPORT_BASE_45]
ID: 45::
Severity: ERROR

+
Message: An error occurred while attempting to export the base schema entry: %s.

[#log-ref-log-ref-ERR_SCHEMA_INVALID_BASE_48]
ID: 48::
Severity: ERROR

+
Message: Unable to retrieve the requested entry %s from the schema backend because the DN is equal to one of the schema entry DNs.

[#log-ref-log-ref-ERR_SCHEMA_UNABLE_TO_CREATE_LDIF_WRITER_49]
ID: 49::
Severity: ERROR

+
Message: An unexpected error occurred while trying to open the LDIF writer for the schema backend: %s.

[#log-ref-log-ref-ERR_SCHEMA_CANNOT_DEREGISTER_BASE_DN_51]
ID: 51::
Severity: ERROR

+
Message: An error occurred while trying to deregister %s as a schema entry DN: %s.

[#log-ref-log-ref-ERR_SCHEMA_CANNOT_REGISTER_BASE_DN_53]
ID: 53::
Severity: ERROR

+
Message: An error occurred while trying to register %s as a schema entry DN: %s.

[#log-ref-log-ref-ERR_BACKEND_CANNOT_LOCK_ENTRY_55]
ID: 55::
Severity: ERROR

+
Message: The Directory Server was unable to obtain a lock on entry %s after multiple attempts. This could mean that the entry is already locked by a long-running operation or that the entry has previously been locked but was not properly unlocked.

[#log-ref-log-ref-ERR_TASK_INVALID_STATE_91]
ID: 91::
Severity: ERROR

+
Message: The task defined in entry %s is invalid because it has an invalid state %s.

[#log-ref-log-ref-ERR_TASK_CANNOT_PARSE_SCHEDULED_START_TIME_92]
ID: 92::
Severity: ERROR

+
Message: An error occurred while trying to parse the scheduled start time value %s from task entry %s.

[#log-ref-log-ref-ERR_TASK_CANNOT_PARSE_ACTUAL_START_TIME_93]
ID: 93::
Severity: ERROR

+
Message: An error occurred while trying to parse the actual start time value %s from task entry %s.

[#log-ref-log-ref-ERR_TASK_CANNOT_PARSE_COMPLETION_TIME_94]
ID: 94::
Severity: ERROR

+
Message: An error occurred while trying to parse the completion time value %s from task entry %s.

[#log-ref-log-ref-ERR_TASK_MISSING_ATTR_95]
ID: 95::
Severity: ERROR

+
Message: Task entry %s is missing required attribute %s.

[#log-ref-log-ref-ERR_TASK_MULTIPLE_ATTRS_FOR_TYPE_96]
ID: 96::
Severity: ERROR

+
Message: There are multiple instances of attribute %s in task entry %s.

[#log-ref-log-ref-ERR_TASK_NO_VALUES_FOR_ATTR_97]
ID: 97::
Severity: ERROR

+
Message: There are no values for attribute %s in task entry %s.

[#log-ref-log-ref-ERR_TASK_MULTIPLE_VALUES_FOR_ATTR_98]
ID: 98::
Severity: ERROR

+
Message: There are multiple values for attribute %s in task entry %s.

[#log-ref-log-ref-ERR_TASK_EXECUTE_FAILED_99]
ID: 99::
Severity: ERROR

+
Message: An error occurred while executing the task defined in entry %s: %s.

[#log-ref-log-ref-ERR_RECURRINGTASK_NO_ID_ATTRIBUTE_100]
ID: 100::
Severity: ERROR

+
Message: The provided recurring task entry does not contain attribute %s which is needed to hold the recurring task ID.

[#log-ref-log-ref-ERR_RECURRINGTASK_MULTIPLE_ID_TYPES_101]
ID: 101::
Severity: ERROR

+
Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold the recurring task ID, but only a single instance is allowed.

[#log-ref-log-ref-ERR_RECURRINGTASK_NO_ID_102]
ID: 102::
Severity: ERROR

+
Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task ID.

[#log-ref-log-ref-ERR_RECURRINGTASK_MULTIPLE_ID_VALUES_103]
ID: 103::
Severity: ERROR

+
Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the recurring task ID, but only a single value is allowed.

[#log-ref-log-ref-ERR_RECURRINGTASK_NO_SCHEDULE_ATTRIBUTE_104]
ID: 104::
Severity: ERROR

+
Message: The provided recurring task entry does not contain attribute %s which is needed to specify recurring task schedule.

[#log-ref-log-ref-ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_TYPES_105]
ID: 105::
Severity: ERROR

+
Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold recurring task schedule, but only a single instance is allowed.

[#log-ref-log-ref-ERR_RECURRINGTASK_NO_SCHEDULE_VALUES_106]
ID: 106::
Severity: ERROR

+
Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task schedule.

[#log-ref-log-ref-ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_VALUES_107]
ID: 107::
Severity: ERROR

+
Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify recurring task schedule, but only a single value is allowed.

[#log-ref-log-ref-ERR_RECURRINGTASK_CANNOT_LOAD_CLASS_108]
ID: 108::
Severity: ERROR

+
Message: An error occurred while attempting to load class %s specified in attribute %s of the provided recurring task entry: %s. Does this class exist in the Directory Server classpath?.

[#log-ref-log-ref-ERR_RECURRINGTASK_CANNOT_INSTANTIATE_CLASS_AS_TASK_109]
ID: 109::
Severity: ERROR

+
Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

[#log-ref-log-ref-ERR_RECURRINGTASK_CANNOT_INITIALIZE_INTERNAL_110]
ID: 110::
Severity: ERROR

+
Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

[#log-ref-log-ref-ERR_TASKBE_NO_BASE_DNS_112]
ID: 112::
Severity: ERROR

+
Message: The task backend configuration entry does not contain any base DNs. There must be exactly one base DN for task information in the Directory Server.

[#log-ref-log-ref-ERR_TASKBE_MULTIPLE_BASE_DNS_113]
ID: 113::
Severity: ERROR

+
Message: The task backend configuration entry contains multiple base DNs. There must be exactly one base DN for task information in the Directory Server.

[#log-ref-log-ref-ERR_TASKBE_CANNOT_DECODE_RECURRING_TASK_BASE_DN_114]
ID: 114::
Severity: ERROR

+
Message: An error occurred while attempting to decode recurring task base %s as a DN: %s.

[#log-ref-log-ref-ERR_TASKBE_CANNOT_DECODE_SCHEDULED_TASK_BASE_DN_115]
ID: 115::
Severity: ERROR

+
Message: An error occurred while attempting to decode scheduled task base %s as a DN: %s.

[#log-ref-log-ref-ERR_TASKBE_BACKING_FILE_EXISTS_121]
ID: 121::
Severity: ERROR

+
Message: The specified task data backing file %s already exists and the Directory Server will not attempt to overwrite it. Please delete or rename the existing file before attempting to use that path for the new backing file, or choose a new path.

[#log-ref-log-ref-ERR_TASKBE_INVALID_BACKING_FILE_PATH_122]
ID: 122::
Severity: ERROR

+
Message: The specified path %s for the new task data backing file appears to be an invalid path. Please choose a new path for the task data backing file.

[#log-ref-log-ref-ERR_TASKBE_BACKING_FILE_MISSING_PARENT_123]
ID: 123::
Severity: ERROR

+
Message: The parent directory %s for the new task data backing file %s does not exist. Please create this directory before attempting to use this path for the new backing file or choose a new path.

[#log-ref-log-ref-ERR_TASKBE_BACKING_FILE_PARENT_NOT_DIRECTORY_124]
ID: 124::
Severity: ERROR

+
Message: The parent directory %s for the new task data backing file %s exists but is not a directory. Please choose a new path for the task data backing file.

[#log-ref-log-ref-ERR_TASKBE_ERROR_GETTING_BACKING_FILE_125]
ID: 125::
Severity: ERROR

+
Message: An error occurred while attempting to determine the new path to the task data backing file: %s.

[#log-ref-log-ref-ERR_TASKBE_ADD_DISALLOWED_DN_130]
ID: 130::
Severity: ERROR

+
Message: New entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasks.

[#log-ref-log-ref-ERR_TASKSCHED_DUPLICATE_RECURRING_ID_133]
ID: 133::
Severity: ERROR

+
Message: Unable to add recurring task %s to the task scheduler because another recurring task already exists with the same ID.

[#log-ref-log-ref-ERR_TASKSCHED_DUPLICATE_TASK_ID_134]
ID: 134::
Severity: ERROR

+
Message: Unable to schedule task %s because another task already exists with the same ID.

[#log-ref-log-ref-ERR_TASKSCHED_ERROR_SCHEDULING_RECURRING_ITERATION_136]
ID: 136::
Severity: ERROR

+
Message: An error occurred while attempting to schedule the next iteration of recurring task %s: %s.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_PARSE_ENTRY_RECOVERABLE_137]
ID: 137::
Severity: ERROR

+
Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is not a fatal error, so the task scheduler will attempt to continue parsing the file and schedule any additional tasks that it contains.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_PARSE_ENTRY_FATAL_138]
ID: 138::
Severity: ERROR

+
Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is an unrecoverable error, and parsing cannot continue.

[#log-ref-log-ref-ERR_TASKSCHED_ENTRY_HAS_NO_PARENT_139]
ID: 139::
Severity: ERROR

+
Message: Entry %s read from the tasks backing file is invalid because it has no parent and does not match the task root DN of %s.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_SCHEDULE_RECURRING_TASK_FROM_ENTRY_140]
ID: 140::
Severity: ERROR

+
Message: An error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %s.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_SCHEDULE_TASK_FROM_ENTRY_141]
ID: 141::
Severity: ERROR

+
Message: An error occurred while attempting to parse entry %s as a task and add it to the scheduler: %s.

[#log-ref-log-ref-ERR_TASKSCHED_INVALID_TASK_ENTRY_DN_142]
ID: 142::
Severity: ERROR

+
Message: Entry %s read from the tasks backing file %s has a DN which is not valid for a task or recurring task definition and will be ignored.

[#log-ref-log-ref-ERR_TASKSCHED_ERROR_READING_TASK_BACKING_FILE_143]
ID: 143::
Severity: ERROR

+
Message: An error occurred while attempting to read from the tasks data backing file %s: %s.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_CREATE_BACKING_FILE_144]
ID: 144::
Severity: ERROR

+
Message: An error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %s.

[#log-ref-log-ref-ERR_TASKSCHED_NO_CLASS_ATTRIBUTE_145]
ID: 145::
Severity: ERROR

+
Message: The provided task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logic.

[#log-ref-log-ref-ERR_TASKSCHED_MULTIPLE_CLASS_TYPES_146]
ID: 146::
Severity: ERROR

+
Message: The provided task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowed.

[#log-ref-log-ref-ERR_TASKSCHED_NO_CLASS_VALUES_147]
ID: 147::
Severity: ERROR

+
Message: The provided task entry does not contain any values for the %s attribute, which is used to specify the fully-qualified name of the class providing the task logic.

[#log-ref-log-ref-ERR_TASKSCHED_MULTIPLE_CLASS_VALUES_148]
ID: 148::
Severity: ERROR

+
Message: The provided task entry contains multiple values for the %s attribute, which is used to specify the task class name, but only a single value is allowed.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_LOAD_CLASS_149]
ID: 149::
Severity: ERROR

+
Message: An error occurred while attempting to load class %s specified in attribute %s of the provided task entry: %s. Does this class exist in the Directory Server classpath?.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_INSTANTIATE_CLASS_AS_TASK_150]
ID: 150::
Severity: ERROR

+
Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_INITIALIZE_INTERNAL_151]
ID: 151::
Severity: ERROR

+
Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_RENAME_NEW_BACKING_FILE_153]
ID: 153::
Severity: ERROR

+
Message: An error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not work as expected.

[#log-ref-log-ref-ERR_TASKSCHED_CANNOT_WRITE_BACKING_FILE_154]
ID: 154::
Severity: ERROR

+
Message: An error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lost.

[#log-ref-log-ref-ERR_TASKSCHED_REMOVE_PENDING_NO_SUCH_TASK_161]
ID: 161::
Severity: ERROR

+
Message: Unable to remove pending task %s because no such task exists.

[#log-ref-log-ref-ERR_TASKSCHED_REMOVE_PENDING_NOT_PENDING_162]
ID: 162::
Severity: ERROR

+
Message: Unable to remove pending task %s because the task is no longer pending.

[#log-ref-log-ref-ERR_TASKSCHED_REMOVE_COMPLETED_NO_SUCH_TASK_163]
ID: 163::
Severity: ERROR

+
Message: Unable to remove completed task %s because no such task exists in the list of completed tasks.

[#log-ref-log-ref-ERR_TASKBE_DELETE_INVALID_ENTRY_164]
ID: 164::
Severity: ERROR

+
Message: Unable to remove entry %s from the task backend because its DN is either not appropriate for that backend or it is not below the scheduled or recurring tasks base entry.

[#log-ref-log-ref-ERR_TASKBE_DELETE_NO_SUCH_TASK_165]
ID: 165::
Severity: ERROR

+
Message: Unable to remove entry %s from the task backend because there is no scheduled task associated with that entry DN.

[#log-ref-log-ref-ERR_TASKBE_DELETE_RUNNING_166]
ID: 166::
Severity: ERROR

+
Message: Unable to delete entry %s from the task backend because the associated task is currently running.

[#log-ref-log-ref-ERR_TASKBE_DELETE_NO_SUCH_RECURRING_TASK_167]
ID: 167::
Severity: ERROR

+
Message: Unable to remove entry %s from the task backend because there is no recurring task associated with that entry DN.

[#log-ref-log-ref-ERR_TASKBE_SEARCH_INVALID_BASE_168]
ID: 168::
Severity: ERROR

+
Message: Unable to process the search operation in the task backend because the provided base DN %s is not valid for entries in the task backend.

[#log-ref-log-ref-ERR_TASKBE_SEARCH_NO_SUCH_TASK_169]
ID: 169::
Severity: ERROR

+
Message: Unable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %s.

[#log-ref-log-ref-ERR_TASKBE_SEARCH_NO_SUCH_RECURRING_TASK_170]
ID: 170::
Severity: ERROR

+
Message: Unable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %s.

[#log-ref-log-ref-ERR_BACKEND_CONFIG_ENTRY_NULL_171]
ID: 171::
Severity: ERROR

+
Message: Unable to initialize the "%s" backend because the provided configuration entry is null.

[#log-ref-log-ref-ERR_BACKUP_INVALID_BASE_176]
ID: 176::
Severity: ERROR

+
Message: Requested entry %s does not exist in the backup backend.

[#log-ref-log-ref-ERR_BACKUP_DN_DOES_NOT_SPECIFY_DIRECTORY_177]
ID: 177::
Severity: ERROR

+
Message: Unable to retrieve entry %s from the backup backend because the requested DN is one level below the base DN but does not specify a backup directory.

[#log-ref-log-ref-ERR_BACKUP_INVALID_BACKUP_DIRECTORY_178]
ID: 178::
Severity: ERROR

+
Message: Unable to retrieve entry %s from the backup backend because the requested backup directory is invalid: %s.

[#log-ref-log-ref-ERR_BACKUP_ERROR_GETTING_BACKUP_DIRECTORY_179]
ID: 179::
Severity: ERROR

+
Message: An error occurred while attempting to examine the requested backup directory: %s.

[#log-ref-log-ref-ERR_BACKUP_NO_BACKUP_ID_IN_DN_180]
ID: 180::
Severity: ERROR

+
Message: Unable to retrieve entry %s from the backup backend because the requested DN is two levels below the base DN but does not specify a backup ID.

[#log-ref-log-ref-ERR_BACKUP_NO_BACKUP_PARENT_DN_181]
ID: 181::
Severity: ERROR

+
Message: Unable to retrieve entry %s from the backup backend because it does not have a parent.

[#log-ref-log-ref-ERR_BACKUP_NO_BACKUP_DIR_IN_DN_182]
ID: 182::
Severity: ERROR

+
Message: Unable to retrieve entry %s from the backup backend because the DN does not contain the backup directory in which the requested backup should reside.

[#log-ref-log-ref-ERR_BACKUP_NO_SUCH_BACKUP_183]
ID: 183::
Severity: ERROR

+
Message: Backup %s does not exist in backup directory %s.

[#log-ref-log-ref-ERR_BACKEND_MODIFY_NOT_SUPPORTED_186]
ID: 186::
Severity: ERROR

+
Message: Unwilling to update entry "%s" because modify operations are not supported in the "%s" backend.

[#log-ref-log-ref-ERR_BACKUP_NO_SUCH_ENTRY_188]
ID: 188::
Severity: ERROR

+
Message: The requested entry %s does not exist in the backup backend.

[#log-ref-log-ref-ERR_MEMORYBACKEND_REQUIRE_EXACTLY_ONE_BASE_192]
ID: 192::
Severity: ERROR

+
Message: Exactly one base DN must be provided for use with the memory-based backend.

[#log-ref-log-ref-ERR_MEMORYBACKEND_ENTRY_ALREADY_EXISTS_193]
ID: 193::
Severity: ERROR

+
Message: Entry %s already exists in the memory-based backend.

[#log-ref-log-ref-ERR_MEMORYBACKEND_ENTRY_DOESNT_BELONG_194]
ID: 194::
Severity: ERROR

+
Message: Entry %s does not belong in the memory-based backend.

[#log-ref-log-ref-ERR_MEMORYBACKEND_PARENT_DOESNT_EXIST_195]
ID: 195::
Severity: ERROR

+
Message: Unable to add entry %s because its parent entry %s does not exist in the memory-based backend.

[#log-ref-log-ref-ERR_BACKEND_ENTRY_DOESNT_EXIST_196]
ID: 196::
Severity: ERROR

+
Message: Entry %s does not exist in the "%s" backend.

[#log-ref-log-ref-ERR_MEMORYBACKEND_CANNOT_DELETE_ENTRY_WITH_CHILDREN_197]
ID: 197::
Severity: ERROR

+
Message: Cannot delete entry %s because it has one or more subordinate entries.

[#log-ref-log-ref-ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_WRITER_199]
ID: 199::
Severity: ERROR

+
Message: Unable to create an LDIF writer: %s.

[#log-ref-log-ref-ERR_MEMORYBACKEND_CANNOT_WRITE_ENTRY_TO_LDIF_200]
ID: 200::
Severity: ERROR

+
Message: Cannot write entry %s to LDIF: %s.

[#log-ref-log-ref-ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_READER_201]
ID: 201::
Severity: ERROR

+
Message: Unable to create an LDIF reader: %s.

[#log-ref-log-ref-ERR_MEMORYBACKEND_ERROR_READING_LDIF_202]
ID: 202::
Severity: ERROR

+
Message: An unrecoverable error occurred while reading from LDIF: %s.

[#log-ref-log-ref-ERR_MEMORYBACKEND_ERROR_DURING_IMPORT_203]
ID: 203::
Severity: ERROR

+
Message: An unexpected error occurred while processing the import: %s.

[#log-ref-log-ref-ERR_MEMORYBACKEND_BACKUP_RESTORE_NOT_SUPPORTED_204]
ID: 204::
Severity: ERROR

+
Message: The memory-based backend does not support backup or restore operations.

[#log-ref-log-ref-ERR_MEMORYBACKEND_CANNOT_RENAME_ENRY_WITH_CHILDREN_205]
ID: 205::
Severity: ERROR

+
Message: Cannot rename entry %s because it has one or more subordinate entries.

[#log-ref-log-ref-ERR_MEMORYBACKEND_CANNOT_RENAME_TO_ANOTHER_BACKEND_206]
ID: 206::
Severity: ERROR

+
Message: Cannot rename entry %s because the target entry is in a different backend.

[#log-ref-log-ref-ERR_MEMORYBACKEND_RENAME_PARENT_DOESNT_EXIST_207]
ID: 207::
Severity: ERROR

+
Message: Cannot rename entry %s because the new parent entry %s doesn't exist.

[#log-ref-log-ref-ERR_BACKEND_CANNOT_REGISTER_BASEDN_210]
ID: 210::
Severity: ERROR

+
Message: An error occurred while attempting to register base DN %s in the Directory Server: %s.

[#log-ref-log-ref-ERR_SCHEMA_INVALID_MODIFICATION_TYPE_212]
ID: 212::
Severity: ERROR

+
Message: The schema backend does not support the %s modification type.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_UNSUPPORTED_ATTRIBUTE_TYPE_213]
ID: 213::
Severity: ERROR

+
Message: The schema backend does not support the modification of the %s attribute type. Only attribute types, object classes, ldap syntaxes, name forms, DIT content rules, DIT structure rules, and matching rule uses may be modified.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_DECODE_OBJECTCLASS_216]
ID: 216::
Severity: ERROR

+
Message: An error occurred while attempting to decode the object class "%s": %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_UNDEFINED_SUPERIOR_OBJECTCLASS_217]
ID: 217::
Severity: ERROR

+
Message: Unable to add objectclass %s because its superior class of %s is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_OC_UNDEFINED_REQUIRED_ATTR_218]
ID: 218::
Severity: ERROR

+
Message: Unable to add objectclass %s because it requires attribute %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_OC_UNDEFINED_OPTIONAL_ATTR_219]
ID: 219::
Severity: ERROR

+
Message: Unable to add objectclass %s because it allows attribute %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_SCHEMA_222]
ID: 222::
Severity: ERROR

+
Message: An error occurred while attempting to write the updated schema: %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_DECODE_NAME_FORM_223]
ID: 223::
Severity: ERROR

+
Message: An error occurred while attempting to decode the name form "%s": %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_DECODE_DCR_224]
ID: 224::
Severity: ERROR

+
Message: An error occurred while attempting to decode the DIT content rule "%s": %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_DECODE_DSR_225]
ID: 225::
Severity: ERROR

+
Message: An error occurred while attempting to decode the DIT structure rule "%s": %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_DECODE_MR_USE_226]
ID: 226::
Severity: ERROR

+
Message: An error occurred while attempting to decode the matching rule use "%s": %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DELETE_NO_VALUES_227]
ID: 227::
Severity: ERROR

+
Message: The server will not allow removing all values for the %s attribute type in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_ATTRTYPE_228]
ID: 228::
Severity: ERROR

+
Message: Unable to add attribute type %s because it conflicts with multiple existing attribute types (%s and %s).

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_OBJECTCLASS_230]
ID: 230::
Severity: ERROR

+
Message: Unable to add objectclass %s because it conflicts with multiple existing objectclasses (%s and %s).

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_NAME_FORM_231]
ID: 231::
Severity: ERROR

+
Message: Unable to add name form %s because it conflicts with multiple existing name forms (%s and %s).

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NF_UNDEFINED_STRUCTURAL_OC_232]
ID: 232::
Severity: ERROR

+
Message: Unable to add name form %s because it references structural objectclass %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NF_UNDEFINED_REQUIRED_ATTR_233]
ID: 233::
Severity: ERROR

+
Message: Unable to add name form %s because it references required attribute type %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NF_UNDEFINED_OPTIONAL_ATTR_234]
ID: 234::
Severity: ERROR

+
Message: Unable to add name form %s because it references optional attribute type %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_DCR_235]
ID: 235::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it conflicts with multiple existing DIT content rules (%s and %s).

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_STRUCTURAL_OC_CONFLICT_FOR_ADD_DCR_236]
ID: 236::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references structural objectclass %s which is already associated with another DIT content rule %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_UNDEFINED_STRUCTURAL_OC_237]
ID: 237::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references structural objectclass %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_UNDEFINED_AUXILIARY_OC_238]
ID: 238::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references auxiliary objectclass %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_UNDEFINED_REQUIRED_ATTR_239]
ID: 239::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references required attribute type %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_UNDEFINED_OPTIONAL_ATTR_240]
ID: 240::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references optional attribute type %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_UNDEFINED_PROHIBITED_ATTR_241]
ID: 241::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references prohibited attribute type %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_DSR_242]
ID: 242::
Severity: ERROR

+
Message: Unable to add DIT structure rule %s because it conflicts with multiple existing DIT structure rules (%s and %s).

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NAME_FORM_CONFLICT_FOR_ADD_DSR_243]
ID: 243::
Severity: ERROR

+
Message: Unable to add DIT structure rule %s because it references name form %s which is already associated with another DIT structure rule %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DSR_UNDEFINED_NAME_FORM_244]
ID: 244::
Severity: ERROR

+
Message: Unable to add DIT structure rule %s because it references name form %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_MR_USE_245]
ID: 245::
Severity: ERROR

+
Message: Unable to add matching rule use %s because it conflicts with multiple existing matching rule uses (%s and %s).

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MR_CONFLICT_FOR_ADD_MR_USE_246]
ID: 246::
Severity: ERROR

+
Message: Unable to add matching rule use %s because it references matching rule %s which is already associated with another matching rule use %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MRU_UNDEFINED_ATTR_247]
ID: 247::
Severity: ERROR

+
Message: Unable to add matching rule use %s because it references attribute type %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_AT_248]
ID: 248::
Severity: ERROR

+
Message: Circular reference detected for attribute type %s in which the superior type chain references the attribute type itself.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_OC_249]
ID: 249::
Severity: ERROR

+
Message: Circular reference detected for objectclass %s in which the superior class chain references the objectclass itself.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_DSR_250]
ID: 250::
Severity: ERROR

+
Message: Circular reference detected for DIT structure rule %s in which the superior rule chain references the DIT structure rule itself.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_CLEANED_251]
ID: 251::
Severity: ERROR

+
Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_NOT_CLEANED_252]
ID: 252::
Severity: ERROR

+
Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_RESTORED_253]
ID: 253::
Severity: ERROR

+
Message: An error occurred while attempting to write new versions of the server schema files: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_NOT_RESTORED_254]
ID: 254::
Severity: ERROR

+
Message: An error occurred while attempting to write new versions of the server schema files: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_ATTRIBUTE_TYPE_255]
ID: 255::
Severity: ERROR

+
Message: Unable to remove attribute type %s from the server schema because no such attribute type is defined.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_AT_SUPERIOR_TYPE_256]
ID: 256::
Severity: ERROR

+
Message: Unable to remove attribute type %s from the server schema because it is referenced as the superior type for attribute type %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_AT_IN_OC_257]
ID: 257::
Severity: ERROR

+
Message: Unable to remove attribute type %s from the server schema because it is referenced as a required or optional attribute type in objectclass %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_AT_IN_NF_258]
ID: 258::
Severity: ERROR

+
Message: Unable to remove attribute type %s from the server schema because it is referenced as a required or optional attribute type in name form %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_AT_IN_DCR_259]
ID: 259::
Severity: ERROR

+
Message: Unable to remove attribute type %s from the server schema because it is referenced as a required, optional, or prohibited attribute type in DIT content rule %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_AT_IN_MR_USE_260]
ID: 260::
Severity: ERROR

+
Message: Unable to remove attribute type %s from the server schema because it is referenced by matching rule use %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_OBJECTCLASS_261]
ID: 261::
Severity: ERROR

+
Message: Unable to remove objectclass %s from the server schema because no such objectclass is defined.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_OC_SUPERIOR_CLASS_262]
ID: 262::
Severity: ERROR

+
Message: Unable to remove objectclass %s from the server schema because it is referenced as the superior class for objectclass %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_OC_IN_NF_263]
ID: 263::
Severity: ERROR

+
Message: Unable to remove objectclass %s from the server schema because it is referenced as the structural class for name form %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_OC_IN_DCR_264]
ID: 264::
Severity: ERROR

+
Message: Unable to remove objectclass %s from the server schema because it is referenced as a structural or auxiliary class for DIT content rule %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_NAME_FORM_265]
ID: 265::
Severity: ERROR

+
Message: Unable to remove name form %s from the server schema because no such name form is defined.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NF_IN_DSR_266]
ID: 266::
Severity: ERROR

+
Message: Unable to remove name form %s from the server schema because it is referenced by DIT structure rule %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DCR_267]
ID: 267::
Severity: ERROR

+
Message: Unable to remove DIT content rule %s from the server schema because no such DIT content rule is defined.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DSR_268]
ID: 268::
Severity: ERROR

+
Message: Unable to remove DIT structure rule %s from the server schema because no such DIT structure rule is defined.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_DSR_SUPERIOR_RULE_269]
ID: 269::
Severity: ERROR

+
Message: Unable to remove DIT structure rule %s from the server schema because it is referenced as a superior rule for DIT structure rule %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_MR_USE_270]
ID: 270::
Severity: ERROR

+
Message: Unable to remove matching rule use %s from the server schema because no such matching rule use is defined.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NF_OC_NOT_STRUCTURAL_271]
ID: 271::
Severity: ERROR

+
Message: Unable to add name form %s because it references objectclass %s which is defined in the server schema but is not a structural objectclass.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_OC_NOT_STRUCTURAL_272]
ID: 272::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references structural objectclass %s which is defined in the server schema but is not structural.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_OBSOLETE_SUPERIOR_ATTRIBUTE_TYPE_274]
ID: 274::
Severity: ERROR

+
Message: Unable to add attribute type %s because the superior type %s is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_ATTRTYPE_OBSOLETE_MR_275]
ID: 275::
Severity: ERROR

+
Message: Unable to add attribute type %s because the associated matching rule %s is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_OBSOLETE_SUPERIOR_OBJECTCLASS_276]
ID: 276::
Severity: ERROR

+
Message: Unable to add object class %s because the superior class %s is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_OC_OBSOLETE_REQUIRED_ATTR_277]
ID: 277::
Severity: ERROR

+
Message: Unable to add object class %s because required attribute %s is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_OC_OBSOLETE_OPTIONAL_ATTR_278]
ID: 278::
Severity: ERROR

+
Message: Unable to add object class %s because optional attribute %s is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NF_OC_OBSOLETE_279]
ID: 279::
Severity: ERROR

+
Message: Unable to add name form %s because its structural object class %s is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NF_OBSOLETE_REQUIRED_ATTR_280]
ID: 280::
Severity: ERROR

+
Message: Unable to add name form %s because it requires attribute type %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_NF_OBSOLETE_OPTIONAL_ATTR_281]
ID: 281::
Severity: ERROR

+
Message: Unable to add name form %s because it allows attribute type %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_STRUCTURAL_OC_OBSOLETE_282]
ID: 282::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because its structural object class %s is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_OC_NOT_AUXILIARY_283]
ID: 283::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references auxiliary object class %s which is defined in the server schema but is not an auxiliary class.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_OBSOLETE_REQUIRED_ATTR_285]
ID: 285::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it requires attribute type %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_OBSOLETE_OPTIONAL_ATTR_286]
ID: 286::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it allows attribute type %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_OBSOLETE_PROHIBITED_ATTR_287]
ID: 287::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it prohibits attribute type %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DSR_OBSOLETE_NAME_FORM_288]
ID: 288::
Severity: ERROR

+
Message: Unable to add DIT structure rule %s because its name form %s is marked OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DSR_OBSOLETE_SUPERIOR_RULE_289]
ID: 289::
Severity: ERROR

+
Message: Unable to add DIT structure rule %s because it references superior rule %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MRU_OBSOLETE_MR_290]
ID: 290::
Severity: ERROR

+
Message: Unable to add matching rule use %s because its matching rule %s is marked OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MRU_OBSOLETE_ATTR_291]
ID: 291::
Severity: ERROR

+
Message: Unable to add matching rule use %s because it references attribute type %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_DCR_OBSOLETE_AUXILIARY_OC_292]
ID: 292::
Severity: ERROR

+
Message: Unable to add DIT content rule %s because it references auxiliary object class %s which is marked as OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_INSUFFICIENT_PRIVILEGES_293]
ID: 293::
Severity: ERROR

+
Message: You do not have sufficient privileges to modify the Directory Server schema.

[#log-ref-log-ref-ERR_SCHEMA_CANNOT_FIND_CONCAT_FILE_294]
ID: 294::
Severity: ERROR

+
Message: Unable to find a file containing concatenated schema element definitions in order to determine if any schema changes were made with the server offline. The file was expected in the %s directory and should have been named either %s or %s.

[#log-ref-log-ref-ERR_SCHEMA_ERROR_DETERMINING_SCHEMA_CHANGES_295]
ID: 295::
Severity: ERROR

+
Message: An error occurred while attempting to determine whether any schema changes had been made by directly editing the schema files with the server offline: %s.

[#log-ref-log-ref-ERR_SCHEMA_CANNOT_WRITE_CONCAT_SCHEMA_FILE_296]
ID: 296::
Severity: ERROR

+
Message: An error occurred while attempting to write file %s containing a concatenated list of all server schema elements: %s. The server may not be able to accurately identify any schema changes made with the server offline.

[#log-ref-log-ref-ERR_TASKSCHED_NOT_ALLOWED_TASK_298]
ID: 298::
Severity: ERROR

+
Message: The Directory Server is not configured to allow task %s to be invoked.

[#log-ref-log-ref-ERR_TRUSTSTORE_INVALID_BASE_301]
ID: 301::
Severity: ERROR

+
Message: Requested entry %s does not exist in the trust store backend.

[#log-ref-log-ref-ERR_TRUSTSTORE_DN_DOES_NOT_SPECIFY_CERTIFICATE_302]
ID: 302::
Severity: ERROR

+
Message: Unable to process entry %s in the trust store backend because the requested DN is one level below the base DN but does not specify a certificate name.

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_RETRIEVE_CERT_303]
ID: 303::
Severity: ERROR

+
Message: Error while trying to retrieve certificate %s from the trust store file %s: %s.

[#log-ref-log-ref-ERR_INDEXES_NOT_SUPPORTED_305]
ID: 305::
Severity: ERROR

+
Message: Indexes are not supported in the "%s" backend.

[#log-ref-log-ref-ERR_TRUSTSTORE_REQUIRES_ONE_BASE_DN_306]
ID: 306::
Severity: ERROR

+
Message: Unable to initialize the trust store backend from configuration entry %s because it does not contain exactly one base DN.

[#log-ref-log-ref-ERR_BACKEND_IMPORT_AND_EXPORT_NOT_SUPPORTED_307]
ID: 307::
Severity: ERROR

+
Message: LDIF import and export operations are not supported in the "%s" backend.

[#log-ref-log-ref-ERR_BACKEND_BACKUP_AND_RESTORE_NOT_SUPPORTED_308]
ID: 308::
Severity: ERROR

+
Message: Backup and restore operations are not supported in the "%s" backend.

[#log-ref-log-ref-ERR_TRUSTSTORE_NO_SUCH_FILE_309]
ID: 309::
Severity: ERROR

+
Message: The trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not exist.

[#log-ref-log-ref-ERR_TRUSTSTORE_INVALID_TYPE_310]
ID: 310::
Severity: ERROR

+
Message: The trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_PIN_FILE_CANNOT_CREATE_311]
ID: 311::
Severity: ERROR

+
Message: An error occurred while trying to create the PIN file %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_PIN_FILE_CANNOT_READ_312]
ID: 312::
Severity: ERROR

+
Message: An error occurred while trying to read the trust store PIN from file %s specified in configuration attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_PIN_FILE_EMPTY_313]
ID: 313::
Severity: ERROR

+
Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the trust store, but this file is empty.

[#log-ref-log-ref-ERR_TRUSTSTORE_PIN_ENVAR_NOT_SET_314]
ID: 314::
Severity: ERROR

+
Message: Environment variable %s which is specified in attribute ds-cfg-trust-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the trust store, but this property is not set.

[#log-ref-log-ref-ERR_TRUSTSTORE_PIN_PROPERTY_NOT_SET_315]
ID: 315::
Severity: ERROR

+
Message: Java property %s which is specified in attribute ds-cfg-trust-store-pin-property of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this property is not set.

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_DETERMINE_FILE_316]
ID: 316::
Severity: ERROR

+
Message: An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-trust-store-file in configuration entry %s: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_LOAD_317]
ID: 317::
Severity: ERROR

+
Message: An error occurred while trying to load the trust store contents from file %s: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_CREATE_FACTORY_318]
ID: 318::
Severity: ERROR

+
Message: An error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_ALIAS_IN_USE_319]
ID: 319::
Severity: ERROR

+
Message: The certificate entry %s already exists.

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_GENERATE_CERT_320]
ID: 320::
Severity: ERROR

+
Message: Error while attempting to generate a self-signed certificate %s in the trust store file %s: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_ADD_CERT_321]
ID: 321::
Severity: ERROR

+
Message: Error while trying to add certificate %s to the trust store file %s: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_ENTRY_MISSING_CERT_ATTR_323]
ID: 323::
Severity: ERROR

+
Message: The entry %s could not be added because it does not contain a certificate attribute %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_ENTRY_HAS_MULTIPLE_CERT_ATTRS_324]
ID: 324::
Severity: ERROR

+
Message: The entry %s could not be added because it contains multiple certificate attributes %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_ENTRY_MISSING_CERT_VALUE_325]
ID: 325::
Severity: ERROR

+
Message: The entry %s could not be added because it does not contain a value of certificate attribute %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_ENTRY_HAS_MULTIPLE_CERT_VALUES_326]
ID: 326::
Severity: ERROR

+
Message: The entry %s could not be added because it contains multiple values of certificate attribute %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_WRITE_CERT_327]
ID: 327::
Severity: ERROR

+
Message: Error while writing certificate %s to a file: %s.

[#log-ref-log-ref-ERR_ROOT_CONTAINER_NOT_INITIALIZED_329]
ID: 329::
Severity: ERROR

+
Message: The root container for backend %s has not been initialized preventing this backend from processing the requested operation.

[#log-ref-log-ref-ERR_TASKBE_MODIFY_CANNOT_LOCK_ENTRY_330]
ID: 330::
Severity: ERROR

+
Message: Unable to obtain a write lock on entry %s.

[#log-ref-log-ref-ERR_TASKBE_MODIFY_INVALID_ENTRY_331]
ID: 331::
Severity: ERROR

+
Message: Entry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backend.

[#log-ref-log-ref-ERR_TASKBE_MODIFY_NO_SUCH_TASK_332]
ID: 332::
Severity: ERROR

+
Message: Entry %s cannot be modified because it does not represent a valid task in the server.

[#log-ref-log-ref-ERR_TASKBE_MODIFY_COMPLETED_333]
ID: 333::
Severity: ERROR

+
Message: Entry %s cannot be modified because the assoicated task has completed running. Completed tasks cannot be modified.

[#log-ref-log-ref-ERR_TASKBE_MODIFY_RECURRING_334]
ID: 334::
Severity: ERROR

+
Message: Entry %s cannot be modified because the server does not currently support modifying recurring task entries.

[#log-ref-log-ref-ERR_TASKBE_MODIFY_RUNNING_335]
ID: 335::
Severity: ERROR

+
Message: The task associated with entry %s is currently running. The only modification allowed for running tasks is to replace the value of the ds-task-state attribute with "cancel".

[#log-ref-log-ref-ERR_TRUSTSTORE_CANNOT_DELETE_CERT_337]
ID: 337::
Severity: ERROR

+
Message: Error while trying to delete certificate %s from the trust store file %s: %s.

[#log-ref-log-ref-ERR_TRUSTSTORE_CERTIFICATE_NOT_FOUND_338]
ID: 338::
Severity: ERROR

+
Message: Unable to retrieve entry %s from the trust store backend because the certificate %s does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_MULTIPLE_BASE_DNS_339]
ID: 339::
Severity: ERROR

+
Message: The LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNs.

[#log-ref-log-ref-ERR_LDIF_BACKEND_DUPLICATE_ENTRY_342]
ID: 342::
Severity: ERROR

+
Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s has multiple entries with a DN of %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ENTRY_OUT_OF_SCOPE_343]
ID: 343::
Severity: ERROR

+
Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s includes entry %s which is not below the base DN defined for that backend.

[#log-ref-log-ref-ERR_LDIF_BACKEND_MISSING_PARENT_344]
ID: 344::
Severity: ERROR

+
Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s contains entry %s but its parent entry has not yet been read.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ERROR_CREATING_FILE_345]
ID: 345::
Severity: ERROR

+
Message: An error occurred while trying to create file %s to write an updated version of the data for the LDIF backend defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ERROR_WRITING_FILE_346]
ID: 346::
Severity: ERROR

+
Message: An error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ERROR_RENAMING_FILE_347]
ID: 347::
Severity: ERROR

+
Message: An error occurred while attempting to rename file %s to %s while writing updated data for the LDIF backend defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ADD_ALREADY_EXISTS_348]
ID: 348::
Severity: ERROR

+
Message: Entry %s already exists in the LDIF backend.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ADD_MISSING_PARENT_349]
ID: 349::
Severity: ERROR

+
Message: The parent for entry %s does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_DELETE_NO_SUCH_ENTRY_350]
ID: 350::
Severity: ERROR

+
Message: Entry %s does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_DELETE_NONLEAF_351]
ID: 351::
Severity: ERROR

+
Message: Entry %s has one or more subordinate entries and cannot be deleted until all of its subordinate entries are removed first.

[#log-ref-log-ref-ERR_LDIF_BACKEND_MODIFY_NO_SUCH_ENTRY_352]
ID: 352::
Severity: ERROR

+
Message: Entry %s does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_MODDN_NO_SUCH_SOURCE_ENTRY_353]
ID: 353::
Severity: ERROR

+
Message: Source entry %s does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_MODDN_TARGET_ENTRY_ALREADY_EXISTS_354]
ID: 354::
Severity: ERROR

+
Message: Target entry %s already exists.

[#log-ref-log-ref-ERR_LDIF_BACKEND_MODDN_NEW_PARENT_DOESNT_EXIST_355]
ID: 355::
Severity: ERROR

+
Message: The new parent DN %s does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_SEARCH_NO_SUCH_BASE_356]
ID: 356::
Severity: ERROR

+
Message: Entry %s specified as the search base DN does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_WRITER_357]
ID: 357::
Severity: ERROR

+
Message: An error occurred while trying to create the writer for the LDIF export operation: %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_CANNOT_WRITE_ENTRY_TO_LDIF_358]
ID: 358::
Severity: ERROR

+
Message: An error occurred while trying to write entry %s during the LDIF export: %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_READER_359]
ID: 359::
Severity: ERROR

+
Message: An error occurred while trying to create the reader for the LDIF import operation: %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ERROR_READING_LDIF_360]
ID: 360::
Severity: ERROR

+
Message: An unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continue.

[#log-ref-log-ref-ERR_LDIF_BACKEND_BACKUP_RESTORE_NOT_SUPPORTED_361]
ID: 361::
Severity: ERROR

+
Message: The LDIF backend currently does not provide a backup or restore mechanism. Use LDIF import and export operations instead.

[#log-ref-log-ref-ERR_LDIF_BACKEND_HAS_SUBORDINATES_NO_SUCH_ENTRY_365]
ID: 365::
Severity: ERROR

+
Message: The target entry %s does not exist.

[#log-ref-log-ref-ERR_LDIF_BACKEND_NUM_SUBORDINATES_NO_SUCH_ENTRY_366]
ID: 366::
Severity: ERROR

+
Message: The target entry %s does not exist.

[#log-ref-log-ref-ERR_TRUSTSTORE_ERROR_READING_KEY_367]
ID: 367::
Severity: ERROR

+
Message: Error reading key %s from key store %s: %s.

[#log-ref-log-ref-ERR_HAS_SUBORDINATES_NOT_SUPPORTED_368]
ID: 368::
Severity: ERROR

+
Message: This backend does not provide support for the hasSubordinates operational attribute.

[#log-ref-log-ref-ERR_NUM_SUBORDINATES_NOT_SUPPORTED_369]
ID: 369::
Severity: ERROR

+
Message: This backend does not provide support for the numSubordinates operational attribute.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_N_TOKENS_371]
ID: 371::
Severity: ERROR

+
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokens.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_MINUTE_TOKEN_372]
ID: 372::
Severity: ERROR

+
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid minute token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_HOUR_TOKEN_373]
ID: 373::
Severity: ERROR

+
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid hour token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_DAY_TOKEN_374]
ID: 374::
Severity: ERROR

+
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_MONTH_TOKEN_375]
ID: 375::
Severity: ERROR

+
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_WEEKDAY_TOKEN_376]
ID: 376::
Severity: ERROR

+
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_TOKENS_COMBO_377]
ID: 377::
Severity: ERROR

+
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar date.

[#log-ref-log-ref-ERR_TASKS_CANNOT_EXPORT_TO_FILE_378]
ID: 378::
Severity: ERROR

+
Message: An error occurred while attempting to export task backend data: %s.

[#log-ref-log-ref-ERR_BACKUP_MISSING_BACKUPID_407]
ID: 407::
Severity: ERROR

+
Message: The information for backup %s could not be found in the backup directory %s.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_RULEID_CONFLICTS_FOR_ADD_DSR_409]
ID: 409::
Severity: ERROR

+
Message: Unable to add DIT structure rule %s because its rule identifier conflicts with existing DIT structure rule (%s).

[#log-ref-log-ref-ERR_TASKSCHED_DEPENDENCY_MISSING_412]
ID: 412::
Severity: ERROR

+
Message: Unable to schedule task %s because its dependency task %s is missing.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_LDAP_SYNTAX_415]
ID: 415::
Severity: ERROR

+
Message: Unable to add ldap syntax description with OID %s because it conflicts with an existing ldap syntax description.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_LSD_416]
ID: 416::
Severity: ERROR

+
Message: Unable to remove ldap syntax description %s from the server schema because no such ldap syntax description is defined.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_INVALID_LDAP_SYNTAX_417]
ID: 417::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax because its OID %s corresponds to an attribute syntax that is already implemented.

[#log-ref-log-ref-ERR_SCHEMA_MODIFY_CANNOT_DECODE_LDAP_SYNTAX_418]
ID: 418::
Severity: ERROR

+
Message: An error occurred while attempting to decode the ldapsyntax description "%s": %s.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_N_TOKENS_SIMPLE_419]
ID: 419::
Severity: ERROR

+
Message: The provided recurring task schedule value has an invalid number of tokens.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_MINUTE_TOKEN_SIMPLE_420]
ID: 420::
Severity: ERROR

+
Message: The provided recurring task schedule value has an invalid minute token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_HOUR_TOKEN_SIMPLE_421]
ID: 421::
Severity: ERROR

+
Message: The provided recurring task schedule value has an invalid hour token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_DAY_TOKEN_SIMPLE_422]
ID: 422::
Severity: ERROR

+
Message: The provided recurring task schedule value has an invalid day of the month token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_MONTH_TOKEN_SIMPLE_423]
ID: 423::
Severity: ERROR

+
Message: The provided recurring task schedule value has an invalid month of the year token.

[#log-ref-log-ref-ERR_RECURRINGTASK_INVALID_WEEKDAY_TOKEN_SIMPLE_424]
ID: 424::
Severity: ERROR

+
Message: The provided recurring task schedule value has an invalid day of the week token.

[#log-ref-log-ref-ERR_SCHEMA_INVALID_REPLACE_MODIFICATION_425]
ID: 425::
Severity: ERROR

+
Message: The schema backend does not support the Replace modification type for the %s attribute type.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ERROR_CLOSING_FILE_426]
ID: 426::
Severity: ERROR

+
Message: An error occurred while trying to close file %s for the LDIF backend defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_LDIF_BACKEND_ERROR_EMPTY_FILE_427]
ID: 427::
Severity: ERROR

+
Message: The file %s written for the LDIF backend defined in configuration entry %s is 0 bytes long and unusable.

[#log-ref-log-ref-ERR_BACKEND_CONFIG_CACHE_SIZE_GREATER_THAN_JVM_HEAP_428]
ID: 428::
Severity: ERROR

+
Message: Configuration attribute ds-cfg-db-cache-size has a value of %d but the JVM has only %d available. Consider using ds-cfg-db-cache-percent.

[#log-ref-log-ref-ERR_BACKEND_CONFIG_CACHE_PERCENT_GREATER_THAN_JVM_HEAP_429]
ID: 429::
Severity: ERROR

+
Message: Configuration attribute ds-cfg-db-cache-percent has a value of %d%% but the JVM has only %d%% available.

[#log-ref-log-ref-ERR_VLV_BAD_ASSERTION_430]
ID: 430::
Severity: ERROR

+
Message: Unable to process the virtual list view request because the target assertion could not be decoded as a valid value for the '%s' attribute type.

[#log-ref-log-ref-ERR_BACKEND_LIST_FILES_TO_BACKUP_433]
ID: 433::
Severity: ERROR

+
Message: An error occurred while trying to list the files to backup for backend '%s': %s.

[#log-ref-log-ref-ERR_BACKEND_SWITCH_TO_APPEND_MODE_434]
ID: 434::
Severity: ERROR

+
Message: An error occurred while trying to switch to append mode for backend '%s': %s.

[#log-ref-log-ref-ERR_BACKEND_END_APPEND_MODE_435]
ID: 435::
Severity: ERROR

+
Message: An error occurred while trying to end append mode for backend '%s': %s.

[#log-ref-log-ref-ERR_IMPORT_LDIF_LACK_MEM_438]
ID: 438::
Severity: ERROR

+
Message: Insufficient free memory (%d bytes) to perform import. At least %d bytes of free memory is required.

[#log-ref-log-ref-ERR_CONFIG_INDEX_TYPE_NEEDS_MATCHING_RULE_440]
ID: 440::
Severity: ERROR

+
Message: The attribute '%s' cannot have indexing of type '%s' because it does not have a corresponding matching rule.

[#log-ref-log-ref-ERR_ENTRYIDSORTER_NEGATIVE_START_POS_441]
ID: 441::
Severity: ERROR

+
Message: Unable to process the virtual list view request because the target start position was before the beginning of the result set.

[#log-ref-log-ref-ERR_MISSING_ID2ENTRY_RECORD_443]
ID: 443::
Severity: ERROR

+
Message: The entry database does not contain a record for ID %s.

[#log-ref-log-ref-ERR_ENTRYIDSORTER_CANNOT_EXAMINE_ENTRY_444]
ID: 444::
Severity: ERROR

+
Message: Unable to examine the entry with ID %s for sorting purposes: %s.

[#log-ref-log-ref-ERR_EXECUTION_ERROR_445]
ID: 445::
Severity: ERROR

+
Message: Execution error during backend operation: %s.

[#log-ref-log-ref-ERR_INTERRUPTED_ERROR_446]
ID: 446::
Severity: ERROR

+
Message: Interrupted error during backend operation: %s.

[#log-ref-log-ref-ERR_CREATE_FAIL_447]
ID: 447::
Severity: ERROR

+
Message: The backend database directory could not be created: %s.

[#log-ref-log-ref-ERR_DIRECTORY_INVALID_451]
ID: 451::
Severity: ERROR

+
Message: The backend database directory '%s' is not a valid directory.

[#log-ref-log-ref-ERR_ADD_ENTRY_ALREADY_EXISTS_453]
ID: 453::
Severity: ERROR

+
Message: The entry '%s' cannot be added because an entry with that name already exists.

[#log-ref-log-ref-ERR_ADD_NO_SUCH_OBJECT_454]
ID: 454::
Severity: ERROR

+
Message: The entry '%s' cannot be added because its parent entry does not exist.

[#log-ref-log-ref-ERR_ATTRIBUTE_INDEX_NOT_CONFIGURED_455]
ID: 455::
Severity: ERROR

+
Message: There is no index configured for attribute type '%s'.

[#log-ref-log-ref-ERR_CACHE_PRELOAD_456]
ID: 456::
Severity: ERROR

+
Message: An error occurred while preloading the database cache for backend %s: %s.

[#log-ref-log-ref-ERR_COMPSCHEMA_CANNOT_DECODE_AD_TOKEN_457]
ID: 457::
Severity: ERROR

+
Message: An error occurred while attempting to decode an attribute description token from the compressed schema definitions: %s.

[#log-ref-log-ref-ERR_COMPSCHEMA_CANNOT_DECODE_OC_TOKEN_458]
ID: 458::
Severity: ERROR

+
Message: An error occurred while attempting to decode an object class set token from the compressed schema definitions: %s.

[#log-ref-log-ref-ERR_COMPSCHEMA_CANNOT_STORE_EX_459]
ID: 459::
Severity: ERROR

+
Message: An error occurred while attempting to store compressed schema information in the database: %s.

[#log-ref-log-ref-ERR_CONFIG_VLV_INDEX_BAD_FILTER_460]
ID: 460::
Severity: ERROR

+
Message: An error occurred while parsing the search filter %s defined for VLV index %s: %s.

[#log-ref-log-ref-ERR_CONFIG_VLV_INDEX_UNDEFINED_ATTR_461]
ID: 461::
Severity: ERROR

+
Message: Sort attribute %s for VLV index %s is not defined in the server schema.

[#log-ref-log-ref-ERR_DATABASE_EXCEPTION_462]
ID: 462::
Severity: ERROR

+
Message: Database exception: %s.

[#log-ref-log-ref-ERR_DELETE_ABORTED_BY_SUBORDINATE_PLUGIN_463]
ID: 463::
Severity: ERROR

+
Message: A plugin caused the delete operation to be aborted while deleting a subordinate entry %s.

[#log-ref-log-ref-ERR_DELETE_NOT_ALLOWED_ON_NONLEAF_464]
ID: 464::
Severity: ERROR

+
Message: The entry '%s' cannot be removed because it has subordinate entries.

[#log-ref-log-ref-ERR_DELETE_NO_SUCH_OBJECT_465]
ID: 465::
Severity: ERROR

+
Message: The entry '%s' cannot be removed because it does not exist.

[#log-ref-log-ref-ERR_ENTRY_CONTAINER_ALREADY_REGISTERED_466]
ID: 466::
Severity: ERROR

+
Message: An entry container named '%s' is alreadly registered for base DN '%s'.

[#log-ref-log-ref-ERR_ENTRY_DATABASE_CORRUPT_467]
ID: 467::
Severity: ERROR

+
Message: The entry database does not contain a valid record for ID %s.

[#log-ref-log-ref-ERR_EXPORT_IO_ERROR_468]
ID: 468::
Severity: ERROR

+
Message: I/O error occurred while exporting entry: %s.

[#log-ref-log-ref-ERR_IMPORT_BACKEND_ONLINE_469]
ID: 469::
Severity: ERROR

+
Message: The backend must be disabled before the import process can start.

[#log-ref-log-ref-ERR_IMPORT_CREATE_TMPDIR_ERROR_471]
ID: 471::
Severity: ERROR

+
Message: Unable to create the temporary directory %s.

[#log-ref-log-ref-ERR_IMPORT_PARENT_NOT_FOUND_481]
ID: 481::
Severity: ERROR

+
Message: The parent entry '%s' does not exist.

[#log-ref-log-ref-ERR_INCOMPATIBLE_ENTRY_VERSION_482]
ID: 482::
Severity: ERROR

+
Message: Entry record is not compatible with this version of the backend database. Entry version: %x.

[#log-ref-log-ref-ERR_INDEX_CORRUPT_REQUIRES_REBUILD_483]
ID: 483::
Severity: ERROR

+
Message: An error occurred while reading from index %s. The index seems to be corrupt and is now operating in a degraded state. The index must be rebuilt before it can return to normal operation.

[#log-ref-log-ref-ERR_INVALID_PAGED_RESULTS_COOKIE_484]
ID: 484::
Severity: ERROR

+
Message: The following paged results control cookie value was not recognized: %s.

[#log-ref-log-ref-ERR_MODIFYDN_ABORTED_BY_SUBORDINATE_PLUGIN_487]
ID: 487::
Severity: ERROR

+
Message: A plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %s.

[#log-ref-log-ref-ERR_MODIFYDN_ABORTED_BY_SUBORDINATE_SCHEMA_ERROR_488]
ID: 488::
Severity: ERROR

+
Message: A plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %s because the change to that entry violated the server schema configuration: %s.

[#log-ref-log-ref-ERR_MODIFYDN_ALREADY_EXISTS_489]
ID: 489::
Severity: ERROR

+
Message: The entry cannot be renamed to '%s' because an entry with that name already exists.

[#log-ref-log-ref-ERR_MODIFYDN_NO_SUCH_OBJECT_490]
ID: 490::
Severity: ERROR

+
Message: The entry '%s' cannot be renamed because it does not exist.

[#log-ref-log-ref-ERR_MODIFY_NO_SUCH_OBJECT_491]
ID: 491::
Severity: ERROR

+
Message: The entry '%s' cannot be modified because it does not exist.

[#log-ref-log-ref-ERR_NEW_SUPERIOR_NO_SUCH_OBJECT_492]
ID: 492::
Severity: ERROR

+
Message: The entry cannot be moved because the new parent entry '%s' does not exist.

[#log-ref-log-ref-ERR_OPEN_ENV_FAIL_493]
ID: 493::
Severity: ERROR

+
Message: The database environment could not be opened: %s.

[#log-ref-log-ref-ERR_REBUILD_BACKEND_ONLINE_494]
ID: 494::
Severity: ERROR

+
Message: Rebuilding system index(es) must be done with the backend containing the base DN disabled.

[#log-ref-log-ref-ERR_REMOVE_FAIL_495]
ID: 495::
Severity: ERROR

+
Message: The backend database files could not be removed: %s.

[#log-ref-log-ref-ERR_SEARCH_CANNOT_MIX_PAGEDRESULTS_AND_VLV_496]
ID: 496::
Severity: ERROR

+
Message: The requested search operation included both the simple paged results control and the virtual list view control. These controls are mutually exclusive and cannot be used together.

[#log-ref-log-ref-ERR_SEARCH_CANNOT_SORT_UNINDEXED_497]
ID: 497::
Severity: ERROR

+
Message: The search results cannot be sorted because the given search request is not indexed.

[#log-ref-log-ref-ERR_SEARCH_NO_SUCH_OBJECT_498]
ID: 498::
Severity: ERROR

+
Message: The search base entry '%s' does not exist.

[#log-ref-log-ref-ERR_SEARCH_UNINDEXED_INSUFFICIENT_PRIVILEGES_499]
ID: 499::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform an unindexed search.

[#log-ref-log-ref-ERR_UNCHECKED_EXCEPTION_500]
ID: 500::
Severity: ERROR

+
Message: Unchecked exception during database transaction: %s.

[#log-ref-log-ref-ERR_VLV_INDEX_NOT_CONFIGURED_501]
ID: 501::
Severity: ERROR

+
Message: There is no VLV index configured with name '%s'.

[#log-ref-log-ref-ERR_JEB_INVALID_LOGGING_LEVEL_561]
ID: 561::
Severity: ERROR

+
Message: The database logging level string '%s' provided for configuration entry '%s' is invalid. The value must be one of OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or ALL. Note that these values are case sensitive.

[#log-ref-log-ref-ERR_CONFIG_JEB_CACHE_SIZE_TOO_SMALL_569]
ID: 569::
Severity: ERROR

+
Message: Configuration attribute ds-cfg-db-cache-size has a value of %d which is less than the minimum: %d.

[#log-ref-log-ref-ERR_CONFIG_JEB_DURABILITY_CONFLICT_570]
ID: 570::
Severity: ERROR

+
Message: Configuration attributes ds-cfg-db-txn-no-sync and ds-cfg-db-txn-write-no-sync are mutually exclusive and cannot be both set at the same time.

[#log-ref-log-ref-ERR_VERIFY_BACKEND_ONLINE_579]
ID: 579::
Severity: ERROR

+
Message: The backend must be disabled before verification process can start.

[#log-ref-log-ref-ERR_VERIFY_MISSING_ID_583]
ID: 583::
Severity: ERROR

+
Message: Missing ID %d%n%s.

[#log-ref-log-ref-ERR_VERIFY_MISSING_ENTRY_VLV_584]
ID: 584::
Severity: ERROR

+
Message: Missing entry %s in VLV index %s.

[#log-ref-log-ref-ERR_VERIFY_UNKNOWN_ID_585]
ID: 585::
Severity: ERROR

+
Message: Reference to unknown entry ID %s%n%s.

[#log-ref-log-ref-ERR_VERIFY_ENTRY_NON_MATCHING_KEY_586]
ID: 586::
Severity: ERROR

+
Message: Reference to entry ID %s has a key which does not match the expected key%n%s.

[#log-ref-log-ref-ERR_VERIFY_EMPTY_IDSET_587]
ID: 587::
Severity: ERROR

+
Message: Empty ID set: %n%s.

[#log-ref-log-ref-ERR_VERIFY_DUPLICATE_REFERENCE_588]
ID: 588::
Severity: ERROR

+
Message: Duplicate reference to ID %d%n%s.

[#log-ref-log-ref-ERR_VERIFY_UNKNOWN_REFERENCE_589]
ID: 589::
Severity: ERROR

+
Message: Reference to unknown ID %d%n%s.

[#log-ref-log-ref-ERR_VERIFY_UNEXPECTED_REFERENCE_590]
ID: 590::
Severity: ERROR

+
Message: Reference to entry <%s> which does not match the value%n%s.

[#log-ref-log-ref-ERR_VERIFY_DN2ID_MISSING_KEY_591]
ID: 591::
Severity: ERROR

+
Message: File dn2id is missing key %s.

[#log-ref-log-ref-ERR_VERIFY_DN2ID_WRONG_ID_592]
ID: 592::
Severity: ERROR

+
Message: File dn2id has ID %d instead of %d for key %s.

[#log-ref-log-ref-ERR_VERIFY_DN2ID_UNKNOWN_ID_593]
ID: 593::
Severity: ERROR

+
Message: File dn2id has DN <%s> referencing unknown ID %d.

[#log-ref-log-ref-ERR_VERIFY_DN2ID_WRONG_ENTRY_594]
ID: 594::
Severity: ERROR

+
Message: File dn2id has DN <%s> referencing entry with wrong DN <%s>.

[#log-ref-log-ref-ERR_VERIFY_WRONG_ENTRY_COUNT_595]
ID: 595::
Severity: ERROR

+
Message: The stored entry count in id2entry (%d) does not agree with the actual number of entry records found (%d).

[#log-ref-log-ref-ERR_VERIFY_ID2COUNT_WRONG_COUNT_596]
ID: 596::
Severity: ERROR

+
Message: File id2childrenCount has wrong number of children for DN <%s> (got %d, expecting %d).

[#log-ref-log-ref-ERR_VERIFY_ID2COUNT_WRONG_ID_597]
ID: 597::
Severity: ERROR

+
Message: File id2ChildrenCount references non-existing EntryID <%d>.

[#log-ref-log-ref-ERR_SCHEMA_PARSE_LINE_600]
ID: 600::
Severity: ERROR

+
Message: Ignoring schema definition '%s' because the following error occurred while it was being parsed: %s.

[#log-ref-log-ref-ERR_SCHEMA_COULD_NOT_PARSE_DEFINITION_601]
ID: 601::
Severity: ERROR

+
Message: Schema definition could not be parsed as valid attribute value.

[#log-ref-log-ref-ERR_CLEARTEXT_BACKEND_FOR_INDEX_CONFIDENTIALITY_602]
ID: 602::
Severity: ERROR

+
Message: Attribute %s is set as confidential on a backend whose entries are still cleartext. Enable confidentiality on the backend first.

[#log-ref-log-ref-ERR_CONFIG_INDEX_CANNOT_PROTECT_BOTH_603]
ID: 603::
Severity: ERROR

+
Message: The attribute '%s' cannot enable confidentiality for keys and values at the same time.

[#log-ref-log-ref-ERR_CANNOT_ENCODE_ENTRY_604]
ID: 604::
Severity: ERROR

+
Message: Cannot encode entry for writing on storage: %s.

[#log-ref-log-ref-ERR_CANNOT_DECODE_ENTRY_605]
ID: 605::
Severity: ERROR

+
Message: Input stream ended unexpectedly while decoding entry.

[#log-ref-log-ref-ERR_BACKEND_CANNOT_CHANGE_CONFIDENTIALITY_606]
ID: 606::
Severity: ERROR

+
Message: Confidentiality cannot be disabled on suffix '%s' because the following indexes have confidentiality still enabled: %s.

[#log-ref-log-ref-ERR_BACKEND_FAULTY_CRYPTO_TRANSFORMATION_608]
ID: 608::
Severity: ERROR

+
Message: Error while enabling confidentiality with cipher %s, %d bits: %s.

[#log-ref-log-ref-ERR_NOT_ENOUGH_RESOURCES_644]
ID: 644::
Severity: ERROR

+
Message: There are insufficient resources to perform the operation.

--


[#CONFIG]
=== Log Message Category: CONFIG

--

[#log-ref-log-ref-ERR_CONFIG_ATTR_IS_REQUIRED_1]
ID: 1::
Severity: ERROR

+
Message: Configuration attribute %s is required to have at least one value but the resulted operation would have removed all values.

[#log-ref-log-ref-ERR_CONFIG_ATTR_REJECTED_VALUE_2]
ID: 2::
Severity: ERROR

+
Message: Provided value %s for configuration attribute %s was rejected. The reason provided was: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_SET_VALUES_IS_SINGLE_VALUED_3]
ID: 3::
Severity: ERROR

+
Message: Configuration attribute %s is single-valued, but multiple values were provided.

[#log-ref-log-ref-ERR_CONFIG_ATTR_ADD_VALUES_IS_SINGLE_VALUED_4]
ID: 4::
Severity: ERROR

+
Message: Configuration attribute %s is single-valued, but adding the provided value(s) would have given it multiple values.

[#log-ref-log-ref-ERR_CONFIG_ATTR_ADD_VALUES_ALREADY_EXISTS_5]
ID: 5::
Severity: ERROR

+
Message: Configuration attribute %s already contains a value %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_NO_SUCH_VALUE_6]
ID: 6::
Severity: ERROR

+
Message: Cannot remove value %s from configuration attribute %s because the specified value does not exist.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INVALID_BOOLEAN_VALUE_7]
ID: 7::
Severity: ERROR

+
Message: Unable to set the value for Boolean configuration attribute %s because the provided value %s was not either 'true' or 'false'.

[#log-ref-log-ref-ERR_CONFIG_ATTR_NO_INT_VALUE_8]
ID: 8::
Severity: ERROR

+
Message: Unable to retrieve the value for configuration attribute %s as an integer because that attribute does not have any values.

[#log-ref-log-ref-ERR_CONFIG_ATTR_MULTIPLE_INT_VALUES_9]
ID: 9::
Severity: ERROR

+
Message: Unable to retrieve the value for configuration attribute %s as an integer because that attribute has multiple values.

[#log-ref-log-ref-ERR_CONFIG_ATTR_VALUE_OUT_OF_INT_RANGE_10]
ID: 10::
Severity: ERROR

+
Message: Unable to retrieve the value for configuration attribute %s as a Java int because the value is outside the allowable range for an int.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INVALID_INT_VALUE_11]
ID: 11::
Severity: ERROR

+
Message: Unable to set the value for integer configuration attribute %s because the provided value %s cannot be interpreted as an integer value: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INT_BELOW_LOWER_BOUND_12]
ID: 12::
Severity: ERROR

+
Message: Unable to set the value for configuration attribute %s because the provided value %d is less than the lowest allowed value of %d.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INT_ABOVE_UPPER_BOUND_13]
ID: 13::
Severity: ERROR

+
Message: Unable to set the value for configuration attribute %s because the provided value %d is greater than the largest allowed value of %d.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INT_COULD_NOT_PARSE_14]
ID: 14::
Severity: ERROR

+
Message: Unable to parse value %s for configuration attribute %s as an integer value: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_NO_STRING_VALUE_15]
ID: 15::
Severity: ERROR

+
Message: Unable to retrieve the value for configuration attribute %s as a string because that attribute does not have any values.

[#log-ref-log-ref-ERR_CONFIG_ATTR_MULTIPLE_STRING_VALUES_16]
ID: 16::
Severity: ERROR

+
Message: Unable to retrieve the value for configuration attribute %s as a string because that attribute has multiple values.

[#log-ref-log-ref-ERR_CONFIG_ATTR_EMPTY_STRING_VALUE_17]
ID: 17::
Severity: ERROR

+
Message: An empty value string was provided for configuration attribute %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_VALUE_NOT_ALLOWED_18]
ID: 18::
Severity: ERROR

+
Message: The value %s is not included in the list of acceptable values for configuration attribute %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INVALID_UNIT_19]
ID: 19::
Severity: ERROR

+
Message: '%s' is not a valid unit for configuration attribute %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_NO_UNIT_DELIMITER_20]
ID: 20::
Severity: ERROR

+
Message: Cannot decode %s as an integer value and a unit for configuration attribute %s because no value/unit delimiter could be found.

[#log-ref-log-ref-ERR_CONFIG_ATTR_COULD_NOT_PARSE_INT_COMPONENT_21]
ID: 21::
Severity: ERROR

+
Message: Could not decode the integer portion of value %s for configuration attribute %s: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INVALID_VALUE_WITH_UNIT_22]
ID: 22::
Severity: ERROR

+
Message: The provided value %s for integer with unit attribute %s is not allowed: %s.

[#log-ref-log-ref-ERR_CONFIG_ENTRY_CONFLICTING_CHILD_23]
ID: 23::
Severity: ERROR

+
Message: Unable to add configuration entry %s as a child of configuration entry %s because a child entry was already found with that DN.

[#log-ref-log-ref-ERR_CONFIG_ENTRY_NO_SUCH_CHILD_24]
ID: 24::
Severity: ERROR

+
Message: Unable to remove entry %s as a child of configuration entry %s because that entry did not have a child with the specified DN.

[#log-ref-log-ref-ERR_CONFIG_ENTRY_CANNOT_REMOVE_NONLEAF_25]
ID: 25::
Severity: ERROR

+
Message: Unable to remove entry %s as a child of configuration entry %s because that entry had children of its own and non-leaf entries may not be removed.

[#log-ref-log-ref-ERR_CONFIG_FILE_DOES_NOT_EXIST_26]
ID: 26::
Severity: ERROR

+
Message: The specified configuration file %s does not exist or is not readable.

[#log-ref-log-ref-ERR_CONFIG_FILE_CANNOT_VERIFY_EXISTENCE_27]
ID: 27::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to determine whether configuration file %s exists: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_CANNOT_OPEN_FOR_READ_28]
ID: 28::
Severity: ERROR

+
Message: An error occurred while attempting to open the configuration file %s for reading: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_READ_ERROR_29]
ID: 29::
Severity: ERROR

+
Message: An error occurred while attempting to read the contents of configuration file %s: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_OPTIONS_NOT_ALLOWED_30]
ID: 30::
Severity: ERROR

+
Message: Invalid configuration attribute %s detected: the only attribute option allowed in the Directory Server configuration is "pending" to indicate the set of pending values.

[#log-ref-log-ref-ERR_CONFIG_FILE_INVALID_LDIF_ENTRY_31]
ID: 31::
Severity: ERROR

+
Message: An error occurred at or near line %d while trying to parse the configuration from LDIF file %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_EMPTY_32]
ID: 32::
Severity: ERROR

+
Message: The specified configuration file %s does not appear to contain any configuration entries.

[#log-ref-log-ref-ERR_CONFIG_FILE_INVALID_BASE_DN_33]
ID: 33::
Severity: ERROR

+
Message: The first entry read from LDIF configuration file %s had a DN of "%s" rather than the expected "%s" which should be used as the Directory Server configuration root.

[#log-ref-log-ref-ERR_CONFIG_FILE_GENERIC_ERROR_34]
ID: 34::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to process the Directory Server configuration file %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_DUPLICATE_ENTRY_35]
ID: 35::
Severity: ERROR

+
Message: Configuration entry %s starting at or near line %s in the LDIF configuration file %s has the same DN as another entry already read from that file.

[#log-ref-log-ref-ERR_CONFIG_FILE_NO_PARENT_36]
ID: 36::
Severity: ERROR

+
Message: Configuration entry %s starting at or near line %d in the configuration LDIF file %s does not appear to have a parent entry (expected parent DN was %s).

[#log-ref-log-ref-ERR_CONFIG_FILE_UNKNOWN_PARENT_37]
ID: 37::
Severity: ERROR

+
Message: The Directory Server was unable to determine the parent DN for configuration entry %s starting at or near line %d in the configuration LDIF file %s.

[#log-ref-log-ref-ERR_CONFIG_CANNOT_DETERMINE_SERVER_ROOT_38]
ID: 38::
Severity: ERROR

+
Message: Unable to determine the Directory Server instance root from either an environment variable or based on the location of the configuration file. Please set an environment variable named %s with a value containing the absolute path to the server installation root.

[#log-ref-log-ref-ERR_CONFIG_FILE_WRITE_ERROR_39]
ID: 39::
Severity: ERROR

+
Message: An unexpected error occurred while trying to write configuration entry %s to LDIF: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_CLOSE_ERROR_40]
ID: 40::
Severity: ERROR

+
Message: An unexpected error occurred while trying to close the LDIF writer: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_UNWILLING_TO_IMPORT_41]
ID: 41::
Severity: ERROR

+
Message: The Directory Server configuration may not be altered by importing a new configuration from LDIF.

[#log-ref-log-ref-ERR_CONFIG_LOGGER_CANNOT_CREATE_LOGGER_49]
ID: 49::
Severity: ERROR

+
Message: An error occurred while attempting to create a Directory Server logger from the information in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_LOGGER_INVALID_OBJECTCLASS_50]
ID: 50::
Severity: ERROR

+
Message: Configuration entry %s does not contain a valid objectclass for a Directory Server access, error, or debug logger definition.

[#log-ref-log-ref-ERR_CONFIG_LOGGER_INVALID_ACCESS_LOGGER_CLASS_54]
ID: 54::
Severity: ERROR

+
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server access logger: %s.

[#log-ref-log-ref-ERR_CONFIG_LOGGER_INVALID_ERROR_LOGGER_CLASS_55]
ID: 55::
Severity: ERROR

+
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server error logger: %s.

[#log-ref-log-ref-ERR_CONFIG_LOGGER_INVALID_DEBUG_LOGGER_CLASS_56]
ID: 56::
Severity: ERROR

+
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server debug logger: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_MULTIPLE_PENDING_VALUE_SETS_64]
ID: 64::
Severity: ERROR

+
Message: Configuration attribute %s appears to contain multiple pending value sets.

[#log-ref-log-ref-ERR_CONFIG_ATTR_MULTIPLE_ACTIVE_VALUE_SETS_65]
ID: 65::
Severity: ERROR

+
Message: Configuration attribute %s appears to contain multiple active value sets.

[#log-ref-log-ref-ERR_CONFIG_ATTR_NO_ACTIVE_VALUE_SET_66]
ID: 66::
Severity: ERROR

+
Message: Configuration attribute %s does not contain an active value set.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INT_INVALID_TYPE_67]
ID: 67::
Severity: ERROR

+
Message: Unable to parse value %s for configuration attribute %s as an integer value because the element was of an invalid type (%s).

[#log-ref-log-ref-ERR_CONFIG_ATTR_INT_INVALID_ARRAY_TYPE_68]
ID: 68::
Severity: ERROR

+
Message: Unable to parse value for configuration attribute %s as a set of integer values because the array contained elements of an invalid type (%s).

[#log-ref-log-ref-ERR_CONFIG_ATTR_INVALID_STRING_VALUE_69]
ID: 69::
Severity: ERROR

+
Message: Unable to parse value %s for configuration attribute %s as a string value: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_STRING_INVALID_TYPE_70]
ID: 70::
Severity: ERROR

+
Message: Unable to parse value %s for configuration attribute %s as a string value because the element was of an invalid type (%s).

[#log-ref-log-ref-ERR_CONFIG_ATTR_STRING_INVALID_ARRAY_TYPE_71]
ID: 71::
Severity: ERROR

+
Message: Unable to parse value for configuration attribute %s as a set of string values because the array contained elements of an invalid type (%s).

[#log-ref-log-ref-ERR_CONFIG_ATTR_INT_WITH_UNIT_INVALID_TYPE_72]
ID: 72::
Severity: ERROR

+
Message: Unable to parse value %s for configuration attribute %s as an integer with unit value because the element was of an invalid type (%s).

[#log-ref-log-ref-ERR_CONFIG_JMX_ATTR_NO_ATTR_74]
ID: 74::
Severity: ERROR

+
Message: Configuration entry %s does not contain attribute %s (or that attribute exists but is not accessible using JMX).

[#log-ref-log-ref-ERR_CONFIG_JMX_NO_METHOD_78]
ID: 78::
Severity: ERROR

+
Message: There is no method %s for any invokable component registered with configuration entry %s.

[#log-ref-log-ref-ERR_CONFIG_JMX_CANNOT_REGISTER_MBEAN_83]
ID: 83::
Severity: ERROR

+
Message: The Directory Server could not register a JMX MBean for the component associated with configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_LDIF_WRITE_ERROR_84]
ID: 84::
Severity: ERROR

+
Message: An unexpected error occurred while trying to export the Directory Server configuration to LDIF: %s.

[#log-ref-log-ref-ERR_CONFIG_WORK_QUEUE_TOO_MANY_FAILURES_94]
ID: 94::
Severity: ERROR

+
Message: Worker thread "%s" has experienced too many repeated failures while attempting to retrieve the next operation from the work queue (%d failures experienced, maximum of %d failures allowed). This worker thread will be destroyed.

[#log-ref-log-ref-ERR_CONFIG_WORK_QUEUE_CANNOT_CREATE_MONITOR_95]
ID: 95::
Severity: ERROR

+
Message: A problem occurred while trying to create and start an instance of class %s to use as a monitor provider for the Directory Server work queue: %s. No monitor information will be available for the work queue.

[#log-ref-log-ref-ERR_CONFIG_ATTR_DN_NULL_98]
ID: 98::
Severity: ERROR

+
Message: A null value was provided for DN configuration attribute %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_DN_CANNOT_PARSE_99]
ID: 99::
Severity: ERROR

+
Message: An error occurred while trying to parse value "%s" of attribute %s as a DN: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_INVALID_DN_VALUE_100]
ID: 100::
Severity: ERROR

+
Message: Unable to parse value %s for configuration attribute %s as a DN: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_DN_INVALID_TYPE_101]
ID: 101::
Severity: ERROR

+
Message: Unable to parse value %s for configuration attribute %s as a DN because the element was of an invalid type (%s).

[#log-ref-log-ref-ERR_CONFIG_ATTR_DN_INVALID_ARRAY_TYPE_102]
ID: 102::
Severity: ERROR

+
Message: Unable to parse value for configuration attribute %s as a set of DN values because the array contained elements of an invalid type (%s).

[#log-ref-log-ref-ERR_CONFIG_CANNOT_REGISTER_AS_PRIVATE_SUFFIX_103]
ID: 103::
Severity: ERROR

+
Message: An unexpected error occurred while trying to register the configuration handler base DN "%s" as a private suffix with the Directory Server: %s.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_CANNOT_GET_CONFIG_BASE_104]
ID: 104::
Severity: ERROR

+
Message: An error occurred while trying to retrieve configuration entry cn=Backends,cn=config in order to initialize the Directory Server backends: %s.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_BASE_DOES_NOT_EXIST_105]
ID: 105::
Severity: ERROR

+
Message: The entry cn=Backends,cn=config does not appear to exist in the Directory Server configuration. This is a required entry.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_ERROR_INTERACTING_WITH_BACKEND_ENTRY_107]
ID: 107::
Severity: ERROR

+
Message: An unexpected error occurred while interacting with backend configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_ENABLED_STATE_112]
ID: 112::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to determine whether the backend associated with configuration entry %s should be enabled or disabled: %s. It will be disabled.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_CANNOT_INSTANTIATE_115]
ID: 115::
Severity: ERROR

+
Message: The Directory Server was unable to load class %s and use it to create a backend instance as defined in configuration entry %s. The error that occurred was: %s. This backend will be disabled.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_CANNOT_INITIALIZE_116]
ID: 116::
Severity: ERROR

+
Message: An error occurred while trying to initialize a backend loaded from class %s with the information in configuration entry %s: %s. This backend will be disabled.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_CLASS_NOT_BACKEND_117]
ID: 117::
Severity: ERROR

+
Message: The class %s specified in configuration entry %s does not contain a valid Directory Server backend implementation.

[#log-ref-log-ref-ERR_CONFIG_MONITOR_INITIALIZATION_FAILED_140]
ID: 140::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a monitor provider as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_CONNHANDLER_CANNOT_INITIALIZE_154]
ID: 154::
Severity: ERROR

+
Message: An error occurred while trying to initialize a connection handler loaded from class %s with the information in configuration entry %s: %s. This connection handler will be disabled.

[#log-ref-log-ref-ERR_CONFIG_SCHEMA_MR_CANNOT_INITIALIZE_172]
ID: 172::
Severity: ERROR

+
Message: An error occurred while trying to initialize a matching rule loaded from class %s with the information in configuration entry %s: %s. This matching rule will be disabled.

[#log-ref-log-ref-ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_INITIALIZE_186]
ID: 186::
Severity: ERROR

+
Message: An error occurred while trying to initialize an attribute syntax loaded from class %s with the information in configuration entry %s: %s. This syntax will be disabled.

[#log-ref-log-ref-ERR_CONFIG_SCHEMA_NO_SCHEMA_DIR_188]
ID: 188::
Severity: ERROR

+
Message: Unable to read the Directory Server schema definitions because the schema directory %s does not exist.

[#log-ref-log-ref-ERR_CONFIG_SCHEMA_DIR_NOT_DIRECTORY_189]
ID: 189::
Severity: ERROR

+
Message: Unable to read the Directory Server schema definitions because the schema directory %s exists but is not a directory.

[#log-ref-log-ref-ERR_CONFIG_SCHEMA_CANNOT_LIST_FILES_190]
ID: 190::
Severity: ERROR

+
Message: Unable to read the Directory Server schema definitions from directory %s because an unexpected error occurred while trying to list the files in that directory: %s.

[#log-ref-log-ref-ERR_CONFIG_ENTRYCACHE_CANNOT_INSTALL_DEFAULT_CACHE_200]
ID: 200::
Severity: ERROR

+
Message: An unexpected error occurred that prevented the server from installing its default entry cache framework: %s.

[#log-ref-log-ref-ERR_CONFIG_ENTRYCACHE_CANNOT_INITIALIZE_CACHE_202]
ID: 202::
Severity: ERROR

+
Message: An error occurred while attempting to initialize an instance of class %s for use as the Directory Server entry cache: %s. As a result, the entry cache will be disabled.

[#log-ref-log-ref-ERR_CONFIG_ENTRYCACHE_CONFIG_NOT_ACCEPTABLE_203]
ID: 203::
Severity: ERROR

+
Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_ENTRYCACHE_CONFIG_LEVEL_NOT_ACCEPTABLE_204]
ID: 204::
Severity: ERROR

+
Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: the entry cache level %d is already in use.

[#log-ref-log-ref-ERR_CONFIG_ENTRY_CANNOT_REMOVE_CHILD_215]
ID: 215::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to remove entry %s as a child of configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_ATTR_READ_ONLY_228]
ID: 228::
Severity: ERROR

+
Message: Configuration attribute %s is read-only and its values may not be altered.

[#log-ref-log-ref-ERR_CONFIG_PLUGIN_CANNOT_INITIALIZE_245]
ID: 245::
Severity: ERROR

+
Message: An error occurred while attempting to initialize an instance of class %s as a Directory Server plugin using the information in configuration entry %s: %s. This plugin will be disabled.

[#log-ref-log-ref-ERR_CONFIG_EXTOP_INVALID_CLASS_256]
ID: 256::
Severity: ERROR

+
Message: Class %s specified in configuration entry %s does not contain a valid extended operation handler implementation: %s.

[#log-ref-log-ref-ERR_CONFIG_EXTOP_INITIALIZATION_FAILED_261]
ID: 261::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as an extended operation handler as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_SASL_INITIALIZATION_FAILED_277]
ID: 277::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a SASL mechanism handler as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_NO_PARENT_DN_278]
ID: 278::
Severity: ERROR

+
Message: Entry %s cannot be removed from the Directory Server configuration because that DN does not have a parent.

[#log-ref-log-ref-ERR_CONFIG_FILE_ADD_ALREADY_EXISTS_280]
ID: 280::
Severity: ERROR

+
Message: Entry %s cannot be added to the Directory Server configuration because another configuration entry already exists with that DN.

[#log-ref-log-ref-ERR_CONFIG_FILE_ADD_NO_PARENT_DN_281]
ID: 281::
Severity: ERROR

+
Message: Entry %s cannot be added to the Directory Server configuration because that DN does not have a parent.

[#log-ref-log-ref-ERR_CONFIG_FILE_ADD_NO_PARENT_282]
ID: 282::
Severity: ERROR

+
Message: Entry %s cannot be added to the Directory Server configuration because its parent entry %s does not exist.

[#log-ref-log-ref-ERR_CONFIG_FILE_ADD_REJECTED_BY_LISTENER_283]
ID: 283::
Severity: ERROR

+
Message: The Directory Server is unwilling to add configuration entry %s because one of the add listeners registered with the parent entry %s rejected this change with the message: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_ADD_FAILED_284]
ID: 284::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to add configuration entry %s as a child of entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_NO_SUCH_ENTRY_285]
ID: 285::
Severity: ERROR

+
Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry does not exist.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_HAS_CHILDREN_286]
ID: 286::
Severity: ERROR

+
Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry has one or more subordinate entries.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_NO_PARENT_287]
ID: 287::
Severity: ERROR

+
Message: Entry %s cannot be removed from the Directory Server configuration because the entry does not have a parent and removing the configuration root entry is not allowed.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_REJECTED_BY_LISTENER_288]
ID: 288::
Severity: ERROR

+
Message: Entry %s cannot be removed from the Directory Server configuration because one of the delete listeners registered with the parent entry %s rejected this change with the message: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_FAILED_289]
ID: 289::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to remove configuration entry %s as a child of entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODIFY_NO_SUCH_ENTRY_290]
ID: 290::
Severity: ERROR

+
Message: Entry %s cannot be modified because the specified entry does not exist.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODIFY_REJECTED_BY_CHANGE_LISTENER_291]
ID: 291::
Severity: ERROR

+
Message: Entry %s cannot be modified because one of the configuration change listeners registered for that entry rejected the change: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODIFY_FAILED_292]
ID: 292::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to modify configuration entry %s as a child of entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_SEARCH_NO_SUCH_BASE_293]
ID: 293::
Severity: ERROR

+
Message: The search operation cannot be processed because base entry %s does not exist.

[#log-ref-log-ref-ERR_CONFIG_FILE_SEARCH_INVALID_SCOPE_294]
ID: 294::
Severity: ERROR

+
Message: The search operation cannot be processed because the specified search scope %s is invalid.

[#log-ref-log-ref-ERR_CONFIG_FILE_WRITE_CANNOT_EXPORT_NEW_CONFIG_300]
ID: 300::
Severity: ERROR

+
Message: An error occurred while attempting to export the new Directory Server configuration to file %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_NEW_CONFIG_301]
ID: 301::
Severity: ERROR

+
Message: An error occurred while attempting to rename the new Directory Server configuration from file %s to %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODDN_NOT_ALLOWED_302]
ID: 302::
Severity: ERROR

+
Message: Modify DN operations are not allowed in the Directory Server configuration.

[#log-ref-log-ref-ERR_CONFIG_TRUSTMANAGER_DESCRIPTION_ENABLED_328]
ID: 328::
Severity: ERROR

+
Message: Indicates whether the Directory Server trust manager provider should be enabled. A trust manager provider is required for operations that require access to a trust manager (e.g., communication over SSL). Changes to this configuration attribute will take effect immediately, but will only impact future attempts to access the trust manager.

[#log-ref-log-ref-ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILED_376]
ID: 376::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a password storage scheme as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_PWSCHEME_EXISTS_377]
ID: 377::
Severity: ERROR

+
Message: Unable to add a new password storage scheme entry with DN %s because there is already a storage scheme registered with that DN.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_CANNOT_ACQUIRE_SHARED_LOCK_422]
ID: 422::
Severity: ERROR

+
Message: The Directory Server was unable to acquire a shared lock for backend %s: %s. This generally means that the backend is in use by a process that requires an exclusive lock (e.g., importing from LDIF or restoring a backup). This backend will be disabled.

[#log-ref-log-ref-ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILED_442]
ID: 442::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as an identity mapper as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_IDMAPPER_NO_PROXY_MAPPER_DN_448]
ID: 448::
Severity: ERROR

+
Message: The Directory Server does not have any identity mapper configured for use in conjunction with proxied authorization V2 operations. The Directory Server will not be able to process requests containing the proxied authorization control with a username-based authorization ID.

[#log-ref-log-ref-ERR_CONFIG_IDMAPPER_INVALID_PROXY_MAPPER_DN_449]
ID: 449::
Severity: ERROR

+
Message: The configured proxied authorization identity mapper DN %s does not refer to an active identity mapper. The Directory Server will not be able to process requests containing the proxied authorization control with a username-based authorization ID.

[#log-ref-log-ref-ERR_CONFIG_SYNCH_UNABLE_TO_LOAD_PROVIDER_CLASS_463]
ID: 463::
Severity: ERROR

+
Message: An error occurred while attempting to load class %s referenced in synchronization provider configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_SYNCH_UNABLE_TO_INSTANTIATE_PROVIDER_464]
ID: 464::
Severity: ERROR

+
Message: An error occurred while attempting to instantiate class %s referenced in synchronization provider configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_SYNCH_ERROR_INITIALIZING_PROVIDER_465]
ID: 465::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server synchronization provider referenced in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILED_489]
ID: 489::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a password validator as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILED_505]
ID: 505::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a password generator as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_PWPOLICY_NO_POLICIES_514]
ID: 514::
Severity: ERROR

+
Message: No password policies have been defined below the cn=Password Policies,cn=config entry in the Directory Server configuration. At least one password policy configuration must be defined.

[#log-ref-log-ref-ERR_CONFIG_PWPOLICY_INVALID_POLICY_CONFIG_515]
ID: 515::
Severity: ERROR

+
Message: The password policy defined in configuration entry %s is invalid: %s.

[#log-ref-log-ref-ERR_CONFIG_PWPOLICY_MISSING_DEFAULT_POLICY_516]
ID: 516::
Severity: ERROR

+
Message: The Directory Server default password policy is defined as %s, but that entry does not exist or is not below the password policy configuration base cn=Password Policies,cn=config.

[#log-ref-log-ref-ERR_CONFIG_AUTHZ_UNABLE_TO_INSTANTIATE_HANDLER_533]
ID: 533::
Severity: ERROR

+
Message: An error occurred while attempting to instantiate class %s referenced in the access control configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_ROOTDN_CONFLICTING_MAPPING_541]
ID: 541::
Severity: ERROR

+
Message: Unable to register "%s" as an alternate bind DN for user "%s" because it is already registered as an alternate bind DN for root user "%s".

[#log-ref-log-ref-ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILED_558]
ID: 558::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as an account status notification handler as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_ACCTNOTHANDLER_EXISTS_559]
ID: 559::
Severity: ERROR

+
Message: Unable to add a new account status notification handler entry with DN %s because there is already a notification handler registered with that DN.

[#log-ref-log-ref-ERR_CONFIG_UNABLE_TO_APPLY_STARTUP_CHANGES_563]
ID: 563::
Severity: ERROR

+
Message: An error occurred while attempting to apply the changes contained in file %s to the server configuration at startup: %s.

[#log-ref-log-ref-ERR_CONFIG_ERROR_APPLYING_STARTUP_CHANGE_564]
ID: 564::
Severity: ERROR

+
Message: Unable to apply a change at server startup: %s.

[#log-ref-log-ref-ERR_CONFIG_UNABLE_TO_APPLY_CHANGES_FILE_565]
ID: 565::
Severity: ERROR

+
Message: One or more errors occurred while applying changes on server startup: %s.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_MODE_INVALID_567]
ID: 567::
Severity: ERROR

+
Message: Configuration entry %s does not contain a valid value for configuration attribute ds-cfg-db-directory-permissions (It should be an UNIX permission mode in three-digit octal notation.).

[#log-ref-log-ref-ERR_CONFIG_BACKEND_INSANE_MODE_568]
ID: 568::
Severity: ERROR

+
Message: Invalid UNIX file permissions %s does not allow read and write access to the backend database directory by the backend.

[#log-ref-log-ref-ERR_CONFIG_PWPOLICY_NO_DEFAULT_POLICY_571]
ID: 571::
Severity: ERROR

+
Message: No default password policy is configured for the Directory Server. The default password policy must be specified by the ds-cfg-default-password-policy attribute in the cn=config entry.

[#log-ref-log-ref-ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIR_NO_REASON_573]
ID: 573::
Severity: ERROR

+
Message: An error occurred while trying to create the configuration archive directory %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIR_574]
ID: 574::
Severity: ERROR

+
Message: An error occurred while trying to create the configuration archive directory %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_CANNOT_WRITE_CONFIG_ARCHIVE_575]
ID: 575::
Severity: ERROR

+
Message: An error occurred while trying to write the current configuration to the configuration archive: %s.

[#log-ref-log-ref-ERR_CONFIG_GROUP_INITIALIZATION_FAILED_591]
ID: 591::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a group implementation as in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_ADD_INSUFFICIENT_PRIVILEGES_598]
ID: 598::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform add operations in the Directory Server configuration.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_INSUFFICIENT_PRIVILEGES_599]
ID: 599::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform delete operations in the Directory Server configuration.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODIFY_INSUFFICIENT_PRIVILEGES_600]
ID: 600::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform modify operations in the Directory Server configuration.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODDN_INSUFFICIENT_PRIVILEGES_601]
ID: 601::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform modify DN operations in the Directory Server configuration.

[#log-ref-log-ref-ERR_CONFIG_FILE_SEARCH_INSUFFICIENT_PRIVILEGES_602]
ID: 602::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform search operations in the Directory Server configuration.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODIFY_PRIVS_INSUFFICIENT_PRIVILEGES_603]
ID: 603::
Severity: ERROR

+
Message: You do not have sufficient privileges to change the set of default root privileges.

[#log-ref-log-ref-ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILED_614]
ID: 614::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a certificate mapper as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_KEYMANAGER_CANNOT_GET_BASE_617]
ID: 617::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve the key manager provider base entry cn=Key Manager Providers,cn=config from the Directory Server configuration: %s.

[#log-ref-log-ref-ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILED_627]
ID: 627::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a key manager provider as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_TRUSTMANAGER_CANNOT_GET_BASE_630]
ID: 630::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve the trust manager provider base entry cn=Trust Manager Providers,cn=config from the Directory Server configuration: %s.

[#log-ref-log-ref-ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILED_640]
ID: 640::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as a trust manager provider as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_JMX_CANNOT_GET_ATTRIBUTE_643]
ID: 643::
Severity: ERROR

+
Message: Unable to retrieve JMX attribute %s associated with configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_CHANGE_NO_RESULT_645]
ID: 645::
Severity: ERROR

+
Message: %s.%s returned a result of null for entry %s.

[#log-ref-log-ref-ERR_CONFIG_CHANGE_RESULT_ERROR_646]
ID: 646::
Severity: ERROR

+
Message: %s.%s failed for entry %s: result code=%s, admin action required=%b, messages="%s".

[#log-ref-log-ref-ERR_CONFIG_VATTR_INVALID_SEARCH_FILTER_649]
ID: 649::
Severity: ERROR

+
Message: Unable to parse value "%s" from config entry "%s" as a valid search filter: %s.

[#log-ref-log-ref-ERR_CONFIG_VATTR_INITIALIZATION_FAILED_650]
ID: 650::
Severity: ERROR

+
Message: An error occurred while trying to load an instance of class %s referenced in configuration entry %s as a virtual attribute provider: %s.

[#log-ref-log-ref-ERR_CONFIG_VATTR_SV_TYPE_WITH_MV_PROVIDER_651]
ID: 651::
Severity: ERROR

+
Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but provider %s may generate multiple values.

[#log-ref-log-ref-ERR_CONFIG_VATTR_SV_TYPE_WITH_MERGE_VALUES_652]
ID: 652::
Severity: ERROR

+
Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but the conflict behavior is configured to merge real and virtual values.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODIFY_STRUCTURAL_CHANGE_NOT_ALLOWED_653]
ID: 653::
Severity: ERROR

+
Message: Configuration entry %s cannot be modified because the change would alter its structural object class.

[#log-ref-log-ref-ERR_CONFIG_CANNOT_CALCULATE_DIGEST_654]
ID: 654::
Severity: ERROR

+
Message: An error occurred while attempting to calculate a SHA-1 digest of file %s: %s.

[#log-ref-log-ref-ERR_CONFIG_MANUAL_CHANGES_LOST_656]
ID: 656::
Severity: ERROR

+
Message: The Directory Server encountered an error while attempting to determine whether the configuration file %s has been externally edited with the server online, and/or trying to preserve such changes: %s. Any manual changes made to that file may have been lost.

[#log-ref-log-ref-ERR_CONFIG_ROTATION_POLICY_INVALID_CLASS_657]
ID: 657::
Severity: ERROR

+
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log rotation policy: %s.

[#log-ref-log-ref-ERR_CONFIG_RETENTION_POLICY_INVALID_CLASS_658]
ID: 658::
Severity: ERROR

+
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log retention policy: %s.

[#log-ref-log-ref-ERR_CONFIG_ROTATION_POLICY_CANNOT_CREATE_POLICY_659]
ID: 659::
Severity: ERROR

+
Message: An error occurred while attempting to create a Directory Server log rotation policy from the information in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_RETENTION_POLICY_CANNOT_CREATE_POLICY_660]
ID: 660::
Severity: ERROR

+
Message: An error occurred while attempting to create a Directory Server log retention policy from the information in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_LOGGING_CANNOT_CREATE_WRITER_661]
ID: 661::
Severity: ERROR

+
Message: An error occurred while attempting to create a text writer for a Directory Server logger from the information in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_WORK_QUEUE_INITIALIZATION_FAILED_674]
ID: 674::
Severity: ERROR

+
Message: Unable to initialize an instance of class %s as a work queue as specified in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_ADD_APPLY_FAILED_676]
ID: 676::
Severity: ERROR

+
Message: The attempt to apply the configuration add failed. The preliminary checks were all successful and the entry was added to the server configuration, but at least one of the configuration add listeners reported an error when attempting to apply the change: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_DELETE_APPLY_FAILED_677]
ID: 677::
Severity: ERROR

+
Message: The attempt to apply the configuration delete failed. The preliminary checks were all successful and the entry was removed from the server configuration, but at least one of the configuration delete listeners reported an error when attempting to apply the change: %s.

[#log-ref-log-ref-ERR_CONFIG_FILE_MODIFY_APPLY_FAILED_678]
ID: 678::
Severity: ERROR

+
Message: The attempt to apply the configuration modification failed. The preliminary checks were all successful and the modified entry was written to the server configuration, but at least one of the configuration change listeners reported an error when attempting to apply the change: %s.

[#log-ref-log-ref-ERR_CONFIG_KEYMANAGER_CONFIG_NOT_ACCEPTABLE_679]
ID: 679::
Severity: ERROR

+
Message: The configuration for the key manager provider defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_TRUSTMANAGER_CONFIG_NOT_ACCEPTABLE_680]
ID: 680::
Severity: ERROR

+
Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_AUTHZ_CONFIG_NOT_ACCEPTABLE_681]
ID: 681::
Severity: ERROR

+
Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_ACCTNOTHANDLER_CONFIG_NOT_ACCEPTABLE_682]
ID: 682::
Severity: ERROR

+
Message: The configuration for the account status notification handler defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_SCHEMA_SYNTAX_CONFIG_NOT_ACCEPTABLE_683]
ID: 683::
Severity: ERROR

+
Message: The configuration for the attribute syntax defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_CERTMAPPER_CONFIG_NOT_ACCEPTABLE_684]
ID: 684::
Severity: ERROR

+
Message: The configuration for the certificate mapper defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_GROUP_CONFIG_NOT_ACCEPTABLE_686]
ID: 686::
Severity: ERROR

+
Message: The configuration for the group implementation defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_IDMAPPER_CONFIG_NOT_ACCEPTABLE_687]
ID: 687::
Severity: ERROR

+
Message: The configuration for the identity mapper defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_SCHEMA_MR_CONFIG_NOT_ACCEPTABLE_688]
ID: 688::
Severity: ERROR

+
Message: The configuration for the matching rule defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_PWGENERATOR_CONFIG_NOT_ACCEPTABLE_689]
ID: 689::
Severity: ERROR

+
Message: The configuration for the password generator defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_PWSCHEME_CONFIG_NOT_ACCEPTABLE_690]
ID: 690::
Severity: ERROR

+
Message: The configuration for the password storage scheme defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_PWVALIDATOR_CONFIG_NOT_ACCEPTABLE_691]
ID: 691::
Severity: ERROR

+
Message: The configuration for the password validator defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_PLUGIN_CONFIG_NOT_ACCEPTABLE_692]
ID: 692::
Severity: ERROR

+
Message: The configuration for the plugin defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_SASL_CONFIG_NOT_ACCEPTABLE_693]
ID: 693::
Severity: ERROR

+
Message: The configuration for the SASL mechanism handler defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_VATTR_CONFIG_NOT_ACCEPTABLE_694]
ID: 694::
Severity: ERROR

+
Message: The configuration for the virtual attribute provider defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_ALERTHANDLER_CONFIG_NOT_ACCEPTABLE_695]
ID: 695::
Severity: ERROR

+
Message: The configuration for the alert handler defined in configuration entry %s was not acceptable: %s.

[#log-ref-log-ref-ERR_CONFIG_ALERTHANDLER_INITIALIZATION_FAILED_696]
ID: 696::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as an alert handler as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_CORE_INVALID_SMTP_SERVER_697]
ID: 697::
Severity: ERROR

+
Message: The provided SMTP server value '%s' is invalid. An SMTP server value must have an IP address or a resolvable name, and it may optionally be followed by a colon and an integer value between 1 and 65535 to specify the server port number.

[#log-ref-log-ref-ERR_STARTOK_CANNOT_OPEN_FOR_READING_698]
ID: 698::
Severity: ERROR

+
Message: An error occurred while attempting to open the current configuration file %s for reading in order to copy it to the ".startok" file: %s.

[#log-ref-log-ref-ERR_STARTOK_CANNOT_OPEN_FOR_WRITING_699]
ID: 699::
Severity: ERROR

+
Message: An error occurred while attempting to open file %s in order to write the ".startok" configuration file: %s.

[#log-ref-log-ref-ERR_STARTOK_CANNOT_WRITE_700]
ID: 700::
Severity: ERROR

+
Message: An error occurred while attempting to copy the current configuration from file %s into temporary file %s for use as the ".startok" configuration file: %s.

[#log-ref-log-ref-ERR_STARTOK_CANNOT_RENAME_701]
ID: 701::
Severity: ERROR

+
Message: An error occurred while attempting to rename file %s to %s for use as the ".startok" configuration file: %s.

[#log-ref-log-ref-ERR_CONFIG_JE_PROPERTY_INVALID_704]
ID: 704::
Severity: ERROR

+
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: %s.

[#log-ref-log-ref-ERR_CONFIG_JE_PROPERTY_INVALID_FORM_705]
ID: 705::
Severity: ERROR

+
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property does not follow a singular property=value form.

[#log-ref-log-ref-ERR_CONFIG_JE_PROPERTY_SHADOWS_CONFIG_706]
ID: 706::
Severity: ERROR

+
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property shadows configuration attribute %s.

[#log-ref-log-ref-ERR_CONFIG_JE_DUPLICATE_PROPERTY_707]
ID: 707::
Severity: ERROR

+
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property is already defined for this component.

[#log-ref-log-ref-ERR_CONFIG_LOGGING_CANNOT_OPEN_FILE_709]
ID: 709::
Severity: ERROR

+
Message: An error occurred while attempting to open the configured log file %s for logger %s: %s.

[#log-ref-log-ref-ERR_CONFIG_LOGGING_INSANE_MODE_715]
ID: 715::
Severity: ERROR

+
Message: Invalid UNIX file permissions %s does not allow write access to the log file by the log publisher.

[#log-ref-log-ref-ERR_CONFIG_LOGGING_MODE_INVALID_716]
ID: 716::
Severity: ERROR

+
Message: Invalid UNIX file permissions %s: %s.

[#log-ref-log-ref-ERR_CONFIG_PWPOLICY_DEFAULT_POLICY_IS_WRONG_TYPE_726]
ID: 726::
Severity: ERROR

+
Message: The configuration entry '%s' is currently defined to be the default password policy, however it is not a password policy.

[#log-ref-log-ref-ERR_CONFIG_PWPOLICY_CANNOT_CHANGE_DEFAULT_POLICY_WRONG_TYPE_727]
ID: 727::
Severity: ERROR

+
Message: The default password policy value '%s' is invalid because it refers to an authentication policy which is not a password policy.

[#log-ref-log-ref-ERR_CONFIG_LOGGING_INVALID_TIME_FORMAT_728]
ID: 728::
Severity: ERROR

+
Message: The timestamp format string "%s" is not a valid format string. The format string should conform to the syntax described in the documentation for the "java.text.SimpleDateFormat" class.

[#log-ref-log-ref-ERR_CONFIG_LOGGING_INVALID_USER_DN_PATTERN_729]
ID: 729::
Severity: ERROR

+
Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s".

[#log-ref-log-ref-ERR_CONFIG_LOGGING_INVALID_TARGET_DN_PATTERN_730]
ID: 730::
Severity: ERROR

+
Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s".

[#log-ref-log-ref-ERR_CONFIG_LOGGER_INVALID_HTTP_ACCESS_LOGGER_CLASS_732]
ID: 732::
Severity: ERROR

+
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server HTTP access logger: %s.

[#log-ref-log-ref-ERR_CONFIG_LOGGING_EMPTY_LOG_FORMAT_733]
ID: 733::
Severity: ERROR

+
Message: The log format for configuration entry %s is empty. No information will be logged even if logging is activated.

[#log-ref-log-ref-ERR_CONFIG_LOGGER_CANNOT_UPDATE_LOGGER_735]
ID: 735::
Severity: ERROR

+
Message: An error occurred while attempting to update a Directory Server logger from the information in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_LOGGER_CANNOT_DELETE_LOGGER_736]
ID: 736::
Severity: ERROR

+
Message: An error occurred while attempting to delete a Directory Server logger from the information in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_CANNOT_CONFIGURE_JUL_LOGGER_737]
ID: 737::
Severity: ERROR

+
Message: Cannot configure java.util.logging root logger level: %s. java.util.logging support is now disabled.

[#log-ref-log-ref-ERR_CONFIG_HTTPENDPOINT_INITIALIZATION_FAILED_738]
ID: 738::
Severity: ERROR

+
Message: An error occurred while trying to initialize an instance of class %s as an HTTP endpoint as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_HTTPENDPOINT_UNABLE_TO_START_739]
ID: 739::
Severity: ERROR

+
Message: An error occurred while starting the HTTP endpoint as defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_HTTPENDPOINT_INVALID_CONFIGURATION_741]
ID: 741::
Severity: ERROR

+
Message: The HTTP endpoint configuration defined in %s is invalid: %s.

[#log-ref-log-ref-ERR_CONFIG_REST2LDAP_MALFORMED_URL_742]
ID: 742::
Severity: ERROR

+
Message: Invalid configuration URL in the REST2LDAP endpoint configuration entry %s: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_CONFIGURATION_FRAMEWORK_743]
ID: 743::
Severity: ERROR

+
Message: Cannot initialize the configuration framework: %s.

[#log-ref-log-ref-ERR_UNABLE_TO_RETRIEVE_CHILDREN_OF_CONFIGURATION_ENTRY_744]
ID: 744::
Severity: ERROR

+
Message: Unable to retrieve children of configuration entry with dn: %s.

[#log-ref-log-ref-ERR_UNABLE_TO_LOAD_CONFIGURATION_ENABLED_SCHEMA_745]
ID: 745::
Severity: ERROR

+
Message: Unable to load the configuration-enabled schema: %s.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_CANNOT_DELETE_ENTRY_746]
ID: 746::
Severity: ERROR

+
Message: Backend config error when trying to delete an entry: %s.

[#log-ref-log-ref-ERR_CONFIG_HTTPENDPOINT_INVALID_AUTHZ_DN_747]
ID: 747::
Severity: ERROR

+
Message: The HTTP endpoint configuration defined in %s is referencing a non existing authorization DN %s.

[#log-ref-log-ref-ERR_CONFIG_HTTPENDPOINT_CONFLICTING_AUTHZ_DN_748]
ID: 748::
Severity: ERROR

+
Message: The HTTP endpoint configuration defined in %s is referencing mutually exclusive authorization DNs %s and %s.

[#log-ref-log-ref-ERR_CONFIG_REST2LDAP_UNABLE_READ_749]
ID: 749::
Severity: ERROR

+
Message: Unable to read the configuration from %s in the REST2LDAP endpoint configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_REST2LDAP_UNEXPECTED_JSON_750]
ID: 750::
Severity: ERROR

+
Message: Invalid JSON element %s from %s in the REST2LDAP endpoint configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_REST2LDAP_INVALID_751]
ID: 751::
Severity: ERROR

+
Message: Invalid configuration element from %s in the REST2LDAP endpoint configuration entry %s: %s.

[#log-ref-log-ref-ERR_CONFIG_OAUTH2_INVALID_JSON_POINTER_752]
ID: 752::
Severity: ERROR

+
Message: The OAuth2 authorization mechanism defined in %s contains an invalid JSON Pointer %s: %s.

[#log-ref-log-ref-ERR_CONFIG_OAUTH2_NON_EXISTING_DIRECTORY_753]
ID: 753::
Severity: ERROR

+
Message: The authorization mechanism defined in %s is referencing a non-existing or non-readable directory: %s.

[#log-ref-log-ref-ERR_CONFIG_AUTHZ_REFERENCED_DN_DOESNT_EXISTS_754]
ID: 754::
Severity: ERROR

+
Message: The authorization mechanism defined in %s is referencing a non existing DN: %s.

[#log-ref-log-ref-ERR_CONFIG_OAUTH2_INVALID_URL_755]
ID: 755::
Severity: ERROR

+
Message: The authorization mechanism defined in %s is referencing an invalid URL %s: %s.

[#log-ref-log-ref-ERR_CONFIG_OAUTH2_CONFIG_ERROR_756]
ID: 756::
Severity: ERROR

+
Message: Unable to configure the authorization mechanism defined in %s: %s.

[#log-ref-log-ref-ERR_BAD_ADMIN_API_RESOURCE_VERSION_757]
ID: 757::
Severity: ERROR

+
Message: The requested admin API version '%s' is unsupported. This endpoint only supports the following admin API version(s): %s.

[#log-ref-log-ref-ERR_CONFIG_BACKEND_BASE_IS_EMPTY_763]
ID: 763::
Severity: ERROR

+
Message: Unable to configure the backend '%s' because one of its base DNs is the empty DN.

--


[#CORE]
=== Log Message Category: CORE

--

[#log-ref-log-ref-ERR_CANNOT_CANCEL_ABANDON_1]
ID: 1::
Severity: ERROR

+
Message: Abandon requests cannot be canceled.

[#log-ref-log-ref-ERR_CANNOT_CANCEL_BIND_2]
ID: 2::
Severity: ERROR

+
Message: Bind requests cannot be canceled.

[#log-ref-log-ref-ERR_CANNOT_CANCEL_UNBIND_3]
ID: 3::
Severity: ERROR

+
Message: Unbind requests cannot be canceled.

[#log-ref-log-ref-ERR_UNCAUGHT_WORKER_THREAD_EXCEPTION_108]
ID: 108::
Severity: ERROR

+
Message: %s encountered an uncaught exception while processing operation %s: %s.

[#log-ref-log-ref-ERR_CANNOT_BOOTSTRAP_WHILE_RUNNING_118]
ID: 118::
Severity: ERROR

+
Message: The Directory Server is currently running. The configuration may not be bootstrapped while the server is online.

[#log-ref-log-ref-ERR_CANNOT_INSTANTIATE_CONFIG_HANDLER_120]
ID: 120::
Severity: ERROR

+
Message: Unable to create an instance of class %s to serve as the Directory Server configuration handler: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_CONFIG_HANDLER_121]
ID: 121::
Severity: ERROR

+
Message: An error occurred while trying to initialize the configuration handler %s using configuration file %s: %s.

[#log-ref-log-ref-ERR_CANNOT_START_BEFORE_BOOTSTRAP_122]
ID: 122::
Severity: ERROR

+
Message: The Directory Server may not be started before the configuration has been bootstrapped.

[#log-ref-log-ref-ERR_CANNOT_START_WHILE_RUNNING_123]
ID: 123::
Severity: ERROR

+
Message: The Directory Server may not be started while it is already running. Please stop the running instance before attempting to start it again.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_MISSING_REQUIRED_ATTR_FOR_OC_126]
ID: 126::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it is missing attribute %s which is required by objectclass %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_DISALLOWED_USER_ATTR_FOR_OC_127]
ID: 127::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_CANNOT_BOOTSTRAP_SYNTAX_130]
ID: 130::
Severity: ERROR

+
Message: An error occurred while attempting to bootstrap the attribute syntax defined in class %s: %s.

[#log-ref-log-ref-ERR_CANNOT_CREATE_MBEAN_SERVER_138]
ID: 138::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_UNCAUGHT_THREAD_EXCEPTION_140]
ID: 140::
Severity: ERROR

+
Message: An uncaught exception during processing for thread %s has caused it to terminate abnormally. The stack trace for that exception is: %s.

[#log-ref-log-ref-ERR_SHUTDOWN_DUE_TO_SHUTDOWN_HOOK_142]
ID: 142::
Severity: ERROR

+
Message: 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).

[#log-ref-log-ref-ERR_SEARCH_FILTER_NULL_143]
ID: 143::
Severity: ERROR

+
Message: Unable to decode the provided filter string as a search filter because the provided string was empty or null.

[#log-ref-log-ref-ERR_SEARCH_FILTER_UNCAUGHT_EXCEPTION_144]
ID: 144::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to decode the string "%s" as a search filter: %s.

[#log-ref-log-ref-ERR_SEARCH_FILTER_MISMATCHED_PARENTHESES_145]
ID: 145::
Severity: ERROR

+
Message: The provided search filter "%s" had mismatched parentheses around the portion between positions %d and %d.

[#log-ref-log-ref-ERR_SEARCH_FILTER_NO_EQUAL_SIGN_146]
ID: 146::
Severity: ERROR

+
Message: The provided search filter "%s" was missing an equal sign in the suspected simple filter component between positions %d and %d.

[#log-ref-log-ref-ERR_SEARCH_FILTER_INVALID_ESCAPED_BYTE_147]
ID: 147::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_FILTER_COMPOUND_MISSING_PARENTHESES_148]
ID: 148::
Severity: ERROR

+
Message: 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).

[#log-ref-log-ref-ERR_SEARCH_FILTER_NO_CORRESPONDING_OPEN_PARENTHESIS_149]
ID: 149::
Severity: ERROR

+
Message: The provided search filter "%s" could not be decoded because the closing parenthesis at position %d did not have a corresponding open parenthesis.

[#log-ref-log-ref-ERR_SEARCH_FILTER_NO_CORRESPONDING_CLOSE_PARENTHESIS_150]
ID: 150::
Severity: ERROR

+
Message: The provided search filter "%s" could not be decoded because the opening parenthesis at position %d did not have a corresponding close parenthesis.

[#log-ref-log-ref-ERR_SEARCH_FILTER_SUBSTRING_NO_ASTERISKS_151]
ID: 151::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_COLON_152]
ID: 152::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_FILTER_INVALID_FILTER_TYPE_153]
ID: 153::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because it contained an unknown filter type %s.

[#log-ref-log-ref-ERR_SEARCH_FILTER_INVALID_RESULT_TYPE_154]
ID: 154::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because the internal check returned an unknown result type "%s".

[#log-ref-log-ref-ERR_SEARCH_FILTER_COMPOUND_COMPONENTS_NULL_155]
ID: 155::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because the set of filter components for an %s component was NULL.

[#log-ref-log-ref-ERR_SEARCH_FILTER_NESTED_TOO_DEEP_156]
ID: 156::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because the filter was nested beyond the maximum allowed depth of 100 levels.

[#log-ref-log-ref-ERR_SEARCH_FILTER_NOT_COMPONENT_NULL_157]
ID: 157::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because the NOT filter component did not include a subcomponent.

[#log-ref-log-ref-ERR_SEARCH_FILTER_EQUALITY_NO_ATTRIBUTE_TYPE_158]
ID: 158::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because an equality component had a NULL attribute type.

[#log-ref-log-ref-ERR_SEARCH_FILTER_EQUALITY_NO_ASSERTION_VALUE_159]
ID: 159::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because an equality component for attribute %s had a NULL assertion value.

[#log-ref-log-ref-ERR_SEARCH_FILTER_SUBSTRING_NO_ATTRIBUTE_TYPE_160]
ID: 160::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because a substring component had a NULL attribute type.

[#log-ref-log-ref-ERR_SEARCH_FILTER_SUBSTRING_NO_SUBSTRING_COMPONENTS_161]
ID: 161::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_FILTER_GREATER_OR_EQUAL_NO_ATTRIBUTE_TYPE_162]
ID: 162::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because a greater-or-equal component had a NULL attribute type.

[#log-ref-log-ref-ERR_SEARCH_FILTER_GREATER_OR_EQUAL_NO_VALUE_163]
ID: 163::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because a greater-or-equal component for attribute %s had a NULL assertion value.

[#log-ref-log-ref-ERR_SEARCH_FILTER_LESS_OR_EQUAL_NO_ATTRIBUTE_TYPE_164]
ID: 164::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because a less-or-equal component had a NULL attribute type.

[#log-ref-log-ref-ERR_SEARCH_FILTER_LESS_OR_EQUAL_NO_ASSERTION_VALUE_165]
ID: 165::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because a less-or-equal component for attribute %s had a NULL assertion value.

[#log-ref-log-ref-ERR_SEARCH_FILTER_PRESENCE_NO_ATTRIBUTE_TYPE_166]
ID: 166::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because a presence component had a NULL attribute type.

[#log-ref-log-ref-ERR_SEARCH_FILTER_APPROXIMATE_NO_ATTRIBUTE_TYPE_167]
ID: 167::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because an approximate component had a NULL attribute type.

[#log-ref-log-ref-ERR_SEARCH_FILTER_APPROXIMATE_NO_ASSERTION_VALUE_168]
ID: 168::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because an approximate component for attribute %s had a NULL assertion value.

[#log-ref-log-ref-ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_ASSERTION_VALUE_169]
ID: 169::
Severity: ERROR

+
Message: Unable to determine whether entry "%s" matches filter "%s" because a contained extensible match filter did not have an assertion value.

[#log-ref-log-ref-ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_RULE_OR_TYPE_170]
ID: 170::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_RDN_DECODE_NULL_171]
ID: 171::
Severity: ERROR

+
Message: Unable to decode the provided string as a relative distinguished name because the provided string was empty or null.

[#log-ref-log-ref-ERR_RDN_END_WITH_ATTR_NAME_172]
ID: 172::
Severity: ERROR

+
Message: Unable to decode the provided string "%s" as a relative distinguished name because the string ended with an attribute type name (%s).

[#log-ref-log-ref-ERR_RDN_NO_EQUAL_173]
ID: 173::
Severity: ERROR

+
Message: 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).

[#log-ref-log-ref-ERR_RDN_UNEXPECTED_COMMA_174]
ID: 174::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_RDN_ILLEGAL_CHARACTER_175]
ID: 175::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_CANNOT_GET_ROOT_DSE_CONFIG_ENTRY_183]
ID: 183::
Severity: ERROR

+
Message: An error occurred while trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) from the Directory Server configuration: %s.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_OBJECTCLASS_OID_186]
ID: 186::
Severity: ERROR

+
Message: Unable to register objectclass %s with the server schema because its OID %s conflicts with the OID of an existing objectclass %s.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_OBJECTCLASS_NAME_187]
ID: 187::
Severity: ERROR

+
Message: Unable to register objectclass %s with the server schema because its name %s conflicts with the name of an existing objectclass %s.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_MR_NAME_190]
ID: 190::
Severity: ERROR

+
Message: Unable to register matching rule %s with the server schema because its name %s conflicts with the name of an existing matching rule %s.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_MATCHING_RULE_USE_191]
ID: 191::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_DIT_CONTENT_RULE_192]
ID: 192::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_DIT_STRUCTURE_RULE_NAME_FORM_193]
ID: 193::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_DIT_STRUCTURE_RULE_ID_194]
ID: 194::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_NAME_FORM_OC_195]
ID: 195::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_NAME_FORM_OID_196]
ID: 196::
Severity: ERROR

+
Message: Unable to register name form %s with the server schema because its OID %s conflicts with the OID for an existing name form %s.

[#log-ref-log-ref-ERR_SCHEMA_CONFLICTING_NAME_FORM_NAME_197]
ID: 197::
Severity: ERROR

+
Message: Unable to register name form %s with the server schema because its name %s conflicts with the name for an existing name form %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_MULTIPLE_STRUCTURAL_CLASSES_198]
ID: 198::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_NO_STRUCTURAL_CLASS_199]
ID: 199::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it does not include a structural objectclass. All entries must contain a structural objectclass.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_ATTR_SINGLE_VALUED_205]
ID: 205::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it includes multiple values for attribute %s, which is defined as a single-valued attribute.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_RDN_MISSING_REQUIRED_ATTR_206]
ID: 206::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because its RDN does not contain attribute %s that is required by name form %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_RDN_DISALLOWED_ATTR_207]
ID: 207::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because its RDN contains attribute %s that is not allowed by name form %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_MISSING_REQUIRED_ATTR_FOR_DCR_208]
ID: 208::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it is missing attribute %s which is required by DIT content rule %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_PROHIBITED_ATTR_FOR_DCR_209]
ID: 209::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it contains attribute %s which is prohibited by DIT content rule %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_DISALLOWED_AUXILIARY_CLASS_211]
ID: 211::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it includes auxiliary objectClass %s that is not allowed by DIT content rule %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_DSR_NO_PARENT_ENTRY_213]
ID: 213::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_DSR_NO_PARENT_OC_214]
ID: 214::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_DSR_DISALLOWED_SUPERIOR_OC_215]
ID: 215::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_COULD_NOT_CHECK_DSR_216]
ID: 216::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to check entry %s against DIT structure rule %s: %s.

[#log-ref-log-ref-ERR_BIND_OPERATION_UNKNOWN_USER_218]
ID: 218::
Severity: ERROR

+
Message: Unable to bind to the Directory Server because no such user exists in the server.

[#log-ref-log-ref-ERR_STARTUP_PLUGIN_ERROR_220]
ID: 220::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_BIND_OPERATION_NO_PASSWORD_221]
ID: 221::
Severity: ERROR

+
Message: Unable to bind to the Directory Server using simple authentication because that user does not have a password.

[#log-ref-log-ref-ERR_BIND_OPERATION_UNKNOWN_SASL_MECHANISM_222]
ID: 222::
Severity: ERROR

+
Message: Unable to process the bind request because it attempted to use an unknown SASL mechanism %s that is not available in the Directory Server.

[#log-ref-log-ref-ERR_COMPARE_NO_SUCH_ENTRY_228]
ID: 228::
Severity: ERROR

+
Message: The specified entry %s does not exist in the Directory Server.

[#log-ref-log-ref-ERR_ADD_CANNOT_ADD_ROOT_DSE_230]
ID: 230::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ADD_ENTRY_NOT_SUFFIX_231]
ID: 231::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ADD_NO_PARENT_233]
ID: 233::
Severity: ERROR

+
Message: Entry %s cannot be added because its parent entry %s does not exist in the server.

[#log-ref-log-ref-ERR_ADD_CANNOT_LOCK_ENTRY_234]
ID: 234::
Severity: ERROR

+
Message: Entry %s cannot be added because the server failed to obtain a write lock for this entry after multiple attempts.

[#log-ref-log-ref-ERR_DELETE_CANNOT_LOCK_ENTRY_235]
ID: 235::
Severity: ERROR

+
Message: Entry %s cannot be removed because the server failed to obtain a write lock for this entry after multiple attempts.

[#log-ref-log-ref-ERR_SEARCH_TIME_LIMIT_EXCEEDED_238]
ID: 238::
Severity: ERROR

+
Message: The maximum time limit of %d seconds for processing this search operation has expired.

[#log-ref-log-ref-ERR_SEARCH_SIZE_LIMIT_EXCEEDED_239]
ID: 239::
Severity: ERROR

+
Message: This search operation has sent the maximum of %d entries to the client.

[#log-ref-log-ref-ERR_SEARCH_BASE_DOESNT_EXIST_240]
ID: 240::
Severity: ERROR

+
Message: The entry %s specified as the search base does not exist in the Directory Server.

[#log-ref-log-ref-ERR_DELETE_NO_SUCH_ENTRY_241]
ID: 241::
Severity: ERROR

+
Message: Entry %s does not exist in the Directory Server.

[#log-ref-log-ref-ERR_DELETE_HAS_SUB_BACKEND_242]
ID: 242::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODDN_NO_PARENT_243]
ID: 243::
Severity: ERROR

+
Message: A modify DN operation cannot be performed on entry %s because the new RDN would not have a parent DN.

[#log-ref-log-ref-ERR_MODDN_NO_BACKEND_FOR_CURRENT_ENTRY_244]
ID: 244::
Severity: ERROR

+
Message: The modify DN operation for entry %s cannot be performed because no backend is registered to handle that DN.

[#log-ref-log-ref-ERR_MODDN_NO_BACKEND_FOR_NEW_ENTRY_245]
ID: 245::
Severity: ERROR

+
Message: The modify DN operation for entry %s cannot be performed because no backend is registered to handle the new DN %s.

[#log-ref-log-ref-ERR_MODDN_DIFFERENT_BACKENDS_246]
ID: 246::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODDN_CANNOT_LOCK_CURRENT_DN_247]
ID: 247::
Severity: ERROR

+
Message: The modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for that DN.

[#log-ref-log-ref-ERR_MODDN_CANNOT_LOCK_NEW_DN_249]
ID: 249::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODDN_NO_CURRENT_ENTRY_250]
ID: 250::
Severity: ERROR

+
Message: The modify DN operation for entry %s cannot be performed because that entry does not exist in the server.

[#log-ref-log-ref-ERR_MODIFY_CANNOT_LOCK_ENTRY_251]
ID: 251::
Severity: ERROR

+
Message: Entry %s cannot be modified because the server failed to obtain a write lock for this entry after multiple attempts.

[#log-ref-log-ref-ERR_MODIFY_NO_SUCH_ENTRY_252]
ID: 252::
Severity: ERROR

+
Message: Entry %s cannot be modified because no such entry exists in the server.

[#log-ref-log-ref-ERR_MODIFY_ADD_NO_VALUES_253]
ID: 253::
Severity: ERROR

+
Message: Entry %s cannot be modified because the modification contained an add component for attribute %s but no values were provided.

[#log-ref-log-ref-ERR_MODIFY_ADD_INVALID_SYNTAX_254]
ID: 254::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_ADD_DUPLICATE_VALUE_255]
ID: 255::
Severity: ERROR

+
Message: Entry %s cannot be modified because it would have resulted in one or more duplicate values for attribute %s: %s.

[#log-ref-log-ref-ERR_MODIFY_DELETE_RDN_ATTR_256]
ID: 256::
Severity: ERROR

+
Message: Entry %s cannot be modified because the change to attribute %s would have removed a value used in the RDN.

[#log-ref-log-ref-ERR_MODIFY_DELETE_MISSING_VALUES_257]
ID: 257::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_DELETE_NO_SUCH_ATTR_258]
ID: 258::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_REPLACE_INVALID_SYNTAX_259]
ID: 259::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_INCREMENT_RDN_260]
ID: 260::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_INCREMENT_REQUIRES_VALUE_261]
ID: 261::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_INCREMENT_REQUIRES_SINGLE_VALUE_262]
ID: 262::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_INCREMENT_PROVIDED_VALUE_NOT_INTEGER_263]
ID: 263::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_INCREMENT_REQUIRES_EXISTING_VALUE_264]
ID: 264::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_INCREMENT_REQUIRES_INTEGER_VALUE_265]
ID: 265::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_VIOLATES_SCHEMA_266]
ID: 266::
Severity: ERROR

+
Message: Entry %s cannot be modified because the resulting entry would have violated the server schema: %s.

[#log-ref-log-ref-ERR_MODIFY_NO_BACKEND_FOR_ENTRY_267]
ID: 267::
Severity: ERROR

+
Message: Entry %s cannot be modified because there is no backend registered to handle operations for that entry.

[#log-ref-log-ref-ERR_EXTENDED_NO_HANDLER_268]
ID: 268::
Severity: ERROR

+
Message: There is no extended operation handler registered with the Directory Server for handling extended operations with a request OID of %s.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_UNKNOWN_OC_269]
ID: 269::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it contains an unknown objectclass %s.

[#log-ref-log-ref-ERR_SEARCH_BACKEND_EXCEPTION_270]
ID: 270::
Severity: ERROR

+
Message: An unexpected error was encountered while processing a search in one of the Directory Server backends: %s.

[#log-ref-log-ref-ERR_MODDN_VIOLATES_SCHEMA_271]
ID: 271::
Severity: ERROR

+
Message: The modify DN operation for entry %s cannot be performed because the change would have violated the server schema: %s.

[#log-ref-log-ref-ERR_ENTRY_ADD_UNKNOWN_OC_276]
ID: 276::
Severity: ERROR

+
Message: Object class %s cannot be added to entry %s because that class is not defined in the Directory Server schema.

[#log-ref-log-ref-ERR_ENTRY_ADD_DUPLICATE_OC_277]
ID: 277::
Severity: ERROR

+
Message: Object class %s is already present in entry %s and cannot be added a second time.

[#log-ref-log-ref-ERR_BIND_OPERATION_WRONG_PASSWORD_279]
ID: 279::
Severity: ERROR

+
Message: The password provided by the user did not match any password(s) stored in the user's entry.

[#log-ref-log-ref-ERR_DSCORE_CANNOT_INITIALIZE_ARGS_288]
ID: 288::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the command-line arguments: %s.

[#log-ref-log-ref-ERR_DSCORE_ERROR_PARSING_ARGS_289]
ID: 289::
Severity: ERROR

+
Message: An error occurred while attempting to parse the provided set of command line arguments: %s.

[#log-ref-log-ref-ERR_DSCORE_CANNOT_BOOTSTRAP_290]
ID: 290::
Severity: ERROR

+
Message: An error occurred while attempting to bootstrap the Directory Server: %s.

[#log-ref-log-ref-ERR_DSCORE_CANNOT_START_291]
ID: 291::
Severity: ERROR

+
Message: An error occurred while trying to start the Directory Server: %s.

[#log-ref-log-ref-ERR_BACKUPINFO_NO_DELIMITER_292]
ID: 292::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_BACKUPINFO_NO_NAME_293]
ID: 293::
Severity: ERROR

+
Message: The line "%s" associated with the backup information in directory %s could not be parsed because it did not include a property name.

[#log-ref-log-ref-ERR_BACKUPINFO_MULTIPLE_BACKUP_IDS_294]
ID: 294::
Severity: ERROR

+
Message: The backup information structure in directory %s could not be parsed because it contained multiple backup IDs (%s and %s).

[#log-ref-log-ref-ERR_BACKUPINFO_UNKNOWN_PROPERTY_295]
ID: 295::
Severity: ERROR

+
Message: The backup information structure in directory %s could not be parsed because it contained an unknown property %s with value %s.

[#log-ref-log-ref-ERR_BACKUPINFO_CANNOT_DECODE_296]
ID: 296::
Severity: ERROR

+
Message: An unexpected error occurred while trying to decode a backup information structure in directory %s: %s.

[#log-ref-log-ref-ERR_BACKUPINFO_NO_BACKUP_ID_297]
ID: 297::
Severity: ERROR

+
Message: Unable to decode a backup information structure in directory %s because the structure did not include a backup ID.

[#log-ref-log-ref-ERR_BACKUPINFO_NO_BACKUP_DATE_298]
ID: 298::
Severity: ERROR

+
Message: The backup information structure with backup ID %s in directory %s was not valid because it did not contain the backup date.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_ADD_DUPLICATE_ID_299]
ID: 299::
Severity: ERROR

+
Message: Cannot add a backup with ID %s to backup directory %s because another backup already exists with that ID.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_NO_SUCH_BACKUP_300]
ID: 300::
Severity: ERROR

+
Message: Cannot remove backup %s from backup directory %s because no backup with that ID exists in that directory.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_UNRESOLVED_DEPENDENCY_301]
ID: 301::
Severity: ERROR

+
Message: Cannot remove backup %s from backup directory %s because it is listed as a dependency for backup %s.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_CANNOT_CREATE_DIRECTORY_302]
ID: 302::
Severity: ERROR

+
Message: Backup directory %s does not exist and an error occurred while attempting to create it: %s.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_NOT_DIRECTORY_303]
ID: 303::
Severity: ERROR

+
Message: The backup directory path %s exists but does not reference a directory.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_CANNOT_DELETE_SAVED_DESCRIPTOR_304]
ID: 304::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_CANNOT_RENAME_CURRENT_DESCRIPTOR_305]
ID: 305::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_CANNOT_RENAME_NEW_DESCRIPTOR_306]
ID: 306::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_NO_DESCRIPTOR_FILE_307]
ID: 307::
Severity: ERROR

+
Message: No backup directory descriptor file was found at %s.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_CANNOT_READ_CONFIG_ENTRY_DN_308]
ID: 308::
Severity: ERROR

+
Message: The backup descriptor file %s is invalid because the first line should have contained the DN of the backend configuration entry but was blank.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_FIRST_LINE_NOT_DN_309]
ID: 309::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_BACKUPDIRECTORY_CANNOT_DECODE_DN_310]
ID: 310::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_SHARED_REJECTED_BY_EXCLUSIVE_311]
ID: 311::
Severity: ERROR

+
Message: The attempt to obtain a shared lock on file %s was rejected because an exclusive lock was already held on that file.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_SHARED_FAILED_CREATE_312]
ID: 312::
Severity: ERROR

+
Message: The attempt to obtain a shared lock on file %s was rejected because the attempt to create the lock file failed: %s.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_SHARED_FAILED_OPEN_313]
ID: 313::
Severity: ERROR

+
Message: The attempt to obtain a shared lock on file %s was rejected because the attempt to open the lock file failed: %s.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_SHARED_FAILED_LOCK_314]
ID: 314::
Severity: ERROR

+
Message: The attempt to obtain a shared lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_SHARED_NOT_GRANTED_315]
ID: 315::
Severity: ERROR

+
Message: The shared lock requested for file %s was not granted, which indicates that another process already holds an exclusive lock on that file.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_EXCLUSIVE_316]
ID: 316::
Severity: ERROR

+
Message: The attempt to obtain an exclusive lock on file %s was rejected because an exclusive lock was already held on that file.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_EXCLUSIVE_REJECTED_BY_SHARED_317]
ID: 317::
Severity: ERROR

+
Message: The attempt to obtain an exclusive lock on file %s was rejected because a shared lock was already held on that file.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_CREATE_318]
ID: 318::
Severity: ERROR

+
Message: The attempt to obtain an exclusive lock on file %s was rejected because the attempt to create the lock file failed: %s.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_OPEN_319]
ID: 319::
Severity: ERROR

+
Message: The attempt to obtain an exclusive lock on file %s was rejected because the attempt to open the lock file failed: %s.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_EXCLUSIVE_FAILED_LOCK_320]
ID: 320::
Severity: ERROR

+
Message: The attempt to obtain an exclusive lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s.

[#log-ref-log-ref-ERR_FILELOCKER_LOCK_EXCLUSIVE_NOT_GRANTED_321]
ID: 321::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_FILELOCKER_UNLOCK_EXCLUSIVE_FAILED_RELEASE_322]
ID: 322::
Severity: ERROR

+
Message: The attempt to release the exclusive lock held on %s failed: %s.

[#log-ref-log-ref-ERR_FILELOCKER_UNLOCK_SHARED_FAILED_RELEASE_323]
ID: 323::
Severity: ERROR

+
Message: The attempt to release the shared lock held on %s failed: %s.

[#log-ref-log-ref-ERR_FILELOCKER_UNLOCK_UNKNOWN_FILE_324]
ID: 324::
Severity: ERROR

+
Message: The attempt to release the lock held on %s failed because no record of a lock on that file was found.

[#log-ref-log-ref-ERR_CANNOT_ACQUIRE_EXCLUSIVE_SERVER_LOCK_343]
ID: 343::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_ATTR_IS_NO_USER_MOD_346]
ID: 346::
Severity: ERROR

+
Message: Entry %s cannot be modified because the modification attempted to update attribute %s which is defined as NO-USER-MODIFICATION in the server schema.

[#log-ref-log-ref-ERR_ADD_ATTR_IS_NO_USER_MOD_347]
ID: 347::
Severity: ERROR

+
Message: Entry %s cannot be added because it includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema.

[#log-ref-log-ref-ERR_MODDN_OLD_RDN_ATTR_IS_NO_USER_MOD_348]
ID: 348::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODDN_NEW_RDN_ATTR_IS_NO_USER_MOD_349]
ID: 349::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODDN_PREOP_VIOLATES_SCHEMA_356]
ID: 356::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_ASSERTION_FAILED_357]
ID: 357::
Severity: ERROR

+
Message: Entry %s cannot be modified because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

[#log-ref-log-ref-ERR_MODIFY_CANNOT_PROCESS_ASSERTION_FILTER_358]
ID: 358::
Severity: ERROR

+
Message: 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 the control: %s.

[#log-ref-log-ref-ERR_MODIFY_UNSUPPORTED_CRITICAL_CONTROL_359]
ID: 359::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_DELETE_ASSERTION_FAILED_362]
ID: 362::
Severity: ERROR

+
Message: Entry %s cannot be removed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

[#log-ref-log-ref-ERR_DELETE_CANNOT_PROCESS_ASSERTION_FILTER_363]
ID: 363::
Severity: ERROR

+
Message: 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 the control: %s.

[#log-ref-log-ref-ERR_DELETE_UNSUPPORTED_CRITICAL_CONTROL_364]
ID: 364::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODDN_ASSERTION_FAILED_365]
ID: 365::
Severity: ERROR

+
Message: Entry %s cannot be renamed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

[#log-ref-log-ref-ERR_MODDN_CANNOT_PROCESS_ASSERTION_FILTER_366]
ID: 366::
Severity: ERROR

+
Message: 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 the control: %s.

[#log-ref-log-ref-ERR_MODDN_UNSUPPORTED_CRITICAL_CONTROL_367]
ID: 367::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ADD_ASSERTION_FAILED_368]
ID: 368::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ADD_CANNOT_PROCESS_ASSERTION_FILTER_369]
ID: 369::
Severity: ERROR

+
Message: 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 the control: %s.

[#log-ref-log-ref-ERR_ADD_UNSUPPORTED_CRITICAL_CONTROL_370]
ID: 370::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_CANNOT_GET_ENTRY_FOR_ASSERTION_371]
ID: 371::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_NO_SUCH_ENTRY_FOR_ASSERTION_372]
ID: 372::
Severity: ERROR

+
Message: The search request cannot be processed because it contains an LDAP assertion control but the search base entry does not exist.

[#log-ref-log-ref-ERR_SEARCH_ASSERTION_FAILED_373]
ID: 373::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_CANNOT_PROCESS_ASSERTION_FILTER_374]
ID: 374::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_UNSUPPORTED_CRITICAL_CONTROL_375]
ID: 375::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_COMPARE_ASSERTION_FAILED_376]
ID: 376::
Severity: ERROR

+
Message: Cannot perform the compare operation on entry %s because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

[#log-ref-log-ref-ERR_COMPARE_CANNOT_PROCESS_ASSERTION_FILTER_377]
ID: 377::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_COMPARE_UNSUPPORTED_CRITICAL_CONTROL_378]
ID: 378::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ADD_MISSING_RDN_ATTRIBUTE_385]
ID: 385::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_BIND_UNSUPPORTED_CRITICAL_CONTROL_394]
ID: 394::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ADD_ENTRY_ALREADY_EXISTS_400]
ID: 400::
Severity: ERROR

+
Message: The entry %s cannot be added because an entry with that name already exists.

[#log-ref-log-ref-ERR_ADD_SYNCH_PREOP_FAILED_401]
ID: 401::
Severity: ERROR

+
Message: An error occurred during preoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_ADD_SYNCH_POSTOP_FAILED_402]
ID: 402::
Severity: ERROR

+
Message: An error occurred during postoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_DELETE_SYNCH_PREOP_FAILED_403]
ID: 403::
Severity: ERROR

+
Message: An error occurred during preoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_DELETE_SYNCH_POSTOP_FAILED_404]
ID: 404::
Severity: ERROR

+
Message: An error occurred during postoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_MODIFY_SYNCH_PREOP_FAILED_405]
ID: 405::
Severity: ERROR

+
Message: An error occurred during preoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_MODIFY_SYNCH_POSTOP_FAILED_406]
ID: 406::
Severity: ERROR

+
Message: An error occurred during postoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_MODDN_SYNCH_PREOP_FAILED_407]
ID: 407::
Severity: ERROR

+
Message: An error occurred during preoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_MODDN_SYNCH_POSTOP_FAILED_408]
ID: 408::
Severity: ERROR

+
Message: An error occurred during postoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_ADD_SYNCH_CONFLICT_RESOLUTION_FAILED_409]
ID: 409::
Severity: ERROR

+
Message: An error occurred during conflict resolution synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_DELETE_SYNCH_CONFLICT_RESOLUTION_FAILED_410]
ID: 410::
Severity: ERROR

+
Message: An error occurred during conflict resolution synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_MODIFY_SYNCH_CONFLICT_RESOLUTION_FAILED_411]
ID: 411::
Severity: ERROR

+
Message: An error occurred during conflict resolution synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_MODDN_SYNCH_CONFLICT_RESOLUTION_FAILED_412]
ID: 412::
Severity: ERROR

+
Message: An error occurred during conflict resolution synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

[#log-ref-log-ref-ERR_ADD_SERVER_READONLY_413]
ID: 413::
Severity: ERROR

+
Message: Unable to add entry %s because the Directory Server is configured in read-only mode.

[#log-ref-log-ref-ERR_ADD_BACKEND_READONLY_414]
ID: 414::
Severity: ERROR

+
Message: Unable to add entry %s because the backend that should hold that entry is configured in read-only mode.

[#log-ref-log-ref-ERR_DELETE_SERVER_READONLY_415]
ID: 415::
Severity: ERROR

+
Message: Unable to delete entry %s because the Directory Server is configured in read-only mode.

[#log-ref-log-ref-ERR_DELETE_BACKEND_READONLY_416]
ID: 416::
Severity: ERROR

+
Message: Unable to delete entry %s because the backend that holds that entry is configured in read-only mode.

[#log-ref-log-ref-ERR_MODIFY_SERVER_READONLY_417]
ID: 417::
Severity: ERROR

+
Message: Unable to modify entry %s because the Directory Server is configured in read-only mode.

[#log-ref-log-ref-ERR_MODIFY_BACKEND_READONLY_418]
ID: 418::
Severity: ERROR

+
Message: Unable to modify entry %s because the backend that holds that entry is configured in read-only mode.

[#log-ref-log-ref-ERR_MODDN_SERVER_READONLY_419]
ID: 419::
Severity: ERROR

+
Message: Unable to rename entry %s because the Directory Server is configured in read-only mode.

[#log-ref-log-ref-ERR_MODDN_BACKEND_READONLY_420]
ID: 420::
Severity: ERROR

+
Message: Unable to rename entry %s because the backend that holds that entry is configured in read-only mode.

[#log-ref-log-ref-ERR_BIND_DN_BUT_NO_PASSWORD_421]
ID: 421::
Severity: ERROR

+
Message: Unable to process the simple bind request because it contained a bind DN but no password, which is forbidden by the server configuration.

[#log-ref-log-ref-ERR_PWPOLICY_UNDEFINED_PASSWORD_ATTRIBUTE_425]
ID: 425::
Severity: ERROR

+
Message: The password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" is not defined in the server schema.

[#log-ref-log-ref-ERR_PWPOLICY_INVALID_PASSWORD_ATTRIBUTE_SYNTAX_426]
ID: 426::
Severity: ERROR

+
Message: 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).

[#log-ref-log-ref-ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CHANGE_BY_TIME_477]
ID: 477::
Severity: ERROR

+
Message: An error occurred while attempting to determine the value for attribute ds-cfg-require-change-by-time in configuration entry %s: %s.

[#log-ref-log-ref-ERR_PWPOLICY_INVALID_LAST_LOGIN_TIME_FORMAT_482]
ID: 482::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_PWPOLICY_INVALID_PREVIOUS_LAST_LOGIN_TIME_FORMAT_485]
ID: 485::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_PWPOLICY_ATTRIBUTE_OPTIONS_NOT_ALLOWED_496]
ID: 496::
Severity: ERROR

+
Message: Attribute options are not allowed for the password attribute %s.

[#log-ref-log-ref-ERR_PWPOLICY_MULTIPLE_PW_VALUES_NOT_ALLOWED_497]
ID: 497::
Severity: ERROR

+
Message: Only a single value may be provided for the password attribute %s.

[#log-ref-log-ref-ERR_PWPOLICY_PREENCODED_NOT_ALLOWED_498]
ID: 498::
Severity: ERROR

+
Message: Pre-encoded passwords are not allowed for the password attribute %s.

[#log-ref-log-ref-ERR_PWPOLICY_VALIDATION_FAILED_499]
ID: 499::
Severity: ERROR

+
Message: The password value for attribute %s was found to be unacceptable: %s.

[#log-ref-log-ref-ERR_PWPOLICY_MUST_HAVE_WARNING_IF_NOT_EXPIRE_WITHOUT_WARNING_500]
ID: 500::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENQUEUE_BIND_IN_PROGRESS_501]
ID: 501::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENQUEUE_MUST_CHANGE_PASSWORD_502]
ID: 502::
Severity: ERROR

+
Message: %s must change their password before it will be allowed to request any other operations.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_DECODE_SUBENTRY_VALUE_AS_DN_504]
ID: 504::
Severity: ERROR

+
Message: An error occurred while attempting to decode the ds-pwp-password-policy-dn value "%s" in user entry "%s" as a DN: %s.

[#log-ref-log-ref-ERR_PWPSTATE_NO_SUCH_POLICY_505]
ID: 505::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_DECODE_GENERALIZED_TIME_506]
ID: 506::
Severity: ERROR

+
Message: An error occurred while attempting to decode value "%s" for attribute %s in user entry %s in accordance with the generalized time format: %s.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_DECODE_BOOLEAN_507]
ID: 507::
Severity: ERROR

+
Message: Unable to decode value "%s" for attribute %s in user entry %s as a Boolean value.

[#log-ref-log-ref-ERR_ADD_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_508]
ID: 508::
Severity: ERROR

+
Message: The entry %s cannot be added due to insufficient access rights.

[#log-ref-log-ref-ERR_BIND_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_509]
ID: 509::
Severity: ERROR

+
Message: The user cannot bind due to insufficient access rights.

[#log-ref-log-ref-ERR_COMPARE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_510]
ID: 510::
Severity: ERROR

+
Message: The entry %s cannot be compared due to insufficient access rights.

[#log-ref-log-ref-ERR_DELETE_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_511]
ID: 511::
Severity: ERROR

+
Message: The entry %s cannot be deleted due to insufficient access rights.

[#log-ref-log-ref-ERR_EXTENDED_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_512]
ID: 512::
Severity: ERROR

+
Message: The extended operation %s cannot be performed due to insufficient access rights.

[#log-ref-log-ref-ERR_MODDN_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_513]
ID: 513::
Severity: ERROR

+
Message: The entry %s cannot be renamed due to insufficient access rights.

[#log-ref-log-ref-ERR_MODIFY_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_514]
ID: 514::
Severity: ERROR

+
Message: The entry %s cannot be modified due to insufficient access rights.

[#log-ref-log-ref-ERR_SEARCH_AUTHZ_INSUFFICIENT_ACCESS_RIGHTS_515]
ID: 515::
Severity: ERROR

+
Message: The entry %s cannot be searched due to insufficient access rights.

[#log-ref-log-ref-ERR_BIND_OPERATION_INSECURE_SIMPLE_BIND_516]
ID: 516::
Severity: ERROR

+
Message: Rejecting a simple bind request because the password policy requires secure authentication.

[#log-ref-log-ref-ERR_BIND_OPERATION_ACCOUNT_DISABLED_517]
ID: 517::
Severity: ERROR

+
Message: Rejecting a bind request because the account has been administratively disabled.

[#log-ref-log-ref-ERR_BIND_OPERATION_ACCOUNT_FAILURE_LOCKED_518]
ID: 518::
Severity: ERROR

+
Message: Rejecting a bind request because the account has been locked due to too many failed authentication attempts.

[#log-ref-log-ref-ERR_BIND_OPERATION_ACCOUNT_RESET_LOCKED_519]
ID: 519::
Severity: ERROR

+
Message: Rejecting a bind request because the account has been locked after the user's password was not changed in a timely manner after an administrative reset.

[#log-ref-log-ref-ERR_BIND_OPERATION_ACCOUNT_IDLE_LOCKED_520]
ID: 520::
Severity: ERROR

+
Message: Rejecting a bind request because the account has been locked after remaining idle for too long.

[#log-ref-log-ref-ERR_BIND_OPERATION_PASSWORD_EXPIRED_521]
ID: 521::
Severity: ERROR

+
Message: Rejecting a bind request because that user's password is expired.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_UPDATE_USER_ENTRY_522]
ID: 522::
Severity: ERROR

+
Message: An error occurred while attempting to update password policy state information for user %s: %s.

[#log-ref-log-ref-ERR_BIND_OPERATION_INSECURE_SASL_BIND_523]
ID: 523::
Severity: ERROR

+
Message: Rejecting a SASL %s bind request for user %s because the password policy requires secure authentication.

[#log-ref-log-ref-ERR_CANNOT_REGISTER_DUPLICATE_ALTERNATE_ROOT_BIND_DN_530]
ID: 530::
Severity: ERROR

+
Message: The alternate root bind DN "%s" is already registered with the Directory Server for actual root entry DN "%s".

[#log-ref-log-ref-ERR_BIND_OPERATION_ACCOUNT_EXPIRED_531]
ID: 531::
Severity: ERROR

+
Message: Rejecting a bind request because the account has expired.

[#log-ref-log-ref-ERR_MODIFY_PASSWORDS_CANNOT_HAVE_OPTIONS_532]
ID: 532::
Severity: ERROR

+
Message: Attributes used to hold user passwords are not allowed to have any attribute options.

[#log-ref-log-ref-ERR_MODIFY_NO_USER_PW_CHANGES_533]
ID: 533::
Severity: ERROR

+
Message: Users are not allowed to change their own passwords.

[#log-ref-log-ref-ERR_MODIFY_REQUIRE_SECURE_CHANGES_534]
ID: 534::
Severity: ERROR

+
Message: Password changes must be performed over a secure authentication channel.

[#log-ref-log-ref-ERR_MODIFY_WITHIN_MINIMUM_AGE_535]
ID: 535::
Severity: ERROR

+
Message: The password cannot be changed because it has not been long enough since the last password change.

[#log-ref-log-ref-ERR_MODIFY_MULTIPLE_VALUES_NOT_ALLOWED_536]
ID: 536::
Severity: ERROR

+
Message: Multiple password values are not allowed in user entries.

[#log-ref-log-ref-ERR_MODIFY_NO_PREENCODED_PASSWORDS_537]
ID: 537::
Severity: ERROR

+
Message: User passwords may not be provided in pre-encoded form.

[#log-ref-log-ref-ERR_MODIFY_INVALID_MOD_TYPE_FOR_PASSWORD_538]
ID: 538::
Severity: ERROR

+
Message: Invalid modification type %s attempted on password attribute %s.

[#log-ref-log-ref-ERR_MODIFY_NO_EXISTING_VALUES_539]
ID: 539::
Severity: ERROR

+
Message: The user entry does not have any existing passwords to remove.

[#log-ref-log-ref-ERR_MODIFY_INVALID_PASSWORD_541]
ID: 541::
Severity: ERROR

+
Message: The provided user password does not match any password in the user's entry.

[#log-ref-log-ref-ERR_MODIFY_PW_CHANGE_REQUIRES_CURRENT_PW_542]
ID: 542::
Severity: ERROR

+
Message: The password policy requires that user password changes include the current password in the request.

[#log-ref-log-ref-ERR_MODIFY_MULTIPLE_PASSWORDS_NOT_ALLOWED_543]
ID: 543::
Severity: ERROR

+
Message: The password change would result in multiple password values in the user entry, which is not allowed.

[#log-ref-log-ref-ERR_MODIFY_PW_VALIDATION_FAILED_544]
ID: 544::
Severity: ERROR

+
Message: The provided password value was rejected by a password validator: %s.

[#log-ref-log-ref-ERR_MODIFY_MUST_CHANGE_PASSWORD_545]
ID: 545::
Severity: ERROR

+
Message: %s must change their password before it will be allowed to perform any other operations.

[#log-ref-log-ref-ERR_BIND_ACCOUNT_TEMPORARILY_LOCKED_548]
ID: 548::
Severity: ERROR

+
Message: The account has been locked as a result of too many failed authentication attempts (time to unlock: %s).

[#log-ref-log-ref-ERR_BIND_ACCOUNT_PERMANENTLY_LOCKED_549]
ID: 549::
Severity: ERROR

+
Message: The account has been locked as a result of too many failed authentication attempts. It may only be unlocked by an administrator.

[#log-ref-log-ref-ERR_MODIFY_PASSWORD_EXISTS_556]
ID: 556::
Severity: ERROR

+
Message: The specified password value already exists in the user entry.

[#log-ref-log-ref-ERR_ENTRY_DUPLICATE_VALUES_559]
ID: 559::
Severity: ERROR

+
Message: Unable to add one or more values to attribute %s because at least one of the values already exists.

[#log-ref-log-ref-ERR_ENTRY_NO_SUCH_VALUE_560]
ID: 560::
Severity: ERROR

+
Message: Unable to remove one or more values from attribute %s because at least one of the attributes does not exist in the entry.

[#log-ref-log-ref-ERR_ENTRY_OC_INCREMENT_NOT_SUPPORTED_561]
ID: 561::
Severity: ERROR

+
Message: The increment operation is not supported for the objectClass attribute.

[#log-ref-log-ref-ERR_ENTRY_UNKNOWN_MODIFICATION_TYPE_562]
ID: 562::
Severity: ERROR

+
Message: Unknown modification type %s requested.

[#log-ref-log-ref-ERR_ENTRY_INCREMENT_INVALID_VALUE_COUNT_564]
ID: 564::
Severity: ERROR

+
Message: Unable to increment the value of attribute %s because the provided modification did not have exactly one value to use as the increment.

[#log-ref-log-ref-ERR_ENTRY_INCREMENT_CANNOT_PARSE_AS_INT_565]
ID: 565::
Severity: ERROR

+
Message: Unable to increment the value of attribute %s because either the current value or the increment could not be parsed as an integer.

[#log-ref-log-ref-ERR_MODIFY_NO_MODIFICATIONS_566]
ID: 566::
Severity: ERROR

+
Message: Entry %s cannot be updated because the request did not contain any modifications.

[#log-ref-log-ref-ERR_ENTRY_INCREMENT_NO_SUCH_ATTRIBUTE_568]
ID: 568::
Severity: ERROR

+
Message: Unable to increment the value of attribute %s because that attribute does not exist in the entry.

[#log-ref-log-ref-ERR_EXTENDED_UNSUPPORTED_CRITICAL_CONTROL_570]
ID: 570::
Severity: ERROR

+
Message: Unable to process the request for extended operation %s because it contained an unsupported critical control with OID %s.

[#log-ref-log-ref-ERR_REGISTER_BACKEND_ALREADY_EXISTS_571]
ID: 571::
Severity: ERROR

+
Message: Unable to register backend %s with the Directory Server because another backend with the same backend ID is already registered.

[#log-ref-log-ref-ERR_REGISTER_BASEDN_ALREADY_EXISTS_572]
ID: 572::
Severity: ERROR

+
Message: Unable to register base DN %s with the Directory Server for backend %s because that base DN is already registered for backend %s.

[#log-ref-log-ref-ERR_REGISTER_BASEDN_HIERARCHY_CONFLICT_573]
ID: 573::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_REGISTER_BASEDN_DIFFERENT_PARENT_BASES_574]
ID: 574::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_REGISTER_BASEDN_NEW_BASE_NOT_SUBORDINATE_575]
ID: 575::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_DEREGISTER_BASEDN_NOT_REGISTERED_577]
ID: 577::
Severity: ERROR

+
Message: Unable to de-register base DN %s with the Directory Server because that base DN is not registered for any active backend.

[#log-ref-log-ref-ERR_SCHEMA_CIRCULAR_DEPENDENCY_REFERENCE_579]
ID: 579::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_REJECT_UNAUTHENTICATED_OPERATION_580]
ID: 580::
Severity: ERROR

+
Message: Rejecting the requested operation because the connection has not been authenticated.

[#log-ref-log-ref-ERR_MODIFY_ATTR_IS_OBSOLETE_583]
ID: 583::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENTRY_ADD_OBSOLETE_OC_584]
ID: 584::
Severity: ERROR

+
Message: Object class %s added to entry %s is marked OBSOLETE in the server schema.

[#log-ref-log-ref-ERR_MODDN_NEWRDN_ATTR_IS_OBSOLETE_585]
ID: 585::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_VIOLATES_PARENT_DSR_586]
ID: 586::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_COULD_NOT_CHECK_PARENT_DSR_587]
ID: 587::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to perform DIT structure rule processing for the parent of entry %s: %s.

[#log-ref-log-ref-ERR_MODIFY_PWRESET_INSUFFICIENT_PRIVILEGES_589]
ID: 589::
Severity: ERROR

+
Message: You do not have sufficient privileges to reset user passwords.

[#log-ref-log-ref-ERR_COMPARE_CONFIG_INSUFFICIENT_PRIVILEGES_590]
ID: 590::
Severity: ERROR

+
Message: You do not have sufficient privileges to access the server configuration.

[#log-ref-log-ref-ERR_ADD_CHANGE_PRIVILEGE_INSUFFICIENT_PRIVILEGES_591]
ID: 591::
Severity: ERROR

+
Message: You do not have sufficient privileges to add entries that include privileges.

[#log-ref-log-ref-ERR_MODIFY_CHANGE_PRIVILEGE_INSUFFICIENT_PRIVILEGES_592]
ID: 592::
Severity: ERROR

+
Message: You do not have sufficient privileges to modify the set of privileges contained in an entry.

[#log-ref-log-ref-ERR_PROXYAUTH_INSUFFICIENT_PRIVILEGES_595]
ID: 595::
Severity: ERROR

+
Message: You do not have sufficient privileges to use the proxied authorization control.

[#log-ref-log-ref-ERR_ENTRY_SCHEMA_ATTR_NO_VALUES_597]
ID: 597::
Severity: ERROR

+
Message: Entry %s violates the Directory Server schema configuration because it includes attribute %s without any values.

[#log-ref-log-ref-ERR_DSCORE_ERROR_NODETACH_AND_WINDOW_SERVICE_598]
ID: 598::
Severity: ERROR

+
Message: OpenDJ is configured to run as a Windows service and it cannot run in no-detach mode.

[#log-ref-log-ref-ERR_ENTRY_DECODE_UNRECOGNIZED_VERSION_600]
ID: 600::
Severity: ERROR

+
Message: Unable to decode an entry because it had an unsupported entry version byte value of %s.

[#log-ref-log-ref-ERR_ENTRY_DECODE_EXCEPTION_601]
ID: 601::
Severity: ERROR

+
Message: Unable to decode an entry because an unexpected exception was caught during processing: %s.

[#log-ref-log-ref-ERR_SEARCH_FILTER_NOT_EXACTLY_ONE_602]
ID: 602::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_CONTROL_INSUFFICIENT_ACCESS_RIGHTS_611]
ID: 611::
Severity: ERROR

+
Message: The request control with Object Identifier (OID) "%s" cannot be used due to insufficient access rights.

[#log-ref-log-ref-ERR_HOST_PORT_ALREADY_SPECIFIED_612]
ID: 612::
Severity: ERROR

+
Message: The connection handler %s is trying to use the listener %s which is already in use by another connection handler.

[#log-ref-log-ref-ERR_NOT_AVAILABLE_CONNECTION_HANDLERS_614]
ID: 614::
Severity: ERROR

+
Message: No enabled connection handler available.

[#log-ref-log-ref-ERR_ERROR_STARTING_CONNECTION_HANDLERS_615]
ID: 615::
Severity: ERROR

+
Message: Could not start connection handlers.

[#log-ref-log-ref-ERR_BIND_REJECTED_LOCKDOWN_MODE_616]
ID: 616::
Severity: ERROR

+
Message: Unable to process the non-root bind because the server is in lockdown mode.

[#log-ref-log-ref-ERR_COMPRESSEDSCHEMA_UNRECOGNIZED_AD_TOKEN_620]
ID: 620::
Severity: ERROR

+
Message: Unable to decode the provided attribute because it used an undefined attribute description token %s.

[#log-ref-log-ref-ERR_COMPRESSEDSCHEMA_UNKNOWN_OC_TOKEN_621]
ID: 621::
Severity: ERROR

+
Message: Unable to decode the provided object class set because it used an undefined token %s.

[#log-ref-log-ref-ERR_COMPRESSEDSCHEMA_CANNOT_WRITE_UPDATED_DATA_622]
ID: 622::
Severity: ERROR

+
Message: Unable to write the updated compressed schema token data: %s.

[#log-ref-log-ref-ERR_ENTRYENCODECFG_INVALID_LENGTH_623]
ID: 623::
Severity: ERROR

+
Message: Unable to decode the provided entry encode configuration element because it has an invalid length.

[#log-ref-log-ref-ERR_SEARCH_FILTER_CREATE_EXTENSIBLE_MATCH_NO_AT_OR_MR_625]
ID: 625::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_AD_OR_MR_626]
ID: 626::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_SEARCH_FILTER_EXTENSIBLE_MATCH_NO_SUCH_MR_627]
ID: 627::
Severity: ERROR

+
Message: The provided search filter "%s" could not be decoded because the extensible match component starting at position %d referenced an unknown matching rule %s.

[#log-ref-log-ref-ERR_BIND_OPERATION_WRITABILITY_DISABLED_628]
ID: 628::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_MODIFY_PW_IN_HISTORY_629]
ID: 629::
Severity: ERROR

+
Message: The provided new password was found in the password history for the user.

[#log-ref-log-ref-ERR_PWPOLICY_WARNING_INTERVAL_LARGER_THAN_MAX_AGE_633]
ID: 633::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_PWPOLICY_MIN_AGE_PLUS_WARNING_GREATER_THAN_MAX_AGE_634]
ID: 634::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_IDLETIME_DISCONNECT_ERROR_638]
ID: 638::
Severity: ERROR

+
Message: An error occurred while attempting to disconnect client connection %d: %s.

[#log-ref-log-ref-ERR_IDLETIME_UNEXPECTED_ERROR_639]
ID: 639::
Severity: ERROR

+
Message: An unexpected error occurred in the idle time limit thread: %s.

[#log-ref-log-ref-ERR_DIRCFG_SERVER_ALREADY_RUNNING_640]
ID: 640::
Severity: ERROR

+
Message: The Directory Server is currently running. Environment configuration changes are not allowed with the server running.

[#log-ref-log-ref-ERR_DIRCFG_INVALID_SERVER_ROOT_641]
ID: 641::
Severity: ERROR

+
Message: The specified server root directory '%s' is invalid. The specified path must exist and must be a directory.

[#log-ref-log-ref-ERR_DIRCFG_INVALID_CONFIG_FILE_642]
ID: 642::
Severity: ERROR

+
Message: The specified config file path '%s' is invalid. The specified path must exist and must be a file.

[#log-ref-log-ref-ERR_DIRCFG_INVALID_CONFIG_CLASS_643]
ID: 643::
Severity: ERROR

+
Message: The specified config handler class '%s' is invalid. The specified class must be a subclass of the org.opends.server.api.ConfigHandler superclass.

[#log-ref-log-ref-ERR_DIRCFG_INVALID_SCHEMA_DIRECTORY_644]
ID: 644::
Severity: ERROR

+
Message: The specified schema configuration directory '%s' is invalid. The specified path must exist and must be a directory.

[#log-ref-log-ref-ERR_DIRCFG_INVALID_LOCK_DIRECTORY_645]
ID: 645::
Severity: ERROR

+
Message: The specified lock directory '%s' is invalid. The specified path must exist and must be a directory.

[#log-ref-log-ref-ERR_CANNOT_SET_ENVIRONMENT_CONFIG_WHILE_RUNNING_648]
ID: 648::
Severity: ERROR

+
Message: The Directory Server is currently running. The environment configuration can not be altered while the server is online.

[#log-ref-log-ref-ERR_CRYPTOMGR_SSL_CONTEXT_CANNOT_INITIALIZE_649]
ID: 649::
Severity: ERROR

+
Message: An error occurred while attempting to initialize a SSL context for server to server communication: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_ADS_TRUST_STORE_BACKEND_NOT_ENABLED_650]
ID: 650::
Severity: ERROR

+
Message: The ADS trust store backend %s is not enabled.

[#log-ref-log-ref-ERR_CRYPTOMGR_ADS_TRUST_STORE_BACKEND_WRONG_CLASS_651]
ID: 651::
Severity: ERROR

+
Message: The backend %s is not a trust store backend.

[#log-ref-log-ref-ERR_TRUSTSTORESYNC_EXCEPTION_654]
ID: 654::
Severity: ERROR

+
Message: An error occurred in the trust store synchronization thread: %s.

[#log-ref-log-ref-ERR_PWPOLICY_SCHEME_DOESNT_SUPPORT_AUTH_657]
ID: 657::
Severity: ERROR

+
Message: The password storage scheme defined in configuration entry %s does not support the auth password syntax, which is used by password attribute %s.

[#log-ref-log-ref-ERR_PWPOLICY_DEPRECATED_SCHEME_NOT_AUTH_659]
ID: 659::
Severity: ERROR

+
Message: Password policy configuration entry %s references deprecated password storage scheme DN %s which does not support the auth password syntax.

[#log-ref-log-ref-ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_DIGEST_661]
ID: 661::
Severity: ERROR

+
Message: CryptoManager cannot get the requested digest %s: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_MAC_ENGINE_662]
ID: 662::
Severity: ERROR

+
Message: CryptoManager cannot get the requested MAC engine %s: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_CANNOT_GET_REQUESTED_ENCRYPTION_CIPHER_663]
ID: 663::
Severity: ERROR

+
Message: CryptoManager cannot get the requested encryption cipher %s: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_CANNOT_GET_PREFERRED_KEY_WRAPPING_CIPHER_664]
ID: 664::
Severity: ERROR

+
Message: CryptoManager cannot get the preferred key wrapping cipher: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_TO_INITIATE_INSTANCE_KEY_GENERATION_665]
ID: 665::
Severity: ERROR

+
Message: CryptoManager failed to add entry "%s" to initiate instance key generation.

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_TO_RETRIEVE_INSTANCE_CERTIFICATE_666]
ID: 666::
Severity: ERROR

+
Message: CryptoManager failed to retrieve entry "%s" (the instance-key-pair public-key-certificate): %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_TO_COMPUTE_INSTANCE_KEY_IDENTIFIER_667]
ID: 667::
Severity: ERROR

+
Message: CryptoManager failed to compute an instance key identifier: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_TO_ADD_INSTANCE_KEY_ENTRY_TO_ADS_668]
ID: 668::
Severity: ERROR

+
Message: Failed to add entry "%s".

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_TO_PUBLISH_INSTANCE_KEY_ENTRY_669]
ID: 669::
Severity: ERROR

+
Message: CryptoManager failed to publish the instance-key-pair public-key-certificate entry in ADS: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_TO_RETRIEVE_ADS_TRUSTSTORE_CERTS_670]
ID: 670::
Severity: ERROR

+
Message: CryptoManager failed to retrieve the collection of instance-key-pair public-key-certificates from ADS container "%s": %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_TO_ENCODE_SYMMETRIC_KEY_ATTRIBUTE_671]
ID: 671::
Severity: ERROR

+
Message: CryptoManager failed to encode symmetric key attribute value: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_FIELD_COUNT_672]
ID: 672::
Severity: ERROR

+
Message: CryptoManager symmetric key attribute value "%s" syntax is invalid: incorrect number of fields.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_SYNTAX_673]
ID: 673::
Severity: ERROR

+
Message: CryptoManager symmetric key attribute value "%s" syntax is invalid. Parsing failed in field "%s" at offset %d.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_NO_PRIVATE_674]
ID: 674::
Severity: ERROR

+
Message: CryptoManager failed to retrieve the instance-key-pair private-key: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_DECIPHER_675]
ID: 675::
Severity: ERROR

+
Message: CryptoManager failed to decipher the wrapped secret-key value: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_REWRAP_SYMMETRIC_KEY_ATTRIBUTE_NO_WRAPPER_676]
ID: 676::
Severity: ERROR

+
Message: CryptoManager cannot find the public-key-certificate (identifier "%s") requested for symmetric key re-encoding.

[#log-ref-log-ref-ERR_CRYPTOMGR_INVALID_KEY_IDENTIFIER_SYNTAX_677]
ID: 677::
Severity: ERROR

+
Message: CryptoManager failed to decode the key entry identifier "%s": %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_GET_MAC_ENGINE_INVALID_MAC_ALGORITHM_678]
ID: 678::
Severity: ERROR

+
Message: CrytpoManager passed invalid MAC algorithm "%s": %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_GET_MAC_ENGINE_CANNOT_INITIALIZE_679]
ID: 679::
Severity: ERROR

+
Message: CryptoManager failed to initialize MAC engine: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_GET_CIPHER_INVALID_CIPHER_TRANSFORMATION_680]
ID: 680::
Severity: ERROR

+
Message: CryptoManager passed invalid Cipher transformation "%s": %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_GET_CIPHER_CANNOT_INITIALIZE_681]
ID: 681::
Severity: ERROR

+
Message: CryptoManager cannot initialize Cipher: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_GET_CIPHER_STREAM_PROLOGUE_WRITE_ERROR_682]
ID: 682::
Severity: ERROR

+
Message: CryptoManager failed to write the stream prologue: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_KEY_IDENTIFIER_683]
ID: 683::
Severity: ERROR

+
Message: CryptoManager failed to decrypt the supplied data because it could not read the symmetric key identifier in the data prologue: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECRYPT_UNKNOWN_KEY_IDENTIFIER_684]
ID: 684::
Severity: ERROR

+
Message: CryptoManager failed to decrypt the supplied data because the symmetric key identifier in the data prologue does not match any known key entries.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_IV_685]
ID: 685::
Severity: ERROR

+
Message: CryptoManager failed to decrypt the supplied data because it could not read the cipher initialization vector in the data prologue.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECRYPT_CIPHER_INPUT_STREAM_ERROR_686]
ID: 686::
Severity: ERROR

+
Message: CryptoManager failed to decrypt the supplied data because there was an error reading from the input stream: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_DECODE_687]
ID: 687::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FIELD_MISMATCH_688]
ID: 688::
Severity: ERROR

+
Message: 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".

[#log-ref-log-ref-ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_OTHER_689]
ID: 689::
Severity: ERROR

+
Message: CryptoManager failed to import the symmetric key entry "%s": %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_IMPORT_KEY_ENTRY_FAILED_TO_ADD_KEY_690]
ID: 690::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_ALGORITHM_691]
ID: 691::
Severity: ERROR

+
Message: CryptoManager failed to instantiate a KeyGenerator for algorithm "%s": %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_SYMMETRIC_KEY_ENTRY_ADD_FAILED_692]
ID: 692::
Severity: ERROR

+
Message: CryptoManager failed to add locally produced symmetric key entry "%s": %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_FULL_CIPHER_TRANSFORMATION_REQUIRED_693]
ID: 693::
Severity: ERROR

+
Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

[#log-ref-log-ref-ERR_CRYPTOMGR_FULL_KEY_WRAPPING_TRANSFORMATION_REQUIRED_694]
ID: 694::
Severity: ERROR

+
Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

[#log-ref-log-ref-ERR_CRYPTOMGR_DECRYPT_FAILED_TO_READ_PROLOGUE_VERSION_695]
ID: 695::
Severity: ERROR

+
Message: CryptoManager failed to decrypt the supplied data because it could not read the version number in the data prologue: %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_DECRYPT_UNKNOWN_PROLOGUE_VERSION_696]
ID: 696::
Severity: ERROR

+
Message: CryptoManager failed to decrypt the supplied data because the version "%d" in the data prologue is unknown.

[#log-ref-log-ref-ERR_ADD_ENTRY_UNKNOWN_SUFFIX_697]
ID: 697::
Severity: ERROR

+
Message: The provided entry %s cannot be added because its suffix is not defined as one of the suffixes within the Directory Server.

[#log-ref-log-ref-ERR_CANNOT_CANCEL_START_TLS_700]
ID: 700::
Severity: ERROR

+
Message: Start TLS extended operations cannot be canceled.

[#log-ref-log-ref-ERR_CANNOT_CANCEL_CANCEL_701]
ID: 701::
Severity: ERROR

+
Message: Cancel extended operations can not be canceled.

[#log-ref-log-ref-ERR_MODDN_NEW_SUPERIOR_IN_SUBTREE_702]
ID: 702::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_REGISTER_WORKFLOW_ELEMENT_ALREADY_EXISTS_703]
ID: 703::
Severity: ERROR

+
Message: Unable to register workflow element %s with the Directory Server because another workflow element with the same ID is already registered.

[#log-ref-log-ref-ERR_ADD_ATTR_IS_INVALID_OPTION_715]
ID: 715::
Severity: ERROR

+
Message: Entry %s can not be added because BER encoding of %s attribute is not supported.

[#log-ref-log-ref-ERR_CRYPTOMGR_FAILED_INSTANCE_CERTIFICATE_NULL_721]
ID: 721::
Severity: ERROR

+
Message: The CryptoManager entry "%s" (the instance-key-pair public-key-certificate) does not contain a public-key certificate.

[#log-ref-log-ref-ERR_DSCORE_ERROR_NODETACH_TIMEOUT_723]
ID: 723::
Severity: ERROR

+
Message: In no-detach mode, the 'timeout' option cannot be used.

[#log-ref-log-ref-ERR_PWPOLICY_NO_PWDPOLICY_OC_726]
ID: 726::
Severity: ERROR

+
Message: The entry %s does not contain the pwdPolicy objectclass, which is required for Directory Server password policy.

[#log-ref-log-ref-ERR_RDN_MISSING_ATTRIBUTE_VALUE_727]
ID: 727::
Severity: ERROR

+
Message: Unable to decode the provided string "%s" as a relative distinguished name because it does not contain a value for attribute type %s.

[#log-ref-log-ref-ERR_CRYPTOMGR_INVALID_SYMMETRIC_KEY_LENGTH_728]
ID: 728::
Severity: ERROR

+
Message: CryptoManager failed to initialize because the specified cipher key length "%d" is beyond the allowed cryptography strength "%d" in jurisdiction policy files.

[#log-ref-log-ref-ERR_DISK_SPACE_MONITOR_UPDATE_FAILED_729]
ID: 729::
Severity: ERROR

+
Message: Failed to update free disk space for directory %s: %s.

[#log-ref-log-ref-ERR_MAX_PSEARCH_LIMIT_EXCEEDED_730]
ID: 730::
Severity: ERROR

+
Message: The directory server is not accepting a new persistent search request because the server has already reached its limit.

[#log-ref-log-ref-ERR_SUBENTRY_WRITE_INSUFFICIENT_PRIVILEGES_739]
ID: 739::
Severity: ERROR

+
Message: This operation involves LDAP subentries which you do not have sufficient privileges to administer.

[#log-ref-log-ref-ERR_MODIFY_ADD_INVALID_SYNTAX_NO_VALUE_743]
ID: 743::
Severity: ERROR

+
Message: When attempting to modify entry %s, one value for attribute %s was found to be invalid according to the associated syntax: %s.

[#log-ref-log-ref-ERR_MODIFY_REPLACE_INVALID_SYNTAX_NO_VALUE_744]
ID: 744::
Severity: ERROR

+
Message: When attempting to modify entry %s to replace the set of values for attribute %s, one value was found to be invalid according to the associated syntax: %s.

[#log-ref-log-ref-ERR_PWPOLICY_UNKNOWN_VALIDATOR_745]
ID: 745::
Severity: ERROR

+
Message: The password policy definition contained in configuration entry "%s" is invalid because the password validator "%s" specified in attribute "%s" cannot be found.

[#log-ref-log-ref-ERR_PWPOLICY_REJECT_DUE_TO_UNKNOWN_VALIDATOR_REASON_746]
ID: 746::
Severity: ERROR

+
Message: The password could not be validated because of misconfiguration. Please contact the administrator.

[#log-ref-log-ref-ERR_PWPOLICY_REJECT_DUE_TO_UNKNOWN_VALIDATOR_LOG_747]
ID: 747::
Severity: ERROR

+
Message: The password for user %s could not be validated because the password policy subentry %s is referring to an unknown password validator (%s). Please make sure the password policy subentry only refers to validators that exist on all replicas.

[#log-ref-log-ref-ERR_DISK_SPACE_GET_MOUNT_POINT_748]
ID: 748::
Severity: ERROR

+
Message: Could not get filesystem for directory %s: %s.

[#log-ref-log-ref-ERR_DISK_SPACE_LOW_THRESHOLD_REACHED_749]
ID: 749::
Severity: ERROR

+
Message: The disk containing directory %s used by %s is low on free space (%d bytes free). Write operations are only permitted by a user with the BYPASS_LOCKDOWN privilege until the free space rises above the threshold. Replication updates are still allowed.

[#log-ref-log-ref-ERR_DISK_SPACE_FULL_THRESHOLD_REACHED_750]
ID: 750::
Severity: ERROR

+
Message: The disk containing directory %s used by %s is full (%d bytes free). Write operations to the backend, replication updates included, will fail until the free space rises above the threshold.

[#log-ref-log-ref-ERR_ENQUEUE_STARTTLS_IN_PROGRESS_752]
ID: 752::
Severity: ERROR

+
Message: A StartTLS operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the StartTLS processing has completed.

[#log-ref-log-ref-ERR_ENQUEUE_SASLBIND_IN_PROGRESS_753]
ID: 753::
Severity: ERROR

+
Message: A SASL bind operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the SASL bind processing has completed.

[#log-ref-log-ref-ERR_CANNOT_HASH_DATA_754]
ID: 754::
Severity: ERROR

+
Message: Cannot properly use SHA-1 using the java provider. Verify java.security is properly configured.

[#log-ref-log-ref-ERR_MISSING_ADMIN_BACKENDS_755]
ID: 755::
Severity: ERROR

+
Message: Cannot complete initialization of server's backends because the root and administrative backends have not been initialized yet.

--


[#EXTENSION]
=== Log Message Category: EXTENSION

--

[#log-ref-log-ref-ERR_PWSCHEME_CANNOT_INITIALIZE_MESSAGE_DIGEST_1]
ID: 1::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the message digest generator for the %s algorithm: %s.

[#log-ref-log-ref-ERR_PWSCHEME_CANNOT_BASE64_DECODE_STORED_PASSWORD_2]
ID: 2::
Severity: ERROR

+
Message: An error occurred while attempting to base64-decode the password value %s: %s.

[#log-ref-log-ref-ERR_PWSCHEME_NOT_REVERSIBLE_3]
ID: 3::
Severity: ERROR

+
Message: The %s password storage scheme is not reversible, so it is impossible to recover the plaintext version of an encoded password.

[#log-ref-log-ref-ERR_JMX_ALERT_HANDLER_CANNOT_REGISTER_4]
ID: 4::
Severity: ERROR

+
Message: An error occurred while trying to register the JMX alert handler with the MBean server: %s.

[#log-ref-log-ref-ERR_PWSCHEME_CANNOT_ENCODE_PASSWORD_5]
ID: 5::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to encode a password using the storage scheme defined in class %s: %s.

[#log-ref-log-ref-ERR_CACHE_INVALID_INCLUDE_FILTER_6]
ID: 6::
Severity: ERROR

+
Message: The ds-cfg-include-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are included in the cache, has an invalid value of "%s": %s.

[#log-ref-log-ref-ERR_CACHE_INVALID_EXCLUDE_FILTER_7]
ID: 7::
Severity: ERROR

+
Message: The ds-cfg-exclude-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are excluded from the cache, has an invalid value of "%s": %s.

[#log-ref-log-ref-ERR_FIFOCACHE_CANNOT_INITIALIZE_8]
ID: 8::
Severity: ERROR

+
Message: A fatal error occurred while trying to initialize fifo entry cache: %s.

[#log-ref-log-ref-ERR_SOFTREFCACHE_CANNOT_INITIALIZE_9]
ID: 9::
Severity: ERROR

+
Message: A fatal error occurred while trying to initialize soft reference entry cache: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_DECODE_REQUEST_33]
ID: 33::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to decode the password modify extended request sequence: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_NO_AUTH_OR_USERID_34]
ID: 34::
Severity: ERROR

+
Message: The password modify extended request cannot be processed because it does not contain an authorization ID and the underlying connection is not authenticated.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_LOCK_USER_ENTRY_35]
ID: 35::
Severity: ERROR

+
Message: The password modify extended request cannot be processed because the server was unable to obtain a write lock on user entry %s after multiple attempts.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_DECODE_AUTHZ_DN_36]
ID: 36::
Severity: ERROR

+
Message: The password modify extended request cannot be processed because the server cannot decode "%s" as a valid DN for use in the authorization ID for the operation.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_INVALID_AUTHZID_STRING_37]
ID: 37::
Severity: ERROR

+
Message: The password modify extended request cannot be processed because it contained an invalid userIdentity field. The provided userIdentity string was "%s".

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_NO_USER_ENTRY_BY_AUTHZID_38]
ID: 38::
Severity: ERROR

+
Message: The password modify extended request cannot be processed because it was not possible to identify the user entry to update based on the authorization DN of "%s".

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_INVALID_OLD_PASSWORD_41]
ID: 41::
Severity: ERROR

+
Message: The password modify extended operation cannot be processed because the current password provided for the user is invalid.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_NO_SUCH_FILE_45]
ID: 45::
Severity: ERROR

+
Message: The keystore file %s specified in attribute ds-cfg-key-store-file of configuration entry %s does not exist.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_CANNOT_DETERMINE_FILE_46]
ID: 46::
Severity: ERROR

+
Message: An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-key-store-file in configuration entry %s: %s.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_PIN_PROPERTY_NOT_SET_50]
ID: 50::
Severity: ERROR

+
Message: Java property %s which is specified in attribute ds-cfg-key-store-pin-property of configuration entry %s should contain the PIN needed to access the file-based key manager, but this property is not set.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_PIN_ENVAR_NOT_SET_53]
ID: 53::
Severity: ERROR

+
Message: Environment variable %s which is specified in attribute ds-cfg-key-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the file-based key manager, but this property is not set.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_PIN_NO_SUCH_FILE_56]
ID: 56::
Severity: ERROR

+
Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based key manager, but this file does not exist.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_PIN_FILE_CANNOT_READ_57]
ID: 57::
Severity: ERROR

+
Message: An error occurred while trying to read the keystore PIN from file %s specified in configuration attribute ds-cfg-key-store-pin-file of configuration entry %s: %s.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_PIN_FILE_EMPTY_58]
ID: 58::
Severity: ERROR

+
Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based key manager, but this file is empty.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_CANNOT_LOAD_62]
ID: 62::
Severity: ERROR

+
Message: An error occurred while trying to load the keystore contents from file %s: %s.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_INVALID_TYPE_63]
ID: 63::
Severity: ERROR

+
Message: The keystore type %s specified in attribute ds-cfg-key-store-type of configuration entry %s is not valid: %s.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_PIN_PROPERTY_NOT_SET_68]
ID: 68::
Severity: ERROR

+
Message: Java property %s which is specified in attribute ds-cfg-key-store-pin-property of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this property is not set.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_PIN_ENVAR_NOT_SET_71]
ID: 71::
Severity: ERROR

+
Message: Environment variable %s which is specified in attribute ds-cfg-key-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this property is not set.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_PIN_NO_SUCH_FILE_74]
ID: 74::
Severity: ERROR

+
Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this file does not exist.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_PIN_FILE_CANNOT_READ_75]
ID: 75::
Severity: ERROR

+
Message: An error occurred while trying to read the keystore PIN from file %s specified in configuration attribute ds-cfg-key-store-pin-file of configuration entry %s: %s.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_PIN_FILE_EMPTY_76]
ID: 76::
Severity: ERROR

+
Message: File %s specified in attribute ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN needed to access the PKCS#11 key manager, but this file is empty.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_CANNOT_DETERMINE_PIN_FROM_ATTR_79]
ID: 79::
Severity: ERROR

+
Message: An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-key-store-pin in configuration entry %s: %s.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_CANNOT_LOAD_81]
ID: 81::
Severity: ERROR

+
Message: An error occurred while trying to access the PKCS#11 key manager: %s.

[#log-ref-log-ref-ERR_FILE_KEYMANAGER_CANNOT_CREATE_FACTORY_83]
ID: 83::
Severity: ERROR

+
Message: An error occurred while trying to create a key manager factory to access the contents of keystore file %s: %s.

[#log-ref-log-ref-ERR_PKCS11_KEYMANAGER_CANNOT_CREATE_FACTORY_84]
ID: 84::
Severity: ERROR

+
Message: An error occurred while trying to create a key manager factory to access the contents of the PKCS#11 keystore: %s.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_NO_SUCH_FILE_87]
ID: 87::
Severity: ERROR

+
Message: The trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not exist.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_FILE_88]
ID: 88::
Severity: ERROR

+
Message: An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-trust-store-file in configuration entry %s: %s.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_PIN_PROPERTY_NOT_SET_92]
ID: 92::
Severity: ERROR

+
Message: Java property %s which is specified in attribute ds-cfg-trust-store-pin-property of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this property is not set.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_PIN_ENVAR_NOT_SET_95]
ID: 95::
Severity: ERROR

+
Message: Environment variable %s which is specified in attribute ds-cfg-trust-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this property is not set.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_PIN_NO_SUCH_FILE_98]
ID: 98::
Severity: ERROR

+
Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this file does not exist.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_PIN_FILE_CANNOT_READ_99]
ID: 99::
Severity: ERROR

+
Message: An error occurred while trying to read the trust store PIN from file %s specified in configuration attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_PIN_FILE_EMPTY_100]
ID: 100::
Severity: ERROR

+
Message: File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this file is empty.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_CANNOT_LOAD_104]
ID: 104::
Severity: ERROR

+
Message: An error occurred while trying to load the trust store contents from file %s: %s.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_CANNOT_CREATE_FACTORY_105]
ID: 105::
Severity: ERROR

+
Message: An error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %s.

[#log-ref-log-ref-ERR_FILE_TRUSTMANAGER_INVALID_TYPE_106]
ID: 106::
Severity: ERROR

+
Message: The trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s.

[#log-ref-log-ref-ERR_SEDCM_NO_PEER_CERTIFICATE_118]
ID: 118::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

[#log-ref-log-ref-ERR_SEDCM_PEER_CERT_NOT_X509_119]
ID: 119::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

[#log-ref-log-ref-ERR_SEDCM_CANNOT_DECODE_SUBJECT_AS_DN_120]
ID: 120::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user because the peer certificate subject "%s" could not be decoded as an LDAP DN: %s.

[#log-ref-log-ref-ERR_SEDCM_CANNOT_GET_ENTRY_121]
ID: 121::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user because an error occurred while attempting to retrieve the user entry with DN "%s": %s.

[#log-ref-log-ref-ERR_SEDCM_NO_USER_FOR_DN_122]
ID: 122::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user because no user entry exists with a DN of %s.

[#log-ref-log-ref-ERR_SASLEXTERNAL_NO_CLIENT_CONNECTION_123]
ID: 123::
Severity: ERROR

+
Message: The SASL EXTERNAL bind request could not be processed because the associated bind request does not have a reference to the client connection.

[#log-ref-log-ref-ERR_SASLEXTERNAL_NOT_LDAP_CLIENT_INSTANCE_124]
ID: 124::
Severity: ERROR

+
Message: The SASL EXTERNAL bind request could not be processed because the associated client connection instance is not an instance of LDAPClientConnection.

[#log-ref-log-ref-ERR_SASLEXTERNAL_NO_CLIENT_CERT_126]
ID: 126::
Severity: ERROR

+
Message: The SASL EXTERNAL bind request could not be processed because the client did not present a certificate chain during SSL/TLS negotiation.

[#log-ref-log-ref-ERR_SASLEXTERNAL_NO_MAPPING_127]
ID: 127::
Severity: ERROR

+
Message: The SASL EXTERNAL bind request failed because the certificate chain presented by the client during SSL/TLS negotiation could not be mapped to a user entry in the Directory Server.

[#log-ref-log-ref-ERR_STARTTLS_NO_CLIENT_CONNECTION_128]
ID: 128::
Severity: ERROR

+
Message: StartTLS cannot be used on this connection because the underlying client connection is not available.

[#log-ref-log-ref-ERR_STARTTLS_NOT_TLS_CAPABLE_129]
ID: 129::
Severity: ERROR

+
Message: StartTLS cannot be used on this client connection because this connection type is not capable of using StartTLS to protect its communication.

[#log-ref-log-ref-ERR_SASLEXTERNAL_NO_CERT_IN_ENTRY_137]
ID: 137::
Severity: ERROR

+
Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s does not have any certificates with which to verify the presented peer certificate.

[#log-ref-log-ref-ERR_SASLEXTERNAL_PEER_CERT_NOT_FOUND_138]
ID: 138::
Severity: ERROR

+
Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s did not contain the peer certificate presented by the client.

[#log-ref-log-ref-ERR_SASLEXTERNAL_CANNOT_VALIDATE_CERT_139]
ID: 139::
Severity: ERROR

+
Message: An error occurred while attempting to validate the peer certificate presented by the client with a certificate from the user's entry %s: %s.

[#log-ref-log-ref-ERR_SASLPLAIN_NO_SASL_CREDENTIALS_147]
ID: 147::
Severity: ERROR

+
Message: SASL PLAIN authentication requires that SASL credentials be provided but none were included in the bind request.

[#log-ref-log-ref-ERR_SASLPLAIN_NO_NULLS_IN_CREDENTIALS_148]
ID: 148::
Severity: ERROR

+
Message: The SASL PLAIN bind request did not include any NULL characters. NULL characters are required as delimiters between the authorization ID and authentication ID, and also between the authentication ID and the password.

[#log-ref-log-ref-ERR_SASLPLAIN_NO_SECOND_NULL_149]
ID: 149::
Severity: ERROR

+
Message: The SASL PLAIN bind request did not include a second NULL character in the credentials, which is required as a delimiter between the authentication ID and the password.

[#log-ref-log-ref-ERR_SASLPLAIN_ZERO_LENGTH_AUTHCID_150]
ID: 150::
Severity: ERROR

+
Message: The authentication ID contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the authentication ID.

[#log-ref-log-ref-ERR_SASLPLAIN_ZERO_LENGTH_PASSWORD_151]
ID: 151::
Severity: ERROR

+
Message: The password contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the password.

[#log-ref-log-ref-ERR_SASLPLAIN_CANNOT_DECODE_AUTHCID_AS_DN_152]
ID: 152::
Severity: ERROR

+
Message: An error occurred while attempting to decode the SASL PLAIN authentication ID "%s" because it appeared to contain a DN but DN decoding failed: %s.

[#log-ref-log-ref-ERR_SASLPLAIN_AUTHCID_IS_NULL_DN_153]
ID: 153::
Severity: ERROR

+
Message: The authentication ID in the SASL PLAIN bind request appears to be an empty DN. This is not allowed.

[#log-ref-log-ref-ERR_SASLPLAIN_CANNOT_GET_ENTRY_BY_DN_154]
ID: 154::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based authentication ID of a SASL PLAIN bind request: %s.

[#log-ref-log-ref-ERR_SASLPLAIN_NO_MATCHING_ENTRIES_157]
ID: 157::
Severity: ERROR

+
Message: The server was not able to find any user entries for the provided authentication ID of %s.

[#log-ref-log-ref-ERR_SASLPLAIN_INVALID_PASSWORD_160]
ID: 160::
Severity: ERROR

+
Message: The provided password is invalid.

[#log-ref-log-ref-ERR_SASLCRAMMD5_CANNOT_GET_MESSAGE_DIGEST_166]
ID: 166::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to obtain an MD5 digest engine for use by the CRAM-MD5 SASL handler: %s.

[#log-ref-log-ref-ERR_SASLCRAMMD5_NO_STORED_CHALLENGE_172]
ID: 172::
Severity: ERROR

+
Message: The SASL CRAM-MD5 bind request contained SASL credentials but there is no stored challenge for this client connection. The first CRAM-MD5 bind request in the two-stage process must not contain client SASL credentials.

[#log-ref-log-ref-ERR_SASLCRAMMD5_INVALID_STORED_CHALLENGE_173]
ID: 173::
Severity: ERROR

+
Message: The SASL CRAM-MD5 bind request contained SASL credentials, but the stored SASL state information for this client connection is not in an appropriate form for the challenge.

[#log-ref-log-ref-ERR_SASLCRAMMD5_NO_SPACE_IN_CREDENTIALS_174]
ID: 174::
Severity: ERROR

+
Message: The SASL CRAM-MD5 bind request from the client included SASL credentials but there was no space to separate the username from the authentication digest.

[#log-ref-log-ref-ERR_SASLCRAMMD5_INVALID_DIGEST_LENGTH_175]
ID: 175::
Severity: ERROR

+
Message: The SASL CRAM-MD5 bind request included SASL credentials, but the decoded digest string had an invalid length of %d bytes rather than the %d bytes expected for a hex representation of an MD5 digest.

[#log-ref-log-ref-ERR_SASLCRAMMD5_INVALID_DIGEST_CONTENT_176]
ID: 176::
Severity: ERROR

+
Message: The SASL CRAM-MD5 bind request included SASL credentials, but the decoded digest was not comprised of only hexadecimal digits: %s.

[#log-ref-log-ref-ERR_SASLCRAMMD5_CANNOT_DECODE_USERNAME_AS_DN_177]
ID: 177::
Severity: ERROR

+
Message: An error occurred while attempting to decode the SASL CRAM-MD5 username "%s" because it appeared to contain a DN but DN decoding failed: %s.

[#log-ref-log-ref-ERR_SASLCRAMMD5_USERNAME_IS_NULL_DN_178]
ID: 178::
Severity: ERROR

+
Message: The username in the SASL CRAM-MD5 bind request appears to be an empty DN. This is not allowed.

[#log-ref-log-ref-ERR_SASLCRAMMD5_CANNOT_GET_ENTRY_BY_DN_180]
ID: 180::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL CRAM-MD5 bind request: %s.

[#log-ref-log-ref-ERR_SASLCRAMMD5_NO_MATCHING_ENTRIES_184]
ID: 184::
Severity: ERROR

+
Message: The server was not able to find any user entries for the provided username of %s.

[#log-ref-log-ref-ERR_SASLCRAMMD5_INVALID_PASSWORD_188]
ID: 188::
Severity: ERROR

+
Message: The provided password is invalid.

[#log-ref-log-ref-ERR_SASLCRAMMD5_NO_REVERSIBLE_PASSWORDS_189]
ID: 189::
Severity: ERROR

+
Message: SASL CRAM-MD5 authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form.

[#log-ref-log-ref-ERR_SASL_NO_CREDENTIALS_193]
ID: 193::
Severity: ERROR

+
Message: The client connection included %s state information, indicating that the client was in the process of performing a %s bind, but the bind request did not include any credentials.

[#log-ref-log-ref-ERR_SASL_CANNOT_GET_SERVER_FQDN_194]
ID: 194::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %s.

[#log-ref-log-ref-ERR_SASL_CONTEXT_CREATE_ERROR_195]
ID: 195::
Severity: ERROR

+
Message: An unexpected error occurred while trying to create an %s context: %s.

[#log-ref-log-ref-ERR_SASL_CANNOT_DECODE_USERNAME_AS_DN_196]
ID: 196::
Severity: ERROR

+
Message: An error occurred while attempting to decode the SASL %s username "%s" because it appeared to contain a DN but DN decoding failed: %s.

[#log-ref-log-ref-ERR_SASL_USERNAME_IS_NULL_DN_197]
ID: 197::
Severity: ERROR

+
Message: The username in the SASL %s bind request appears to be an empty DN. This is not allowed.

[#log-ref-log-ref-ERR_SASL_CANNOT_GET_ENTRY_BY_DN_199]
ID: 199::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL %s bind request: %s.

[#log-ref-log-ref-ERR_SASL_ZERO_LENGTH_USERNAME_200]
ID: 200::
Severity: ERROR

+
Message: The username contained in the SASL %s bind request had a length of zero characters, which is not allowed. %s authentication does not allow an empty string for use as the username.

[#log-ref-log-ref-ERR_SASL_NO_MATCHING_ENTRIES_201]
ID: 201::
Severity: ERROR

+
Message: The server was not able to find any user entries for the provided username of %s.

[#log-ref-log-ref-ERR_SASL_AUTHZID_INVALID_DN_202]
ID: 202::
Severity: ERROR

+
Message: The provided authorization ID %s contained an invalid DN: %s.

[#log-ref-log-ref-ERR_SASL_AUTHZID_NO_SUCH_ENTRY_203]
ID: 203::
Severity: ERROR

+
Message: The entry %s specified as the authorization identity does not exist.

[#log-ref-log-ref-ERR_SASL_AUTHZID_CANNOT_GET_ENTRY_204]
ID: 204::
Severity: ERROR

+
Message: The entry %s specified as the authorization identity could not be retrieved: %s.

[#log-ref-log-ref-ERR_SASL_AUTHZID_NO_MAPPED_ENTRY_205]
ID: 205::
Severity: ERROR

+
Message: The server was unable to find any entry corresponding to authorization ID %s.

[#log-ref-log-ref-ERR_SASL_CANNOT_GET_REVERSIBLE_PASSWORDS_207]
ID: 207::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL %s authentication: %s.

[#log-ref-log-ref-ERR_SASL_NO_REVERSIBLE_PASSWORDS_208]
ID: 208::
Severity: ERROR

+
Message: SASL %s authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form.

[#log-ref-log-ref-ERR_SASL_PROTOCOL_ERROR_209]
ID: 209::
Severity: ERROR

+
Message: SASL %s protocol error: %s.

[#log-ref-log-ref-ERR_SASL_AUTHZID_INSUFFICIENT_PRIVILEGES_210]
ID: 210::
Severity: ERROR

+
Message: The authenticating user %s does not have sufficient privileges to assume a different authorization identity.

[#log-ref-log-ref-ERR_SASL_AUTHZID_INSUFFICIENT_ACCESS_211]
ID: 211::
Severity: ERROR

+
Message: The authenticating user %s does not have sufficient access to assume a different authorization identity.

[#log-ref-log-ref-ERR_SASL_AUTHENTRY_NO_MAPPED_ENTRY_212]
ID: 212::
Severity: ERROR

+
Message: The server was unable to find any entry corresponding to authentication ID %s.

[#log-ref-log-ref-ERR_SASLGSSAPI_KDC_REALM_NOT_DEFINED_213]
ID: 213::
Severity: ERROR

+
Message: The server was unable to because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be defined or neither defined.

[#log-ref-log-ref-ERR_SASL_CANNOT_MAP_AUTHENTRY_214]
ID: 214::
Severity: ERROR

+
Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

[#log-ref-log-ref-ERR_SASLGSSAPI_CANNOT_CREATE_JAAS_CONFIG_215]
ID: 215::
Severity: ERROR

+
Message: An error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %s.

[#log-ref-log-ref-ERR_SASLGSSAPI_CANNOT_CREATE_LOGIN_CONTEXT_216]
ID: 216::
Severity: ERROR

+
Message: An error occurred while attempting to create the JAAS login context for GSSAPI authentication: %s.

[#log-ref-log-ref-ERR_SASLGSSAPI_NO_CLIENT_CONNECTION_217]
ID: 217::
Severity: ERROR

+
Message: No client connection was available for use in processing the GSSAPI bind request.

[#log-ref-log-ref-ERR_EXTOP_WHOAMI_PROXYAUTH_INSUFFICIENT_PRIVILEGES_277]
ID: 277::
Severity: ERROR

+
Message: You do not have sufficient privileges to use the proxied authorization control.

[#log-ref-log-ref-ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_306]
ID: 306::
Severity: ERROR

+
Message: ID string %s mapped to multiple users.

[#log-ref-log-ref-ERR_EXACTMAP_INEFFICIENT_SEARCH_307]
ID: 307::
Severity: ERROR

+
Message: The internal search based on ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

[#log-ref-log-ref-ERR_EXACTMAP_SEARCH_FAILED_308]
ID: 308::
Severity: ERROR

+
Message: An internal failure occurred while attempting to resolve ID string %s to a user entry: %s.

[#log-ref-log-ref-ERR_SASLCRAMMD5_CANNOT_MAP_USERNAME_313]
ID: 313::
Severity: ERROR

+
Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

[#log-ref-log-ref-ERR_SASLDIGESTMD5_CANNOT_MAP_USERNAME_319]
ID: 319::
Severity: ERROR

+
Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

[#log-ref-log-ref-ERR_SASLPLAIN_CANNOT_MAP_USERNAME_325]
ID: 325::
Severity: ERROR

+
Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

[#log-ref-log-ref-ERR_EXTOP_CANCEL_NO_REQUEST_VALUE_327]
ID: 327::
Severity: ERROR

+
Message: Unable to process the cancel request because the extended operation did not include a request value.

[#log-ref-log-ref-ERR_EXTOP_CANCEL_CANNOT_DECODE_REQUEST_VALUE_328]
ID: 328::
Severity: ERROR

+
Message: An error occurred while attempting to decode the value of the cancel extended request: %s.

[#log-ref-log-ref-ERR_PWSCHEME_DOES_NOT_SUPPORT_AUTH_PASSWORD_330]
ID: 330::
Severity: ERROR

+
Message: Password storage scheme %s does not support use with the authentication password attribute syntax.

[#log-ref-log-ref-ERR_PWLENGTHVALIDATOR_MIN_GREATER_THAN_MAX_335]
ID: 335::
Severity: ERROR

+
Message: The configured minimum password length of %d characters is greater than the configured maximum password length of %d.

[#log-ref-log-ref-ERR_PWLENGTHVALIDATOR_TOO_SHORT_336]
ID: 336::
Severity: ERROR

+
Message: The provided password is shorter than the minimum required length of %d characters.

[#log-ref-log-ref-ERR_PWLENGTHVALIDATOR_TOO_LONG_337]
ID: 337::
Severity: ERROR

+
Message: The provided password is longer than the maximum allowed length of %d characters.

[#log-ref-log-ref-ERR_RANDOMPWGEN_NO_CHARSETS_341]
ID: 341::
Severity: ERROR

+
Message: Configuration entry "%s" does not contain attribute ds-cfg-password-character-set which specifies the sets of characters that should be used when generating the password. This is a required attribute.

[#log-ref-log-ref-ERR_RANDOMPWGEN_CHARSET_NAME_CONFLICT_342]
ID: 342::
Severity: ERROR

+
Message: Configuration entry "%s" contains multiple definitions for the %s character set.

[#log-ref-log-ref-ERR_RANDOMPWGEN_CANNOT_DETERMINE_CHARSETS_343]
ID: 343::
Severity: ERROR

+
Message: An error occurred while attempting to decode the value(s) of the configuration attribute ds-cfg-password-character-set, which is used to hold the character set(s) for use in generating the password: %s.

[#log-ref-log-ref-ERR_RANDOMPWGEN_UNKNOWN_CHARSET_346]
ID: 346::
Severity: ERROR

+
Message: The password format string "%s" references an undefined character set "%s".

[#log-ref-log-ref-ERR_RANDOMPWGEN_INVALID_PWFORMAT_347]
ID: 347::
Severity: ERROR

+
Message: The password format string "%s" contains an invalid syntax. This value should be a comma-delimited sequence of elements, where each element is the name of a character set followed by a colon and the number of characters to choose at random from that character set.

[#log-ref-log-ref-ERR_RANDOMPWGEN_CANNOT_DETERMINE_PWFORMAT_348]
ID: 348::
Severity: ERROR

+
Message: An error occurred while attempting to decode the value for configuration attribute ds-cfg-password-format, which is used to specify the format for the generated passwords: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_GET_PW_POLICY_354]
ID: 354::
Severity: ERROR

+
Message: An error occurred while attempting to get the password policy for user %s: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_REQUIRE_CURRENT_PW_355]
ID: 355::
Severity: ERROR

+
Message: The current password must be provided for self password changes.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_SECURE_AUTH_REQUIRED_356]
ID: 356::
Severity: ERROR

+
Message: Password modify operations that supply the user's current password must be performed over a secure communication channel.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_USER_PW_CHANGES_NOT_ALLOWED_357]
ID: 357::
Severity: ERROR

+
Message: End users are not allowed to change their passwords.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_SECURE_CHANGES_REQUIRED_358]
ID: 358::
Severity: ERROR

+
Message: Password changes must be performed over a secure communication channel.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_IN_MIN_AGE_359]
ID: 359::
Severity: ERROR

+
Message: The password cannot be changed because the previous password change was too recent.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_PASSWORD_IS_EXPIRED_360]
ID: 360::
Severity: ERROR

+
Message: The password cannot be changed because it is expired.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_NO_PW_GENERATOR_361]
ID: 361::
Severity: ERROR

+
Message: No new password was provided, and no password generator has been defined that may be used to automatically create a new password.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_GENERATE_PW_362]
ID: 362::
Severity: ERROR

+
Message: An error occurred while attempting to create a new password using the password generator: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_PRE_ENCODED_NOT_ALLOWED_363]
ID: 363::
Severity: ERROR

+
Message: The password policy does not allow users to supply pre-encoded passwords.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_UNACCEPTABLE_PW_364]
ID: 364::
Severity: ERROR

+
Message: The provided new password failed the validation checks defined in the server: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_ENCODE_PASSWORD_365]
ID: 365::
Severity: ERROR

+
Message: Unable to encode the provided password using the default scheme(s): %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_NO_SUCH_ID_MAPPER_368]
ID: 368::
Severity: ERROR

+
Message: The identity mapper with configuration entry DN %s as specified for use with the password modify extended operation defined in entry %s either does not exist or is not enabled. The identity mapper is a required component, and the password modify extended operation will not be enabled.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_DETERMINE_ID_MAPPER_369]
ID: 369::
Severity: ERROR

+
Message: An error occurred while attempting to determine the identity mapper to use in conjunction with the password modify extended operation defined in configuration entry %s: %s. The password modify extended operation will not be enabled for use in the server.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_CANNOT_MAP_USER_370]
ID: 370::
Severity: ERROR

+
Message: The provided authorization ID string "%s" could not be mapped to any user in the directory.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_ERROR_MAPPING_USER_371]
ID: 371::
Severity: ERROR

+
Message: An error occurred while attempting to map authorization ID string "%s" to a user entry: %s.

[#log-ref-log-ref-ERR_SASLCRAMMD5_CANNOT_GET_REVERSIBLE_PASSWORDS_377]
ID: 377::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL CRAM-MD5 authentication: %s.

[#log-ref-log-ref-ERR_SASLPLAIN_CANNOT_CHECK_PASSWORD_VALIDITY_378]
ID: 378::
Severity: ERROR

+
Message: An error occurred while attempting to verify the password for user %s during SASL PLAIN authentication: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_ACCOUNT_DISABLED_381]
ID: 381::
Severity: ERROR

+
Message: The user account has been administratively disabled.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_ACCOUNT_LOCKED_382]
ID: 382::
Severity: ERROR

+
Message: The user account is locked.

[#log-ref-log-ref-ERR_STATICMEMBERS_NO_SUCH_ENTRY_383]
ID: 383::
Severity: ERROR

+
Message: Unable to examine entry %s as a potential member of static group %s because that entry does not exist in the Directory Server.

[#log-ref-log-ref-ERR_STATICMEMBERS_CANNOT_GET_ENTRY_384]
ID: 384::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve entry %s as a potential member of static group %s: %s.

[#log-ref-log-ref-ERR_STATICGROUP_INVALID_OC_COMBINATION_385]
ID: 385::
Severity: ERROR

+
Message: Entry %s cannot be parsed as a valid static group because static groups are not allowed to have both the %s and %s object classes.

[#log-ref-log-ref-ERR_STATICGROUP_NO_VALID_OC_386]
ID: 386::
Severity: ERROR

+
Message: Entry %s cannot be parsed as a valid static group because it does not contain exactly one of the %s or the %s object classes.

[#log-ref-log-ref-ERR_STATICGROUP_CANNOT_DECODE_MEMBER_VALUE_AS_DN_387]
ID: 387::
Severity: ERROR

+
Message: Value %s for attribute %s in entry %s cannot be parsed as a valid DN: %s. It will be excluded from the set of group members.

[#log-ref-log-ref-ERR_STATICGROUP_ADD_MEMBER_ALREADY_EXISTS_388]
ID: 388::
Severity: ERROR

+
Message: Cannot add user %s as a new member of static group %s because that user is already in the member list for the group.

[#log-ref-log-ref-ERR_STATICGROUP_REMOVE_MEMBER_NO_SUCH_MEMBER_389]
ID: 389::
Severity: ERROR

+
Message: Cannot remove user %s as a member of static group %s because that user is not included in the member list for the group.

[#log-ref-log-ref-ERR_STATICGROUP_ADD_MEMBER_UPDATE_FAILED_390]
ID: 390::
Severity: ERROR

+
Message: Cannot add user %s as a new member of static group %s because an error occurred while attempting to perform an internal modification to update the group: %s.

[#log-ref-log-ref-ERR_STATICGROUP_REMOVE_MEMBER_UPDATE_FAILED_391]
ID: 391::
Severity: ERROR

+
Message: Cannot remove user %s as a member of static group %s because an error occurred while attempting to perform an internal modification to update the group: %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_INSUFFICIENT_PRIVILEGES_392]
ID: 392::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform password reset operations.

[#log-ref-log-ref-ERR_SASLDIGESTMD5_EMPTY_AUTHZID_393]
ID: 393::
Severity: ERROR

+
Message: The provided authorization ID was empty, which is not allowed for DIGEST-MD5 authentication.

[#log-ref-log-ref-ERR_SASLPLAIN_AUTHZID_INVALID_DN_400]
ID: 400::
Severity: ERROR

+
Message: The provided authorization ID %s contained an invalid DN: %s.

[#log-ref-log-ref-ERR_SASLPLAIN_AUTHZID_INSUFFICIENT_PRIVILEGES_401]
ID: 401::
Severity: ERROR

+
Message: The authenticating user %s does not have sufficient privileges to specify an alternate authorization ID.

[#log-ref-log-ref-ERR_SASLPLAIN_AUTHZID_NO_SUCH_ENTRY_402]
ID: 402::
Severity: ERROR

+
Message: The entry corresponding to authorization DN %s does not exist in the Directory Server.

[#log-ref-log-ref-ERR_SASLPLAIN_AUTHZID_CANNOT_GET_ENTRY_403]
ID: 403::
Severity: ERROR

+
Message: An error occurred while attempting to retrieve entry %s specified as the authorization ID: %s.

[#log-ref-log-ref-ERR_SASLPLAIN_AUTHZID_NO_MAPPED_ENTRY_404]
ID: 404::
Severity: ERROR

+
Message: No entry corresponding to authorization ID %s was found in the server.

[#log-ref-log-ref-ERR_SASLPLAIN_AUTHZID_CANNOT_MAP_AUTHZID_405]
ID: 405::
Severity: ERROR

+
Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

[#log-ref-log-ref-ERR_SDTUACM_NO_PEER_CERTIFICATE_417]
ID: 417::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

[#log-ref-log-ref-ERR_SDTUACM_PEER_CERT_NOT_X509_418]
ID: 418::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

[#log-ref-log-ref-ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_419]
ID: 419::
Severity: ERROR

+
Message: The certificate with subject %s could not be mapped to exactly one user. It maps to both %s and %s.

[#log-ref-log-ref-ERR_SATUACM_INVALID_MAP_FORMAT_422]
ID: 422::
Severity: ERROR

+
Message: Configuration entry %s has value '%s' which violates the format required for attribute mappings. The expected format is 'certattr:userattr'.

[#log-ref-log-ref-ERR_SATUACM_DUPLICATE_CERT_ATTR_423]
ID: 423::
Severity: ERROR

+
Message: Configuration entry %s contains multiple mappings for certificate attribute %s.

[#log-ref-log-ref-ERR_SATUACM_NO_SUCH_ATTR_424]
ID: 424::
Severity: ERROR

+
Message: Mapping %s in configuration entry %s references attribute %s which is not defined in the server schema.

[#log-ref-log-ref-ERR_SATUACM_DUPLICATE_USER_ATTR_425]
ID: 425::
Severity: ERROR

+
Message: Configuration entry %s contains multiple mappings for user attribute %s.

[#log-ref-log-ref-ERR_SATUACM_NO_PEER_CERTIFICATE_429]
ID: 429::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

[#log-ref-log-ref-ERR_SATUACM_PEER_CERT_NOT_X509_430]
ID: 430::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

[#log-ref-log-ref-ERR_SATUACM_CANNOT_DECODE_SUBJECT_AS_DN_431]
ID: 431::
Severity: ERROR

+
Message: Unable to decode peer certificate subject %s as a DN: %s.

[#log-ref-log-ref-ERR_SATUACM_NO_MAPPABLE_ATTRIBUTES_432]
ID: 432::
Severity: ERROR

+
Message: Peer certificate subject %s does not contain any attributes for which a mapping has been established.

[#log-ref-log-ref-ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_433]
ID: 433::
Severity: ERROR

+
Message: The certificate with subject %s could not be mapped to exactly one user. It maps to both %s and %s.

[#log-ref-log-ref-ERR_FCM_NO_PEER_CERTIFICATE_443]
ID: 443::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

[#log-ref-log-ref-ERR_FCM_PEER_CERT_NOT_X509_444]
ID: 444::
Severity: ERROR

+
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

[#log-ref-log-ref-ERR_FCM_CANNOT_CALCULATE_FINGERPRINT_445]
ID: 445::
Severity: ERROR

+
Message: An error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %s.

[#log-ref-log-ref-ERR_FCM_MULTIPLE_MATCHING_ENTRIES_446]
ID: 446::
Severity: ERROR

+
Message: The certificate with fingerprint %s could not be mapped to exactly one user. It maps to both %s and %s.

[#log-ref-log-ref-ERR_DYNAMICGROUP_CANNOT_DECODE_MEMBERURL_447]
ID: 447::
Severity: ERROR

+
Message: Unable to decode value "%s" in entry "%s" as an LDAP URL: %s.

[#log-ref-log-ref-ERR_DYNAMICGROUP_NESTING_NOT_SUPPORTED_448]
ID: 448::
Severity: ERROR

+
Message: Dynamic groups do not support nested groups.

[#log-ref-log-ref-ERR_DYNAMICGROUP_ALTERING_MEMBERS_NOT_SUPPORTED_449]
ID: 449::
Severity: ERROR

+
Message: Dynamic groups do not support explicitly altering their membership.

[#log-ref-log-ref-ERR_DYNAMICGROUP_INTERNAL_SEARCH_FAILED_451]
ID: 451::
Severity: ERROR

+
Message: An error occurred while attempting perform an internal search with base DN %s and filter %s to resolve the member list for dynamic group %s: result code %s, error message %s.

[#log-ref-log-ref-ERR_DYNAMICGROUP_CANNOT_RETURN_ENTRY_452]
ID: 452::
Severity: ERROR

+
Message: The server encountered a timeout while attempting to add user %s to the member list for dynamic group %s.

[#log-ref-log-ref-ERR_PWDIFFERENCEVALIDATOR_TOO_SMALL_456]
ID: 456::
Severity: ERROR

+
Message: The provided password differs less than the minimum required difference of %d characters.

[#log-ref-log-ref-ERR_REPEATEDCHARS_VALIDATOR_TOO_MANY_CONSECUTIVE_457]
ID: 457::
Severity: ERROR

+
Message: The provided password contained too many instances of the same character appearing consecutively. The maximum number of times the same character may appear consecutively in a password is %d.

[#log-ref-log-ref-ERR_UNIQUECHARS_VALIDATOR_NOT_ENOUGH_UNIQUE_CHARS_458]
ID: 458::
Severity: ERROR

+
Message: The provided password does not contain enough unique characters. The minimum number of unique characters that may appear in a user password is %d.

[#log-ref-log-ref-ERR_VATTR_NOT_SEARCHABLE_459]
ID: 459::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_DICTIONARY_VALIDATOR_PASSWORD_IN_DICTIONARY_460]
ID: 460::
Severity: ERROR

+
Message: The provided password contained a word from the server's dictionary.

[#log-ref-log-ref-ERR_DICTIONARY_VALIDATOR_NO_SUCH_FILE_461]
ID: 461::
Severity: ERROR

+
Message: The specified dictionary file %s does not exist.

[#log-ref-log-ref-ERR_DICTIONARY_VALIDATOR_CANNOT_READ_FILE_462]
ID: 462::
Severity: ERROR

+
Message: An error occurred while attempting to load the dictionary from file %s: %s.

[#log-ref-log-ref-ERR_ATTRVALUE_VALIDATOR_PASSWORD_IN_ENTRY_463]
ID: 463::
Severity: ERROR

+
Message: The provided password was found in another attribute in the user entry.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_ILLEGAL_CHARACTER_464]
ID: 464::
Severity: ERROR

+
Message: The provided password contained character '%s' which is not allowed for use in passwords.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_SET_465]
ID: 465::
Severity: ERROR

+
Message: The provided password did not contain enough characters from the character set '%s'. The minimum number of characters from that set that must be present in user passwords is %d.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_NO_SET_COLON_466]
ID: 466::
Severity: ERROR

+
Message: The provided character set definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character set.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_NO_SET_CHARS_467]
ID: 467::
Severity: ERROR

+
Message: The provided character set definition '%s' is invalid because the provided character set is empty.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_INVALID_SET_COUNT_468]
ID: 468::
Severity: ERROR

+
Message: The provided character set definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_DUPLICATE_CHAR_469]
ID: 469::
Severity: ERROR

+
Message: The provided character set definition '%s' is invalid because it contains character '%s' which has already been used.

[#log-ref-log-ref-ERR_VIRTUAL_STATIC_GROUP_MULTIPLE_TARGETS_470]
ID: 470::
Severity: ERROR

+
Message: The virtual static group defined in entry %s contains multiple target group DNs, but only one is allowed.

[#log-ref-log-ref-ERR_VIRTUAL_STATIC_GROUP_CANNOT_DECODE_TARGET_471]
ID: 471::
Severity: ERROR

+
Message: Unable to decode "%s" as the target DN for group %s: %s.

[#log-ref-log-ref-ERR_VIRTUAL_STATIC_GROUP_NO_TARGET_472]
ID: 472::
Severity: ERROR

+
Message: The virtual static group defined in entry %s does not contain a target group definition.

[#log-ref-log-ref-ERR_VIRTUAL_STATIC_GROUP_NESTING_NOT_SUPPORTED_473]
ID: 473::
Severity: ERROR

+
Message: Virtual static groups do not support nesting.

[#log-ref-log-ref-ERR_VIRTUAL_STATIC_GROUP_NO_TARGET_GROUP_474]
ID: 474::
Severity: ERROR

+
Message: Target group %s referenced by virtual static group %s does not exist.

[#log-ref-log-ref-ERR_VIRTUAL_STATIC_GROUP_ALTERING_MEMBERS_NOT_SUPPORTED_475]
ID: 475::
Severity: ERROR

+
Message: Altering membership for virtual static group %s is not allowed.

[#log-ref-log-ref-ERR_VIRTUAL_STATIC_GROUP_TARGET_CANNOT_BE_VIRTUAL_476]
ID: 476::
Severity: ERROR

+
Message: Virtual static group %s references target group %s which is itself a virtual static group. One virtual static group is not allowed to reference another as its target group.

[#log-ref-log-ref-ERR_ENTRYUUID_VATTR_NOT_SEARCHABLE_501]
ID: 501::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_NO_PRIVILEGE_502]
ID: 502::
Severity: ERROR

+
Message: You do not have sufficient privileges to use the password policy state extended operation.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_NO_REQUEST_VALUE_503]
ID: 503::
Severity: ERROR

+
Message: The provided password policy state extended request did not include a request value.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_DECODE_FAILURE_504]
ID: 504::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to decode password policy state extended request value: %s.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_MULTIPLE_ENTRIES_505]
ID: 505::
Severity: ERROR

+
Message: Multiple entries were found with DN %s.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_INVALID_OP_ENCODING_506]
ID: 506::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to decode an operation from the password policy state extended request: %s.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_NO_DISABLED_VALUE_507]
ID: 507::
Severity: ERROR

+
Message: No value was provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE_COUNT_508]
ID: 508::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE_509]
ID: 509::
Severity: ERROR

+
Message: The value provided for the password policy state operation intended to set the disabled state for the user was invalid. The value must be either 'true' or 'false'.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE_COUNT_510]
ID: 510::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to set the account expiration time for the user. Exactly one value must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE_511]
ID: 511::
Severity: ERROR

+
Message: The value %s provided for the password policy state operation used to set the account expiration time was invalid: %s. The value should be specified using the generalized time format.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE_COUNT_512]
ID: 512::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to set the password changed time for the user. Exactly one value must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE_513]
ID: 513::
Severity: ERROR

+
Message: The value %s provided for the password policy state operation used to set the password changed time was invalid: %s. The value should be specified using the generalized time format.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE_COUNT_514]
ID: 514::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to set the password warned time for the user. Exactly one value must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE_515]
ID: 515::
Severity: ERROR

+
Message: The value %s provided for the password policy state operation used to set the password warned time was invalid: %s. The value should be specified using the generalized time format.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_ADD_FAILURE_TIME_COUNT_516]
ID: 516::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to add an authentication failure time for the user. Exactly one value must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_AUTH_FAILURE_TIME_517]
ID: 517::
Severity: ERROR

+
Message: The value %s provided for the password policy state operation used to update the authentication failure times was invalid: %s. The value should be specified using the generalized time format.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME_COUNT_518]
ID: 518::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to set the last login time for the user. Exactly one value must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME_519]
ID: 519::
Severity: ERROR

+
Message: The value %s provided for the password policy state operation used to set the last login time was invalid: %s. The value should be specified using the generalized time format.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_NO_RESET_STATE_VALUE_520]
ID: 520::
Severity: ERROR

+
Message: No value was provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE_COUNT_521]
ID: 521::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE_522]
ID: 522::
Severity: ERROR

+
Message: The value provided for the password policy state operation intended to set the reset state for the user was invalid. The value must be either 'true' or 'false'.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_ADD_GRACE_LOGIN_TIME_COUNT_523]
ID: 523::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to add a grace login use time for the user. Exactly one value must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_GRACE_LOGIN_TIME_524]
ID: 524::
Severity: ERROR

+
Message: The value %s provided for the password policy state operation used to update the grace login use times was invalid: %s. The value should be specified using the generalized time format.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME_COUNT_525]
ID: 525::
Severity: ERROR

+
Message: Multiple values were provided for the password policy state operation intended to set the required change time for the user. Exactly one value must be given.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME_526]
ID: 526::
Severity: ERROR

+
Message: The value %s provided for the password policy state operation used to set the required change time was invalid: %s. The value should be specified using the generalized time format.

[#log-ref-log-ref-ERR_PWPSTATE_EXTOP_UNKNOWN_OP_TYPE_527]
ID: 527::
Severity: ERROR

+
Message: The password policy state extended request included an operation with an invalid or unsupported operation type of %s.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_PW_IN_HISTORY_530]
ID: 530::
Severity: ERROR

+
Message: The provided new password was already contained in the password history.

[#log-ref-log-ref-ERR_SMTPALERTHANDLER_NO_SMTP_SERVERS_531]
ID: 531::
Severity: ERROR

+
Message: The Directory Server is not configured with any SMTP servers. The SMTP alert handler cannot be used unless the Directory Server is configured with information about at least one SMTP server.

[#log-ref-log-ref-ERR_REGEXMAP_INVALID_MATCH_PATTERN_533]
ID: 533::
Severity: ERROR

+
Message: The provided match pattern "%s" could not be parsed as a regular expression: %s.

[#log-ref-log-ref-ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_535]
ID: 535::
Severity: ERROR

+
Message: The processed ID string %s mapped to multiple users.

[#log-ref-log-ref-ERR_REGEXMAP_INEFFICIENT_SEARCH_536]
ID: 536::
Severity: ERROR

+
Message: The internal search based on processed ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

[#log-ref-log-ref-ERR_REGEXMAP_SEARCH_FAILED_537]
ID: 537::
Severity: ERROR

+
Message: An internal failure occurred while attempting to resolve processed ID string %s to a user entry: %s.

[#log-ref-log-ref-ERR_STATICGROUP_ADD_NESTED_GROUP_ALREADY_EXISTS_538]
ID: 538::
Severity: ERROR

+
Message: Cannot add group %s as a new nested group of static group %s because that group is already in the nested group list for the group.

[#log-ref-log-ref-ERR_STATICGROUP_REMOVE_NESTED_GROUP_NO_SUCH_GROUP_539]
ID: 539::
Severity: ERROR

+
Message: Cannot remove group %s as a nested group of static group %s because that group is not included in the nested group list for the group.

[#log-ref-log-ref-ERR_STATICGROUP_GROUP_INSTANCE_INVALID_540]
ID: 540::
Severity: ERROR

+
Message: Group instance with DN %s has been deleted and is no longer valid.

[#log-ref-log-ref-ERR_NUMSUBORDINATES_VATTR_NOT_SEARCHABLE_541]
ID: 541::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_HASSUBORDINATES_VATTR_NOT_SEARCHABLE_542]
ID: 542::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_SMTP_ASNH_NO_MAIL_SERVERS_CONFIGURED_543]
ID: 543::
Severity: ERROR

+
Message: The SMTP account status notification handler defined in configuration entry %s cannot be enabled unless the Directory Server is with information about one or more SMTP servers.

[#log-ref-log-ref-ERR_SMTP_ASNH_NO_RECIPIENTS_544]
ID: 544::
Severity: ERROR

+
Message: SMTP account status notification handler configuration entry '%s' does not include any email address attribute types or recipient addresses. At least one of these must be provided.

[#log-ref-log-ref-ERR_SMTP_ASNH_SUBJECT_NO_COLON_545]
ID: 545::
Severity: ERROR

+
Message: Unable to parse message subject value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the subject.

[#log-ref-log-ref-ERR_SMTP_ASNH_SUBJECT_INVALID_NOTIFICATION_TYPE_546]
ID: 546::
Severity: ERROR

+
Message: Unable to parse message subject value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type.

[#log-ref-log-ref-ERR_SMTP_ASNH_SUBJECT_DUPLICATE_TYPE_547]
ID: 547::
Severity: ERROR

+
Message: The message subject definitions contained in configuration entry '%s' have multiple subjects defined for notification type %s.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_NO_COLON_548]
ID: 548::
Severity: ERROR

+
Message: Unable to parse message template file path value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the template file path.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_INVALID_NOTIFICATION_TYPE_549]
ID: 549::
Severity: ERROR

+
Message: Unable to parse message template file path value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_DUPLICATE_TYPE_550]
ID: 550::
Severity: ERROR

+
Message: The message template file path definitions contained in configuration entry '%s' have multiple template file paths defined for notification type %s.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_NO_SUCH_FILE_551]
ID: 551::
Severity: ERROR

+
Message: The message template file '%s' referenced in configuration entry '%s' does not exist.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_UNCLOSED_TOKEN_552]
ID: 552::
Severity: ERROR

+
Message: An unclosed token was found starting at column %d of line %d.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_ATTR_TYPE_553]
ID: 553::
Severity: ERROR

+
Message: The notification-user-attr token starting at column %d of line %d references undefined attribute type %s.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_PROPERTY_554]
ID: 554::
Severity: ERROR

+
Message: The notification-property token starting at column %d of line %d references undefined notification property %s.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_UNRECOGNIZED_TOKEN_555]
ID: 555::
Severity: ERROR

+
Message: An unrecognized token %s was found at column %d of line %d.

[#log-ref-log-ref-ERR_SMTP_ASNH_TEMPLATE_CANNOT_PARSE_556]
ID: 556::
Severity: ERROR

+
Message: An error occurred while attempting to parse message template file '%s' referenced in configuration entry '%s': %s.

[#log-ref-log-ref-ERR_SMTP_ASNH_CANNOT_SEND_MESSAGE_558]
ID: 558::
Severity: ERROR

+
Message: An error occurred while attempting to send an account status notification message for notification type %s for user entry %s: %s.

[#log-ref-log-ref-ERR_PWSCHEME_CANNOT_ENCRYPT_559]
ID: 559::
Severity: ERROR

+
Message: An error occurred while trying to encrypt a value using password storage scheme %s: %s.

[#log-ref-log-ref-ERR_PWSCHEME_CANNOT_DECRYPT_560]
ID: 560::
Severity: ERROR

+
Message: An error occurred while trying to decrypt a value using password storage scheme %s: %s.

[#log-ref-log-ref-ERR_GET_SYMMETRIC_KEY_NO_VALUE_561]
ID: 561::
Severity: ERROR

+
Message: Cannot decode the provided symmetric key extended operation because it does not have a value.

[#log-ref-log-ref-ERR_GET_SYMMETRIC_KEY_ASN1_DECODE_EXCEPTION_563]
ID: 563::
Severity: ERROR

+
Message: Cannot decode the provided symmetric key extended request: %s.

[#log-ref-log-ref-ERR_GET_SYMMETRIC_KEY_DECODE_EXCEPTION_564]
ID: 564::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to decode the symmetric key extended request sequence: %s.

[#log-ref-log-ref-ERR_EXACTMAP_ATTR_UNINDEXED_565]
ID: 565::
Severity: ERROR

+
Message: The exact match identity mapper defined in configuration entry %s references attribute type %s which is does not have an equality index defined in backend %s.

[#log-ref-log-ref-ERR_REGEXMAP_ATTR_UNINDEXED_566]
ID: 566::
Severity: ERROR

+
Message: The regular expression identity mapper defined in configuration entry %s references attribute type %s which is does not have an equality index defined in backend %s.

[#log-ref-log-ref-ERR_SASL_CREATE_SASL_SERVER_FAILED_572]
ID: 572::
Severity: ERROR

+
Message: Failed to create a SASL server for SASL mechanism %s using a server FQDN of %s.

[#log-ref-log-ref-ERR_SASL_GSSAPI_KEYTAB_INVALID_573]
ID: 573::
Severity: ERROR

+
Message: GSSAPI SASL mechanism handler initalization failed because the keytab file %s does not exist.

[#log-ref-log-ref-ERR_COLLECTIVEATTRIBUTESUBENTRIES_VATTR_NOT_SEARCHABLE_576]
ID: 576::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_PASSWORDPOLICYSUBENTRY_VATTR_NOT_SEARCHABLE_577]
ID: 577::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_PWSCHEME_INVALID_BASE64_DECODED_STORED_PASSWORD_578]
ID: 578::
Severity: ERROR

+
Message: The password value %s has been base64-decoded but is too short to be valid.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_MIN_CHAR_SETS_TOO_SMALL_579]
ID: 579::
Severity: ERROR

+
Message: The provided minimum required number of character sets '%d' is invalid because it must at least include all mandatory character sets.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_MIN_CHAR_SETS_TOO_BIG_580]
ID: 580::
Severity: ERROR

+
Message: The provided minimum required number of character sets '%d' is invalid because it is greater than the total number of defined character sets.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_TOO_FEW_OPTIONAL_CHAR_SETS_581]
ID: 581::
Severity: ERROR

+
Message: The provided password did not contain characters from at least %d of the following character sets or ranges: %s.

[#log-ref-log-ref-ERR_STATICMEMBERS_CANNOT_DECODE_DN_582]
ID: 582::
Severity: ERROR

+
Message: An error occurred while attempting to decode member's DN %s of static group %s: %s.

[#log-ref-log-ref-ERR_SASL_ACCOUNT_NOT_LOCAL_583]
ID: 583::
Severity: ERROR

+
Message: SASL %s authentication is not supported for user %s because the account is not managed locally.

[#log-ref-log-ref-ERR_EXTOP_PASSMOD_ACCOUNT_NOT_LOCAL_584]
ID: 584::
Severity: ERROR

+
Message: Password modification is not supported for user %s because the account is not managed locally.

[#log-ref-log-ref-ERR_EXTOP_PWPSTATE_ACCOUNT_NOT_LOCAL_585]
ID: 585::
Severity: ERROR

+
Message: The password policy state extended operation is not supported for user %s because the account is not managed locally.

[#log-ref-log-ref-ERR_LDAP_PTA_MAPPING_ATTRIBUTE_NOT_FOUND_586]
ID: 586::
Severity: ERROR

+
Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the following mapping attributes were not found in the user's entry: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_MAPPED_SEARCH_TOO_MANY_CANDIDATES_587]
ID: 587::
Severity: ERROR

+
Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search of base DN "%s" returned more than one entry matching the filter "%s".

[#log-ref-log-ref-ERR_LDAP_PTA_MAPPED_SEARCH_NO_CANDIDATES_588]
ID: 588::
Severity: ERROR

+
Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search did not return any entries matching the filter "%s".

[#log-ref-log-ref-ERR_LDAP_PTA_MAPPED_SEARCH_FAILED_589]
ID: 589::
Severity: ERROR

+
Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search failed unexpectedly for the following reason: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_MAPPED_BIND_FAILED_590]
ID: 590::
Severity: ERROR

+
Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the bind failed unexpectedly for the following reason: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECT_UNKNOWN_HOST_591]
ID: 591::
Severity: ERROR

+
Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because the host name "%s" could not be resolved to an IP address.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECT_ERROR_592]
ID: 592::
Severity: ERROR

+
Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because the connection was refused. This may indicate that the server is either offline or it is not listening on port %d.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECT_TIMEOUT_593]
ID: 593::
Severity: ERROR

+
Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because the connection attempt timed out. This may indicate that the server is slow to respond, the network is slow, or that there is some other network problem.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECT_SSL_ERROR_594]
ID: 594::
Severity: ERROR

+
Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because SSL negotiation failed for the following reason: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECT_OTHER_ERROR_595]
ID: 595::
Severity: ERROR

+
Message: A connection could not be established to the remote LDAP server at %s:%d for LDAP PTA policy "%s" because an unexpected error occurred: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_OTHER_ERROR_596]
ID: 596::
Severity: ERROR

+
Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has failed unexpectedly: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_CLOSED_597]
ID: 597::
Severity: ERROR

+
Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has been closed unexpectedly.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_TIMEOUT_598]
ID: 598::
Severity: ERROR

+
Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has timed out and will be closed. This may indicate that the server is slow to respond, the network is slow, or that there is some other network problem.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_DECODE_ERROR_599]
ID: 599::
Severity: ERROR

+
Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has encountered a protocol error while decoding a response from the server and will be closed. The decoding error was: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_WRONG_RESPONSE_600]
ID: 600::
Severity: ERROR

+
Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has received an unexpected response from the server and will be closed. The unexpected response message was: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_DISCONNECTING_601]
ID: 601::
Severity: ERROR

+
Message: The connection to the remote LDAP server at %s:%d for LDAP PTA policy "%s" has received a disconnect notification with response code %d (%s) and error message "%s".

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_BIND_FAILED_602]
ID: 602::
Severity: ERROR

+
Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" has failed to authenticate user "%s", returning the response code %d (%s) and error message "%s".

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_SEARCH_SIZE_LIMIT_603]
ID: 603::
Severity: ERROR

+
Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" returned multiple matching entries while searching "%s" using the filter "%s".

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_SEARCH_NO_MATCHES_604]
ID: 604::
Severity: ERROR

+
Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" did not return any matching entries while searching "%s" using the filter "%s".

[#log-ref-log-ref-ERR_LDAP_PTA_CONNECTION_SEARCH_FAILED_605]
ID: 605::
Severity: ERROR

+
Message: The remote LDAP server at %s:%d for LDAP PTA policy "%s" returned an error while searching "%s" using the filter "%s": response code %d (%s) and error message "%s".

[#log-ref-log-ref-ERR_LDAP_PTA_INVALID_PORT_NUMBER_606]
ID: 606::
Severity: ERROR

+
Message: The configuration of LDAP PTA policy "%s" is invalid because the remote LDAP server address "%s" specifies a port number which is invalid. Port numbers should be greater than 0 and less than 65536.

[#log-ref-log-ref-ERR_LDAP_PTA_PWD_PROPERTY_NOT_SET_607]
ID: 607::
Severity: ERROR

+
Message: The configuration of LDAP PTA policy "%s" is invalid because the Java property %s which should contain the mapped search bind password is not set.

[#log-ref-log-ref-ERR_LDAP_PTA_PWD_ENVAR_NOT_SET_608]
ID: 608::
Severity: ERROR

+
Message: The configuration of LDAP PTA policy "%s" is invalid because the environment variable %s which should contain the mapped search bind password is not set.

[#log-ref-log-ref-ERR_LDAP_PTA_PWD_NO_SUCH_FILE_609]
ID: 609::
Severity: ERROR

+
Message: The configuration of LDAP PTA policy "%s" is invalid because the file %s which should contain the mapped search bind password does not exist.

[#log-ref-log-ref-ERR_LDAP_PTA_PWD_FILE_CANNOT_READ_610]
ID: 610::
Severity: ERROR

+
Message: The configuration of LDAP PTA policy "%s" is invalid because the file %s which should contain the mapped search bind password cannot be read for the following reason: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_PWD_FILE_EMPTY_611]
ID: 611::
Severity: ERROR

+
Message: The configuration of LDAP PTA policy "%s" is invalid because the file %s which should contain the mapped search bind password is empty.

[#log-ref-log-ref-ERR_LDAP_PTA_NO_PWD_613]
ID: 613::
Severity: ERROR

+
Message: The configuration of LDAP PTA policy "%s" is invalid because it does not specify the a means for obtaining the mapped search bind password.

[#log-ref-log-ref-ERR_ETAG_VATTR_NOT_SEARCHABLE_614]
ID: 614::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_PWDEXPTIME_VATTR_NOT_SEARCHABLE_615]
ID: 615::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_SATUACM_MULTIPLE_SEARCH_MATCHING_ENTRIES_616]
ID: 616::
Severity: ERROR

+
Message: The certificate with subject %s mapped to multiple users.

[#log-ref-log-ref-ERR_SATUACM_INEFFICIENT_SEARCH_617]
ID: 617::
Severity: ERROR

+
Message: The internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

[#log-ref-log-ref-ERR_SATUACM_SEARCH_FAILED_618]
ID: 618::
Severity: ERROR

+
Message: An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s.

[#log-ref-log-ref-ERR_SDTUACM_MULTIPLE_SEARCH_MATCHING_ENTRIES_619]
ID: 619::
Severity: ERROR

+
Message: The certificate with subject %s mapped to multiple users.

[#log-ref-log-ref-ERR_SDTUACM_INEFFICIENT_SEARCH_620]
ID: 620::
Severity: ERROR

+
Message: The internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

[#log-ref-log-ref-ERR_SDTUACM_SEARCH_FAILED_621]
ID: 621::
Severity: ERROR

+
Message: An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s.

[#log-ref-log-ref-ERR_FCM_MULTIPLE_SEARCH_MATCHING_ENTRIES_622]
ID: 622::
Severity: ERROR

+
Message: The certificate with fingerprint %s mapped to multiple users.

[#log-ref-log-ref-ERR_FCM_INEFFICIENT_SEARCH_623]
ID: 623::
Severity: ERROR

+
Message: The internal search based on the certificate with fingerprint %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

[#log-ref-log-ref-ERR_FCM_SEARCH_FAILED_624]
ID: 624::
Severity: ERROR

+
Message: An internal failure occurred while attempting to map the certificate with fingerprint %s to a user entry: %s.

[#log-ref-log-ref-ERR_FIRSTCHANGENUMBER_VATTR_NOT_SEARCHABLE_625]
ID: 625::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_LASTCHANGENUMBER_VATTR_NOT_SEARCHABLE_626]
ID: 626::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_LASTCOOKIE_VATTR_NOT_SEARCHABLE_627]
ID: 627::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_CHANGELOGBASEDN_VATTR_NOT_SEARCHABLE_628]
ID: 628::
Severity: ERROR

+
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_TOO_FEW_CHARS_FROM_RANGE_629]
ID: 629::
Severity: ERROR

+
Message: The provided password did not contain enough characters from the character range '%s'. The minimum number of characters from that range that must be present in user passwords is %d.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_NO_RANGE_COLON_630]
ID: 630::
Severity: ERROR

+
Message: The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_NO_RANGE_CHARS_631]
ID: 631::
Severity: ERROR

+
Message: The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_INVALID_RANGE_COUNT_632]
ID: 632::
Severity: ERROR

+
Message: The provided character range definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_UNSORTED_RANGE_633]
ID: 633::
Severity: ERROR

+
Message: The provided character range definition '%s' is invalid because the range '%s' is reversed.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_MALFORMED_RANGE_634]
ID: 634::
Severity: ERROR

+
Message: The provided character range definition '%s' is invalid because the range '%s' is missing the minus.

[#log-ref-log-ref-ERR_CHARSET_VALIDATOR_SHORT_RANGE_635]
ID: 635::
Severity: ERROR

+
Message: The provided character range definition '%s' is invalid because the range '%s' is too short.

[#log-ref-log-ref-ERR_NO_KEY_ENTRY_IN_KEYSTORE_636]
ID: 636::
Severity: ERROR

+
Message: There is no private key entry in keystore %s.

[#log-ref-log-ref-ERR_PWSCHEME_INVALID_STORED_PASSWORD_638]
ID: 638::
Severity: ERROR

+
Message: An error occurred while attempting to match a bcrypt hashed password value: %s.

[#log-ref-log-ref-ERR_LDAP_PTA_INVALID_FILTER_TEMPLATE_639]
ID: 639::
Severity: ERROR

+
Message: The mapped search filter template "%s" could not be parsed as a valid LDAP filter.

--


[#LOGGER]
=== Log Message Category: LOGGER

--

[#log-ref-log-ref-ERR_LOGGER_ERROR_WRITING_RECORD_1]
ID: 1::
Severity: ERROR

+
Message: Error occurred while writing log record for logger %s: %s. Any further write errors will be ignored.

[#log-ref-log-ref-ERR_LOGGER_ERROR_OPENING_FILE_2]
ID: 2::
Severity: ERROR

+
Message: Error occurred while opening log file %s for logger %s: %s.

[#log-ref-log-ref-ERR_LOGGER_ERROR_CLOSING_FILE_3]
ID: 3::
Severity: ERROR

+
Message: Error occurred while closing log file for logger %s: %s.

[#log-ref-log-ref-ERR_LOGGER_ERROR_FLUSHING_BUFFER_4]
ID: 4::
Severity: ERROR

+
Message: Error occurred while flushing writer buffer for logger %s: %s.

[#log-ref-log-ref-ERR_LOGGER_ERROR_LISTING_FILES_10]
ID: 10::
Severity: ERROR

+
Message: Error occurred while listing log files named by policy with initial file name %s.

[#log-ref-log-ref-ERR_LOGGER_ERROR_OBTAINING_FREE_SPACE_11]
ID: 11::
Severity: ERROR

+
Message: Error occurred while obtaining free disk space in the partition containing log file %s: %s.

[#log-ref-log-ref-ERR_LOGGER_ERROR_ENFORCING_RETENTION_POLICY_12]
ID: 12::
Severity: ERROR

+
Message: Error occurred while enforcing retention policy %s for logger %s: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_CREATE_13]
ID: 13::
Severity: ERROR

+
Message: Error occurred while creating common audit facility: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_ADD_OR_UPDATE_LOG_PUBLISHER_14]
ID: 14::
Severity: ERROR

+
Message: Error while creating or updating common audit log publisher %s: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_REMOVE_LOG_PUBLISHER_15]
ID: 15::
Severity: ERROR

+
Message: Error while removing common audit log publisher %s: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_UNSUPPORTED_HANDLER_TYPE_16]
ID: 16::
Severity: ERROR

+
Message: Error while adding common audit log publisher %s, the publisher has an unsupported handler type.

[#log-ref-log-ref-ERR_COMMON_AUDIT_EXTERNAL_HANDLER_JSON_FILE_17]
ID: 17::
Severity: ERROR

+
Message: Error while reading JSON configuration file %s while creating common audit external log publisher %s: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_EXTERNAL_HANDLER_CREATION_18]
ID: 18::
Severity: ERROR

+
Message: Error while creating common audit external log publisher %s: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_CSV_HANDLER_CREATION_19]
ID: 19::
Severity: ERROR

+
Message: Error while creating CSV log publisher %s: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_UNSUPPORTED_LOG_ROTATION_POLICY_20]
ID: 20::
Severity: ERROR

+
Message: Error while adding common audit CSV log publisher %s, the publisher defines an unsupported log rotation policy %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_UNSUPPORTED_LOG_RETENTION_POLICY_21]
ID: 21::
Severity: ERROR

+
Message: Error while adding common audit CSV log publisher %s, the publisher defines an unsupported log retention policy %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_UNSUPPORTED_LOG_PUBLISHER_22]
ID: 22::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, this type of log publisher is unsupported.

[#log-ref-log-ref-ERR_COMMON_AUDIT_CSV_HANDLER_DELIMITER_CHAR_23]
ID: 23::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, delimiter char '%s' should not contains more than one character.

[#log-ref-log-ref-ERR_COMMON_AUDIT_CSV_HANDLER_QUOTE_CHAR_24]
ID: 24::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, quote char '%s' should not contains more than one character.

[#log-ref-log-ref-ERR_COMMON_AUDIT_INVALID_TIME_OF_DAY_25]
ID: 25::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, time of the day value '%s' for fixed time log rotation policy is not valid, it should use a 24-hour format "HHmm" : %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_INVALID_TRANSACTION_ID_26]
ID: 26::
Severity: ERROR

+
Message: Error while decoding a transaction id control received from a request: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_UNABLE_TO_PROCESS_LOG_EVENT_27]
ID: 27::
Severity: ERROR

+
Message: Error while processing a log event for common audit: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_MISSING_28]
ID: 28::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, the keystore pin file %s is missing.

[#log-ref-log-ref-ERR_COMMON_AUDIT_ERROR_READING_KEYSTORE_PIN_FILE_29]
ID: 29::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, the keystore pin file %s could not be read: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_KEYSTORE_PIN_FILE_CONTAINS_EMPTY_PIN_30]
ID: 30::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, the keystore pin file %s contains an empty pin.

[#log-ref-log-ref-ERR_COMMON_AUDIT_KEYSTORE_FILE_MISSING_31]
ID: 31::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, the keystore file %s is missing.

[#log-ref-log-ref-ERR_COMMON_AUDIT_ERROR_READING_KEYSTORE_FILE_32]
ID: 32::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, the keystore file %s could not be read: %s.

[#log-ref-log-ref-ERR_COMMON_AUDIT_KEYSTORE_FILE_IS_EMPTY_33]
ID: 33::
Severity: ERROR

+
Message: Error while processing common audit log publisher %s, the keystore file %s is empty.

--


[#PLUGIN]
=== Log Message Category: PLUGIN

--

[#log-ref-log-ref-ERR_PLUGIN_ADLIST_NO_PLUGIN_TYPES_3]
ID: 3::
Severity: ERROR

+
Message: The LDAP attribute description list plugin instance defined in configuration entry %s does not list any plugin types. This plugin must be configured to operate as a pre-parse search plugin.

[#log-ref-log-ref-ERR_PLUGIN_ADLIST_INVALID_PLUGIN_TYPE_4]
ID: 4::
Severity: ERROR

+
Message: The LDAP attribute description list plugin instance defined in configuration entry %s lists an invalid plugin type %s. This plugin can only be used as a pre-parse search plugin.

[#log-ref-log-ref-ERR_PLUGIN_PROFILER_NO_PLUGIN_TYPES_5]
ID: 5::
Severity: ERROR

+
Message: The Directory Server profiler plugin instance defined in configuration entry %s does not list any plugin types. This plugin must be configured to operate as a startup plugin.

[#log-ref-log-ref-ERR_PLUGIN_PROFILER_INVALID_PLUGIN_TYPE_6]
ID: 6::
Severity: ERROR

+
Message: The Directory Server profiler plugin instance defined in configuration entry %s lists an invalid plugin type %s. This plugin can only be used as a startup plugin.

[#log-ref-log-ref-ERR_PLUGIN_PROFILER_CANNOT_WRITE_PROFILE_DATA_9]
ID: 9::
Severity: ERROR

+
Message: An unexpected error occurred when the profiler plugin defined in configuration entry %s attempted to write the information captured to output file %s: %s.

[#log-ref-log-ref-ERR_PLUGIN_STARTUP_PLUGIN_EXCEPTION_30]
ID: 30::
Severity: ERROR

+
Message: The startup plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server startup process: %s. The server startup process has been aborted.

[#log-ref-log-ref-ERR_PLUGIN_STARTUP_PLUGIN_RETURNED_NULL_31]
ID: 31::
Severity: ERROR

+
Message: The startup plugin defined in configuration entry %s returned a null value when it was invoked during the Directory Server startup process. This is an illegal return value, and the server startup process has been aborted.

[#log-ref-log-ref-ERR_PLUGIN_STARTUP_PLUGIN_FAIL_ABORT_33]
ID: 33::
Severity: ERROR

+
Message: The startup plugin defined in configuration entry %s encountered an error when it was invoked during the Directory Server startup process: %s (error ID %d). The server startup process has been aborted.

[#log-ref-log-ref-ERR_PLUGIN_SHUTDOWN_PLUGIN_EXCEPTION_34]
ID: 34::
Severity: ERROR

+
Message: The shutdown plugin defined in configuration entry %s threw an exception when it was invoked during the Directory Server shutdown process: %s.

[#log-ref-log-ref-ERR_PLUGIN_POST_CONNECT_PLUGIN_EXCEPTION_35]
ID: 35::
Severity: ERROR

+
Message: The post-connect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %s. The connection will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_POST_CONNECT_PLUGIN_RETURNED_NULL_36]
ID: 36::
Severity: ERROR

+
Message: The post-connect plugin defined in configuration entry %s returned null when invoked for connection %d from %s. This is an illegal response, and the connection will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_POST_DISCONNECT_PLUGIN_EXCEPTION_37]
ID: 37::
Severity: ERROR

+
Message: The post-disconnect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %s.

[#log-ref-log-ref-ERR_PLUGIN_POST_DISCONNECT_PLUGIN_RETURNED_NULL_38]
ID: 38::
Severity: ERROR

+
Message: The post-disconnect plugin defined in configuration entry %s returned null when invoked for connection %d from %s. This is an illegal response.

[#log-ref-log-ref-ERR_PLUGIN_PRE_PARSE_PLUGIN_EXCEPTION_39]
ID: 39::
Severity: ERROR

+
Message: The pre-parse %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_PRE_PARSE_PLUGIN_RETURNED_NULL_40]
ID: 40::
Severity: ERROR

+
Message: The pre-parse %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_PRE_OPERATION_PLUGIN_EXCEPTION_41]
ID: 41::
Severity: ERROR

+
Message: The pre-operation %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_PRE_OPERATION_PLUGIN_RETURNED_NULL_42]
ID: 42::
Severity: ERROR

+
Message: The pre-operation %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_POST_OPERATION_PLUGIN_EXCEPTION_43]
ID: 43::
Severity: ERROR

+
Message: The post-operation %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_POST_OPERATION_PLUGIN_RETURNED_NULL_44]
ID: 44::
Severity: ERROR

+
Message: The post-operation %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_POST_RESPONSE_PLUGIN_EXCEPTION_45]
ID: 45::
Severity: ERROR

+
Message: The post-response %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_POST_RESPONSE_PLUGIN_RETURNED_NULL_46]
ID: 46::
Severity: ERROR

+
Message: The post-response %s plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_SEARCH_ENTRY_PLUGIN_EXCEPTION_47]
ID: 47::
Severity: ERROR

+
Message: The search result entry plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d with entry %s: %s. Processing on this search operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_SEARCH_ENTRY_PLUGIN_RETURNED_NULL_48]
ID: 48::
Severity: ERROR

+
Message: The search result entry plugin defined in configuration entry %s returned null when invoked for connection %d operation %d with entry %s. This is an illegal response, and processing on this search operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_SEARCH_REFERENCE_PLUGIN_EXCEPTION_49]
ID: 49::
Severity: ERROR

+
Message: The search result reference plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d with referral URL(s) %s: %s. Processing on this search operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_SEARCH_REFERENCE_PLUGIN_RETURNED_NULL_50]
ID: 50::
Severity: ERROR

+
Message: The search result reference plugin defined in configuration entry %s returned null when invoked for connection %d operation %d with referral URL(s) %s. This is an illegal response, and processing on this search operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_LASTMOD_INVALID_PLUGIN_TYPE_51]
ID: 51::
Severity: ERROR

+
Message: An attempt was made to register the LastMod plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

[#log-ref-log-ref-ERR_PROFILEVIEWER_CANNOT_INITIALIZE_ARGS_55]
ID: 55::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to initialize the command-line arguments: %s.

[#log-ref-log-ref-ERR_PROFILEVIEWER_ERROR_PARSING_ARGS_56]
ID: 56::
Severity: ERROR

+
Message: An error occurred while parsing the command-line arguments: %s.

[#log-ref-log-ref-ERR_PROFILEVIEWER_CANNOT_PROCESS_DATA_FILE_57]
ID: 57::
Severity: ERROR

+
Message: An error occurred while trying to process the profile data in file %s: %s.

[#log-ref-log-ref-ERR_PLUGIN_LDIF_IMPORT_PLUGIN_EXCEPTION_58]
ID: 58::
Severity: ERROR

+
Message: The LDIF import plugin defined in configuration entry %s threw an exception when it was invoked on entry %s: %s.

[#log-ref-log-ref-ERR_PLUGIN_LDIF_IMPORT_PLUGIN_RETURNED_NULL_59]
ID: 59::
Severity: ERROR

+
Message: The LDIF import plugin defined in configuration entry %s returned null when invoked on entry %s. This is an illegal response.

[#log-ref-log-ref-ERR_PLUGIN_LDIF_EXPORT_PLUGIN_EXCEPTION_60]
ID: 60::
Severity: ERROR

+
Message: The LDIF export plugin defined in configuration entry %s threw an exception when it was invoked on entry %s: %s.

[#log-ref-log-ref-ERR_PLUGIN_LDIF_EXPORT_PLUGIN_RETURNED_NULL_61]
ID: 61::
Severity: ERROR

+
Message: The LDIF export plugin defined in configuration entry %s returned null when invoked on entry %s. This is an illegal response.

[#log-ref-log-ref-ERR_PLUGIN_ENTRYUUID_INVALID_PLUGIN_TYPE_62]
ID: 62::
Severity: ERROR

+
Message: An attempt was made to register the EntryUUID plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

[#log-ref-log-ref-ERR_PLUGIN_INTERMEDIATE_RESPONSE_PLUGIN_EXCEPTION_63]
ID: 63::
Severity: ERROR

+
Message: The intermediate response plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_INTERMEDIATE_RESPONSE_PLUGIN_RETURNED_NULL_64]
ID: 64::
Severity: ERROR

+
Message: The intermediate response plugin defined in configuration entry %s returned null when invoked for connection %d operation %d. This is an illegal response, and processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_PWPIMPORT_INVALID_PLUGIN_TYPE_65]
ID: 65::
Severity: ERROR

+
Message: An attempt was made to register the password policy import plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

[#log-ref-log-ref-ERR_PLUGIN_PWPIMPORT_ERROR_ENCODING_PASSWORD_66]
ID: 66::
Severity: ERROR

+
Message: An error occurred while attempting to encode a password value stored in attribute %s of user entry %s: %s. Password values for this user will not be encoded.

[#log-ref-log-ref-ERR_PLUGIN_TYPE_NOT_SUPPORTED_67]
ID: 67::
Severity: ERROR

+
Message: The plugin defined in configuration entry %s does not support the %s plugin type.

[#log-ref-log-ref-ERR_PLUGIN_PWIMPORT_NO_DEFAULT_AUTH_SCHEMES_69]
ID: 69::
Severity: ERROR

+
Message: The password policy import plugin is not configured any default auth password schemes, and the server does not support the %s auth password scheme.

[#log-ref-log-ref-ERR_PLUGIN_PWIMPORT_INVALID_DEFAULT_AUTH_SCHEME_70]
ID: 70::
Severity: ERROR

+
Message: Auth password storage scheme %s referenced by the password policy import plugin is not configured for use in the server.

[#log-ref-log-ref-ERR_PLUGIN_PWIMPORT_NO_DEFAULT_USER_SCHEMES_71]
ID: 71::
Severity: ERROR

+
Message: The password policy import plugin is not configured any default user password schemes, and the server does not support the %s auth password scheme.

[#log-ref-log-ref-ERR_PLUGIN_PWIMPORT_INVALID_DEFAULT_USER_SCHEME_72]
ID: 72::
Severity: ERROR

+
Message: User password storage scheme %s referenced by the password policy import plugin is not configured for use in the server.

[#log-ref-log-ref-ERR_PLUGIN_SUBORDINATE_MODIFY_DN_PLUGIN_EXCEPTION_75]
ID: 75::
Severity: ERROR

+
Message: The subordinate modify DN plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_SUBORDINATE_MODIFY_DN_PLUGIN_RETURNED_NULL_76]
ID: 76::
Severity: ERROR

+
Message: The subordinate modify DN plugin defined in configuration entry %s returned null when invoked for connection %d operation %s. This is an illegal response, and processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_UNIQUEATTR_INVALID_PLUGIN_TYPE_77]
ID: 77::
Severity: ERROR

+
Message: An attempt was made to register the Unique Attribute plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_INVALID_PLUGIN_TYPE_81]
ID: 81::
Severity: ERROR

+
Message: An attempt was made to register the Referential Integrity plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_CREATE_LOGFILE_82]
ID: 82::
Severity: ERROR

+
Message: An error occurred during Referential Integity plugin initialization because log file creation failed: %s.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_CLOSE_LOGFILE_83]
ID: 83::
Severity: ERROR

+
Message: An error occurred closing the Referential Integrity plugin update log file: %s.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_REPLACE_LOGFILE_84]
ID: 84::
Severity: ERROR

+
Message: An error occurred replacing the Referential Integrity plugin update log file: %s.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_SEARCH_FAILED_89]
ID: 89::
Severity: ERROR

+
Message: The Referential Integrity plugin failed when performaing an internal search: %s.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_MODIFY_FAILED_90]
ID: 90::
Severity: ERROR

+
Message: The Referential Integrity plugin failed when performing an internal modify on entry %s: %s.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_CANNOT_DECODE_STRING_AS_DN_91]
ID: 91::
Severity: ERROR

+
Message: The Referential Integrity plugin failed to decode a entry DN from the update log: %s.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_INVALID_ATTRIBUTE_SYNTAX_93]
ID: 93::
Severity: ERROR

+
Message: An error occurred in the Referential Integrity plugin while attempting to configure the attribute type %s which has a syntax OID of %s. A Referential Integrity attribute type must have a syntax OID of either 1.3.6.1.4.1.1466.115.121.1.12 (for the distinguished name syntax) or 1.3.6.1.4.1.1466.115.121.1.34 (for the name and optional uid syntax).

[#log-ref-log-ref-ERR_PLUGIN_7BIT_INVALID_PLUGIN_TYPE_96]
ID: 96::
Severity: ERROR

+
Message: The 7-bit clean plugin is configured with invalid plugin type %s. Only the ldifImport, preOperationAdd, preOperationModify, and preOperationModifyDN plugin types are allowed.

[#log-ref-log-ref-ERR_PLUGIN_7BIT_CANNOT_DECODE_DN_97]
ID: 97::
Severity: ERROR

+
Message: An error occurred while trying to decode the DN of the target entry: %s.

[#log-ref-log-ref-ERR_PLUGIN_7BIT_CANNOT_DECODE_ATTR_98]
ID: 98::
Severity: ERROR

+
Message: An error occurred while trying to decode attribute %s in the target entry: %s.

[#log-ref-log-ref-ERR_PLUGIN_7BIT_CANNOT_DECODE_NEW_RDN_99]
ID: 99::
Severity: ERROR

+
Message: An error occurred while trying to decode the new RDN: %s.

[#log-ref-log-ref-ERR_PLUGIN_7BIT_MODIFYDN_ATTR_NOT_CLEAN_102]
ID: 102::
Severity: ERROR

+
Message: The modify DN operation would have resulted in a value for attribute %s that was not 7-bit clean.

[#log-ref-log-ref-ERR_PLUGIN_7BIT_IMPORT_ATTR_NOT_CLEAN_103]
ID: 103::
Severity: ERROR

+
Message: The entry included a value for attribute %s that was not 7-bit clean.

[#log-ref-log-ref-ERR_PLUGIN_PWIMPORT_NO_SUCH_DEFAULT_AUTH_SCHEME_104]
ID: 104::
Severity: ERROR

+
Message: The password policy import plugin references default auth password storage scheme %s which is not available for use in the server.

[#log-ref-log-ref-ERR_PLUGIN_POST_SYNCHRONIZATION_PLUGIN_EXCEPTION_105]
ID: 105::
Severity: ERROR

+
Message: The post-synchronization %s plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s.

[#log-ref-log-ref-ERR_PLUGIN_UNIQUEATTR_ATTR_NOT_UNIQUE_106]
ID: 106::
Severity: ERROR

+
Message: A unique attribute conflict was detected for attribute %s: value %s already exists in entry %s.

[#log-ref-log-ref-ERR_PLUGIN_UNIQUEATTR_SYNC_NOT_UNIQUE_107]
ID: 107::
Severity: ERROR

+
Message: A unique attribute conflict was detected for attribute %s during synchronization (connID=%d, opID=%d): value %s in entry %s conflicts with an existing value in entry %s. Manual interaction is required to eliminate the conflict.

[#log-ref-log-ref-ERR_PLUGIN_UNIQUEATTR_INTERNAL_ERROR_108]
ID: 108::
Severity: ERROR

+
Message: An internal error occurred while attempting to determine whether the operation would have resulted in a unique attribute conflict (result %s, message %s).

[#log-ref-log-ref-ERR_PLUGIN_UNIQUEATTR_INTERNAL_ERROR_SYNC_109]
ID: 109::
Severity: ERROR

+
Message: An internal error occurred while attempting to determine whether the synchronization operation (connID=%d, opID=%d) for entry %s would have resulted in a unique attribute conflict (result %s, message %s).

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_ATTR_UNINDEXED_110]
ID: 110::
Severity: ERROR

+
Message: The referential integrity plugin defined in configuration entry %s is configured to operate on attribute %s but there is no equality index defined for this attribute in backend %s.

[#log-ref-log-ref-ERR_PLUGIN_UNIQUEATTR_ATTR_UNINDEXED_111]
ID: 111::
Severity: ERROR

+
Message: The unique attribute plugin defined in configuration entry %s is configured to operate on attribute %s but there is no equality index defined for this attribute in backend %s.

[#log-ref-log-ref-ERR_PLUGIN_CHANGE_NUMBER_INVALID_PLUGIN_TYPE_113]
ID: 113::
Severity: ERROR

+
Message: An attempt was made to register the Change Number Control plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

[#log-ref-log-ref-ERR_PLUGIN_CHANGE_NUMBER_INVALID_PLUGIN_TYPE_LIST_114]
ID: 114::
Severity: ERROR

+
Message: An attempt was made to register the Change Number Control plugin with the following plugin types : %s. However this plugin must be configured with all of the following plugin types : %s.

[#log-ref-log-ref-ERR_PLUGIN_SUBORDINATE_DELETE_PLUGIN_EXCEPTION_115]
ID: 115::
Severity: ERROR

+
Message: The subordinate delete plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_SUBORDINATE_DELETE_PLUGIN_RETURNED_NULL_116]
ID: 116::
Severity: ERROR

+
Message: The subordinate delete plugin defined in configuration entry %s returned null when invoked for connection %d operation %s. This is an illegal response, and processing on this operation will be terminated.

[#log-ref-log-ref-ERR_PLUGIN_SAMBA_SYNC_INVALID_PLUGIN_TYPE_117]
ID: 117::
Severity: ERROR

+
Message: An attempt was made to register the Samba password synchronization plugin to be invoked as a %s plugin. This plugin type is not allowed for this plugin.

[#log-ref-log-ref-ERR_PLUGIN_SAMBA_SYNC_ENCODING_118]
ID: 118::
Severity: ERROR

+
Message: The Samba password synchronization plugin could not encode a password for the following reasons: %s.

[#log-ref-log-ref-ERR_PLUGIN_SAMBA_SYNC_MODIFICATION_PROCESSING_119]
ID: 119::
Severity: ERROR

+
Message: The Samba password synchronization plugin could not process a modification for the following reason: %s.

[#log-ref-log-ref-ERR_PLUGIN_ATTR_CLEANUP_INITIALIZE_PLUGIN_120]
ID: 120::
Severity: ERROR

+
Message: Invalid plugin type '%s' for the Attribute Cleanup plugin.

[#log-ref-log-ref-ERR_PLUGIN_ATTR_CLEANUP_ATTRIBUTE_MISSING_121]
ID: 121::
Severity: ERROR

+
Message: Attribute '%s' is not defined in the directory schema.

[#log-ref-log-ref-ERR_PLUGIN_ATTR_CLEANUP_DUPLICATE_VALUE_122]
ID: 122::
Severity: ERROR

+
Message: The attribute '%s' has already been defined in the configuration.

[#log-ref-log-ref-ERR_PLUGIN_ATTR_CLEANUP_EQUAL_VALUES_123]
ID: 123::
Severity: ERROR

+
Message: The mapping '%s:%s' maps the attribute to itself.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_ATTR_NOT_LISTED_124]
ID: 124::
Severity: ERROR

+
Message: The property 'check-references-filter-criteria' specifies filtering criteria for attribute '%s', but this attribute is not listed in the 'attribute-type' property.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_BAD_FILTER_125]
ID: 125::
Severity: ERROR

+
Message: The filtering criteria '%s' specified in property 'check-references-filter-criteria' is invalid because the filter could not be decoded: '%s'.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_ENTRY_MISSING_126]
ID: 126::
Severity: ERROR

+
Message: The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not exist in any of the configured naming contexts.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_FILTER_MISMATCH_127]
ID: 127::
Severity: ERROR

+
Message: The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not match the filter '%s'.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_NAMINGCONTEXT_MISMATCH_128]
ID: 128::
Severity: ERROR

+
Message: The entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not belong to any of the configured naming contexts.

[#log-ref-log-ref-ERR_PLUGIN_REFERENT_EXCEPTION_129]
ID: 129::
Severity: ERROR

+
Message: The opration could not be processed due to an unexpected exception: '%s'.

--


[#PROTOCOL]
=== Log Message Category: PROTOCOL

--

[#log-ref-log-ref-ERR_LDAP_MESSAGE_DECODE_NULL_45]
ID: 45::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the sequence was null.

[#log-ref-log-ref-ERR_LDAP_MESSAGE_DECODE_MESSAGE_ID_47]
ID: 47::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the first element of the sequence could not be decoded as an integer message ID: %s.

[#log-ref-log-ref-ERR_LDAP_MESSAGE_DECODE_PROTOCOL_OP_48]
ID: 48::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the second element of the sequence could not be decoded as the protocol op: %s.

[#log-ref-log-ref-ERR_LDAP_MESSAGE_DECODE_CONTROLS_49]
ID: 49::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 sequence as an LDAP message because the third element of the sequence could not be decoded as the set of controls: %s.

[#log-ref-log-ref-ERR_LDAP_CONTROL_DECODE_SEQUENCE_51]
ID: 51::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP control because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_CONTROL_DECODE_OID_53]
ID: 53::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP control because the OID could not be decoded as a string: %s.

[#log-ref-log-ref-ERR_LDAP_CONTROL_DECODE_CRITICALITY_54]
ID: 54::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP control because the criticality could not be decoded as Boolean value: %s.

[#log-ref-log-ref-ERR_LDAP_CONTROL_DECODE_VALUE_55]
ID: 55::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP control because the value could not be decoded as an octet string: %s.

[#log-ref-log-ref-ERR_LDAP_CONTROL_DECODE_CONTROLS_SEQUENCE_58]
ID: 58::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as a set of LDAP controls because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_ABANDON_REQUEST_DECODE_ID_59]
ID: 59::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP abandon request protocol op because a problem occurred while trying to obtain the message ID of the operation to abandon: %s.

[#log-ref-log-ref-ERR_LDAP_RESULT_DECODE_SEQUENCE_60]
ID: 60::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because a problem occurred while trying to parse the result sequence: %s.

[#log-ref-log-ref-ERR_LDAP_RESULT_DECODE_RESULT_CODE_62]
ID: 62::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the first element in the result sequence could not be decoded as an integer result code: %s.

[#log-ref-log-ref-ERR_LDAP_RESULT_DECODE_MATCHED_DN_63]
ID: 63::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the second element in the result sequence could not be decoded as the matched DN: %s.

[#log-ref-log-ref-ERR_LDAP_RESULT_DECODE_ERROR_MESSAGE_64]
ID: 64::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the third element in the result sequence could not be decoded as the error message: %s.

[#log-ref-log-ref-ERR_LDAP_RESULT_DECODE_REFERRALS_65]
ID: 65::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP result protocol op because the fourth element in the result sequence could not be decoded as a set of referral URLs: %s.

[#log-ref-log-ref-ERR_LDAP_BIND_RESULT_DECODE_SERVER_SASL_CREDENTIALS_67]
ID: 67::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind response protocol op because the final element in the result sequence could not be decoded as the server SASL credentials: %s.

[#log-ref-log-ref-ERR_LDAP_EXTENDED_RESULT_DECODE_OID_71]
ID: 71::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind response protocol op because the response OID could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_EXTENDED_RESULT_DECODE_VALUE_72]
ID: 72::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind response protocol op because the response value could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_UNBIND_DECODE_74]
ID: 74::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP unbind request protocol op: %s.

[#log-ref-log-ref-ERR_LDAP_BIND_REQUEST_DECODE_SEQUENCE_75]
ID: 75::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_BIND_REQUEST_DECODE_VERSION_77]
ID: 77::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the protocol version could not be decoded as an integer: %s.

[#log-ref-log-ref-ERR_LDAP_BIND_REQUEST_DECODE_DN_78]
ID: 78::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the bind DN could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_BIND_REQUEST_DECODE_PASSWORD_79]
ID: 79::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the password to use for simple authentication could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_BIND_REQUEST_DECODE_SASL_INFO_80]
ID: 80::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the SASL authentication information could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_BIND_REQUEST_DECODE_INVALID_CRED_TYPE_81]
ID: 81::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because the authentication info element had an invalid BER type (expected 80 or A3, got %x).

[#log-ref-log-ref-ERR_LDAP_BIND_REQUEST_DECODE_CREDENTIALS_82]
ID: 82::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because an unexpected error occurred while trying to decode the authentication info element: %s.

[#log-ref-log-ref-ERR_LDAP_COMPARE_REQUEST_DECODE_SEQUENCE_83]
ID: 83::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_COMPARE_REQUEST_DECODE_DN_85]
ID: 85::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the target DN could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_COMPARE_REQUEST_DECODE_AVA_86]
ID: 86::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the attribute value assertion could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_COMPARE_REQUEST_DECODE_TYPE_88]
ID: 88::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the attribute type could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_COMPARE_REQUEST_DECODE_VALUE_89]
ID: 89::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP compare request protocol op because the assertion value could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_DELETE_REQUEST_DECODE_DN_90]
ID: 90::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP delete request protocol op because the target DN could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_EXTENDED_REQUEST_DECODE_SEQUENCE_91]
ID: 91::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP extended request protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_EXTENDED_REQUEST_DECODE_OID_93]
ID: 93::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP extended request protocol op because the OID could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_EXTENDED_REQUEST_DECODE_VALUE_94]
ID: 94::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP extended request protocol op because the value could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_DN_REQUEST_DECODE_SEQUENCE_95]
ID: 95::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_DN_REQUEST_DECODE_DN_97]
ID: 97::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the entry DN could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_DN_REQUEST_DECODE_NEW_RDN_98]
ID: 98::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the new RDN could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_DN_REQUEST_DECODE_DELETE_OLD_RDN_99]
ID: 99::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the deleteOldRDN flag could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_DN_REQUEST_DECODE_NEW_SUPERIOR_100]
ID: 100::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify DN request protocol op because the new superior DN could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_ATTRIBUTE_DECODE_SEQUENCE_101]
ID: 101::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP attribute because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_ATTRIBUTE_DECODE_TYPE_103]
ID: 103::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP attribute because the attribute type could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_ATTRIBUTE_DECODE_VALUES_104]
ID: 104::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP attribute because the set of values could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_ADD_REQUEST_DECODE_SEQUENCE_105]
ID: 105::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP add request protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_ADD_REQUEST_DECODE_DN_107]
ID: 107::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP add request protocol op because the entry DN could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_ADD_REQUEST_DECODE_ATTRS_108]
ID: 108::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP add request protocol op because the set of attributes could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFICATION_DECODE_SEQUENCE_109]
ID: 109::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modification because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFICATION_DECODE_INVALID_MOD_TYPE_111]
ID: 111::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modification because it contained an invalid modification type (%d).

[#log-ref-log-ref-ERR_LDAP_MODIFICATION_DECODE_MOD_TYPE_112]
ID: 112::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modification because the modification type could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFICATION_DECODE_ATTR_113]
ID: 113::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modification because the attribute could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_REQUEST_DECODE_SEQUENCE_114]
ID: 114::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify request protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_REQUEST_DECODE_DN_116]
ID: 116::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify request protocol op because the entry DN could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_MODIFY_REQUEST_DECODE_MODS_117]
ID: 117::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP modify request protocol op because the set of modifications could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_ENTRY_DECODE_SEQUENCE_118]
ID: 118::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search result entry protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_ENTRY_DECODE_DN_120]
ID: 120::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search result entry protocol op because the entry DN could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_ENTRY_DECODE_ATTRS_121]
ID: 121::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search result entry protocol op because the set of attributes could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REFERENCE_DECODE_SEQUENCE_122]
ID: 122::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search result reference protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REFERENCE_DECODE_URLS_123]
ID: 123::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search result reference protocol op because a problem occurred while trying to decode the sequence elements as referral URLs: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_SEQUENCE_124]
ID: 124::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_BASE_126]
ID: 126::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the base DN could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_INVALID_SCOPE_127]
ID: 127::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the provided scope value (%d) is invalid.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_SCOPE_128]
ID: 128::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the scope could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_INVALID_DEREF_129]
ID: 129::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the provided alias dereferencing policy value (%d) is invalid.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_DEREF_130]
ID: 130::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the alias dereferencing policy could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_SIZE_LIMIT_131]
ID: 131::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the size limit could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_TIME_LIMIT_132]
ID: 132::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the time limit could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_TYPES_ONLY_133]
ID: 133::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the typesOnly flag could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_FILTER_134]
ID: 134::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the filter could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_SEARCH_REQUEST_DECODE_ATTRIBUTES_135]
ID: 135::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search request protocol op because the requested attribute set could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_PROTOCOL_OP_DECODE_NULL_136]
ID: 136::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP protocol op because the element was null.

[#log-ref-log-ref-ERR_LDAP_PROTOCOL_OP_DECODE_INVALID_TYPE_137]
ID: 137::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP protocol op because the element had an invalid BER type (%x) for an LDAP protocol op.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_NULL_138]
ID: 138::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element was null.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_INVALID_TYPE_139]
ID: 139::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element had an invalid BER type (%x) for a search filter.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_COMPOUND_COMPONENTS_141]
ID: 141::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because an unexpected error occurred while trying to decode one of the compound filter components: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_NOT_COMPONENT_143]
ID: 143::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the NOT component element could not be decoded as an LDAP filter: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_TV_SEQUENCE_144]
ID: 144::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as a type-and-value sequence: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_TV_TYPE_146]
ID: 146::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the attribute type could not be decoded from the type-and-value sequence: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_TV_VALUE_147]
ID: 147::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the assertion value could not be decoded from the type-and-value sequence: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_SUBSTRING_SEQUENCE_148]
ID: 148::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as a substring sequence: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_SUBSTRING_TYPE_150]
ID: 150::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the attribute type could not be decoded from the substring sequence: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_SUBSTRING_ELEMENTS_151]
ID: 151::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the substring value sequence could not be decoded: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_SUBSTRING_NO_SUBELEMENTS_152]
ID: 152::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the substring value sequence did not contain any elements.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_SUBSTRING_VALUES_154]
ID: 154::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because a problem occurred while trying to parse the substring value elements: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_PRESENCE_TYPE_155]
ID: 155::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as the presence attribute type: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_EXTENSIBLE_SEQUENCE_156]
ID: 156::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because the element could not be decoded as an extensible matching sequence: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_DECODE_EXTENSIBLE_ELEMENTS_158]
ID: 158::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP search filter because a problem occurred while trying to parse the extensible match sequence elements: %s.

[#log-ref-log-ref-ERR_LDAP_CLIENT_SEND_RESPONSE_NO_RESULT_CODE_159]
ID: 159::
Severity: ERROR

+
Message: The server attempted to send a response to the %s operation (conn=%d, op=%d), but the operation did not have a result code. This could indicate that the operation did not complete properly or that it is one that is not allowed to have a response. Using a generic 'Operations Error' response.

[#log-ref-log-ref-ERR_LDAP_CLIENT_SEND_RESPONSE_INVALID_OP_160]
ID: 160::
Severity: ERROR

+
Message: The server attempted to send a response to the %s operation (conn=%d, op=%d), but this type of operation is not allowed to have responses. Backtrace: %s.

[#log-ref-log-ref-ERR_LDAP_CONNHANDLER_OPEN_SELECTOR_FAILED_177]
ID: 177::
Severity: ERROR

+
Message: The LDAP connection handler defined in configuration entry %s was unable to open a selector to allow it to multiplex the associated accept sockets: %s. This connection handler will be disabled.

[#log-ref-log-ref-ERR_LDAP_CONNHANDLER_CREATE_CHANNEL_FAILED_178]
ID: 178::
Severity: ERROR

+
Message: The LDAP connection handler defined in configuration entry %s was unable to create a server socket channel to accept connections on %s:%d: %s. The Directory Server will not listen for new connections on that address.

[#log-ref-log-ref-ERR_LDAP_CONNHANDLER_NO_ACCEPTORS_179]
ID: 179::
Severity: ERROR

+
Message: The LDAP connection handler defined in configuration entry %s was unable to create any of the socket channels on any of the configured addresses. This connection handler will be disabled.

[#log-ref-log-ref-ERR_CONNHANDLER_DENIED_CLIENT_180]
ID: 180::
Severity: ERROR

+
Message: The connection attempt from client %s to %s has been rejected because the client was included in one of the denied address ranges.

[#log-ref-log-ref-ERR_CONNHANDLER_DISALLOWED_CLIENT_181]
ID: 181::
Severity: ERROR

+
Message: The connection attempt from client %s to %s has been rejected because the client was not included in one of the allowed address ranges.

[#log-ref-log-ref-ERR_CONNHANDLER_CANNOT_ACCEPT_CONNECTION_183]
ID: 183::
Severity: ERROR

+
Message: The %s defined in configuration entry %s was unable to accept a new client connection: %s.

[#log-ref-log-ref-ERR_CONNHANDLER_CONSECUTIVE_ACCEPT_FAILURES_184]
ID: 184::
Severity: ERROR

+
Message: The %s defined in configuration entry %s has experienced consecutive failures while trying to accept client connections: %s. This connection handler will be disabled.

[#log-ref-log-ref-ERR_LDAP_CONNHANDLER_UNCAUGHT_ERROR_185]
ID: 185::
Severity: ERROR

+
Message: The LDAP connection handler defined in configuration entry %s caught an unexpected error while trying to listen for new connections: %s. This connection handler will be disabled.

[#log-ref-log-ref-ERR_LDAP_REQHANDLER_OPEN_SELECTOR_FAILED_186]
ID: 186::
Severity: ERROR

+
Message: %s was unable to open a selector to multiplex reads from clients: %s. This request handler cannot continue processing.

[#log-ref-log-ref-ERR_LDAP_REQHANDLER_CANNOT_REGISTER_187]
ID: 187::
Severity: ERROR

+
Message: %s was unable to register this client connection with the selector: %s.

[#log-ref-log-ref-ERR_LDAP_REQHANDLER_REJECT_DUE_TO_SHUTDOWN_188]
ID: 188::
Severity: ERROR

+
Message: This connection could not be registered with a request handler because the Directory Server is shutting down.

[#log-ref-log-ref-ERR_LDAP_REQHANDLER_DEREGISTER_DUE_TO_SHUTDOWN_190]
ID: 190::
Severity: ERROR

+
Message: This client connection is being deregistered from the associated request handler because the Directory Server is shutting down.

[#log-ref-log-ref-ERR_LDAP_FILTER_STRING_NULL_192]
ID: 192::
Severity: ERROR

+
Message: Cannot decode the provided string as an LDAP search filter because the string was null.

[#log-ref-log-ref-ERR_LDAP_FILTER_UNCAUGHT_EXCEPTION_193]
ID: 193::
Severity: ERROR

+
Message: Cannot decode the provided string %s as an LDAP search filter because an unexpected exception was thrown during processing: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_MISMATCHED_PARENTHESES_194]
ID: 194::
Severity: ERROR

+
Message: The provided search filter "%s" had mismatched parentheses around the portion between positions %d and %d.

[#log-ref-log-ref-ERR_LDAP_FILTER_NO_EQUAL_SIGN_195]
ID: 195::
Severity: ERROR

+
Message: The provided search filter "%s" was missing an equal sign in the suspected simple filter component between positions %d and %d.

[#log-ref-log-ref-ERR_LDAP_FILTER_INVALID_ESCAPED_BYTE_196]
ID: 196::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_LDAP_FILTER_COMPOUND_MISSING_PARENTHESES_197]
ID: 197::
Severity: ERROR

+
Message: 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 might be parentheses for different filter components).

[#log-ref-log-ref-ERR_LDAP_FILTER_NO_CORRESPONDING_OPEN_PARENTHESIS_198]
ID: 198::
Severity: ERROR

+
Message: The provided search filter "%s" could not be decoded because the closing parenthesis at position %d did not have a corresponding open parenthesis.

[#log-ref-log-ref-ERR_LDAP_FILTER_NO_CORRESPONDING_CLOSE_PARENTHESIS_199]
ID: 199::
Severity: ERROR

+
Message: The provided search filter "%s" could not be decoded because the opening parenthesis at position %d did not have a corresponding close parenthesis.

[#log-ref-log-ref-ERR_LDAP_FILTER_SUBSTRING_NO_ASTERISKS_200]
ID: 200::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_COLON_201]
ID: 201::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_LDAP_DISCONNECT_DUE_TO_INVALID_REQUEST_TYPE_202]
ID: 202::
Severity: ERROR

+
Message: Terminating this connection because the client sent an invalid message of type %s (LDAP message ID %d) that is not allowed for request messages.

[#log-ref-log-ref-ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE_203]
ID: 203::
Severity: ERROR

+
Message: An unexpected failure occurred while trying to process a request of type %s (LDAP message ID %d): %s. The client connection will be terminated.

[#log-ref-log-ref-ERR_LDAP_INVALID_BIND_AUTH_TYPE_204]
ID: 204::
Severity: ERROR

+
Message: The bind request message (LDAP message ID %d) included an invalid authentication type of %s. This is a protocol error, and this connection will be terminated as per RFC 2251 section 4.2.3.

[#log-ref-log-ref-ERR_LDAP_DISCONNECT_DUE_TO_BIND_PROTOCOL_ERROR_205]
ID: 205::
Severity: ERROR

+
Message: This client connection is being terminated because a protocol error occurred while trying to process a bind request. The LDAP message ID was %d and the error message for the bind response was %s.

[#log-ref-log-ref-ERR_LDAPV2_SKIPPING_EXTENDED_RESPONSE_206]
ID: 206::
Severity: ERROR

+
Message: An extended response message would have been sent to an LDAPv2 client (connection ID=%d, operation ID=%d): %s. LDAPv2 does not allow extended operations, so this response will not be sent.

[#log-ref-log-ref-ERR_LDAPV2_SKIPPING_SEARCH_REFERENCE_207]
ID: 207::
Severity: ERROR

+
Message: A search performed by an LDAPv2 client (connection ID=%d, operation ID=%d) would have included a search result reference %s. Referrals are not allowed for LDAPv2 clients, so this search reference will not be sent.

[#log-ref-log-ref-ERR_LDAPV2_REFERRAL_RESULT_CHANGED_208]
ID: 208::
Severity: ERROR

+
Message: The original result code for this message was 10 but this result is not allowed for LDAPv2 clients.

[#log-ref-log-ref-ERR_LDAPV2_REFERRALS_OMITTED_209]
ID: 209::
Severity: ERROR

+
Message: The response included one or more referrals, which are not allowed for LDAPv2 clients. The referrals included were: %s.

[#log-ref-log-ref-ERR_LDAPV2_CLIENTS_NOT_ALLOWED_210]
ID: 210::
Severity: ERROR

+
Message: The Directory Server has been configured to deny access to LDAPv2 clients. This connection will be closed.

[#log-ref-log-ref-ERR_LDAPV2_EXTENDED_REQUEST_NOT_ALLOWED_211]
ID: 211::
Severity: ERROR

+
Message: The client with connection ID %d authenticated to the Directory Server using LDAPv2, but attempted to send an extended operation request (LDAP message ID %d), which is not allowed for LDAPv2 clients. The connection will be terminated.

[#log-ref-log-ref-ERR_LDAP_STATS_INVALID_MONITOR_INITIALIZATION_212]
ID: 212::
Severity: ERROR

+
Message: An attempt was made to initialize the LDAP statistics monitor provider as defined in configuration entry %s. This monitor provider should only be dynamically created within the Directory Server itself and not from within the configuration.

[#log-ref-log-ref-ERR_LDAP_REQHANDLER_UNEXPECTED_SELECT_EXCEPTION_213]
ID: 213::
Severity: ERROR

+
Message: The LDAP request handler thread "%s" encountered an unexpected error that would have caused the thread to die: %s. The error has been caught and the request handler should continue operating as normal.

[#log-ref-log-ref-ERR_CONNHANDLER_REJECTED_BY_SERVER_214]
ID: 214::
Severity: ERROR

+
Message: The attempt to register this connection with the Directory Server was rejected. This might indicate that the server already has the maximum allowed number of concurrent connections established, or that it is in a restricted access mode.

[#log-ref-log-ref-ERR_INTERNAL_CANNOT_DECODE_DN_264]
ID: 264::
Severity: ERROR

+
Message: An unexpected error occurred while trying to decode the DN %s used for internal operations as a root user: %s.

[#log-ref-log-ref-ERR_LDAP_TLS_EXISTING_SECURITY_PROVIDER_271]
ID: 271::
Severity: ERROR

+
Message: The TLS connection security provider cannot be enabled on this client connection because it is already using the %s provider. StartTLS can only be used on clear-text connections.

[#log-ref-log-ref-ERR_LDAP_TLS_STARTTLS_NOT_ALLOWED_272]
ID: 272::
Severity: ERROR

+
Message: StartTLS cannot be enabled on this LDAP client connection because the corresponding LDAP connection handler is configured to reject StartTLS requests. The use of StartTLS can be enabled using the ds-cfg-allow-start-tls configuration attribute.

[#log-ref-log-ref-ERR_LDAP_TLS_CANNOT_CREATE_TLS_PROVIDER_273]
ID: 273::
Severity: ERROR

+
Message: An error occurred while attempting to create a TLS connection security provider for this client connection for use with StartTLS: %s.

[#log-ref-log-ref-ERR_LDAP_PAGED_RESULTS_DECODE_NULL_278]
ID: 278::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the element is null.

[#log-ref-log-ref-ERR_LDAP_PAGED_RESULTS_DECODE_SEQUENCE_279]
ID: 279::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_PAGED_RESULTS_DECODE_SIZE_281]
ID: 281::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the size element could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAP_PAGED_RESULTS_DECODE_COOKIE_282]
ID: 282::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP paged results control value because the cookie could not be properly decoded: %s.

[#log-ref-log-ref-ERR_LDAPASSERT_NO_CONTROL_VALUE_283]
ID: 283::
Severity: ERROR

+
Message: Cannot decode the provided LDAP assertion control because the control does not have a value.

[#log-ref-log-ref-ERR_PREREADREQ_NO_CONTROL_VALUE_285]
ID: 285::
Severity: ERROR

+
Message: Cannot decode the provided LDAP pre-read request control because the control does not have a value.

[#log-ref-log-ref-ERR_PREREADREQ_CANNOT_DECODE_VALUE_286]
ID: 286::
Severity: ERROR

+
Message: Cannot decode the provided LDAP pre-read request control because an error occurred while trying to decode the control value: %s.

[#log-ref-log-ref-ERR_POSTREADREQ_NO_CONTROL_VALUE_287]
ID: 287::
Severity: ERROR

+
Message: Cannot decode the provided LDAP post-read request control because the control does not have a value.

[#log-ref-log-ref-ERR_POSTREADREQ_CANNOT_DECODE_VALUE_288]
ID: 288::
Severity: ERROR

+
Message: Cannot decode the provided LDAP post-read request control because an error occurred while trying to decode the control value: %s.

[#log-ref-log-ref-ERR_PREREADRESP_NO_CONTROL_VALUE_289]
ID: 289::
Severity: ERROR

+
Message: Cannot decode the provided LDAP pre-read response control because the control does not have a value.

[#log-ref-log-ref-ERR_PREREADRESP_CANNOT_DECODE_VALUE_290]
ID: 290::
Severity: ERROR

+
Message: Cannot decode the provided LDAP pre-read response control because an error occurred while trying to decode the control value: %s.

[#log-ref-log-ref-ERR_POSTREADRESP_NO_CONTROL_VALUE_291]
ID: 291::
Severity: ERROR

+
Message: Cannot decode the provided LDAP post-read response control because the control does not have a value.

[#log-ref-log-ref-ERR_POSTREADRESP_CANNOT_DECODE_VALUE_292]
ID: 292::
Severity: ERROR

+
Message: Cannot decode the provided LDAP post-read response control because an error occurred while trying to decode the control value: %s.

[#log-ref-log-ref-ERR_PROXYAUTH1_NO_CONTROL_VALUE_293]
ID: 293::
Severity: ERROR

+
Message: Cannot decode the provided proxied authorization V1 control because it does not have a value.

[#log-ref-log-ref-ERR_PROXYAUTH1_CANNOT_DECODE_VALUE_295]
ID: 295::
Severity: ERROR

+
Message: Cannot decode the provided proxied authorization V1 control because an error occurred while attempting to decode the control value: %s.

[#log-ref-log-ref-ERR_PROXYAUTH1_NO_SUCH_USER_296]
ID: 296::
Severity: ERROR

+
Message: User %s specified in the proxied authorization V1 control does not exist in the Directory Server.

[#log-ref-log-ref-ERR_PROXYAUTH2_NO_CONTROL_VALUE_297]
ID: 297::
Severity: ERROR

+
Message: Cannot decode the provided proxied authorization V2 control because it does not have a value.

[#log-ref-log-ref-ERR_PROXYAUTH2_NO_IDENTITY_MAPPER_299]
ID: 299::
Severity: ERROR

+
Message: Unable to process proxied authorization V2 control because it contains an authorization ID based on a username and no proxied authorization identity mapper is configured in the Directory Server.

[#log-ref-log-ref-ERR_PROXYAUTH2_INVALID_AUTHZID_300]
ID: 300::
Severity: ERROR

+
Message: The authorization ID "%s" contained in the proxied authorization V2 control is invalid because it does not start with "dn:" to indicate a user DN or "u:" to indicate a username.

[#log-ref-log-ref-ERR_PROXYAUTH2_NO_SUCH_USER_301]
ID: 301::
Severity: ERROR

+
Message: User %s specified in the proxied authorization V2 control does not exist in the Directory Server.

[#log-ref-log-ref-ERR_PSEARCH_CHANGETYPES_INVALID_TYPE_302]
ID: 302::
Severity: ERROR

+
Message: The provided integer value %d does not correspond to any persistent search change type.

[#log-ref-log-ref-ERR_PSEARCH_CHANGETYPES_NO_TYPES_303]
ID: 303::
Severity: ERROR

+
Message: The provided integer value indicated that there were no persistent search change types, which is not allowed.

[#log-ref-log-ref-ERR_PSEARCH_CHANGETYPES_INVALID_TYPES_304]
ID: 304::
Severity: ERROR

+
Message: The provided integer value %d was outside the range of acceptable values for an encoded change type set.

[#log-ref-log-ref-ERR_PSEARCH_NO_CONTROL_VALUE_305]
ID: 305::
Severity: ERROR

+
Message: Cannot decode the provided persistent search control because it does not have a value.

[#log-ref-log-ref-ERR_PSEARCH_CANNOT_DECODE_VALUE_307]
ID: 307::
Severity: ERROR

+
Message: Cannot decode the provided persistent search control because an error occurred while attempting to decode the control value: %s.

[#log-ref-log-ref-ERR_ECN_NO_CONTROL_VALUE_308]
ID: 308::
Severity: ERROR

+
Message: Cannot decode the provided entry change notification control because it does not have a value.

[#log-ref-log-ref-ERR_ECN_ILLEGAL_PREVIOUS_DN_310]
ID: 310::
Severity: ERROR

+
Message: Cannot decode the provided entry change notification control because it contains a previous DN element but had a change type of %s. The previous DN element can only be provided with the modify DN change type.

[#log-ref-log-ref-ERR_ECN_CANNOT_DECODE_VALUE_312]
ID: 312::
Severity: ERROR

+
Message: Cannot decode the provided entry change notification control because an error occurred while attempting to decode the control value: %s.

[#log-ref-log-ref-ERR_AUTHZIDRESP_NO_CONTROL_VALUE_313]
ID: 313::
Severity: ERROR

+
Message: Cannot decode the provided authorization identity response control because it does not have a value.

[#log-ref-log-ref-ERR_LDAP_INTERMEDIATE_RESPONSE_DECODE_SEQUENCE_314]
ID: 314::
Severity: ERROR

+
Message: Cannot decode the provided ASN.1 element as an LDAP intermediate response protocol op because the element could not be decoded as a sequence: %s.

[#log-ref-log-ref-ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_OID_316]
ID: 316::
Severity: ERROR

+
Message: An error occurred while attempting to decode the intermediate response OID: %s.

[#log-ref-log-ref-ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_VALUE_317]
ID: 317::
Severity: ERROR

+
Message: An error occurred while attempting to decode the intermediate response value: %s.

[#log-ref-log-ref-ERR_MVFILTER_INVALID_LDAP_FILTER_TYPE_321]
ID: 321::
Severity: ERROR

+
Message: The provided LDAP filter "%s" cannot be used as a matched values filter because filters of type %s are not allowed for use in matched values filters.

[#log-ref-log-ref-ERR_MVFILTER_INVALID_DN_ATTRIBUTES_FLAG_322]
ID: 322::
Severity: ERROR

+
Message: The provided LDAP filter "%s" cannot be used as a matched values filter because it is an extensible match filter that contains the dnAttributes flag, which is not allowed for matched values filters.

[#log-ref-log-ref-ERR_MVFILTER_CANNOT_DECODE_AVA_324]
ID: 324::
Severity: ERROR

+
Message: An error occurred while attempting to decode the attribute value assertion in the provided matched values filter: %s.

[#log-ref-log-ref-ERR_MVFILTER_NO_SUBSTRING_ELEMENTS_326]
ID: 326::
Severity: ERROR

+
Message: The provided matched values filter could not be decoded because there were no subInitial, subAny, or subFinal components in the substring filter.

[#log-ref-log-ref-ERR_MVFILTER_CANNOT_DECODE_SUBSTRINGS_330]
ID: 330::
Severity: ERROR

+
Message: The provided matched values filter could not be decoded because an error occurred while decoding the substring filter component: %s.

[#log-ref-log-ref-ERR_MVFILTER_CANNOT_DECODE_PRESENT_TYPE_331]
ID: 331::
Severity: ERROR

+
Message: The provided matched values filter could not be decoded because an error occurred while decoding the presence filter component: %s.

[#log-ref-log-ref-ERR_MVFILTER_CANNOT_DECODE_EXTENSIBLE_MATCH_337]
ID: 337::
Severity: ERROR

+
Message: The provided matched values filter could not be decoded because an error occurred while decoding the extensible match filter component: %s.

[#log-ref-log-ref-ERR_MVFILTER_INVALID_ELEMENT_TYPE_338]
ID: 338::
Severity: ERROR

+
Message: The provided matched values filter could not be decoded because it had an invalid BER type of %s.

[#log-ref-log-ref-ERR_MATCHEDVALUES_NO_CONTROL_VALUE_339]
ID: 339::
Severity: ERROR

+
Message: Cannot decode the provided matched values control because it does not have a value.

[#log-ref-log-ref-ERR_MATCHEDVALUES_CANNOT_DECODE_VALUE_AS_SEQUENCE_340]
ID: 340::
Severity: ERROR

+
Message: Cannot decode the provided matched values control because an error occurred while attempting to decode the value as an ASN.1 sequence: %s.

[#log-ref-log-ref-ERR_MATCHEDVALUES_NO_FILTERS_341]
ID: 341::
Severity: ERROR

+
Message: Cannot decode the provided matched values control because the control value does not specify any filters for use in matching attribute values.

[#log-ref-log-ref-ERR_PWEXPIRED_CONTROL_INVALID_VALUE_342]
ID: 342::
Severity: ERROR

+
Message: Cannot decode the provided control as a password expired control because the provided control had a value that could not be parsed as an integer.

[#log-ref-log-ref-ERR_PWEXPIRING_NO_CONTROL_VALUE_343]
ID: 343::
Severity: ERROR

+
Message: Cannot decode the provided password expiring control because it does not have a value.

[#log-ref-log-ref-ERR_PWEXPIRING_CANNOT_DECODE_SECONDS_UNTIL_EXPIRATION_344]
ID: 344::
Severity: ERROR

+
Message: Cannot decode the provided control as a password expiring control because an error occurred while attempting to decode the number of seconds until expiration: %s.

[#log-ref-log-ref-ERR_PWPOLICYREQ_CONTROL_HAS_VALUE_354]
ID: 354::
Severity: ERROR

+
Message: Cannot decode the provided control as a password policy request control because the provided control had a value but the password policy request control should not have a value.

[#log-ref-log-ref-ERR_PWPOLICYRES_NO_CONTROL_VALUE_355]
ID: 355::
Severity: ERROR

+
Message: Cannot decode the provided password policy response control because it does not have a value.

[#log-ref-log-ref-ERR_PWPOLICYRES_INVALID_WARNING_TYPE_356]
ID: 356::
Severity: ERROR

+
Message: Cannot decode the provided password policy response control because the warning element has an invalid type of %s.

[#log-ref-log-ref-ERR_PWPOLICYRES_INVALID_ERROR_TYPE_357]
ID: 357::
Severity: ERROR

+
Message: Cannot decode the provided password policy response control because the error element has an invalid type of %d.

[#log-ref-log-ref-ERR_PWPOLICYRES_DECODE_ERROR_359]
ID: 359::
Severity: ERROR

+
Message: Cannot decode the provided password policy response control: %s.

[#log-ref-log-ref-ERR_PROXYAUTH1_UNUSABLE_ACCOUNT_372]
ID: 372::
Severity: ERROR

+
Message: Use of the proxied authorization V1 control for user %s is not allowed by the password policy configuration.

[#log-ref-log-ref-ERR_ACCTUSABLEREQ_CONTROL_HAS_VALUE_375]
ID: 375::
Severity: ERROR

+
Message: Cannot decode the provided control as an account availability request control because the provided control had a value but the account availability request control should not have a value.

[#log-ref-log-ref-ERR_ACCTUSABLERES_NO_CONTROL_VALUE_376]
ID: 376::
Severity: ERROR

+
Message: Cannot decode the provided account availability response control because it does not have a value.

[#log-ref-log-ref-ERR_ACCTUSABLERES_UNKNOWN_VALUE_ELEMENT_TYPE_378]
ID: 378::
Severity: ERROR

+
Message: The account availability response control had an unknown ACCOUNT_USABLE_RESPONSE element type of %s.

[#log-ref-log-ref-ERR_ACCTUSABLERES_DECODE_ERROR_379]
ID: 379::
Severity: ERROR

+
Message: Cannot decode the provided account availability response control: %s.

[#log-ref-log-ref-ERR_LDAP_ATTRIBUTE_DUPLICATE_VALUES_384]
ID: 384::
Severity: ERROR

+
Message: The provided LDAP attribute %s contains duplicate values.

[#log-ref-log-ref-ERR_LDAP_FILTER_UNKNOWN_MATCHING_RULE_385]
ID: 385::
Severity: ERROR

+
Message: The provided LDAP search filter references unknown matching rule %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_VALUE_WITH_NO_ATTR_OR_MR_386]
ID: 386::
Severity: ERROR

+
Message: The provided LDAP search filter has an assertion value but does not include either an attribute type or a matching rule ID.

[#log-ref-log-ref-ERR_LDAP_REQHANDLER_DETECTED_JVM_ISSUE_CR6322825_387]
ID: 387::
Severity: ERROR

+
Message: Unable to call select() in the LDAP connection handler: %s. It appears that your JVM may be susceptible to the issue described at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable to handle LDAP requests in its current configuration. Please upgrade to a newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) or set the number of available file descriptors to a value greater than or equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting the Directory Server.

[#log-ref-log-ref-ERR_PROXYAUTH1_CONTROL_NOT_CRITICAL_388]
ID: 388::
Severity: ERROR

+
Message: Unwilling to process the request because it contains a proxied authorization V1 control which is not marked critical. The proxied authorization control must always have a criticality of "true".

[#log-ref-log-ref-ERR_PROXYAUTH2_CONTROL_NOT_CRITICAL_389]
ID: 389::
Severity: ERROR

+
Message: Unwilling to process the request because it contains a proxied authorization V2 control which is not marked critical. The proxied authorization control must always have a criticality of "true".

[#log-ref-log-ref-ERR_LDAP_FILTER_NOT_EXACTLY_ONE_405]
ID: 405::
Severity: ERROR

+
Message: 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.

[#log-ref-log-ref-ERR_LDAP_FILTER_ENCLOSED_IN_APOSTROPHES_427]
ID: 427::
Severity: ERROR

+
Message: An LDAP filter enclosed in apostrophes is invalid: %s.

[#log-ref-log-ref-ERR_LDAP_FILTER_INVALID_CHAR_IN_ATTR_TYPE_429]
ID: 429::
Severity: ERROR

+
Message: The provided search filter contains an invalid attribute type '%s' with invalid character '%s' at position %d.

[#log-ref-log-ref-ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_AD_OR_MR_430]
ID: 430::
Severity: ERROR

+
Message: The provided search filter "%s" could not be decoded because the extensible match component starting at position %d did not include either an attribute description or a matching rule ID. At least one of them must be provided.

[#log-ref-log-ref-ERR_LDAPV2_CONTROLS_NOT_ALLOWED_431]
ID: 431::
Severity: ERROR

+
Message: LDAPv2 clients are not allowed to use request controls.

[#log-ref-log-ref-ERR_CONNHANDLER_CANNOT_BIND_432]
ID: 432::
Severity: ERROR

+
Message: The %s connection handler defined in configuration entry %s was unable to bind to %s:%d: %s.

[#log-ref-log-ref-ERR_JMX_SEARCH_INSUFFICIENT_PRIVILEGES_438]
ID: 438::
Severity: ERROR

+
Message: You do not have sufficient privileges to perform search operations through JMX.

[#log-ref-log-ref-ERR_JMX_INSUFFICIENT_PRIVILEGES_439]
ID: 439::
Severity: ERROR

+
Message: You do not have sufficient privileges to establish the connection through JMX. At least JMX_READ privilege is required.

[#log-ref-log-ref-ERR_INTERNALCONN_NO_SUCH_USER_440]
ID: 440::
Severity: ERROR

+
Message: User %s does not exist in the directory.

[#log-ref-log-ref-ERR_INTERNALOS_CLOSED_441]
ID: 441::
Severity: ERROR

+
Message: This output stream has been closed.

[#log-ref-log-ref-ERR_INTERNALOS_INVALID_REQUEST_442]
ID: 442::
Severity: ERROR

+
Message: The provided LDAP message had an invalid operation type (%s) for a request.

[#log-ref-log-ref-ERR_INTERNALOS_SASL_BIND_NOT_SUPPORTED_443]
ID: 443::
Severity: ERROR

+
Message: SASL bind operations are not supported over internal LDAP sockets.

[#log-ref-log-ref-ERR_INTERNALOS_STARTTLS_NOT_SUPPORTED_444]
ID: 444::
Severity: ERROR

+
Message: StartTLS operations are not supported over internal LDAP sockets.

[#log-ref-log-ref-ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_NONFATAL_447]
ID: 447::
Severity: ERROR

+
Message: An error occurred while trying to read a change record from the LDIF file: %s. This change will be skipped but processing on the LDIF file will continue.

[#log-ref-log-ref-ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_FATAL_448]
ID: 448::
Severity: ERROR

+
Message: An error occurred while trying to read a change record from the LDIF file: %s. No further processing on this LDIF file can be performed.

[#log-ref-log-ref-ERR_LDIF_CONNHANDLER_IO_ERROR_454]
ID: 454::
Severity: ERROR

+
Message: An I/O error occurred while the LDIF connection handler was processing LDIF file %s: %s.

[#log-ref-log-ref-ERR_LDIF_CONNHANDLER_CANNOT_RENAME_455]
ID: 455::
Severity: ERROR

+
Message: An error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %s.

[#log-ref-log-ref-ERR_LDIF_CONNHANDLER_CANNOT_DELETE_456]
ID: 456::
Severity: ERROR

+
Message: An error occurred while the LDIF connection handler was attempting to delete processed file %s: %s.

[#log-ref-log-ref-ERR_CONNHANDLER_ADDRESS_INUSE_457]
ID: 457::
Severity: ERROR

+
Message: Address already in use.

[#log-ref-log-ref-ERR_SUBENTRIES_NO_CONTROL_VALUE_458]
ID: 458::
Severity: ERROR

+
Message: Cannot decode the provided subentries control because it does not have a value.

[#log-ref-log-ref-ERR_SUBENTRIES_CANNOT_DECODE_VALUE_459]
ID: 459::
Severity: ERROR

+
Message: Cannot decode the provided subentries control because an error occurred while attempting to decode the control value: %s.

[#log-ref-log-ref-ERR_SNMP_CONNHANDLER_NO_CONFIGURATION_1462]
ID: 1462::
Severity: ERROR

+
Message: No Configuration was defined for this connection handler. The configuration parameters ds-cfg-listen-port and ds-cfg-trap-port are required by the connection handler to start.

[#log-ref-log-ref-ERR_SNMP_CONNHANDLER_TRAPS_DESTINATION_1463]
ID: 1463::
Severity: ERROR

+
Message: Traps Destination %s is an unknown host. Traps will not be sent to this destination.

[#log-ref-log-ref-ERR_SNMP_CONNHANDLER_NO_OPENDMK_JARFILES_1464]
ID: 1464::
Severity: ERROR

+
Message: You do not have the appropriate OpenDMK jar files to enable the SNMP Connection Handler. Please go under http://opendmk.dev.java.net and set the opendmk-jarfile configuration parameter to set the full path of the required jdmkrt.jar file. The SNMP connection Handler didn't started.

[#log-ref-log-ref-ERR_SNMP_CONNHANDLER_BAD_CONFIGURATION_1465]
ID: 1465::
Severity: ERROR

+
Message: Cannot initialize the SNMP Connection Handler. Please check the configuration attributes.

[#log-ref-log-ref-ERR_SNMP_CONNHANDLER_NO_VALID_TRAP_DESTINATIONS_1466]
ID: 1466::
Severity: ERROR

+
Message: No valid trap destinations has been found. No trap will be sent.

[#log-ref-log-ref-ERR_SUBTREE_DELETE_INVALID_CONTROL_VALUE_1503]
ID: 1503::
Severity: ERROR

+
Message: Cannot decode the provided subtree delete control because it contains a value.

[#log-ref-log-ref-ERR_CONNHANDLER_SSL_CANNOT_INITIALIZE_1504]
ID: 1504::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the SSL context for use in the LDAP Connection Handler: %s.

[#log-ref-log-ref-ERR_LDAP_UNSUPPORTED_PROTOCOL_VERSION_1505]
ID: 1505::
Severity: ERROR

+
Message: The Directory Server does not support LDAP protocol version %d. This connection will be closed.

[#log-ref-log-ref-ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_DOES_NOT_EXIST_1506]
ID: 1506::
Severity: ERROR

+
Message: The specified OpenDMK jar file '%s' could not be found. Verify that the value set in the opendmk-jarfile configuration parameter of the SNMP connection handler is the valid path to the jdmkrt.jar file and that the file is accessible.

[#log-ref-log-ref-ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_NOT_OPERATIONAL_1507]
ID: 1507::
Severity: ERROR

+
Message: The required classes could not be loaded using jar file '%s'. Verify that the jar file is not corrupted.

[#log-ref-log-ref-ERR_HTTP_ERROR_WHILE_PROCESSING_REQUEST_1508]
ID: 1508::
Severity: ERROR

+
Message: Cannot decode the provided control %s because an error occurred while attempting to decode the control value: %s.

[#log-ref-log-ref-ERR_ECLN_NO_CONTROL_VALUE_1509]
ID: 1509::
Severity: ERROR

+
Message: Cannot decode the provided entry changelog notification control because it does not have a value.

[#log-ref-log-ref-ERR_ECLN_CANNOT_DECODE_VALUE_1510]
ID: 1510::
Severity: ERROR

+
Message: Cannot decode the provided entry changelog notification control because an error occurred while attempting to decode the control value: %s.

[#log-ref-log-ref-ERR_UNEXPECTED_CONNECTION_CLOSURE_1511]
ID: 1511::
Severity: ERROR

+
Message: The connection to the Directory Server was closed while waiting for a response.

[#log-ref-log-ref-ERR_LDAP_CLIENT_IO_ERROR_DURING_READ_1513]
ID: 1513::
Severity: ERROR

+
Message: An IO error occurred while reading a request from the client: %s.

[#log-ref-log-ref-ERR_LDAP_CLIENT_IO_ERROR_BEFORE_READ_1514]
ID: 1514::
Severity: ERROR

+
Message: Connection reset by client.

[#log-ref-log-ref-ERR_CONNHANDLER_CONFIG_CHANGES_REQUIRE_RESTART_1516]
ID: 1516::
Severity: ERROR

+
Message: The server received configuration changes that require a restart of the %s connection handler to take effect.

[#log-ref-log-ref-ERR_GSER_PATTERN_NO_MATCH_1517]
ID: 1517::
Severity: ERROR

+
Message: The GSER value does not contain a String matching the pattern %s at the current position: %s.

[#log-ref-log-ref-ERR_GSER_NO_VALID_SEPARATOR_1518]
ID: 1518::
Severity: ERROR

+
Message: The GSER value does not contain a separator at the current position: %s.

[#log-ref-log-ref-ERR_GSER_NO_VALID_STRING_1519]
ID: 1519::
Severity: ERROR

+
Message: The GSER value does not contain a valid String value at the current position: %s.

[#log-ref-log-ref-ERR_GSER_NO_VALID_INTEGER_1520]
ID: 1520::
Severity: ERROR

+
Message: The GSER value does not contain a valid integer value at the current position: %s.

[#log-ref-log-ref-ERR_GSER_NO_VALID_IDENTIFIER_1521]
ID: 1521::
Severity: ERROR

+
Message: The GSER value does not contain a valid identifier at the current position: %s.

[#log-ref-log-ref-ERR_GSER_SPACE_CHAR_EXPECTED_1522]
ID: 1522::
Severity: ERROR

+
Message: The GSER value does not contain a whitespace character at the current position: %s.

[#log-ref-log-ref-ERR_GSER_NO_VALID_IDENTIFIEDCHOICE_1523]
ID: 1523::
Severity: ERROR

+
Message: The GSER value does not contain a valid IdentifiedChoiceValue at the current position: %s.

[#log-ref-log-ref-ERR_NULL_KEY_PROVIDER_MANAGER_1524]
ID: 1524::
Severity: ERROR

+
Message: The keystore %s seems to be missing, this may render the secure port inoperative for '%s'. Verify the keystore setting in the configuration.

[#log-ref-log-ref-ERR_PROXYAUTH_AUTHZ_NOT_PERMITTED_1525]
ID: 1525::
Severity: ERROR

+
Message: Authorization as '%s' specified in the proxied authorization control is not permitted.

[#log-ref-log-ref-ERR_KEYSTORE_DOES_NOT_CONTAIN_ALIAS_1526]
ID: 1526::
Severity: ERROR

+
Message: The key with alias '%s' was not found for '%s'. Verify that the keystore is properly configured.

[#log-ref-log-ref-ERR_INVALID_KEYSTORE_1527]
ID: 1527::
Severity: ERROR

+
Message: No usable key was found for '%s'. Verify the keystore content.

[#log-ref-log-ref-ERR_INITIALIZE_HTTP_CONNECTION_HANDLER_1529]
ID: 1529::
Severity: ERROR

+
Message: Failed to initialize Http Connection Handler.

[#log-ref-log-ref-ERR_TRANSACTION_ID_CONTROL_HAS_NO_VALUE_1530]
ID: 1530::
Severity: ERROR

+
Message: No value was provided for the transaction id control, whereas an UTF-8 encoded value is expected.

[#log-ref-log-ref-ERR_UNEXPECTED_EXCEPTION_ON_CLIENT_CONNECTION_1531]
ID: 1531::
Severity: ERROR

+
Message: Exception on the underlying client connection: %s.

[#log-ref-log-ref-ERR_IO_ERROR_ON_CLIENT_CONNECTION_1532]
ID: 1532::
Severity: ERROR

+
Message: The underlying client connection timed out or closed: %s.

[#log-ref-log-ref-ERR_PROXYAUTH2_ACCOUNT_DISABLED_1533]
ID: 1533::
Severity: ERROR

+
Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is disabled.

[#log-ref-log-ref-ERR_PROXYAUTH2_ACCOUNT_EXPIRED_1534]
ID: 1534::
Severity: ERROR

+
Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is expired.

[#log-ref-log-ref-ERR_PROXYAUTH2_ACCOUNT_LOCKED_1535]
ID: 1535::
Severity: ERROR

+
Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is locked.

[#log-ref-log-ref-ERR_PROXYAUTH2_PASSWORD_EXPIRED_1536]
ID: 1536::
Severity: ERROR

+
Message: Use of the proxied authorization V2 control for user %s is not allowed: the account's password is expired.

--


[#QUICKSETUP]
=== Log Message Category: QUICKSETUP

--

[#log-ref-log-ref-ERR_ADS]
ID: N/A::
Severity: ERROR

+
Message: The registration information of server %s and server %s could not be merged. Reasons:%n%s.

--


[#REPLICATION]
=== Log Message Category: REPLICATION

--

[#log-ref-log-ref-ERR_SYNC_INVALID_DN_1]
ID: 1::
Severity: ERROR

+
Message: The configured DN is already used by another domain.

[#log-ref-log-ref-ERR_UNKNOWN_HOSTNAME_5]
ID: 5::
Severity: ERROR

+
Message: Replication Server failed to start because the hostname is unknown.

[#log-ref-log-ref-ERR_COULD_NOT_BIND_CHANGELOG_6]
ID: 6::
Severity: ERROR

+
Message: Replication Server failed to start : could not bind to the listen port : %d. Error : %s.

[#log-ref-log-ref-ERR_UNKNOWN_TYPE_7]
ID: 7::
Severity: ERROR

+
Message: Unknown operation type : %s.

[#log-ref-log-ref-ERR_OPERATION_NOT_FOUND_IN_PENDING_9]
ID: 9::
Severity: ERROR

+
Message: Internal Error : Operation %s change number %s was not found in pending list.

[#log-ref-log-ref-ERR_COULD_NOT_READ_DB_11]
ID: 11::
Severity: ERROR

+
Message: The replication server failed to start because the database %s could not be read : %s.

[#log-ref-log-ref-ERR_EXCEPTION_REPLAYING_OPERATION_12]
ID: 12::
Severity: ERROR

+
Message: An Exception was caught while replaying operation %s : %s.

[#log-ref-log-ref-ERR_ERROR_SEARCHING_RUV_15]
ID: 15::
Severity: ERROR

+
Message: Error %s when searching for server state %s : %s base dn : %s.

[#log-ref-log-ref-ERR_EXCEPTION_SENDING_TOPO_INFO_20]
ID: 20::
Severity: ERROR

+
Message: Caught IOException while sending topology info (for update) on domain %s for %s server %s : %s.

[#log-ref-log-ref-ERR_CANNOT_RECOVER_CHANGES_21]
ID: 21::
Severity: ERROR

+
Message: Error when searching old changes from the database for base DN %s.

[#log-ref-log-ref-ERR_EXCEPTION_DECODING_OPERATION_25]
ID: 25::
Severity: ERROR

+
Message: Error trying to replay %s, operation could not be decoded :.

[#log-ref-log-ref-ERR_CHANGELOG_SHUTDOWN_DATABASE_ERROR_26]
ID: 26::
Severity: ERROR

+
Message: Error trying to use the underlying database. The Replication Server is going to shut down: %s.

[#log-ref-log-ref-ERR_EXCEPTION_CHANGELOG_TRIM_FLUSH_29]
ID: 29::
Severity: ERROR

+
Message: Error during the Replication Server database trimming or flush process. The Changelog service is going to shutdown: %s.

[#log-ref-log-ref-ERR_WRITER_UNEXPECTED_EXCEPTION_32]
ID: 32::
Severity: ERROR

+
Message: An unexpected error happened handling connection with %s. This connection is going to be closed.

[#log-ref-log-ref-ERR_RS_ERROR_SENDING_ACK_33]
ID: 33::
Severity: ERROR

+
Message: In replication server %s: an unexpected error occurred while sending an ack to server id %s for change number %s in domain %s . This connection is going to be closed and reopened.

[#log-ref-log-ref-ERR_LOOP_REPLAYING_OPERATION_35]
ID: 35::
Severity: ERROR

+
Message: A loop was detected while replaying operation: %s error %s.

[#log-ref-log-ref-ERR_FILE_CHECK_CREATE_FAILED_36]
ID: 36::
Severity: ERROR

+
Message: An Exception was caught while testing existence or trying to create the directory for the Replication Server database : %s.

[#log-ref-log-ref-ERR_SIMULTANEOUS_IMPORT_EXPORT_REJECTED_44]
ID: 44::
Severity: ERROR

+
Message: The current request is rejected due to an import or an export already in progress for the same data.

[#log-ref-log-ref-ERR_INVALID_IMPORT_SOURCE_45]
ID: 45::
Severity: ERROR

+
Message: On domain %s, initialization of server with serverId:%s has been requested from a server with an invalid serverId:%s. %s.

[#log-ref-log-ref-ERR_INVALID_EXPORT_TARGET_46]
ID: 46::
Severity: ERROR

+
Message: Invalid target for the export.

[#log-ref-log-ref-ERR_NO_REACHABLE_PEER_IN_THE_DOMAIN_47]
ID: 47::
Severity: ERROR

+
Message: Domain %s: the server with serverId=%s is unreachable.

[#log-ref-log-ref-ERR_NO_MATCHING_DOMAIN_48]
ID: 48::
Severity: ERROR

+
Message: No domain matches the provided base DN '%s'.

[#log-ref-log-ref-ERR_MULTIPLE_MATCHING_DOMAIN_49]
ID: 49::
Severity: ERROR

+
Message: Multiple domains match the base DN provided.

[#log-ref-log-ref-ERR_INVALID_PROVIDER_50]
ID: 50::
Severity: ERROR

+
Message: The provider class does not allow the operation requested.

[#log-ref-log-ref-ERR_COULD_NOT_SOLVE_HOSTNAME_51]
ID: 51::
Severity: ERROR

+
Message: The hostname %s could not be resolved as an IP address.

[#log-ref-log-ref-ERR_DUPLICATE_SERVER_ID_54]
ID: 54::
Severity: ERROR

+
Message: In Replication server %s: servers %s and %s have the same ServerId : %d.

[#log-ref-log-ref-ERR_DUPLICATE_REPLICATION_SERVER_ID_55]
ID: 55::
Severity: ERROR

+
Message: In Replication server %s: replication servers %s and %s have the same ServerId : %d.

[#log-ref-log-ref-ERR_BAD_HISTORICAL_56]
ID: 56::
Severity: ERROR

+
Message: Entry %s was containing some unknown historical information, This may cause some inconsistency for this entry.

[#log-ref-log-ref-ERR_CANNOT_ADD_CONFLICT_ATTRIBUTE_57]
ID: 57::
Severity: ERROR

+
Message: A conflict was detected but the conflict information could not be added. Operation: %s, Result: %s.

[#log-ref-log-ref-ERR_CANNOT_RENAME_CONFLICT_ENTRY_58]
ID: 58::
Severity: ERROR

+
Message: An error happened trying to rename a conflicting entry. DN: %s, Operation: %s, Result: %s.

[#log-ref-log-ref-ERR_REPLICATION_COULD_NOT_CONNECT_61]
ID: 61::
Severity: ERROR

+
Message: The Replication is configured for suffix %s but was not able to connect to any Replication Server.

[#log-ref-log-ref-ERR_CHANGELOG_ERROR_SENDING_ERROR_65]
ID: 65::
Severity: ERROR

+
Message: An unexpected error occurred while sending an Error Message to %s. This connection is going to be closed and reopened.

[#log-ref-log-ref-ERR_CHANGELOG_ERROR_SENDING_MSG_66]
ID: 66::
Severity: ERROR

+
Message: An unexpected error occurred while sending a Message to %s. This connection is going to be closed and reopened.

[#log-ref-log-ref-ERR_ERROR_REPLAYING_OPERATION_67]
ID: 67::
Severity: ERROR

+
Message: Could not replay operation %s with ChangeNumber %s error %s %s.

[#log-ref-log-ref-ERR_UNKNOWN_ATTRIBUTE_IN_HISTORICAL_68]
ID: 68::
Severity: ERROR

+
Message: The entry %s has historical information for attribute %s which is not defined in the schema. This information will be ignored.

[#log-ref-log-ref-ERR_COULD_NOT_CLOSE_THE_SOCKET_70]
ID: 70::
Severity: ERROR

+
Message: The Replication Server socket could not be closed : %s.

[#log-ref-log-ref-ERR_COULD_NOT_STOP_LISTEN_THREAD_71]
ID: 71::
Severity: ERROR

+
Message: The thread listening on the replication server port could not be stopped : %s.

[#log-ref-log-ref-ERR_SEARCHING_GENERATION_ID_73]
ID: 73::
Severity: ERROR

+
Message: An unexpected error occurred when searching for generation id for domain "%s": %s.

[#log-ref-log-ref-ERR_SEARCHING_DOMAIN_BACKEND_74]
ID: 74::
Severity: ERROR

+
Message: An unexpected error occurred when looking for the replicated backend : %s. It may be not configured or disabled.

[#log-ref-log-ref-ERR_LOADING_GENERATION_ID_75]
ID: 75::
Severity: ERROR

+
Message: An unexpected error occurred when searching in %s for the generation ID : %s.

[#log-ref-log-ref-ERR_UPDATING_GENERATION_ID_76]
ID: 76::
Severity: ERROR

+
Message: An unexpected error occurred when updating generation ID for domain "%s": %s.

[#log-ref-log-ref-ERR_ERROR_MSG_RECEIVED_79]
ID: 79::
Severity: ERROR

+
Message: The following error has been received : %s.

[#log-ref-log-ref-ERR_INIT_IMPORT_NOT_SUPPORTED_82]
ID: 82::
Severity: ERROR

+
Message: Initialization cannot be done because import is not supported by the backend %s.

[#log-ref-log-ref-ERR_INIT_EXPORT_NOT_SUPPORTED_83]
ID: 83::
Severity: ERROR

+
Message: Initialization cannot be done because export is not supported by the backend %s.

[#log-ref-log-ref-ERR_INIT_CANNOT_LOCK_BACKEND_84]
ID: 84::
Severity: ERROR

+
Message: Initialization cannot be done because the following error occurred while locking the backend %s : %s.

[#log-ref-log-ref-ERR_EXCEPTION_LISTENING_86]
ID: 86::
Severity: ERROR

+
Message: Replication server caught exception while listening for client connections %s.

[#log-ref-log-ref-ERR_ERROR_CLEARING_DB_87]
ID: 87::
Severity: ERROR

+
Message: While clearing the database %s , the following error happened: %s.

[#log-ref-log-ref-ERR_CHECK_CREATE_REPL_BACKEND_FAILED_89]
ID: 89::
Severity: ERROR

+
Message: An unexpected error occurred when testing existence or creating the replication backend : %s.

[#log-ref-log-ref-ERR_BACKEND_SEARCH_ENTRY_93]
ID: 93::
Severity: ERROR

+
Message: An error occurred when searching for %s : %s.

[#log-ref-log-ref-ERR_UNKNOWN_DN_95]
ID: 95::
Severity: ERROR

+
Message: The base DN %s is not stored by any of the Directory Server backend.

[#log-ref-log-ref-ERR_PROCESSING_REMOTE_MONITOR_DATA_107]
ID: 107::
Severity: ERROR

+
Message: Monitor data of remote servers are missing due to a processing error : %s.

[#log-ref-log-ref-ERR_SENDING_REMOTE_MONITOR_DATA_REQUEST_108]
ID: 108::
Severity: ERROR

+
Message: Unable to send monitor data request for domain "%s" to replication server RS(%d) due to the following error: %s.

[#log-ref-log-ref-ERR_EXCEPTION_REPLAYING_REPLICATION_MESSAGE_109]
ID: 109::
Severity: ERROR

+
Message: An Exception was caught while replaying replication message : %s.

[#log-ref-log-ref-ERR_PUBLISHING_FAKE_OPS_114]
ID: 114::
Severity: ERROR

+
Message: Caught exception publishing fake operations for domain %s : %s.

[#log-ref-log-ref-ERR_COMPUTING_FAKE_OPS_115]
ID: 115::
Severity: ERROR

+
Message: Caught exception computing fake operations for domain %s for replication server %s : %s.

[#log-ref-log-ref-ERR_RESET_GENERATION_CONN_ERR_ID_118]
ID: 118::
Severity: ERROR

+
Message: For replicated domain %s, in server with serverId=%s, the generation ID could not be set to value %s in the rest of the topology because this server is NOT connected to any replication server. You should check in the configuration that the domain is enabled and that there is one replication server up and running.

[#log-ref-log-ref-ERR_RS_DN_DOES_NOT_MATCH_121]
ID: 121::
Severity: ERROR

+
Message: DN sent by remote replication server: %s does not match local replication server one: %s.

[#log-ref-log-ref-ERR_DS_DN_DOES_NOT_MATCH_122]
ID: 122::
Severity: ERROR

+
Message: DN sent by replication server: %s does not match local directory server one: %s.

[#log-ref-log-ref-ERR_EXCEPTION_FORWARDING_RESET_GEN_ID_123]
ID: 123::
Severity: ERROR

+
Message: Caught IOException while forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %s.

[#log-ref-log-ref-ERR_DS_INVALID_INIT_STATUS_124]
ID: 124::
Severity: ERROR

+
Message: Computed invalid initial status: %s in DS replication domain %s with server id %s.

[#log-ref-log-ref-ERR_RS_INVALID_INIT_STATUS_125]
ID: 125::
Severity: ERROR

+
Message: Replication server received invalid initial status: %s for replication domain %s from server id %s.

[#log-ref-log-ref-ERR_DS_INVALID_REQUESTED_STATUS_126]
ID: 126::
Severity: ERROR

+
Message: Received invalid requested status %s in DS replication domain %s with server id %s.

[#log-ref-log-ref-ERR_RS_CANNOT_CHANGE_STATUS_127]
ID: 127::
Severity: ERROR

+
Message: Could not compute new status in RS replication domain %s for server id %s. Was in %s status and received %s event.

[#log-ref-log-ref-ERR_DS_CANNOT_CHANGE_STATUS_128]
ID: 128::
Severity: ERROR

+
Message: Could not compute new status in DS replication domain %s with server id %s. Was in %s status and received %s event.

[#log-ref-log-ref-ERR_EXCEPTION_CHANGING_STATUS_AFTER_RESET_GEN_ID_129]
ID: 129::
Severity: ERROR

+
Message: Caught IOException while changing status for domain %s and serverId: %s after reset for generation id: %s.

[#log-ref-log-ref-ERR_RECEIVED_CHANGE_STATUS_NOT_FROM_DS_130]
ID: 130::
Severity: ERROR

+
Message: Received change status message does not come from a directory server (dn: %s, server id: %s, msg: %s).

[#log-ref-log-ref-ERR_RS_INVALID_NEW_STATUS_132]
ID: 132::
Severity: ERROR

+
Message: Received invalid new status %s in RS for replication domain %s and directory server id %s.

[#log-ref-log-ref-ERR_EXCEPTION_SENDING_CS_134]
ID: 134::
Severity: ERROR

+
Message: Replication broker with dn %s and server id %s failed to signal status change because of: %s.

[#log-ref-log-ref-ERR_EXCEPTION_CHANGING_STATUS_FROM_STATUS_ANALYZER_139]
ID: 139::
Severity: ERROR

+
Message: Caught IOException while changing status for domain %s and serverId: %s from status analyzer: %s.

[#log-ref-log-ref-ERR_DS_UNKNOWN_ASSURED_MODE_149]
ID: 149::
Severity: ERROR

+
Message: In directory server %s, received unknown assured update mode: %s, for domain %s. Message: %s.

[#log-ref-log-ref-ERR_RS_UNKNOWN_ASSURED_MODE_150]
ID: 150::
Severity: ERROR

+
Message: In replication server %s, received unknown assured update mode: %s, for domain %s. Message: %s.

[#log-ref-log-ref-ERR_UNKNOWN_ASSURED_SAFE_DATA_LEVEL_151]
ID: 151::
Severity: ERROR

+
Message: In replication server %s, received a safe data assured update message with incoherent level: %s, this is for domain %s. Message: %s.

[#log-ref-log-ref-ERR_RESET_GENERATION_ID_FAILED_152]
ID: 152::
Severity: ERROR

+
Message: The generation ID could not be reset for domain %s.

[#log-ref-log-ref-ERR_COULD_NOT_START_REPLICATION_154]
ID: 154::
Severity: ERROR

+
Message: The Replication was not started on base-dn %s : %s.

[#log-ref-log-ref-ERR_REPLICATION_PROTOCOL_MESSAGE_TYPE_157]
ID: 157::
Severity: ERROR

+
Message: Replication protocol error. Bad message type. %s received, %s required.

[#log-ref-log-ref-ERR_BYTE_COUNT_159]
ID: 159::
Severity: ERROR

+
Message: The Server Handler byte count is not correct Byte Count=%s (Fixed).

[#log-ref-log-ref-ERR_PLUGIN_FRACTIONAL_LDIF_IMPORT_INVALID_PLUGIN_TYPE_168]
ID: 168::
Severity: ERROR

+
Message: The fractional replication ldif import plugin is configured with invalid plugin type %s. Only the ldifImport plugin type is allowed.

[#log-ref-log-ref-ERR_CHANGENUMBER_DATABASE_173]
ID: 173::
Severity: ERROR

+
Message: An error occurred when accessing the change number database : %s.

[#log-ref-log-ref-ERR_INITIALIZATION_FAILED_NOCONN_174]
ID: 174::
Severity: ERROR

+
Message: The initialization failed because the domain %s is not connected to a replication server.

[#log-ref-log-ref-ERR_FRACTIONAL_COULD_NOT_RETRIEVE_CONFIG_175]
ID: 175::
Severity: ERROR

+
Message: Could not retrieve the configuration for a replication domain matching the entry %s.

[#log-ref-log-ref-ERR_DS_DISCONNECTED_DURING_HANDSHAKE_178]
ID: 178::
Severity: ERROR

+
Message: Directory server %s was attempting to connect to replication server %s but has disconnected in handshake phase. Error: %s.

[#log-ref-log-ref-ERR_RS_DISCONNECTED_DURING_HANDSHAKE_179]
ID: 179::
Severity: ERROR

+
Message: Replication server %s was attempting to connect to replication server %s but has disconnected in handshake phase. Error: %s.

[#log-ref-log-ref-ERR_RS_BADLY_DISCONNECTED_181]
ID: 181::
Severity: ERROR

+
Message: The connection from this replication server RS(%d) to replication server RS(%d) at %s for domain "%s" has failed.

[#log-ref-log-ref-ERR_RESYNC_REQUIRED_UNKNOWN_DOMAIN_IN_PROVIDED_COOKIE_185]
ID: 185::
Severity: ERROR

+
Message: Full resync required. Reason: The provided cookie contains unknown replicated domain %s. Current starting cookie <%s>.

[#log-ref-log-ref-ERR_RESYNC_REQUIRED_TOO_OLD_DOMAIN_IN_PROVIDED_COOKIE_186]
ID: 186::
Severity: ERROR

+
Message: Full resync required. Reason: The provided cookie is older than the start of historical in the server for the replicated domain : %s.

[#log-ref-log-ref-ERR_INVALID_COOKIE_SYNTAX_187]
ID: 187::
Severity: ERROR

+
Message: Invalid syntax for the provided cookie '%s'.

[#log-ref-log-ref-ERR_INIT_EXPORTER_DISCONNECTION_189]
ID: 189::
Severity: ERROR

+
Message: Domain %s (server id: %s) : remote exporter server disconnection (server id: %s ) detected during initialization.

[#log-ref-log-ref-ERR_INIT_IMPORT_FAILURE_190]
ID: 190::
Severity: ERROR

+
Message: During initialization from a remote server, the following error occurred : %s.

[#log-ref-log-ref-ERR_INIT_RS_DISCONNECTION_DURING_IMPORT_191]
ID: 191::
Severity: ERROR

+
Message: Connection failure with Replication Server %s during import.

[#log-ref-log-ref-ERR_INIT_BAD_MSG_ID_SEQ_DURING_IMPORT_192]
ID: 192::
Severity: ERROR

+
Message: Bad msg id sequence during import. Expected:%s Actual:%s.

[#log-ref-log-ref-ERR_INIT_NO_SUCCESS_START_FROM_SERVERS_193]
ID: 193::
Severity: ERROR

+
Message: The following servers did not acknowledge initialization in the expected time for domain %s. They are potentially down or too slow. Servers list: %s.

[#log-ref-log-ref-ERR_INIT_NO_SUCCESS_END_FROM_SERVERS_194]
ID: 194::
Severity: ERROR

+
Message: The following servers did not end initialization being connected with the right generation (%s). They are potentially stopped or too slow. Servers list: %s.

[#log-ref-log-ref-ERR_INIT_RS_DISCONNECTION_DURING_EXPORT_195]
ID: 195::
Severity: ERROR

+
Message: When initializing remote server(s), connection to Replication Server with serverId=%s is lost.

[#log-ref-log-ref-ERR_INIT_HEARTBEAT_LOST_DURING_EXPORT_196]
ID: 196::
Severity: ERROR

+
Message: When initializing remote server(s), the initialized server with serverId=%s is potentially stopped or too slow.

[#log-ref-log-ref-ERR_SENDING_NEW_ATTEMPT_INIT_REQUEST_197]
ID: 197::
Severity: ERROR

+
Message: When sending a new initialization request for an initialization from a remote server, the following error occurred %s. The initial error was : %s.

[#log-ref-log-ref-ERR_RSQUEUE_DIFFERENT_MSGS_WITH_SAME_CSN_201]
ID: 201::
Severity: ERROR

+
Message: Processing two different changes with same CSN=%s. Previous msg=<%s>, New msg=<%s>.

[#log-ref-log-ref-ERR_COULD_NOT_SOLVE_CONFLICT_202]
ID: 202::
Severity: ERROR

+
Message: Error while trying to solve conflict with DN : %s ERROR : %s.

[#log-ref-log-ref-ERR_DS_BADLY_DISCONNECTED_211]
ID: 211::
Severity: ERROR

+
Message: The connection from this replication server RS(%d) to directory server DS(%d) at %s for domain "%s" has failed.

[#log-ref-log-ref-ERR_SESSION_STARTUP_INTERRUPTED_216]
ID: 216::
Severity: ERROR

+
Message: %s was interrupted in the startup phase.

[#log-ref-log-ref-ERR_CANNOT_CREATE_REPLICA_DB_BECAUSE_CHANGELOG_DB_SHUTDOWN_235]
ID: 235::
Severity: ERROR

+
Message: Could not create replica database because the changelog database is shutting down.

[#log-ref-log-ref-ERR_CHANGE_NUMBER_INDEXER_UNEXPECTED_EXCEPTION_236]
ID: 236::
Severity: ERROR

+
Message: An unexpected error forced the %s thread to shutdown: %s. The changeNumber attribute will not move forward anymore. You can reenable this thread by first setting the "compute-change-number" property to false and then back to true.

[#log-ref-log-ref-ERR_COULD_NOT_ADD_CHANGE_TO_SHUTTING_DOWN_REPLICA_DB_240]
ID: 240::
Severity: ERROR

+
Message: Could not add change %s to replicaDB %s %s because flushing thread is shutting down.

[#log-ref-log-ref-ERR_CHANGELOG_READ_STATE_CANT_READ_DOMAIN_DIRECTORY_243]
ID: 243::
Severity: ERROR

+
Message: Error when retrieving changelog state from root path '%s' : IO error on domain directory '%s' when retrieving list of server ids.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_CREATE_REPLICA_DB_244]
ID: 244::
Severity: ERROR

+
Message: Could not get or create replica DB for baseDN '%s', serverId '%d', generationId '%d': %s.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_CREATE_CN_INDEX_DB_245]
ID: 245::
Severity: ERROR

+
Message: Could not get or create change number index DB in root path '%s', using path '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DELETE_GENERATION_ID_FILE_246]
ID: 246::
Severity: ERROR

+
Message: Could not retrieve generation id file '%s' for DN '%s' to delete it.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_CREATE_SERVER_ID_DIRECTORY_247]
ID: 247::
Severity: ERROR

+
Message: Could not create directory '%s' for server id %d.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_CREATE_GENERATION_ID_FILE_248]
ID: 248::
Severity: ERROR

+
Message: Could not create generation id file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_SERVER_ID_FILENAME_WRONG_FORMAT_250]
ID: 250::
Severity: ERROR

+
Message: Could not read server id filename because it uses a wrong format, expecting '[id].server' where [id] is numeric but got '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_GENERATION_ID_WRONG_FORMAT_251]
ID: 251::
Severity: ERROR

+
Message: Could not read generation id because it uses a wrong format, expecting a number but got '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_OPEN_LOG_FILE_252]
ID: 252::
Severity: ERROR

+
Message: Could not open log file '%s' for write.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_OPEN_READER_ON_LOG_FILE_253]
ID: 253::
Severity: ERROR

+
Message: Could not open a reader on log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DECODE_RECORD_254]
ID: 254::
Severity: ERROR

+
Message: Could not decode a record from data read in log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DELETE_LOG_FILE_255]
ID: 255::
Severity: ERROR

+
Message: Could not delete log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_FILE_256]
ID: 256::
Severity: ERROR

+
Message: Could not create log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_ADD_RECORD_258]
ID: 258::
Severity: ERROR

+
Message: Could not add record '%s' in log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_SYNC_259]
ID: 259::
Severity: ERROR

+
Message: Could not synchronize written records to file system for log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_SEEK_260]
ID: 260::
Severity: ERROR

+
Message: Could not seek to position %d for reader on log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_CREATE_LOG_DIRECTORY_261]
ID: 261::
Severity: ERROR

+
Message: Could not create root directory '%s' for log file.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DECODE_DN_FROM_DOMAIN_STATE_FILE_262]
ID: 262::
Severity: ERROR

+
Message: Could not decode DN from domain state file '%s', from line '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_READ_DOMAIN_STATE_FILE_263]
ID: 263::
Severity: ERROR

+
Message: Could not read domain state file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_INCOHERENT_DOMAIN_STATE_264]
ID: 264::
Severity: ERROR

+
Message: There is a mismatch between domain state file and actual domain directories found in file system. Expected domain ids : '%s'. Actual domain ids found in file system: '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_UPDATE_DOMAIN_STATE_FILE_265]
ID: 265::
Severity: ERROR

+
Message: Could not create a new domain id %s for domain DN %s and save it in domain state file '%s".

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_GET_CURSOR_READER_POSITION_LOG_FILE_266]
ID: 266::
Severity: ERROR

+
Message: Could not get reader position for cursor in log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DECODE_KEY_FROM_STRING_267]
ID: 267::
Severity: ERROR

+
Message: Could not decode the key from string [%s].

[#log-ref-log-ref-ERR_CHANGELOG_CURSOR_OPENED_WHILE_CLOSING_LOG_269]
ID: 269::
Severity: ERROR

+
Message: When closing log '%s', found %d cursor(s) still opened on the log.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_INITIALIZE_LOG_270]
ID: 270::
Severity: ERROR

+
Message: Could not initialize the log '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_RETRIEVE_KEY_BOUNDS_FROM_FILE_271]
ID: 271::
Severity: ERROR

+
Message: Could not retrieve key bounds from log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_RETRIEVE_READ_ONLY_LOG_FILES_LIST_272]
ID: 272::
Severity: ERROR

+
Message: Could not retrieve read-only log files from log '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DELETE_LOG_FILE_WHILE_PURGING_273]
ID: 273::
Severity: ERROR

+
Message: While purging log, could not delete log file(s): '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNREFERENCED_LOG_WHILE_RELEASING_274]
ID: 274::
Severity: ERROR

+
Message: The following log '%s' must be released but it is not referenced.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_RENAME_HEAD_LOG_FILE_275]
ID: 275::
Severity: ERROR

+
Message: Could not rename head log file from '%s' to '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_WRITE_REPLICA_OFFLINE_STATE_FILE_278]
ID: 278::
Severity: ERROR

+
Message: Could not write offline replica information for domain %s and server id %d, using path '%s' (offline CSN is %s).

[#log-ref-log-ref-ERR_CHANGELOG_INVALID_REPLICA_OFFLINE_STATE_FILE_279]
ID: 279::
Severity: ERROR

+
Message: Could not read replica offline state file '%s' for domain %s, it should contain exactly one line corresponding to the offline CSN.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_READ_REPLICA_OFFLINE_STATE_FILE_280]
ID: 280::
Severity: ERROR

+
Message: Could not read content of replica offline state file '%s' for domain %s.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DELETE_REPLICA_OFFLINE_STATE_FILE_281]
ID: 281::
Severity: ERROR

+
Message: Could not delete replica offline state file '%s' for domain %s and server id %d.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_RETRIEVE_FILE_LENGTH_282]
ID: 282::
Severity: ERROR

+
Message: Could not retrieve file length of log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_RECOVER_LOG_FILE_283]
ID: 283::
Severity: ERROR

+
Message: An error occurred while recovering the replication change log file '%s'. The recovery has been aborted and this replication server will be removed from the replication topology. The change log file system may be read-only, full, or corrupt and must be fixed before this replication server can be used. The underlying error was: %s.

[#log-ref-log-ref-ERR_CHANGELOG_BACKEND_SEARCH_286]
ID: 286::
Severity: ERROR

+
Message: An error occurred when searching base DN '%s' with filter '%s' in changelog backend : %s.

[#log-ref-log-ref-ERR_CHANGELOG_BACKEND_ATTRIBUTE_287]
ID: 287::
Severity: ERROR

+
Message: An error occurred when retrieving attribute value for attribute '%s' for entry DN '%s' in changelog backend : %s.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_CREATE_LAST_LOG_ROTATION_TIME_FILE_288]
ID: 288::
Severity: ERROR

+
Message: Could not create file '%s' to store last log rotation time %d.

[#log-ref-log-ref-ERR_CHANGELOG_UNABLE_TO_DELETE_LAST_LOG_ROTATION_TIME_FILE_289]
ID: 289::
Severity: ERROR

+
Message: Could not delete file '%s' that stored the previous last log rotation time.

[#log-ref-log-ref-ERR_CHANGELOG_CURSOR_ABORTED_290]
ID: 290::
Severity: ERROR

+
Message: Cursor on log '%s' has been aborted after a purge or a clear.

[#log-ref-log-ref-ERR_CHANGELOG_CANNOT_READ_NEWEST_RECORD_291]
ID: 291::
Severity: ERROR

+
Message: Could not position and read newest record from log file '%s'.

[#log-ref-log-ref-ERR_CHANGELOG_RESET_CHANGE_NUMBER_CHANGE_NOT_PRESENT_293]
ID: 293::
Severity: ERROR

+
Message: The change number index could not be reset to start with %d in base DN '%s' because starting CSN '%s' does not exist in the change log.

[#log-ref-log-ref-ERR_CHANGELOG_RESET_CHANGE_NUMBER_CSN_TOO_OLD_294]
ID: 294::
Severity: ERROR

+
Message: The change number could not be reset to %d because the associated change with CSN '%s' has already been purged from the change log. Try resetting to a more recent change.

[#log-ref-log-ref-ERR_REPLICATION_CHANGE_NUMBER_DISABLED_295]
ID: 295::
Severity: ERROR

+
Message: Change number indexing is disabled for replication domain '%s'.

[#log-ref-log-ref-ERR_UNRECOGNIZED_RECORD_VERSION_297]
ID: 297::
Severity: ERROR

+
Message: Cannot decode change-log record with version %x.

[#log-ref-log-ref-ERR_REPLICATION_UNEXPECTED_MESSAGE_300]
ID: 300::
Severity: ERROR

+
Message: New replication connection from %s started with unexpected message %s and is being closed.

[#log-ref-log-ref-ERR_INVALID_CSN_RANGE_COMPARISON_OPERATOR_305]
ID: 305::
Severity: ERROR

+
Message: Invalid operator '%s' specified in historicalCsnRangeMatch extensible matching rule assertion.

[#log-ref-log-ref-ERR_INVALID_CSN_RANGE_ASSERTION_SYNTAX_306]
ID: 306::
Severity: ERROR

+
Message: Specified assertion '%s' for historicalCsnRangeMatch extensible matching rule does not conform to expected syntax. The assertion must specify a CSN range.

[#log-ref-log-ref-ERR_CSN_RANGE_INCLUDES_MORE_THAN_ONE_SERVER_307]
ID: 307::
Severity: ERROR

+
Message: Specified CSNs '%s' and '%s' have two different server ids. The historicalCsnRangeMatch extensible matching rule requires CSNs to have the same server id.

[#log-ref-log-ref-ERR_CSN_RANGE_SAME_OPERATOR_TYPE_308]
ID: 308::
Severity: ERROR

+
Message: Specified operators '%s' and '%s' do not specify a range for historicalCsnRangeMatch extensible matching rule.

[#log-ref-log-ref-ERR_COULD_NOT_RESTART_CHANGELOG_309]
ID: 309::
Severity: ERROR

+
Message: Could not restart the Replication Server, bind to listen port %d failed : %s.

[#log-ref-log-ref-ERR_DISK_FULL_CHANGELOG_DIRECTORY_310]
ID: 310::
Severity: ERROR

+
Message: The replication server has detected that the file system containing the changelog is full. In order to prevent further problems, the replication server will disconnect from the replication topology and wait for sufficient disk space to be recovered, at which point it will reconnect.

--


[#SCHEMA]
=== Log Message Category: SCHEMA

--

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_END_WITH_COMMA_26]
ID: 26::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was a comma or semicolon.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_CHAR_28]
ID: 28::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not allowed in an attribute name.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_UNDERSCORE_CHAR_29]
ID: 29::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the underscore character is not allowed in an attribute name unless the %s configuration option is enabled.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_INITIAL_DASH_30]
ID: 30::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the hyphen character is not allowed as the first character of an attribute name.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_INITIAL_UNDERSCORE_31]
ID: 31::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the underscore character is not allowed as the first character of an attribute name even if the %s configuration option is enabled.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_INITIAL_DIGIT_32]
ID: 32::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the digit '%c' is not allowed as the first character of an attribute name unless the name is specified as an OID or the %s configuration option is enabled.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_NO_NAME_33]
ID: 33::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because it contained an RDN containing an empty attribute name.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_PERIOD_34]
ID: 34::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the parsed attribute name %s included a period but that name did not appear to be a valid OID.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_END_WITH_ATTR_NAME_35]
ID: 35::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the last non-space character was part of the attribute name '%s'.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_NO_EQUAL_36]
ID: 36::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because the next non-space character after attribute name "%s" should have been an equal sign but instead was '%c'.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_INVALID_CHAR_37]
ID: 37::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not valid.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_HEX_VALUE_TOO_SHORT_38]
ID: 38::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with an octothorpe (#) but was not followed by a positive multiple of two hexadecimal digits.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_INVALID_HEX_DIGIT_39]
ID: 39::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with an octothorpe (#) but contained a character %c that was not a valid hexadecimal digit.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ATTR_VALUE_DECODE_FAILURE_40]
ID: 40::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because an unexpected failure occurred while attempting to parse an attribute value from one of the RDN components: "%s".

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_UNMATCHED_QUOTE_41]
ID: 41::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because one of the RDN components included a quoted value that did not have a corresponding closing quotation mark.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_ESCAPED_HEX_VALUE_INVALID_42]
ID: 42::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because one of the RDN components included a value with an escaped hexadecimal digit that was not followed by a second hexadecimal digit.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_ATTRTYPE_EMPTY_VALUE_52]
ID: 52::
Severity: ERROR

+
Message: The provided value could not be parsed as a valid attribute type description because it was empty or contained only whitespace.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_EMPTY_VALUE_69]
ID: 69::
Severity: ERROR

+
Message: The provided value could not be parsed as a valid objectclass description because it was empty or contained only whitespace.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_EXPECTED_OPEN_PARENTHESIS_70]
ID: 70::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an objectclass description because an open parenthesis was expected at position %d but instead a '%s' character was found.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_TRUNCATED_VALUE_71]
ID: 71::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an objectclass description because the end of the value was encountered while the Directory Server expected more data to be provided.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_DOUBLE_PERIOD_IN_NUMERIC_OID_72]
ID: 72::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an objectclass description because the numeric OID contained two consecutive periods at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_ILLEGAL_CHAR_IN_NUMERIC_OID_73]
ID: 73::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an objectclass description because the numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_ILLEGAL_CHAR_IN_STRING_OID_74]
ID: 74::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an objectclass description because the non-numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_ILLEGAL_CHAR_75]
ID: 75::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an objectclass description because it contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_OBJECTCLASS_UNEXPECTED_CLOSE_PARENTHESIS_76]
ID: 76::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an objectclass description because it contained an unexpected closing parenthesis at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_EMPTY_VALUE_119]
ID: 119::
Severity: ERROR

+
Message: The provided value could not be parsed as a valid DIT content rule description because it was empty or contained only whitespace.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_EXPECTED_OPEN_PARENTHESIS_120]
ID: 120::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because an open parenthesis was expected at position %d but instead a '%s' character was found.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_TRUNCATED_VALUE_121]
ID: 121::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because the end of the value was encountered while the Directory Server expected more data to be provided.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_DOUBLE_PERIOD_IN_NUMERIC_OID_122]
ID: 122::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because the numeric OID contained two consecutive periods at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_ILLEGAL_CHAR_IN_NUMERIC_OID_123]
ID: 123::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because the numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_ILLEGAL_CHAR_IN_STRING_OID_124]
ID: 124::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because the non-numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_UNEXPECTED_CLOSE_PARENTHESIS_125]
ID: 125::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because it contained an unexpected closing parenthesis at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_ILLEGAL_CHAR_126]
ID: 126::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because it contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_UNKNOWN_STRUCTURAL_CLASS_127]
ID: 127::
Severity: ERROR

+
Message: The DIT content rule "%s" is associated with a structural objectclass %s that is not defined in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_STRUCTURAL_CLASS_NOT_STRUCTURAL_128]
ID: 128::
Severity: ERROR

+
Message: The DIT content rule "%s" is associated with the objectclass with OID %s (%s). This objectclass exists in the server schema but is defined as %s rather than structural.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_UNKNOWN_AUXILIARY_CLASS_129]
ID: 129::
Severity: ERROR

+
Message: The DIT content rule "%s" is associated with an auxiliary objectclass %s that is not defined in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_AUXILIARY_CLASS_NOT_AUXILIARY_130]
ID: 130::
Severity: ERROR

+
Message: The DIT content rule "%s" is associated with an auxiliary objectclass %s. This objectclass exists in the server schema but is defined as %s rather than auxiliary.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_UNKNOWN_REQUIRED_ATTR_131]
ID: 131::
Severity: ERROR

+
Message: The DIT content rule "%s" is associated with a required attribute type %s that is not defined in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_UNKNOWN_OPTIONAL_ATTR_132]
ID: 132::
Severity: ERROR

+
Message: The DIT content rule "%s" is associated with an optional attribute type %s that is not defined in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_UNKNOWN_PROHIBITED_ATTR_133]
ID: 133::
Severity: ERROR

+
Message: The DIT content rule "%s" is associated with a prohibited attribute type %s that is not defined in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_EXPECTED_QUOTE_AT_POS_134]
ID: 134::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT content rule description because a single quote was expected at position %d but the %s character was found instead.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_EMPTY_VALUE_135]
ID: 135::
Severity: ERROR

+
Message: The provided value could not be parsed as a valid name form description because it was empty or contained only whitespace.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_EXPECTED_OPEN_PARENTHESIS_136]
ID: 136::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because an open parenthesis was expected at position %d but instead a '%c' character was found.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_TRUNCATED_VALUE_137]
ID: 137::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because the end of the value was encountered while the Directory Server expected more data to be provided.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_DOUBLE_PERIOD_IN_NUMERIC_OID_138]
ID: 138::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because the numeric OID contained two consecutive periods at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_ILLEGAL_CHAR_IN_NUMERIC_OID_139]
ID: 139::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because the numeric OID contained an illegal character %c at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_ILLEGAL_CHAR_IN_STRING_OID_140]
ID: 140::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because the non-numeric OID contained an illegal character %c at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_UNEXPECTED_CLOSE_PARENTHESIS_141]
ID: 141::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because it contained an unexpected closing parenthesis at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_ILLEGAL_CHAR_142]
ID: 142::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because it contained an illegal character %c at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_UNKNOWN_STRUCTURAL_CLASS_143]
ID: 143::
Severity: ERROR

+
Message: The name form description "%s" is associated with a structural objectclass %s that is not defined in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_STRUCTURAL_CLASS_NOT_STRUCTURAL_144]
ID: 144::
Severity: ERROR

+
Message: The name form description "%s" is associated with the objectclass with OID %s (%s). This objectclass exists in the server schema but is defined as %s rather than structural.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_UNKNOWN_REQUIRED_ATTR_145]
ID: 145::
Severity: ERROR

+
Message: The definition for the name form with OID %s declared that it should include required attribute "%s". No attribute type matching this name or OID exists in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_UNKNOWN_OPTIONAL_ATTR_146]
ID: 146::
Severity: ERROR

+
Message: The definition for the name form with OID %s declared that it should include optional attribute "%s". No attribute type matching this name or OID exists in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_NO_STRUCTURAL_CLASS_147]
ID: 147::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because it does not specify the structural objectclass with which it is associated.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_NAME_FORM_EXPECTED_QUOTE_AT_POS_148]
ID: 148::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a name form description because a single quote was expected at position %d but the %c character was found instead.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_EMPTY_VALUE_160]
ID: 160::
Severity: ERROR

+
Message: The provided value could not be parsed as a valid matching rule use description because it was empty or contained only whitespace.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_EXPECTED_OPEN_PARENTHESIS_161]
ID: 161::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because an open parenthesis was expected at position %d but instead a '%s' character was found.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_TRUNCATED_VALUE_162]
ID: 162::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because the end of the value was encountered while the Directory Server expected more data to be provided.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_DOUBLE_PERIOD_IN_NUMERIC_OID_163]
ID: 163::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because the numeric OID contained two consecutive periods at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_ILLEGAL_CHAR_IN_NUMERIC_OID_164]
ID: 164::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because the numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_ILLEGAL_CHAR_IN_STRING_OID_165]
ID: 165::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because the non-numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_UNKNOWN_MATCHING_RULE_166]
ID: 166::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because the specified matching rule %s is unknown.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_UNEXPECTED_CLOSE_PARENTHESIS_167]
ID: 167::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because it contained an unexpected closing parenthesis at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_ILLEGAL_CHAR_168]
ID: 168::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because it contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_UNKNOWN_ATTR_169]
ID: 169::
Severity: ERROR

+
Message: The matching rule use description "%s" is associated with attribute type %s that is not defined in the server schema.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_NO_ATTR_170]
ID: 170::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule description because it does not specify the set of attribute types that may be used with the associated OID.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_MRUSE_EXPECTED_QUOTE_AT_POS_171]
ID: 171::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a matching rule use description because a single quote was expected at position %d but the %s character was found instead.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_EMPTY_VALUE_172]
ID: 172::
Severity: ERROR

+
Message: The provided value could not be parsed as a valid DIT structure rule description because it was empty or contained only whitespace.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_EXPECTED_OPEN_PARENTHESIS_173]
ID: 173::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because an open parenthesis was expected at position %d but instead a '%s' character was found.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_TRUNCATED_VALUE_174]
ID: 174::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because the end of the value was encountered while the Directory Server expected more data to be provided.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_ILLEGAL_CHAR_IN_RULE_ID_175]
ID: 175::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because the rule ID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_UNEXPECTED_CLOSE_PARENTHESIS_176]
ID: 176::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because it contained an unexpected closing parenthesis at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_ILLEGAL_CHAR_177]
ID: 177::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because it contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_UNKNOWN_NAME_FORM_178]
ID: 178::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because it referenced an unknown name form %s.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_UNKNOWN_RULE_ID_179]
ID: 179::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because it referenced an unknown rule ID %d for a superior DIT structure rule.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_NO_NAME_FORM_180]
ID: 180::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because it did not specify the name form for the rule.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_EXPECTED_QUOTE_AT_POS_181]
ID: 181::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because a single quote was expected at position %d but the %s character was found instead.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_DOUBLE_PERIOD_IN_NUMERIC_OID_182]
ID: 182::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because the numeric OID contained two consecutive periods at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_ILLEGAL_CHAR_IN_NUMERIC_OID_183]
ID: 183::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because the numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DSR_ILLEGAL_CHAR_IN_STRING_OID_184]
ID: 184::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a DIT structure rule description because the non-numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_GUIDE_ILLEGAL_CHAR_206]
ID: 206::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s contained an illegal character %c at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_GUIDE_MISSING_CLOSE_PAREN_207]
ID: 207::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not contain a close parenthesis that corresponded to the initial open parenthesis.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_GUIDE_INVALID_QUESTION_MARK_208]
ID: 208::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s started with a question mark but was not followed by the string "true" or "false".

[#log-ref-log-ref-ERR_ATTR_SYNTAX_GUIDE_NO_DOLLAR_209]
ID: 209::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not contain a dollar sign to separate the attribute type from the match type.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_GUIDE_NO_ATTR_210]
ID: 210::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not specify an attribute type before the dollar sign.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_GUIDE_NO_MATCH_TYPE_211]
ID: 211::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s did not specify a match type after the dollar sign.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_GUIDE_INVALID_MATCH_TYPE_212]
ID: 212::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a guide value because the criteria portion %s had an invalid match type starting at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_INVALID_SCHEME_CHAR_243]
ID: 243::
Severity: ERROR

+
Message: The provided authPassword value had an invalid scheme character at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_NO_SCHEME_244]
ID: 244::
Severity: ERROR

+
Message: The provided authPassword value had a zero-length scheme element.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_NO_SCHEME_SEPARATOR_245]
ID: 245::
Severity: ERROR

+
Message: The provided authPassword value was missing the separator character or had an illegal character between the scheme and authInfo elements.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_INVALID_AUTH_INFO_CHAR_246]
ID: 246::
Severity: ERROR

+
Message: The provided authPassword value had an invalid authInfo character at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_NO_AUTH_INFO_247]
ID: 247::
Severity: ERROR

+
Message: The provided authPassword value had a zero-length authInfo element.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_NO_AUTH_INFO_SEPARATOR_248]
ID: 248::
Severity: ERROR

+
Message: The provided authPassword value was missing the separator character or had an illegal character between the authInfo and authValue elements.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_USERPW_NO_VALUE_253]
ID: 253::
Severity: ERROR

+
Message: No value was given to decode by the user password attribute syntax.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_USERPW_NO_OPENING_BRACE_254]
ID: 254::
Severity: ERROR

+
Message: Unable to decode the provided value according to the user password syntax because the value does not start with the opening curly brace ("{") character.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_USERPW_NO_CLOSING_BRACE_255]
ID: 255::
Severity: ERROR

+
Message: Unable to decode the provided value according to the user password syntax because the value does not contain a closing curly brace ("}") character.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_USERPW_NO_SCHEME_256]
ID: 256::
Severity: ERROR

+
Message: Unable to decode the provided value according to the user password syntax because the value does not contain a storage scheme name.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_RFC3672_SUBTREE_SPECIFICATION_INVALID_257]
ID: 257::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid RFC 3672 subtree specification.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_INVALID_AUTH_VALUE_CHAR_261]
ID: 261::
Severity: ERROR

+
Message: The provided authPassword value had an invalid authValue character at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_NO_AUTH_VALUE_262]
ID: 262::
Severity: ERROR

+
Message: The provided authPassword value had a zero-length authValue element.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_AUTHPW_INVALID_TRAILING_CHAR_263]
ID: 263::
Severity: ERROR

+
Message: The provided authPassword value had an invalid trailing character at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_SUBTREE_SPECIFICATION_INVALID_269]
ID: 269::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid subtree specification.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_PROHIBITED_REQUIRED_BY_STRUCTURAL_271]
ID: 271::
Severity: ERROR

+
Message: The DIT content rule "%s" is not valid because it prohibits the use of attribute type %s which is required by the associated structural object class %s.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DCR_PROHIBITED_REQUIRED_BY_AUXILIARY_272]
ID: 272::
Severity: ERROR

+
Message: The DIT content rule "%s" is not valid because it prohibits the use of attribute type %s which is required by the associated auxiliary object class %s.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_DN_INVALID_REQUIRES_ESCAPE_CHAR_282]
ID: 282::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid distinguished name because an attribute value started with a character at position %d that needs to be escaped.

[#log-ref-log-ref-ERR_OC_SYNTAX_ATTR_ILLEGAL_CHAR_288]
ID: 288::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid object class definition because character '%c' at position %d is not allowed in an object class name.

[#log-ref-log-ref-ERR_OC_SYNTAX_ATTR_ILLEGAL_UNDERSCORE_CHAR_289]
ID: 289::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid object class definition because the underscore character is not allowed in an object class name unless the %s configuration option is enabled.

[#log-ref-log-ref-ERR_OC_SYNTAX_ATTR_ILLEGAL_INITIAL_DASH_290]
ID: 290::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid object class definition because the hyphen character is not allowed as the first character of an object class name.

[#log-ref-log-ref-ERR_OC_SYNTAX_ATTR_ILLEGAL_INITIAL_UNDERSCORE_291]
ID: 291::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid object class definition because the underscore character is not allowed as the first character of an object class name even if the %s configuration option is enabled.

[#log-ref-log-ref-ERR_OC_SYNTAX_ATTR_ILLEGAL_INITIAL_DIGIT_292]
ID: 292::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as a valid object class definition because the digit '%c' is not allowed as the first character of an object class name unless the name is specified as an OID or the %s configuration option is enabled.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_UNKNOWN_EXT_306]
ID: 306::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax because it contains an unrecognized extension %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_EMPTY_VALUE_317]
ID: 317::
Severity: ERROR

+
Message: The provided value could not be parsed as a valid ldap syntax description because it was empty or contained only whitespace.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_EXPECTED_OPEN_PARENTHESIS_318]
ID: 318::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because an open parenthesis was expected at position %d but instead a '%s' character was found.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_TRUNCATED_VALUE_319]
ID: 319::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because the end of the value was encountered while the Directory Server expected more data to be provided.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_DOUBLE_PERIOD_IN_NUMERIC_OID_320]
ID: 320::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because the numeric OID contained two consecutive periods at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_ILLEGAL_CHAR_IN_NUMERIC_OID_321]
ID: 321::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because the numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_ILLEGAL_CHAR_IN_STRING_OID_322]
ID: 322::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because the non-numeric OID contained an illegal character %s at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_UNEXPECTED_CLOSE_PARENTHESIS_323]
ID: 323::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because it contained an unexpected closing parenthesis at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_TOO_MANY_EXTENSIONS_324]
ID: 324::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because it contains more than one form of constructor.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_UNKNOWN_SYNTAX_325]
ID: 325::
Severity: ERROR

+
Message: The definition for the ldap syntax with OID %s declared that it's a substitute for a syntax with OID %s. No such syntax is configured for use in the Directory Server.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_ENUM_NO_VALUES_326]
ID: 326::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an enumeration syntax, because there is no value.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_EXTENSION_INVALID_CHARACTER_327]
ID: 327::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax extension because an invalid character was found at position %d.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_LDAPSYNTAX_EXPECTED_QUOTE_AT_POS_329]
ID: 329::
Severity: ERROR

+
Message: The provided value "%s" could not be parsed as an ldap syntax description because a single quote was expected at position %d but the character %s was found instead.

[#log-ref-log-ref-ERR_ATTR_SYNTAX_ILLEGAL_X_SCHEMA_FILE_334]
ID: 334::
Severity: ERROR

+
Message: The provided value "%s" is not safe for X-SCHEMA-FILE.

[#log-ref-log-ref-ERR_ATTR_TYPE_CANNOT_REGISTER_340]
ID: 340::
Severity: ERROR

+
Message: Attribute type could not be registered from definition: %s.

[#log-ref-log-ref-ERR_SCHEMA_HAS_WARNINGS_341]
ID: 341::
Severity: ERROR

+
Message: There should be no warnings on the schema, but instead got %d warnings: %s.

[#log-ref-log-ref-ERR_MATCHING_RULE_USE_CANNOT_REGISTER_342]
ID: 342::
Severity: ERROR

+
Message: Matching rule use could not be registered from definition: %s.

[#log-ref-log-ref-ERR_OBJECT_CLASS_CANNOT_REGISTER_343]
ID: 343::
Severity: ERROR

+
Message: Object class could not be registered from definition: %s.

[#log-ref-log-ref-ERR_PARSING_OBJECTCLASS_OID_344]
ID: 344::
Severity: ERROR

+
Message: Unable to parse the OID from the provided definition of objectclass: '%s'.

[#log-ref-log-ref-ERR_PARSING_ATTRIBUTE_TYPE_OID_345]
ID: 345::
Severity: ERROR

+
Message: Unable to parse the OID from the provided definition of attribute type: '%s'.

[#log-ref-log-ref-ERR_PARSING_LDAP_SYNTAX_OID_346]
ID: 346::
Severity: ERROR

+
Message: Unable to parse the OID from the provided definition of ldap syntax: '%s'.

[#log-ref-log-ref-ERR_PARSING_MATCHING_RULE_USE_OID_347]
ID: 347::
Severity: ERROR

+
Message: Unable to parse the OID from the provided definition of matching rule use: '%s' .

[#log-ref-log-ref-ERR_DIT_CONTENT_RULE_CANNOT_REGISTER_348]
ID: 348::
Severity: ERROR

+
Message: DIT content rule could not be registered from definition: %s.

[#log-ref-log-ref-ERR_NAME_FORM_CANNOT_REGISTER_349]
ID: 349::
Severity: ERROR

+
Message: Name form could not be registered from definition: %s.

[#log-ref-log-ref-ERR_PARSING_NAME_FORM_OID_350]
ID: 350::
Severity: ERROR

+
Message: Unable to parse the OID from the provided definition of name form: '%s'.

[#log-ref-log-ref-ERR_PARSING_DIT_CONTENT_RULE_OID_351]
ID: 351::
Severity: ERROR

+
Message: Unable to parse the OID from the provided definition of DIT content rule: '%s'.

[#log-ref-log-ref-ERR_PARSING_DIT_STRUCTURE_RULE_RULEID_352]
ID: 352::
Severity: ERROR

+
Message: Unable to parse the rule ID from the provided definition of DIT structure rule: '%s' .

--


[#TASK]
=== Log Message Category: TASK

--

[#log-ref-log-ref-ERR_TASK_CANNOT_ENABLE_BACKEND_1]
ID: 1::
Severity: ERROR

+
Message: The task could not enable a backend: %s.

[#log-ref-log-ref-ERR_TASK_CANNOT_DISABLE_BACKEND_2]
ID: 2::
Severity: ERROR

+
Message: The task could not disable a backend: %s.

[#log-ref-log-ref-ERR_TASK_ADDSCHEMAFILE_NO_FILENAME_5]
ID: 5::
Severity: ERROR

+
Message: Unable to add one or more files to the server schema because no schema file names were provided in attribute %s of task entry %s.

[#log-ref-log-ref-ERR_TASK_ADDSCHEMAFILE_NO_SUCH_FILE_6]
ID: 6::
Severity: ERROR

+
Message: Unable to add one or more files to the server schema because the specified schema file %s does not exist in schema directory %s.

[#log-ref-log-ref-ERR_TASK_ADDSCHEMAFILE_ERROR_CHECKING_FOR_FILE_7]
ID: 7::
Severity: ERROR

+
Message: Unable to add one or more files to the server schema because an error occurred while attempting to determine whether file %s exists in schema directory %s: %s.

[#log-ref-log-ref-ERR_TASK_ADDSCHEMAFILE_ERROR_LOADING_SCHEMA_FILE_8]
ID: 8::
Severity: ERROR

+
Message: An error occurred while attempting to load the contents of schema file %s into the server schema: %s.

[#log-ref-log-ref-ERR_TASK_ADDSCHEMAFILE_CANNOT_LOCK_SCHEMA_9]
ID: 9::
Severity: ERROR

+
Message: Unable to add one or more files to the server schema because the server was unable to obtain a write lock on the schema entry %s after multiple attempts.

[#log-ref-log-ref-ERR_TASK_ADDSCHEMAFILE_INSUFFICIENT_PRIVILEGES_10]
ID: 10::
Severity: ERROR

+
Message: You do not have sufficient privileges to modify the server schema.

[#log-ref-log-ref-ERR_TASK_BACKUP_INSUFFICIENT_PRIVILEGES_11]
ID: 11::
Severity: ERROR

+
Message: You do not have sufficient privileges to initiate a Directory Server backup.

[#log-ref-log-ref-ERR_TASK_RESTORE_INSUFFICIENT_PRIVILEGES_12]
ID: 12::
Severity: ERROR

+
Message: You do not have sufficient privileges to initiate a Directory Server restore.

[#log-ref-log-ref-ERR_TASK_LDIFIMPORT_INSUFFICIENT_PRIVILEGES_13]
ID: 13::
Severity: ERROR

+
Message: You do not have sufficient privileges to initiate an LDIF import.

[#log-ref-log-ref-ERR_TASK_LDIFEXPORT_INSUFFICIENT_PRIVILEGES_14]
ID: 14::
Severity: ERROR

+
Message: You do not have sufficient privileges to initiate an LDIF export.

[#log-ref-log-ref-ERR_TASK_SHUTDOWN_INSUFFICIENT_RESTART_PRIVILEGES_15]
ID: 15::
Severity: ERROR

+
Message: You do not have sufficient privileges to initiate a Directory Server restart.

[#log-ref-log-ref-ERR_TASK_SHUTDOWN_INSUFFICIENT_SHUTDOWN_PRIVILEGES_16]
ID: 16::
Severity: ERROR

+
Message: You do not have sufficient privileges to initiate a Directory Server shutdown.

[#log-ref-log-ref-ERR_TASK_ADDSCHEMAFILE_CANNOT_NOTIFY_SYNC_PROVIDER_17]
ID: 17::
Severity: ERROR

+
Message: An error occurred while attempting to notify a synchronization provider of type %s about the schema changes made by the add schema file task: %s.

[#log-ref-log-ref-ERR_TASK_INDEXREBUILD_INSUFFICIENT_PRIVILEGES_18]
ID: 18::
Severity: ERROR

+
Message: You do not have sufficient privileges to initiate an index rebuild.

[#log-ref-log-ref-ERR_TASK_INITIALIZE_INVALID_DN_20]
ID: 20::
Severity: ERROR

+
Message: Invalid DN provided with the Initialize task.

[#log-ref-log-ref-ERR_TASK_ENTERLOCKDOWN_NOT_ROOT_21]
ID: 21::
Severity: ERROR

+
Message: Only users with the SERVER_LOCKDOWN privilege may place the server in lockdown mode.

[#log-ref-log-ref-ERR_TASK_ENTERLOCKDOWN_NOT_LOOPBACK_22]
ID: 22::
Severity: ERROR

+
Message: Only users with the SERVER_LOCKDOWN privilege connected from a loopback address may place the server in lockdown mode.

[#log-ref-log-ref-ERR_TASK_LEAVELOCKDOWN_NOT_ROOT_23]
ID: 23::
Severity: ERROR

+
Message: Only users with the SERVER_LOCKDOWN privilege may cause the server to leave lockdown mode.

[#log-ref-log-ref-ERR_TASK_LEAVELOCKDOWN_NOT_LOOPBACK_24]
ID: 24::
Severity: ERROR

+
Message: Only users with the SERVER_LOCKDOWN privilege connected from a loopback address may cause the server to leave lockdown mode.

[#log-ref-log-ref-ERR_TASK_DISCONNECT_NO_PRIVILEGE_25]
ID: 25::
Severity: ERROR

+
Message: You do not have sufficient privileges to terminate client connections.

[#log-ref-log-ref-ERR_TASK_DISCONNECT_INVALID_CONN_ID_26]
ID: 26::
Severity: ERROR

+
Message: Unable to decode value %s as an integer connection ID.

[#log-ref-log-ref-ERR_TASK_DISCONNECT_NO_CONN_ID_27]
ID: 27::
Severity: ERROR

+
Message: Attribute %s must be provided to specify the connection ID for the client to disconnect.

[#log-ref-log-ref-ERR_TASK_DISCONNECT_INVALID_NOTIFY_CLIENT_28]
ID: 28::
Severity: ERROR

+
Message: Unable to decode value %s as an indication of whether to notify the client before disconnecting it. The provided value should be either 'true' or 'false'.

[#log-ref-log-ref-ERR_TASK_DISCONNECT_NO_SUCH_CONNECTION_30]
ID: 30::
Severity: ERROR

+
Message: There is no client connection with connection ID %s.

[#log-ref-log-ref-ERR_TASK_INITIALIZE_INVALID_GENERATION_ID_103]
ID: 103::
Severity: ERROR

+
Message: Invalid generation ID provided with the task.

[#log-ref-log-ref-ERR_TASK_LDAP_FAILED_TO_CONNECT_WRONG_PORT_106]
ID: 106::
Severity: ERROR

+
Message: Unable to connect to the server at %s on port %s. Check this port is an administration port.

[#log-ref-log-ref-ERR_TASK_INDEXREBUILD_ALL_ERROR_108]
ID: 108::
Severity: ERROR

+
Message: Index option cannot be specified when the rebuildAll or rebuildDegraded option is used.

[#log-ref-log-ref-ERR_TASK_INVALID_ATTRIBUTE_VALUE_110]
ID: 110::
Severity: ERROR

+
Message: Attribute %s has an invalid value. Reason: %s.

[#log-ref-log-ref-ERR_TASK_RESET_CHANGE_NUMBER_CHANGELOG_NOT_FOUND_112]
ID: 112::
Severity: ERROR

+
Message: No changelog database was found for baseDN '%s'. Either the baseDN is not replicated or its changelog has not been enabled in this server.

[#log-ref-log-ref-ERR_TASK_RESET_CHANGE_NUMBER_NO_RSES_113]
ID: 113::
Severity: ERROR

+
Message: The change number index cannot be reset because this OpenDJ instance does not appear to be a replication server.

[#log-ref-log-ref-ERR_TASK_RESET_CHANGE_NUMBER_INVALID_114]
ID: 114::
Severity: ERROR

+
Message: Invalid change number (%d) specified, it must be greater than zero.

[#log-ref-log-ref-ERR_TASK_RESET_CHANGE_NUMBER_FAILED_115]
ID: 115::
Severity: ERROR

+
Message: Unable to reset the change number index: %s.

--


[#TOOL]
=== Log Message Category: TOOL

--

[#log-ref-log-ref-ERR_TOOLS_CANNOT_CREATE_SSL_CONNECTION_1]
ID: 1::
Severity: ERROR

+
Message: Unable to create an SSL connection to the server: %s.

[#log-ref-log-ref-ERR_TOOLS_SSL_CONNECTION_NOT_INITIALIZED_2]
ID: 2::
Severity: ERROR

+
Message: Unable to create an SSL connection to the server because the connection factory has not been initialized.

[#log-ref-log-ref-ERR_TOOLS_CANNOT_LOAD_KEYSTORE_FILE_3]
ID: 3::
Severity: ERROR

+
Message: Cannot load the key store file: %s.

[#log-ref-log-ref-ERR_TOOLS_CANNOT_INIT_KEYMANAGER_4]
ID: 4::
Severity: ERROR

+
Message: Cannot initialize the key manager for the key store:%s.

[#log-ref-log-ref-ERR_TOOLS_CANNOT_LOAD_TRUSTSTORE_FILE_5]
ID: 5::
Severity: ERROR

+
Message: Cannot load the key store file: %s.

[#log-ref-log-ref-ERR_TOOLS_CANNOT_INIT_TRUSTMANAGER_6]
ID: 6::
Severity: ERROR

+
Message: Cannot initialize the key manager for the key store:%s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_ARGS_16]
ID: 16::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to initialize the command-line arguments: %s.

[#log-ref-log-ref-ERR_ERROR_PARSING_ARGS_17]
ID: 17::
Severity: ERROR

+
Message: An error occurred while parsing the command-line arguments: %s.

[#log-ref-log-ref-ERR_ENCPW_NO_CLEAR_PW_18]
ID: 18::
Severity: ERROR

+
Message: No clear-text password was specified. Use --%s, --%s or --%s to specify the password to encode.

[#log-ref-log-ref-ERR_ENCPW_NO_SCHEME_19]
ID: 19::
Severity: ERROR

+
Message: No password storage scheme was specified. Use the --%s argument to specify the storage scheme.

[#log-ref-log-ref-ERR_SERVER_BOOTSTRAP_ERROR_20]
ID: 20::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to bootstrap the Directory Server client-side code: %s.

[#log-ref-log-ref-ERR_CANNOT_LOAD_CONFIG_21]
ID: 21::
Severity: ERROR

+
Message: An error occurred while trying to load the Directory Server configuration: %s.

[#log-ref-log-ref-ERR_CANNOT_LOAD_SCHEMA_22]
ID: 22::
Severity: ERROR

+
Message: An error occurred while trying to load the Directory Server schema: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_CORE_CONFIG_23]
ID: 23::
Severity: ERROR

+
Message: An error occurred while trying to initialize the core Directory Server configuration: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_STORAGE_SCHEMES_24]
ID: 24::
Severity: ERROR

+
Message: An error occurred while trying to initialize the Directory Server password storage schemes: %s.

[#log-ref-log-ref-ERR_ENCPW_NO_STORAGE_SCHEMES_25]
ID: 25::
Severity: ERROR

+
Message: No password storage schemes have been configured for use in the Directory Server.

[#log-ref-log-ref-ERR_ENCPW_NO_SUCH_SCHEME_26]
ID: 26::
Severity: ERROR

+
Message: Password storage scheme "%s" is not configured for use in the Directory Server.

[#log-ref-log-ref-ERR_ENCPW_ENCODED_PASSWORD_29]
ID: 29::
Severity: ERROR

+
Message: Encoded Password: "%s".

[#log-ref-log-ref-ERR_ENCPW_CANNOT_ENCODE_30]
ID: 30::
Severity: ERROR

+
Message: An error occurred while attempting to encode the clear-text password: %s.

[#log-ref-log-ref-ERR_LDIFEXPORT_CANNOT_PARSE_EXCLUDE_FILTER_52]
ID: 52::
Severity: ERROR

+
Message: Unable to decode exclude filter string "%s" as a valid search filter: %s.

[#log-ref-log-ref-ERR_LDIFEXPORT_CANNOT_PARSE_INCLUDE_FILTER_53]
ID: 53::
Severity: ERROR

+
Message: Unable to decode include filter string "%s" as a valid search filter: %s.

[#log-ref-log-ref-ERR_CANNOT_DECODE_BASE_DN_54]
ID: 54::
Severity: ERROR

+
Message: Unable to decode base DN string "%s" as a valid distinguished name: %s.

[#log-ref-log-ref-ERR_LDIFEXPORT_MULTIPLE_BACKENDS_FOR_ID_55]
ID: 55::
Severity: ERROR

+
Message: Multiple Directory Server backends are configured with the requested backend ID "%s".

[#log-ref-log-ref-ERR_LDIFEXPORT_NO_BACKENDS_FOR_ID_56]
ID: 56::
Severity: ERROR

+
Message: None of the Directory Server backends are configured with the requested backend ID "%s".

[#log-ref-log-ref-ERR_LDIFEXPORT_CANNOT_DECODE_EXCLUDE_BASE_57]
ID: 57::
Severity: ERROR

+
Message: Unable to decode exclude branch string "%s" as a valid distinguished name: %s.

[#log-ref-log-ref-ERR_LDIFEXPORT_CANNOT_DECODE_WRAP_COLUMN_AS_INTEGER_58]
ID: 58::
Severity: ERROR

+
Message: Unable to decode wrap column value "%s" as an integer.

[#log-ref-log-ref-ERR_LDIFEXPORT_ERROR_DURING_EXPORT_59]
ID: 59::
Severity: ERROR

+
Message: An error occurred while attempting to process the LDIF export: %s.

[#log-ref-log-ref-ERR_CANNOT_DECODE_BACKEND_BASE_DN_60]
ID: 60::
Severity: ERROR

+
Message: Unable to decode the backend configuration base DN string "%s" as a valid DN: %s.

[#log-ref-log-ref-ERR_CANNOT_RETRIEVE_BACKEND_BASE_ENTRY_61]
ID: 61::
Severity: ERROR

+
Message: Unable to retrieve the backend configuration base entry "%s" from the server configuration: %s.

[#log-ref-log-ref-ERR_CANNOT_DETERMINE_BACKEND_CLASS_62]
ID: 62::
Severity: ERROR

+
Message: Cannot determine the name of the Java class providing the logic for the backend defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_CANNOT_LOAD_BACKEND_CLASS_63]
ID: 63::
Severity: ERROR

+
Message: Unable to load class %s referenced in configuration entry %s for use as a Directory Server backend: %s.

[#log-ref-log-ref-ERR_CANNOT_INSTANTIATE_BACKEND_CLASS_64]
ID: 64::
Severity: ERROR

+
Message: Unable to create an instance of class %s referenced in configuration entry %s as a Directory Server backend: %s.

[#log-ref-log-ref-ERR_NO_BASES_FOR_BACKEND_65]
ID: 65::
Severity: ERROR

+
Message: No base DNs have been defined in backend configuration entry %s. This backend will not be evaluated.

[#log-ref-log-ref-ERR_CANNOT_DETERMINE_BASES_FOR_BACKEND_66]
ID: 66::
Severity: ERROR

+
Message: Unable to determine the set of base DNs defined in backend configuration entry %s: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_PARSE_EXCLUDE_FILTER_89]
ID: 89::
Severity: ERROR

+
Message: Unable to decode exclude filter string "%s" as a valid search filter: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_PARSE_INCLUDE_FILTER_90]
ID: 90::
Severity: ERROR

+
Message: Unable to decode include filter string "%s" as a valid search filter: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_MULTIPLE_BACKENDS_FOR_ID_92]
ID: 92::
Severity: ERROR

+
Message: Imported branches or backend IDs can not span across multiple Directory Server backends.

[#log-ref-log-ref-ERR_LDIFIMPORT_NO_BACKENDS_FOR_ID_93]
ID: 93::
Severity: ERROR

+
Message: None of the Directory Server backends are configured with the requested backend ID or base DNs that include the specified branches.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_DECODE_EXCLUDE_BASE_94]
ID: 94::
Severity: ERROR

+
Message: Unable to decode exclude branch string "%s" as a valid distinguished name: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_OPEN_REJECTS_FILE_95]
ID: 95::
Severity: ERROR

+
Message: An error occurred while trying to open the rejects file %s for writing: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_ERROR_DURING_IMPORT_96]
ID: 96::
Severity: ERROR

+
Message: An error occurred while attempting to process the LDIF import: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_SEND_SIMPLE_BIND_136]
ID: 136::
Severity: ERROR

+
Message: Cannot send the simple bind request: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_READ_BIND_RESPONSE_137]
ID: 137::
Severity: ERROR

+
Message: Cannot read the bind response from the server. The port you are using may require a secured communication (--useSSL). %s.

[#log-ref-log-ref-ERR_LDAPAUTH_SERVER_DISCONNECT_138]
ID: 138::
Severity: ERROR

+
Message: The Directory Server indicated that it was closing the connection to the client (result code %d, message "%s".

[#log-ref-log-ref-ERR_LDAPAUTH_UNEXPECTED_EXTENDED_RESPONSE_139]
ID: 139::
Severity: ERROR

+
Message: The Directory Server sent an unexpected extended response message to the client: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_UNEXPECTED_RESPONSE_140]
ID: 140::
Severity: ERROR

+
Message: The Directory Server sent an unexpected response message to the client: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_SIMPLE_BIND_FAILED_141]
ID: 141::
Severity: ERROR

+
Message: The simple bind attempt failed.

[#log-ref-log-ref-ERR_LDAPAUTH_NO_SASL_MECHANISM_142]
ID: 142::
Severity: ERROR

+
Message: A SASL bind was requested but no SASL mechanism was specified.

[#log-ref-log-ref-ERR_LDAPAUTH_UNSUPPORTED_SASL_MECHANISM_143]
ID: 143::
Severity: ERROR

+
Message: The requested SASL mechanism "%s" is not supported by this client.

[#log-ref-log-ref-ERR_LDAPAUTH_TRACE_SINGLE_VALUED_144]
ID: 144::
Severity: ERROR

+
Message: The trace SASL property may only be given a single value.

[#log-ref-log-ref-ERR_LDAPAUTH_INVALID_SASL_PROPERTY_145]
ID: 145::
Severity: ERROR

+
Message: Property "%s" is not allowed for the %s SASL mechanism.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_SEND_SASL_BIND_146]
ID: 146::
Severity: ERROR

+
Message: Cannot send the SASL %S bind request: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_SASL_BIND_FAILED_147]
ID: 147::
Severity: ERROR

+
Message: The SASL %s bind attempt failed.

[#log-ref-log-ref-ERR_LDAPAUTH_NO_SASL_PROPERTIES_148]
ID: 148::
Severity: ERROR

+
Message: No SASL properties were provided for use with the %s mechanism.

[#log-ref-log-ref-ERR_LDAPAUTH_AUTHID_SINGLE_VALUED_149]
ID: 149::
Severity: ERROR

+
Message: The "authid" SASL property only accepts a single value.

[#log-ref-log-ref-ERR_LDAPAUTH_SASL_AUTHID_REQUIRED_150]
ID: 150::
Severity: ERROR

+
Message: The "authid" SASL property is required for use with the %s mechanism.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_SEND_INITIAL_SASL_BIND_151]
ID: 151::
Severity: ERROR

+
Message: Cannot send the initial bind request in the multi-stage %s bind to the server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_READ_INITIAL_BIND_RESPONSE_152]
ID: 152::
Severity: ERROR

+
Message: Cannot read the initial %s bind response from the server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_UNEXPECTED_INITIAL_BIND_RESPONSE_153]
ID: 153::
Severity: ERROR

+
Message: The client received an unexpected intermediate bind response. The "SASL bind in progress" result was expected for the first response in the multi-stage %s bind process, but the bind response had a result code of %d (%s) and an error message of "%s".

[#log-ref-log-ref-ERR_LDAPAUTH_NO_CRAMMD5_SERVER_CREDENTIALS_154]
ID: 154::
Severity: ERROR

+
Message: The initial bind response from the server did not include any server SASL credentials containing the challenge information needed to complete the CRAM-MD5 authentication.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_INITIALIZE_MD5_DIGEST_155]
ID: 155::
Severity: ERROR

+
Message: An unexpected error occurred while trying to initialize the MD5 digest generator: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_SEND_SECOND_SASL_BIND_156]
ID: 156::
Severity: ERROR

+
Message: Cannot send the second bind request in the multi-stage %s bind to the server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_READ_SECOND_BIND_RESPONSE_157]
ID: 157::
Severity: ERROR

+
Message: Cannot read the second %s bind response from the server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_NO_ALLOWED_SASL_PROPERTIES_158]
ID: 158::
Severity: ERROR

+
Message: One or more SASL properties were provided, but the %s mechanism does not take any SASL properties.

[#log-ref-log-ref-ERR_LDAPAUTH_AUTHZID_SINGLE_VALUED_159]
ID: 159::
Severity: ERROR

+
Message: The "authzid" SASL property only accepts a single value.

[#log-ref-log-ref-ERR_LDAPAUTH_REALM_SINGLE_VALUED_160]
ID: 160::
Severity: ERROR

+
Message: The "realm" SASL property only accepts a single value.

[#log-ref-log-ref-ERR_LDAPAUTH_QOP_SINGLE_VALUED_161]
ID: 161::
Severity: ERROR

+
Message: The "qop" SASL property only accepts a single value.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_QOP_NOT_SUPPORTED_162]
ID: 162::
Severity: ERROR

+
Message: The "%s" QoP mode is not supported by this client. Only the "auth" mode is currently available for use.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_INVALID_QOP_163]
ID: 163::
Severity: ERROR

+
Message: The specified DIGEST-MD5 quality of protection mode "%s" is not valid. The only QoP mode currently supported is "auth".

[#log-ref-log-ref-ERR_LDAPAUTH_DIGEST_URI_SINGLE_VALUED_164]
ID: 164::
Severity: ERROR

+
Message: The "digest-uri" SASL property only accepts a single value.

[#log-ref-log-ref-ERR_LDAPAUTH_NO_DIGESTMD5_SERVER_CREDENTIALS_165]
ID: 165::
Severity: ERROR

+
Message: The initial bind response from the server did not include any server SASL credentials containing the challenge information needed to complete the DIGEST-MD5 authentication.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_INVALID_TOKEN_IN_CREDENTIALS_166]
ID: 166::
Severity: ERROR

+
Message: The DIGEST-MD5 credentials provided by the server contained an invalid token of "%s" starting at position %d.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_INVALID_CHARSET_167]
ID: 167::
Severity: ERROR

+
Message: The DIGEST-MD5 credentials provided by the server specified the use of the "%s" character set. The character set that may be specified in the DIGEST-MD5 credentials is "utf-8".

[#log-ref-log-ref-ERR_LDAPAUTH_REQUESTED_QOP_NOT_SUPPORTED_BY_SERVER_168]
ID: 168::
Severity: ERROR

+
Message: The requested QoP mode of "%s" is not listed as supported by the Directory Server. The Directory Server's list of supported QoP modes is: "%s".

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_NO_NONCE_169]
ID: 169::
Severity: ERROR

+
Message: The server SASL credentials provided in response to the initial DIGEST-MD5 bind request did not include the nonce to use to generate the authentication digests.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_CANNOT_CREATE_RESPONSE_DIGEST_170]
ID: 170::
Severity: ERROR

+
Message: An error occurred while attempting to generate the response digest for the DIGEST-MD5 bind request: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_NO_RSPAUTH_CREDS_171]
ID: 171::
Severity: ERROR

+
Message: The DIGEST-MD5 bind response from the server did not include the "rspauth" element to provide a digest of the response authentication information.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_COULD_NOT_DECODE_RSPAUTH_172]
ID: 172::
Severity: ERROR

+
Message: An error occurred while trying to decode the rspauth element of the DIGEST-MD5 bind response from the server as a hexadecimal string: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_COULD_NOT_CALCULATE_RSPAUTH_173]
ID: 173::
Severity: ERROR

+
Message: An error occurred while trying to calculate the expected rspauth element to compare against the value included in the DIGEST-MD5 response from the server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_RSPAUTH_MISMATCH_174]
ID: 174::
Severity: ERROR

+
Message: The rpsauth element included in the DIGEST-MD5 bind response from the Directory Server was different from the expected value calculated by the client.

[#log-ref-log-ref-ERR_LDAPAUTH_DIGESTMD5_INVALID_CLOSING_QUOTE_POS_175]
ID: 175::
Severity: ERROR

+
Message: The DIGEST-MD5 response challenge could not be parsed because it had an invalid quotation mark at position %d.

[#log-ref-log-ref-ERR_LDAPAUTH_KDC_SINGLE_VALUED_184]
ID: 184::
Severity: ERROR

+
Message: The "kdc" SASL property only accepts a single value.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_INVALID_QOP_185]
ID: 185::
Severity: ERROR

+
Message: The specified GSSAPI quality of protection mode "%s" is not valid. The only QoP mode currently supported is "auth".

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_CANNOT_CREATE_JAAS_CONFIG_186]
ID: 186::
Severity: ERROR

+
Message: An error occurred while trying to create the temporary JAAS configuration for GSSAPI authentication: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_LOCAL_AUTHENTICATION_FAILED_187]
ID: 187::
Severity: ERROR

+
Message: An error occurred while attempting to perform local authentication to the Kerberos realm: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_REMOTE_AUTHENTICATION_FAILED_188]
ID: 188::
Severity: ERROR

+
Message: An error occurred while attempting to perform GSSAPI authentication to the Directory Server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_NONSASL_RUN_INVOCATION_189]
ID: 189::
Severity: ERROR

+
Message: The LDAPAuthenticationHandler.run() method was called for a non-SASL bind. The backtrace for this call is %s.

[#log-ref-log-ref-ERR_LDAPAUTH_UNEXPECTED_RUN_INVOCATION_190]
ID: 190::
Severity: ERROR

+
Message: The LDAPAuthenticationHandler.run() method was called for a SASL bind with an unexpected mechanism of "%s". The backtrace for this call is %s.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_CANNOT_CREATE_SASL_CLIENT_191]
ID: 191::
Severity: ERROR

+
Message: An error occurred while attempting to create a SASL client to process the GSSAPI authentication: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_CANNOT_CREATE_INITIAL_CHALLENGE_192]
ID: 192::
Severity: ERROR

+
Message: An error occurred while attempting to create the initial challenge for GSSAPI authentication: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_CANNOT_VALIDATE_SERVER_CREDS_193]
ID: 193::
Severity: ERROR

+
Message: An error occurred while trying to validate the SASL credentials provided by the Directory Server in the GSSAPI bind response: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_UNEXPECTED_SUCCESS_RESPONSE_194]
ID: 194::
Severity: ERROR

+
Message: The Directory Server unexpectedly returned a success response to the client even though the client does not believe that the GSSAPI negotiation is complete.

[#log-ref-log-ref-ERR_LDAPAUTH_GSSAPI_BIND_FAILED_195]
ID: 195::
Severity: ERROR

+
Message: The GSSAPI bind attempt failed.

[#log-ref-log-ref-ERR_LDAPAUTH_NONSASL_CALLBACK_INVOCATION_196]
ID: 196::
Severity: ERROR

+
Message: The LDAPAuthenticationHandler.handle() method was called for a non-SASL bind. The backtrace for this call is %s.

[#log-ref-log-ref-ERR_LDAPAUTH_UNEXPECTED_GSSAPI_CALLBACK_197]
ID: 197::
Severity: ERROR

+
Message: The LDAPAuthenticationHandler.handle() method was called during a GSSAPI bind attempt with an unexpected callback type of %s.

[#log-ref-log-ref-ERR_LDAPAUTH_UNEXPECTED_CALLBACK_INVOCATION_198]
ID: 198::
Severity: ERROR

+
Message: The LDAPAuthenticationHandler.handle() method was called for an unexpected SASL mechanism of %s. The backtrace for this call is %s.

[#log-ref-log-ref-ERR_DESCRIPTION_INVALID_VERSION_201]
ID: 201::
Severity: ERROR

+
Message: Invalid LDAP version number '%s'. Allowed values are 2 and 3.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_SEND_WHOAMI_REQUEST_202]
ID: 202::
Severity: ERROR

+
Message: Cannot send the 'Who Am I?' request to the Directory Server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_CANNOT_READ_WHOAMI_RESPONSE_203]
ID: 203::
Severity: ERROR

+
Message: Cannot read the 'Who Am I?' response from the Directory Server: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_WHOAMI_FAILED_204]
ID: 204::
Severity: ERROR

+
Message: The 'Who Am I?' request was rejected by the Directory Server.

[#log-ref-log-ref-ERR_SEARCH_INVALID_SEARCH_SCOPE_205]
ID: 205::
Severity: ERROR

+
Message: Invalid scope '%s' specified for the search request.

[#log-ref-log-ref-ERR_SEARCH_NO_FILTERS_206]
ID: 206::
Severity: ERROR

+
Message: No filters specified for the search request.

[#log-ref-log-ref-ERR_VERIFYINDEX_ERROR_DURING_VERIFY_210]
ID: 210::
Severity: ERROR

+
Message: An error occurred while attempting to perform index verification: %s.

[#log-ref-log-ref-ERR_VERIFYINDEX_VERIFY_CLEAN_REQUIRES_SINGLE_INDEX_211]
ID: 211::
Severity: ERROR

+
Message: Only one index at a time may be verified for cleanliness.

[#log-ref-log-ref-ERR_BACKEND_NO_INDEXING_SUPPORT_212]
ID: 212::
Severity: ERROR

+
Message: The backend does not support indexing.

[#log-ref-log-ref-ERR_LDIFEXPORT_CANNOT_EXPORT_BACKEND_213]
ID: 213::
Severity: ERROR

+
Message: The Directory Server backend with backend ID "%s" does not provide a mechanism for performing LDIF exports.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_IMPORT_214]
ID: 214::
Severity: ERROR

+
Message: The Directory Server backend with backend ID %s does not provide a mechanism for performing LDIF imports.

[#log-ref-log-ref-ERR_CANNOT_DETERMINE_BACKEND_ID_217]
ID: 217::
Severity: ERROR

+
Message: Cannot determine the backend ID for the backend defined in configuration entry %s: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_DECODE_INCLUDE_BASE_218]
ID: 218::
Severity: ERROR

+
Message: Unable to decode include branch string "%s" as a valid distinguished name: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_INVALID_INCLUDE_BASE_219]
ID: 219::
Severity: ERROR

+
Message: Provided include base DN "%s" is not handled by the backend with backend ID %s.

[#log-ref-log-ref-ERR_MULTIPLE_BACKENDS_FOR_BASE_230]
ID: 230::
Severity: ERROR

+
Message: Multiple Directory Server backends are configured to support base DN "%s".

[#log-ref-log-ref-ERR_NO_BACKENDS_FOR_BASE_231]
ID: 231::
Severity: ERROR

+
Message: None of the Directory Server backends are configured to support the requested base DN "%s".

[#log-ref-log-ref-ERR_LDIFEXPORT_INVALID_INCLUDE_BASE_242]
ID: 242::
Severity: ERROR

+
Message: Provided include base DN "%s" is not handled by the backend with backend ID %s.

[#log-ref-log-ref-ERR_BACKUPDB_NO_BACKENDS_FOR_ID_261]
ID: 261::
Severity: ERROR

+
Message: None of the Directory Server backends are configured with the requested backend ID "%s".

[#log-ref-log-ref-ERR_BACKUPDB_CANNOT_BACKUP_264]
ID: 264::
Severity: ERROR

+
Message: The target backend %s cannot be backed up using the requested configuration.

[#log-ref-log-ref-ERR_BACKUPDB_ERROR_DURING_BACKUP_265]
ID: 265::
Severity: ERROR

+
Message: An error occurred while attempting to back up backend %s with the requested configuration: %s.

[#log-ref-log-ref-ERR_BACKUPDB_CANNOT_MIX_BACKUP_ALL_AND_BACKEND_ID_275]
ID: 275::
Severity: ERROR

+
Message: The %s and %s arguments may not be used together. Exactly one of them must be provided.

[#log-ref-log-ref-ERR_BACKUPDB_NEED_BACKUP_ALL_OR_BACKEND_ID_276]
ID: 276::
Severity: ERROR

+
Message: Neither the %s argument nor the %s argument was provided. Exactly one of them is required.

[#log-ref-log-ref-ERR_BACKUPDB_CANNOT_CREATE_BACKUP_DIR_277]
ID: 277::
Severity: ERROR

+
Message: An error occurred while attempting to create the backup directory %s: %s.

[#log-ref-log-ref-ERR_BACKUPDB_CANNOT_PARSE_BACKUP_DESCRIPTOR_281]
ID: 281::
Severity: ERROR

+
Message: An error occurred while attempting to parse the backup descriptor file %s: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_CRYPTO_MANAGER_284]
ID: 284::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the crypto manager: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_SUBENTRY_MANAGER_285]
ID: 285::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the subentry manager: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_ROOTDN_MANAGER_286]
ID: 286::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the root DN manager: %s.

[#log-ref-log-ref-ERR_BACKUPDB_INCREMENTAL_BASE_REQUIRES_INCREMENTAL_288]
ID: 288::
Severity: ERROR

+
Message: The use of the %s argument requires that the %s argument is also provided.

[#log-ref-log-ref-ERR_RESTOREDB_CANNOT_READ_BACKUP_DIRECTORY_304]
ID: 304::
Severity: ERROR

+
Message: An error occurred while attempting to examine the set of backups contained in backup directory %s: %s.

[#log-ref-log-ref-ERR_RESTOREDB_INVALID_BACKUP_ID_313]
ID: 313::
Severity: ERROR

+
Message: The requested backup ID %s does not exist in %s.

[#log-ref-log-ref-ERR_RESTOREDB_NO_BACKUPS_IN_DIRECTORY_314]
ID: 314::
Severity: ERROR

+
Message: There are no Directory Server backups contained in %s.

[#log-ref-log-ref-ERR_RESTOREDB_NO_BACKENDS_FOR_DN_315]
ID: 315::
Severity: ERROR

+
Message: The backups contained in directory %s were taken from a Directory Server backend defined in configuration entry %s but no such backend is available.

[#log-ref-log-ref-ERR_RESTOREDB_CANNOT_RESTORE_316]
ID: 316::
Severity: ERROR

+
Message: The Directory Server backend configured with backend ID %s does not provide a mechanism for restoring backups.

[#log-ref-log-ref-ERR_RESTOREDB_ERROR_DURING_BACKUP_317]
ID: 317::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to restore backup %s from %s: %s.

[#log-ref-log-ref-ERR_RESTOREDB_ENCRYPT_OR_SIGN_REQUIRES_ONLINE_318]
ID: 318::
Severity: ERROR

+
Message: Restoring an encrypted or signed backup requires a connection to an online server.

[#log-ref-log-ref-ERR_BACKUPDB_ENCRYPT_OR_SIGN_REQUIRES_ONLINE_325]
ID: 325::
Severity: ERROR

+
Message: The use of the %s argument or the %s argument requires a connection to an online server instance.

[#log-ref-log-ref-ERR_BACKUPDB_SIGN_REQUIRES_HASH_326]
ID: 326::
Severity: ERROR

+
Message: The use of the %s argument requires that the %s argument is also provided.

[#log-ref-log-ref-ERR_BACKUPDB_CANNOT_LOCK_BACKEND_328]
ID: 328::
Severity: ERROR

+
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has exclusive access to this backend (e.g., a restore or an LDIF import). This backend will not be archived.

[#log-ref-log-ref-ERR_RESTOREDB_CANNOT_LOCK_BACKEND_330]
ID: 330::
Severity: ERROR

+
Message: An error occurred while attempting to acquire an exclusive lock for backend %s: %s. This generally means some other process is still using this backend (e.g., it is in use by the Directory Server or a backup or LDIF export is in progress). The restore cannot continue.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_LOCK_BACKEND_332]
ID: 332::
Severity: ERROR

+
Message: An error occurred while attempting to acquire an exclusive lock for backend %s: %s. This generally means some other process is still using this backend (e.g., it is in use by the Directory Server or a backup or LDIF export is in progress). The LDIF import cannot continue.

[#log-ref-log-ref-ERR_LDIFEXPORT_CANNOT_LOCK_BACKEND_334]
ID: 334::
Severity: ERROR

+
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The LDIF export cannot continue.

[#log-ref-log-ref-ERR_VERIFYINDEX_CANNOT_LOCK_BACKEND_336]
ID: 336::
Severity: ERROR

+
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The index verification cannot continue.

[#log-ref-log-ref-ERR_LDAP_ASSERTION_INVALID_FILTER_343]
ID: 343::
Severity: ERROR

+
Message: The search filter provided for the LDAP assertion control was invalid: %s.

[#log-ref-log-ref-ERR_LDAPMODIFY_PREREAD_CANNOT_DECODE_VALUE_349]
ID: 349::
Severity: ERROR

+
Message: An error occurred while trying to decode the entry contained in the value of the pre-read response control: %s.

[#log-ref-log-ref-ERR_LDAPMODIFY_POSTREAD_CANNOT_DECODE_VALUE_352]
ID: 352::
Severity: ERROR

+
Message: An error occurred while trying to decode the entry contained in the value of the post-read response control: %s.

[#log-ref-log-ref-ERR_PSEARCH_MISSING_DESCRIPTOR_356]
ID: 356::
Severity: ERROR

+
Message: The request to use the persistent search control did not include a descriptor that indicates the options to use with that control.

[#log-ref-log-ref-ERR_PSEARCH_DOESNT_START_WITH_PS_357]
ID: 357::
Severity: ERROR

+
Message: The persistent search descriptor %s did not start with the required 'ps' string.

[#log-ref-log-ref-ERR_PSEARCH_INVALID_CHANGE_TYPE_358]
ID: 358::
Severity: ERROR

+
Message: The provided change type value %s is invalid. The recognized change types are add, delete, modify, modifydn, and any.

[#log-ref-log-ref-ERR_PSEARCH_INVALID_CHANGESONLY_359]
ID: 359::
Severity: ERROR

+
Message: The provided changesOnly value %s is invalid. Allowed values are 1 to only return matching entries that have changed since the beginning of the search, or 0 to also include existing entries that match the search criteria.

[#log-ref-log-ref-ERR_PSEARCH_INVALID_RETURN_ECS_360]
ID: 360::
Severity: ERROR

+
Message: The provided returnECs value %s is invalid. Allowed values are 1 to request that the entry change notification control be included in updated entries, or 0 to exclude the control from matching entries.

[#log-ref-log-ref-ERR_LDAP_MATCHEDVALUES_INVALID_FILTER_365]
ID: 365::
Severity: ERROR

+
Message: The provided matched values filter was invalid: %s.

[#log-ref-log-ref-ERR_LDIF_FILE_CANNOT_OPEN_FOR_READ_366]
ID: 366::
Severity: ERROR

+
Message: An error occurred while attempting to open the LDIF file %s for reading: %s.

[#log-ref-log-ref-ERR_LDIF_FILE_READ_ERROR_367]
ID: 367::
Severity: ERROR

+
Message: An error occurred while attempting to read the contents of LDIF file %s: %s.

[#log-ref-log-ref-ERR_LDIF_FILE_INVALID_LDIF_ENTRY_368]
ID: 368::
Severity: ERROR

+
Message: Error at or near line %d in LDIF file %s: %s.

[#log-ref-log-ref-ERR_ENCPW_NO_SUCH_AUTH_SCHEME_371]
ID: 371::
Severity: ERROR

+
Message: Authentication password storage scheme "%s" is not configured for use in the Directory Server.

[#log-ref-log-ref-ERR_ENCPW_INVALID_ENCODED_AUTHPW_372]
ID: 372::
Severity: ERROR

+
Message: The provided password is not a valid encoded authentication password value: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_PWPOLICY_373]
ID: 373::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the password policy components: %s.

[#log-ref-log-ref-ERR_STOPDS_MUTUALLY_EXCLUSIVE_ARGUMENTS_395]
ID: 395::
Severity: ERROR

+
Message: ERROR: You may not provide both the %s and the %s arguments.

[#log-ref-log-ref-ERR_STOPDS_CANNOT_DECODE_STOP_TIME_396]
ID: 396::
Severity: ERROR

+
Message: ERROR: Unable to decode the provided stop time. It should be in the form YYYYMMDDhhmmssZ for UTC time or YYYYMMDDhhmmss for local time.

[#log-ref-log-ref-ERR_STOPDS_CANNOT_INITIALIZE_SSL_397]
ID: 397::
Severity: ERROR

+
Message: ERROR: Unable to perform SSL initialization: %s.

[#log-ref-log-ref-ERR_STOPDS_CANNOT_PARSE_SASL_OPTION_398]
ID: 398::
Severity: ERROR

+
Message: ERROR: The provided SASL option string "%s" could not be parsed in the form "name=value".

[#log-ref-log-ref-ERR_STOPDS_NO_SASL_MECHANISM_399]
ID: 399::
Severity: ERROR

+
Message: ERROR: One or more SASL options were provided, but none of them were the "mech" option to specify which SASL mechanism should be used.

[#log-ref-log-ref-ERR_STOPDS_CANNOT_DETERMINE_PORT_400]
ID: 400::
Severity: ERROR

+
Message: ERROR: Cannot parse the value of the %s argument as an integer value between 1 and 65535: %s.

[#log-ref-log-ref-ERR_STOPDS_CANNOT_CONNECT_401]
ID: 401::
Severity: ERROR

+
Message: ERROR: Cannot establish a connection to the Directory Server %s. Verify that the server is running and that the provided credentials are valid. Details: %s.

[#log-ref-log-ref-ERR_STOPDS_UNEXPECTED_CONNECTION_CLOSURE_402]
ID: 402::
Severity: ERROR

+
Message: NOTICE: The connection to the Directory Server was closed while waiting for a response to the shutdown request. This likely means that the server has started the shutdown process.

[#log-ref-log-ref-ERR_STOPDS_IO_ERROR_403]
ID: 403::
Severity: ERROR

+
Message: ERROR: An I/O error occurred while attempting to communicate with the Directory Server: %s.

[#log-ref-log-ref-ERR_STOPDS_DECODE_ERROR_404]
ID: 404::
Severity: ERROR

+
Message: ERROR: An error occurred while trying to decode the response from the server: %s.

[#log-ref-log-ref-ERR_STOPDS_INVALID_RESPONSE_TYPE_405]
ID: 405::
Severity: ERROR

+
Message: ERROR: Expected an add response message but got a %s message instead.

[#log-ref-log-ref-ERR_LDIFSEARCH_NO_FILTER_428]
ID: 428::
Severity: ERROR

+
Message: No search filter was specified. Either a filter file or an individual search filter must be provided.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_INITIALIZE_CONFIG_429]
ID: 429::
Severity: ERROR

+
Message: An error occurred while attempting to process the Directory Server configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_INITIALIZE_SCHEMA_430]
ID: 430::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server schema based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_PARSE_FILTER_431]
ID: 431::
Severity: ERROR

+
Message: An error occurred while attempting to parse search filter '%s': %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_PARSE_BASE_DN_432]
ID: 432::
Severity: ERROR

+
Message: An error occurred while attempting to parse base DN '%s': %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_PARSE_TIME_LIMIT_433]
ID: 433::
Severity: ERROR

+
Message: An error occurred while attempting to parse the time limit as an integer: %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_PARSE_SIZE_LIMIT_434]
ID: 434::
Severity: ERROR

+
Message: An error occurred while attempting to parse the size limit as an integer: %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_CREATE_READER_435]
ID: 435::
Severity: ERROR

+
Message: An error occurred while attempting to create the LDIF reader: %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_CREATE_WRITER_436]
ID: 436::
Severity: ERROR

+
Message: An error occurred while attempting to create the LDIF writer used to return matching entries: %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_READ_ENTRY_RECOVERABLE_439]
ID: 439::
Severity: ERROR

+
Message: An error occurred while attempting to read an entry from the LDIF content: %s. Skipping this entry and continuing processing.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_READ_ENTRY_FATAL_440]
ID: 440::
Severity: ERROR

+
Message: An error occurred while attempting to read an entry from the LDIF content: %s. Unable to continue processing.

[#log-ref-log-ref-ERR_LDIFSEARCH_ERROR_DURING_PROCESSING_441]
ID: 441::
Severity: ERROR

+
Message: An unexpected error occurred during search processing: %s.

[#log-ref-log-ref-ERR_LDIFSEARCH_CANNOT_INITIALIZE_JMX_442]
ID: 442::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server JMX subsystem based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_INITIALIZE_JMX_452]
ID: 452::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server JMX subsystem based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_INITIALIZE_CONFIG_453]
ID: 453::
Severity: ERROR

+
Message: An error occurred while attempting to process the Directory Server configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_INITIALIZE_SCHEMA_454]
ID: 454::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server schema based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_OPEN_SOURCE_LDIF_455]
ID: 455::
Severity: ERROR

+
Message: An error occurred while attempting to open source LDIF %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_ERROR_READING_SOURCE_LDIF_456]
ID: 456::
Severity: ERROR

+
Message: An error occurred while reading the contents of source LDIF %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_OPEN_TARGET_LDIF_457]
ID: 457::
Severity: ERROR

+
Message: An error occurred while attempting to open target LDIF %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_ERROR_READING_TARGET_LDIF_458]
ID: 458::
Severity: ERROR

+
Message: An error occurred while reading the contents of target LDIF %s: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_OPEN_OUTPUT_459]
ID: 459::
Severity: ERROR

+
Message: An error occurred while attempting to open the LDIF writer for the diff output: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_ERROR_WRITING_OUTPUT_461]
ID: 461::
Severity: ERROR

+
Message: An error occurred while attempting to write the diff output: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_ACQUIRE_SERVER_LOCK_472]
ID: 472::
Severity: ERROR

+
Message: An error occurred while attempting to acquire the server-wide lock file %s: %s. This generally means that the Directory Server is running, or another tool that requires exclusive access to the server is in use.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_INITIALIZE_JMX_473]
ID: 473::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server JMX subsystem based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_INITIALIZE_CONFIG_474]
ID: 474::
Severity: ERROR

+
Message: An error occurred while attempting to process the Directory Server configuration file %s: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_INITIALIZE_SCHEMA_475]
ID: 475::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server schema based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_PARSE_BASE_DN_476]
ID: 476::
Severity: ERROR

+
Message: An error occurred while attempting to parse base DN value "%s" as a DN: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_PARSE_ROOT_DN_477]
ID: 477::
Severity: ERROR

+
Message: An error occurred while attempting to parse root DN value "%s" as a DN: %s.

[#log-ref-log-ref-ERR_CONFIGDS_NO_ROOT_PW_478]
ID: 478::
Severity: ERROR

+
Message: The DN for the initial root user was provided, but no corresponding password was given. If the root DN is specified then the password must also be provided.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_LDAP_PORT_480]
ID: 480::
Severity: ERROR

+
Message: An error occurred while attempting to update the port on which to listen for LDAP communication: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_ROOT_USER_481]
ID: 481::
Severity: ERROR

+
Message: An error occurred while attempting to update the entry for the initial Directory Server root user: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_WRITE_UPDATED_CONFIG_482]
ID: 482::
Severity: ERROR

+
Message: An error occurred while writing the updated Directory Server configuration: %s.

[#log-ref-log-ref-ERR_CONFIGDS_NO_CONFIG_CHANGES_483]
ID: 483::
Severity: ERROR

+
Message: ERROR: No configuration changes were specified.

[#log-ref-log-ref-ERR_INSTALLDS_CANNOT_PARSE_DN_503]
ID: 503::
Severity: ERROR

+
Message: An error occurred while attempting to parse the string "%s" as a valid DN: %s.

[#log-ref-log-ref-ERR_INSTALLDS_CANNOT_BIND_TO_PRIVILEGED_PORT_510]
ID: 510::
Severity: ERROR

+
Message: ERROR: Unable to bind to port %d. This port may already be in use, or you may not have permission to bind to it. On UNIX-based operating systems, non-root users may not be allowed to bind to ports 1 through 1024.

[#log-ref-log-ref-ERR_INSTALLDS_CANNOT_BIND_TO_PORT_511]
ID: 511::
Severity: ERROR

+
Message: ERROR: Unable to bind to port %d. This port may already be in use, or you may not have permission to bind to it.

[#log-ref-log-ref-ERR_INSTALLDS_NO_ROOT_PASSWORD_513]
ID: 513::
Severity: ERROR

+
Message: Unable to authenticate using simple authentication.

[#log-ref-log-ref-ERR_INSTALLDS_INVALID_INTEGER_RESPONSE_524]
ID: 524::
Severity: ERROR

+
Message: ERROR: The provided response could not be interpreted as an integer. Please provide the response as an integer value.

[#log-ref-log-ref-ERR_INSTALLDS_INTEGER_BELOW_LOWER_BOUND_525]
ID: 525::
Severity: ERROR

+
Message: ERROR: The provided value is less than the lowest allowed value of %d.

[#log-ref-log-ref-ERR_INSTALLDS_INTEGER_ABOVE_UPPER_BOUND_526]
ID: 526::
Severity: ERROR

+
Message: ERROR: The provided value is greater than the largest allowed value of %d.

[#log-ref-log-ref-ERR_INSTALLDS_INVALID_DN_RESPONSE_527]
ID: 527::
Severity: ERROR

+
Message: ERROR: The provided response could not be interpreted as an LDAP DN.

[#log-ref-log-ref-ERR_INSTALLDS_PASSWORDS_DONT_MATCH_530]
ID: 530::
Severity: ERROR

+
Message: ERROR: The provided password values do not match.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_INVALID_ARGUMENT_COUNT_535]
ID: 535::
Severity: ERROR

+
Message: Invalid number of arguments provided for tag %s on line number %d of the template file: expected %d, got %d.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_INVALID_ARGUMENT_RANGE_COUNT_536]
ID: 536::
Severity: ERROR

+
Message: Invalid number of arguments provided for tag %s on line number %d of the template file: expected between %d and %d, got %d.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_UNDEFINED_ATTRIBUTE_537]
ID: 537::
Severity: ERROR

+
Message: Undefined attribute %s referenced on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_INTEGER_BELOW_LOWER_BOUND_538]
ID: 538::
Severity: ERROR

+
Message: Value %d is below the lowest allowed value of %d for tag %s on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_CANNOT_PARSE_AS_INTEGER_539]
ID: 539::
Severity: ERROR

+
Message: Cannot parse value "%s" as an integer for tag %s on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_INTEGER_ABOVE_UPPER_BOUND_540]
ID: 540::
Severity: ERROR

+
Message: Value %d is above the largest allowed value of %d for tag %s on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_CANNOT_PARSE_AS_BOOLEAN_542]
ID: 542::
Severity: ERROR

+
Message: Cannot parse value "%s" as a Boolean value for tag %s on line %d of the template file. The value must be either 'true' or 'false'.

[#log-ref-log-ref-ERR_MAKELDIF_UNDEFINED_BRANCH_SUBORDINATE_543]
ID: 543::
Severity: ERROR

+
Message: The branch with entry DN '%s' references a subordinate template named '%s' which is not defined in the template file.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_LOAD_TAG_CLASS_544]
ID: 544::
Severity: ERROR

+
Message: Unable to load class %s for use as a MakeLDIF tag.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_INSTANTIATE_TAG_545]
ID: 545::
Severity: ERROR

+
Message: Cannot instantiate class %s as a MakeLDIF tag.

[#log-ref-log-ref-ERR_MAKELDIF_CONFLICTING_TAG_NAME_546]
ID: 546::
Severity: ERROR

+
Message: Cannot register the tag defined in class %s because the tag name %s conflicts with the name of another tag that has already been registered.

[#log-ref-log-ref-ERR_MAKELDIF_DEFINE_MISSING_EQUALS_548]
ID: 548::
Severity: ERROR

+
Message: The constant definition on line %d is missing an equal sign to delimit the constant name from the value.

[#log-ref-log-ref-ERR_MAKELDIF_DEFINE_NAME_EMPTY_549]
ID: 549::
Severity: ERROR

+
Message: The constant definition on line %d does not include a name for the constant.

[#log-ref-log-ref-ERR_MAKELDIF_CONFLICTING_CONSTANT_NAME_550]
ID: 550::
Severity: ERROR

+
Message: The definition for constant %s on line %d conflicts with an earlier constant definition included in the template.

[#log-ref-log-ref-ERR_MAKELDIF_WARNING_DEFINE_VALUE_EMPTY_551]
ID: 551::
Severity: ERROR

+
Message: Constant %s defined on line %d has not been assigned a value.

[#log-ref-log-ref-ERR_MAKELDIF_CONFLICTING_BRANCH_DN_552]
ID: 552::
Severity: ERROR

+
Message: The branch definition %s starting on line %d conflicts with an earlier branch definition contained in the template file.

[#log-ref-log-ref-ERR_MAKELDIF_CONFLICTING_TEMPLATE_NAME_553]
ID: 553::
Severity: ERROR

+
Message: The template definition %s starting on line %d conflicts with an earlier template definition contained in the template file.

[#log-ref-log-ref-ERR_MAKELDIF_UNEXPECTED_TEMPLATE_FILE_LINE_554]
ID: 554::
Severity: ERROR

+
Message: Unexpected template line "%s" encountered on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_UNDEFINED_TEMPLATE_SUBORDINATE_555]
ID: 555::
Severity: ERROR

+
Message: The template named %s references a subordinate template named %s which is not defined in the template file.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_DECODE_BRANCH_DN_556]
ID: 556::
Severity: ERROR

+
Message: Unable to decode branch DN "%s" on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_BRANCH_SUBORDINATE_TEMPLATE_NO_COLON_557]
ID: 557::
Severity: ERROR

+
Message: Subordinate template definition on line %d for branch %s is missing a colon to separate the template name from the number of entries.

[#log-ref-log-ref-ERR_MAKELDIF_BRANCH_SUBORDINATE_INVALID_NUM_ENTRIES_558]
ID: 558::
Severity: ERROR

+
Message: Subordinate template definition on line %d for branch %s specified invalid number of entries %d for template %s.

[#log-ref-log-ref-ERR_MAKELDIF_BRANCH_SUBORDINATE_CANT_PARSE_NUMENTRIES_560]
ID: 560::
Severity: ERROR

+
Message: Unable to parse the number of entries for template %s as an integer for the subordinate template definition on line %d for branch %s.

[#log-ref-log-ref-ERR_MAKELDIF_TEMPLATE_SUBORDINATE_TEMPLATE_NO_COLON_561]
ID: 561::
Severity: ERROR

+
Message: Subordinate template definition on line %d for template %s is missing a colon to separate the template name from the number of entries.

[#log-ref-log-ref-ERR_MAKELDIF_TEMPLATE_SUBORDINATE_INVALID_NUM_ENTRIES_562]
ID: 562::
Severity: ERROR

+
Message: Subordinate template definition on line %d for template %s specified invalid number of entries %d for subordinate template %s.

[#log-ref-log-ref-ERR_MAKELDIF_TEMPLATE_SUBORDINATE_CANT_PARSE_NUMENTRIES_564]
ID: 564::
Severity: ERROR

+
Message: Unable to parse the number of entries for template %s as an integer for the subordinate template definition on line %d for template %s.

[#log-ref-log-ref-ERR_MAKELDIF_TEMPLATE_MISSING_RDN_ATTR_565]
ID: 565::
Severity: ERROR

+
Message: The template named %s includes RDN attribute %s that is not assigned a value in that template.

[#log-ref-log-ref-ERR_MAKELDIF_NO_COLON_IN_BRANCH_EXTRA_LINE_566]
ID: 566::
Severity: ERROR

+
Message: There is no colon to separate the attribute name from the value pattern on line %d of the template file in the definition for branch %s.

[#log-ref-log-ref-ERR_MAKELDIF_NO_ATTR_IN_BRANCH_EXTRA_LINE_567]
ID: 567::
Severity: ERROR

+
Message: There is no attribute name before the colon on line %d of the template file in the definition for branch %s.

[#log-ref-log-ref-ERR_MAKELDIF_NO_COLON_IN_TEMPLATE_LINE_569]
ID: 569::
Severity: ERROR

+
Message: There is no colon to separate the attribute name from the value pattern on line %d of the template file in the definition for template %s.

[#log-ref-log-ref-ERR_MAKELDIF_NO_ATTR_IN_TEMPLATE_LINE_570]
ID: 570::
Severity: ERROR

+
Message: There is no attribute name before the colon on line %d of the template file in the definition for template %s.

[#log-ref-log-ref-ERR_MAKELDIF_NO_SUCH_TAG_572]
ID: 572::
Severity: ERROR

+
Message: An undefined tag %s is referenced on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_INSTANTIATE_NEW_TAG_573]
ID: 573::
Severity: ERROR

+
Message: An unexpected error occurred while trying to create a new instance of tag %s referenced on line %d of the template file: %s.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_INITIALIZE_JMX_582]
ID: 582::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server JMX subsystem based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_INITIALIZE_CONFIG_583]
ID: 583::
Severity: ERROR

+
Message: An error occurred while attempting to process the Directory Server configuration file %s: %s.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_INITIALIZE_SCHEMA_584]
ID: 584::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server schema based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_MAKELDIF_IOEXCEPTION_DURING_PARSE_585]
ID: 585::
Severity: ERROR

+
Message: An error occurred while attempting to read the template file: %s.

[#log-ref-log-ref-ERR_MAKELDIF_EXCEPTION_DURING_PARSE_586]
ID: 586::
Severity: ERROR

+
Message: An error occurred while attempting to parse the template file: %s.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_INVALID_FORMAT_STRING_587]
ID: 587::
Severity: ERROR

+
Message: Cannot parse value "%s" as an valid format string for tag %s on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_NO_RANDOM_TYPE_ARGUMENT_588]
ID: 588::
Severity: ERROR

+
Message: The random tag on line %d of the template file does not include an argument to specify the type of random value that should be generated.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_UNKNOWN_RANDOM_TYPE_590]
ID: 590::
Severity: ERROR

+
Message: The random tag on line %d of the template file references an unknown random type of %s.

[#log-ref-log-ref-ERR_MAKELDIF_COULD_NOT_FIND_TEMPLATE_FILE_592]
ID: 592::
Severity: ERROR

+
Message: Could not find template file %s.

[#log-ref-log-ref-ERR_MAKELDIF_NO_SUCH_RESOURCE_DIRECTORY_593]
ID: 593::
Severity: ERROR

+
Message: The specified resource directory %s could not be found.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_CANNOT_FIND_FILE_595]
ID: 595::
Severity: ERROR

+
Message: Cannot find file %s referenced by tag %s on line %d of the template file.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_INVALID_FILE_ACCESS_MODE_596]
ID: 596::
Severity: ERROR

+
Message: Invalid file access mode %s for tag %s on line %d of the template file. It must be either "sequential" or "random".

[#log-ref-log-ref-ERR_MAKELDIF_TAG_CANNOT_READ_FILE_597]
ID: 597::
Severity: ERROR

+
Message: An error occurred while trying to read file %s referenced by tag %s on line %d of the template file: %s.

[#log-ref-log-ref-ERR_MAKELDIF_UNABLE_TO_CREATE_LDIF_598]
ID: 598::
Severity: ERROR

+
Message: An error occurred while attempting to open LDIF file %s for writing: %s.

[#log-ref-log-ref-ERR_MAKELDIF_ERROR_WRITING_LDIF_599]
ID: 599::
Severity: ERROR

+
Message: An error occurred while writing data to LDIF file %s: %s.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_WRITE_ENTRY_601]
ID: 601::
Severity: ERROR

+
Message: An error occurred while attempting to write entry %s to LDIF: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_MISSING_REQUIRED_ARGUMENT_605]
ID: 605::
Severity: ERROR

+
Message: Neither the %s or the %s argument was provided. One of these arguments must be given to specify the source for the LDIF data to be imported.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_PARSE_TEMPLATE_FILE_606]
ID: 606::
Severity: ERROR

+
Message: Unable to parse the specified file %s as a MakeLDIF template file: %s.

[#log-ref-log-ref-ERR_MAKELDIF_INCOMPLETE_TAG_607]
ID: 607::
Severity: ERROR

+
Message: Line %d of the template file contains an incomplete tag that starts with either '<' or '{' but does get closed.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_NOT_ALLOWED_IN_BRANCH_608]
ID: 608::
Severity: ERROR

+
Message: The provided passwords do not match.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_ADD_ENTRY_TWICE_610]
ID: 610::
Severity: ERROR

+
Message: Entry %s is added twice in the set of changes to apply, which is not supported by the LDIF modify tool.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_DELETE_AFTER_ADD_611]
ID: 611::
Severity: ERROR

+
Message: Entry %s cannot be deleted because it was previously added in the set of changes. This is not supported by the LDIF modify tool.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_MODIFY_ADDED_OR_DELETED_612]
ID: 612::
Severity: ERROR

+
Message: Cannot modify entry %s because it was previously added or deleted in the set of changes. This is not supported by the LDIF modify tool.

[#log-ref-log-ref-ERR_LDIFMODIFY_MODDN_NOT_SUPPORTED_613]
ID: 613::
Severity: ERROR

+
Message: The modify DN operation targeted at entry %s cannot be processed because modify DN operations are not supported by the LDIF modify tool.

[#log-ref-log-ref-ERR_LDIFMODIFY_UNKNOWN_CHANGETYPE_614]
ID: 614::
Severity: ERROR

+
Message: Entry %s has an unknown changetype of %s.

[#log-ref-log-ref-ERR_LDIFMODIFY_ADD_ALREADY_EXISTS_615]
ID: 615::
Severity: ERROR

+
Message: Unable to add entry %s because it already exists in the data set.

[#log-ref-log-ref-ERR_LDIFMODIFY_DELETE_NO_SUCH_ENTRY_616]
ID: 616::
Severity: ERROR

+
Message: Unable to delete entry %s because it does not exist in the data set.

[#log-ref-log-ref-ERR_LDIFMODIFY_MODIFY_NO_SUCH_ENTRY_617]
ID: 617::
Severity: ERROR

+
Message: Unable to modify entry %s because it does not exist in the data set.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_INITIALIZE_JMX_626]
ID: 626::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server JMX subsystem based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_INITIALIZE_CONFIG_627]
ID: 627::
Severity: ERROR

+
Message: An error occurred while attempting to process the Directory Server configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_INITIALIZE_SCHEMA_628]
ID: 628::
Severity: ERROR

+
Message: An error occurred while attempting to initialize the Directory Server schema based on the information in configuration file %s: %s.

[#log-ref-log-ref-ERR_LDIFMODIFY_SOURCE_DOES_NOT_EXIST_629]
ID: 629::
Severity: ERROR

+
Message: The source LDIF file %s does not exist.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_OPEN_SOURCE_630]
ID: 630::
Severity: ERROR

+
Message: Unable to open the source LDIF file %s: %s.

[#log-ref-log-ref-ERR_LDIFMODIFY_CHANGES_DOES_NOT_EXIST_631]
ID: 631::
Severity: ERROR

+
Message: The changes LDIF file %s does not exist.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_OPEN_CHANGES_632]
ID: 632::
Severity: ERROR

+
Message: Unable to open the changes LDIF file %s: %s.

[#log-ref-log-ref-ERR_LDIFMODIFY_CANNOT_OPEN_TARGET_633]
ID: 633::
Severity: ERROR

+
Message: Unable to open the target LDIF file %s for writing: %s.

[#log-ref-log-ref-ERR_LDIFMODIFY_ERROR_PROCESSING_LDIF_634]
ID: 634::
Severity: ERROR

+
Message: An error occurred while processing the requested changes: %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_BIND_DN_AND_PW_MUST_BE_TOGETHER_657]
ID: 657::
Severity: ERROR

+
Message: If either a bind DN or bind password is provided, then the other must be given as well.

[#log-ref-log-ref-ERR_LDAPPWMOD_ANON_REQUIRES_AUTHZID_AND_CURRENTPW_658]
ID: 658::
Severity: ERROR

+
Message: If a bind DN and password are not provided, then an authorization ID and current password must be given.

[#log-ref-log-ref-ERR_LDAPPWMOD_DEPENDENT_ARGS_659]
ID: 659::
Severity: ERROR

+
Message: If the %s argument is provided, then the %s argument must also be given.

[#log-ref-log-ref-ERR_LDAPPWMOD_ERROR_INITIALIZING_SSL_660]
ID: 660::
Severity: ERROR

+
Message: Unable to initialize SSL/TLS support: %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_CANNOT_CONNECT_661]
ID: 661::
Severity: ERROR

+
Message: An error occurred while attempting to connect to the Directory Server: %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_CANNOT_SEND_PWMOD_REQUEST_662]
ID: 662::
Severity: ERROR

+
Message: Unable to send the LDAP password modify request: %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_CANNOT_READ_PWMOD_RESPONSE_663]
ID: 663::
Severity: ERROR

+
Message: Unable to read the LDAP password modify response: %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_FAILED_664]
ID: 664::
Severity: ERROR

+
Message: The LDAP password modify operation failed with result code %d.

[#log-ref-log-ref-ERR_LDAPPWMOD_FAILURE_ERROR_MESSAGE_665]
ID: 665::
Severity: ERROR

+
Message: Error Message: %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_FAILURE_MATCHED_DN_666]
ID: 666::
Severity: ERROR

+
Message: Matched DN: %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_UNRECOGNIZED_VALUE_TYPE_670]
ID: 670::
Severity: ERROR

+
Message: Unable to decode the password modify response value because it contained an invalid element type of %s.

[#log-ref-log-ref-ERR_LDAPPWMOD_COULD_NOT_DECODE_RESPONSE_VALUE_671]
ID: 671::
Severity: ERROR

+
Message: Unable to decode the password modify response value: %s.

[#log-ref-log-ref-ERR_LDAPCOMPARE_NO_DNS_682]
ID: 682::
Severity: ERROR

+
Message: No entry DNs provided for the compare operation.

[#log-ref-log-ref-ERR_LDAPCOMPARE_NO_ATTR_703]
ID: 703::
Severity: ERROR

+
Message: No attribute was specified to use as the target for the comparison.

[#log-ref-log-ref-ERR_LDAPCOMPARE_INVALID_ATTR_STRING_704]
ID: 704::
Severity: ERROR

+
Message: Invalid attribute string '%s'. The attribute string must be in one of the following forms: 'attribute:value', 'attribute::base64value', or 'attribute:<valueFilePath'.

[#log-ref-log-ref-ERR_TOOL_INVALID_CONTROL_STRING_705]
ID: 705::
Severity: ERROR

+
Message: Invalid control specification '%s'.

[#log-ref-log-ref-ERR_TOOL_SASLEXTERNAL_NEEDS_SSL_OR_TLS_706]
ID: 706::
Severity: ERROR

+
Message: SASL EXTERNAL authentication may only be requested if SSL or StartTLS is used.

[#log-ref-log-ref-ERR_TOOL_SASLEXTERNAL_NEEDS_KEYSTORE_707]
ID: 707::
Severity: ERROR

+
Message: SASL EXTERNAL authentication may only be used if a client certificate key store is specified.

[#log-ref-log-ref-ERR_LISTBACKENDS_CANNOT_GET_BACKENDS_734]
ID: 734::
Severity: ERROR

+
Message: An error occurred while trying to read backend information from the server configuration: %s.

[#log-ref-log-ref-ERR_LISTBACKENDS_INVALID_DN_735]
ID: 735::
Severity: ERROR

+
Message: The provided base DN value '%s' could not be parsed as a valid DN: %s.

[#log-ref-log-ref-ERR_LISTBACKENDS_NO_SUCH_BACKEND_742]
ID: 742::
Severity: ERROR

+
Message: There is no backend with ID '%s' in the server configuration.

[#log-ref-log-ref-ERR_LISTBACKENDS_NO_VALID_BACKENDS_743]
ID: 743::
Severity: ERROR

+
Message: None of the provided backend IDs exist in the server configuration.

[#log-ref-log-ref-ERR_ENCPW_INVALID_ENCODED_USERPW_748]
ID: 748::
Severity: ERROR

+
Message: The provided password is not a valid encoded user password value: %s.

[#log-ref-log-ref-ERR_INSTALLDS_NO_SUCH_LDIF_FILE_780]
ID: 780::
Severity: ERROR

+
Message: ERROR: The specified LDIF file %s does not exist.

[#log-ref-log-ref-ERR_LDAPPWMOD_CANNOT_DECODE_PWPOLICY_CONTROL_788]
ID: 788::
Severity: ERROR

+
Message: Unable to decode the password policy response control: %s.

[#log-ref-log-ref-ERR_LDAPAUTH_CONNECTION_CLOSED_WITHOUT_BIND_RESPONSE_789]
ID: 789::
Severity: ERROR

+
Message: The connection to the Directory Server was closed before the bind response could be read.

[#log-ref-log-ref-ERR_PAGED_RESULTS_REQUIRES_SINGLE_FILTER_791]
ID: 791::
Severity: ERROR

+
Message: The simple paged results control may only be used with a single search filter.

[#log-ref-log-ref-ERR_PAGED_RESULTS_CANNOT_DECODE_792]
ID: 792::
Severity: ERROR

+
Message: Unable to decode the simple paged results control from the search response: %s.

[#log-ref-log-ref-ERR_PAGED_RESULTS_RESPONSE_NOT_FOUND_793]
ID: 793::
Severity: ERROR

+
Message: The simple paged results response control was not found in the search result done message from the server.

[#log-ref-log-ref-ERR_PROMPTTM_REJECTING_CLIENT_CERT_795]
ID: 795::
Severity: ERROR

+
Message: Rejecting client certificate chain because the prompt trust manager may only be used to trust server certificates.

[#log-ref-log-ref-ERR_PROMPTTM_USER_REJECTED_801]
ID: 801::
Severity: ERROR

+
Message: The server certificate has been rejected by the user.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_JMX_PORT_807]
ID: 807::
Severity: ERROR

+
Message: An error occurred while attempting to update the port on which to listen for JMX communication: %s.

[#log-ref-log-ref-ERR_TOOL_RESULT_CODE_810]
ID: 810::
Severity: ERROR

+
Message: Result Code: %d (%s).

[#log-ref-log-ref-ERR_TOOL_ERROR_MESSAGE_811]
ID: 811::
Severity: ERROR

+
Message: Additional Information: %s.

[#log-ref-log-ref-ERR_TOOL_MATCHED_DN_812]
ID: 812::
Severity: ERROR

+
Message: Matched DN: %s.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_NOT_FOUND_813]
ID: 813::
Severity: ERROR

+
Message: Could not find the service name for the server.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_START_ERROR_814]
ID: 814::
Severity: ERROR

+
Message: An unexpected error occurred starting the server as a windows service.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_STOP_ERROR_815]
ID: 815::
Severity: ERROR

+
Message: An unexpected error occurred stopping the server windows service.

[#log-ref-log-ref-ERR_CONFIGURE_WINDOWS_SERVICE_TOO_MANY_ARGS_823]
ID: 823::
Severity: ERROR

+
Message: You can only provide one of the following arguments: enableService, disableService, serviceState or cleanupService.

[#log-ref-log-ref-ERR_CONFIGURE_WINDOWS_SERVICE_TOO_FEW_ARGS_824]
ID: 824::
Severity: ERROR

+
Message: You must provide at least one of the following arguments: enableService, disableService or serviceState or cleanupService.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_NAME_ALREADY_IN_USE_829]
ID: 829::
Severity: ERROR

+
Message: The server could not be enabled to run as a Windows service. The service name is already in use.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_ENABLE_ERROR_830]
ID: 830::
Severity: ERROR

+
Message: ERROR: Unable to bind to port %d. This port may already be in use, or you may not have permission to bind to it.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_DISABLE_ERROR_834]
ID: 834::
Severity: ERROR

+
Message: An unexpected error occurred trying to disable the server as a Windows service%nCheck that you have administrator rights (only Administrators can disable the server as a Windows Service).

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_STATE_ERROR_837]
ID: 837::
Severity: ERROR

+
Message: An unexpected error occurred trying to retrieve the state of the server as a Windows service.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_CLEANUP_NOT_FOUND_846]
ID: 846::
Severity: ERROR

+
Message: Could not find the service with name %s.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_CLEANUP_ERROR_848]
ID: 848::
Severity: ERROR

+
Message: An unexpected error occurred cleaning up the service %s.

[#log-ref-log-ref-ERR_REBUILDINDEX_ERROR_DURING_REBUILD_852]
ID: 852::
Severity: ERROR

+
Message: An error occurred while attempting to perform index rebuild: %s.

[#log-ref-log-ref-ERR_REBUILDINDEX_WRONG_BACKEND_TYPE_853]
ID: 853::
Severity: ERROR

+
Message: The backend does not support rebuilding of indexes.

[#log-ref-log-ref-ERR_REBUILDINDEX_REQUIRES_AT_LEAST_ONE_INDEX_854]
ID: 854::
Severity: ERROR

+
Message: At least one index must be specified for the rebuild process.

[#log-ref-log-ref-ERR_REBUILDINDEX_CANNOT_EXCLUSIVE_LOCK_BACKEND_855]
ID: 855::
Severity: ERROR

+
Message: An error occurred while attempting to acquire a exclusive lock for backend %s: %s. This generally means that some other process has an lock on this backend or the server is running with this backend online. The rebuild process cannot continue.

[#log-ref-log-ref-ERR_REBUILDINDEX_CANNOT_SHARED_LOCK_BACKEND_857]
ID: 857::
Severity: ERROR

+
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has an exclusive lock on this backend (e.g., an LDIF import or a restore). The rebuild process cannot continue.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_LDAPS_PORT_859]
ID: 859::
Severity: ERROR

+
Message: An error occurred while attempting to update the port on which to listen for LDAPS communication: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_PARSE_KEYMANAGER_PROVIDER_DN_863]
ID: 863::
Severity: ERROR

+
Message: An error occurred while attempting to parse key manager provider DN value "%s" as a DN: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_PARSE_TRUSTMANAGER_PROVIDER_DN_864]
ID: 864::
Severity: ERROR

+
Message: An error occurred while attempting to parse trust manager provider DN value "%s" as a DN: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_ENABLE_STARTTLS_865]
ID: 865::
Severity: ERROR

+
Message: An error occurred while attempting to enable StartTLS: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_ENABLE_KEYMANAGER_866]
ID: 866::
Severity: ERROR

+
Message: An error occurred while attempting to enable key manager provider entry: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_ENABLE_TRUSTMANAGER_867]
ID: 867::
Severity: ERROR

+
Message: An error occurred while attempting to enable trust manager provider entry: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_KEYMANAGER_REFERENCE_868]
ID: 868::
Severity: ERROR

+
Message: An error occurred while attempting to update the key manager provider DN used for LDAPS communication: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_TRUSTMANAGER_REFERENCE_869]
ID: 869::
Severity: ERROR

+
Message: An error occurred while attempting to update the trust manager provider DN used for LDAPS communication: %s.

[#log-ref-log-ref-ERR_CONFIGDS_KEYMANAGER_PROVIDER_DN_REQUIRED_872]
ID: 872::
Severity: ERROR

+
Message: ERROR: You must provide the %s argument when providing the %s argument.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_CERT_NICKNAME_873]
ID: 873::
Severity: ERROR

+
Message: An error occurred while attempting to update the nickname of the certificate that the connection handler should use when accepting SSL-based connections or performing StartTLS negotiation: %s.

[#log-ref-log-ref-ERR_MAKELDIF_TEMPLATE_INVALID_PARENT_TEMPLATE_875]
ID: 875::
Severity: ERROR

+
Message: The parent template %s referenced on line %d for template %s is invalid because the referenced parent template is not defined before the template that extends it.

[#log-ref-log-ref-ERR_LDAP_SORTCONTROL_INVALID_ORDER_877]
ID: 877::
Severity: ERROR

+
Message: The provided sort order was invalid: %s.

[#log-ref-log-ref-ERR_LDAPSEARCH_VLV_REQUIRES_SORT_879]
ID: 879::
Severity: ERROR

+
Message: If the --%s argument is provided, then the --%s argument must also be given.

[#log-ref-log-ref-ERR_LDAPSEARCH_VLV_INVALID_DESCRIPTOR_880]
ID: 880::
Severity: ERROR

+
Message: The provided virtual list view descriptor was invalid. It must be a value in the form 'beforeCount:afterCount:offset:contentCount' (where offset specifies the index of the target entry and contentCount specifies the estimated total number of results or zero if it is not known), or 'beforeCount:afterCount:assertionValue' (where the entry should be the first entry whose primary sort value is greater than or equal to the provided assertionValue). In either case, beforeCount is the number of entries to return before the target value and afterCount is the number of entries to return after the target value.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_READ_FILE_887]
ID: 887::
Severity: ERROR

+
Message: The specified LDIF file %s cannot be read.

[#log-ref-log-ref-ERR_EFFECTIVERIGHTS_INVALID_AUTHZID_890]
ID: 890::
Severity: ERROR

+
Message: The authorization ID "%s" contained in the geteffectiverights control is invalid because it does not start with "dn:" to indicate a user DN.

[#log-ref-log-ref-ERR_PWPSTATE_NO_SUBCOMMAND_1155]
ID: 1155::
Severity: ERROR

+
Message: No subcommand was provided to indicate which password policy state operation should be performed.

[#log-ref-log-ref-ERR_PWPSTATE_INVALID_BOOLEAN_VALUE_1156]
ID: 1156::
Severity: ERROR

+
Message: The provided value '%s' was invalid for the requested operation. A Boolean value of either 'true' or 'false' was expected.

[#log-ref-log-ref-ERR_PWPSTATE_NO_BOOLEAN_VALUE_1157]
ID: 1157::
Severity: ERROR

+
Message: No value was specified, but the requested operation requires a Boolean value of either 'true' or 'false'.

[#log-ref-log-ref-ERR_PWPSTATE_INVALID_SUBCOMMAND_1158]
ID: 1158::
Severity: ERROR

+
Message: Unrecognized subcommand '%s'.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_SEND_REQUEST_EXTOP_1159]
ID: 1159::
Severity: ERROR

+
Message: An error occurred while attempting to send the request to the server: %s.

[#log-ref-log-ref-ERR_PWPSTATE_CONNECTION_CLOSED_READING_RESPONSE_1160]
ID: 1160::
Severity: ERROR

+
Message: The Directory Server closed the connection before the response could be read.

[#log-ref-log-ref-ERR_PWPSTATE_REQUEST_FAILED_1161]
ID: 1161::
Severity: ERROR

+
Message: The server was unable to process the request: result code %d (%s), error message '%s'.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_DECODE_RESPONSE_MESSAGE_1162]
ID: 1162::
Severity: ERROR

+
Message: Unable to decode the response message from the server: %s.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_DECODE_RESPONSE_OP_1163]
ID: 1163::
Severity: ERROR

+
Message: Unable to decode information about an operation contained in the response: %s.

[#log-ref-log-ref-ERR_PWPSTATE_INVALID_RESPONSE_OP_TYPE_1183]
ID: 1183::
Severity: ERROR

+
Message: Unrecognized or invalid operation type: %s.

[#log-ref-log-ref-ERR_PWPSTATE_MUTUALLY_EXCLUSIVE_ARGUMENTS_1184]
ID: 1184::
Severity: ERROR

+
Message: ERROR: You may not provide both the %s and the %s arguments.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_INITIALIZE_SSL_1185]
ID: 1185::
Severity: ERROR

+
Message: ERROR: Unable to perform SSL initialization: %s.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_PARSE_SASL_OPTION_1186]
ID: 1186::
Severity: ERROR

+
Message: ERROR: The provided SASL option string "%s" could not be parsed in the form "name=value".

[#log-ref-log-ref-ERR_PWPSTATE_NO_SASL_MECHANISM_1187]
ID: 1187::
Severity: ERROR

+
Message: ERROR: One or more SASL options were provided, but none of them were the "mech" option to specify which SASL mechanism should be used.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_DETERMINE_PORT_1188]
ID: 1188::
Severity: ERROR

+
Message: ERROR: Cannot parse the value of the %s argument as an integer value between 1 and 65535: %s.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_CONNECT_1189]
ID: 1189::
Severity: ERROR

+
Message: ERROR: Cannot establish a connection to the Directory Server %s. Verify that the server is running and that the provided credentials are valid. Details: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_OPEN_SKIP_FILE_1198]
ID: 1198::
Severity: ERROR

+
Message: An error occurred while trying to open the skip file %s for writing: %s.

[#log-ref-log-ref-ERR_CONFIGDS_PORT_ALREADY_SPECIFIED_1211]
ID: 1211::
Severity: ERROR

+
Message: ERROR: You have specified the value %s for different ports.

[#log-ref-log-ref-ERR_LDIFIMPORT_MISSING_BACKEND_ARGUMENT_1252]
ID: 1252::
Severity: ERROR

+
Message: Neither the %s or the %s argument was provided. One of these arguments must be given to specify the backend for the LDIF data to be imported to.

[#log-ref-log-ref-ERR_MAKELDIF_TAG_LIST_NO_ARGUMENTS_1291]
ID: 1291::
Severity: ERROR

+
Message: The list tag on line %d of the template file does not contain any arguments to specify the list values. At least one list value must be provided.

[#log-ref-log-ref-ERR_INITIALIZE_SERVER_ROOT_1293]
ID: 1293::
Severity: ERROR

+
Message: An unexpected error occurred attempting to set the server's root directory to %s: %s.

[#log-ref-log-ref-ERR_LDAP_CONN_CANNOT_INITIALIZE_SSL_1295]
ID: 1295::
Severity: ERROR

+
Message: ERROR: Unable to perform SSL initialization: %s.

[#log-ref-log-ref-ERR_LDAP_CONN_CANNOT_PARSE_SASL_OPTION_1296]
ID: 1296::
Severity: ERROR

+
Message: ERROR: The provided SASL option string "%s" could not be parsed in the form "name=value".

[#log-ref-log-ref-ERR_LDAP_CONN_NO_SASL_MECHANISM_1297]
ID: 1297::
Severity: ERROR

+
Message: ERROR: One or more SASL options were provided, but none of them were the "mech" option to specify which SASL mechanism should be used.

[#log-ref-log-ref-ERR_TASK_CLIENT_UNEXPECTED_CONNECTION_CLOSURE_1315]
ID: 1315::
Severity: ERROR

+
Message: NOTICE: The connection to the Directory Server was closed while waiting for a response to the shutdown request. This likely means that the server has started the shutdown process.

[#log-ref-log-ref-ERR_TASK_TOOL_IO_ERROR_1316]
ID: 1316::
Severity: ERROR

+
Message: ERROR: An I/O error occurred while attempting to communicate with the Directory Server: %s.

[#log-ref-log-ref-ERR_TASK_TOOL_DECODE_ERROR_1317]
ID: 1317::
Severity: ERROR

+
Message: ERROR: An error occurred while trying to decode the response from the server: %s.

[#log-ref-log-ref-ERR_TASK_CLIENT_INVALID_RESPONSE_TYPE_1318]
ID: 1318::
Severity: ERROR

+
Message: ERROR: Expected an add response message but got a %s message instead.

[#log-ref-log-ref-ERR_LDAP_CONN_INCOMPATIBLE_ARGS_1320]
ID: 1320::
Severity: ERROR

+
Message: ERROR: argument %s is incompatible with use of this tool to interact with the directory as a client.

[#log-ref-log-ref-ERR_CREATERC_ONLY_RUNS_ON_UNIX_1321]
ID: 1321::
Severity: ERROR

+
Message: This tool may only be used on UNIX-based systems.

[#log-ref-log-ref-ERR_CREATERC_UNABLE_TO_DETERMINE_SERVER_ROOT_1324]
ID: 1324::
Severity: ERROR

+
Message: Unable to determine the path to the server root directory. Please ensure that the %s system property or the %s environment variable is set to the path of the server root directory.

[#log-ref-log-ref-ERR_CREATERC_CANNOT_WRITE_1325]
ID: 1325::
Severity: ERROR

+
Message: An error occurred while attempting to generate the RC script: %s.

[#log-ref-log-ref-ERR_BACKEND_DEBUG_NO_BACKENDS_FOR_ID_1347]
ID: 1347::
Severity: ERROR

+
Message: None of the Directory Server backends are configured with the requested backend ID %s.

[#log-ref-log-ref-ERR_BACKEND_DEBUG_NO_ENTRY_CONTAINERS_FOR_BASE_DN_1348]
ID: 1348::
Severity: ERROR

+
Message: None of the entry containers are configured with the requested base DN %s in backend %s.

[#log-ref-log-ref-ERR_BACKEND_DEBUG_DECODE_BASE_DN_1352]
ID: 1352::
Severity: ERROR

+
Message: Unable to decode base DN string "%s" as a valid distinguished name: %s.

[#log-ref-log-ref-ERR_BACKEND_DEBUG_CANNOT_LOCK_BACKEND_1363]
ID: 1363::
Severity: ERROR

+
Message: An error occurred while attempting to acquire a shared lock for backend %s: %s. This generally means that some other process has exclusive access to this backend (e.g., a restore or an LDIF import).

[#log-ref-log-ref-ERR_BACKEND_DEBUG_MISSING_SUBCOMMAND_1374]
ID: 1374::
Severity: ERROR

+
Message: A sub-command must be specified.

[#log-ref-log-ref-ERR_CREATERC_JAVA_HOME_DOESNT_EXIST_1378]
ID: 1378::
Severity: ERROR

+
Message: The directory %s specified as the OPENDJ_JAVA_HOME path does not exist or is not a directory.

[#log-ref-log-ref-ERR_INSTALLDS_CERTNICKNAME_NOT_FOUND_1394]
ID: 1394::
Severity: ERROR

+
Message: The provided certificate nickname could not be found. The key store contains the following certificate nicknames: %s.

[#log-ref-log-ref-ERR_INSTALLDS_MUST_PROVIDE_CERTNICKNAME_1395]
ID: 1395::
Severity: ERROR

+
Message: The key store contains the following certificate nicknames: %s.%nYou have to provide the nickname of the certificate you want to use.

[#log-ref-log-ref-ERR_INSTALLDS_SEVERAL_CERTIFICATE_TYPE_SPECIFIED_1406]
ID: 1406::
Severity: ERROR

+
Message: You have specified several certificate types to be used. Only one certificate type (self-signed, JKS, JCEKS, PKCS#12 or PCKS#11) is allowed.

[#log-ref-log-ref-ERR_INSTALLDS_CERTIFICATE_REQUIRED_FOR_SSL_OR_STARTTLS_1407]
ID: 1407::
Severity: ERROR

+
Message: You have chosen to enable SSL or StartTLS. You must specify which type of certificate you want the server to use.

[#log-ref-log-ref-ERR_INSTALLDS_NO_KEYSTORE_PASSWORD_1408]
ID: 1408::
Severity: ERROR

+
Message: You must provide the PIN of the keystore to retrieve the certificate to be used by the server. You can use {%s} or {%s}.

[#log-ref-log-ref-ERR_INSTALLDS_SSL_OR_STARTTLS_REQUIRED_1410]
ID: 1410::
Severity: ERROR

+
Message: You have specified to use a certificate as server certificate. You must enable SSL (using option {%s}) or Start TLS (using option %s).

[#log-ref-log-ref-ERR_UPGRADE_INCOMPATIBLE_ARGS_1411]
ID: 1411::
Severity: ERROR

+
Message: The argument '%s' is incompatible with '%s'.

[#log-ref-log-ref-ERR_TASKINFO_INVALID_MENU_KEY_1422]
ID: 1422::
Severity: ERROR

+
Message: Invalid menu item or task number '%s'.

[#log-ref-log-ref-ERR_TASKINFO_RETRIEVING_TASK_ENTRY_1437]
ID: 1437::
Severity: ERROR

+
Message: Error retrieving task entry %s: %s.

[#log-ref-log-ref-ERR_TASKINFO_UNKNOWN_TASK_ENTRY_1438]
ID: 1438::
Severity: ERROR

+
Message: There are no tasks with ID %s.

[#log-ref-log-ref-ERR_INCOMPATIBLE_ARGUMENTS_1446]
ID: 1446::
Severity: ERROR

+
Message: Options '%s' and '%s' are incompatible with each other and cannot be used together.

[#log-ref-log-ref-ERR_TASKINFO_CANCELING_TASK_1448]
ID: 1448::
Severity: ERROR

+
Message: Error canceling task '%s': %s.

[#log-ref-log-ref-ERR_TASKINFO_ACCESSING_LOGS_1449]
ID: 1449::
Severity: ERROR

+
Message: Error accessing logs for task '%s': %s.

[#log-ref-log-ref-ERR_TASKINFO_NOT_CANCELABLE_TASK_INDEX_1450]
ID: 1450::
Severity: ERROR

+
Message: Task at index %d is not cancelable.

[#log-ref-log-ref-ERR_TASK_CLIENT_UNKNOWN_TASK_1453]
ID: 1453::
Severity: ERROR

+
Message: There are no tasks defined with ID '%s'.

[#log-ref-log-ref-ERR_TASK_CLIENT_UNCANCELABLE_TASK_1454]
ID: 1454::
Severity: ERROR

+
Message: Task '%s' has finished and cannot be canceled.

[#log-ref-log-ref-ERR_TASK_CLIENT_TASK_STATE_UNKNOWN_1455]
ID: 1455::
Severity: ERROR

+
Message: State for task '%s' cannot be determined.

[#log-ref-log-ref-ERR_START_DATETIME_FORMAT_1457]
ID: 1457::
Severity: ERROR

+
Message: The start date/time must in YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time.

[#log-ref-log-ref-ERR_TASK_TOOL_START_TIME_NO_LDAP_1459]
ID: 1459::
Severity: ERROR

+
Message: You have provided options for scheduling this operation as a task but options provided for connecting to the server's tasks backend resulted in the following error: '%s'.

[#log-ref-log-ref-ERR_TASKTOOL_OPTIONS_FOR_TASK_ONLY_1473]
ID: 1473::
Severity: ERROR

+
Message: The option %s is only applicable when scheduling this operation as a task.

[#log-ref-log-ref-ERR_TASKTOOL_INVALID_EMAIL_ADDRESS_1474]
ID: 1474::
Severity: ERROR

+
Message: The value %s for option %s is not a valid email address.

[#log-ref-log-ref-ERR_TASKTOOL_INVALID_FDA_1475]
ID: 1475::
Severity: ERROR

+
Message: The failed dependency action value %s is invalid. The value must be one of %s.

[#log-ref-log-ref-ERR_TASKTOOL_FDA_WITH_NO_DEPENDENCY_1476]
ID: 1476::
Severity: ERROR

+
Message: The failed dependency action option is to be used in conjunction with one or more dependencies.

[#log-ref-log-ref-ERR_TASKINFO_TASK_NOT_CANCELABLE_TASK_1477]
ID: 1477::
Severity: ERROR

+
Message: Error: task %s is not in a cancelable state.

[#log-ref-log-ref-ERR_INSTALLDS_CANNOT_WRITE_REJECTED_1480]
ID: 1480::
Severity: ERROR

+
Message: Cannot write to rejected entries file %s. Verify that you have enough write rights on the file.

[#log-ref-log-ref-ERR_INSTALLDS_CANNOT_WRITE_SKIPPED_1483]
ID: 1483::
Severity: ERROR

+
Message: Cannot write to skipped entries file %s. Verify that you have enough write rights on the file.

[#log-ref-log-ref-ERR_INSTALLDS_TOO_MANY_KEYSTORE_PASSWORD_TRIES_1485]
ID: 1485::
Severity: ERROR

+
Message: The maximum number of tries to provide the certificate key store PIN is %s. Install canceled.

[#log-ref-log-ref-ERR_JAVAPROPERTIES_WITH_PROPERTIES_FILE_1491]
ID: 1491::
Severity: ERROR

+
Message: The file properties "%s" cannot be read. Check that it exists and that you have read rights to it.

[#log-ref-log-ref-ERR_JAVAPROPERTIES_WITH_DESTINATION_FILE_1492]
ID: 1492::
Severity: ERROR

+
Message: The destination file "%s" cannot be written. Check that you have write rights to it.

[#log-ref-log-ref-ERR_JAVAPROPERTIES_WRITING_DESTINATION_FILE_1493]
ID: 1493::
Severity: ERROR

+
Message: The destination file "%s" cannot be written. Check that you have right reads to it.

[#log-ref-log-ref-ERR_BACKUPDB_REPEATED_BACKEND_ID_1497]
ID: 1497::
Severity: ERROR

+
Message: The backend ID '%s' has been specified several times.

[#log-ref-log-ref-ERR_INSTALLDS_EMPTY_DN_RESPONSE_1498]
ID: 1498::
Severity: ERROR

+
Message: ERROR: The empty LDAP DN is not a valid value.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_CRYPTO_MANAGER_1607]
ID: 1607::
Severity: ERROR

+
Message: An error occurred while attempting to update the crypto manager in the Directory Server: %s.

[#log-ref-log-ref-ERR_CANNOT_READ_TRUSTSTORE_1610]
ID: 1610::
Severity: ERROR

+
Message: Cannot access trust store '%s'. Verify that the provided trust store exists and that you have read access rights to it.

[#log-ref-log-ref-ERR_CANNOT_READ_KEYSTORE_1611]
ID: 1611::
Severity: ERROR

+
Message: Cannot access key store '%s'. Verify that the provided key store exists and that you have read access rights to it.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_READ_FILE_IGNORE_ENTRIES_1614]
ID: 1614::
Severity: ERROR

+
Message: An error occurred while attempting to read the file '%s' containing the list of ignored entries: %s.

[#log-ref-log-ref-ERR_LDIFDIFF_CANNOT_READ_FILE_IGNORE_ATTRIBS_1615]
ID: 1615::
Severity: ERROR

+
Message: An error occurred while attempting to read the file '%s' containing the list of ignored attributes: %s.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_ADMIN_CONNECTOR_PORT_1620]
ID: 1620::
Severity: ERROR

+
Message: An error occurred while attempting to update the administration connector port: %s.

[#log-ref-log-ref-ERR_TASKINFO_LDAP_EXCEPTION_SSL_1621]
ID: 1621::
Severity: ERROR

+
Message: Error connecting to the directory server at %s on %s. Check this port is an administration port.

[#log-ref-log-ref-ERR_CONFIG_KEYMANAGER_CANNOT_CREATE_JCEKS_PROVIDER_1626]
ID: 1626::
Severity: ERROR

+
Message: Error creating JCEKS Key Provider configuration: %s.

[#log-ref-log-ref-ERR_STOPDS_CANNOT_CONNECT_SSL_1628]
ID: 1628::
Severity: ERROR

+
Message: ERROR: Cannot establish a connection to the Directory Server at %s on port %s. Check this port is an administration port.

[#log-ref-log-ref-ERR_PWPSTATE_CANNOT_CONNECT_SSL_1629]
ID: 1629::
Severity: ERROR

+
Message: ERROR: Cannot establish a connection to the Directory Server at %s on port %s. Check this port is an administration port.

[#log-ref-log-ref-ERR_BACKUPDB_CANNOT_BACKUP_IN_DIRECTORY_1650]
ID: 1650::
Severity: ERROR

+
Message: The target backend %s cannot be backed up to the backup directory %s: this directory is already a backup location for backend %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_SERVER_COMPONENTS_1652]
ID: 1652::
Severity: ERROR

+
Message: An error occurred while attempting to initialize server components to run the tool: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_COUNT_REJECTS_REQUIRES_OFFLINE_1653]
ID: 1653::
Severity: ERROR

+
Message: The %s argument is not supported for online imports.

[#log-ref-log-ref-ERR_START_DATETIME_ALREADY_PASSED_1667]
ID: 1667::
Severity: ERROR

+
Message: The specified start time '%s' has already passed.

[#log-ref-log-ref-ERR_LDAPCOMPARE_ERROR_READING_FILE_1668]
ID: 1668::
Severity: ERROR

+
Message: An error occurred reading file '%s'. Check that the file exists and that you have read access rights to it. Details: %s.

[#log-ref-log-ref-ERR_STOPDS_DATETIME_ALREADY_PASSED_1669]
ID: 1669::
Severity: ERROR

+
Message: The specified stop time '%s' has already passed.

[#log-ref-log-ref-ERR_LDAPCOMPARE_FILENAME_AND_DNS_1670]
ID: 1670::
Severity: ERROR

+
Message: Both entry DNs and a file name were provided for the compare operation. These arguments are not compatible.

[#log-ref-log-ref-ERR_TIMEOUT_DURING_STARTUP_1680]
ID: 1680::
Severity: ERROR

+
Message: The timeout of '%d' seconds to start the server has been reached. You can use the argument '--%s' to increase this timeout.

[#log-ref-log-ref-ERR_LDIFIMPORT_CANNOT_PARSE_THREAD_COUNT_1688]
ID: 1688::
Severity: ERROR

+
Message: The value %s for threadCount cannot be parsed: %s.

[#log-ref-log-ref-ERR_ENCPW_NOT_SAME_PW_1693]
ID: 1693::
Severity: ERROR

+
Message: Provided passwords don't matched.

[#log-ref-log-ref-ERR_ENCPW_CANNOT_READ_PW_1694]
ID: 1694::
Severity: ERROR

+
Message: Cannot read password from the input: %s.

[#log-ref-log-ref-ERR_REBUILDINDEX_REBUILD_ALL_ERROR_1699]
ID: 1699::
Severity: ERROR

+
Message: Index "-i" option cannot be specified with the "--rebuildAll" option.

[#log-ref-log-ref-ERR_INSTALLDS_NO_BASE_DN_AND_CONFLICTING_ARG_1701]
ID: 1701::
Severity: ERROR

+
Message: You have specified not to create a base DN. If no base DN is to be created you cannot specify argument '%s'.

[#log-ref-log-ref-ERR_WINDOWS_SERVICE_ENABLING_ERROR_STARTING_SERVER_1709]
ID: 1709::
Severity: ERROR

+
Message: The Windows Service was successfully configured but there was an error starting it. Error code starting Windows Service: %d.

[#log-ref-log-ref-ERR_MAKELDIF_CANNOT_WRITE_ENTRY_WITHOUT_DN_1713]
ID: 1713::
Severity: ERROR

+
Message: An error occurred while attempting to write entry to LDIF: Could not calculate the DN for the entry (no value found for the RDN attribute %s).

[#log-ref-log-ref-ERR_CLIENT_SIDE_TIMEOUT_1714]
ID: 1714::
Severity: ERROR

+
Message: A client side timeout occurred.%nAdditional Information: %s.

[#log-ref-log-ref-ERR_RECURRING_SCHEDULE_FORMAT_ERROR_1718]
ID: 1718::
Severity: ERROR

+
Message: The provided schedule value has an invalid format. The schedule must be expressed using a crontab(5) format. Error details: %s.

[#log-ref-log-ref-ERR_REBUILDINDEX_REBUILD_DEGRADED_ERROR_1721]
ID: 1721::
Severity: ERROR

+
Message: Option "--rebuildDegraded" cannot be specified with the "--%s" option.

[#log-ref-log-ref-ERR_REBUILDINDEX_REBUILD_ALL_DEGRADED_ERROR_1722]
ID: 1722::
Severity: ERROR

+
Message: Option "--rebuildAll" cannot be specified with the "--%s" option.

[#log-ref-log-ref-ERR_CONFIGDS_CANNOT_UPDATE_DIGEST_MD5_FQDN_1733]
ID: 1733::
Severity: ERROR

+
Message: An error occurred while attempting to update the FQDN for the DIGEST-MD5 SASL mechanism: %s.

[#log-ref-log-ref-ERR_BUILDVERSION_NOT_FOUND_1737]
ID: 1737::
Severity: ERROR

+
Message: The version of the installed OpenDJ could not be determined because the version file '%s' could not be found. Restore it from backup before continuing.

[#log-ref-log-ref-ERR_BUILDVERSION_MALFORMED_1738]
ID: 1738::
Severity: ERROR

+
Message: The version of the installed OpenDJ could not be determined because the version file '%s' exists but contains invalid data. Restore it from backup before continuing.

[#log-ref-log-ref-ERR_BUILDVERSION_MISMATCH_1739]
ID: 1739::
Severity: ERROR

+
Message: The OpenDJ binary version '%s' does not match the installed version '%s'. Please run upgrade before continuing.

[#log-ref-log-ref-ERR_UPGRADE_MAIN_UPGRADE_PROCESS_1800]
ID: 1800::
Severity: ERROR

+
Message: The upgrade failed to complete for the following reason: %s.

[#log-ref-log-ref-ERR_UPGRADE_REQUIRES_SERVER_OFFLINE_1805]
ID: 1805::
Severity: ERROR

+
Message: OpenDJ cannot be upgraded because the server is currently running. Please stop the server and try again.

[#log-ref-log-ref-ERR_UPGRADE_VERSION_UP_TO_DATE_1806]
ID: 1806::
Severity: ERROR

+
Message: OpenDJ has already been upgraded to version %s.

[#log-ref-log-ref-ERR_UPGRADE_DISPLAY_NOTIFICATION_ERROR_1807]
ID: 1807::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to display a notification: %s.

[#log-ref-log-ref-ERR_UPGRADE_DISPLAY_CONFIRM_ERROR_1808]
ID: 1808::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to display a confirmation : %s.

[#log-ref-log-ref-ERR_UPGRADE_TASKS_FAIL_1812]
ID: 1812::
Severity: ERROR

+
Message: An error occurred while performing an upgrade task: %s.

[#log-ref-log-ref-ERR_UPGRADE_UNKNOWN_OC_ATT_1816]
ID: 1816::
Severity: ERROR

+
Message: No %s with OID %s exists in the schema.

[#log-ref-log-ref-ERR_UPGRADE_CONFIG_ERROR_UPGRADE_FOLDER_1817]
ID: 1817::
Severity: ERROR

+
Message: An error occurred when trying to upgrade the config/upgrade folder: %s.

[#log-ref-log-ref-ERR_UPGRADE_FAILS_1827]
ID: 1827::
Severity: ERROR

+
Message: The upgrade failed because %d errors were encountered. Please check log for further details.

[#log-ref-log-ref-ERR_UPGRADE_COPYSCHEMA_FAILS_1828]
ID: 1828::
Severity: ERROR

+
Message: An error occurred while copying the schema file '%s': %s.

[#log-ref-log-ref-ERR_UPGRADE_ADDATTRIBUTE_FAILS_1829]
ID: 1829::
Severity: ERROR

+
Message: An error occurred while adding one or more attributes to the schema file '%s': %s.

[#log-ref-log-ref-ERR_UPGRADE_ADDOBJECTCLASS_FAILS_1830]
ID: 1830::
Severity: ERROR

+
Message: An error occurred while adding one or more object classes to the schema file '%s': %s.

[#log-ref-log-ref-ERR_UPGRADE_ADD_CONFIG_FILE_FAILS_1835]
ID: 1835::
Severity: ERROR

+
Message: An error occurred while adding configuration file '%s': %s.

[#log-ref-log-ref-ERR_UPGRADE_RENAME_SNMP_SECURITY_CONFIG_FILE_1838]
ID: 1838::
Severity: ERROR

+
Message: An error occurred when trying to rename the SNMP security config file: %s.

[#log-ref-log-ref-ERR_UPGRADE_PERFORMING_POST_TASKS_FAIL_1843]
ID: 1843::
Severity: ERROR

+
Message: An error occurred during post upgrade task. Process aborted. Please check log for further details.

[#log-ref-log-ref-ERR_UPGRADE_INVALID_LOG_FILE_1846]
ID: 1846::
Severity: ERROR

+
Message: Invalid log file %s.

[#log-ref-log-ref-ERR_UPGRADE_CORRUPTED_TEMPLATE_1850]
ID: 1850::
Severity: ERROR

+
Message: '%s' is missing or empty, it is probably corrupted.

[#log-ref-log-ref-ERR_UPGRADE_DSJAVAPROPERTIES_FAILED_1853]
ID: 1853::
Severity: ERROR

+
Message: The dsjavaproperties tool failed to run. Please rerun dsjavaproperties manually.

[#log-ref-log-ref-ERR_BACKEND_TOOL_ERROR_LISTING_BASE_DNS_1863]
ID: 1863::
Severity: ERROR

+
Message: An error occurred while listing the base DNs: %s.

[#log-ref-log-ref-ERR_BACKEND_TOOL_ERROR_LISTING_TREES_1864]
ID: 1864::
Severity: ERROR

+
Message: An error occurred while listing indexes: %s.

[#log-ref-log-ref-ERR_BACKEND_TOOL_ERROR_INITIALIZING_BACKEND_1865]
ID: 1865::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to initialize the backend '%s': %s.

[#log-ref-log-ref-ERR_BACKEND_TOOL_ERROR_READING_TREE_1866]
ID: 1866::
Severity: ERROR

+
Message: An unexpected error occurred while attempting to read and/or decode records from an index: %s.

[#log-ref-log-ref-ERR_BACKEND_TOOL_NO_TREE_FOR_NAME_1868]
ID: 1868::
Severity: ERROR

+
Message: No index exists with the requested name '%s' in base DN '%s' and backend '%s'.

[#log-ref-log-ref-ERR_BACKEND_TOOL_ONLY_ONE_MIN_KEY_1869]
ID: 1869::
Severity: ERROR

+
Message: Cannot specify a minimum key both as a string and as an hexadecimal string.

[#log-ref-log-ref-ERR_BACKEND_TOOL_ONLY_ONE_MAX_KEY_1870]
ID: 1870::
Severity: ERROR

+
Message: Cannot specify a maximum key both as a string and as an hexadecimal string.

[#log-ref-log-ref-ERR_BACKEND_TOOL_PROCESSING_ARGUMENT_1871]
ID: 1871::
Severity: ERROR

+
Message: An error occurred while processing arguments: %s.

[#log-ref-log-ref-ERR_BACKEND_TOOL_EXECUTING_COMMAND_1872]
ID: 1872::
Severity: ERROR

+
Message: An error occurred while trying to execute %s: %s.

[#log-ref-log-ref-ERR_BACKEND_TOOL_CANNOT_CONFIGURE_BACKEND_1881]
ID: 1881::
Severity: ERROR

+
Message: Cannot configure backend %s: %s.

[#log-ref-log-ref-ERR_BACKEND_TOOL_CURSOR_AT_KEY_NUMBER_1887]
ID: 1887::
Severity: ERROR

+
Message: At key number %d, %s:.

[#log-ref-log-ref-ERR_BACKEND_TOOL_DECODER_NOT_AVAILABLE_1890]
ID: 1890::
Severity: ERROR

+
Message: Data decoder for printing is not available, should use hex dump.

[#log-ref-log-ref-ERR_BACKEND_TOOL_NO_TREE_FOR_NAME_IN_STORAGE_1891]
ID: 1891::
Severity: ERROR

+
Message: No storage index exists with the requested name %s in backend %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_BACKENDS_1897]
ID: 1897::
Severity: ERROR

+
Message: An error occurred while initializing server backends: %s.

[#log-ref-log-ref-ERR_CANNOT_INITIALIZE_SERVER_PLUGINS_1898]
ID: 1898::
Severity: ERROR

+
Message: An error occurred while initializing plugins: %s.

[#log-ref-log-ref-ERR_CANNOT_SUBSYSTEM_NOT_INITIALIZED_1899]
ID: 1899::
Severity: ERROR

+
Message: Subsystem %s should be initialized first.

[#log-ref-log-ref-ERR_STARTTLS_FAILED_1901]
ID: 1901::
Severity: ERROR

+
Message: StartTLS failed: the connection has been closed without receiving a response. This may indicate you tried to connect to an LDAPS port instead of the LDAP port, or that the network is down.

[#log-ref-log-ref-ERR_TASK_TOOL_LDAP_ERROR_10020]
ID: 10020::
Severity: ERROR

+
Message: ERROR: The server rejected the task for the following reason: %s.

[#log-ref-log-ref-ERR_LDIFIMPORT_LDIF_FILE_DOESNT_EXIST_10055]
ID: 10055::
Severity: ERROR

+
Message: Unable to access the LDIF file %s to import. Please check that the file is local to the server and the path correct.

[#log-ref-log-ref-ERR_INSTALLDS_NO_SUCH_BACKEND_TYPE_20009]
ID: 20009::
Severity: ERROR

+
Message: The backend type '%s' is not recognized. The supported backend types are %s.

[#log-ref-log-ref-ERR_CONFIGDS_BACKEND_TYPE_UNKNOWN_20010]
ID: 20010::
Severity: ERROR

+
Message: The backend type '%s' is not recognized. The supported backend types are %s.

[#log-ref-log-ref-ERR_CONFIGDS_SET_BACKEND_TYPE_20011]
ID: 20011::
Severity: ERROR

+
Message: An error occurred while trying to create userRoot backend type %s. Error message: %s.

[#log-ref-log-ref-ERR_INSTANCE_NOT_CONFIGURED_20013]
ID: 20013::
Severity: ERROR

+
Message: The local instance is not configured or you do not have permissions to access it.

[#log-ref-log-ref-ERR_SEARCH_INVALID_DEREFERENCE_POLICY_20014]
ID: 20014::
Severity: ERROR

+
Message: Invalid deref alias specified: %s.

[#log-ref-log-ref-ERR_FILE_NOT_FULLY_READABLE_20015]
ID: 20015::
Severity: ERROR

+
Message: Could not completely read file '%s'.

--


[#UTILITY]
=== Log Message Category: UTILITY

--

[#log-ref-log-ref-ERR_BASE64_DECODE_INVALID_LENGTH_1]
ID: 1::
Severity: ERROR

+
Message: The value %s cannot be base64-decoded because it does not have a length that is a multiple of four bytes.

[#log-ref-log-ref-ERR_BASE64_DECODE_INVALID_CHARACTER_2]
ID: 2::
Severity: ERROR

+
Message: The value %s cannot be base64-decoded because it contains an illegal character %c that is not allowed in base64-encoded values.

[#log-ref-log-ref-ERR_HEX_DECODE_INVALID_LENGTH_3]
ID: 3::
Severity: ERROR

+
Message: The value %s cannot be decoded as a hexadecimal string because it does not have a length that is a multiple of two bytes.

[#log-ref-log-ref-ERR_HEX_DECODE_INVALID_CHARACTER_4]
ID: 4::
Severity: ERROR

+
Message: The value %s cannot be decoded as a hexadecimal string because it contains an illegal character %c that is not a valid hexadecimal digit.

[#log-ref-log-ref-ERR_LDIF_INVALID_LEADING_SPACE_5]
ID: 5::
Severity: ERROR

+
Message: Unable to parse line %d ("%s") from the LDIF source because the line started with a space but there were no previous lines in the entry to which this line could be appended.

[#log-ref-log-ref-ERR_LDIF_NO_ATTR_NAME_6]
ID: 6::
Severity: ERROR

+
Message: Unable to parse LDIF entry starting at line %d because the line "%s" does not include an attribute name.

[#log-ref-log-ref-ERR_LDIF_NO_DN_7]
ID: 7::
Severity: ERROR

+
Message: Unable to parse LDIF entry starting at line %d because the first line does not contain a DN (the first line was "%s".

[#log-ref-log-ref-ERR_LDIF_INVALID_DN_9]
ID: 9::
Severity: ERROR

+
Message: Unable to parse LDIF entry starting at line %d because an error occurred while trying to parse the value of line "%s" as a distinguished name: %s.

[#log-ref-log-ref-ERR_LDIF_COULD_NOT_BASE64_DECODE_DN_11]
ID: 11::
Severity: ERROR

+
Message: Unable to parse LDIF entry starting at line %d because it was not possible to base64-decode the DN on line "%s": %s.

[#log-ref-log-ref-ERR_LDIF_COULD_NOT_BASE64_DECODE_ATTR_12]
ID: 12::
Severity: ERROR

+
Message: Unable to parse LDIF entry %s starting at line %d because it was not possible to base64-decode the attribute on line "%s": %s.

[#log-ref-log-ref-ERR_LDIF_MULTIPLE_VALUES_FOR_SINGLE_VALUED_ATTR_15]
ID: 15::
Severity: ERROR

+
Message: Entry %s starting at line %d includes multiple values for single-valued attribute %s.

[#log-ref-log-ref-ERR_LDIF_SCHEMA_VIOLATION_17]
ID: 17::
Severity: ERROR

+
Message: Entry %s read from LDIF starting at line %d is not valid because it violates the server's schema configuration: %s.

[#log-ref-log-ref-ERR_LDIF_FILE_EXISTS_18]
ID: 18::
Severity: ERROR

+
Message: The specified LDIF file %s already exists and the export configuration indicates that no attempt should be made to append to or replace the file.

[#log-ref-log-ref-ERR_LDIF_INVALID_URL_19]
ID: 19::
Severity: ERROR

+
Message: Unable to parse LDIF entry %s starting at line %d because the value of attribute %s was to be read from a URL but the URL was invalid: %s.

[#log-ref-log-ref-ERR_LDIF_URL_IO_ERROR_20]
ID: 20::
Severity: ERROR

+
Message: Unable to parse LDIF entry %s starting at line %d because the value of attribute %s was to be read from URL %s but an error occurred while trying to read that content: %s.

[#log-ref-log-ref-ERR_REJECT_FILE_EXISTS_21]
ID: 21::
Severity: ERROR

+
Message: The specified reject file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the file.

[#log-ref-log-ref-ERR_LDIF_COULD_NOT_EVALUATE_FILTERS_FOR_IMPORT_22]
ID: 22::
Severity: ERROR

+
Message: An error occurred while attempting to determine whether LDIF entry "%s" starting at line %d should be imported as a result of the include and exclude filter configuration: %s.

[#log-ref-log-ref-ERR_LDIF_COULD_NOT_EVALUATE_FILTERS_FOR_EXPORT_23]
ID: 23::
Severity: ERROR

+
Message: An error occurred while attempting to determine whether LDIF entry "%s" should be exported as a result of the include and exclude filter configuration: %s.

[#log-ref-log-ref-ERR_LDIF_INVALID_DELETE_ATTRIBUTES_24]
ID: 24::
Severity: ERROR

+
Message: Error in the LDIF change record entry. Invalid attributes specified for the delete operation.

[#log-ref-log-ref-ERR_LDIF_NO_MOD_DN_ATTRIBUTES_25]
ID: 25::
Severity: ERROR

+
Message: Error in the LDIF change record entry. No attributes specified for the mod DN operation.

[#log-ref-log-ref-ERR_LDIF_NO_DELETE_OLDRDN_ATTRIBUTE_26]
ID: 26::
Severity: ERROR

+
Message: Error in the LDIF change record entry. No delete old RDN attribute specified for the mod DN operation.

[#log-ref-log-ref-ERR_LDIF_INVALID_DELETE_OLDRDN_ATTRIBUTE_27]
ID: 27::
Severity: ERROR

+
Message: Error in the LDIF change record entry. Invalid value "%s" for the delete old RDN attribute specified for the mod DN operation.

[#log-ref-log-ref-ERR_LDIF_INVALID_CHANGERECORD_ATTRIBUTE_28]
ID: 28::
Severity: ERROR

+
Message: Error in the LDIF change record entry. Invalid attribute "%s" specified. Expecting attribute "%s".

[#log-ref-log-ref-ERR_LDIF_INVALID_MODIFY_ATTRIBUTE_29]
ID: 29::
Severity: ERROR

+
Message: Error in the LDIF change record entry. Invalid attribute "%s" specified. Expecting one of the following attributes "%s".

[#log-ref-log-ref-ERR_LDIF_INVALID_CHANGETYPE_ATTRIBUTE_30]
ID: 30::
Severity: ERROR

+
Message: Error in the LDIF change record entry. Invalid value "%s" for the changetype specified. Expecting one of the following values "%s".

[#log-ref-log-ref-ERR_SCHEMANAME_EMPTY_VALUE_32]
ID: 32::
Severity: ERROR

+
Message: The provided value could not be parsed to determine whether it contained a valid schema element name or OID because it was null or empty.

[#log-ref-log-ref-ERR_SCHEMANAME_ILLEGAL_CHAR_33]
ID: 33::
Severity: ERROR

+
Message: The provided value "%s" does not contain a valid schema element name or OID because it contains an illegal character %c at position %d.

[#log-ref-log-ref-ERR_SCHEMANAME_CONSECUTIVE_PERIODS_34]
ID: 34::
Severity: ERROR

+
Message: The provided value "%s" does not contain a valid schema element name or OID because the numeric OID contains two consecutive periods at position %d.

[#log-ref-log-ref-ERR_MOVEFILE_NO_SUCH_FILE_72]
ID: 72::
Severity: ERROR

+
Message: The file to move %s does not exist.

[#log-ref-log-ref-ERR_MOVEFILE_NOT_FILE_73]
ID: 73::
Severity: ERROR

+
Message: The file to move %s exists but is not a file.

[#log-ref-log-ref-ERR_MOVEFILE_NO_SUCH_DIRECTORY_74]
ID: 74::
Severity: ERROR

+
Message: The target directory %s does not exist.

[#log-ref-log-ref-ERR_MOVEFILE_NOT_DIRECTORY_75]
ID: 75::
Severity: ERROR

+
Message: The target directory %s exists but is not a directory.

[#log-ref-log-ref-ERR_EMAILMSG_INVALID_SENDER_ADDRESS_76]
ID: 76::
Severity: ERROR

+
Message: The provided sender address %s is invalid: %s.

[#log-ref-log-ref-ERR_EMAILMSG_INVALID_RECIPIENT_ADDRESS_77]
ID: 77::
Severity: ERROR

+
Message: The provided recipient address %s is invalid: %s.

[#log-ref-log-ref-ERR_EMAILMSG_CANNOT_SEND_78]
ID: 78::
Severity: ERROR

+
Message: The specified e-mail message could not be sent using any of the configured mail servers.

[#log-ref-log-ref-ERR_LDAPURL_NO_COLON_SLASH_SLASH_110]
ID: 110::
Severity: ERROR

+
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain the necessary :// component to separate the scheme from the rest of the URL.

[#log-ref-log-ref-ERR_LDAPURL_NO_SCHEME_111]
ID: 111::
Severity: ERROR

+
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain a protocol scheme.

[#log-ref-log-ref-ERR_LDAPURL_NO_HOST_112]
ID: 112::
Severity: ERROR

+
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain a host before the colon to specify the port number.

[#log-ref-log-ref-ERR_LDAPURL_NO_PORT_113]
ID: 113::
Severity: ERROR

+
Message: The provided string "%s" cannot be decoded as an LDAP URL because it does not contain a port number after the colon following the host.

[#log-ref-log-ref-ERR_LDAPURL_CANNOT_DECODE_PORT_114]
ID: 114::
Severity: ERROR

+
Message: The provided string "%s" cannot be decoded as an LDAP URL because the port number portion %s cannot be decoded as an integer.

[#log-ref-log-ref-ERR_LDAPURL_INVALID_PORT_115]
ID: 115::
Severity: ERROR

+
Message: The provided string "%s" cannot be decoded as an LDAP URL because the provided port number %d is not within the valid range between 1 and 65535.

[#log-ref-log-ref-ERR_LDAPURL_INVALID_SCOPE_STRING_116]
ID: 116::
Severity: ERROR

+
Message: The provided string "%s" cannot be decoded as an LDAP URL because the scope string %s was not one of the allowed values of base, one, sub, or subordinate.

[#log-ref-log-ref-ERR_LDAPURL_PERCENT_TOO_CLOSE_TO_END_117]
ID: 117::
Severity: ERROR

+
Message: The provided URL component "%s" could not be decoded because the percent character at byte %d was not followed by two hexadecimal digits.

[#log-ref-log-ref-ERR_LDAPURL_INVALID_HEX_BYTE_118]
ID: 118::
Severity: ERROR

+
Message: The provided URL component "%s" could not be decoded because the character at byte %d was not a valid hexadecimal digit.

[#log-ref-log-ref-ERR_LDAPURL_CANNOT_CREATE_UTF8_STRING_119]
ID: 119::
Severity: ERROR

+
Message: An error occurred while attempting to represent a byte array as a UTF-8 string during the course of decoding a portion of an LDAP URL: %s.

[#log-ref-log-ref-ERR_CHARSET_NO_COLON_120]
ID: 120::
Severity: ERROR

+
Message: Cannot decode value "%s" as a named character set because it does not contain a colon to separate the name from the set of characters.

[#log-ref-log-ref-ERR_CHARSET_CONSTRUCTOR_NO_NAME_121]
ID: 121::
Severity: ERROR

+
Message: The named character set is invalid because it does not contain a name.

[#log-ref-log-ref-ERR_CHARSET_CONSTRUCTOR_INVALID_NAME_CHAR_122]
ID: 122::
Severity: ERROR

+
Message: The named character set is invalid because the provide name "%s" has an invalid character at position %d. Only ASCII alphabetic characters are allowed in the name.

[#log-ref-log-ref-ERR_CHARSET_NO_NAME_123]
ID: 123::
Severity: ERROR

+
Message: Cannot decode value "%s" as a named character set because it does not contain a name to use for the character set.

[#log-ref-log-ref-ERR_CHARSET_NO_CHARS_124]
ID: 124::
Severity: ERROR

+
Message: Cannot decode value "%s" as a named character set because there are no characters to include in the set.

[#log-ref-log-ref-ERR_FILEPERM_SET_NO_SUCH_FILE_141]
ID: 141::
Severity: ERROR

+
Message: Unable to set permissions for file %s because it does not exist.

[#log-ref-log-ref-ERR_FILEPERM_SET_JAVA_EXCEPTION_143]
ID: 143::
Severity: ERROR

+
Message: One or more exceptions were thrown in the process of updating the file permissions for %s. Some of the permissions for the file may have been altered.

[#log-ref-log-ref-ERR_FILEPERM_INVALID_UNIX_MODE_STRING_146]
ID: 146::
Severity: ERROR

+
Message: The provided string %s does not represent a valid UNIX file mode. UNIX file modes must be a three-character string in which each character is a numeric digit between zero and seven.

[#log-ref-log-ref-ERR_EXEC_DISABLED_147]
ID: 147::
Severity: ERROR

+
Message: The %s command will not be allowed because the Directory Server has been configured to refuse the use of the exec method.

[#log-ref-log-ref-ERR_RENAMEFILE_CANNOT_RENAME_157]
ID: 157::
Severity: ERROR

+
Message: Failed to rename file %s to %s.

[#log-ref-log-ref-ERR_RENAMEFILE_CANNOT_DELETE_TARGET_158]
ID: 158::
Severity: ERROR

+
Message: Failed to delete target file %s. Make sure the file is not currently in use by this or another application.

[#log-ref-log-ref-ERR_EXPCHECK_TRUSTMGR_CLIENT_CERT_EXPIRED_159]
ID: 159::
Severity: ERROR

+
Message: Refusing to trust client or issuer certificate '%s' because it expired on %s.

[#log-ref-log-ref-ERR_EXPCHECK_TRUSTMGR_CLIENT_CERT_NOT_YET_VALID_160]
ID: 160::
Severity: ERROR

+
Message: Refusing to trust client or issuer certificate '%s' because it is not valid until %s.

[#log-ref-log-ref-ERR_EXPCHECK_TRUSTMGR_SERVER_CERT_EXPIRED_161]
ID: 161::
Severity: ERROR

+
Message: Refusing to trust server or issuer certificate '%s' because it expired on %s.

[#log-ref-log-ref-ERR_EXPCHECK_TRUSTMGR_SERVER_CERT_NOT_YET_VALID_162]
ID: 162::
Severity: ERROR

+
Message: Refusing to trust server or issuer certificate '%s' because it is not valid until %s.

[#log-ref-log-ref-ERR_SKIP_FILE_EXISTS_164]
ID: 164::
Severity: ERROR

+
Message: The specified skip file %s already exists and the import configuration indicates that no attempt should be made to append to or replace the file.

[#log-ref-log-ref-ERR_LDIF_SKIP_165]
ID: 165::
Severity: ERROR

+
Message: Skipping entry %s because the DN is not one that should be included based on the include and exclude branches.

[#log-ref-log-ref-ERR_EMBEDUTILS_SERVER_ALREADY_RUNNING_167]
ID: 167::
Severity: ERROR

+
Message: The Directory Server cannot be started because it is already running.

[#log-ref-log-ref-ERR_EMAIL_NO_SUCH_BODY_FILE_181]
ID: 181::
Severity: ERROR

+
Message: The file %s specified as the body file for the e-mail message does not exist.

[#log-ref-log-ref-ERR_EMAIL_CANNOT_PROCESS_BODY_FILE_182]
ID: 182::
Severity: ERROR

+
Message: An error occurred while attempting to process message body file %s: %s.

[#log-ref-log-ref-ERR_EMAIL_NO_SUCH_ATTACHMENT_FILE_183]
ID: 183::
Severity: ERROR

+
Message: The attachment file %s does not exist.

[#log-ref-log-ref-ERR_EMAIL_CANNOT_ATTACH_FILE_184]
ID: 184::
Severity: ERROR

+
Message: An error occurred while trying to attach file %s: %s.

[#log-ref-log-ref-ERR_EMAIL_CANNOT_SEND_MESSAGE_185]
ID: 185::
Severity: ERROR

+
Message: An error occurred while trying to send the e-mail message: %s.

[#log-ref-log-ref-ERR_BASE64_CANNOT_READ_RAW_DATA_196]
ID: 196::
Severity: ERROR

+
Message: An error occurred while attempting to read the raw data to encode: %s.

[#log-ref-log-ref-ERR_BASE64_CANNOT_WRITE_ENCODED_DATA_197]
ID: 197::
Severity: ERROR

+
Message: An error occurred while attempting to write the encoded data: %s.

[#log-ref-log-ref-ERR_BASE64_CANNOT_READ_ENCODED_DATA_198]
ID: 198::
Severity: ERROR

+
Message: An error occurred while attempting to read the base64-encoded data: %s.

[#log-ref-log-ref-ERR_BASE64_CANNOT_WRITE_RAW_DATA_199]
ID: 199::
Severity: ERROR

+
Message: An error occurred while attempting to write the decoded data: %s.

[#log-ref-log-ref-ERR_BASE64_UNKNOWN_SUBCOMMAND_200]
ID: 200::
Severity: ERROR

+
Message: Unknown subcommand %s.

[#log-ref-log-ref-ERR_LDIF_REJECTED_BY_PLUGIN_NOMESSAGE_224]
ID: 224::
Severity: ERROR

+
Message: Rejecting entry %s because it was rejected by a plugin.

[#log-ref-log-ref-ERR_LDIF_REJECTED_BY_PLUGIN_225]
ID: 225::
Severity: ERROR

+
Message: Rejecting entry %s because it was rejected by a plugin: %s.

[#log-ref-log-ref-ERR_LDAP_CONN_BAD_HOST_NAME_237]
ID: 237::
Severity: ERROR

+
Message: The hostname "%s" could not be resolved. Please check you have provided the correct address.

[#log-ref-log-ref-ERR_LDAP_CONN_BAD_PORT_NUMBER_238]
ID: 238::
Severity: ERROR

+
Message: Invalid port number "%s". Please enter a valid port number between 1 and 65535.

[#log-ref-log-ref-ERR_LDAP_CONN_PROMPT_SECURITY_INVALID_FILE_PATH_244]
ID: 244::
Severity: ERROR

+
Message: The provided path is not valid.

[#log-ref-log-ref-ERR_CONFIRMATION_TRIES_LIMIT_REACHED_267]
ID: 267::
Severity: ERROR

+
Message: Confirmation tries limit reached (%d).

[#log-ref-log-ref-ERR_UNEXPECTED_268]
ID: 268::
Severity: ERROR

+
Message: Unexpected error. Details: %s.

[#log-ref-log-ref-ERR_TRIES_LIMIT_REACHED_269]
ID: 269::
Severity: ERROR

+
Message: Input tries limit reached (%d).

[#log-ref-log-ref-ERR_LDIF_INVALID_ATTR_OPTION_271]
ID: 271::
Severity: ERROR

+
Message: Unable to parse LDIF entry %s starting at line %d because it has an invalid binary option for attribute %s.

[#log-ref-log-ref-ERR_CERTMGR_INVALID_PKCS11_PATH_272]
ID: 272::
Severity: ERROR

+
Message: Invalid key store path for PKCS11 keystore, it must be %s.

[#log-ref-log-ref-ERR_CERTMGR_INVALID_KEYSTORE_PATH_273]
ID: 273::
Severity: ERROR

+
Message: Key store path %s exists but is not a file.

[#log-ref-log-ref-ERR_CERTMGR_INVALID_PARENT_274]
ID: 274::
Severity: ERROR

+
Message: Parent directory for key store path %s does not exist or is not a directory.

[#log-ref-log-ref-ERR_CERTMGR_INVALID_STORETYPE_275]
ID: 275::
Severity: ERROR

+
Message: Invalid key store type, it must be one of the following: %s, %s, %s or %s.

[#log-ref-log-ref-ERR_CERTMGR_KEYSTORE_NONEXISTANT_276]
ID: 276::
Severity: ERROR

+
Message: Keystore does not exist, it must exist to retrieve an alias, delete an alias or generate a certificate request.

[#log-ref-log-ref-ERR_CERTMGR_VALIDITY_277]
ID: 277::
Severity: ERROR

+
Message: Validity value %d is invalid, it must be a positive integer.

[#log-ref-log-ref-ERR_CERTMGR_ALIAS_ALREADY_EXISTS_278]
ID: 278::
Severity: ERROR

+
Message: A certificate with the alias %s already exists in the key store.

[#log-ref-log-ref-ERR_CERTMGR_ADD_CERT_279]
ID: 279::
Severity: ERROR

+
Message: The following error occurred when adding a certificate with alias %s to the keystore: %s.

[#log-ref-log-ref-ERR_CERTMGR_ALIAS_INVALID_280]
ID: 280::
Severity: ERROR

+
Message: The alias %s cannot be added to the keystore for one of the following reasons: it already exists in the keystore, or, it is not an instance of a trusted certificate class.

[#log-ref-log-ref-ERR_CERTMGR_CERT_REPLIES_INVALID_281]
ID: 281::
Severity: ERROR

+
Message: The alias %s is an instance of a private key entry, which is not supported being added to the keystore at this time.

[#log-ref-log-ref-ERR_CERTMGR_DELETE_ALIAS_282]
ID: 282::
Severity: ERROR

+
Message: The following error occurred when deleting a certificate with alias %s from the keystore: %s.

[#log-ref-log-ref-ERR_CERTMGR_GEN_SELF_SIGNED_CERT_284]
ID: 284::
Severity: ERROR

+
Message: The following error occurred when generating a self-signed certificate using the alias %s: %s.

[#log-ref-log-ref-ERR_CERTMGR_INVALID_CERT_FILE_285]
ID: 285::
Severity: ERROR

+
Message: The certificate file %s is invalid because it does not exists, or exists, but is not a file.

[#log-ref-log-ref-ERR_CERTMGR_ALIAS_CAN_NOT_DELETE_286]
ID: 286::
Severity: ERROR

+
Message: The alias %s cannot be deleted from the keystore because it does not exist.

[#log-ref-log-ref-ERR_CERTMGR_TRUSTED_CERT_292]
ID: 292::
Severity: ERROR

+
Message: The trusted certificate associated with alias %s could not be added to keystore because of the following reason: %s.

[#log-ref-log-ref-ERR_CERTMGR_FILE_NAME_INVALID_293]
ID: 293::
Severity: ERROR

+
Message: The %s is invalid because it is null.

[#log-ref-log-ref-ERR_CERTMGR_VALUE_INVALID_294]
ID: 294::
Severity: ERROR

+
Message: The argument %s is invalid because it is either null, or has zero length.

[#log-ref-log-ref-ERR_CERTMGR_CLASS_NOT_FOUND_295]
ID: 295::
Severity: ERROR

+
Message: A security class cannot be found in this JVM because of the following reason: %s.

[#log-ref-log-ref-ERR_CERTMGR_SECURITY_296]
ID: 296::
Severity: ERROR

+
Message: The security classes could not be initialized because of the following reason: %s.

[#log-ref-log-ref-ERR_CERTMGR_NO_METHOD_297]
ID: 297::
Severity: ERROR

+
Message: A method needed in the security classes could not be located because of the following reason: %s.

[#log-ref-log-ref-ERR_CERTMGR_CERTGEN_NOT_FOUND_298]
ID: 298::
Severity: ERROR

+
Message: The CertAndKeyGen security class cannot be found, consider setting -D%s=.

[#log-ref-log-ref-ERR_LDIF_READ_ATTR_SKIP_301]
ID: 301::
Severity: ERROR

+
Message: Skipping entry %s because the following error was received when reading its attributes: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_GET_MAC_305]
ID: 305::
Severity: ERROR

+
Message: An error occurred while attempting to obtain the %s MAC provider to create the signed hash for the backup: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_GET_DIGEST_306]
ID: 306::
Severity: ERROR

+
Message: An error occurred while attempting to obtain the %s message digest to create the hash for the backup: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_CREATE_ARCHIVE_FILE_307]
ID: 307::
Severity: ERROR

+
Message: An error occurred while trying to create the archive file %s in directory %s for the backup %s: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_GET_CIPHER_308]
ID: 308::
Severity: ERROR

+
Message: An error occurred while attempting to obtain the cipher to use to encrypt the backup: %s.

[#log-ref-log-ref-ERR_BACKUP_ZIP_COMMENT_309]
ID: 309::
Severity: ERROR

+
Message: %s backup %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_LIST_LOG_FILES_310]
ID: 310::
Severity: ERROR

+
Message: An error occurred while attempting to obtain a list of the files in directory %s to include in the backup: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_WRITE_ARCHIVE_FILE_311]
ID: 311::
Severity: ERROR

+
Message: An error occurred while attempting to back up file %s of backup %s: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_CLOSE_ZIP_STREAM_312]
ID: 312::
Severity: ERROR

+
Message: An error occurred while trying to close the archive file %s in directory %s: %s.

[#log-ref-log-ref-ERR_BACKUP_UNSIGNED_HASH_ERROR_313]
ID: 313::
Severity: ERROR

+
Message: The computed hash of backup %s is different to the value computed at time of backup.

[#log-ref-log-ref-ERR_BACKUP_SIGNED_HASH_ERROR_314]
ID: 314::
Severity: ERROR

+
Message: The computed signed hash of backup %s is different to the value computed at time of backup.

[#log-ref-log-ref-ERR_CANNOT_RENAME_RESTORE_DIRECTORY_315]
ID: 315::
Severity: ERROR

+
Message: The directory %s, containing the files restored from backup, could not be renamed to the directory %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_316]
ID: 316::
Severity: ERROR

+
Message: An error occurred while attempting to update the backup descriptor file %s with information about the backup: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_RESTORE_317]
ID: 317::
Severity: ERROR

+
Message: An error occurred while attempting to restore the files from backup %s: %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_GET_MAC_KEY_ID_323]
ID: 323::
Severity: ERROR

+
Message: An error occurred while attempting to obtain the MAC key ID to create the signed hash for the backup %s : %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_CREATE_DIRECTORY_TO_RESTORE_FILE_324]
ID: 324::
Severity: ERROR

+
Message: An error occurred while attempting to create a directory to restore the file %s for backup of %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_SAVE_FILES_BEFORE_RESTORE_325]
ID: 325::
Severity: ERROR

+
Message: An error occurred while attempting to save files from root directory %s to target directory %s, for backup of %s : %s.

[#log-ref-log-ref-ERR_BACKUP_CANNOT_CREATE_SAVE_DIRECTORY_326]
ID: 326::
Severity: ERROR

+
Message: An error occurred while attempting to create a save directory with base path %s before restore of backup of %s: %s.

--


