7.8 D07x 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.

D071 LDAP authentication failed because the password has expired

Source: GroupWise engine.
Explanation: The GroupWise client was attempting to authenticate using LDAP, but the user’s LDAP password has expired.
Action: The user needs to contact the administrator of the LDAP server and get the password reset.

D072 Changing the LDAP password has been disabled

Source: GroupWise engine.
Explanation: A user tried to change his or her LDAP password from the GroupWise client but the administrator has disabled that capability for the user’s post office.
Action: Enable LDAP password changes in ConsoleOne. See Providing LDAP Authentication for GroupWise Users in Post Office Agent in the GroupWise 2012 Administration Guide.
Action: Show the user what application he or she needs to use to change the LDAP password.

D073 Attempting to log in trusted without SSL

Source: GroupWise engine.
Explanation: A trusted application tried to log in to the POA and was not successful because an SSL connection could not be established.
Possible Cause: The POA is not configured to support SSL connections.
Action: Enable SSL for the POA that the trusted application needs to log in to. See Securing the Post Office with SSL Connections to the POA in Post Office Agent in the GroupWise 2012 Administration Guide.

D074 Invalid key for trusted application

Source: GroupWise engine.
Explanation: A trusted application tried to log in to the POA and was not successful because the key was invalid.
Possible Cause: The private key offered by the application did the match the private key the POA was configured to accept.
Action: Verify the private key that the POA is configured to accept. See Securing the Post Office with SSL Connections to the POA in Post Office Agent in the GroupWise 2012 Administration Guide.

D075 Invalid IP address for trusted application

Source: GroupWise engine.
Explanation: A trusted application tried to log in to the POA and was not successful because the POA was configured for a specific IP address and the trusted application was not running there.
Possible Cause: The trusted application is running on a different server from where it was designed to run.
Action: Run the trusted application on the server with the IP address that the POA is expecting.
Possible Cause: The POA is configured with an incorrect IP address for the trusted application.
Action: In eDirectory, change the expected IP address to the IP address of the server where the trusted application is running. See Trusted Applications in System in the GroupWise 2012 Administration Guide.

D076 Missing trusted application name

Source: GroupWise engine.
Explanation: A trusted application tried to log in to the POA and was not successful because no application name was provided.
Possible Cause: The trusted application is not providing an application name.
Action: Add an application name to the trusted application.
Possible Cause: The POA is configured with an incorrect application name for the trusted application.
Action: In eDirectory, change the expected application name to the application name that the trusted application is providing. See Trusted Applications in System in the GroupWise 2012 Administration Guide.

D077 The problem file is being rebuilt

Source: GroupWise engine.
Explanation: The database you want to repair cannot be accessed.
Possible Cause: You are trying to perform database maintenance on a database that is currently being repaired.
Action: None. Your database maintenance request will be deferred until the build in completed.

D078 LDAP SSL key file not found

Source: GroupWise engine.
Explanation: The POA is configured to use SSL on its LDAP connection, but it cannot locate the SSL key file.
Possible Cause: The SSL key file has not been specified or has been specified incorrectly.
Action: Provide the full path to a valid SSL key file. See Providing LDAP Authentication for GroupWise Users in Post Office Agent in the GroupWise 2012 Administration Guide. See also Server Certificates and SSL Encryption in Security Administration in the GroupWise 2012 Administration Guide.

D07B Mailbox is full

Source: GroupWise engine.
Explanation: The mailbox exceeds the size limit set by the GroupWise administrator. While this conditions exists, the user can receive messages but cannot send them.
Possible Cause: The user has received an unexpectedly large number of very large messages or attachments.
Possible Cause: The user has not emptied the Trash in a very long time.
Possible Cause: The GroupWise administrator has set the mailbox size limit unreasonably small.
Action: The user can remove items from the mailbox, especially emptying the Trash.
Action: The GroupWise administrator can make the mailbox size limit larger, as described in Setting Mailbox Size Limits in Post Offices in the GroupWise 2012 Administration Guide.

D07C Invalid content in user’s rule

Source: GroupWise engine.
Explanation: A rule cannot be executed because it does not work.
Possible Cause: The user has constructed the rule incorrectly.
Action: See Rules in the GroupWise 2012 Windows Client User Guide

D07E Sending to more recipients than allowed by your administrator. Remove some users.

Source: GroupWise engine.
Explanation: A user has been prevented from sending a message because the number of recipients exceeds the allowed number.
Possible Cause: The user wants to send the message to an unreasonable large number of recipients.
Possible Cause: The maximum number of recipients has been set too low and is hampering users from sending messages to a reasonable number of recipients.
Action: The user can send the message multiple times to different subsets of the desired set of recipients.
Action: You can increase the number of recipients that users can send a single message to. See Maximum Recipients Allowed in Client in the GroupWise 2012 Administration Guide.

D07F Sending with attachment types that are restricted by your administrator Remove the illegal attachments.

Source: GroupWise engine.
Explanation: A user has been prevented from sending a message because the message has illegal attachments.
Possible Cause: The user is not aware of what attachment types are illegal.
Possible Cause: The current set of illegal attachment types is hampering users from sending messages with attachments that need to be sent.
Action: Notify users about illegal attachment types.
Action: Allow additional attachment types. See Restricted Attachment Extensions in Client in the GroupWise 2012 Administration Guide.