7.20 DB1x 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.

DB10 Post office not found

Source: GroupWise engine; administration engine.
Explanation: Post office not found.
Possible Cause: Cannot find the specified post office.
Action: Make sure that the post office exists and that the post office name is correct. In ConsoleOne, browse to and right-click the Post Office object, then click Properties.

DB11 Unexpected error

Source: GroupWise engine; administration engine.
Action: See Dxxx Unexpected error.

DB12 Maximum number of objects per post office reached

Source: GroupWise engine; administration engine.
Explanation: No more file ID combinations exist for the post office.
Possible Cause: The maximum user limit has been reached for this post office. The maximum number of FID combinations is approximately 46,000 per post office.
Action: Delete obsolete users. See Removing GroupWise Accounts in Users in the GroupWise 2012 Administration Guide.
Action: Remove unneeded resources. See Deleting a Resource in Resources in the GroupWise 2012 Administration Guide.
Action: Create additional post offices. See Creating a New Post Office in Post Offices in the GroupWise 2012 Administration Guide.

DB17 Domain already exists in specified directory

Source: GroupWise engine; administration engine.
Explanation: Directory exists.
Possible Cause: A domain already exists in the specified directory.
Action: Specify a new domain directory or remove the existing domain. See Deleting a Domain in Domains in the GroupWise 2012 Administration Guide.

DB19 Local post office not found

Source: GroupWise engine; administration engine.
Explanation: No local post office record found.
Possible Cause: GroupWise was unable to find a local post office. The post office database (wphost.db) might have been damaged.
Action: Validate the post office database and rebuild if necessary. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

DB1A Insufficient administrative rights to perform operation

Source: GroupWise engine; administration engine.
Explanation: No administrative rights to perform action.
Possible Cause: The current domain has no administrative rights to perform the specified action for the selected record.
Action: Connect to the GroupWise system that owns this record. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide.

DB1B Message Transfer Agent not installed

Source: GroupWise engine; administration engine.
Explanation: The MTA is not installed.
Possible Cause: The MTA is not installed, or the MTA record is missing from the database.
Action: Set up the MTA. See Installing GroupWise Agents in the GroupWise 2012 Installation Guide.

DB1C Invalid object name

Source: GroupWise engine; administration engine.
Explanation: Invalid object.
Possible Cause: An invalid object name was specified for an administrator, group name, or other object.
Action: Make sure the specified object ID is correct.

DB1D Cannot delete post office

Source: GroupWise engine; administration engine.
Explanation: Error deleting post office.
Possible Cause: You do not have sufficient rights to perform the operation.
Action: Make sure you have rights to delete files and directories by checking rights for file and directory removal.
Possible Cause: The post office directory or files in that directory are in use by another user.
Action: Check the open/lock activity on files.

DB1F Cannot delete current domain

Source: GroupWise engine; administration engine.
Explanation: Error deleting current domain.
Possible Cause: The attempt to delete the current domain failed.
Action: Connect to the primary domain. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide. Then delete the secondary domain from the primary domain. See Deleting a Domain in Domains in the GroupWise 2012 Administration Guide.
Action: If the current domain is the primary domain, you cannot delete it unless you delete all secondary domains first (meaning that you want to delete your entire GroupWise system) or you designate a different domain as the primary domain. See Converting a Secondary Domain to a Primary Domain in Domains in the GroupWise 2012 Administration Guide.