> Groupwise Error
> Groupwise Error Code 8908
Groupwise Error Code 8908
Action: Run the agent on a more powerful server. 891F Invalid SSL certificate Source: GroupWise engine; TCP/IP communication. Action: Retry the operation. Action: Make sure that all routers are running. Action: Obtain a usable certificate file. his comment is here
The machine might have been exited while connections were active. 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. It is possible that TCP/IP is loaded incorrectly on this server. Action: Wait and try the operation again. http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/babbgedf.html
Explanation: Connection to the specified address failed. Generated Thu, 24 Nov 2016 14:55:49 GMT by s_fl369 (squid/3.5.20) You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved. 8901 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP Action: Determine what the correct IP address should be. 8918 UDP send failed Source: GroupWise engine; TCP/IP communication.
Explanation: A GroupWise agent cannot establish an SSL connection because the handshake negotiation between the two servers failed. Action: Obtain an SSL certificate in the proper format. 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. The machine might have been exited while connections were active.
Possible Cause: If the agent repeatedly fails to establish the SSL connection, the SSL certificate file or key file might be damaged. Explanation: A GroupWise agent cannot establish an SSL connection because the other server failed to connect. Possible Cause: Cannot load WINSOCK (Windows only), or the WINSOCK that did load is not supported. Discover More Explanation: You have configured an agent for SSL, but the agent cannot read the private key file or the password.
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. Possible Cause: The agent or client was passed an invalid IP address. If that does not help, a Analyze/Fix with or without contents. My AccountSearchMapsYouTubePlayNewsGmailDriveCalendarGoogle+TranslatePhotosMoreShoppingWalletFinanceDocsBooksBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the
Possible Cause: The server where the agent is running has insufficient memory for proper functioning. Explanation: Cannot write on connection; the receiver isn’t responding. Right-click the GWIA object, then click Properties. 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.
Restart the MTA if necessary. 8910 TCP/IP read failed on an established connection Source: GroupWise engine; TCP/IP communication. this content URL: http://ngwlist.com/pipermail/ngw/attachments/20080716/84103a15/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Action: Verify that the IP address and port provided in ConsoleOne are correct. 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.
On Wed, Jul 16, 2008 at 6:10 PM, Jeff Bernier wrote: > Hi All, > > One user is seeing the following error on the Cross Platform GW 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. Do NOT run a recreate user database. weblink Click Post Office Links, select the post office, then click Edit Link.
Action: Specify the IP address instead of the DNS hostname. 8927 Host not reachable Source: GroupWise engine; TCP/IP communication. If it does not respond, correct the problem with the server associated with that IP address. 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  Next message: [ngw] GroupWise Error  Messages sorted by: [ date ]
Possible Cause: An incorrect IP address was specified. Possible Cause: Another program was temporarily using a very large amount of memory on the server. Action: Check the status of the MTA for the domain. Make sure you are using a current IP stack.
Action: Make sure the POA is running. TCP/IP services will continue to try to read the data. Explanation: No network error. check over here Possible Cause: The agent is not communicating on the right TCP port number.
Your cache administrator is webmaster. Explanation: The GroupWise agent cannot write to the specified UDP socket (port). Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down. Explanation: You have configured an agent for SSL, but the agent cannot read the SSL certificate.
Action: Correctly configure TCP/IP on the server. Action: Finish configuring the agent for SSL. Possible Cause: One of the files is damaged. Action: Obtain usable files.