1
answer

Hi,

 

I am running NXlog CE version 2.9.1347 on Windows 2012 R2.  The service keeps crashing with the following;

 

Log Name:      Application
Source:        Application Error
Date:          07/09/2015 09:26:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      myServer
Description:
Faulting application name: nxlog.exe, version: 0.0.0.0, time stamp: 0x54fedd1a
Faulting module name: ntdll.dll, version: 6.3.9600.17668, time stamp: 0x54c846bb
Exception code: 0xc0000005
Fault offset: 0x000195da
Faulting process id: 0x3504
Faulting application start time: 0x01d0e94f3d2521e0
Faulting application path: C:\Program Files (x86)\nxlog\nxlog.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8c5cf6ce-5542-11e5-80c1-005056bc12a5
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-09-07T09:26:42.000000000Z" />
    <EventRecordID>123651</EventRecordID>
    <Channel>Application</Channel>
    <Computer>myServer</Computer>
    <Security />
  </System>
  <EventData>
    <Data>nxlog.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>54fedd1a</Data>
    <Data>ntdll.dll</Data>
    <Data>6.3.9600.17668</Data>
    <Data>54c846bb</Data>
    <Data>c0000005</Data>
    <Data>000195da</Data>
    <Data>3504</Data>
    <Data>01d0e94f3d2521e0</Data>
    <Data>C:\Program Files (x86)\nxlog\nxlog.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>8c5cf6ce-5542-11e5-80c1-005056bc12a5</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

I have seen other posts about a hotfix that fixes another app crashing issue.  But does it also fix this one?

Thanks,

Darren.

AskedSeptember 7, 2015 - 1:35pm

Answer (1)

This issue is likely already fixed in NXLog EE, feel free to to test the trial. The fix will be available in the next NXLog CE release also.

 

Comments (6)

  • adm's picture
    (NXLog)

    This has been resolved for most people experiencing crashes when using im_msvistalog. There is another report suggesting that there is still something wrong. If you could help isolate the issue that would help, probably it's specific to some rare windows app generating eventlog entries.

  • edgarcb83's picture

    I'm still having this issue with 2.9.1504, log says it starts but then when service stops log does not register anything:

    2016-02-17 09:37:03 INFO nxlog-ce-2.9.1504 started
    2016-02-24 14:00:30 INFO nxlog-ce-2.9.1504 started
    2016-02-24 14:12:04 INFO nxlog-ce-2.9.1504 started
    2016-02-25 09:11:54 INFO nxlog-ce-2.9.1504 started

    This is an Exchange Server 2013 SP1. the weird part is that I have 2 exchange servers that are exactly the same (no cluster), in "server1" nxlog is working just fine with version 2.8.1248.

    The server with the problem is "server2" I uninstalled version 2.9.1504 to fix crashing problem because of "bad parameter" and now It just crashes without any more information.

  • adm's picture
    (NXLog)

    An issue has been identified that could be possibly causing this. Could you download and test nxlog-2.10.1577-trial.msi to see if that works ok? The fix will be merged into the next release of the community edition.

  • b0ti's picture
    (NXLog)

    That is no longer available. The current trials are:

    • nxlog-3.2.2002 for the NXLog Enterprise Edition stable version
    • nxlog-3.99.3177 for the NXLog Enterprise Edition v4 beta