Home > Success Center > Network Performance Monitor (NPM) > A transport-level error has occurred when receiving results from the server (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

A transport-level error has occurred when receiving results from the server (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

Updated December 9, 2016

Overview

Configuration Wizard fails with the following error:

A transport-level error has occurred when receiving results from the server (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

Environment

  • Orion Platform products
  • All NPM versions
  • All SAM versions
  • All NCM versions
  • All NTA versions
  • All UDT versions
  • All IPAM versions

Cause 

The cause is environmental and can be a number of things regarding the SQL server and configuration.

It can be a deadlock in the database and time outs need to be increased.

It can also be a network connectivity issue.

Resolution

  1. Enable Remote Connection, right click on the server node and select Properties:
    a. Go to the left tab of Connections and select “Allow remote connections to this server”.
    b. Make sure that MSDTC is enabled in the firewall.
  2. Enable SQL Server Browser Service:
    a. Go to All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager > SQL Server Browser.
    b. Right click on SQL Server Browser and click Enable.
  3. Create an exception of sqlbrowser.exe in Firewall, Windows Firewall may prevent sqlbrowser.exe to execute.
    a. Search for sqlbrowser.exe on your local drive where SQL Server is installed.
    b. Copy the path of the sqlbrowser.exe like C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe and create the exception of the file in Firewall.
  4. Go to All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager > Select TCP/IP.
    a. Right Click on TCP/IP and click Enable.
    b. Restart SQL Server Services for all the changes to take effect.
    c. Right click and go to the menu properties to select a location where the default port of SQL server can be changed.
  5. Set the commandtimeout property of the command object to an appropriate value. Use a value of zero to wait without an exception being thrown. (Increased the "connect timeout"  in connectionstring of app.config).
  6. Check the network cabling, the NIC for any driver updates or physical issues, or any network equipment that  the SQL server connects to such as the ports.

 

You must to post a comment.
Last modified
05:09, 28 Mar 2017

Tags

Classifications

Public