7.2 Error Messages
For each event or operation received from the engine, the driver returns an XML document containing a status report in DSTrace. See Section 7.3, Troubleshooting Driver Processes for instructions on how to capture this information. If the operation or event is not successful, the status report also contains a text message describing the error condition.
Table 7-1 Status Levels
|
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. |
Driver initialization error
Source:
The status log or DSTrace screen.
Explanation:
On driver initialization, no parameters were provided.
Level:
Fatal
Failure initializing GroupWise
Source:
The status log or DSTrace screen.
Explanation:
During initialization, the driver cannot communicate with GroupWise.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Error getting driver DN from src-dn attribute
Source:
The status log or DSTrace screen.
Explanation:
The src-dn attribute value in <init-params> did not have a value or the value was not recognized by the driver.
Level:
Fatal
Invalid GroupWise Primary Domain Path initialization parameter
Source:
The status log or DSTrace screen.
Explanation:
An invalid format was used to specify the domain path.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Source:
The status log or DSTrace screen.
Explanation:
The value of this parameter cannot be “mapi,” which is a reserved ID.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Missing domain path initialization parameter
Source:
The status log or DSTrace screen.
Explanation:
The GroupWise primary domain path has not been specified on the Driver Parameters page in iManager.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Missing Admin User ID initialization parameter
Source:
The status log or DSTrace screen.
Explanation:
The Admin User ID has not been specified on the Driver Parameters page in iManager.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Invalid character in Admin User ID
Source:
The status log or DSTrace screen.
Explanation:
An invalid character is used in the Admin User ID in the Driver Parameters page in iManager.
Possible Cause:
The User ID contains 1 to 256 characters, and cannot contain the ()@.:,{}*" 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 ID) for this value.
Level:
Fatal
Source:
The status log or DSTrace screen.
Explanation:
A name exception occurred.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Class not found exception
Source:
The status log or DSTrace screen.
Explanation:
The driver cannot find the requested class.
Possible Cause:
The eDirectory schema might not be extended properly.
Level:
Fatal
Unsatisfied link error (can’t load .dll)
Source:
The status log or DSTrace screen.
Explanation:
The driver cannot find the proper files.
Possible Cause:
The driver might not be installed correctly.
Level:
Fatal
Unable to determine initial context
Source:
The status log or DSTrace screen.
Explanation:
The driver cannot determine the initial context.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Source:
The status log or DSTrace screen.
Explanation:
The GroupWise domain path is incorrect.
Possible Cause:
A driver parameter is not configured correctly.
Level:
Fatal
Unable to make connection with remote server
Source:
The status log or DSTrace screen.
Explanation:
The Identity Manager engine cannot connect to the Remote Loader server
Possible Cause:
Missing or invalid authentication information.
Possible Cause:
Incorrect setup of authentication accounts.
Level:
Fatal
Source:
The status log or DSTrace screen.
Explanation:
There are multiple causes for this error.
Possible Cause:
Invalid post office specified. Either the post office does not exist or the driver does not have eDirectory access rights (read/write).
Possible Cause:
The parent of an external post office must be an external domain.
Possible Cause:
Invalid post office or domain specified.
Possible Cause:
Query Scope Entry: No base object identified.
Possible Cause:
Requested Query operation is not supported.
Possible Cause:
Unsupported Class. The driver received an event for an object other than a Novell® eDirectory User object.
Possible Cause:
No username specified. The CN attribute was not specified.
Possible Cause:
java.lang.NullPointerException. The XML document is not correctly formed. It might be syntactically correct, but it doesn’t make sense.
Action:
Specify a valid post office, or verify that the driver has the correct eDirectory access rights.
The driver must have Read/Write access to users, post offices, resources, groups, distribution lists, and Create, Read, and Write rights to the post office container in the Identity Vault. If you are creating external post offices, the driver also needs read/write access to the domain.
The Admin user object is most often used to supply these rights. However, you might want to create a DriversUser (for example) and assign security equivalence to that user. Whatever rights that the driver needs to have on the server, the DriversUser object must have the same security rights.
Level:
Error
Source:
The status log or DSTrace screen.
Explanation:
The driver does not understand the XML event.
Possible Cause:
The XML document is not correctly formed. It might be syntactically correct, but it doesn’t make sense.
Action:
Review and fix the XML document.
Level:
Error
Event failed. The Identity Manager association for this driver has been removed
Source:
The status log or DSTrace screen.
Explanation:
The driver received an event for an object without an expected GroupWise ID.
Possible Cause:
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.
Level:
Error
Source:
The status log or DSTrace screen.
Explanation:
When GroupWise is in the process of moving an account from one post office to another, other operations cannot be performed on the account.
Level:
Retry
Prior modification pending
Source:
The status log or DSTrace screen.
Explanation:
You attempted to move a user to another post office, but previous modifications have not been processed.
Action:
Allow the previous modifications to process before attempting to move the user.
Level:
Retry
Name already exists in GroupWise
Source:
The status log or DSTrace screen.
Explanation:
This can occur on an account create, rename, or post office move event.
Action:
Verify that the account has an unique name.
Level:
Error
Event is for a different system.
Source:
The status log or DSTrace screen.
Explanation:
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.
Level:
Warning (for event)
Error publishing to eDirectory
Source:
The status log or DSTrace screen.
Explanation:
GroupWise tried to update attributes in eDirectory for an object. The error message is from Identity Manager or eDirectory.
Possible Cause:
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.
Level:
Error
Source:
The status log or DSTrace screen.
Explanation:
An input document without any commands was received.
Possible Cause:
This is a probably a style sheet error, where the style sheet didn’t pass any commands through.
Level:
Error
Query posted to publisher failed
Source:
The source of the message.
Explanation:
This error is generated for the following conditions:
Level:
Error
Waiting for publisher to start
Source:
The status log or DSTrace screen.
Explanation:
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.
Level:
Retry
Invalid reference to GroupWise
Source:
The status log or DSTrace screen.
Explanation:
This error occurred because there is an invalid reference to GroupWise. This is not a problem if it occurred on a Modify event that is generated by eDirectory in response to a Move event.
Possible Cause:
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.
Level:
Warning
Password synchronization was not processed
Source:
The status message or DSTrace screen.
Explanation:
The post office security is set to LDAP Authentication. You cannot set the GroupWise password, which would be ignored.
Level:
Success
Source:
The status log or DSTrace screen.
Explanation:
Rename or move error. The operation might not be supported with this GroupWise domain version.
Possible Cause:
An error probably occurred processing a move or rename. Part of the event might not have been processed. Most likely, this operation is not supported in the GroupWise domain version. You should upgrade the GroupWise system.
Level:
Warning
Source:
The status log or DSTrace screen.
Explanation:
This attempt to read from or write to eDirectory failed. See the error message and prior results from eDirectory for more details.
Level:
Retry or Error