During installation of Workload Automation AE on Windows 2016 with SQL Server 2016, an error is encountered indicating osql cannot be found.
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
The issue normally happens when the Database is running on a different server and we have client tools installed on the Autosys server.
Recent versions of SQL Server do not provide OSQL.EXE in their set of files when the Client Tools are installed.
The OSQL.EXE file is installed on the full SQL Server installation.
From the computer holding the full SQL Server installation you might be able to copy just the following two files to the remote engine server (place them in the same directory) and have it work:
C:\Program Files\Microsoft SQL Server\110\Tools\Binn\OSQL.EXE
C:\Program Files\Microsoft SQL Server\110\Tools\Binn\Resources\1033\osql.rll
To test the connection Install the Microsoft SQL Server Management Studio on the server and rerun the installation script for the Workload Automation AE product.