Faulting application name: Coveo.DiagnosticTool.Client.exe, version: 126.96.36.199, time stamp: 0x563cd56a
After upgrading to Coveo Enterprise Search 7.0 x64 (8047)
I looked at the eventviewer and saw the following error:
Faulting application name: Coveo.DiagnosticTool.Client.exe, version: 188.8.131.52, time stamp: 0x563cd56a Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e Exception code: 0xe0434352 Fault offset: 0x000000000000606c Faulting process id: 0x169c Faulting application start time: 0x01d170a4a0154022 Faulting application path: C:\Program Files\Coveo Enterprise Search 7\Bin\Coveo.DiagnosticTool.Client.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: de6fccf3-dc97-11e5-80d1-000d3a11ca7c Faulting package full name: Faulting package-relative application ID: Do you have any idea of why I'm getting this error. I can provide more logs found in C:\Program Files\Coveo Enterprise Search 7\Bin\CoveoDiagnosticToolService.log 2016-02-26 09:44:20,044  INFO Coveo.DiagnosticTool.Client.Service.Service Trying to start the DiagnosticTool process 2016-02-26 09:44:20,153  INFO Coveo.DiagnosticTool.Client.Service.Service Download the Coveo Diagnostic Tool package or update if necessary. The package should be at: Coveo.DiagnosticTool.Client.exe 2016-02-26 09:44:20,153  INFO Coveo.DiagnosticTool.Client.Service.Service Status of the update request: 2016-02-26 09:44:20,872  INFO Coveo.DiagnosticTool.Client.Service.Service A command was received: AT
That is indeed strange. Normally there shouldn't be any failures in the event viewer about the diagnostic tool.
I would ask you to contact Coveo's customer support and provide as much information as you can. If you could please provide the "CoveoDiagnosticToolService.log" that you have found in "
C:\Program Files\Coveo Enterprise Search 7\Bin\". Also I would ask that you include the "config.json" and the "CoveoDiagnosticTool.log" located in "
C:\Program Files\Coveo Enterprise Search 7\Diagnostic Tool".
Once this is done I can review the logs to try and better understand whats going on.