Groupwise Error 8209 Restore Backup
Favorite Rating: GroupWise Client Error: 8209 trying to restore messages from backup.This document (3864678) is provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 6.5Novell GroupWise 7.0 Situation GroupWise Client Error: 8209 trying to restore messages from backup.POA Error: 8200 trying to restore messages from backup.Error: D069Error: 8200Error: 8209 Resolution POA object did not have File System Rights to the post office backup directory structure. Assign the POA object , RWCEMF rights.Assigning Rights to the POA object has been known to resolve this when the Restore Area is the same server or different server, or different volume. Assigning POA object rights can be done in ConsoleOne highlighting the POA object | Right Click | Properties | Rights to Files & Folders tab | Add. Walk the tree to the Restore and Live area directory structures.NOTE: The restore will also fail with an 8209 error if any portion of the restore area's directory path is longer than 8 characters. For example, if you create a restore area at VOL2:\verylongdirectoryname\restore, the mailbox restore will fail with an 8209 error, but if the path was VOL2:\shortdir\restore, it should work correctly.NOTE: The POA may also require RWCEMF rights to the Live Post Office directory structure as well.It may also be helpful to reference tid 10083858 for additional information on GroupWise restore problems.This is fixed in GroupWise Bonsai. StatusReported to EngineeringAdditional Information There is a bug in versions earlier than GW 6.5.6 that causes 8209 and this bug is more apparent when running Groupwise and restore area on a cluster. This specific cluster issue should be fixed in Groupwise 6.5.6 or later.There is still a scenario with a restore area located on a different server where a user gets 8209 error accessing a backup mailbox. This has also been reported to a development.Formerly known as TID# 10083863 + Novell GroupWise 8: Upgrading your Existing Novell GroupWise Environment DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organ
Favorite Rating: 8209 error when accessing backup mailbox.This document (3044515) is provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 7Novell GroupWise client for Linux Situation 8209 error when accessing backup mailbox from Linux version of GroupWise clientThe path to the file is invalid or the file does not exist. Specify a valid path and file name. Resolution The fix is included in the SP2 of GW7. Additional Information Steps to duplicate:1. Have http://www.novell.com/support/kb/doc.php?id=3864678 a GroupWise system installed on NetWare server.2. Create a restore directory on the same server and copy / restore from backup there any PO directory structure.3. Use ConsoleOne and define new restore area. Use browse button to navigate to a specified restore directory. Copy / paste the same UNC path in Linux path field. Add membership and use user http://www.novell.com/support/kb/doc.php?id=3044515 / pwd startup switches in a POA startup configuration file. Eventually grant POA eDir object file access rights to a restore directory.4. Check accessing a backup mailbox using Windows version of GroupWise client.5. Repeat the same using Linux client version. After File | Open Backup client displays the 8209 error about invalid path. Click on OK. In GroupWise restore path dialog box notice that Linux client adds extra "/" character at the end of the UNC path. Remove it and client will be able to access backup mailbox. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:3044515Creation Date:20-SEP-06Modified Date:27-APR-12NovellGroupWise Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
Support Pack 1 GroupWise 6 client GroupWise agents running on NetWare 5 servers symptom POA/GroupWise client reports 8209 when users try to restore mail Users get 8209 error when http://support.novell.com/docs/Tids/Solutions/10067841.html clicking on Restore Users cannot Restore mail items "GroupWise Error [8209]" Error: D069 " Attempt to open invalid backup location". "The path to the file is invalid or the file does not exist. http://thebackroomtech.com/2008/08/28/fix-for-path-not-found-8209-when-loading-groupwise-poa/ Specify a valid path and filename" Admin cannot restore all mail for one user POA may report "Error processing admin task [E811]" fact Access mode to post office is Client/Server when getting the groupwise error 8209 error 8209 error does not occur if access mode to post office is Direct Problem happens when restoring items from GroupWise client Problems happens when Admin tries to restore all mail from ConsoleOne Happens when Restore Area is on a remote/different server than where POA and post office directory is located. Does not happen if Restore Area is on same box as where the POA and groupwise error 8209 post office directory is located Happens when Restore Area and POA are installed on the cluster fix The ability to restore a full user's mailbox from ConsoleOne with the restore area on a different server has been fixed in GroupWise 6.5 Support Pack 2. Use the NetWare UNC path in the Restore Area Management UNC path not the Cluster path. Customers seeing this problem can go to http://support.novell.com/filefinder/ and search for the most recent Sevice Patch.After applying the agents you will need to grant the POA object rights to the restore area directories (RWCMF). Please make sure the /USER and /PASSWORD switches are remmed/remarked out. If you are using Document Management and the /USER and /PASSWORD switches are used by the POA to connect to a remote storage area just grant the POA object the rights it needs to the document storage area and the /USER and /PASSWORD switches will not be needed.Steps to duplicate:1. Create a test user in GroupWise (UserA)2. Start the GroupWise client as UserA. Either have this users send themselves some messages or have some other users send some mail messages. Open the messages, then delete them and remove them from the Tra
7.0.3 server. I had just migrated the POA named testpo from Netware to SLES manually rather than use the Groupwise Server Migration Utility since I wanted to have a good understanding what had to happen behind the scenes before I tried migrating my live system. The path to \\nw1\vol1\logs\testpo was the POA log file location on the old Netware Groupwise server. I knew that I needed to fix that path, but couldn't find where Groupwise was pulling it from. Things I tried to resolve the problem included: Verified /log path to location reported was not specified in testpo.poa file on the SLES server Verified in ConsoleOne that the POA object for testpo did not have the Netware path in question specified in the Groupwise > Log Settings > Log File Path Deleted and recreated POA object for testpo Deleted testpo.poa file and re-ran Groupwise install from SLES box, specifying post office named testpo and path to testpo database on the SLES server Verified path to old Software Distribution Directory on Netware server was not shown in ConsoleOne > Tools > Groupwise System operations > Software Directory Management Verified path to old restore area on Netware server was not shown in ConsoleOne > Tools > Groupwise System operations > Restore Area Management Used gnome-search-toolto search the entire SLES server for files containing the text \\nw1\vol1\logs\testpo no files containing that text were found on the SLES server The Fix ended up being rebuilding the testpo post office. To do this: ConsoleOne > Tools > Groupwise Utilities > System Maintenance > Rebuild Database Related PostsFix: Groupwise 6.5 won't install on SLES 10 SP2Simple script to backup Groupwise 7 configuration files on SLES LinuxFix: 8209 error when attempting to create an archive from a restored Groupwise post office mailboxFix: Incompatible device specified for device ‘0' when cold migrating VMware gue