Source: GroupWise engine; database services.
Explanation: GroupWise tried to open a file that could not be recognized as a valid GroupWise 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 6.5 Administration Guide.
Action: If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See "Standalone Database Maintenance Programs" in "Databases" in the GroupWise 6.5 Administration Guide. It can sometimes be helpful to run GWCheck multiple times, because as some errors are fixed, others are uncovered.
Action: If the damaged database cannot be repaired successfully, restore it from backup.
Action: If a damaged user database cannot be repaired or restored, it can be rebuilt. First, archive all personal appointments, tasks, and notes. Make a backup copy of the user database. Then, re-create the user database. See "Re-creating a User Database" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs each time the user exits the GroupWise client, the archive database 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 6.5 Administration Guide.
Action: Run GWCheck on the archive. See "Standalone Database Maintenance Programs" in "Databases" in the GroupWise 6.5 Administration Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .