Source:
GroupWise engine; database services.
Explanation:
Attempted operation after critical error; transaction aborted.
Possible Cause:
If this error occurs during domain-related activities, such as adding users or synchronizing domains, the domain database has been damaged.
Source:
GroupWise engine; database services.
C057 Database maintenance in progress; please exit
Source:
GroupWise engine; database services.
Explanation:
Maintenance in progress error.
Possible Cause:
Database maintenance in progress (one of the databases is being recovered or rebuilt).
Action:
Exit GroupWise and try again later. Depending on the size of the database, the maintenance could take from a few seconds to several minutes.
Possible Cause:
If the condition continues for an extended period and no GroupWise maintenance is being performed, another program might already have the required file open with exclusive access.
Action:
Check the open/lock activity on GroupWise databases and other files. You might find that a backup program is holding the file open.
Possible Cause:
If this error occurs constantly from the POA, a damaged message file might be blocking its processing.
C059 Database file already exists
Source:
GroupWise engine; database services.
Explanation:
GroupWise attempted to create a user file, message file, or library file, but it could not create the file because the file already existed.
Possible Cause:
The ngwguard.db file has been renamed or deleted. When the POA detects the guardian database is missing, it creates a new one. The original guardian database contained a catalog of dependent databases (user, messages, library, and so on). The new guardian database lacks this catalog, so the POA attempts to create the needed dependent databases, but it cannot because they already exist. The POA does not overwrite existing files. See also Information Stored in the Post Office
in Post Office Agent
in the GroupWise 8 Administration Guide.
Action:
Restore the original ngwguard.db file from backup. If the original guardian database is not available, seek assistance. For technical services, see Novell Support.
Possible Cause:
A user was moved to a different post office and then moved back to the original post office. When the user is moved back to the original post office, the POA attempts to create the user database. If the user database was not deleted when the user was moved out, the POA cannot create the new user database.
C05D Cannot open database file
Source:
GroupWise engine; database services.
Explanation:
Store file not found.
Possible Cause:
GroupWise 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 (msgnnn.db) to which the users belong might be missing.
Possible Cause:
If the message occurs for only a single user, that user’s user database (userxxx.db) might be missing.
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.
Possible Cause:
If this message occurs in the GroupWise client in Remote mode, 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.
Source:
GroupWise engine; database services.