Groupwise Error 8209 Archive
column headings. Right-click the bar where the column headings belongselect some column headings such as From, Subject, Date, etc., from the drop-down list. Possible Cause:If this error occurs when creating a post office, you might not be connected to the correct domain. Action:If you try to create a post office in a secondary domain while connected to a different domain, you might not have sufficient rights to create the post office correctly. It might show up in the GroupWise View but not have an Novell eDirectoryTM object created for it. Connect to the secondary domain. See "Connecting to a Domain" in "Domains" in the GroupWise 6.5 Administration Guide. Then graft the post office into the correct domain. See "GW / eDirectory Association" in "System" in the GroupWise 6.5 Administration Guide. Possible Cause:If this error occurs when deleting a Library object representing a remote document storage area, the remote document storage area and its directory might have already been deleted. Action:In ConsoleOne, display the GroupWise View. Right-click the Library object, then click Properties. Remove the path to the document storage area that no longer exists. Select Store Documents in Post Office, thenclick OK. Then delete the library object from the GroupWise View. 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 .
differential backup. After logging into a newly restored mailbox, I received a Path not Found [8209] error when attempting http://thebackroomtech.com/2009/03/25/fix-8209-error-when-attempting-to-create-an-archive-from-a-restored-groupwise-post-office-mailbox/ to create an archive from within the Groupwise client. The reason for the 8209 error ended up being that the daily differential backup did not capture http://wmnug-mary.blogspot.com/2011/01/8201-error-on-archive-location-in.html the ngwguard.dc file located in the root of the post office directory. Once I copied this file from the live post office to the restore location, groupwise error I was able the create the archive. I also could have copied the file from the po directory in the Groupwise software distribution directory. For additional details, see Novell TID 10052390 Related PostsFix for ConsoleOne.exe error – The procedure entry point WpSUDataLength could not be located in the dynamic link library gwenv1.dllFix: groupwise error 8209 The Novell Groupwise Address Book is the only address book shown when adding users to personal group distribution listsFIX: Faulting application gwpoa.exe, version 7.0.3.1068, faulting module gwwww1a.dllFix for path not found (8209) when loading Groupwise POAGroupwise GWcheck Error: Mailbox/library maintenance can not be executed because a duplicate request is running March 25th, 2009 by Aseem Kishore File in: Groupwise There are 0 comments, care to add yours? Tweet Like Google+ Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Tagsbackup BES Blackberry Blackberry Enterprise Server ConsoleOne Dell DNS edirectory exchange firefox firewall fix Group Policy Groupwise GWIA howto IE7 IIS Internet Explorer McAfee Netware NIC Novell password patch RDP registry Remote Desktop script security Server Core Sles SQL suse troubleshooting utilities Vista VMware Vulnerability Webaccess Windows Windows 2003 Windows 2008 Windows XP XP SP3 Categories Active Directory backup best practices Blackberry browser add-ons Ci
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 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 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