Bypassing Attachment Errors In Exchange Archive Jobs

  • 7019260
  • 05-Aug-2015
  • 07-Aug-2017


Retain 4


I'm seeing errors about attachments being "null" and such where Exchange reports to the Retain Worker that it cannot retrieve the attachment.  When I open the message in question in Outlook, sure enough, I see the attachment icon but cannot open the attachment.  When these errors occur, the message does not get archived.  What can I do about this so that the message gets archived and the Item Store flag gets advanced?


Add a setting to the file (.../RetainWorker/WEB-INF/classes/config) that reads:  att.nonfatal=1

Save the file and restart tomcat.

This procedure must be done for EVERY worker that you have installed.

It will cause Retain to add a replacement attachment for each missing attachment named "missing attachment.txt".  Inside that text file it will read:  "The attachment"+attName+" could not be retrieved".

Of course, you may want to research the messages first to verify that Outook cannot open the attachments.  The details of the messages are in the Worker log.  It will give you the message subject, its delivered date, and its folder path in the user's mailbox.  If you see that the attachments truly cannot be accessed by Exchanged - and if Microsoft cannot fix it - then there is nothing lost by moving past these messages that was not lost already.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2592.