ESMWorker.exe not terminating gracefully at the end of each processing run. Behaviour is the same regardless of which parent process spawned ESMWorker.exe ( Archive Manager Exchange Store Manager Service or Archive Manager Data Load Service ). ESMWorker.exe completes the run, displays statistics in the ESM log and then terminates with exit code 128.
The following errors may also be observed in the Archive Manager event log.
EventID 7 for Source: Exchange Store Manager, with the following Exception Message: "Worker for 'MAILBOXNAME'(MailboxID XXX) terminated unexpectedly with exit code 128, state DEAD".
EventID 0 for Source: DataLoaderWorker, with the following Exception Message: "Worker for journal 'JOURNALACCOUNT' terminated unexpectedly with exit code 128, state DEAD".
An EventID 1000 for Source: .NET Runtime 2.0 Error may also be found in the Application event log with the following error: "Faulting application esmworker.exe, version 4.1.1.446, stamp 4aaa816a, faulting module rpcrt4.dll, version 5.2.3790.4502, stamp 49f5889a, debug? 0, fault address 0x0002d9ab"
A review of the ESM log file will show error after mailbox export completed:
Mailbox export complete.
ERROR: Application failed with an unhandled exception:
ExceptionCode=0xC0000005; Reason=0x00000000; Address=0x0511CE2C
Address=0x77C8920A
Stack trace: ContextFlags=0x0001003F
ESP=0x0545FF70
EBP=0x0545FF74 EIP=0x77C8920A (RPCRT4.dll+0x0003920A)
EBP=0x0545FF90 EIP=0x616E9658 (EMSMDB32.DLL+0x00019658)
EBP=0x0545FFB8 EIP=0x616EAB98 (EMSMDB32.DLL+0x0001AB98)
EBP=0x0545FFEC EIP=0x77E6482F (kernel32.dll+0x0002482F)