Groupwise Error 8200
Site Leaders Articles Blogs What's New? FAQ Advanced Search Forum PRODUCT RELATED DISCUSSIONS COLLABORATION GroupWise GroupWise 2012 GW2012: Clients GroupWise error 8200 Cannot access post office files You can view the discussions, but you must login before you can post. Click the LOGIN link in the forum header to proceed. To start viewing messages, select the forum that you want to visit from the selection below. If this is your first visit, be sure to check out the FAQ by clicking the link above. Results 1 to 8 of 8 Thread: GroupWise error 8200 Cannot access post office files Thread Tools Show Printable Version Subscribe to this Thread… Display Switch to Linear Mode Switch to Hybrid Mode Threaded Mode Threaded View 22-Jan-2015,09:04 AM #1 Floh04 View Profile View Forum Posts Private Message View Blog Entries View Articles New or Quiet Member Join Date Jan 2015 Posts 4 GroupWise error 8200 Cannot access post office files Hello, we've got some users where sporadically within the GroupWise client (Client Version 8 oder 2012 with and without caching mode, System is on GW 2012SP1) the error message 'GroupWise error 8200' - 'Cannot access post office files' pops-up. Recreating a new GW-Database, Re-Installing a new client, GWCheck, checking the network does not help. Did someone have a suggestion, idea for this problem? Thanks, F.A. Reply With Quote « Previous Thread | Next Thread » Bookmarks Bookmarks Twitter Facebook Google Digg del.icio.us StumbleUpon Posting Permissions You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is Off [VIDEO] code is Off HTML code is Off Forum Rules Contact Us Micro Focus Discussion Forums Archive Privacy Statement Terms of Service Top All times are GMT +1. The time now is 09:51 AM. © 2016 Micro Focus
Favorite Rating: GroupWise Error [8200] when accessing a shared folderThis document (7000796) is provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 6.5 Situation When User A shares a folder with User B and the administrator then disables the GroupWise account for User A, User B will no longer be able to access information in the shared folder. Instead, "GroupWise Error [8200]" is displayed whenever the shared folder is highlighted. At the same time, the Post Office Agent for User B's post office will display GroupWise Error [8200] when accessing a shared folder Error: User Database is temporarily disabled [D714] User: Xxxx Note that this error https://forums.novell.com/showthread.php/481466-GroupWise-error-8200-Cannot-access-post-office-files will be displayed at the post office of the user trying to access the shared folder and not the post office to which the owner of the folder belongs. Furthermore, using the above-mentioned example, when User B views the properties of the shared folder and selects the Sharing Tab, User B will appear to be the owner of the shared folder. Resolution This problem can be resolved by re-enabling the account of the shared folder owner. https://www.novell.com/support/kb/doc.php?id=7000796 Other users in the Share List will then be able to access the folder again and will reflect the correct ownership and membership of the list. Please note: This does not affect GroupWise 7. Shared folders will continue to function even after the owner has been disabled. This does however make it more difficult to establish whether or not a user owns any shared folders before being deleted. An enhancement request has been raised to consider adding a way to establish if a user has shared any folders or address books in preperation for the account to be deleted. Additional Information Steps to duplicate: 1) User A: Share a Folder in GroupWise with User B. 2) Log into the account for User B, accept the shared folder and close the GroupWise client. 3) In ConsoleOne, view the properties of User A, select GroupWise Account and check "Disable Logins"4) Once the administrative change has been synchronised, log into the account for User B again. 5) Highlight the shared folder and observe the [8200] error 6) View the properties of the shared folder and observe that User B is listed as "Accepted" and "Owner"7) On the Post Office Agent, observe the [D714] error implicating User A. (even if User A exists on a different Post Office) This is working as designed.Formerly known as TID# 10091608 DisclaimerThis Support
frÄn GoogleLogga inDolda fÀltSök efter grupper eller meddelanden
says: "The database facilityreported error [8200] on msg5.db"And when I turn on verbose logging I can get a different error also:"Error: Generic file I/O error [8200]"The msg5.db is 2Gb and standalone GWcheck will not rebuild it or perform aRecover.All message databases on this PO are in the 1.7-2Gb range, other POs havemessage databases up to 0.5Gb.There are no tape backups of (uncorrupt/smaller?) message DBs Mark Haynes 2005-09-28 16:57:59 UTC PermalinkRaw Message I just have to say this..OMG. Those are monster dbs. Have you tried a gwcheck Structure&Index from C1? Is it maybe corruption problem with a shared folder from a GW client? Error: 8200 "GroupWise cannot open the post office files" - TID10016457?Mark Anthony Hilton 2005-09-29 13:17:20 UTC PermalinkRaw Message I tried the Structure and Index check, using stand-alone GWCheck, against on of the 2Gb databases and got an error IO SEEK ERR 0x8207 and no work done.Against the smallest DB on this PO it took 90 mins to reduce it from 1,694,252Kb to 1,693,980KbWe are currently running Expire/Reduce against all mailboxes on the PO to remove anything over 3 years old (using the stand alone GWCheck). Hoping we lose less than by deleting whole dbs.We also need to find out why the dbs on this one PO are so much bigger than any of our other 17 POs - it isn't our biggest in terms of number of users.AnthonyI just have to say this..OMG. Those are monster dbs. Have you tried a gwcheck Structure&Index from C1? Is it maybe corruption problem with a shared folder from a GW client? Error: 8200 "GroupWise cannot open the post office files" - TID10016457?Mark Michael Bell 2005-09-28 17:55:07 UTC PermalinkRaw Message Indeed this may be a corruption issue. In which case without good backupsyour only option isa) open incident with novellorb) unload poa, delete each msg file ,run standalone gwcheck, structuralrebuild, username=filenameofmsgdb. This will drop it from the store andallow recreation (all data lost)--Michael J. BellNovell Support Connection Volunteer SysopAuthor of Guinevere (http://www.openhandhome.com)PLEASE: Do not e-mail me privately unless specifically asked.I'm a volunteer, not a Novell employee!All opinions and advice provided are MINE alone and NOT Novell's unlessspecifically identified as such.Novell does not officially monitor these forums.Enhancement requests for all Novell products may be made athttp://support.novell.com/enhancement"You've got a way to keep me on your side/You give me causefor love that I can't hide/For you I know I'd even try toturn the tide/Because