Using the Error Classes If you know what each error class means, you will still be missing an important piece of the puzzle. Look up “archive, directory” in GroupWise client Help. Possible Cause: The password entered by the user does not match the one stored in the encrypted file. Action: Check the ownership of these databases and make sure that owner does not have disk space restrictions. weblink
Click GroupWise > Post Offices. Make sure the post office you are trying to rebuild and the domain it belongs to contain the correct files (especially *.dc files). See Maintaining Library Databases and Documents in Databases in the GroupWise 2012 Administration Guide. In most cases, the exact set of conditions you are seeing has already been documented by Novell Technical Services, and one or more ready-made solutions await you. http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/hvryhoeh.html
Action: If documents are being stored at the post office, make sure the docs subdirectory exists for the library. Action: Run GWCheck on the archive. Explanation: The POA cannot access a required file.
Action: Enter a valid file name. 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. Explanation: File lock error. These codes map to certain kinds of problems.
The only way you can know which component has the problem is to apply some of the architectural information available in the rest of the book. Explanation: Generic file I/O error. This method is helpful for looking up messages one at a time, as you encounter them. http://www.novell.com/support/kb/doc.php?id=3864678 Action: In the GroupWise client, verify that the path to the archive directory exists and that you have sufficient rights to create and modify files.
Action: Make sure no users associated with the database to be rebuilt are currently running the GroupWise client. Action: Check the ownership of the GroupWise databases. Check the open/lock activity on the GroupWise program files. Possible Cause: A directory required for the normal flow of GroupWise messages might be missing.
Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner. http://www.novell.com/documentation//nwec/nwec/data/hfrsevmn.html Suppose the client reports an error, but the POA does not. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. You can copy ngwguard.dc from your Software directory/po directory.
Action: Verify that the list of post offices belonging to the domain is correct. have a peek at these guys Action: Check destination file name specified and ensure it is unique. Action: In the GroupWise client, verify the path to the archive directory exists and the user has sufficient rights to create and modify files there. If the document is needed, you can restore the BLOB file from backup.
Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files. See Tools for Analyzing and Correcting GroupWise Client Problems in Client in the GroupWise 2012 Administration Guide. Pages Home About Me BrainShare Tips & Tricks Monday, January 10, 2011 8201 Error on Archive location in GroupWise 8.x If you've used GroupWise long at all you've probably seen this http://glitchtest.org/groupwise-error/groupwise-error-8209-archive.html This means that one or more store files are not correctly registered in the GroupWise guardian database.
Action: Verify that the file is not currently locked by another process that has terminated. Action: Check the user’s rights to the archive location. Action: You can determine what BLOB file the document was in from the GroupWise client.