iPlanet Meta-Directory Configuration and Administration Guide: Appendix D Error Messages

Previous Contents Index Next

iPlanet Meta-Directory Configuration and Administration Guide

Appendix D     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

Join Engine Messages

Table D-1 provides a list of join engine error messages arranged in alphabetical order. The messages are generated to logs found at the following location:
NETSITE_ROOT/join-engine/logs

Table D-1    Join Engine Error Messages

Message

Cause and Solution

DA_E_NO_SUCH_OBJECT

The object or entry was not found in the Directory Server.

DA_E_UNWILLING_TO
_PERFORM

One reason this message might appear is that an LDAP version 3 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. Other possible reasons are:

The ldbm database plug-in did not load properly.

An unknown attribute(s) was added to the configuration.

The user's password expired.

An add, rename, or delete was applied against a DSE.

A 1.0-syntax ACI was added.

A modify was applied to a read-only DSE attribute.

You attempted to replace an objectclass or attribute definition in the schema DSE.

An objectclass definition was deleted, which is a superior definition for another objectclass.

A read-only objectclass or attribute was deleted.

To correct the problem, see Directory Server Performance Tuning for Meta-Directory in the iPlanet Meta-Directory Deployment Guide.

DA_E_USER_TIMELIMIT
_EXCEEDED

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_S_NO_RESULTS
_RETURNED

A search was conducted and no results were returned for the search.

E_DCNS_TOO_LATE

Any message that appears with DCNS in it, including this one, is associated with the Directory Server changelog.
For this message, the following events might have occurred:

You may have started the join engine without enabling the changelog.

You enabled the changelog and restarted the Directory Server, but did not subsequently start the join engine.

The changelog wrapped around so that the sync number stored in the iMDS configuration is greater than the last change number in the changelog, thereby resulting in a mismatch.

For the first two cases, after enabling the changelog, restart the Directory Server, stop the join engine, restart the iPlanet Console, then start the join engine. For the last case, reset from the console the sync points stored in the iMDS configuration.

MDS_CONTROLLER
_UNAVAILABLE

Either you did not configure the changelog, or you did not restart the Directory Server after configuring Meta-Directory.

MDS_S_ENTRY_ALREADY
_EXISTS

The entry you are attempting to add already exists in the target view. You may need a join rule to join or link the entry.

MDS_S_INSUFFICIENT
_PRIVILEGES

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.

TIMEOUT

This message usually appears with the DA_E_USER_TIMELIMIT_EXCEEDED message, and indicates that an operation, such as a refresh or search, has timed out. Increase the join engine time-out limit.

Universal Connector Messages

provides a list of Universal Connector error messages arranged in alphabetical order. The messages are generated to logs found at the following location:
NETSITE_ROOT/utc-ViewName/logs

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

Message	Cause and Solution
DA_E_NO_SUCH_OBJECT	The object or entry was not found in the Directory Server.
DA_E_UNWILLING_TO _PERFORM	One reason this message might appear is that an LDAP version 3 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. Other possible reasons are: The ldbm database plug-in did not load properly. An unknown attribute(s) was added to the configuration. The user's password expired. An add, rename, or delete was applied against a DSE. A 1.0-syntax ACI was added. A modify was applied to a read-only DSE attribute. You attempted to replace an objectclass or attribute definition in the schema DSE. An objectclass definition was deleted, which is a superior definition for another objectclass. A read-only objectclass or attribute was deleted. To correct the problem, see Directory Server Performance Tuning for Meta-Directory in the iPlanet Meta-Directory Deployment Guide.
DA_E_USER_TIMELIMIT _EXCEEDED	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_S_NO_RESULTS _RETURNED	A search was conducted and no results were returned for the search.
E_DCNS_TOO_LATE	Any message that appears with DCNS in it, including this one, is associated with the Directory Server changelog. For this message, the following events might have occurred: You may have started the join engine without enabling the changelog. You enabled the changelog and restarted the Directory Server, but did not subsequently start the join engine. The changelog wrapped around so that the sync number stored in the iMDS configuration is greater than the last change number in the changelog, thereby resulting in a mismatch. For the first two cases, after enabling the changelog, restart the Directory Server, stop the join engine, restart the iPlanet Console, then start the join engine. For the last case, reset from the console the sync points stored in the iMDS configuration.
MDS_CONTROLLER _UNAVAILABLE	Either you did not configure the changelog, or you did not restart the Directory Server after configuring Meta-Directory.
MDS_S_ENTRY_ALREADY _EXISTS	The entry you are attempting to add already exists in the target view. You may need a join rule to join or link the entry.
MDS_S_INSUFFICIENT _PRIVILEGES	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.
TIMEOUT	This message usually appears with the DA_E_USER_TIMELIMIT_EXCEEDED message, and indicates that an operation, such as a refresh or search, has timed out. Increase the join engine time-out limit.

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.

Previous Contents Index Next
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

Last Updated April 08, 2002