7.21 DB2x 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.

DB20 Unexpected error

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

DB21 Database inconsistency detected

Source: GroupWise engine; administration engine.
Explanation: Database invalid or damaged.
Possible Cause: The database is invalid.
Action: Rebuild the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.

DB23 Password incorrect

Source: GroupWise engine; administration engine.
Explanation: Invalid password.
Action: Enter the correct password.

DB24 Invalid link

Source: GroupWise engine; administration engine.
Explanation: A link between domains is invalid.
Action: Select a valid link type and link protocol for the domain link. See Editing a Domain Link in Domains in the GroupWise 2012 Administration Guide.

DB25 Duplicate domain name

Source: GroupWise engine; administration engine.
Explanation: Duplicate domain name.
Possible Cause: The name of the external domain being merged conflicts with the name of an existing local domain. The names of all primary and secondary domains must be unique in both systems when merging systems.
Action: Remove one of the duplicate domains. See Deleting a Domain in Domains in the GroupWise 2012 Administration Guide.

DB26 Secondary domains exist

Source: GroupWise engine; administration engine.
Explanation: Secondary domains exist.
Possible Cause: Multiple local domains were found in an external domain being merged.
Action: Release all secondary domains from the domain to be merged, or release the domain to be merged from its owning primary domain. See Merging GroupWise Systems in the GroupWise 2012 Multi-System Administration Guide.

DB29 Invalid character

Source: GroupWise engine; administration engine.
Explanation: Invalid character.
Possible Cause: Invalid character in a domain, post office, or object name.
Action: Check the contents of the name strings for invalid characters. Do not use any of the following characters in GroupWise object names:
  • Space
  • Period .
  • At-sign @
  • Asterisk (*)
  • Comma ,
  • Colon :
  • Double quote
  • Parentheses ( )
  • Braces { }
  • ASCII characters 0-31

DB2A Invalid name

Source: GroupWise engine; administration engine.
Explanation: Invalid name.
Possible Cause: An invalid or restricted name has been specified.
Action: Enter a valid name.

DB2B Non-unique entry

Source: GroupWise engine; administration engine.
Explanation: Non-unique entry.
Possible Cause: A new entry conflicts with an existing entry in an index that must be unique. This can occur with a user’s network ID.
Action: Check the network ID for uniqueness on the post office where the user will reside.

DB2C Invalid post office database

Source: GroupWise engine; administration engine.
Explanation: Invalid post office database (wphost.db).
Action: Rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

DB2D Platform error

Source: GroupWise engine; administration engine.
Explanation: Wrong platform.
Possible Cause: No valid path could be found for the current platform type.
Action: Enter a path for the current platform.

DB2E Link record not found

Source: GroupWise engine; administration engine.
Explanation: No link record exists.
Possible Cause: No link record has been defined between an external domain to be merged and any local domain.
Action: Define a link record between an external domain to be merged and any local domain. See Merging GroupWise Systems in the GroupWise 2012 Multi-System Administration Guide.

DB2F Correct database type not found

Source: GroupWise engine; administration engine.
Explanation: No database exists.
Possible Cause: Specified database type does not exist in the specified directory.
Action: Check the domain path. In ConsoleOne, browse to and right-click the Domain object, then click Properties.
Action: Check the setting of the --home switch in the MTA startup file.