2.3 85xx Errors

8502 Cannot initialize protocol

Source: GroupWise engine; general communication.
Explanation: Cannot open protocol.
Action: See 8901 Cannot use TCP/IP services.

8503 Cannot connect to specified IP address

Source: GroupWise engine; general communication.
Explanation: Cannot open connection to specified address.
Action: See 8908 Cannot connect 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.

8555 Port in use

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.
Action: To enable TCP/IP communication, configure the POA for ConsoleOne. See Using Client/Server Access to the Post Office in Configuring the POA in the GroupWise 7 Administration Guide .
Action: To disable TCP/IP communication, use the /notcpip switch when starting the POA. See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide .
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.
Action: Check the TCP port for each POA object. See Using Client/Server Access to the Post Office in Configuring the POA in the GroupWise 7 Administration Guide . Change the TCP port for one of the POAs.
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.
Action: In ConsoleOne, create a second POA object in the post office. Make sure you give it a unique TCP port number, different from what the first POA is using. Use the /name switch when starting each POA. You might want to create a separate startup file for each POA. See Creating a POA Object in eDirectory in Post Office Agent in the GroupWise 7 Administration Guide .

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.
Action: See 8562 Client/server request packet contained invalid identifier

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.
Action: Check the HTTP port for each POA object. See Setting Up the POA Web Console in Monitoring the POA in the GroupWise 7 Administration Guide . Change the HTTP port for one of the POAs.

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.
Action: Have users update their GroupWise client software. See Updating Users' GroupWise Clients in Update in the GroupWise 7 Installation Guide .
Action: Configure the POA so that SSL is enabled rather than required, so that the older GroupWise clients can connect to the post office. See Securing the Post Office with SSL Connections to the POA in Post Office Agent in the GroupWise 7 Administration Guide .

8570 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.
Action: Check the IMAP port for each POA object. See Supporting IMAP Clients in Configuring the POA in the GroupWise 7 Administration Guide . Change the IMAP port for one of the POAs.

8571 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.
Action: Check the SOAP port for each POA. See Supporting SOAP Clients in Configuring the POA in the GroupWise 7 Administration Guide . Change the SOAP port for one of the POAs.

8572 CAP port already in use

Source: GroupWise engine; general communication.
Explanation: The CAP port used by the POA to communicate with CAP 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 CAP port numbers.
Action: Check the CAP port for each POA object. See Supporting CAP Clients in Configuring the POA in the GroupWise 7 Administration Guide . Change the CAP port for one of the POAs.

8573 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.
Action: Check the LDAP port for each POA object. See Providing LDAP Authentication for GroupWise Users in Configuring the POA in the GroupWise 7 Administration Guide . Change the LDAP port for one of the POAs.