The "NetQos ReporterAnalyzer Query Service" stops when I run a custom report that uses a protocol filter of UDP or TCP

Document ID : KB000004221
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The "NetQos ReporterAnalyzer Query Service" stops when I run a custom report that uses a protocol filter of UDP or TCP.

This will prevent your custom reports from running.

The error below will be seen in the Windows Application Event Logs:

Faulting application name: nqreporter.exe, version: 4.1.0.0, time stamp: 0x55b7e493

Faulting module name: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5

Exception code: 0xc0000417

Fault offset: 0x0006ccd5

Faulting process id: 0x1cb4

Faulting application start time: 0x01d10c368f72a62f

Faulting application path: E:\CA\NFA\bin\nqreporter.exe

Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll

Report Id: 0017a489-782a-11e5-80ca-005056866442

Faulting package full name: 

Faulting package-relative application ID:

Environment:
NFA Console 9.3.x
Cause:

This occurs when there are protocolID values in the reporter.protocol_groups table that are not associated with an ID in the reporter.protocol_definitions table.

Resolution:

To resolve, follow the steps below:

1. Login to mysql on the NFA console server by running:

mysql -P3308 reporter

2. Run the following query to determine if there are protocolID's with a value of 0 in the protocol_groups table:

select * from protocol_groups where protocolid=0;

3. If there are any results returned in the query above please delete these values with:

delete from protocol_groups where protocolid=0;

4. Restart the "NetQos ReporterAnalyzer Query Service".

5. Run the Custom Report again which was causing the Query service to stop and it should now complete without the service stopping.