7.6 D05x Errors

NOTE:This guide does not include a comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved.

D050 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: No TCP/IP services.
Possible Cause: The GroupWise client cannot connect to the specified post office in client/server mode because an IP address has not been provided. The POA in a remote post office is required for cross-post office proxy and library access.
Action: Set up the IP address for the POA. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.
Possible Cause: The GroupWise client cannot connect to the specified post office in client/server mode because the POA in that post office is not running. The POA in a remote post office is required for cross-post office proxy and library access.
Action: Make sure the POA is running in the remote post office. See Monitoring the POA in Post Office Agent in the GroupWise 2012 Administration Guide.
Action: Make sure the POA in the remote post office is configured with the correct IP address and TCP port.
Action: Make sure the POA in the remote post office is configured to allow TCP/IP connections. Make sure it has not been started with the --notcpip switch.

D051 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: TCP/IP not allowed.
Possible Cause: An attempt to connect to a post office by way of a direct or mapped mode was rejected. No IP address information is available to attempt a client/server connection. The administrator hasn’t set up the client/server addressing.
Action: Set up the IP address for the POA. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.

D054 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: Missing path for direct mode connection.
Possible Cause: The post office rejected the client/server mode connection but is allowing direct mode. The path might be set up, but not for this platform.
Action: Set up the path for the specified post office in the post office Identification page in ConsoleOne.
Action: To start the GroupWise client in direct mode, use the /ph switch to provide the path to the post office.
Action: If you want to use client/server mode, you can set up an additional POA to handle client/server communication. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.

D055 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: Cannot use direct (mapped) connection.
Possible Cause: The post office rejected the direct mode connection but is allowing client/server mode.
Action: Make sure the IP address for the POA is set up correctly. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.

D057 Cannot connect to any post office

Source: GroupWise engine.
Explanation: TCP/IP default address failed.
Possible Cause: An attempt to connect to a post office using the GroupWise IP address defaults (NGWNAMESERVER and NGWNAMESERVER2) was unsuccessful.
Possible Cause: No client/server or direct information was specified or available.
Action: Make sure the GroupWise name server is properly set up and running. See Simplifying Client/Server Access with a GroupWise Name Server in Post Office Agent in the GroupWise 2012 Administration Guide.
Possible Cause: The GroupWise name server cannot locate any post offices.
Action: Make sure the network connections to the servers where post offices reside are functioning properly.

D058 Version mismatch on GroupWise client/POA/post office

Source: GroupWise engine.
Explanation: The post office directory, with its associated user databases (userxxx.db) and message databases (msgnnn.db) was created by a version of GroupWise that is older than the version of the GroupWise client that is accessing the post office.
Possible Cause: A user is running the latest version of the GroupWise client, but the post office has not yet been updated.
Action: Update the post office. See Update in the GroupWise 2012 Installation Guide.
Possible Cause: The post office has been updated, but the latest version of the POA has not yet been installed and started.
Action: Update the POA. See Updating Post Offices in Update in the GroupWise 2012 Installation Guide.

D059 Recursion limit exceeded during delivery

Source: GroupWise engine.
Explanation: The POA received a message that contained more than 36 levels of encapsulation. The POA could not deliver the message.
Possible Cause: This can be caused by rule forwarding loops that include one hop to an external user, or by some Internet chain letters.
Action: Check the rule configuration of the GroupWise recipient. Disable any rules that forward mail to an external user who might be forwarding the mail back into GroupWise. Look up “rules” in GroupWise client Help.

D05A User database access denied

Source: GroupWise engine.
Explanation: The GroupWise client cannot start because it cannot access the user’s user database (userxxx.db).
Possible Cause: The user tried to access a mailbox that does not have a password using the wrong network user ID, in a post office with security set to high.
Action: Set a password on the user’s mailbox. See Creating or Changing a Mailbox Password in Users in the GroupWise 2012 Administration Guide.
Possible Cause: The user’s current login ID, either from eDirectory or Windows, does not match the network login ID stored in the GroupWise user database.
Action: Make sure the user is using the correct login ID.
Possible Cause: Password information in the user database might be damaged.
Action: Check and, if necessary, repair the database, including resetting user options to reset the password. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: Run GWCheck. See Stand-Alone Database Maintenance Programs in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The post office database (wphost.db) might be damaged.
Action: Rebuild the index of the post office database. See Rebuilding Database Indexes in Databases in the GroupWise 2012 Administration Guide.
Action: If rebuilding the index is not sufficient to resolve the problem, validate the database, then take the appropriate actions to either recover or rebuild the database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The IP address of the POA has changed, but GroupWise client users are still trying to start the client using old /ipa and /ipp client switch settings.
Action: Update the information in users’ /ipa and /ipp switch settings with the current IP address information.
Action: Remove the /ipa and /ipp switches and let the client and/or the POA resolve the address. See Simplifying Client/Server Access with a GroupWise Name Server in Post Office Agent in the GroupWise 2012 Administration Guide.

D05D Post office intruder lockout is enforced

Source: GroupWise engine.
Explanation: The POA has detected a possible intruder. The user has been locked out.
Action: You have several options for handling the situation. See Enabling Intruder Detection in Post Office Agent in the GroupWise 2012 Administration Guide.

D05E Message size exceeds limit

Source: GroupWise engine.
Explanation: A user tried to send a message that exceeded the user’s message size limit as set by the administrator.
Possible Cause: The user is not aware that there is a message size limit on his or her mailbox.
Action: Notify the user of the message size limit so that the user can send messages of appropriate size.
Possible Cause: The administrator has set a message size limit that is too restrictive. Increase the message size limit.
Action: Increase the maximum message size for the user. See Send Options: Disk Space Management in Users in the GroupWise 2012 Administration Guide.

D05F Box size limit exceeded

Source: GroupWise engine.
Explanation: A user’s GroupWise mailbox exceeds the size limit set by the administrator
Possible Cause: The user is not aware that there is a size limit on his or her mailbox.
Action: Notify the user of the mailbox size limit so that the user can delete unneeded messages from the mailbox.
Possible Cause: The administrator has set a mailbox size limit that is too restrictive. Increase the message size limit.
Action: Increase the maximum mailbox size for the user. See Send Options: Disk Space Management in Users in the GroupWise 2012 Administration Guide.