I'm using the trial version of Setup Factory to convert a VB6 app from Windows Server 2008 to Windows Server 2016.
The issue I'm having is with ntdll.dll, it's crashing the setup. It looks like the issue is the version it's using. The event viewer shows the faulting module for the dll is in the System32 directory. It should be accessing the version in SysWOW64. Is there any way to force the app to use the 32 bit version? Or could it be a different issue?
Faulting application name: TMS.exe, version: 1.0.0.312, time stamp: 0x6099961c
Faulting module name: ntdll.dll, version: 10.0.14393.4350, time stamp: 0x606eb0f6
Exception code: 0xc0000005
Fault offset: 0x00082cdb
Faulting process id: 0x16ec
Faulting application start time: 0x01d747fdb4f62915
Faulting application path: C:\Programs\TMS.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9f5c60cf-7c33-4d73-bd0c-3ae2ed679acd
Faulting package full name:
Faulting package-relative application ID:
The issue I'm having is with ntdll.dll, it's crashing the setup. It looks like the issue is the version it's using. The event viewer shows the faulting module for the dll is in the System32 directory. It should be accessing the version in SysWOW64. Is there any way to force the app to use the 32 bit version? Or could it be a different issue?
Faulting application name: TMS.exe, version: 1.0.0.312, time stamp: 0x6099961c
Faulting module name: ntdll.dll, version: 10.0.14393.4350, time stamp: 0x606eb0f6
Exception code: 0xc0000005
Fault offset: 0x00082cdb
Faulting process id: 0x16ec
Faulting application start time: 0x01d747fdb4f62915
Faulting application path: C:\Programs\TMS.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9f5c60cf-7c33-4d73-bd0c-3ae2ed679acd
Faulting package full name:
Faulting package-relative application ID:
Comment