Common Error Messages

This section describes the error messages displayed in the instance-path/logs/errors and instance-path/logs/access logs and the appropriate action to take should these errors occur.

No value provided for required attribute listenPort in client listener listener-entry-dn. Disabling the listener.

Solution:

Set the listen-port in ldap-listener or ldaps-listener with a port number in which the listener should listen for new connections from the client

Attribute listenPort must have a value between 1 and 65535. Disabling the listener.

Solution:

Set the listen-port in ldap-listener or ldaps-listener with a port number that should be in the range from 1 to 65535.

Attempt to reload Proxy Server configuration failed. (exception-detail). Current configuration not altered.

Solution:

Check the server configuration is valid, that is, it contains all the necessary entries and the configuration file is a valid ldif file.

Directory Proxy Server configuration reload failed. Directory Proxy server configuration may be inconsistent.

Solution:

Check the server configuration is valid, that is, it contains all the necessary entries and the configuration file is a valid ldif file.

Unable to create entry from information starting at line line-number in the configuration file -- "dn: " expected but found "problematic-line-from-config-file".

Solution:

Check if the server configuration file is a valid ldif file.

Unable to create entry from information starting at line line-number in the configuration file -- "attr: value" expected but found "problematic-line-from-config-file".

Solution:

Check if the server configuration file is a valid ldif file.

Unable to initialize SSL (exception-detail) -- SSL may fail.

Solution:

Check the SSL configuration - certificate database location, keystore password, nick names of client and server certificates.

Attempt to reload file ldif-file-name failed. (exception-detail). Current DIT not altered.

Solution:

Check if the server configuration file is a valid ldif file.

Search of "search-base-dn" would have returned multiple data views. This indicates a bad distribution configuration.

Solution:

Check if there are more than one data views with the same base dn.

Invalid value for attribute listenPort. Port already in use.

Solution:

Set the listen-port in ldap-listener or ldaps-listener with a port number that is not in use.

Can't invoke alert plugin config-entry-dn-of-alert-plugin -- exception-detail

Solution:

Check the alert plugin configuration.

Unable to register plugin config-entry-dn-of-postop-plugin as a postoperation add plugin -- exception-detail

Solution:

Check the postop plugin configuration.

The attribute attribute-name does not support case sensitive queries. Use only cis ldap-syntax for this attribute.

Solution:

The ldap-syntax of jdbc-attr is specified as ces and the matching sql column is found to be case-insensitive. Directory Proxy Server supports only the following possibilities - ldap-syntax:cis and sql-column:case-insensitive, ldap-syntax:cis and sql-column:case-sensitive, ldap-syntax:ces and sql-column:case-sensitive. Change the configuration to the one supported by Directory Proxy Server.

Server address provided in attribute serverAddress in configuration entry config-entry-dn-of-ldap-data-source can't be resolved. -- LDAP Server ldap-data-source-name disabled.

Solution:

Check if the host-address value provided in ldap-address attribute of ldap-data-source is valid and resolvable.

Could not decrypt password exception-detail

Solution:

If the password values in the server configuration are changed manually or through some other means, restore the password value with the valid value that was present previously.

Unable to create client listener name-of-listener: I/O Exception detail. Disabling the client listener.

Solution:

Check the listener address and port.

SSL Initialization Failed: exception-detail

Solution:

Check the SSL configuration.

Unable to access database metadata for table jdbc-table-name in data view jdbc-data-view-name -- some SQL statements may fail.

Solution:

Check the configuration or the connection to the back-end database.

Unable to get the Metadata information for the backend jdbc-data-source-info -- exception-detail

Solution:

Check if the connection to the back-end database specified in jdbc-data-source is alive.

Failed to create a connection to ldap-data-source-info.

Solution:

Check if the connection to the back-end LDAP server specified in ldap-data-source is alive. Also check the ldap-data-source configuration.

SQL Exception when committing the transaction to the database: db-name on server db-url -- exception-detail Cause: cause-of-exception SQL State: sql-state Vendor specific exception code: error-code.

Solution:

Check if the connection to the back-end database specified in jdbc-data-source is alive. Also refer to the documentation of RDBMS server vendor for the possible causes of the problem

SQL Exception when executing query to get column metadata: exception-detail Cause: cause-of-exception SQL State: sql-state Vendor specific exception code: error-code.

Solution:

Check if the column specified in JDBC attributes exists in the table at the back-end. Check if the connection to the back-end database specified in jdbc-data-source is alive. Refer the documentation of RDBMS server vendor for the possible causes of the problem.

Unable to connect to JDBC server jdbc-data-source-info -- exception-detail

Solution:

Check the jdbc-data-source configuration.

Fatal uncaughtException in thread-name. No more monitoring running on data-source-info

Solution:

Check the available Java Virtual Machine (JVM) memory for Directory Proxy Server.

Fatal uncaughtException in thread-name. Abandon current operation.

Solution:

Check the available JVM memory for Directory Proxy Server.

Fatal uncaughtException in thread-name.Abandon and send error response to the client.

Solution:

Check the available JVM memory for Directory Proxy Server.

Fatal uncaughtException in thread-name. Disconnecting all client connections.

Solution:

Check the available JVM memory for Directory Proxy Server.

ACI syntax error

Solution:

Check the ACI Syntax.