Home > Groupwise Error > Groupwise Error D039

Groupwise Error D039

Action: See 8901 Cannot use TCP/IP services. 8907 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. 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. Possible Cause: Too many programs are currently running on the server. weblink

Action: Obtain an SSL certificate in the proper format. It happens to the best of em..A lot of people just don't have the time/resources to become intimately familiar with the architecture of GroupWise and the required maintenance. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. Action: Wait and try the operation again. http://www.novell.com/documentation/nwec/index.html?page=/documentation/nwec/nwec/data/higmv673.html

If you are not the intended recipient, you must immediately notify the sender via electronic mail and further refrain from reading, disseminating, distributing, copying or using this message or any of 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: See 8901 Cannot use TCP/IP services. 8908 Cannot connect to specified address Source: GroupWise engine; TCP/IP communication. Action: See 8901 Cannot use TCP/IP services. 890A Cannot listen on specified port Source: GroupWise engine; TCP/IP communication.

This document only contains return values for Target Services. D039 Missing attachment Source: GroupWise engine. Action: Check and, if necessary, repair the user and/or message databases. Possible Cause: If this error occurs in the GroupWise client in Remote mode, there might be a problem with the structure or content of the Remote mailbox.

Explanation: A GroupWise agent or client cannot ping the specified IP address. Possible Cause: TCP/IP services couldn’t be used. The machine might have been exited while connections were active. If it does not respond, correct the problem with the server associated with that IP address.

Though this message and its transmitted files have been swept for the presence of computer viruses, the North-West Provincial Government accepts no liability whatsoever for any loss, damage or expenses resulting Action: Obtain an SSL certificate in the proper format. How can you say that without laughing hysterically?What is your basis?What is the OS that GroupWise is running on?I see systems like yours all the time, usually with first time customers.Their I bet if you had someone who knows GroupWise look over your system, straighten a few things out, lube the chassis and change the oil and rotate the tires, you'd be

Action: Make sure that the DNS name server is running. http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/b4k4bku.html See the following sections of the GroupWise 2012 Administration Guide, depending on which agent is refusing the connection: Using Client/Server Access to the Post Office in Post Office Agent Using TCP/IP This probably occurred in Windows where the workstation is not connected to the network. I get it, you have other stuff to do besides manage GroupWise.So it gets ignored, then you have strange problems like you mention.

The machine might have been exited while connections were active. have a peek at these guys Please try the request again. Easy fix just go an delete the rofdata folderon her remote but she does not have a remote.. Explanation: An attachment for a message can no longer be found.

Possible Cause: If this error occurs from the GWIA, the GWIA might not be able to establish a TCP/IP connection to the POA. Possible Cause: Cannot load WINSOCK (Windows only), or the WINSOCK that did load is not supported. 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. check over here See Encryption and Certificates in Security Administration in the GroupWise 2012 Administration Guide. 8925 Connection refused Source: GroupWise engine; TCP/IP communication.

However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Action: Obtain usable files.

Action: Specify the IP address instead of the DNS hostname. 8927 Host not reachable Source: GroupWise engine; TCP/IP communication.

The system returned: (22) Invalid argument The remote host or network may be down. novell.support.groupwise.6x.clients Discussion: GroupWise error message D039 (too old to reply) w***@oceaneering.com 2006-02-03 16:11:19 UTC PermalinkRaw Message I have a user getting this error when she tries to modify an appointment onhere Action: Ping the IP address manually to see if it responds. Possible Cause: Another program was temporarily using a very large amount of memory on the server.

Possible Cause: One of the files is damaged. Explanation: A GroupWise agent cannot establish an SSL connection because the handshake negotiation between the two servers failed. Already a member? this content document Document Title: POA Displays Error D039 Document ID: 2957055 Creation Date: 04Jul2000 Modified Date: 04Jul2000 Revision: 3 Novell Product Class:Groupware disclaimer The Origin of this information may be internal or

Possible Cause: You are trying to use a certificate file and a public key file that were not generated for use together. Possible Cause: Hardware is overloaded. Explanation: An agent that is configured for TCP/IP attempted to contact another agent and no route could be found on the network to contact the specified host. Action: Wait and try the operation again.

Possible Cause: The user database (userxxx.db) and/or message database (msgnnn.db) for the user have been damaged. Action: Check the status of the MTA for the domain. If you must use an older IP stack, try specifying the IP address in dotted numeric format (172.16.5.18), rather than as a hostname that requires resolution, when setting the --ipa switch. Explanation: Cannot write on connection; the receiver isn’t responding.

Explanation: Listen failed. Action: Make sure that you have the required files, and that they are in the search path. In ConsoleOne, click the domain where the GWIA is installed. Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down.

See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide. Action: Run the agent on a more powerful server. 8924 SSL handshake timeout failure Source: GroupWise engine; TCP/IP communication. Action: Make sure that all routers are running. Restart the MTA if necessary. 8910 TCP/IP read failed on an established connection Source: GroupWise engine; TCP/IP communication.

Possible Cause: The certificate file is damaged. Action: Stop some programs that are running on the machine in order to free up some memory. Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down.