You may receive an error in Event Viewer indicating that errors were generated in an Exchange Store Manager .wlog file.
While viewing the .wlog file, an error similar to the following is generated:
19:15:03 Subject: Message Subject Title
19:15:03 Checksum: 2c078cbf-0adc-d919-f967-ce7aadccc37f
19:15:03 DEBUG: END WalkMessage() - result 0
19:15:03 DEBUG: BEGIN BLATTACHMENTFILE::Select()
19:15:03 DEBUG: END BLATTACHMENTFILE::Select() - result 0
19:15:03 ERROR: Message.Stub: Attachment 'Attachmentname.doc' has not been archived.
There are two possible causes of this error.
1) This message and attachment had previously been archived and stripped by Archive Manager version 3.6.
Archive Manager 3.6 checksummed attachments in an different manner than versions 3.7 and later. This message is displayed for older messages that have already been processed and are in the database. The ESM should move on to the next message after it generates this message.
2) The error means that the message was already exported or stripped, after this process happened the user opened the message and edited the attachment then saved the attachment back to the exchange server.
Archive manager is unable to re-export\re-strip the message and the following debug\error occurs in the log.
This is because Archive Manager does not currently support versioning. If the attachment has been changed in exchange we can not re-export or overwrite the attachment we currently have in the archive.
This message can be ignored and has been changed to an informational message rather than an error in Archive Manager 4.1.