Groupwise 7 Error 8201

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 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 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 l

amongst my new client shops. 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 error pop up from time to time and you know it has multiple possible causes. However, none of the TIDs that I've come across seem to have the particular issue I've been running into noted. Good news is I have a work around. First though, you'll need some background info. All of our archive locations are locked by default. Default archive locations for this environment are to the users home drives. GroupWise version on the backend is 8.01 HP2, client is at 7.03 or higher up to 8.0.2. Home drives are http://www.novell.com/documentation/gw65/gw65_tsh1/data/hxnjs40x.html on an OES2 SP2 - Linux server The server is virtualized on VMWare's VSphere (was ESXi to begin with) The symptoms are usually experienced by a new archive user, but not always. What happens is the user goes to Open Archive within the GroupWise client and they immediately get an 8201 error. For some users it moves from an 8201 error to an 8209 error after several unsuccessful attempts to get at the archive. This occurs for PC users only, our Mac users don't http://wmnug-mary.blogspot.com/2011/01/8201-error-on-archive-location-in.html get to archive unless it's to their local drive and they have to agree to be responsible for the backup of the archive. Here's the workaround: Unlock the archive location for the given user (use ConsoelOne, right click on the user, select Client Options, pick the File Locations tab) If there is an existing archive, copy that folder to the user's local drive. I generally use c:\grpwise\archive to keep within the 8.3 file format. Close the GroupWise client. Open the GroupWise client and change the File Location (Tools | Options) to the new spot on the local drive. Have the user select Open Archive. Go back to the mailbox. Archive a message that is "ok" to potentially lose (only had this happen once, but it's a caveat you'll want to be aware of) Open Archive and verify the message is there. Close the GroupWise client. Copy the archive from the local drive back up to the server, and lock the archive location again (if you want). Open the GroupWise client, verify that the File Location is pointing back to the original location. Open Archive, verify that they can see at least the message that was just archived. This has worked for everyone reporting the issue here. Hopefully it will work for everyone else as well. Posted by "The" Mary at 2:01 PM No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Mary's Favorites Bliss Point Danita's site GroupLink -

GROUPWISE [Download message RAW] Hi, Thank you for your input as this resolved the problem. There was http://marc.info/?l=ngw&m=119237980885304 an entry for a different user in the remote path. Once again Thank you >>> harvpa@wwc.edu 29/04/2004 01:47:40 >>> Does she have the same problems on a different computer? If not, then it isn't her account, but something with the computer. I haven't seen this error in a long time, but it used to be caused groupwise 7 by an incorrect (hence the 8201 error) path to remote database being stored in the registery. Just delete "HKCU\Software\Novell\GroupWise\Login Parameters\Path to Remote Database". If that isn't there, you might try uninstalling the GW client, then delete the HKCU\Software\Novell\GroupWise key to make sure the custom settings are gone. -- Paul Harvey harvpa@wwc.edu Network Engineer Walla Walla College >>> groupwise 7 error Rtisdell@sl.nsw.gov.au 4/27/2004 11:14:49 PM >>> ** High Priority ** Hi, The user is on Windows 2000, GW6.5 and when she opens the GroupWise client is unable to do anything until this error message pops up: Access to file has been denied. Please note the error code in the title. I have checked the documentation and can not really see anything that is relevant other than if this error occurs for a user who has preciously been able to access GroupWise successfully, the user's Novell eDirectory object might have become damaged. I have logged in using their login on XP and do not have the problem. I have run a mailbox analyze/fix and structural rebuild. Any assistance would be appreciated. ///Please note/// This email and any attachments to it are privileged and confidential. If you are not the intended recipient, please notify the sender and delete it. The contents of this email are not given or endorsed by the State Library of New South Wales unless otherwise indicated

be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 17 Oct 2016 10:38:30 GMT by s_wx1131 (squid/3.5.20)