Home > Groupwise Error > Groupwise Error Code 8908

Groupwise Error Code 8908

The sender isn’t writing the required information to GroupWise. Name: not available Type: image/gif Size: 2918 bytes Desc: not available Url : http://ngwlist.com/pipermail/ngw/attachments/20080716/84103a15/attachment.gif Previous message: GroupWise Error [8908] Next message: [ngw] GroupWise Error [8908] Messages sorted by: [ date ] If it does not respond, correct the problem with the server associated with that IP address. Action: Correct the password information in ConsoleOne. navigate here

Action: Check the status of the MTA for the domain. Possible Cause: One of the files is damaged. Possible Cause: The other server is down. Action: None. navigate here

The machine might have been exited while connections were active. Action: Obtain a usable certificate file. Explanation: The other end of the connection has stopped responding.

Explanation: A GroupWise agent cannot establish an SSL connection because the other server failed to connect. Possible Cause: Another program was temporarily using a very large amount of memory on the machine. Action: Retry the operation. 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

In ConsoleOne, click the domain where the GWIA is installed. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide. Possible Cause: If a DNS hostname was specified, the DNS name server might not be running. http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/al39nm6.html 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.

URL: http://ngwlist.com/pipermail/ngw/attachments/20080716/84103a15/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... 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: A GroupWise agent failed to establish an SSL connection because insufficient memory is available for creating the connection. Action: Configure the POA for client/server processing to match the needs of the client.

See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide. 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. Possible Cause: GroupWise has encountered unusually long timeouts while trying to retrieve names from DNS. Restart the MTA if necessary.

Connectivity between GW agents is good. > We run GW 7.0.1 on NetWare 6.5 sp7. > > Any ideas as to the possible cause of this? > > Thanks, > Jeff http://jennysbookreview.com/groupwise-error/groupwise-error-code-c081.php Explanation: The TCP/IP connection is blocked. Possible Cause: Too many programs are currently running on the server. This error > is not logged at the POA.

See Encryption and Certificates in Security Administration in the GroupWise 2012 Administration Guide. Action: Make sure that you have the required files, and that they are in the search path. 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. his comment is here Please try the request again.

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. The agent will try again on the next SSL connection request and might be successful. DNS is not loaded and you are trying to resolve DNS names.

The machine might have been exited while connections were active.

Explanation: You have configured an agent for SSL, but the agent cannot locate the SSL certificate. Generated Thu, 24 Nov 2016 14:55:49 GMT by s_fl369 (squid/3.5.20) Action: Correctly configure TCP/IP on the server. 8902 Cannot load TCP/IP services Source: GroupWise engine; TCP/IP communication. Possible Cause: The GroupWise client cannot establish a TCP/IP connection with the POA.

See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide. Possible Cause: A firewall is interfering with the connection. Action: Restart the other server. weblink Action: Verify the IP address.

Possible Cause: If the agent repeatedly fails to establish the SSL connection, the SSL certificate file or key file might be damaged. 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. 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: A GroupWise agent cannot establish an SSL connection because the SSL certificate file is not usable. Possible Cause: Unable to listen on the specified port.