Category: Connections and Protocols

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.

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.

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.

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.

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.

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.

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.

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.

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.

Severity: ERROR

Message: The original result code for this message was 10 but this result is not allowed for LDAPv2 clients.

Severity: ERROR

Message: The response included one or more referrals, which are not allowed for LDAPv2 clients. The referrals included were: %s.

Severity: ERROR

Message: The Directory Server has been configured to deny access to LDAPv2 clients. This connection will be closed.

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.

Severity: ERROR

Message: The attempt to register this connection with the Directory Server was rejected. This indicates that the server already has the maximum allowed number of concurrent connections established.

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.

Severity: ERROR

Message: User %s specified in the proxied authorization V1 control does not exist in the Directory Server.

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.

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.

Severity: ERROR

Message: User %s specified in the proxied authorization V2 control does not exist in the Directory Server.

Severity: ERROR

Message: Use of the proxied authorization V1 control for user %s is not allowed by the password policy configuration.

Severity: ERROR

Message: LDAPv2 clients are not allowed to use request controls.

Severity: ERROR

Message: You do not have sufficient privileges to perform search operations through JMX.

Severity: ERROR

Message: You do not have sufficient privileges to establish the connection through JMX. At least JMX_READ privilege is required.

Severity: ERROR

Message: User %s does not exist in the directory.

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.

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.

Severity: ERROR

Message: An I/O error occurred while the LDIF connection handler was processing LDIF file %s: %s.

Severity: ERROR

Message: An error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %s.

Severity: ERROR

Message: An error occurred while the LDIF connection handler was attempting to delete processed file %s: %s.

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.

Severity: ERROR

Message: Traps Destination %s is an unknown host. Traps will not be sent to this destination.

Severity: ERROR

Message: You do not have the appropriate OpenDMK jar files to enable the SNMP Connection Handler. The jdmkrt.jar file must be installed into the 'extlib' directory. The SNMP connection Handler could not be started.

Severity: ERROR

Message: Cannot initialize the SNMP Connection Handler. Please check the configuration attributes.

Severity: ERROR

Message: No valid trap destinations has been found. No trap will be sent.

Severity: ERROR

Message: An error occurred while attempting to initialize the SSL context for use in the LDAP Connection Handler: %s.

Severity: ERROR

Message: The Directory Server does not support LDAP protocol version %d. This connection will be closed.

Severity: ERROR

Message: The required OpenDMK classes could not be loaded using jar file '%s'. Verify that the jar file is not corrupted.

Severity: ERROR

Message: Cannot decode the provided control %s because an error occurred while attempting to decode the control value: %s.

Severity: ERROR

Message: Unable to process the provided internal modifications request control because it did not contain an origin.

Severity: ERROR

Message: Cannot decode the provided entry changelog notification control because an error occurred while attempting to decode the control value: %s.

Severity: ERROR

Message: Unable to process the provided internal modifications request control: %s.

Severity: ERROR

Message: Unable to process the provided replication context request control because it did not contain a CSN.

Severity: ERROR

Message: Unable to process the provided replication context request control because it did not contain an entry UUID.

Severity: ERROR

Message: Unable to process the provided replication context request control: %s.

Severity: ERROR

Message: Unable to process response received for HTTP client connection for request '%s' because the response '%s' is not of any of the expected types.

Severity: ERROR

Message: An error occurred during multi-stage authentication: '%s'.

Severity: ERROR

Message: No result received after completion for request '%s' received for HTTP client connection.

Severity: ERROR

Message: The GSER value does not contain a separator at the current position: %s.

Severity: ERROR

Message: The GSER value does not contain a valid String value at the current position: %s.

Severity: ERROR

Message: The GSER value does not contain a valid integer value at the current position: %s.

Severity: ERROR

Message: The GSER value does not contain a valid identifier at the current position: %s.

Severity: ERROR

Message: Unable to process request '%s' received for JMX client because this type of request is not supported for JMX.

Severity: ERROR

Message: The GSER value does not contain a valid IdentifiedChoiceValue at the current position: %s.

Severity: ERROR

Message: Unable to process response received for JMX client connection for request '%s' because the response '%s' is not of any of the expected types.

Severity: ERROR

Message: Authorization as '%s' specified in the proxied authorization control is not permitted.

Severity: ERROR

Message: The key with alias '%s' used by '%s' could not be found, which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configured.

Severity: ERROR

Message: No usable key was found for '%s', which may cause subsequent SSL connections to fail. Verify that the underlying keystore is properly configured.

Severity: ERROR

Message: Unable to process the provided server-side sort request control because it references unrecognized attribute type '%s'.

Severity: ERROR

Message: Could not write data to the client for %s.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is disabled.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is expired.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account is locked.

Severity: ERROR

Message: Use of the proxied authorization V2 control for user %s is not allowed: the account's password is expired.

Severity: ERROR

Message: The connection attempt from client %s to %s has been rejected because there are too many open connections from this client.

Severity: ERROR

Message: Unable to process the provided server-side sort request control: %s.

Severity: ERROR

Message: The key with alias '%s' used by '%s' appears to be invalid. The key will be used, but SSL connections may fail depending on the validation performed by the peer. Verify that the underlying keystore is properly configured.