Source: GroupWise engine; database services.
Explanation: Store file not found.
Possible Cause: Cannot open a file associated with a multi-file database. For example, one of the dependent databases listed in ngwguard.db has been deleted.
Action: Restore the missing database from backup.
Possible Cause: If this error occurs when users send mail, the message database (msgnn.db) to which the users belong might be missing.
Action: If the message database cannot be restored from backup, perform a structural rebuild on the user(s) experiencing the problem. See "Performing a Structural Rebuild of a User Database" in "Databases" in the GroupWise 6.5 Administration Guide. This will create a new, empty message database. Old messages will no longer be available to the affected users.
Possible Cause: If the message occurs for only a single user, that user's user database (userxxx.db) might be missing.
Action: If the user database cannot be restored from backup, re-create the user database. See "Re-creating a User Database" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: A library database is missing.
Action: Library databases must be restored from backup. They cannot be re-created.
Possible Cause: If this message occurs from the POA when starting its indexing cycle, a library directory structure might have been deleted without deleting the library object.
Action: Run GWCheck to perform a structural rebuild on the dmsh.db file in the post office, then verify the library. See "Standalone Database Maintenance Programs" in "Databases" in the GroupWise 6.5 Administration Guide.
Then delete the library. See "Deleting a Library" in "Libraries and Documents" in the GroupWise 6.5 Administration Guide.
Possible Cause: If this message occurs from GroupWise Remote, a database might be missing from the Remote mailbox.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.