Updated November 18th, 2016
After you install the SolarWinds® NetFlow Traffic Analyzer (NTA) storage database on a separate server, you cannot connect to the NTA Flow Storage database from the server hosting the current NPM/NTA and Orion SQL database.
When you run the main poller configuration wizard and attempt to connect to the NetFlow Storage database on the separate server, the following error appears:
- Windows Server 2008 R2 SP3
- Windows Server 2012 and 2012 R2
- The NTA Flow Storage Database server is not properly installed.
- The SolarWinds NetFlow Storage Service is stopped or not running.
- The hostname or IP address is incorrect.
- The software and hardware firewall settings between the NTA Flow Storage database server and the Orion server are incorrect.
- Your antivirus software is blocking the connection to the NTA Flow Storage Database server.
- The SSL certificate is invalid.
- The NTA Flow Storage is accessing the wrong database and needs to use the same database as NPM.
- The version of the NTA Flow Storage Database does not match the version of the NTA Collector.
Perform the following steps:
- Check the server hosting the NTA Flow Storage database. Ensure that:
- The server is running and connected to your network.
- The server responds to PING commands.
- The NTA NetFlow Storage database is running.
- The hostname or IP address is correct.
- Verify that your antivirus software is not blocking your connection to the NTA Flow Storage database server.
- Check the firewall hardware and software settings between your NTA Flow Storage database server and your Orion server. If required, disable the firewall until the NTA installation is completed.
See Port Requirements for SolarWinds products for more information.
Check for certificate errors in the FastBigServerService.log file.
If you have a certificate problem, an error appears in the file, as shown below:
2015-12-11 18:52:18,765  ERROR SolarWinds.Netflow.FastBit.Server.Utils.OrionCertificateValidator - Rejecting certificate:
Because it does not match the Orion certificate:
If the SolarWinds-Orion certificate changed, resolve the invalid certificate on the main poller.
Resolve an invalid certificate on an existing installation
- Log in to the NTA Flow Storage Database server as an administrator.
- Navigate to the following directory:
c:\Program Files (x86)\SolarWinds\Orion\
- Copy the SolarWinds.ConfigurationWizard.Plugin.NetFlow.dll file and save it as:
- Delete the SolarWinds.ConfigurationWizard.Plugin.NetFlow.dll file.
- On the main poller, repair the SolarWinds Orion Core installation.
- Go to Add/Remove programs.
- Click SolarWinds Orion Core.
- Click Repair.
- When completed, complete the steps in the configuration wizard.
The wizard completes without the original NTA error.
- On the NTA Flow Storage database server, open the Microsoft Management Console (MMC) and navigate to Certificates > Local Computer > Personal.
- Delete the SolarWinds-Orion certificate on the server.
- Run the NTA Flow Storage database configuration wizard to sync the Orion database certificate.
When completed, the wizard generates the correct certificate.
- On the main poller, restore the SolarWinds.ConfigurationWizard.Plugin.NetFlow.dll file by removing backup from the file name.
- Run the configuration wizard again.
Resolve an invalid certificate on a new installation
Warning: This procedure applies to new installations with an empty NTA Flow Storage Database. Executing this procedure on an existing installation will erase your NetFlow data.
- Log in to the NTA Flow Storage database server.
- Unistall the NTA Flow Storage database.
- Log in to your NTA/NPM server.
- Uninstall NTA 4.0.
See Uninstalling NTA for instructions.
- Run the Configuration Wizard.
- Delete the SolarWinds-Orion certificate on the NTA Flow Storage database and NTA/NPM servers.
- On the NTA Flow Storage database server, open the Microsoft Management Console (MMC).
- Add the Certificates Snap-In to the MMC console.
See the Microsoft KB article How to: View Certificates with the MMC Snap-in (© 2017 Microsoft, available at https://msdn.microsoft.com, obtained on March 3, 2017.) for instructions.
- Navigate to Certificates (Local Computer) > Personal > Certificates and locate the SolarWinds-Orion certificate.
- Right-click the certificate and click Delete.
- Repeat steps a through e on the NTA/NPM server.
- On the primary poller, repair the SolarWinds Orion Core installation.
- Go to Add/Remove programs
- Click SolarWinds Orion Core.
- Click Repair.
- Complete the steps in the configuration wizard.
- Install the NTA Flow Storage database on the Flow Storage database server.
- Install the NTA main polling engine on the NTA/NPM server.
- Ensure that the NTA server is using the NPM database on the NTA Flow Storage database server. Otherwise, the system will generate a connectivity error if you try to use a new database targeted only for NTA.
Resolve an invalid certificate on a Additional Poller
See Additional Poller with NTA Certificate Issue for instructions.
UAC blocking connection to the remote server:
In some cases, the error displays during your NTA installation due to issues with user account control (UAC).
To resolve this issue:
- Right click the installer and select Run As Administrator.
- Enter the host name or IP address.
SolarWinds was running evaluation and activated licenses
1. In some circumstances customer evaluation is expired and when activating licenses this still generates errors that the database can't connect.
2. Run the Configuration Wizard against services, database, and website.
WireShark is showing traffic on port 50592 to 17777
1. Run a capture on both the Poller and flow storage server and validate traffic which way is failing.
2. Telnet to 17777 on both the poller from fsdb and from poller to fsdb.
3. If there is an issue with the traffic flow one thing to check is that one of the servers has the Microsoft Monitoring Agent installed, if it does uninstall it.
Security Providers Conflict in the Registry:
SolarWinds will work with SSL 2.0 & TLS 1.2 in the Protocols folder in the registry. If you see other protocols listed export them first. Check to see whihc are enabled as they should have a default key showing they are disabled. If they are not needed then delete them and test the connectivity with NTA.
Some hints would be to check Event Viewer System Logs:
Schannel errors event ID: 10013
Example of protocols listed in the registry:
GP 031017 - Placed image in pro content. Image needs to be replaced, or error needs to be placed as text within article.