DUAS: Job Abort with "(WinSock): Address already in use"
book
Article ID: 112293
calendar_today
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
After patching a Windows Server with July 2018 Monthly updates, some Uprocs abort with the following kind of errors
In Job Log: ############# Error connecting to the IO server: o_connect_auth returns -1: (WinSock): Address already in use Error getting conf from IO server: o_get_conf_from_io returns -1 Cannot load environment The syntax of the command is incorrect. #############
In universe.log: ############# |ERROR|X|END|pid=p.t| o_connect_auth | k_connect_auth_timeout returns error [200] |ERROR|X|END|pid=p.t| u_io_callsrv_connect_r | Error connecting to target IO server: (WinSock): Address already in use (connect returns error) #############
Environment
All Windows
Cause
Regression introduced in Windows Update delivered in July Patches that would impact every application using TCP/IP like Dollar Universe.
Resolution
Upgrade to a superior version the impacted Windows servers as explained here: https://blogs.msdn.microsoft.com/psssql/2018/07/26/july-10-2018-windows-updates-cause-sql-startup-issues-due-to-tcp-port-is-already-in-use-errors/
As a general rule, August 2018 Monthly Rollup Patch fixes the regression.
Additional Information
In case you need more information about the patch needed, please open a case with Microsoft. Example, for Windows 2008 R2, KB4338821 is the patch causing this issue and KB4343900 (August Monthly Rollup) will resolve it