Groupwise Error 83 Item Failed To Archive
Favorite Rating: Error 83- Item failed to archiveThis document (7009495) is provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 2012Novell GroupWise 8 Situation While running a Contents check on users or post offices, getting multiple Error 83- Item failed to archive messages.Samples of the message types: Error 83- Item failed to archive - Subject: Re: Budget for next year - From: DAVID WILLIAMS - Date: Oct 10, 2007 - First archive attempt date: Jan 9, 2008 - Number of archive attempts: 9 - Error number on last Archive attempt: 0x8204 Error 83- Item failed to archive - Subject: Re: Today's reverse repo - From: MICHAEL WILLIAMS - Date: Oct 10, 2007 - First archive attempt date: Jan 9, 2008 - Number of archive attempts: 8 - Error number on last Archive attempt: 0xC050 Error 83- Item failed to archive - Subject: TDC error / issue - From: TODD WILLIAMS - Date: Oct 3, 2008 - First archive attempt date: Jan 5, 2009 - Number of archive attempts: 967 - Error number on last Archive attempt: 0xD107Users are able to open the mail or calendar items but are not able manually or automatically archive them. Resolution WARNING: THE FOLLOWING RESOLUTION WILL DELETE MAILGroupWise POA code level minimum must be 7.0.4 or 8.0.2HP2.Run the following options on one or more users before running it against an entire post office.1) Run a standard expire reduce that covers the dates of these items and verify that they are not purged (because of the outstanding archive failure)2) Add the IGNOREARCHIVEFAILURE option on the MISC tab of GWCheck and run the same expire reduce again.3) The new option should allow the items to be purged. Additional Information The most common reasons that the GroupWise items failed to auto-archive is either because the archive disk filled up or there was a disruption in communication to a remote archive store. 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 y
to archive - RESOLVED IN 8.02HP2 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] I opened up an SR for this today to see if there was a server-based option to remove these emails, as they are still in the user's email account, refusing to be archived and refusing to be purged with the system's weekly purging task. We see a number of these during our weekly analyze/fix https://www.novell.com/support/kb/doc.php?id=7009495 task that we have scheduled. Error number on last Archive attempt results in 0xD11B or 0xD107 errors. I posed the question to the tech: Can we (as system administrators) forcibly remove or repair these emails so that they either archive or go away? Some are many years old. YES, in version 8.02 HP2. TID 7009495 will be created http://ngwlist.com/pipermail/ngw/2011-October/160833.html to reflect this. You first run your normal Expire/Reduce GWCHECK as you normally would. You can do it for a user or PO. You then turn around and run the same Expire/Reduce GWCHECK and in the MISC TAB, put in the option: ignorearchivefailure BE SURE TO USE 8.02 HP2's version of GWCHECK against your 8.02 HP2 system. Finally! Please be sure to test this option before you use it against a live system. Paul Caron, CNE, MCSE | Messaging Architect Maine Medical Center | http://www.mmc.org NOMOREcaronp at SPAMmmc.org | 207-662-6666 Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues. P Go Green! Print this email only if necessary. CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the use of the intended recipient(s) only and may contain information that is privileged, confidential, and prohibited from unauthorized disclosure under applicable law. If you are not the intended recipient of this message, any dissemination, distribution, or copying of this message is strictly prohibit
- Item failed to Archive. I have a user with just over 1000 failedarchive items. I was able to stop the http://novell.support.groupwise.6x.agents.narkive.com/8HLmAfj6/error-83-gwcheck-item-failed-to-archive archive items from failing byrunning a rebuild at the client with a new archive. No new auto-archiveitems receive errors. The user does not want any of http://marc.info/?a=119238056400016&r=1&w=2 the old archivemessages, so I was wondering how do I clean up the message DB so thatgwcheck no longer reports these errors.TID # 10094373 states the groupwise error Novell was working on something for this, butthe TID is dated 2004. Any ideas on how to clean up the message db?link to TID # 10094373'Search Results Page' (http://tinyurl.com/2k98tm)Thanks in advance?SD--somedude Michael Bell 2007-07-10 15:02:40 UTC PermalinkRaw Message Nope. Checked with them. The only only way to clean the error is to groupwise error 83 manuallygo through with client and delete them.Post by somedudeHello,Running gwcheck from 6.5.6up2, I am having a problem clearing up Error83 - Item failed to Archive. I have a user with just over 1000 failedarchive items. I was able to stop the archive items from failing byrunning a rebuild at the client with a new archive. No new auto-archiveitems receive errors. The user does not want any of the old archivemessages, so I was wondering how do I clean up the message DB so thatgwcheck no longer reports these errors.TID # 10094373 states the Novell was working on something for this, butthe TID is dated 2004. Any ideas on how to clean up the message db?link to TID # 10094373'Search Results Page' (http://tinyurl.com/2k98tm)Thanks in advance?SD--somedude 1 Reply 40 Views Switch to linear view Disable enhanced parsing Permalink to this page Thread Navigation somedude 2007-07-10 12:38:18 UTC Michael Bell 2007-07-10 15:02:40 UTC about - legalese Loading...
disappearing ngw 2. 2011-12-09 [1] [ngw] [NGW] Archive Location reporting mechanism ngw 3. 2011-12-07 [1] Re: [ngw] GW Notify fails to connect after user renam ngw 4. 2011-11-29 [1] Re: [ngw] First things first ngw 5. 2011-11-18 [1] Re: [ngw] creating a GWIA ngw 6. 2011-11-15 [2] [ngw] How do I remove GroupWise Monitor Agent from S ngw 7. 2011-11-10 [1] Re: [ngw] size limit on msg.db? ngw 8. 2011-11-04 [1] Re: [ngw] OT: Anybody recently migrate from eDirector ngw 9. 2011-10-20 [1] Re: [ngw] Items moved to cabinet keep returning to in ngw 10. 2011-10-11 [1] [ngw] Throttle DBcopy for nightly backups ngw 11. 2011-10-06 [1] [ngw] - Error 83 - Item failed to archive - RESOLVED ngw 12. 2011-09-16 [1] Re: [ngw] Same admin messages repeated constantly ngw 13. 2011-09-07 [1] [ngw] OT: Internal email routing ngw 14. 2011-08-31 [2] Re: [ngw] OT: Sorta - Domain version ngw 15. 2011-08-31 [1] Re: [ngw] multiple gwia's in primary domain? ngw 16. 2011-08-29 [2] [ngw] All email is gone from manually created folder ngw 17. 2011-08-26 [1] Re: [ngw] System Dist list not sending to full list - ngw 18. 2011-08-24 [1] [ngw] What is the limit for the number of people in a ngw 19. 2011-08-23 [1] [ngw] Is there a way to not display the time in the c ngw 20. 2011-08-23 [1] Re: [ngw] Feedback wanted for BrainShare demos ngw 21. 2011-08-15 [1] Re: [ngw] Restores on GroupWise ngw 22. 2011-07-12 [1] Re: [ngw] cleaning up an empty post office ngw 23. 2011-07-08 [2] [ngw] Unable to reply to emails sent to us from one ngw 24. 2011-06-17 [1] Re: [ngw] OT: Lulzsec releases passwords and e-mail a ngw 25. 2011-06-16 [2] [ngw] Email is pending for one user ngw 26. 2011-06-09 [1] Re: [ngw] IMAP abends absolutely atrocious ngw 27. 2011-06-06 [1] [ngw] how do i tell what version of GroupWise i'm run ngw 28. 2011-06-03 [1] Re: [ngw] OT: RBL & Yahoo ngw 29. 2011-06-02 [1] [ngw] Invalid permission for fil