
The table below contains error messages and appropriate action.
|
Error number |
Solution |
|
GW-LOT-001 |
An exception occurred when reading the response sent by Domino. The response from the Domino server was not complete. This can occur for the following two reasons: 1. The Domino server, or the HTTP service on the Domino server, was restarted. 2. The response from the Domino server could not be read due to network problems. Launch http://<hostname>:<port>/<servletDirectory>/CalendarServlet in the browser to check the connectivity. |
|
GW-LOT-002 |
No protocol was specified when you created the Lotus transport. Check the specification and specify a protocol that the Domino server supports. Only HTTP and HTTPS protocols are supported. For more information, see Creating a Lotus Transport . |
|
GW-LOT-003 |
The Domino server is down or cannot be reached. Launch http://<hostname>:<port>/<servletDirectory>/CalendarServlet in the browser to check the connectivity. |
|
GW-LOT-004 |
The protocol specified when you created the Lotus transport is incorrect. Check the specification and specify a protocol that the Domino server supports. Only HTTP and HTTPS protocols are supported. For more information, see Creating a Lotus Transport . |
|
GW-LOT-005 |
Some of the configuration parameters have not been defined for this transport. Check the transport configuration you created and update the parameters accordingly. |
|
GW-LOT-006 |
The port for connecting to the Domino server was not specified correctly when you created the Lotus transport. Check the port on which the virtual directory exists on the Domino server, and update the transport accordingly |
|
GW-LOT-007 |
The port for connecting to the Domino server was not specified when you created the Lotus transport. Check the port on which the virtual directory exists on the Domino server, and update the transport accordingly. |
|
GW-LOT-008 |
The URL constructed from the information specified when you created a Lotus transport in the Lotus transport configuration resulted in an error. Launch http://<hostname>:<port>/<servletDirectory>/CalendarServlet in the browser to check the settings and update the configuration of the Lotus transport accordingly. |
|
GW-LOT-009 |
The Domino server specified when you created a Lotus transport in the Lotus transport configuration is either incorrect or cannot be reached. Launch http://<hostname>:<port>/<servletDirectory>/CalendarServlet in the browser to check the connectivity, and update the configuration of the Lotus transport accordingly. |
|
GW-LOT-010 |
The user credentials passed for authentication are incorrect or were not specified. |
|
GW-LOT-011 |
No default Domino server has been configured for this transport. Launch http://<hostname>:<port>/<servletDirectory>/CalendarServlet in the browser to check the connectivity, and update the configuration of the Lotus transport accordingly. |
|
GW-LOT-012 |
The Domino server name has not been configured for this transport. Launch http://<hostname>:<port>/<servletDirectory>/CalendarServlet in the browser to check the connectivity, and update the configuration of the Lotus transport accordingly. |
|
GW-LOT-013 |
The Groupware manager has not been initialized for Lotus. This transport has failed. Check for errors logged when the portal was started up. |
|
GW-LOT-014 |
The XML generated by the Lotus Servlet component is not well formed. |
|
GW-LOT-015 |
The virtual directory was not configured correctly when you created the Lotus transport. Launch http://<hostname>:<port>/<servletDirectory>/CalendarServlet in the browser to check the connectivity. |
|
GW-LOT-018 |
The user attempted to modify an instance of a recurring appointment. This feature is not supported. Use native clients to do this instead. |
|
GW-LOT-019 |
This error can occur for the following two reasons: 1. The e-mail address specified in the LDAP mapped for the portal is invalid or was not recognized by the Domino server. 2. The e-mail address for one or more users returned by the Domino servlet has an invalid form. Check for errors logged. |
|
GW-LOT-020 |
The configuration for this transport was not initialized. Check for any error messages logged during the start-up and take any necessary action. |
|
GW-LOT-021 |
The user attempted to create a multi-day appointment. This feature is not supported by Domino. |
|
GW-LOT-022 |
The user attempted to create an all-day appointment. This feature is not supported by Domino. |
|
GW-LOT-023 |
The user attempted to change an all-day event or an appointment to a meeting request (or vice versa). This feature is not supported by Domino. |
|
GW-LOT-024 |
The e-mail server in the user credentials specified in user mapping is not correct for the user currently logged on. Change the e-mail server to one of the servers configured in the Lotus transport. |
|
GW-LOT-025 |
The single sign-on connection to the Lotus server failed. Check the following: 1. Is this portal user mapped to one of the Lotus users on the Domino server? 2. Are there multiple Lotus users for the same portal user? |
|
GW-LOT-026 |
The Domino servlet threw an exception when trying to process the user request. Check for errors logged. |
|
GW-LOT-027 |
The Domino servlet threw an exception when trying to read the data from Domino. Check for errors logged. |
|
GW-LOT-028 |
The user credentials specified in user mapping are not correct for the user currently logged on. Check and update the user credentials. The following are valid formats for usernames: 1. User name 1. Short name/user ID 2. Internet address The user name, short name/user ID and internet address can all be found in the record of the user in question. For more information, see Mapping Your User in the Groupware user guide. |
|
GW-LOT-029 |
The user attempted to create an all-day event with recipients. A meeting request cannot last all day. This feature is not supported by Domino |