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.
|