6.7 C06x Errors

C060 Unexpected error

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

C061 Unexpected error

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

C062 Unexpected error

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

C063 Database error

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

C066 Unexpected error

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

C067 Database error

Source: GroupWise engine; database services.
Explanation: Invalid store number.
Possible Cause: The post office database ( wphost.db ) has been damaged.
Action: Check and, if necessary, repair the database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide .
Possible Cause: If this error occurs when a new user starts the GroupWise client, there might be a problem with the user database ( user xxx.db ).
Action: Perform a structural rebuild on the user. See Performing a Structural Rebuild of a User Database in Databases in the GroupWise 7 Administration Guide .
Action: Reset the client options for that user. See Resetting Client Options to Default Settings in Users in the GroupWise 7 Administration Guide .
Possible Cause: If this error occurs when new users exit GroupWise or try to archive items, the archive might be damaged.
Action: Copy a new ngwguard.dc file from the po subdirectory of the software distribution directory into the post office directory. Delete new users’ archive directories, because they haven’t been able to archive anything yet.

C068 Database error

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

C069 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C06A Database error

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

C06B Database error

Source: GroupWise engine; database services.
Explanation: Server not defined.
Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid.
Action: Check and repair the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 7 Administration Guide .

C06C Database error

Source: GroupWise engine; database services.
Explanation: Driver not found.
Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid.
Action: Check and repair the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 7 Administration Guide .

C06D Database error

Source: GroupWise engine; database services.
Explanation: Bad driver path.
Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid.
Action: Check and repair the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 7 Administration Guide .

C06E Unexpected error

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

C06F Store number mismatch

Source: GroupWise engine; database services.
Explanation: The store number in a database does not match the store number recorded in the store catalog.
Possible Cause: The database is damaged.
Action: Check and, if necessary, repair the database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 7 Administration Guide .
Action: Run GWCheck. See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide .
Possible Cause: The database has been renamed to another valid database name (for example, renaming msg7.db to msg8.db). This circumstance could indicate tampering by a user attempting to access another user’s messages.
Action: Restore the original database. See Restoring GroupWise Databases from Backup in Databases in the GroupWise 7 Administration Guide . For information about databases in the post office, see Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure .