Retain complains error 8E03 for one user.
There is one TID suggesting to run gwchecks. But none of these reports show any problems.
Use "Verified Answers" if your problem/issue has been solved!
Cybersecurity
DevOps Cloud
IT Operations Cloud
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more
Retain complains error 8E03 for one user.
There is one TID suggesting to run gwchecks. But none of these reports show any problems.
Use "Verified Answers" if your problem/issue has been solved!
assuming both TID 7020615 & 7012098 (no files directly under /offiles/ )
I would do a contents check with the Attachment File Check as well, might be worth to make sure that has been done for whole PO
________________________
Andy of KonecnyConsulting.ca in Toronto
Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.
I did it all.
I checked the directory structure.
I did almost all kinds of gwchecks.
Maybe I have to open a case - but this customer (university) does not have free (included) cases.
Use "Verified Answers" if your problem/issue has been solved!
sleeping on it brings a thought, we can tell what was the last successfully archived message, so from that may well be able to determine the message or small range of messages on the mailbox in question that are triggering the error. If not really needed, just purging it or getting Retain to bypass that small time range may be all we need to do.
under 'About', down at the bottom is the 'Retention Date Utility'
https://support.microfocus.com/kb/doc.php?id=7020297
________________________
Andy of KonecnyConsulting.ca in Toronto
Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.
Good idea, Andy.
I will create a Retain job just for this user and let start the job from the very beginning.
Use "Verified Answers" if your problem/issue has been solved!
I had similar problem and was directed to get SOAP Trace log, in that log you can see, which message is triggering the error.
David