SSIS packages failing with a status "ended unexpectedly" (SSL/TLS timeout ?)

• Eric M Russell

  SSC Guru

  Points: 125604

  More actions

  October 29, 2025 at 3:59 pm

  #4678917

  We have an issue where SSIS packages are failing with a status of "ended unexpectedly" within 30 - 60 seconds after scheduled start. This issue is transient and not specific to any SSIS package. After rebooting the server, packages will run normally for a couple of weeks but then start to fail a few at a time, with failures becoming more frequent until another server reboot.

  For these failed runs, no messages are logged in [operation_messages], so no detail is available.

  Re-starting SQL Server service or SSIS runtime (MsDtsServer) alone does not resolve, only restarting Windows server will temporarily resolve for about a week or two.

  Installing latest CU did not resolve, and we're currently running on:

  Windows Server 2022 Standard - Build 20348

  SQL Server 2019 Enterprise - CU32

  When the issue presents itself, there is no evidence of memory pressure, high CPU load, or high I/O load, and I don’t see any recent SSIS dump files.

  However, looking at Windows event log, there does appear to be a correlation with the following error:

  The SSIS Execution Process could not write to the IS catalog: MYSERVER:SSISDB Error details: Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=14684; handshake=0; ;

  I'm pretty sure this has something to do with SSL/TLS configuration or some accumulating low resource, but I'm not sure how to address this.

  Any ideas?

   

   

   

   

  "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho