7.22 DB3x 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.

DB30 Gateway directory not found

Source: GroupWise engine; administration engine.
Explanation: Gateway directory does not exist.
Action: Check the specified gateway directory path and make sure the requested gateway is installed. For a list of gateways, see GroupWise Gateways.

DB31 Required field missing or empty

Source: GroupWise engine; administration engine.
Explanation: A required field is missing or empty.
Action: Provide a value for the required field(s).

DB32 Required field missing

Source: GroupWise engine; administration engine.
Explanation: A required field is missing.
Action: Check the record for a missing required field.

DB33 Cannot open all post offices

Source: GroupWise engine; administration engine.
Explanation: Unable to open all post offices.
Possible Cause: There are more post offices defined than the operating system file handles allow.
Action: All directory synchronized commands will be performed through the MTA for the closed post offices.
Possible Cause: The link to the post office has been lost.
Action: Reestablish the link to the post office. See Strategies for Message Delivery Problems in GroupWise 2012 Troubleshooting 2: Solutions to Common Problems.

DB34 Time zone definition not found

Source: GroupWise engine; administration engine.
Explanation: No time zone defined.
Possible Cause: Unable to find a time zone definition for the current domain or post office.
Action: Select a time zone in the Identification page for the current domain or post office in ConsoleOne. See Time Zones in System in the GroupWise 2012 Administration Guide

DB35 No pending operation for record

Source: GroupWise engine; administration engine.
Explanation: No pending operation for record.
Possible Cause: The pending operation has been completed.
Action: Refresh the list of pending operations. See Pending Operations in System in the GroupWise 2012 Administration Guide.

DB37 Cannot delete current domain

Source: GroupWise engine; administration engine.
Explanation: Cannot delete the current domain.
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.

DB38 Cannot delete domain that has post offices

Source: GroupWise engine; administration engine.
Explanation: Post offices exist for this domain.
Possible Cause: An attempt was made to delete a domain that has post offices assigned to it.
Action: Move the post offices to another domain. See Moving a Post Office in Post Offices in the GroupWise 2012 Administration Guide. Then delete the domain after it is empty. See Deleting a Domain in Domains in the GroupWise 2012 Administration Guide.
Action: Delete the post offices. See Deleting a Post Office in Post Offices in the GroupWise 2012 Administration Guide. Then delete the domain after it is empty. See Deleting a Domain in Domains in the GroupWise 2012 Administration Guide.

DB39 Domain database not found

Source: GroupWise engine; administration engine.
Explanation: Database is not available. No domain database (wpdomain.db) was found; however, a recover.ddb file was found.
Possible Cause: The database is currently being rebuilt.
Action: Allow the rebuild operation to finish.
Possible Cause: A database rebuild failed.
Action: Rename recover.ddb to wpdomain.db in the domain directory, then rerun the rebuild. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

DB3A Cannot delete domain that has links

Source: GroupWise engine; administration engine.
Explanation: Domain has indirect links.
Possible Cause: Cannot delete the domain because it is used in indirect routing.
Action: Reconfigure domain links before deleting the domain. See Editing a Domain Link in Domains in the GroupWise 2012 Administration Guide.

DB3B Remote management message sent

Source: GroupWise engine; administration engine.
Explanation: Remote management message sent.
Action: None. This is not an error. It is a notification by the program that the operation to be performed has been sent to the parent domain.

DB3C Domain database in use

Source: GroupWise engine; administration engine.
Explanation: Exclusive open error.
Possible Cause: An exclusive open for a domain to be merged or released failed because the domain is already in use.
Action: Have all administrators exit the domain database (wpdomain.db) before running the merge or release.
Action: Stop the MTA in the domain to be merged or released.

DB3D Database sorting language changed

Source: GroupWise engine; administration engine.
Explanation: Database language has changed.
Action: Rebuild the database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

DB3F Cannot delete required field

Source: GroupWise engine; administration engine.
Explanation: Cannot remove a required field.
Action: You must supply valid data for all required fields.