We have Data Services Designer Version is 14.2.6.1113
We have CMS & Repositories in both SQL Server Version is 2014 & 2017
All of these are hosted in AWS.
From last few days after the Job Server restart, all our jobs are failing with below error.
520 2224 DBS-070401 2/21/2019 10:59:01 AM ODBC data source <DB Server> error message for operation <SQLFetchScroll>: 520 2224 DBS-070401 2/21/2019 10:59:01 AM <[Microsoft][SQL Server Native Client 11.0]TCP Provider: A connection attempt failed because the connected party did not 520 2224 DBS-070401 2/21/2019 10:59:01 AM properly respond after a period of time, or established connection failed because connected host has failed to respond. 520 2224 DBS-070401 2/21/2019 10:59:01 AM [Microsoft][SQL Server Native Client 11.0]Communication link failure 520 2224 DBS-070401 2/21/2019 10:59:01 AM [Microsoft][SQL Server Native Client 11.0]Protocol error in TDS stream>. 520 2224 CON-120108 2/21/2019 10:59:01 AM |Dataflow DF_ETL_Validate_LOB_Version 520 2224 CON-120108 2/21/2019 10:59:01 AM Database connection to <DB Server> is broken. Retrying with retry count <6> and sleep 520 2224 CON-120108 2/21/2019 10:59:01 AM interval <10> seconds. 520 2224 CON-120109 2/21/2019 10:59:01 AM |Dataflow DF_ETL_Validate_LOB_Version 520 2224 CON-120109 2/21/2019 10:59:01 AM Database connection to <DB Server> was broken. Successfully obtained connection after <1> 520 2224 CON-120109 2/21/2019 10:59:01 AM attempts.
Or
ODBC data source <DB Server> error message for operation <SQLFetch>: <[Microsoft][SQL Server Native Client 11.0]TCP Provider: The semaphore timeout period has expired. [Microsoft][SQL Server Native Client 11.0]Communication link failure>.
any help is appreciated
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.