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)Check the status of the POA server and the load on the network. 890A Cannot listen on specified port SourceGroupWise engine; TCP/IP communication. I've found references to this type of error, but only in reference to proxy access issues, so not the same context as I'm seeing it. Specify the script information, then click Save. this contact form
Possible Cause(s)A client or server machine has crashed, or the process was forced to close without shutting down. Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server box. For more information about using LDAP for authentication, see Providing LDAP Authentication for GroupWise Users in Post Office Agent in the GroupWise 2012 Administration Guide. Possible Cause: The server where the agent is running has insufficient memory for proper functioning. https://forums.novell.com/showthread.php/465075-GW-deskop-client-8503-errors
LDAP failure detected Required information is missing from the connection Some setup files are missing The following information necessary to run GroupWise against... Please try the request again. See Installing the GroupWise Client in the GroupWise 2012 Installation Guide. Possible Cause: The application is unable to use the provided network connection path.
Action: See 8908 Cannot connect to specified address. 8509 Cannot access TCP/IP services Source: GroupWise engine; general communication. ExplanationCannot write on connection; the receiver isn't responding. Possible Cause: Another program was temporarily using a very large amount of memory on the server. Action: Check the HTTP port for each POA object.
The machine might have been exited while connections were active. Action: Replace the bad SSL certificate with a valid SSL certificate. 891D Bad SSL private key or password Source: GroupWise engine; TCP/IP communication. Action(s)Check the network connections for the workstation. 8F03 Invalid configuration option SourceGroupWise engine; server toolkit. Possible Cause: You are trying to run two POAs on the same server and you have not given them unique IMAP port numbers.
Possible Cause(s)TCP/IP services couldn't be used. Some setup files are missing Source: GroupWise Windows client; Remote mode. Explanation: Cannot write on connection; the receiver isn’t responding. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.
Possible Cause: A TCP/IP packet was damaged in transit. weblink Action: Make sure that you have the required files, and that they are in the search path. RE: GWIA and smtp jjtbt (MIS) (OP) 1 Feb 08 09:58 Thanks for the suggestion of trying Thunderbird...its errors actually helped me to find the solution.It led me to tweak some 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. Possible Cause(s)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. Already a member? navigate here Action: Send another request to the master GroupWise system.
Possible Cause(s)A client or server machine has crashed, or the process was forced to close without shutting down. Error: 8503 Error: Could not connect to the specified network address. The path might be entered incorrectly or there might be network changes.
Action: See 8562 Client/server request packet contained invalid identifier 8567 Data not in BCEF format Source: GroupWise engine; general communication. See Post Office Access Modes in Chapter 1: Message Delivery and Storage in the Post Office in the Agent Configuration Guide. 8910 Cannot read on connection Source GroupWise engine; TCP/IP communication. Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. 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
Possible Cause: You are trying to use a certificate file and a public key file that were not generated for use together. Action: Wait and try the operation again. Action: Correctly configure TCP/IP on the server. 8902 Cannot load TCP/IP services Source: GroupWise engine; TCP/IP communication. http://fileupster.com/groupwise-error/groupwise-error-code-7.html Action: Obtain an SSL certificate in the proper format.
Explanation: You have configured an agent for SSL, but the agent cannot read the SSL certificate. Possible Cause: Users of clients earlier than GroupWise 6.5 are trying to log in to the post office. ExplanationConnection was broken while in use. Possible Cause(s)TCP/IP is not loaded on the workstation or is not loaded correctly.
Action: Check the post office link set up for the GWIA. Same for error codes 8903, 8906, 8907, 8909. Action(s)Change the access mode in the post office to direct mode to match the capabilities of the POA. Explanation: A GroupWise agent or client cannot ping the specified IP address.
Check the gateway login ID... Action: Check the TCP port for each POA object. I upgraded users desktop clients that were on GW8 to GW2012sp1 and that has not resolved the issue (our backend servers are Linux Sles 11sp2 with GW2012sp1). IP Address and Port for TCP/IP Connections: To check the IP address and port in ConsoleOne, double-click the Post Office object to connect to, right-click the POA object, then click Properties.
Action: Run the GroupWise program on a more powerful machine. 8916 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Action: Check your system security. 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