Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NetFlow Collector service is down after migrating the Orion database

NetFlow Collector service is down after migrating the Orion database

Updated June 27, 2017

Overview

This article describes an issue where the NetFlow Collector services are down but all NetFlow services are up after migrating the Orion database. The configuration wizard completes successfully on the NetFlow storage database and the charts display data.

The NTA business layer log displays the following error (C:\ProgramData\Solarwinds\Logs\NTA):

2017-06-02 10:04:43,117 [10] INFO  SolarWinds.Netflow.Processing.AppContext - Time on NetFlow Receiver Service [xxx xxx xxx ] is: 6/2/2017 10:04:43 AM. DB server time is: 6/2/2017 10:06:23 AM. The difference is: 100.8s. The thresholds are 60s for warning, 300s for error.

Environment

All NTA versions

Cause 

This issue is caused when there is a time difference of more than 300 seconds between the servers.

Resolution

Make sure that the Orion SQL server, main Orion polling engine, and the NetFlow storage database time are synchronized.

 

Last modified
19:15, 26 Jun 2017

Tags

Classifications

Public