6.1 C00x 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.

C003 Invalid object name has been passed in

Source: Internet Agent Installation program or WebAccess Installation program on Linux
Explanation: The Installation program cannot create an Agent object with the name you specified.
Possible Cause: You did not specify the object name in the correct format.
Action: Use the following format:

cn=user_name,ou=organizational_unit,o=organization

Possible Cause: An object by the name you specified already exists.
Action: Specify a different object name.

C005 Invalid container has been selected for the GW objects

Source: Internet Agent Installation program or WebAccess Installation program on Linux
Explanation: The Installation program cannot create an Agent object in the context you specified.
Possible Cause: The container object you specified was not a GroupWise Domain object, an Organizational Unit object, or an Organization object.
Action: Specify an appropriate container for the Agent object.

C006 Record, key, or key reference not found

Source: GroupWise engine; database services.
Explanation: A record or key was not found.
Possible Cause: In the GroupWise client, the user dragged away all the column headings.
Action: Restore the column headings. Right-click the bar where the column headings belong, then select the column headings such as From, Subject, and Date, from the drop-down list.
Possible Cause: If this error occurs when creating a post office, you might not be connected to the correct domain.
Action: If you try to create a post office in a secondary domain while connected to a different domain, you might not have sufficient rights to create the post office correctly. It might show up in the GroupWise View but not have a Novell eDirectory object created for it. Connect to the secondary domain. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide. Then graft the post office into the correct domain. See GW / eDirectory Association in System in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs when deleting a Library object representing a remote document storage area, the remote document storage area and its directory might have already been deleted.
Action: In ConsoleOne, display the GroupWise View. Right-click the Library object, then click Properties. Remove the path to the document storage area that no longer exists. Select Store Documents in Post Office, then click OK. Then delete the library object from the GroupWise View.

C007 Database error

Source: GroupWise engine; database services.

C008 Database error

Source: GroupWise engine; database services.

C009 Database error

Source: GroupWise engine; database services.

C00A Database error

Source: GroupWise engine; database services.

C00B Database error

Source: GroupWise engine; database services.

C00C Field type mismatch

Source: GroupWise engine; database services.
Explanation: Invalid field type in record being added.
Possible Cause: If this error occurs when rebuilding a database, you might not be connected to the correct GroupWise system.
Action: Connect to the GroupWise system where the database is located. See Select Domain in System in the GroupWise 2012 Administration Guide. Then perform the rebuild again.

C00D Database error

Source: GroupWise engine; database services.

C00E Invalid index number

Source: GroupWise engine; database services.
Explanation: Invalid index number.
Possible Cause: When converting a post office from 5.x to 6.x, the post office database (wphost.db) was missing in the post office.
Action: Restore the wphost.db file to the post office. Although the conversion does not actually use the old wphost.db file, it does attempt to access a file by that name in order to rename it.

C00F Invalid password

Source: GroupWise engine; database services.
Explanation: Invalid password specified on database open.
Possible Cause: If this error occurs when a user has been moved to a different post office, the update to the post office database might not have completed.
Action: Move the user back to the original post office. Verify the user’s password. Make sure the agents are running. Repeat the move user procedure. See Moving GroupWise Accounts in Users in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs when rebuilding a database, you might not be connected to the correct GroupWise system.
Action: Connect to the GroupWise system where the database is located. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide. Then perform the rebuild again.
Possible Cause: The password information in the user database (userxxx.db) has been damaged.
Action: Check and, if necessary, repair the database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs in the GroupWise client when accessing archived messages, the archive might be damaged.
Action: In the GroupWise client, open the archive, then use the Repair Mailbox feature to repair the archive. See Enabling GroupWise Check in the Windows Client in Client in the GroupWise 2012 Administration Guide.
Action: Run GWCheck on the user’s archive. See Stand-Alone Database Maintenance Programs in Databases in the GroupWise 2012 Administration Guide.