Source: GroupWise engine; database services.
Explanation: GroupWise attempted to create a user file, message file, or library file, but it could not 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 6.5 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.
Action: Delete the residual user database, then move the user back into the post office. See "Moving GroupWise Accounts" in "Users" in the GroupWise 6.5 Administration Guide.