Home > Groupwise Error > Groupwise Error Code 8908

Groupwise Error Code 8908

Action: See 8901 Cannot use TCP/IP services. 8908 Cannot connect to specified address Source: GroupWise engine; TCP/IP communication. Possible Cause: An incorrect IP address was specified. Explanation: A GroupWise agent cannot establish an SSL connection because the SSL certificate file and the public key file cannot be used together. Action: Run the agent on a more powerful server. 891F Invalid SSL certificate Source: GroupWise engine; TCP/IP communication. check over here

If it does not respond, correct the problem with the server associated with that IP address. Explanation: A GroupWise agent failed to establish an SSL connection because insufficient memory is available for creating the connection. Explanation: A GroupWise agent cannot establish an SSL connection because the handshake negotiation between the two servers failed. Explanation: Listen failed. http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/babbgedf.html

Possible Cause: A firewall is interfering with the connection. Action: Wait and try the operation again. Action: Make sure that the DNS name server is running. In ConsoleOne, click the domain where the GWIA is installed.

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. Restart the MTA if necessary. 8910 TCP/IP read failed on an established connection Source: GroupWise engine; TCP/IP communication. The agent will try again on the next SSL connection request and might be successful. Explanation: Cannot read on connection.

See the following sections of the GroupWise 2012 Administration Guide, depending on which agent is encountering the problem: Securing the Post Office with SSL Connections to the POA in Post Office Action: Wait and try the operation again. Action: Wait and try the operation again. Explanation: The IP address or DNS hostname cannot be resolved to a host in the network.

Possible Cause: If the agent repeatedly fails to establish the SSL connection, the SSL certificate file or key file might be damaged. Action: Configure the POA for client/server processing to match the needs of the client. Action: Check the status of the MTA for the domain. Action: Correctly configure TCP/IP on the server.

Explanation: You have configured an agent for SSL, but the agent failed to establish the SSL connection. http://ngwlist.com/pipermail/ngw/2008-July/126604.html Possible Cause: The agent is not communicating on the right TCP port number. 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. Restart the MTA if necessary.

Action: Determine the configuration of the target agent and make sure the initiating agent is using the correct port number. http://glitchtest.org/groupwise-error/groupwise-error-code-8201.html Make sure you are using a current IP stack. Possible Cause: The SSL certificate has been damaged. Possible Cause: The agent or client was passed an invalid IP address.

Explanation: Cannot write on connection; the receiver isn’t responding. The machine might have been exited while connections were active. Action: Restart the GroupWise client when the machine is back up. this content Possible Cause: You are trying to use a certificate file and a public key file that were not generated for use together.

The system returned: (22) Invalid argument The remote host or network may be down. 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. The system returned: (22) Invalid argument The remote host or network may be down.

The sender isn’t writing the required information to GroupWise.

Action: Verify that the IP address and port provided in ConsoleOne are correct. Your cache administrator is webmaster. 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. Explanation: A GroupWise agent cannot establish an SSL connection because the other server failed to connect.

Make sure a current, valid winsock.dll file is available on the workstation where the problem is occurring. Action: Install the latest TCP/IP. Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server box. have a peek at these guys Explanation: The TCP/IP connection is blocked.

Possible Cause: The server that the agent is running on is not functioning normally. It lists error codes for which solutions are readily available from GroupWise engineers and testers. Action: Make sure that the third-party application and the GroupWise agent are configured to use the desired TCP port. 8926 Unknown host Source: GroupWise engine; TCP/IP communication. See Server Certificates and SSL Encryption in Security Administration in the GroupWise 2012 Administration Guide. 8923 Insufficient memory for SSL Source: GroupWise engine; TCP/IP communication.

See Encryption and Certificates in Security Administration in the GroupWise 2012 Administration Guide. Possible Cause: TCP/IP services couldn’t be used. Action: Make sure the POA is running. Possible Cause: The SSL certificate that accompanies the private key file is not in the required format.

This probably occurred in Windows where the workstation is not connected to the network. Action: Correctly configure TCP/IP on the server. 8902 Cannot load TCP/IP services Source: GroupWise engine; TCP/IP communication. Explanation: The GroupWise agent cannot write to the specified UDP socket (port). Possible Cause: Too many programs are currently running on the server.

See Server Certificates and SSL Encryption in Security Administration in the GroupWise 2012 Administration Guide. 8921 SSL accept failure Source: GroupWise engine; TCP/IP communication. Explanation: No network error. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide. 890B Cannot accept incoming connection Source: GroupWise engine; TCP/IP communication. Action: Check the network connections for the workstation. 8917 TCP/IP name lookup failed Source: GroupWise engine; TCP/IP communication.

The machine might have been exited while connections were active. Connectivity has been checked and verified for all > workstations this user logs in on. Explanation: An agent that is configured for TCP/IP attempted to contact another agent and the connection was refused. Action: Ping the IP address manually to see if it responds.

TCP/IP services will continue to try to read the data. This error > is not logged at the POA. See Encryption and Certificates in Security Administration in the GroupWise 2012 Administration Guide. 8925 Connection refused Source: GroupWise engine; TCP/IP communication.