Event ID: 40967 Restarting failed process. The process has failed abnormally and will be restarted automatically. Being this causes a mutex issue you may eventually see Event ID: 41050.
The Lotus Notes System Diagnostics (NSD) fatal will be on the EVLotusDominoArchivingTask:
############################################################
### thread 13/20: [EvLotusDominoArchivingTask: 13a8: 22cc] FATAL THREAD (Panic)
### FP=0x04c4a1a0, PC=0x7780f8b1, SP=0x04c4a134
### stkbase=0x04c48000, total stksize=8192, used stksize=-8500
### EAX=0x00000000, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000
### ESI=0x000009f0, EDI=0x04c4a17c, CS=0x00000023, SS=0x0000002b
### DS=0x0000002b, ES=0x0000002b, FS=0x00000053, GS=0x0000002b Flags=0x00000246
############################################################
[ 1] 0x7780f8b1 ntdll.ZwWaitForSingleObject+21 (9f0,493e0,0,10)
The Dtrace will show:
8883 15:14:07.138 [9364] (EvLotusDominoArchivingTask) <7912> EV-M {DOMNOTE.EN_US} Result = [False]
8884 15:14:07.138 [9364] (EvLotusDominoArchivingTask) <7912> EV-L {DOMINOSHORTCUT.EN_US} Processing attachments
8885 15:14:07.138 [9364] (EvLotusDominoArchivingTask) <7912> EV-L {DOMNOTE.EN_US} False
8886 15:14:07.154 [9364] (EvLotusDominoArchivingTask) <7912> EV-L {DOMNOTE.EN_US} False
8887 15:14:07.154 [9364] (EvLotusDominoArchivingTask) <7912> EV-L {DOMINOSHORTCUT.EN_US} Entry
Notice: The DominoShortcut.MakeShortcut has an Entry line but no Exit.
The Mutex Checker output file had the following line:
7/31/2013 5:47:36 PM EvLotusDominoArchivingTask.exe pid: 9964 type: Mutant A28: \BaseNamedObjects\EV~NRH~INIT-MUTEX
Enterprise Vault begins the process of creating the shortcut through the Notes API. The Notes API would fail on a couple of documents throwing an NSD.
Upgrading the Lotus Notes client to version 8.5.3 resolved the issue Enterprise Vault Gateway.
Note 1: One should review the Open Documents section of the NSD in order to determine which notes are open at the time of the fatal. These documents can be collected from the customer and used to reproduce the issue in a similar test environment.
Note 2: Because this issue locks resources causing a mutex issue the server will also need to be restarted each time the issue occurs. If using the mutex checker, look for the first mutant process in the output file that occurs after a reboot. This will give you the process to run DTrace on. Once the process is determined reboot the server again and start DTrace on that process.
Applies To
Enterprise Vault Domino Gateway
Enterprise Vault for Domino 10 SP2
Lotus Domino 8.5.2
Lotus Notes 8.5.2