|
|
|||
|
|||
|
Since yesterday CommitCRM has been shutting down for no apparent reason several times.
Here is the what I found in the event viewer. Log Name: Application Source: Application Error Date: 1/27/2017 6:00:34 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Optiplex-390-PC Description: Faulting application name: CommitCRM.exe, version: 12.0.0.4, time stamp: 0x57cd4f5f Faulting module name: ntdll.dll, version: 6.1.7601.23572, time stamp: 0x57fd02d3 Exception code: 0xc0000005 Fault offset: 0x0002df5c Faulting process id: 0xcd44 Faulting application start time: 0x01d27884047eaab8 Faulting application path: C:\CommitCRM\Client\CommitCRM.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: d2fc8298-e47f-11e6-b66a-d067e5169bec 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="2017-01-27T11:00:34.000000000Z" /> <EventRecordID>188449</EventRecordID> <Channel>Application</Channel> <Computer>Optiplex-390-PC</Computer> <Security /> </System> <EventData> <Data>CommitCRM.exe</Data> <Data>12.0.0.4</Data> <Data>57cd4f5f</Data> <Data>ntdll.dll</Data> <Data>6.1.7601.23572</Data> <Data>57fd02d3</Data> <Data>c0000005</Data> <Data>0002df5c</Data> <Data>cd44</Data> <Data>01d27884047eaab8</Data> <Data>C:\CommitCRM\Client\CommitCRM.exe</Data> <Data>C:\Windows\SysWOW64\ntdll.dll</Data> <Data>d2fc8298-e47f-11e6-b66a-d067e5169bec</Data> </EventData> </Event> |
|
|
|||
|
|||
|
Thank you for posting. We are not familiar with such an issue and it is hard to tell what might be causing this (unfortunately the details of the event log that you provided do not tell much). First I'd recommend that you try to run RangerMSP client from another PC on your network and see whether it works there. Also try to undo any recent updates to your PC, try to stop the Anti-Virus program for a while, and try to look for a possible external cause. Besides, we will need to work with you directly on this, analyze the application log files and possibly the database. Please contact our support directly.
|
