When trying to run my executable program on a Windows Server 2008 R2 (x64), it fails immediately and Windows says "Program (x64) has stopped working".
The same executable works on many other machines.
Even on other machines with the same OS.
The program comes with its own Dlls in the folder.
Even if it would require other Dlls that arent present i think the system would say so?
Here is the output from Windows Event Viewer:
Faulting application name: dscp.exe, version: 19.0.0.398, time stamp: 0x5d8b42ef
Faulting module name: VERSION.dll_unloaded, version: 0.0.0.0, time stamp: 0x4a5be082
Exception code: 0xc0000005
Fault offset: 0x000007fefbcc15b4
Faulting process id: 0x1db4
Faulting application start time: 0x01d5744a0d493693
Faulting application path: C:\TEMP\DebugW\dscp.exe
Faulting module path: VERSION.dll
Report Id: 50adb64b-e03d-11e9-a7b2-000c29b302dd
I have looked up VERSION.dll and it seems to be a Windows system Dll.
I dont' know how to debug this issue.
Related
I am developing an app for windows, and I need it to work on Windows server 2019.
The flutter docs website mentions support for: Win 7 and above, and I'm not sure if that includes Windows server.
So, does flutter Desktop support Windows server 2019 and above?
I tried to run the application on windows server 2019, the application does not open, an error is logged:
Faulting application name: logbook.exe, version: 1.0.0.0, time stamp: 0x62fc7c7c
Faulting module name: logbook.exe, version: 1.0.0.0, time stamp: 0x62fc7c7c
Exception code: 0xc0000005
Fault offset: 0x0000000000005680
Faulting process id: 0x2590
Faulting application start time: 0x01d8b200df09b765
Faulting application path: C:\dev\logbook\logbook.exe
Faulting module path: C:\dev\logbook\logbook.exe
Report Id: fb88d338-89c8-4697-b637-5922dd9ad358
Faulting package full name:
Faulting package-relative application ID:
I'm a little stumped as to why this windows service is not running when using the Network Service account (but does so on other machines using the same code), getting me these two subsequent errors in event viewer:
Application: MyApplication.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 06F3C67E
Stack:
and
Faulting application name: MyApplication.exe, Version: 1.0.0.0, time stamp: 0x87654321
Faulting module name: ReferencedComLib.dll, Version: 1.0.0.0, time stamp: 0x12345678
Exception code: 0xc0000005
Fault offset: 0x0000c67e
Faulting process ID: 0x148c
Faulting application start time: 0x01d4df2e591220f2
Faulting application path: C:\Program Files (x86)\MyApplication\MyApplication.exe
Faulting module path: C:\Windows\SYSTEM32\ReferencedComLib.dll
Report ID: 9d8df956-4b21-11e9-80c8-00155dc82141
Faulting package full name:
Faulting package-relative application ID:
This seems to indicate that the service is looking for ReferencedComLib.dll under C:\Windows\SYSTEM32...
But ReferencedComLib.dll is actually located under C:\Windows\SysWOW64 - it's a COM-library from third party (and their installer correctly installs it into SysWOW64)
Running under Local System however this error does not even show up and the service runs without problems - and this problem is currently only reproducable on one stage, on all others it is running fine with Network Service.
How could changing the service account running the service result in a faulting module?
Simon Mourier was right, the problem was internal to the third party dlls I am using and it was trying to access a directory that was under C:\Users....
Reinstalling under a different path that Network Service could access fixed the problem.
I have an SSIS package that runs an executable by using Powershell. This worked fine for more than a year, but all of the sudden I get this strange error. I've isolated the command:
& '\\iguana01\VMMa\Process e-Invoice\ProcesseInvoice.exe' #('/countfiles','46')
If I run this command on my own PC there is no problem
But if I run this same command on the server (2012) then I get this strange error
This error dissapears when I run it on the 2012 server from a local folder
The event viewer doesn't give me that much more information, .NET Runtime 1026 error
Application: ProcesseInvoice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
at ProcesseInvoice.Program.Main(System.String[])
And an application error (1000)
Faulting application name: ProcesseInvoice.exe, version: 2.2.4.0, time stamp: 0x5857fbf7
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0x4488
Faulting application start time: 0x01d34be3a1f4ea5d
Faulting application path: \\iguana01\VMMa\Process e-Invoice\ProcesseInvoice.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: dfaca8c6-b7d6-11e7-b19f-005056b765a3
Don't know what the problem is and in which direction I have to look.
Pretty stupid, seemed that the processinvoicing*32.exe was still running under processes on the server. The logging in Powershell and eventviewer where not that clear.
After installing latest haxe toolkit (3.2.0), I have tried to install some libraries to start work on my project. But library manager (haxelib.exe) seems not working properly on my computer. It always crashes and windows showing alert:
The application was unable to start correctly (0xc000000d). Click OK
to close the application
I have also installed toolkit on wife computer and everything working fine. Wife has Windows 7 x64. On my computer is installed Windows 8.1 x64.
In Windows event viewer I found logs:
(Error description)
Faulting application name: haxelib.exe, version: 0.0.0.0, time stamp: 0x5128e2cf
Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68dd1
Exception code: 0xc000000d
Fault offset: 0x0009d4f2
Faulting process id: 0x1710
Faulting application start time: 0x01d0f85f90454af3
Faulting application path: C:\HaxeToolkit\haxe\haxelib.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d9781581-6452-11e5-82b6-94de80bc77ca
Faulting package full name:
Faulting package-relative application ID:
(Information)
Fault bucket 116025787538, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: haxelib.exe
P2: 0.0.0.0
P3: 5128e2cf
P4: ntdll.dll
P5: 6.3.9600.17936
P6: 55a68dd1
P7: 0009d4f2
P8: c000000d
P9: 00000000
P10:
Attached files:
C:\Users\stanosky\AppData\Local\Temp\WER95F7.tmp.WERInternalMetadata.xml
C:\Users\stanosky\AppData\Local\Temp\WERA1B0.tmp.appcompat.txt
C:\Users\stanosky\AppData\Local\Temp\WERA1E0.tmp.dmp
C:\Users\stanosky\AppData\Local\Temp\WERA21F.tmp.WERDataCollectionFailure.txt
These files may be available here:
C:\Users\stanosky\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_haxelib.exe_2b43177c7b6b1557ce91e7560961d98719c3f54_0b7bc880_0bf3a5b6
Analysis symbol:
Rechecking for solution: 0
Report Id: d9781581-6452-11e5-82b6-94de80bc77ca
Report Status: 4104
Hashed bucket: f45888bea7f3cfaa0a11620b03ca7f6a
Any ideas what is going wrong with my computer/windows?
It turns out that my computer was infected by rootkit. It injects some bits of code into Windows dll files and that caused malfunction of haxelib.exe. I have removed it and my problem has gone.
I have a 32-bit windows .exe. Which will run as windows service. This .exe runs fine as servics for window 2000/xp 32-bit version.
However when try to run on 64-bit windows 2008 server it crash. I am observing two cases.
1) If I build the application on VC++ 6. From Event log entry it seems to Kernel.dll is crashing.
Faulting application name: , version: , time stamp: 0x4e6461c0
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0xe06d7363
Fault offset: 0x0000b727
Faulting process id: 0xe2c
Faulting application start time: 0x01cc83cb1052e4b3
Faulting application path: C:\Program Files (x86)\\\Admin.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 4e0693b4-efbe-11e0-a07f-001143e8bb9d
2) If I build the application with VS2005 32 bit, A run time error displayed and Event log says msvscrt.dll is crashed.
Faulting application name: , version: ,
Faulting module name: MSVCR80.dll, version: 8.0.50727.4927, time stamp: 0x4a2752ff
Exception code: 0x40000015
Fault offset: 0x000046b4
Faulting process id: 0x34c
Faulting application start time: 0x01cc8c4f2a223426
Faulting application path: C:\Program Files (x86)\\\Admin.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCR80.dll
Report Id: 69554d57-f842-11e0-a07f-001143e8bb9d
Please help me out resolve this issue.
You need to diagnose the problem better before you can solve it, which probably means finding a way to reproduce it while program is executing under the debugger. Some suggestions:
Since your service is EXE (and not DLL that runs under svchost.exe, which is a generic host process name for services that run from DLLs), you should be able to use "Attach to Process" option in Visual Studio to attach the debugger to it. You might need to start the Visual Studio as administrator and/or change the user under which the service executes to be able to do that.
Also, if the service crashes soon after starting, you might need to call MessageBox with MB_SERVICE_NOTIFICATION to pause execution long enough so you can attach the debugger.
However, if the service crashes during startup before it even reaches the MessageBox, you need to
build it as console application. Now you can actually start it under the debugger and see what is going on.
Can you please try installing redistributable package on client machine to run your application.