Source: GroupWise engine; database services.
Explanation: The integrity of an item or structure in the database has been compromised.
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.
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 6.5 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 6.5 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 GroupWise Remote, there might be a problem with the structure or content of the Remote mailbox. For example, copying a GroupWise Remote 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 GroupWise Remote on the remote computer. See the platform-specific setup instructions for GroupWise Remote in"Setting Up GroupWise Modes and Accounts" in "Client" in the GroupWise 6.5 Administration 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: 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 the database cannot be repaired, you must restore it from backup. See "Restoring GroupWise Databases from Backup" in "Databases" in the GroupWise 6.5 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" in the GroupWise 6.5 Administration Guide.
Possible Cause: If users are accessing a post office on a NetWare server through a Windows workstation using the Microsoft Gateway for NetWare, the gateway might not be providing adequate support for the number of users trying to access the post office.
Action: The Gateway Service for NetWare is not intended as a full service router for NetWare services. Use a more robust connection to the post office.
Action: Make sure you have all the latest NetWare patches installed. If using the Novell IPXTM/IP gateway, make sure you have the latest version.