Source: GroupWise engine; file input/output.
Explanation: Access denied. The program tried to access or open a file that did not have or allow sharing. The program might also have tried to create a file that already exists.
Possible Cause: If this error occurs from the POA, the POA might not have access to a required file.
Action: Start the POA including the /rights switch to determine the specific problem the POA is encountering. See "Using POA Startup Switches" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs when creating a post office, you might not be connected to the domain in which you are trying to create the post office.
Action: Connect to the domain where you want the post office located. See "Connecting to a Domain" in "Domains" in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs when users exit the GroupWise client, the users might have their archive directory set to a location where they do not have sufficient rights.
Action: In the GroupWise client, check the users' path to the archive directory. Look up "archive, directory" in GroupWise client Help. Make sure users have sufficient rights to create and modify files there. Or have users change their archive directory to a location where they already have sufficient rights.
Possible Cause: If this error occurs when trying to access the account of a new user, some required files might be missing from the post office directory.
Action: See "Post Office Directory" in "Directory Structure Diagrams" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Make sure all required files are present in the post office directory, especially the *.dc files, which are required for creating new user and message databases. If *.dc files are missing, copy them from another post office or from the po subdirectory of the software distribution directory.
Possible Cause: If this error occurs for a user who has previously been able to access GroupWise successfully, the user's Novell® eDirectoryTM object might have become damaged.
Action: Delete the user object from eDirectory, then recreate it. Do not delete the user's GroupWise account, because this would delete the user's mailbox as well.
Possible Cause: If this error occurs when users exit the GroupWise client, the user database (userxxx.db) might be damaged.
Action: Check and, if necessary, repair the user database. See "Maintaining User/Resource and Message Databases" in "Databases" in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See "Standalone Database Maintenance Programs" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: The GroupWise databases might be owned by an invalid user.
Action: For the locations of GroupWise databases in domains and post offices, see "Domain Directory" and "Post Office Directory" in "Directory Structure Diagrams" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
Possible Cause: 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 or virus scanner is holding the file open.
Possible Cause: The GroupWise client has been installed on the local drive, so the program can still run, but the network connection to the post office has been lost.
Action: When the network connection to the post office is reestablished the GroupWise client will function normally again. Reboot the machine. If the post office still cannot be accessed, resolve those network problems.
Action: Record 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 .