Error "unable to open tcp connection with host 'hostname.example.com:YYYY': dial tcp XX.XX.XX.XX:YYYY: i/o timeout" during Autosys install using SQL Server
search cancel

Error "unable to open tcp connection with host 'hostname.example.com:YYYY': dial tcp XX.XX.XX.XX:YYYY: i/o timeout" during Autosys install using SQL Server

book

Article ID: 378973

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

AutoSys installation fails during creation of the database task with errors like below in the %TEMP%/cawa_installer.log

 

2024-10-01 06:58:10,115 [installer] DEBUG com.ca.autosys.db.install.CreateInstanceSchema(167) - SQL file is generated at: C:\Users\Administrator\AppData\Local\Temp\408288.tmp\seed_misc_tmp.sql
2024-10-01 06:58:10,115 [installer] INFO  com.ca.autosys.db.install.CreateInstanceSchema(168) - executeADBFile : aedbVersion-
2024-10-01 06:58:10,131 [installer] INFO  com.ca.autosys.db.install.CreateInstanceSchema(273) - Executing sql script : C:\Users\Administrator\AppData\Local\Temp\408288.tmp\seed_misc_tmp.sql
2024-10-01 06:58:10,147 [installer] DEBUG com.ca.autosys.db.connection.DBConnectionMSSQL(179) - Running command: sqlcmd -Usa -P "XXXXXX"-S"hostname.example.com:YYYY'" -dAutosys -m 11 -e -iC:\Users\Administrator\AppData\Local\Temp\408288.tmp\seed_misc_tmp.sql 
2024-10-01 06:58:10,147 [installer] DEBUG com.ca.autosys.db.connection.DBConnectionMSSQL(185) - executeSqlFileBySqlcmd- [Ljava.lang.String;@71afe0b8
2024-10-01 06:58:10,147 [installer] DEBUG com.ca.autosys.db.utils.CommandExecutor(22) - In execute Command
2024-10-01 07:01:23,911 [Thread-266697] DEBUG com.ca.autosys.db.utils.CommandExecutorThread(39) - unable to open tcp connection with host 'hostname.example.com:YYYY': dial tcp XX.XX.XX.XX:YYYY: i/o timeout 

 

Environment

Workload Automation AutoSys

Cause

SQL Server was configured with a very low query timeout value.

 

Resolution

Work with the Database Administrator to get the "Remote query timeout" increased to a higher value or set it to unlimited 

 

 

In the above screenshot (it is set to 600), set the value for Remote query timeout to 0 (unlimited) to resolve the issue. Work with the Database Administrator to schedule this change.