Appendix C Error Messages

Appendix C
Error Messages

This appendix provides a listing of primary error messages for the Join Engine and Universal Text Connector, along with causes and solutions. The messages are generated to log files.

This appendix contains the following sections:

Join Engine Messages

Universal Connector Messages

Novell eDirectory and Lotus Notes Connector Messages

Join Engine Messages

The table below provides a list of Join Engine error messages arranged in alphabetical order. Oracle database Connector error messages are also included in this section. The messages are reported in the logs located here:

NETSITE_ROOT/join-engine/logs

Table C-1 List of messages, the message type and the possible cause and solution
Message	Message Type	Cause and Solution
DA_S_TIMELIMIT_EXCEEDED	Warning	The search operation could not be completed within the maximum time limit. Go to Configuration > Meta-Directory > Data Servers > Tuning and increase value of “Maximum Operation result time” parameter
DA_S_SIZELIMIT_EXCEEDED	Warning	The search found more than the maximum number of results. Go to Directory Server->Configuration->Performance and increase the number of entries specified at “Size Limit” parameter
DA_E_NO_SUCH_OBJECT	Error/Warning	The entry specified in the request does not exist. There are some situations where this message does not indicate an error. For instance during DCNS polling, a search is done for the lastchangenumber + 1 at regular intervals, which returns this error if the changenumber does not exist, which does not indicate an error.
DA_E_UNWILLING_TO _PERFORM	Error	Indicates that the LDAP server cannot process the request because of server-defined restrictions. The possible reasons for this error message are: - If the server is unable to sort the results. This could be prevented by adding the required indexes as mentioned in Directory Server Performance Tuning for Meta-Directory in the Sun ONE Meta-Directory Deployment Guide. - modRDN operation failed. If you rename an entry and additionally move the entry under a new parent, the LDAP protocol command to do so must specify the “newsuperior” or the DN of the parent. - The ldbm database plug-in did not load properly. - The add entry request violates the server's structure rules. - The modify attribute request specifies attributes that users cannot modify. - Password restrictions prevent the action. - Connection restrictions prevent the action.
DA_E_OBJECT_CLASS_VIOLATION	Error	An object class violation occurred when the LDAP server checked the data sent by the client against the server-side schema (e.g. a “must” attribute was missing in the entry data).
DA_S_NO_RESULTS_RETURNED	Information	Indicates that a result code was not returned, instead an entry/search referral was returned.
DA_E_BAD_RETRY_TIMES_SYNTAX	Error	The syntax used to specify the retry time schedule was incorrect. Go to Configuration > Meta-Directory > Data Servers > Tuning. Correct the value specified for the Retry Intervals attribute.
DA_E_USER_TIMELIMIT _EXCEEDED	Error	A search in the Directory Server has timed out. Go to Configuration > Meta-Directory > Data Servers > Tuning. Increase the value in the Maximum Operation Result Time field. If the time-out continues, change the values in the retry fields.
DA_E_USER_RETRYLIMIT_EXCEEDED	Error	Indicates either the “Maximum Number of Retries” tuning parameter was not configured, or the server could not be contacted even after the specified number of retries.
MDS_S_ENTRY_ALREADY_EXISTS	Error	Indicates that since the join rules did not turn up with a matching candidate for the source entry, a new entry was to be created, but the DN Mapping rules have come up with a pre-existing candidate of their own, and since there were no join rules then we consider this as a failure to identify a suitable entry to join to.
MDS_S_INSUFFICIENT_CAPABILITI ES	Error	The configured Join Engine capabilities are prohibiting the requested operation from proceeding. Add more Join Engine capabilities for the operation you are attempting to perform.
MDS_S_DN_MAP_FAILED	Error	This error occurs when -No DN Mapping rule set has been specified for the entry -there was an error in obtaining the handle to the Rule set -No applicable rules within the rule set for the entry.
DCNS_E_TOO_LATE	Error	Indicates the following scenarios: -the specified changenumber could not be found in the changelogs -the last sync point was not greater than the first change number or the last sync point was greater than the last changenumber thereby resulting in a mismatch. -Reset from the console the sync points stored in the Sun ONE Meta-Directory configuration. -The changelog trimming has occurred -You may have started the Join Engine without enabling the retro-changelog plug-in. -You enabled the retro-changelog plug-in and restarted the Directory Server, but did not subsequently start the Join Engine. For the above two cases, after enabling the retro-changelog plug-in, restart the Directory Server, stop the Join Engine, restart the Sun ONE Console, then start the Join Engine.

Universal Connector Messages

The table below provides a list of Universal Connector error messages sorted in alphabetically. These error messages also apply for NT Domain, Active Directory and Exchange Connectors. The messages are reported in the logs located here:

NETSITE_ROOT/utc-ViewName/logs

NETSITE_ROOT/adc-ViewName/logs

NETSITE_ROOT/exc-ViewName/logs

NETSITE_ROOT/ntdc-ViewName/logs

Table C-2 Universal Connector Error Messages
Message	Cause and Solution
Delta modified Perl address record unapplicable, id 'utcuser1', DN 'cn=utcuser1,ou=CV2'	The entry 'cn=utcuser1,ou=CV2' was detected as unchanged. No action is required.
Directory delta determination postponed pending active delta processing	For flow control, the current synchronization cycle has been skipped because the delta queue has reached its limit. No action is required.
DraDua PerlDra LDAP List error 32 'No such object'	This is usually not an error. It is a generic message indicating that the LDAP search could not return the specified object. Check the log messages in the same area to determine which entry search is causing the ‘No such object’ error.
Local delta determination postponed pending active delta processing	For flow control, the current synchronization cycle has been skipped because the delta queue has reached its limit. No action is required.
Local delta determination postponed until sync time	The time has not yet arrived for synchronization. No action is required.
Task ‘1’ invalid Perl record index ‘xxx’, cannot process	The index value the Perl script returned for the Perl record is invalid. Check your Perl script for errors.
Unable to initialize host system. Shutting down...	This message usually indicates that the Perl script you specified for the connector is invalid. Check the file path, and also check for syntax errors in your Perl script.

Novell eDirectory and Lotus Notes Connector Messages

The table below provides a list of common errors messages for Lotus Notes and Novell eDirectory connectors. The messages are reported in the logs located here:

NETSITE_ROOT/ndc-ViewName/logs

NETSITE_ROOT/notes-ViewName/logs

Table C-3 Message description and the possible casuse and solution
Message	Cause and Solution
"Error in initialising the connector. Please make sure that the attribute mappings are proper. Exiting."	This error message would get printed if an “Attribute Flow” was created and was not saved properly. Recreate the “Attribute Flow” and save it again.
"Error in initialising the connector. Please make sure that the object class mappings are proper. Exiting."	This error message would get printed if an “Object Class Flow” was created and was not saved properly. Recreate the “Object Class Flow” and save it again.
"Error in initializing the connector."	This error message would get printed if the connector instance's initialization fails due to one of the following root causes - The configuration for “Attribute Flow” and “Object Class Flow” are not defined properly. Define proper rules at the Novell/Notes Directory connector-type level and apply them to the Novell/Notes Directory connector instance you are running. - Failure to connect to external data source (Novell/Notes Directory Server), intermediate changelog database (MySQL database server) or Sun ONE Directory Server. Verify the bind username and password entered for Sun ONE Directory server and external database. Start the Sun ONE Directory server, Novell/Notes Directory server and MySQL server, if they are not running already. - Version of Sun ONE Directory Server used is < V 5.0. - Sun ONE Directory Server's Retro-Changelog plug-in is not enabled. The connector needs it for change-detection in the Directory to External synchronization cycle. Enable it via the Sun ONE Directory Server console.
“Error in initialising the connector. Please make sure that the synchronization directions are set."	This error message would get printed if the value for “TaskMode” is not valid. Set a valid value for “TaskMode” for the connector instance, from the “General” tab in the Meta-Directory Console.
"Error in initializing the connector. Unable to load the main connector class."	This error message would get printed if a custom connector is developed using the new connector framework and the main connector class (that must implement the “IConnector” interface) is not present in the CLASSPATH. Ensure that the class file for the custom ConnectorBase is present in the CLASSPATH by updating the “jconnect.jar” JAR file present under NetsiteRoot/bin/ndc50/bin.
"Error in initializing the connector. Unable to load the boot configuration file."	This error message gets printed when the boot-configuration-file - “start.conf” is not created on start-up, for the connector instance. Ensure that the “start.conf” file gets created successfully by the administration CGI script - “start.pl”. This file gets deleted by the connector once it starts-up successfully.
"Fatal error in initializing the connector. Engine is stopping..."	This error message gets printed when any of the above mentioned error cases prevent the connector from starting up successfully. The connector prints this message before stopping/shutting-down.
"Error in performing change-detection."	This error message would get printed if an error occurs while detecting the changes in External to Directory OR Directory to External synchronization cycle. Exact cause for the error will be present in the log file if the log-level is set to “Debug”.
"Network Error while communicating with Sun ONE Directory Server."	This error message would get printed if the Sun ONE Directory Server hosting the Connector View is not running. Start the Sun ONE Directory Server server if it is not running already.
"Error in updating the intermediate changelog database while handling a normal connector shutdown."	This error message would get printed if MySQL server is not running when the connector is shutdown. Start the MySQL server if it is not running already.
"Error in updating the intermediate changelog database while handling the previous abnormal connector shutdown."	This error message would get printed if MySQL server is not running when the connector starts up again after a previous abnormal shutdown. Start the MySQL server if the server is not running already.
“Error in updating the intermediate changelog database for the asynchronous add delta."	This error message would get printed if MySQL server is not running. Start the MySQL server if it is not running already.
"Error while updating the connector configuration in the global configuration directory."	This error message would get printed if the configuration Directory Server instance is not running. Start the Sun ONE Directory server instance that stores the connector configuration.
"Error in connecting to the global configuration directory."	This error message would also get printed if the configuration Directory Server instance is not running. Start the Sun ONE Directory server instance that stores the connector configuration.
"Error in the creation of deltalist from the ChangelogTable."	This error message would get printed if the connector cannot get the required data from the ChangelogTable in the MySQL database server. Check if the privileges on this table for the changelog user were changed after the connector instance creation. Start the mysql server if it is not running already.
"Error in creating delta list out of intermediate changelog database."	This error message would get printed if the connector cannot get the required data from the ChangelogTable in the MySQL database server. Check if the privileges on this table for the changelog user were changed after the connector instance creation. Start the mysql server if it is not running already.
"Error in creating delta list out of intermediate changelog database."	This error message would get printed if the connector cannot get the required data from the ChangelogTable in the MySQL database server. Check if the privileges on this table for the changelog user were changed after the connector instance creation. Start the mysql server if it is not running already.
"Exceeded log limit. Please check up your settings for RollOverDays and MaxLogFileSize."	This error message would get printed if the “LogRetentionDays” setting does not allow deletion of a log file and maximum disk space allocated for logging (via “LogTotalMaxKBytes”) is over. Remove old log files OR increase the disk space allocated for log OR Change the “LogRetentionDays” setting so that old log files are automatically removed.
"Failed to retrieve entries from the root suffix <root-suffix-value> in the LDAP data source."	This error message would get printed if either the external (Novell/Notes Directory Server) or directory (Sun ONE Directory Server) are not reachable. Ensure that the LDAP server is running.
"Failed to load the database driver for intermediate data source."	This error message would get printed if the database driver class file is not found.
"Attempts to connect to the intermediate database failed."	This error message would get printed if the MySQL database server is not reachable or running. Start the MySQL database server if it is not running already.
"Failed to cleanup ChangelogTable."	This error message would get printed if the connector cannot access the required data from the ChangelogTable in the MySQL database server. Check if the privileges on this table for the changelog user were changed after the connector instance creation. Start the MySQL server if it is not running already.
"Failed to create ChangelogTable in the intermediate changelog database."	This error message would get printed if there are insufficient privileges assigned to the database-administrator-user attempting to create this table in the intermediate changelog database. Check the privileges of the database-administrator-user attempting to create this table. Start the MySQL server if it is not running already.
"Failed to create ImageTable in the intermediate changelog database."	This error message would get printed if there are insufficient privileges assigned to the database-administrator-user attempting to create this table in the intermediate changelog database. Check the privileges of the database-administrator-user attempting to create this table. Start the MySQL server if it is not running already.
"Failed to drop ImageTable from the intermediate changelog database."	This error message would get printed if there are insufficient privileges assigned to the database-administrator-user attempting to drop this table from the intermediate changelog database. Check the privileges of the database-administrator-user attempting to drop this table. Start the MySQL server if it is not running already.
"Failed to drop ChangelogTable from the intermediate changelog database."	This error message would get printed if there are insufficient privileges assigned to the database-administrator-user attempting to drop this table from the intermediate changelog database. Check the privileges of the database-administrator-user attempting to drop this table. Start the MySQL server if it is not running already.
"Failed to cleanup ImageTable."	This error message would get printed if the connector cannot access the required data from the ImageTable in the MySQL database server. Check if the privileges on this table for the changelog user were changed after the connector instance creation. Start the MySQL server if it is not running already.
"Failed to connect to the LDAP data source with Hostname :<hostNameValue> and Port : <portNumberValue>."	This error message would get printed if there is a failure in connecting to external data source (Novell Directory Server/ Lotus Notes server) or Sun ONE Directory Server. Verify the bind username and password entered for Sun ONE Directory server and external data source. Start the Sun ONE Directory server or Novell/Notes Directory server, if they are not running already.
"Failed to add the entry to the LDAP data source."	This error message would get printed if there is a failure in creation of a new entry in external data source (Novell/Notes Directory Server) or Sun ONE Directory Server. This could be because of object class violation. Ensure that all the required/mandatory attributes are mapped via the “Attribute Flow” configuration rule. Check if the user (“ExternalLoginDN” or “DirectoryLoginDN”) has appropriate LDAP write access.
"Failed to get the command-implementation mapping from the configuration."	This error message would get printed if any custom management commands are implemented but are not specified properly in configuration.
"Failed to get the command-implementation mapping from the configuration for command - <commandName>."	This error message would get printed if the class file for the custom management command implementation is not specified properly in the configuration.
"Unable to load class <className>."	This error message would get printed if the class file for the custom management command implementation cannot be loaded. Make sure the class file is present in the classpath by updating the “jconnect.jar” JAR file present under “NetsiteRoot/bin/ndc50/bin”.
"Unable to initiate refresh operation."	This error message would get printed if either of the LDAP servers (Novell/Notes or Sun ONE Directory Server) and/or MySQL server are not running when a REFRESH operation is performed. Start the relevant server if it is not running already.

Previous Contents Index Next