Error during step 2 of installation: Failed to locate OSQL

Alerts and notices

Situation

This error can be received during step 2 of the installation process when connecting the application to your SQL Server database.

Error message

Connection failed attempting to connect to SQL Server (). Please run this setup again and specify the correct database server login name and password or use Windows authentication and make sure you are logged on to the correct Windows account.

See error log entries below:

Checking if MSSQLSERVER service is installed...
Result: 0
Checking if MSSQLSERVER service starts automatically.
Result: 0:2
Checking if MSSQLSERVER service is running...
Result: 0:1
Checking if SQLBrowser service is installed...
Result: 0
Checking if SQLBrowser service starts automatically.
Result: 0:2
Checking if SQLBrowser service is running...
Result: 0:1
Searching for OSQL.EXE...
Attempting to locate OSQL in 32-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
Attempting to locate OSQL in 64-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
Attempting to locate OSQL in 32-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup
Attempting to locate OSQL in 64-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup
Attempting to locate OSQL in 32-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup
Attempting to locate OSQL in 64-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup
Attempting to locate OSQL in 32-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\ClientSetup
Attempting to locate OSQL in 64-bit registry key SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\ClientSetup
Attempting to locate OSQL in C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn...
Attempting to locate OSQL in C:\Program Files\Microsoft SQL Server\80\Tools\Binn...
Attempting to locate OSQL in C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn...
Attempting to locate OSQL in C:\Program Files\Microsoft SQL Server\90\Tools\Binn...
Attempting to locate OSQL in C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn...
Attempting to locate OSQL in C:\Program Files\Microsoft SQL Server\100\Tools\Binn...
Attempting to locate OSQL in C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn...
Attempting to locate OSQL in C:\Program Files\Microsoft SQL Server\110\Tools\Binn...
Attempting to locate OSQL in C:\Program Files (x86)\Microsoft SQL Server...
Attempting to locate OSQL in C:\Program Files\Microsoft SQL Server...
Result: The OSQL program was not found. It does not appear that any Microsoft SQL Server 2000, 2005, 2008 or 2012 instances are properly installed.
Attempting to connect to SQL Server...
Result: error,
Failed. Attempting to use ExecWait...
Execute: "The OSQL program was not found. It does not appear that any Microsoft SQL Server 2000, 2005, 2008 or 2012 instances are properly installed." -E -S "SQLSRV01" -Q "PRINT 'CONNECTION ESTABLISHED'" -n

Right-click here to copy details to clipboard for customer support.
Connection failed attempting to connect to SQL Server ().
Please run this step again and specify the correct database server login name and password or use Windows authentication and make sure you are logged on to the correct Windows account.

Resolution

This is caused by an incomplete registry key. Use the following steps to correct the entry.

Thomson Reuters recommends consulting a qualified IT professional before making changes to the registry as problems with the registry can cause serious problems with the operating system. It is also recommended that you backup the registry before making changes to it.

  1. Click the Windows Start button and choose Run.
  2. Enter REGEDIT in the Open field, and click the OK button.
  3. Navigate to the following location: HKey_Local_Machine\Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup

    Note : 64-bit installations of SQL may need to check HKey_Local_Machine\Software\Wow6432Node\Microsoft\Microsoft SQL Server\ for these registry keys

    What if I don't have an 80 registry folder?

    If you do not have the 80 folder in your registry you may need to use the lowest number available in the HKey_Local_Machine\Software\Microsoft\Microsoft SQL Server\ directory. Seek assistance from your IT professional if you are unable to locate this registry.
  4. Double-click on SQLPath.
  5. Edit the existing path in the Value data field so it reads as follows:

    X:\Program Files\Microsoft SQL Server\\Tools, where X represents the drive letter the SQL instance is installed on, and represents the number assigned by Microsoft for the version of SQL you have installed, to determine this version, see Microsoft's Shared Files for All Instances of SQL Server External link . (What's this?)

    This icon appears alongside links to resources that are not developed or maintained by Thomson Reuters. We provide access to these resources for your convenience, but we are not responsible for their accuracy. If you need additional assistance, please consult your qualified technician and/or the vendor who developed the resource.
    .