7.7 D06x Errors

D060 Message size exceeds threshold limit

Source: GroupWise engine.
Explanation: A user’s GroupWise mailbox is close to exceeding 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 8 Administration Guide.

D061 Status denied to external Internet user

Source: GroupWise engine.
Explanation: The local GroupWise system is configured so that users outside the local GroupWise system cannot receive status information about messages.
Action: To permit access to status information by external users, enable Allow External Status Tracking. See System Preferences in System in the GroupWise 8 Administration Guide.

D062 Busy Search denied for external Internet user

Source: GroupWise engine.
Explanation: The local GroupWise system is configured so that users outside the local GroupWise system cannot perform Busy Searches on local users.
Action: To permit Busy Search access by external users, enable Allow External Busy Search. See System Preferences in System in the GroupWise 8 Administration Guide.

D065 Attempt to purge item that has not been backed up

Source: GroupWise engine.
Explanation: Client Cleanup options are set so that items cannot be purged from users’ mailboxes until they have been backed up. A user has tried to purge an item that has not yet been backed up.
Action: You can allow users to purge items that have not yet been backed up. See Environment Options: Cleanup in Users in the GroupWise 8 Administration Guide. See also GroupWise Time Stamp Utility in Databases in the GroupWise 8 Administration Guide.

D066 Attempt to purge an item from a user that has not been backed up

Source: GroupWise engine.
Explanation: Client Cleanup options are set so that items cannot be purged from users’ mailboxes until they have been backed up. A process has tried to purge an item that has not yet been backed up.
Action: You can allow purging of items that have not yet been backed up. See Environment Options: Cleanup in Users in the GroupWise 8 Administration Guide. See also GroupWise Time Stamp Utility in Databases in the GroupWise 8 Administration Guide.

D069 Attempt to open invalid backup location

Source: GroupWise engine.
Explanation: The user attempted to open a backup location that did not contain a valid backup of a GroupWise post office or mailbox.
Possible Cause: The user is unsure of the backup location.
Action: Make sure users know where their backed-up messages have been restored. See Restoring Deleted Mailbox Items in Databases in the GroupWise 8 Administration Guide.
Possible Cause: The backup location path includes a directory name that has more than eight characters.
Action: Rename any long directory names to eight characters maximum, then make matching changes to the restore area information in ConsoleOne. See Setting Up a Restore Area in Databases in the GroupWise 8 Administration Guide.
Possible Cause: The restore area is in a location where the POA does not have the necessary rights to access it.
Action: If the restore area is on a different server from where the POA is running, provide a username and password for the POA to use to access the remote location. You can provide this information in ConsoleOne in the Remote File Server Settings box on the Post Office Settings page of the Post office object or in the POA startup file using the /user and /password switches.
Action: If the restore area is on the same server, add a trustee assignment to the restore area directory that provides the POA with object file system rights to the directory.

D06A Inform the remote client to retry the login

Source: GroupWise engine.
Explanation: The POA is currently out of threads for service Caching users.
Possible Cause: The POA is very busy.
Action: Increase the number of client/server processing threads, as described in Adjusting the Number of POA Threads for Client/Server Processing in Post Office Agent in the GroupWise 8 Administration Guide.
Action: Increase the maximum number of threads for priming and moves, as described in Supporting Forced Mailbox Caching in Post Office Agent in the GroupWise 8 Administration Guide, if this configuration option pertains to your GroupWise system.
Action: Wait until the POA has threads available for servicing your Caching mailbox.

D06B LDAP failure detected

Source: GroupWise engine.
Explanation: GroupWise was unable to authenticate using LDAP.
Action: Make sure your LDAP server is functioning correctly.

D06E Lockout of older GroupWise clients being enforced

Source: GroupWise engine.
Explanation: The POA is not allowing GroupWise client users with older versions of the client software to access the post office.
Possible Cause: The administrator does not want older versions of the GroupWise client to access the post office. The client version can be controlled as described in Checking What GroupWise Clients Are in Use in Post Office Agent in the GroupWise 8 Administration Guide
Action: GroupWise client users must update their client software before they can access the post office. See Updating Users’ GroupWise Clients in Updating Your GroupWise 7 System to Version 8 in the GroupWise 8 Installation Guide.

D06F This GroupWise client doesn’t match the user’s license

Source: GroupWise engine.
Explanation: The GroupWise administrator has restricted client users to the WebAccess client and a user is attempting to access his or her mailbox using the Windows client.
Action: Explain to the user that he or she must use the WebAccess client.
Action: Allow the user to use the Windows client. See Setting Client Options in Users in the GroupWise 8 Administration Guide.