Orion Configuration Wizard fails with a transport-level error

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.) Check the SQL server configuration, firewall and network connectivity.

1. 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.
2. It can also be caused when the Orion server is unable to resolve the IP address from the SQL server's hostname.

Resolution 1:

1. Enable Remote Connection, right-click on the server node, and select Properties:
2. a. Go to the left tab of Connections and select "Allow remote connections to this server."
3. b. Make sure that MSDTC is enabled in the Firewall.
4. Enable SQL Server Browser Service:
5. a. Go to All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager > SQL Server Browser.
6. b. Right-click on SQL Server Browser and click Enable.
7. Create an exception of sqlbrowser.exe in Firewall; Windows Firewall may prevent sqlbrowser.exe from executing.
8. a. Search for sqlbrowser.exe on your local drive where SQL Server is installed.
9. 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.
10. Go to All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager > Select TCP/IP.
11. a. Right Click on TCP/IP and click Enable.
12. b. Restart SQL Server Services for all the changes to take effect.
13. c. Right; click and go to the menu properties to select a location where the default port of SQL Server can be changed.
14. Set the commandtimeout property of the command object to an appropriate value. Use a value of zero to wait without exception being thrown. (Increased the "connect timeout" in the connection string of app.config).
15. 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.

Resolution 2:

Run Configuration Wizard, and instead of indicating the hostname or FQDN of the SQL server, input the IP address
Kindly follow this format:

tcp:sqlipaddress,portnumber
tcp:x.x.x.x,pppp

Sample Image:

NOTE: Ensure to run Configuration Wizard on "Database", "Website" and "Services".

The reason behind this is that there are SQL connection strings within Website and Services; thus, there is a need to run against all 3
It also exhibits an issue with DNS in your environment, and you should be working on rectifying it. If there is a need (in the future) to leverage DNS for failover, etc., there will be issues.