Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > NTA not collecting data - Unable to start listening on configured port 2055

NTA not collecting data - Unable to start listening on configured port 2055

Created by Brian O'Donovan, last modified by MindTouch on Jun 23, 2016

Views: 1,090 Votes: 1 Revisions: 3

Overview

NTA is not collecting data and the following message appears in the NTA.BusinessLayer.log file:

[Flow Listener on port 2055] WARN  SolarWinds.Netflow.Processing.PacketListener - Unable to start listening on configured port 2055. Waiting for 10sec for the port

Environment

 All NTA versions

Cause 

This is caused by another process using port 2055 and therefore NTA cannot use the port for listening.

Resolution

  1. Determine what application is using the port by running the following command from Administrator CMD prompt on the poller:
netstat -ano | find ":2055"
  1. Take note the Process ID.
  2. Stop the service using the port:
    1. Open Windows Task Manager and go to the Services tab.
    2. Sort by PID [Process ID].
    3. Locate the service with the PID from Step 3b and stop the service.

Note: If you cannot find a process in Task manager that matches the PID from the netstat command, it is likely that there is a service that did not stop properly that is still using the port. In this instance a reboot of the server will clear the service.

 

Last modified

Tags

Classifications

Public