As part of our nightly upgrade routine, we perform a database compact
and repair on our customers databases. At one of our customers, the
jetcomp application crashes causing the database to be destroyed.
Below is an excerpt from the Dr Watson log file generated when this
occurs:
function: msjet40!Ordinal55
1b0b2ba1 0cc2 or al,0xc2
1b0b2ba3 0400 add al,0x0
1b0b2ba5 33d2 xor edx,edx
1b0b2ba7 85db test ebx,ebx
1b0b2ba9 0f94c2 sete dl
1b0b2bac 8bda mov ebx,edx
1b0b2bae 46 inc esi
1b0b2baf e9afb5f9ff jmp msjet40!Ordinal130+0x8fd
(1b04e163)
1b0b2bb4 85c9 test ecx,ecx
1b0b2bb6 7406 jz msjet40!Ordinal55+0x1f5d1
(1b0b2bbe)
FAULT ->1b0b2bb8 668b16 mov dx,[esi]
ds:0023:01daffff=????
1b0b2bbb 668917 mov [edi],dx
1b0b2bbe 83c702 add edi,0x2
1b0b2bc1 83c502 add ebp,0x2
1b0b2bc4 83c602 add esi,0x2
1b0b2bc7 e997b5f9ff jmp msjet40!Ordinal130+0x8fd
(1b04e163)
1b0b2bcc c7451000000000 mov dword ptr [ebp+0x10],0x0
1b0b2bd3 5f pop edi
1b0b2bd4 5e pop esi
1b0b2bd5 5d pop ebp
1b0b2bd6 5b pop ebx
The fault occurs in the msjet40.dll module. Can any genius interpret
what is going on by looking at this? I have the complete Dr. Watson
log file if it would be of any use. Thank you for any and all help.
-Vincent