How To: Fix Velocity installation failure in Server machine or Client machine or Split Server

Owned by Anand Rajaraman
Last updated: Dec 13, 2021 by Christopher Karr (Unlicensed)
3 min read

Problem:

  • Velocity client installation fails when manually enter the Server name and SQL Server location

    In Install Options for Client while selecting the Velocity Server location and the SQL Server location and clicking Next.

An error message like the below one shows:

Solution

  1. Launch the Windows Service Manager (services.msc) application.

  2. Start SQL Server Browser service on the Velocity Data Server. This allows locating the Velocity Client installations on SQL Server. Click Start.

    Note: Based on your MS SQL Server 2019, 2017, 2016, 2014, 2012 versions, you must enable the service start mode in SQL Server Browser Properties.

  3. Enable the SQL Server network protocols, Named Pipes, and TCP/IP for SQL in the SQL Server Configuration Manager as shown below.

  4. Restart the SQL server service after clicking OK/Apply.

  5. Turn ON network sharing. Refer https://www.webnots.com/guide-to-windows-10-network-and-sharing-center/ for more details.
    Note: Make sure you can ping and get a response from the SQL server and check your firewall settings. Consult your IT department for policies. Refer https://www.sqlshack.com/how-to-connect-to-a-remote-sql-server/ for more details.

  6. Enable SQL Server to allow remote connections to the server that you connect and click OK as shown below.

Problem:

  • Not able to browse network and pick a server.  Installation proceeds successfully after manually entering Velocity Server name and SQL Server name. 

Solution:

  1. Go to Control Panel-> Network and Internet-> Network and Sharing Center in Windows 10.

  2. Click Change advanced sharing settings.

     

  3. In Advanced sharing settings, expand Guest or Public (current profile) to select Turn on network discovery and click Save changes as shown.

  4. From the Services panel, enable Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host Startup types to Automatic. Click OK.
    An example of Function Discovery Provider Host startup type to automatic is given below.

  5. Reboot the system. After restart open File Explorer and click on 'Network' to view all the systems on your network.

  • Now to make systems discoverable in Server machines:

SMBv1 protocol is turned off by Windows Update for security reasons, therefore we will manually enter the server name in the installer rather than continue the above workaround.

  1. From Control Panel open Programs and Features.

  2. Click Turn Windows features on or off.

  3. Scroll down to Check the SMB 1.0/CIFS File Sharing Support features listed and click OK.

  4. Reboot the system. After the restart, open File Explorer and click on 'Network' to view all the systems on your network.