Home > Groupwise Error > Groupwise Error 8202

Groupwise Error 8202

See Message Transfer/Storage Directories in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure. See the platform-specific setup instructions for GroupWise Remote in the Client Setup Guide. 8204 Disk full SourceGroupWise engine; file input/output. Rename the wpcsout directory in the post office. Check the location to make sure the required library directory structure exists. this contact form

Action(s)Use Browse to find the correct path. Action(s)Make sure the user has the necessary network rights to access the directories or files in the post office. Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS Novell Documentation Action: Check and, if necessary, repair the user database.

Document ID: 10057370 Solution ID: NOVL28176 Creation Date: 02Oct2000 Modified Date: 19Feb2003 NovellGroupware Did this document solve your problem? Action(s)See Post Office Directory in Book 4: Directory Structures. Action(s)Make sure the NGWGUARD.DC file exists in the post office directory. Also make sure the MTA has access to the post office.

Explanation: Bad file handle. Action: Start the POA including the --rights switch to determine the specific problem the POA is encountering. 8211 Cannot rename file Source: GroupWise engine; file input/output. The user may not have rights to the file or directory. If this error occurs when creating a new document in the GroupWise client, the blank template file for the application may be missing.

Possible Cause: If this error occurs for a user who has previously been able to access GroupWise successfully, the user’s Novell eDirectory object might have become damaged. Action: Create space on disk by deleting unwanted or unnecessary files. This re-creates the wpcsout directory structure for the post office. An attempt by the file system to create a unique file failed.

You can reset ownership if needed using the FILER command. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved. 8200 File I/O error Source: GroupWise engine; file input/output. Action: Check and, if necessary, fix the library. See Chapter 3: GroupWise User Rights in the Security Guide.

If the document is not needed, you can delete it from the library to eliminate the error. Look up "archive, directory" in GroupWise client Help. For technical services, see Novell Support Connection Worldwide Sites at http://www.support.novell.com/misc/worldwide.htm. 8201 Access to file denied SourceGroupWise engine; file input/output. Possible Cause: If the error occurs as the user is exiting the GroupWise client, the client might be encountering a problem archiving messages.

If the destination file exists and is read only, this error may occur. weblink You should then be able to create new documents using that application from GroupWise. Reboot the server. Possible Cause(s)If this error occurs from the POA, the POA may not have access to a required file.

Action(s)Make sure the user has the necessary network rights to access the directories or files in the post office. Action: Make sure the ngwguard.dc file exists in the post office directory. Possible Cause(s)If this error occurs when trying to add users to a post office or when trying to rebuild a user database, a required file may be missing from the post navigate here Check the open/lock activity on the GroupWise program files.

To restore the NGWGUARD.DC file if it is missing, copy it from the PO directory in the software distribution directory to the post office directory. See Post Office Directory in Book 4: Directory Structures for the location of this file. Verify the existence, ownership, and rights of the directories involved with message flow (domain, post office, and MTA local).

Explanation: Path too long.

To check the date of the GroupWise client you are using, click Help > About GroupWise. Action: Check the ownership of the GroupWise databases. ExplanationBad file handle. Action(s)Record the conditions under which you encountered the error.

Action(s)Reinstall GroupWise Remote on the remote computer. Action: In the GroupWise client, check the users’ path to the archive directory. Possible Cause(s)If this error occurs when a specific user starts the GroupWise client, that user database (USER.DB) may be damaged. his comment is here Action(s)None.

In ConsoleOne, right-click the Post Office object to display the post office Identification page. See Chapter 3: GroupWise User Rights in the Security Guide.