wrun32.exe crashes when calling mshtml.dll

Hi everyone, I work at an MSP in their support department, one of our clients has a line of business application that uses AcuCobolGT. There is a module in this application that prints an image of a check, after migrating them to a new server this feature causes an application crash. The vendor of the application refuses to look at it. stating that it's not the wrun32.exe causing the issue, but rather mshtml.dll

I am hoping someone here can provide more insight into this than the vendor and maybe tell me which file is likely casuing the issue

Thanks

Environment Details

  • Windows Server 2016 Standard
  • wrun32.exe version - Au Windows 10 - 10.001.014

Here is a copy of the event log

Faulting application name: wrun32.exe, version: 10000.1000.1.3902, time stamp: 0x56e081bb
Faulting module name: MSHTML.dll, version: 11.0.14393.3053, time stamp: 0x5d01d3ab
Exception code: 0xc0000005
Fault offset: 0x00aa911f
Faulting process id: 0x5748
Faulting application start time: 0x01d543e85a8b7e2f
Faulting application path: C:\SP3000\Acucbl1001\AcuGT\bin\wrun32.exe
Faulting module path: C:\Windows\SYSTEM32\MSHTML.dll
Report Id: b9a1eb39-6c65-40be-8ae8-3d2f80724e7d
Faulting package full name:
Faulting package-relative application ID:

And here is the associated MS Error Report

 

Fault bucket 2101604597205222279, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: wrun32.exe
P2: 10000.1000.1.3902
P3: 56e081bb
P4: MSHTML.dll
P5: 11.0.14393.3053
P6: 5d01d3ab
P7: c0000005
P8: 00aa911f
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD86B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wrun32.exe_ca8b41c5e692c4f4ce1893767e2ab8dd4c6_e226479b_5672e1d1

Analysis symbol:
Rechecking for solution: 0
Report Id: b9a1eb39-6c65-40be-8ae8-3d2f80724e7d
Report Status: 1
Hashed bucket: f2cd612c1acdf9332d2a663f12bec387

Parents
  • Verified Answer

    With the new server - the mshtml.dll is 64 bit -  Windows x64 has a directory System32 that contains 64-bit DLLs .

    Thus native processes with a bitness of 64 find “their” DLLs where they expect them: in the System32 folder. A second directory, SysWOW64, contains the 32-bit DLLs.

Reply
  • Verified Answer

    With the new server - the mshtml.dll is 64 bit -  Windows x64 has a directory System32 that contains 64-bit DLLs .

    Thus native processes with a bitness of 64 find “their” DLLs where they expect them: in the System32 folder. A second directory, SysWOW64, contains the 32-bit DLLs.

Children