NTA charts: Data not available

10/19/2018 7:03 PM

5/12/2026 12:00 AM

The following error message appears in the NTA charts:

Data not available

Netflow Traffic Analyzer

This issue can be caused by the following:

• You changed the time for resources to show more than 30 days back. By default, NTA has a 30-day retention period.
• The chart is not configured to display the correct flow direction for the device. This is usually the case of missing CBQoS data.
• You are using unsupported language settings.
• The NTA Flow Storage database service is not running.
• NetFlow data are not being received due to firewall blocks. 

You changed the time for resources to show more than 30 days back

By default, NTA has a 30-day retention period. If this is the cause of the issue, follow the steps below to fix the issue: 

1. Click Edit on the resource with the issue.
2. On the Edit Resource page, under Time Period, select Use Time Period from the current view.
3. Click Submit.

The chart is not configured to display the correct flow direction for the device

1. Click Edit on the resource with the issue.
2. On the Edit Resource page, select Both in the Flow Direction drop-down.
3. Click Submit.

   

Note: In case of fixing a CBQoS issue, use the NetFlow Sources resource to validate the CBQoS column is updating. Expand the node and drill down to the correct interface that has a timestamp for CBQoS. CBQoS data is only available in the Interface Details view.
 

You are using unsupported language settings

The following errors display in the web and information service logs:

ERROR:<ERROR SolarWinds.Netflow.Web.Reporting.AsyncNTASWQLCoreCharts - (null)  Returned null DataTable, skipping execution
2016-10-18 16:29:34,277 [47] (755) ERROR ResourceChartService - (null)  Error while querying data in Async object:
'SWIS query error, cancelling execution.'. Returning No Data to the client.
ERROR ResourceChartService - (null)  Error while quering data in Async object: 'SWIS query error, cancelling execution.'. Returning No Data to the client.>

To fix the issue, change the language settings on the Orion server and NTA Flow Storage Database server to English US:

1. Stop all services in the SolarWinds Platform Service Manager.
2. Open the Region OR Region and Language Control Panel (depending on your Microsoft Windows Server version).
3. In the list menu, click Formats >  English (United States).

4. Go to the Administrative tab.
5. Click Copy Settings. This opens the Welcome screen and New user accounts settings window.
6. Select Welcome screen and system accounts and New user accounts.

​​​​​​​

7. Click OK.
8. Click OK to close the Region settings window.
9. Restart the Orion server to apply settings to the Orion services and website.

 

 

The NTA Flow Storage database service is not running

See Troubleshoot collector services in SolarWinds NTA in the NTA Administrator Guide.
 

The firewall is blocking NetFlow data

This scenario assumes you have set up your device to export NetFlow to the Orion server, and you have verified with a packet capture tool that the flow packets are being sent from the device and arriving at the Orion server (for more information, see NTA shows "Never" or a date in the past in Netflow Sources "Last Received Netflow"). The most likely cause of NTA failing to process flow packets is that the packets are not being written into the Orion database due to a firewall block.
Packet capture tools such as Wireshark operate on a lower level in the IP stack. Even though the capture shows the packets successfully sent and received, the firewall can subsequently block their processing at the application layer, before Orion NTA can work on them.
If you are running a firewall on the Orion server, follow the steps below:

1. Disable firewall on the NTA server.
2. View the NTA event log for a notification that Orion NTA is receiving flows from an unmonitored interface.
3. Click the link in the event log notification to add the device to NetFlow sources. Alternatively, you can manually add the device through the NetFlow Sources resource.
4. Enable the firewall, and create a rule to permit flows from the relevant interface.