Faulting module in Windows with NXLog 4.2.4216.0
Tags:
crash
#1
hatula
Hi everybody,
I did upgrade my NXLog client from version 3.2.202 to version 4.2.4216, but windows service can not run. But old version worked normally. It was in Microsoft Windows 10 Enterprise 2016 LTSB. And windows application log contains this event:
Faulting application name: nxlog.exe, version: 4.2.4216.0, time stamp: 0x00000000
Faulting module name: libnx-0.dll, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000001196e
Faulting process id: 0x1368
Faulting application start time: 0x01d4cdb54eb121da
Faulting application path: C:\nxlog\nxlog.exe
Faulting module path: C:\nxlog\libnx-0.dll
Report Id: 4b6f1d21-d02e-4502-9c20-f6e0cc5f9637
Faulting package full name:
Faulting package-relative application ID:
Any ideas? Thanks a lot!
#1
hatula
Hi everybody,
I did upgrade my NXLog client from version 3.2.202 to version 4.2.4216, but windows service can not run. But old version worked normally.
It was in Microsoft Windows 10 Enterprise 2016 LTSB.
And windows application log contains this event:
Faulting application name: nxlog.exe, version: 4.2.4216.0, time stamp: 0x00000000
Faulting module name: libnx-0.dll, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000001196e
Faulting process id: 0x1368
Faulting application start time: 0x01d4cdb54eb121da
Faulting application path: C:\nxlog\nxlog.exe
Faulting module path: C:\nxlog\libnx-0.dll
Report Id: 4b6f1d21-d02e-4502-9c20-f6e0cc5f9637
Faulting package full name:
Faulting package-relative application ID:
Any ideas?
Thanks a lot!
We believe the cause of this is very likely to be the same as those other crash reports mentioned here:
- https://nxlog.co/question/4232/nxlog-crashes-service-start
- https://nxlog.co/question/4259/nxlog-client-failed-read-config-cache
The root cause has been identified and our team is working on the fix. There will be a new NXLog EE version released within a couple days.
