6.3 C02x 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.

C020 Database error

Source: GroupWise engine; database services.

C021 Database error

Source: GroupWise engine; database services.

C022 Database damaged

Source: GroupWise engine; database services.
Explanation: The integrity of an item or structure in the database has been compromised.
Action: If this error occurs on a message database (msgnnn.db) or user database (userxxx.db), run GWCheck. See Stand-Alone Database Maintenance Programs in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The ngwguard.db file has been damaged.
Action: Check the size of the ngwguard.rfl file (roll forward log). If it is less than 24 KB, it is considered empty. Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files. Delete the ngwguard.db file, then copy ngwguard.fbk to ngwguard.db. Be sure to copy it; do not rename it. See Information Stored in the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs when administering GroupWise, a domain database (wpdomain.db) or post office database (wphost.db) might be damaged.
Action: Validate and rebuild the domain or post office database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If this error occurs from the POA after you have already rebuilt databases, restart the POA.
Possible Cause: If this error occurs in the GroupWise client in Remote mode, there might be a problem with the structure or content of the Remote mailbox. For example, copying a GroupWise client installation from one laptop to another might introduce this problem.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Reinstall the GroupWise client on the remote computer. See the platform-specific setup instructions for using Remote mode inSetting Up GroupWise Client Modes and Accounts in Client in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs in the GroupWise client when accessing the archive or during auto-archiving, there might be a problem with the structure or content of the archive.
Action: Repair the GroupWise archive, as described in Repairing Your Mailbox in Maintaining GroupWise in the GroupWise 2012 Windows Client User Guide
Possible Cause: The hard disk where the GroupWise databases are stored is damaged.
Action: Scan the hard disk for damage. Correct any problems with the hard disk.
Action: If the database cannot be repaired, you must restore it from backup. See Restoring GroupWise Databases from Backup in Databases in the GroupWise 2012 Administration Guide.
Action: In ConsoleOne, you can set the proper user rights for all users in a post office or for an individual user. See GroupWise User Rights in Security Administration in the GroupWise 2012 Administration Guide.

C023 Database error

Source: GroupWise engine; database services.

C024 Database dictionary damaged

Source: GroupWise engine; database services.
Explanation: Database dictionary compromised.
Possible Cause: The database dictionary (*.dc file) has been damaged.
Action: Make sure the ngwguard.dc file exists in the post office directory. If it does not, copy it from the po subdirectory of your software distribution directory.
Action: If this does not solve the problem, check and repair the database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.

C026 Database error

Source: GroupWise engine; database services.

C027 Database error

Source: GroupWise engine; database services.

C028 Database error

Source: GroupWise engine; database services.

C029 Database version unsupported

Source: GroupWise engine; database services.
Explanation: Unsupported version of database.
Possible Cause: The database was created with an older version of GroupWise and cannot be opened by the current version.

C02A Cannot access database dictionary file

Source: GroupWise engine; database services.
Explanation: Dictionary file access error.
Possible Cause: In the GroupWise client, this error usually indicates there was a file I/O error accessing one of the database dictionary (*.dc) files which are used to create databases.
Action: Check for any problems accessing the disk where the dictionary files reside. To determine the standard locations for the various database dictionary files, see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.
Action: Make sure the ngwguard.dc file exists in the post office directory. If it does not, copy it from the po subdirectory of your software distribution directory.
Action: The network might have gone down, or there might be some other transitory problem with the disk. The problem might go away simply by retrying.

C02B Database error

Source: GroupWise engine; database services.

C02C Database error

Source: GroupWise engine; database services.

C02D Database error

Source: GroupWise engine; database services.

C02E Database error

Source: GroupWise engine; database services.

C02F Database error

Source: GroupWise engine; database services.