0

for some time we have the problem that SSIS packages sometimes terminated unexpectedly - not reproducible. I have already found other similar problems and also checked the suggested solutions like checking the retention of the SSISDB or see if auto cleanup is set to enable in this regard:

Output atalog properties

The exact error message (found in the Windows event log) is:

The SSIS Execution Process could not write to the IS catalog: SERVERNAME:SSISDB Error details: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.; at System.Data.SqlClient.SqlConnection.OnError

SQL Server: Microsoft SQL Server 2019 (RTM-CU16-GDR) (KB5014353) - 15.0.4236.7 (X64) May 29 2022 15:55:47 Copyright (C) 2019 Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: )

Further info: Its our production environment which is a failover cluster with three nodes.

The error does not occur so far in our development and test environment (Non-cluster environments).

Anyone tips or could observe similar?

1
  • In the meantime, we have installed the CU18 and are observing. SQL Server: Microsoft SQL Server 2019 (RTM-CU18) (KB5017593) - 15.0.4261.1 (X64) Sep 12 2022 15:07:06 Copyright (C) 2019 Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: )
    – Denis1893
    Nov 30, 2022 at 16:28

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.