Groupwise Error Number 8e03
userxxx.db cause Error 8E03 is an issue with GW 5.5 and GW 5.5.1. fix 1.Update to Support Pack 3 for GroupWise 5.52. Go to the DOS prompt and look for the directory where the executable of GWCHECK resides, and type the following: COPY CON ATTCLIP.NGW3. Run GWCHECK with the following options:Analyze/Fix DatabasesContentsFix Problems[Under the tab "Databases"]Check: User & Message document Document Title: Error 8E03 Document ID: 10026701 Solution ID: 1.0.54615605.2532439 Creation Date: 15Feb2000 Modified Date: 13Mar2003 Novell Product Class:Groupware disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
Favorite Rating: Error: 8E03 (Last modified: 24Dec2003) This document (10058127) is provided subject to the disclaimer at the end of this document. fact Novell GroupWise 5.5 symptom Error: 8E03 Error: "8E03 - Bad Data, To requeue, save the last http://support.novell.com/docs/Tids/Solutions/10026701.html attachment to \WPCSOUT\OFS\0" Error occurs on the POA cause Corruption in the GroupWise databases. fix Perform a Top Down Rebuild.System.Troubleshooting Notes:1- In this case all GroupWise agents are on the same box. 2-NOVL78312- How to Perform a Top Down Rebuild http://www.novell.com/support/kb/doc.php?id=10058127 on GroupWise disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. Document ID: 10058127 Solution ID: NOVL31338 Creation Date: 01Nov2000 Modified Date: 24Dec2003 NovellGroupware 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
Site Leaders Articles Blogs What's New? FAQ Advanced Search Forum PRODUCT RELATED DISCUSSIONS COLLABORATION GroupWise GroupWise 2014 GW2014: Clients 8e03 Bad Data especially on some attachments You can view the discussions, but you must https://forums.novell.com/showthread.php/495589-8e03-Bad-Data-especially-on-some-attachments login before you can post. Click the LOGIN link in the forum header to http://ngwlist.com/pipermail/ngw/2016-April/178782.html 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 4 of 4 Thread: 8e03 Bad Data especially on some attachments Thread Tools Show Printable Version Subscribe to this groupwise error Thread… Display Switch to Linear Mode Switch to Hybrid Mode Threaded Mode Threaded View 09-Dec-2015,11:02 AM #1 Thomas Roberts NNTP User 8e03 Bad Data especially on some attachments We have a site with GroupWise client 14.02 and have an issue where two or three users are reporting a bad data error 8c03 when trying to open email. This is particularly the case (but not always) when trying to open pdf attachments. groupwise error number If we try and open the attachment we get 8e03 Bad Data. If we try to save the attachment we get “A file copy error has occurred. Make sure that you have access rights to the file or directory.” If I forward the email and its attachment to another internal user I get the same errors. The weird thing though, is that if I forward the same email and attachment to an external address at another site (also GW2014) the attachment opens and saves just fine. If I then re-forward that same email and attachment back to the original user, they can then open and or save the attachment without error. If I send a completely different email and different attachment from an external address to an affected user then things all work as expected. I’m not sure what I should be trying to get to the bottom of this. I’ve checked in GW Administration and the client/server box is ticked. Has anyone else seen/fixed this? Thomas 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 B
[ date ] [ thread ] [ subject ] [ author ] This past week I had my GroupWise system upgraded to 2014R2 HP1 and migrated to new hardware. Since this was done I've started seeing a large number of "[8E03], updating index" errors in my POA log pretty much all across my mailboxes. I've done a Analyze/Fix GWCheck followed by a manual index update but these errors are still showing up. When I've looked for the error online all I can find are really old references for it, from the early 2000's where most of them say to run GWCheck Analyze/Fix or that the issue has been fixed in GW 6.x. I'm getting ready to try running GWCheck using Structural Rebuild and possibly triggering the "Delete Old QFinder Files" when I reindex before opening a SR on this, but I was wondering if the community had any experience or ideas for what to do about this. Thanks! Mark +-----------------------------------------------+ E-mail Notice: If you think you received this e-mail by mistake, please do not use it in any way. It may contain confidential or legally protected information. Please delete the e-mail, destroy any copies, and immediately notify us by reply e-mail or by phone (800-968-1442). E-mail Warning: This e-mail was swept for computer viruses, but we cannot guarantee that it is virus-free or accept responsibility if it is contaminated. +------------------mail.michbar.org------------------+ Previous message: [ngw] Message creation date is off by five hours in the future Next message: [ngw] 8E03 Indexing Error Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the ngw mailing list