7.24 DB5x 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.

DB51 Required network address information is missing

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of insufficient configuration information.
Possible Cause: An agent has not been properly configured with an IP address or TCP port.
Action: The POA is not properly configured. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.
Action: The MTA is not properly configured. See Changing the Link Protocol between Domains in Message Transfer Agent in the GroupWise 2012 Administration Guide.
Action: The GWIA is not properly configured. In ConsoleOne, browse to and right-click the GWIA object, then click Properties. Click Post Office Links, then correct the link information as needed. See Internet Agent in the GroupWise 2012 Administration Guide.

DB52 Required path information is missing

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of insufficient configuration information.
Possible Cause: A domain or post office has not been properly configured with the path to the directory where the domain or post office is located.
Action: Check the UNC path information provided for the domain or post offices. See Editing Domain Properties in Domains or Editing Post Office Properties in Post Offices in the GroupWise 2012 Administration Guide.

DB53 No message transfer POA has been selected

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of insufficient configuration information.
Possible Cause: A post office has been configured with a TCP/IP link to its domain, but no POA has been selected to provide the link to the MTA.
Action: Configure the link between the POA and the MTA. See Editing a Post Office Link in Domains in the GroupWise 2012 Administration Guide.

DB55 No POA is available for client/server

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of incorrect configuration.
Possible Cause: A post office has been configured for client/server access mode, but no POA has been configured for client/server processing.
Action: Configure a POA for client/server mode. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.

DB56 Specified e-mail address conflicts with the address of an existing gateway alias

Source: GroupWise engine; administration engine.
Possible Cause: You are creating or modifying a gateway alias in such a way that its new name conflicts with an existing gateway alias.
Action: Choose a different name for the new gateway alias. Check for existing names first. See Email Address Lookup in System in the GroupWise 2012 Administration Guide.

DB57 Specified e-mail address conflicts with the address of an existing user

Source: GroupWise engine; administration engine.
Possible Cause: You are creating, modifying, or moving a user in such a way that its new name conflicts with an existing user name.
Action: Choose a different name for the new user. Check for existing names first. See Email Address Lookup in System in the GroupWise 2012 Administration Guide.

DB58 Specified e-mail address conflicts with an address from a post office alias record

Source: GroupWise engine; administration engine.
Possible Cause: You are creating or modifying a post office alias in such a way that its new name conflicts with an existing post office alias.
Action: Choose a different name for the new post office alias. Check for existing names first. See Email Address Lookup in System in the GroupWise 2012 Administration Guide.

DB59 This GroupWise administration version is older than the minimum allowed by the system administrator

Source: GroupWise engine; administration engine.
Explanation: Although you can start ConsoleOne, the GroupWise snap-ins are out of date.
Possible Cause: In ConsoleOne, the Lock Out Older GroupWise Administration Snapins option has been selected under Tools > GroupWise System Operations > System Preferences > Admin Lockout Settings and you are trying to run ConsoleOne with a version of the snap-ins that is too old.
Action: Update the GroupWise snap-ins. See ConsoleOne in Installing a Basic GroupWise System in the GroupWise 2012 Installation Guide.

DB5A The LDAP server is being used for eDirectory synchronization

Source: GroupWise engine; administration engine.
Explanation: An MTA that performs eDirectory user synchronization obtains its eDirectory information from a server that is also being used in your GroupWise system as an LDAP server.
Possible Cause: You are trying to delete an LDAP server that is being used for eDirectory user synchronization as well as for LDAP.
Action: Reconfigure eDirectory synchronization. See Using eDirectory User Synchronization in Message Transfer Agent in the GroupWise 2012 Administration Guide. Then delete the LDAP server.

DB5B The signature information is too large

Source: GroupWise engine; administration engine.
Explanation: ConsoleOne cannot save the global signature you have created because it exceeds 2.43 MB.
Possible Cause: You have tried to create a global signature that is larger than 2.43 MB.
Action: Remove some text or objects from the global signature.

DB5C The software area is being referenced

Source: GroupWise engine; administration engine.
Explanation: The software distribution area is still in use by one or more post offices.
Possible Cause: You are trying to delete a software distribution area that is still in use.
Action: Configure the post offices to use other software distribution directories. In ConsoleOne, display the Post Office Settings property page of each Post Office object, then select a different software distribution directory. When no post offices reference the software distribution directory, it can be deleted.

DB5D Following a database rebuild the ownership of the target file has been changed. The file uid.run must be deleted manually.

Source: GroupWise engine; administration engine.
Explanation: After it rebuilds a domain or post office database, ConsoleOne tries to delete the uid.run file that specifies the user that the agent runs as, so that user information can be reestablished from the uid.conf file.
Possible Cause: ConsoleOne was unable to delete the uid.run file.
Action: Delete the uid.run file from the domain or post office directory. The agent generates a new one based on the uid.conf file when it starts running against the rebuilt database.

DB5E Invalid preferred EMail ID

Source: GroupWise engine; administration engine.
Explanation: The preferred email ID allows you to customize users’ email addresses, but it must consist of valid characters.
Possible Cause: You have included a character in the preferred email ID for a user that is not RFC compliant.
Action: Use only the following characters in the preferred email ID:
  • Numbers 0-9
  • Uppercase letters A-Z
  • Lowercase letters a-z
  • Plus sign +
  • Hyphen -
  • Underscore _
  • Tilde ~

DB5F Incompatible visibility

Source: GroupWise engine; administration engine.
Explanation: You have assigned an administrative user to a distribution list under conditions where the user cannot see the distribution list.
Possible Cause: The distribution list has limited visibility in the selected administrative user’s post office.
Action: Adjust the visibility for the distribution list. For information about distribution list visibility, see Creating a New Distribution List in Distribution Lists, Groups, and Organizational Roles in the GroupWise 2012 Administration Guide.
Action: Select a distribution list administrative user in a post office where the distribution list is visible. See Enabling Users to Modify a Distribution List in Distribution Lists, Groups, and Organizational Roles in the GroupWise 2012 Administration Guide