autosys SP1 cum2 patch on mssql server on Linux fails TCP Provider: Error code 0x102.

Products

• Autosys Workload Automation

Issue/Introduction

./Install_INCR.sh -t S -f 99111248 -d MSQ -n XXXXX -u sa -s XXX.XXXXX.com

************ Testing the database connection to XXXX.XXXXX.com ************

perl: warning: Setting locale failed.

perl: warning: Please check that your locale settings:

 LANGUAGE = (unset),

 LC_ALL = (unset),

 LC_CTYPE = "UTF-8",

 LANG = "en_US.UTF-8"

    are supported and installed on your system.

perl: warning: Falling back to the standard locale ("C").

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login timeout expired.

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x102.

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

RefreshAEDB:  XXXX.XXXXXX.com/sa/password combination is invalid.

Error. Retrieve the log file at /tmp/WAAE_install_Jun_02_00_34.log.

Environment

Release : 12.0

Component : CA Workload Automation AE (AutoSys)

Resolution

Ran sqlcmd from /opt/mssql-tools/bin

./sqlcmd -S XXXXX.XXXX.com -U username -d XXXX

Then we got the same error

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login timeout expired.

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x102.

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

We then added the port

./sqlcmd -S XXXX.XXXXX.com,1441 -U username -d XXXXXX

This time the error was different it complained about sa password.

After DBA fixed the issue with 'sa' password, retried the command with the port number and patching is successful.

./Install_INCR.sh -t S -f 99111248 -d MSQ -n XXXXX -u sa -s XXXXX.XXXX.com,1441