vRanger GUI fails to open: Could not connect to service. (4032822)

vRanger GUI fails to open and the vRanger service are confirmed to be running.  Following error can be found running vRanger service in debug mode.

For debug mode:
vRanger 5.3.1 to 6.1:  From an administrative command prompt run the following to get details:

1. cd "C:\Program Files (x86)\Quest Software\vRanger\Service" (Change the drive letter and path if vRanger is not installed in the default location.)
2. Vizioncore.vRanger.Service.exe DEBUG

vRanger 7.0-7.5.1:  From an administrative command prompt run the following to get details:

1. cd "C:\Program Files\Dell\vRanger" (Change the drive letter and path if vRanger is not installed in the default location.)
2. Vizioncore.vRanger.Service.exe DEBUG

vRanger 7.6.x+:  From an administrative command prompt run the following to get details:

1. cd "C:\Program Files\Quest\vRanger" (Change the drive letter and path if vRanger is not installed in the default location.)
2. Vizioncore.vRanger.Service.exe DEBUG

"A network-related or instance specific error occurred while establishing a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL server is configured to allow remote connections. (provider: Named Pipes Provider, error:40 - Could not open a connection to SQL Server)."

A.  If the database is local then ensure that the "SQL Server (VRANGERPRO)" service is running.

B.  Confirm that the user for the vRanger services has rights to access the database.  Connect to SQL instance with SQL Server Management Studio. Open Security - Logins. Select user and right click to confirm properties. Under Server roles confirm public and sysadmin are checked.

C.  If the database is running on a remote server confirm that the server is running and can be reached. Confirm SQL server services are running.