Home > Groupwise Error > Groupwise Error 8909

Groupwise Error 8909

Possible Cause: Unable to listen on the specified port. See the Client Setup Guide. 8912 Cannot read on connection; timed out SourceGroupWise engine; TCP/IP communication. However, the information provided in this document is for your information only. 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. this contact form

Action: Obtain an SSL certificate in the proper format. Explanation: The TCP/IP connection is blocked. Action: Ping the IP address manually to see if it responds. Explanation: Connection to the specified address failed.

Use the following SET command in the AUTOEXEC.NCF file: SET MAXIMUM PACKET RECEIVE BUFFERS = number Note that the memory allocated for ECBs cannot be used for other purposes. Possible Cause: The machine where the GroupWise program is running has insufficient memory for proper functioning. Check the IP address for the POA. Action: Obtain a new SSL certificate and key file.

Possible Cause(s)A client or server machine has crashed, or the process was forced to close without shutting down. The TCP port is already in use by another process. Action(s)Exit and restart GroupWise when the server is back up. 8555 Port in use SourceGroupWise engine; general communication. These values are taken from the "Novell BorderManager Installation and Setup" manual, the chapter on "Installing Novell BorderManager", page 9.

The system returned: (22) Invalid argument The remote host or network may be down. Action: Restart the server. 8919 Attempt to bind to a non-existent IP address Source: GroupWise engine; TCP/IP communication. Consult your product manuals for complete trademark information. weblink It is possible that TCP/IP is not correctly loaded on this machine.

The system returned: (22) Invalid argument The remote host or network may be down. The server may have been exited while connections were active. The server may have been exited while connections were active. Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down.

TCP/IP services will continue to try to read the data. http://www.novell.com/support/kb/doc.php?id=7000974 ExplanationConnection to the specified address failed. Explanation: A GroupWise agent or client cannot ping the specified IP address. Possible Cause: The agent is not communicating on the right TCP port number.

Action: Make sure the POA is running. weblink See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide. Action: Restart the other server. Possible Cause(s)Cannot initialize protocol.

Possible Cause(s)TCP/IP services couldn't be used. On the other hand, if your server memory load is very high and you receive frequent ECB allocation errors, you should probably set your maximum ECB allocation higher. ExplanationNo network error. navigate here Any trademarks referenced in this document are the property of their respective owners.

Please try the request again. Possible Cause: The server that the agent is running on is not functioning normally. Explanation: A GroupWise agent cannot establish an SSL connection because the SSL certificate file and the public key file cannot be used together.

Action(s)Configure TCP/IP on the workstation correctly. 8902 Cannot load TCP/IP services SourceGroupWise engine; TCP/IP communication.

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. 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. See Use Client/Server Access to Post Office in Chapter 3: Reconfigure the POA in Book 2: Post Office Agent in the Agent Configuration Guide. 890B Cannot accept incoming connection SourceGroupWise engine; Action(s)Upgrade the hardware. 890F Connection no longer valid Source GroupWise engine; TCP/IP communication.

Possible Cause: Another program was temporarily using a very large amount of memory on the server. Action(s)Make sure the user is providing the correct IP address and port number. Action: Restart the GroupWise client. http://fileupster.com/groupwise-error/groupwise-error-601.html Action(s)Check the startup switches in use for the agent reporting the error.

ExplanationA fundamental TCP/IP call failed. Possible Cause: If this error occurs from the GWIA, the GWIA might not be able to establish a TCP/IP connection to the POA. Action(s)Provide the path to the user's post office using the /ph switch on the command line. If not, then change it to the new IP Address and press ESC key and select Yes to save the changes.Load the MTA and POA.

Document ID: 10011290 Solution ID: 4.0.1443234.2203944 Creation Date: 25Jun1999 Modified Date: 07Feb2003 Novell Product Class:Groupware disclaimer The Origin of this information may be internal or external to Novell. Exit the Link Configuration tool and save your changes9. Novell makes no explicit or implied claims to the validity of this information.