Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Netflow Traffic Analyzer (NTA) > ERROR SolarWinds.Netflow.Processing.Workflow.NetFlowPacketWorkflowManager - Error flushing data System.ServiceModel.FaultException: Exception 'SqlException' while resolving string IDs

ERROR SolarWinds.Netflow.Processing.Workflow.NetFlowPacketWorkflowManager - Error flushing data System.ServiceModel.FaultException: Exception 'SqlException' while resolving string IDs

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 7 Votes: 0 Revisions: 9

Issue:

The netflow data fails with the error in the flow storage database (FSDB):

ERROR SolarWinds.Netflow.Processing.Workflow.NetFlowPacketWorkflowManager - Error flushing data
System.ServiceModel.FaultException: Exception 'SqlException' while resolving string IDs: Could not allocate space for object 
'dbo.NetFlowFastBitStringHeap'.'PK_NetFlowFastBitStringHeap' in database 'SolarWindsOrion' because the 'PRIMARY' filegroup is full.

Cause:

  • The Orion application server and the flow storage server are pointing to two different SQL server instances.

 

Resolution:

The Orion application and flow storage servers need to be pointing to the same SQL server instance. To confirm this configuration, do the following steps:

  1. Go to Start > All programs > SolarWinds Orion > Configuration and Auto-Discovery > Configuration Wizard.
  2. Click Next to run the wizard. The initial screens will display the SQL instance name of the Orion database.
  3. Take note of the SQL instance name of the Orion database, and then click Cancel.
  4. Click Start > All Programs > SolarWinds Orion > NetFlow Traffic Analysis > NTA Flow Storage Configurator.
  5. In the flow storage configuration section, specify the same SQL instance name of the Orion database which was obtained in Step 3.
  6. Go to SQL programs folder, and check if the MDF file is full, i.e. File Max Filesize of MDF is reached.
  7. Verify if the netflow screens of the Web Console are populated with flow data.

 

Applies to:  NTA v4.0 and later.

Last modified
20:31, 22 Jun 2016

Tags

Classifications

Public