EA10 Missing session string
Source:
GroupWise engine; SOAP protocol.
Explanation:
A session string identifies a user and his or her GroupWise data. This information is missing.
Possible Cause:
The POA has timed out the session after 30 minutes.
Action:
Your application needs to log in again for that user.
Possible Cause:
Your application does not use a loginResponse to obtain a session string before calling a method that requires a session string.
Action:
Make sure you use the login method to obtain a session string.
For more information, see:
EA11 Maximum event read threads
Source:
GroupWise engine; SOAP protocol.
Explanation:
Your application has started as many event read threads as the POA is configured to service. The POA cannot create additional event read threads.
Possible Cause:
Your application is issuing more getEventsRequest methods than the POA can respond to.
Action:
Reduce the number of getEventsRequest methods that your application issues at one time.
For more information, see:
EA12 Too much data requested for an attachment
Source:
GroupWise engine; SOAP protocol.
Explanation:
The attachment cannot be returned.
Possible Cause:
The attachment is too large to get in one request.
Action:
Request the attachment data in multiple chunks.
For more information, see:
EA13 Redirect user to different post office
Source:
GroupWise engine; SOAP protocol.
Explanation:
The specified user does not exist in the specified post office and needs to be redirected in order to log in to GroupWise successfully.
Possible Cause:
The user resides in a different post office than your application specified in the login.
Action:
Redirect the user to the correct post office.
For more information, see:
EA15 The method called is not supported on this container
Source:
GroupWise engine; SOAP protocol.
Explanation:
The calling method is valid, but the container type on which it is being called is not appropriate.
Possible Cause:
Your application is calling a method that is not supported on the container type for which it was called. For example:
-
The getQuickMessages method cannot be used on the Contacts folder, the Trash folder, or a query folder.
-
The createCursor method cannot be used on the Contacts folder.
Action:
Use a method that is valid for the container type.
For more information, see:
EA16 The specified contentType is not supported with this call
Source:
GroupWise engine; SOAP protocol.
Explanation:
The call that generated this error supports only the text/plain content type. HTML is not yet supported for this call.
Possible Cause:
Your application is trying to create a GroupWise item with HTML content type when only the text/plain content type is currently supported.
Action:
Use the text/plain content type.
EA17 The specified date/time range is invalid
Source:
GroupWise engine; SOAP protocol.
Explanation:
The specified date/time range is not usable.
Possible Cause:
Your application fails to specify a start date on a recurring item.
Possible Cause:
Your application specifies an end date that is earlier than the start date.
Action:
Specify a valid date/type range.
For more information, see:
EA18 Searching over the entire mailbox requires a filter
Source:
GroupWise engine; SOAP protocol.
Explanation:
Because a GroupWise mailbox can be very large, the process of searching the entire mailbox should be limited, either by a filter or by restricting the search to a particular container in the mailbox.
Possible Cause:
Your application is attempting to search an entire mailbox without limiting the search using either a filter or a container.
Action:
Supply a filter.
For more information, see:
Action:
Supply a container.