2.3 85xx Errors
8502 Cannot initialize protocol
Source:
GroupWise engine; general communication.
Explanation:
Cannot open protocol.
8503 Cannot connect to specified IP address
Source:
GroupWise engine; general communication.
Explanation:
Cannot open connection to specified address.
8509 Cannot access TCP/IP services
Source:
GroupWise engine; general communication.
Explanation:
TCP/IP bind failed.
Possible Cause:
TCP/IP is not loaded on the server or is not loaded correctly. The TCP port is already in use by another process.
Action:
Configure TCP/IP on the server correctly. If this error occurs on a NetWare server, make sure you have the latest version of the TCPIP NLM. For technical services and file updates, see Novell Support.
Action:
Reboot the server.
850F Connection no longer valid
Source:
GroupWise engine; general communication.
Explanation:
Connection was broken while in use.
Possible Cause:
A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active.
Action:
Exit and restart GroupWise when the machine is back up.
Source:
GroupWise engine; general communication.
Explanation:
Port in use.
Possible Cause:
The POA defaults to TCP/IP communication, but the necessary TCP/IP information is not configured in ConsoleOne. The default TCP port used by the POA (1667) is in use by another program.
Possible Cause:
You are trying to run two POAs on the same server in client/server mode and you have not given them unique TCP port numbers.
Possible Cause:
You are trying to run two POAs on the same server in client/server mode and you haven’t created a second POA object in ConsoleOne.
8562 Client/server request packet contained invalid identifier
Source:
GroupWise engine; general communication.
Explanation:
Client/server request packet contained an invalid identifier.
Possible Cause:
Someone is trying to forge packets to break into the system.
Action:
Check your system security.
Possible Cause:
The server was shut down and brought back up while GroupWise clients were attached.
Action:
Exit and restart the GroupWise clients.
Possible Cause:
A TCP/IP packet was damaged in transit.
Action:
None.
8563 Client/server request packet contained invalid identifier
Source:
GroupWise engine; general communication.
8567 Data not in BCEF format
Source:
GroupWise engine; general communication.
Explanation:
A packet of information received by an agent was not in the expected format.
Possible Cause:
The packet was damaged somewhere between the source and the destination of the data.
Action:
Use packet trace software to identify the source of the problem. It could be something like a bad network card or a problem with dial-up software.
8568 HTTP port already in use
Source:
GroupWise engine; general communication.
Explanation:
The HTTP port used by the POA for its Web console is already in use by another program on the server.
Possible Cause:
You are trying to run two POAs on the same server and you have not given them unique HTTP port numbers.
8569 SSL login required for this post office
Source:
GroupWise engine; general communication.
Explanation:
Starting with GroupWise 6.5, the POA can be configured to require SSL connections with clients.
Possible Cause:
Users of clients earlier than GroupWise 6.5 are trying to log in to the post office.
856A IMAP port already in use
Source:
GroupWise engine; general communication.
Explanation:
The IMAP port used by the POA to communicate with IMAP e-mail clients is already in use by another program on the server.
Possible Cause:
You are trying to run two POAs on the same server and you have not given them unique IMAP port numbers.
856B SOAP port already in use
Source:
GroupWise engine; general communication.
Explanation:
The SOAP port used by the POA to communicate with SOAP clients is already in use by another program on the server.
Possible Cause:
You are trying to run two POAs on the same server and you have not given them unique SOAP port numbers.
856D LDAP port already in use
Source:
GroupWise engine; general communication.
Explanation:
The LDAP port used by the POA is already in use by another program on the server.
Possible Cause:
You are trying to run two POAs on the same server and you have not given them unique LDAP port numbers.
856E POP port already in use
Source:
GroupWise engine; general communication.
Explanation:
The POP port used by the Internet Agent is already in use by another program on the server.
Possible Cause:
You are trying to run two Internet Agents on the same server and you have not given them unique POP port numbers.
856F Calendar Publishing port already in use
Source:
GroupWise engine; general communication.
Explanation:
The Calendar Publishing port used by the POA is already in use by another program on the server.
Possible Cause:
You are trying to run two POAs on the same server and you have not given them unique Calendar Publishing port numbers.