- The expected result is that the package execution should succeed or should fail with some errors. Additionally, the "Canceled" status should appear only for package executions that are explicitly stopped.
- This issue is more likely to occur when the SQL Server Database Engine instance in which the SSIS events are logged is under stressful conditions. The stressful conditions could include blocking, slow performance, or delays that are caused by SSISDB database growth.
When an SSIS event is configured to be logged in the SSISDB or MSDB tables, an Insert command writes the log event and performance statistics to those tables internally. When there are many parallel executions of SSIS packages, many parallel Insert commands are executed. Therefore, the time-out error is more likely to occur and cause the issue that is described in the "Symptoms" section.
Cumulative update information
Cumulative update package 3 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
- Try to run fewer SSIS packages or fewer tasks in parallel.
- Try to decrease the Logging Level parameter when you execute a package from Management Studio or from a SQL Server Agent job. For example, if you are using verbose logging, you can set the Logging Level parameter to Basic or None. If you are using the Logging settings from the SSIS package settings in SQL Server Data Tools designer, you can log the events to a text file instead of to the SSISDB or MSDB database tables.
Article ID: 2735763 - Last Review: 31 Aug 2012 - Revision: 1