6.5 C04x 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.

C040 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C042 Database being modified

Source: GroupWise engine; database services.
Explanation: Read consistent view of record not available.
Possible Cause: A read operation encountered data that was being modified by another concurrent program. The read operation needs to see a prior version of the data; however, no prior version is available. This error should be handled by the GroupWise engine in most cases. If it finally does come through to the end user, it might indicate there is a problem with the database. However, it might also indicate the update activity on the database is currently very high.
Action: Generally, the error is transitory and goes away when the operation is retried. Make sure that others are not doing updates to the database, and retry the action. If the problem persists, validate and rebuild the database as necessary. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If this error occurs on a message or user database, run GWCheck. See Stand-Alone Database Maintenance Programs in the GroupWise 2012 Administration Guide.

C043 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C044 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C045 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C046 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C047 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C048 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C04A Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C04B Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C04C Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C04D Memory error

Source: GroupWise engine; database services.
Action: See C0xx Memory error.

C04E Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C04F Database checksum error

Source: GroupWise engine; database services.
Explanation: Checksum error reading database.
Action: Check and, if necessary, repair the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.

If the error returns, check for bad network cards on workstations from which the GroupWise client updates the databases.

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 guardian database (ngwguard.db) is damaged.
Action: Stop the POA. Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files. Delete the ngwguard.db file, then create a new, empty file named ngwguard.db.

Start the POA. The POA will recognize the invalid ngwguard.db file and rebuild it from the ngwguard.fbk file, merging in transactions from the ngwguard.rfl file.

See also Information Stored in the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide.

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.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Reinstall GroupWise on the remote computer. See the platform-specific setup instructions for using Remote mode in Setting Up GroupWise Client Modes and Accounts in Client in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs in the GroupWise client in the Find Results dialog box, the POA has not indexed the documents yet and might not be running.
Action: Start the POA. Check its indexing cycle. See Regulating Indexing in Optimizing the POA in the GroupWise 2012 Administration Guide.

After the documents have been indexed, the user will be able to use the Find feature in the GroupWise client to access them.