8.9 EA0x Errors
NOTE:This guide does not include a comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved.
EA02 The item is not found in the container portion of the uid
Source:
GroupWise engine; SOAP protocol.
Explanation:
Your application looked for a GroupWise item in a particular container (a folder or an address book) in a GroupWise mailbox and did not find the item.
Possible Cause:
Your application calls a method that requires a container as an argument and the item is not in the specified container.
Possible Cause:
Your application passes a uid that does not have the container appended to the end. Therefore, the item cannot be found.
Action:
Call getItemsRequest and compare the uid from that call to the uid that you used when the error was generated.
For more information, see:
EA03 Handling of SOAP protocol is not enabled
Source:
GroupWise engine; SOAP protocol.
Explanation:
A SOAP client has attempted to contact the POA and the POA cannot respond successfully.
Possible Cause:
The POA is not yet configured for SOAP.
EA04 The response is too large
Source:
GroupWise engine; SOAP protocol.
Explanation:
The POA received a response from your application that is too large for it to process.
Possible Cause:
Your application responded to the POA with more than 1 MB of data.
Action:
Refine the SOAP request so that the response is smaller.
Action:
Use the --soapsizelimit switch on the POA to increase the maximum size of the data that the POA accepts.
Source:
GroupWise engine; SOAP protocol.
Explanation:
Your application cannot read the current cursor value. Cursors break lists of data into chunks. Your application cannot determine where the boundary of the data chunk is located.
Possible Cause:
The cursor has already been freed using the destroyCursorRequest method.
Action:
Create a new cursor. A cursor cannot be used again after it has been freed.
Possible Cause:
The current value of the cursor is not valid.
Action:
Create a cursor before attempting to position or read from it.
For more information, see:
EA06 Invalid session string
Source:
GroupWise engine; SOAP protocol.
Explanation:
Your application cannot access the current session with the POA.
Possible Cause:
The SOAP client user has logged out of his or her GroupWise mailbox.
Possible Cause:
The POA has timed out the session after 30 minutes.
Action:
Your application needs to log in again for that user.
For more information, see:
EA07 Container string is missing
Source:
GroupWise engine; SOAP protocol.
Explanation:
The container string in a POA request is not found in your application.
Possible Cause:
Your application calls a method that requires a container as an argument and you have not provided a container.
Possible Cause:
Your application passes in a uid that does not have the container appended to the end.
Action:
Call getItemsRequest and compare the uid from that call to the uid that you used when the error was generated.
For more information, see:
EA08 Display name is missing
Source:
GroupWise engine; SOAP protocol.
Explanation:
A display name is the human-readable name of a GroupWise object. It is required when creating such objects as a contact or a resource.
Possible Cause:
Your application tries to create a GroupWise item that should include a display name without providing the display name.
Action:
Make sure you provide the display name when creating the object.
For more information, see:
EA09 User structure still busy
Source:
GroupWise engine; SOAP protocol.
Explanation:
A user structure contains the data about a user session. It cannot be accessed when it is busy.
Possible Cause:
Your application is trying to log out of the POA when a lengthy activity such as a Busy Search is in progress.
Action:
Program your application to wait when this error is encountered. The problem typically resolves itself in a short period of time.
EA0A Item already accepted
Source:
GroupWise engine; SOAP protocol.
Explanation:
The GroupWise item being processed has already been accepted and cannot be accepted again.
Possible Cause:
Your application is trying to mark as Accepted a GroupWise item that has already been accepted by the SOAP client user.
Action:
Accepted items are marked as accepted. Check the status of an item before trying to accept it.
For more information, see:
EA0B Item not acceptable/declinable
Source:
GroupWise engine; SOAP protocol.
Explanation:
The GroupWise item being processed is not eligible for being accepted or declined.
Possible Cause:
Your application is trying to accept a GroupWise item that cannot be accepted or declined because it is not the right type of item.
Action:
Check the following item status information before trying to accept an item:
-
The item is a calendar item (appointment, note, or task).
-
The item is a received item in the Mailbox folder.
-
The item is not archived.
-
The items is not in the Work in Progress folder.
-
The item is not in the Trash folder.
-
Your application has sufficient access rights to the item.
For more information, see:
EA0C The method called is not supported
Source:
GroupWise engine; SOAP protocol.
Explanation:
The action that your application is trying to perform is no longer accepted by the GroupWise SOAP protocol used by the POA.
Possible Cause:
Your application contains a method that is out of date.
Action:
Use a supported method.
For a list of currently supported methods, see:
Source:
GroupWise engine; SOAP protocol.
Explanation:
A key is a unique identifier that is used to create or modify an event configuration. Events notify your application when an event has occurred in a user’s mailbox, for example, when an item is deleted.
Possible Cause:
Your application did not provide a usable key.
Possible Cause:
The key string is empty.
Action:
Check the configureEventsRequest to see if it is passing a valid key element.
For more information, see:
Source:
GroupWise engine; SOAP protocol.
Explanation:
A required cursor string is absent.
Possible Cause:
Your application calls a method that requires a cursor, but no cursor was provided.
Action:
Call createCursorRequest to get a valid cursor before using positionCursorRequest or readCursorRequest.
For more information, see: