Novell Documentation: Identity Manager Drivers - Viewing Driver Errors in the DS Trace Screen

4.2 Viewing Driver Errors in the DS Trace Screen

For each event or operation received from the engine, the driver returns an XML document containing a status report in DSTrace. If the operation or event is not successful, the status report also contains a text message describing the error condition.

Table 4-1 Status Levels

Status Level	Description
Success	Operation or event was successful.
Warning	Operation or event was partially successful.
Error	Operation or event failed.
Fatal	A fatal error occurred. The driver shuts down.
Retry	Application server was unavailable. Send this event or operation later.

4.2.1 Understanding Error Text Descriptions

The table below contains errors from the driver that display in the Trace screen. The Error Reason Text column in the table contains the error condition text returned to the Metadirectory engine in the Trace screen. The Level column in the table specifies the status level. The Description column describes the situations that might cause the condition and possible actions you can take to fix the problem. The status level and error condition text are recorded in the Driver log.

Table 4-2 Error Descriptions

Error Reason Text	Level	Description	Recommended Action
Driver initialization error	Fatal	On driver initialization, no parameters were provided.
Failure initializing GroupWise	Fatal	During initialization the driver cannot communicate with GroupWise. <text> can be one of the following: Error getting driver DN from src-dn attribute The src-dn attribute value in <init-params> did not have a value or the value was not recognized by the driver. Invalid GroupWise Primary Domain Path initialization parameter An invalid format was used to specify the domain path. Invalid Admin User ID. The value of this parameter cannot be “mapi”, which is a reserved ID. Missing domain path initialization parameter. The GroupWise primary domain path has not been specified in the Driver Parameters page in iManager. Missing Admin User ID initialization parameter The Admin User ID has not been specified in the Driver Parameters page in iManager. Invalid character in Admin User ID. An invalid character is used in the Admin User ID in the Driver Parameters page in iManager. The User ID contains 1 to 256 characters, and cannot contain the following characters: ()@.:,{}*". The UserID must be unique within its namespace (UserID shares the same namespace as nicknames, resources, and distribution lists.) Do not use “mapi” (reserved IDs) for this value. Various text messages. JNDI Naming exception, class not found exception, unsatisfied link error (can’t load .dll), unable to determine initial context, or domain path not correct. Unable to make connection with remote server Missing or invalid authentication information. Incorrect setup of authentication accounts.
GroupWise error	Error	Invalid post office specified. Either the post office does not exist or the driver does not have eDirectory™ access rights (read/write). The parent of an external post office must be an external domain. Invalid post office or domain specified. Query Scope Entry: No base object identified. Requested Query operation is not supported. Unsupported Class. The driver received an event for an object other than a Novell® eDirectory User object. No username specified. The CN attribute was not specified. java.lang.NullPointerException. The XML document is not correctly formed. It might be syntactically correct, but it doesn’t make sense.
Unsupported operation	Error	The driver does not understand the XML event.
Event failed. The Identity Manager association for this driver has been removed.	Error	The driver received an event for an object without an expected GroupWise ID. This is probably caused when the GroupWise account is deleted through the GroupWise snap-ins. The driver has removed the association to the driver in eDirectory for this object.
Move pending	Retry	When GroupWise is in the process of moving an account from one post office to another, other operations cannot be performed on the account.
Prior modification pending	Retry	Attempted to move a user to another post office, but previous modifications have not been processed.
Name already exists in GroupWise	Error	This can occur on an account create, rename, or post office move event.
Event is for a different system.	Warning (for event)	The received event is not for this GroupWise system and is ignored by the driver. There can be multiple GroupWise systems in a single eDirectory tree. An instance of the driver supports only a single GroupWise system.	Add a rule to allow only items for this GroupWise system.
Event is for a different system.	Error (for query)	The received query is not for this GroupWise system and is ignored by the driver. There can be multiple GroupWise systems in a single eDirectory tree. An instance of the driver supports only a single GroupWise system.	Add a rule to allow only items for this GroupWise system
Error publishing to eDirectory.	Error	GroupWise tried to update attributes in eDirectory for an object. The error message is from Identity Manager or eDirectory. You might have a GroupWise object without a corresponding object in eDirectory. If the corresponding object does exist in eDirectory, the attribute values in eDirectory might not be correct.
No commands to execute	Error	An input document without any commands was received. This is a probably a style sheet error, where the style sheet didn’t pass any commands through.
Query posted to publisher failed	Error	This error is generated for the following conditions: The driver received a query for an object other than user. The object to be queried does not exist or cannot be read.
Waiting for publisher to start	Retry	The Subscriber channel does not process events until the Publisher channel is initialized and running. The Subscriber channel can initialize before the Publisher channel. Normally both channels initialize within a short time.
Invalid reference to GroupWise	Warning	This error occurred because there is an invalid reference to GroupWise. This is OK if it occurred on a Modify event that is generated by eDirectory in response to a Move event. This could also occur if required data is missing, incorrect, invalid, or refers to the wrong type of object. In these cases, the error message includes specific information.
Password synchronization was not processed	Success	The post office security is set to LDAP Authentication. You cannot set the GroupWise password, which would be ignored.
Rename or Move	Warning	Rename or Move error: The operation might not be supported with this GroupWise domain version. An error probably occurred processing a move or rename. Part of the event might have been processed. Most likely, this operation is not supported in the GroupWise domain version. Please upgrade the GroupWIse system.
eDirectory Error	Retry or Error	This attempt to read from or write to eDirectory failed. See the error message and prior result from eDirectory for more details.