An Exchange mailbox does not get archived even after multiple passes of the esm service, and when you open up the corresponding wlog file for that mailbox you will see the following error:
Application received an unhandled exception:
12:00:12 ExceptionCode=0xC0000005; Reason=0x00000000; Address=0xC8E98000
12:00:12 Address=0x78576B6A
12:00:12 Stack trace: ContextFlags=0x0001003F
12:00:12 ESP=0x0012EE4C
12:00:12 EBP=0x0012F2CC EIP=0x78576B6A (MSVCR90.dll+0x00056B6A)
12:00:12 EBP=0x0012F308 EIP=0x78554F24 (MSVCR90.dll+0x00034F24)
12:00:12 EBP=0x0012F320 EIP=0x78554F46 (MSVCR90.dll+0x00034F46)
12:00:12 EBP=0x0012F338 EIP=0x78A35C95 (mfc90u.dll+0x00055C95)
12:00:12 EBP=0x0012F348 EIP=0x78A35CDC (mfc90u.dll+0x00055CDC)
12:00:12 EBP=0x00A13C50 EIP=0x003D5AD3 (Badger EmailObjects.dll+0x00005AD3)
When looking at the logs it appears that there are messages that fail to be archived and kills the archiving process for that mailbox. If you look for those messages in Outllook you may not find them.
The reason why you may not see these messages in Outlook, but you will see them trying to be archived in the wlog file is due to major message corruption in the Exchange mailbox. There may be messages that get so corrupt even Outlook is not able to read them.
The workaround for this is to move the Exchange mailbox to a different mailstore which will recreate the mailbox and leave the old corrupt mailbox behind. When you move a mailbox to a different mailstore in Exchange, it does not bring the original mailbox. It recreates a new mailbox and then copies the message over, then deletes the mailbox in the original location. Any corruption that it is not able to read it simply ignores and leaves it behind.
Once the Archive Manager Active Directory Connector service has run successfully, and Archive Manager is able to detect that the mailbox now resides on a different mailstore the mailbox should archive successfully.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center