Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > FATAL SolarWinds.Netflow.Processing.AppContext - FastBit Server version '4220' doesn't match with expected server version '4192' for this client. Please upgrade FastBit server to the required version

FATAL SolarWinds.Netflow.Processing.AppContext - FastBit Server version '4220' doesn't match with expected server version '4192' for this client. Please upgrade FastBit server to the required version

Updated March 10, 2017

Overview

This article provides brief information and a resolution to the issue when the NTA Collector status is down due to lack of connectivity to the NTA Flow Storage Database. 

 

This is seen in the NTA Settings page under the Collectors heading, or in the Last 25 Traffic Events on the NTA Summary Page. See the following sample:  

 

The error in the NTA.BusinessLayer.log states the following:

FATAL SolarWinds.Netflow.Processing.AppContext - FastBit Server version '4220' doesn't match with expected server version '4192' for this client. Please upgrade FastBit server to the required version

This error appears in conjunction with the following error message in the NTA.BusinessLayer.log:

 

INFO Solarwinds.Netflow.Processing.AppContext - Fastbit server didn't respond or version mismatch.  Waiting for 30s...

Environment

NTA version 4.2.x 

Cause 

There is a version mismatch between the NTA Flow Storage Database and the NTA Collector versions as confirmed in the NTA.BusinessLayer.log and FastbitServerService.log files:

 

NTA.BusinessLayer.log:

*** SolarWinds NTA v4.2.0.1585, .Net Runtime v4.0.30319 ***
*** Assembly SolarWinds.Netflow.Common, Version=4.2.0.1585, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Orion.Proxy.I18N, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly NetFlowService, Version=4.2.0.1585, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Netflow.Processing, Version=4.2.0.1649, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Orion.Common, Version=2.0.0.0, Culture=neutral, PublicKeyToken=316e86daa515e407, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Netflow.Utils, Version=4.2.0.1585, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Netflow.FastBit.Contract, Version=4.2.0.1585, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***

 

FastbitServerService:

SolarWinds Netflow FastBit Server Service v4.2.2.3106, .Net Runtime v4.0.30319 ***
*** Assembly SolarWinds.Netflow.FastBit.Server.Service, Version=4.2.2.3106, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Netflow.Utils, Version=4.2.2.3106, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Netflow.FastBit.Contract, Version=4.2.2.3106, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***

Resolution

Install the same version on the NTA Collector and the NTA Flow Storage Database, and vice versa.

See the following articles for more information: 

 

 

 

Last modified

Tags

Classifications

Public