2.5 89xx Errors
8901 Cannot use TCP/IP services
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A fundamental TCP/IP call failed.
Possible Cause:
TCP/IP services couldn’t be used. It is possible that TCP/IP is loaded incorrectly on this server.
Possible Cause:
Cannot load WINSOCK (Windows only), or the WINSOCK that did load is not supported. DNS is not loaded and you are trying to resolve DNS names.
Action:
Correctly configure TCP/IP on the server.
8902 Cannot load TCP/IP services
Source:
GroupWise engine; TCP/IP communication.
Explanation:
TCP/IP load failed because a required file was missing.
Possible Cause:
Unable to load TCP/IP services because one or more of the required files is missing:
winsock.dll,
wsoc32.dll, or
tcpip.nlm.
Action:
Make sure that you have the required files, and that they are in the search path.
Action:
Correctly configure TCP/IP on the server.
8903 Cannot use TCP/IP services
Source:
GroupWise engine; TCP/IP communication.
8906 Cannot use TCP/IP services
Source:
GroupWise engine; TCP/IP communication.
8907 Cannot use TCP/IP services
Source:
GroupWise engine; TCP/IP communication.
8908 Cannot connect to specified address
Source:
GroupWise engine; TCP/IP communication.
Explanation:
Connection to the specified address failed.
Possible Cause:
Unable to load TCP/IP services because one or more of the required files is missing:
winsock.dll,
wsoc32.dll, or
tcpip.nlm.
Action:
Make sure that you have the required files, and that they are in the search path.
Action:
Correctly configure TCP/IP on the server. Make sure you are using a current IP stack. If you must use an older IP stack, try specifying the IP address in dotted numeric format (172.16.5.18), rather than as a host name that requires resolution, when setting the /ipa switch.
Action:
When using direct mode rather than client/server, the GroupWise client still requires a valid winsock.dll to be available on the search path. Make sure a current, valid
winsock.dll file is available on the workstation where the problem is occurring.
Possible Cause:
The GroupWise client cannot establish a TCP/IP connection with the POA.
Action:
Check the status of the POA server and the load on the network.
Possible Cause:
If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages is not running.
Action:
Check the status of the MTA for the domain. Restart the MTA if necessary.
Possible Cause:
If this error occurs from the GroupWise Internet Agent, the Internet Agent might not be able to establish a TCP/IP connection to the POA.
Action:
Check the post office link set up for the Internet Agent. In ConsoleOne, click the domain where the Internet Agent is installed. Right-click the Internet Agent object, then click
. Click
, select the post office, then click
. Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server box.
Action:
Use a UNC or mapped link between the Internet Agent and the POA, rather than a TCP/IP link.
8909 Cannot use TCP/IP services
Source:
GroupWise engine; TCP/IP communication.
890A Cannot listen on specified port
Source:
GroupWise engine; TCP/IP communication.
Explanation:
Listen failed.
Possible Cause:
Unable to listen on the specified port. It is possible the specified port is in use by another process. For example, two GroupWise agents might be running on the same server where both were configured for the same port.
890B Cannot accept incoming connection
Source:
GroupWise engine; TCP/IP communication.
Explanation:
Acceptance failed.
Possible Cause:
Hardware is overloaded.
Action:
Upgrade the hardware.
890F Connection no longer valid
Source:
GroupWise engine; TCP/IP 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.
Possible Cause:
The GroupWise client is trying to use client/server mode to connect with the POA, but the POA is not set up for client/server processing.
Possible Cause:
If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages is not running.
Action:
Check the status of the MTA for the domain. Restart the MTA if necessary.
8910 Cannot read on connection
Source:
GroupWise engine; TCP/IP communication.
Explanation:
Read failed.
Action:
Retry the operation.
8911 Cannot write on connection
Source:
GroupWise engine; TCP/IP communication.
Explanation:
Cannot write on connection; the receiver isn’t responding.
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:
Restart the GroupWise client.
Possible Cause:
If this error occurs from the POA, the server where the POA runs might not have the most current version of TCP/IP.
Action:
Install the latest TCP/IP. For technical services and file updates, see
Novell Support.
8912 Cannot read on connection; timed out
Source:
GroupWise engine; TCP/IP communication.
Explanation:
Cannot read on connection. The sender isn’t writing the required information to GroupWise.
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:
Restart the GroupWise client when the machine is back up.
Possible Cause:
If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages might be restarting.
Action:
Check the status of the MTA for the domain. If the MTA is restarting, the message transfer status should change to Open after the restart is completed.
8913 Cannot write on connection; timed out
Source:
GroupWise engine; TCP/IP communication.
Explanation:
Cannot write on connection because it is no longer available.
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:
Restart the GroupWise client to reestablish the connection.
8915 The server or the client machine is running out of memory
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise program failed to establish a connection because insufficient memory is available for creating the connection.
Possible Cause:
Another program was temporarily using a very large amount of memory on the machine.
Action:
Wait and try the operation again.
Possible Cause:
Too many programs are currently running on the machine.
Action:
Stop some programs that are running on the machine in order to free up some memory.
Possible Cause:
The machine where the GroupWise program is running has insufficient memory for proper functioning.
Action:
Run the GroupWise program on a more powerful machine.
8916 Cannot use TCP/IP services
Source:
GroupWise engine; TCP/IP communication.
Explanation:
No network error.
Possible Cause:
TCP/IP services couldn’t be used. It is possible that TCP/IP isn’t loaded correctly on the server.
Possible Cause:
GroupWise has encountered unusually long timeouts while trying to retrieve names from DNS. This probably occurred in Windows where the workstation is not connected to the network.
Action:
Check the network connections for the workstation.
8917 TCP/IP name lookup failed
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise agent or client cannot ping the specified IP address.
Possible Cause:
The agent or client was passed an invalid IP address.
Action:
Ping the IP address manually to see if it responds. If it does not respond, correct the problem with the server associated with that IP address.
Action:
Determine what the correct IP address should be.
Source:
GroupWise engine; TCP/IP communication.
Explanation:
The GroupWise agent cannot write to the specified UDP socket (port).
Possible Cause:
The server that the agent is running on is not functioning normally.
Action:
Restart the server.
8919 Attempt to bind to a non-existent IP address
Source:
GroupWise engine; TCP/IP communication.
Explanation:
The GroupWise agent cannot locate the specified IP address to set up an exclusive bind on it.
Possible Cause:
The agent is configured to bind to an IP address but that IP address is not available on the server where the agent is running.
Action:
Determine what IP addresses are available on the server where the agent is running, then configure the agent to use a valid IP address. See the following sections of the
GroupWise 7 Administration Guide
, depending on which agent is encountering the problem:
891A TCP/IP data is not ready for reading
Source:
GroupWise engine; TCP/IP communication.
Explanation:
The TCP/IP connection is blocked.
Possible Cause:
The data has been delayed by SSL encryption.
Action:
None. TCP/IP services will continue to try to read the data.
Action:
If the problem persists, check the line connection and the NIC card on the server.
891B No SSL certificate supplied
Source:
GroupWise engine; TCP/IP communication.
Explanation:
You have configured an agent for SSL, but the agent cannot locate the SSL certificate.
Possible Cause:
In ConsoleOne, you enabled SSL on the Agent object Network Address page but did not provide the certificate information on the SSL Settings page.
Action:
Finish configuring the agent for SSL. See the following sections of the
GroupWise 7 Administration Guide
, depending on which agent is encountering the problem:
Source:
GroupWise engine; TCP/IP communication.
Explanation:
You have configured an agent for SSL, but the agent cannot read the SSL certificate.
Possible Cause:
The SSL certificate is not in the required format.
Possible Cause:
The SSL certificate has been damaged.
Action:
Replace the bad SSL certificate with a valid SSL certificate.
891D Bad SSL private key or password
Source:
GroupWise engine; TCP/IP communication.
Explanation:
You have configured an agent for SSL, but the agent cannot read the private key file or the password.
Possible Cause:
The SSL certificate that accompanies the private key file is not in the required format.
Possible Cause:
The password you provided on the agent object SSL Settings page in ConsoleOne does not match the password in the private key file.
Action:
Correct the password information in ConsoleOne. See the following sections of the
GroupWise 7 Administration Guide
, depending on which agent is encountering the problem:
891E Insufficient memory for SSL
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise agent failed to establish an SSL connection because insufficient memory is available for creating the connection.
Possible Cause:
Another program was temporarily using a very large amount of memory on the server.
Action:
Wait and try the operation again.
Possible Cause:
Too many programs are currently running on the server.
Action:
Stop some programs that are running on the server in order to free up some memory.
Possible Cause:
The server where the agent is running has insufficient memory for proper functioning.
Action:
Run the agent on a more powerful server.
891F Invalid SSL certificate
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise agent cannot establish an SSL connection because the SSL certificate file is not usable.
Possible Cause:
The certificate file is damaged.
8920 SSL certificate and private key do not match
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise agent cannot establish an SSL connection because the SSL certificate file and the public key file cannot be used together.
Possible Cause:
One of the files is damaged.
Possible Cause:
You are trying to use a certificate file and a public key file that were not generated for use together.
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise agent cannot establish an SSL connection because the handshake negotiation between the two servers failed.
Possible Cause:
Both servers might have identical certificate files.
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise agent cannot establish an SSL connection because the other server failed to connect.
Possible Cause:
The other server is down.
Action:
Restart the other server.
Possible Cause:
The certificate file is damaged.
8923 Insufficient memory for SSL
Source:
GroupWise engine; TCP/IP communication.
Explanation:
A GroupWise agent failed to establish an SSL connection because insufficient memory is available for creating the connection.
Possible Cause:
Another program was temporarily using a very large amount of memory on the server.
Action:
Wait and try the operation again.
Possible Cause:
Too many programs are currently running on the server.
Action:
Stop some programs that are running on the server in order to free up some memory.
Possible Cause:
The server where the agent is running has insufficient memory for proper functioning.
Action:
Run the agent on a more powerful server.
8924 SSL handshake timeout failure
Source:
GroupWise engine; TCP/IP communication.
Explanation:
You have configured an agent for SSL, but the agent failed to establish the SSL connection. The agent will try again on the next SSL connection request and might be successful.
Possible Cause:
If the agent repeatedly fails to establish the SSL connection, the SSL certificate file or key file might be damaged.
Source:
GroupWise engine; TCP/IP communication.
Explanation:
An agent that is configured for TCP/IP attempted to contact another agent and the connection was refused.
Possible Cause:
The agent is not communicating on the right TCP port number.
Action:
Determine the configuration of the target agent and make sure the initiating agent is using the correct port number. See the following sections of the
GroupWise 7 Administration Guide
, depending on which agent is refusing the connection:
Possible Cause:
If you are running GroupWise Mobile Server (GMS), the POA might not be able to communicate with it on the default TCP port of 8191.
Action:
Make sure that GMS is using port 8191.
Possible Cause:
If you are using a third-party application that communicates with a GroupWise agent, the agent might not be able to communicate with it on the exported TCP port.
Action:
Make sure that the third-party application and the GroupWise agent are configured to use the desired TCP port.
Source:
GroupWise engine; TCP/IP communication.
Explanation:
The IP address or DNS hostname cannot be resolved to a host in the network.
Possible Cause:
An incorrect IP address was specified.
Action:
Verify the IP address.
Possible Cause:
If a DNS hostname was specified, the DNS name server might not be running.
Action:
Make sure that the DNS name server is running.
Action:
Specify the IP address instead of the DNS hostname.
Source:
GroupWise engine; TCP/IP communication.
Explanation:
An agent that is configured for TCP/IP attempted to contact another agent and no route could be found on the network to contact the specified host.
Possible Cause:
A firewall is interfering with the connection.
Action:
Contact the administrator of the firewall to obtain the external IP address for use outside the firewall.
Possible Cause:
A router is down.
Action:
Make sure that all routers are running.