ssis timeouts

  • Hi Experts,

    Need small help on this SSIS issue. Check if there is any workaround or better way to alleviate the issues.

    We have SSISDB Catalog configuration in place and we see lot of timeout issues.

    When I dig deeper we came to know we are hitting the above bug.

    Initially, we thought the queries are getting timed out due to performance issues for heavy blocking and so we have changed the remote query timeout.

    But in reality we are seeing below errors.

    package_name event_name message_source_name message

    Master.dtsx OnError Create Package Execution Create Package Execution:Error: Executing the query "EXECUTE [SSISDB].[catalog].[create_execution] ..." failed with the following error: "The operation failed because the execution timed out.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Master.dtsx OnError Create Package Execution Create Package Execution:Error: Executing the query "EXECUTE [SSISDB].[catalog].[create_execution] ..." failed with the following error: "The operation failed because the execution timed out.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Master.dtsx OnError Create Package Execution Create Package Execution:Error: Executing the query "EXECUTE [SSISDB].[catalog].[create_execution] ..." failed with the following error: "The operation failed because the execution timed out.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Basically, we are hitting this BUG in our environment.

    https://connect.microsoft.com/SQLServer/feedback/details/783291/ssis-package-fails-to-start-application-lock-timeout-in-ssisdb-catalog-create-execution

    Environment details

    =======================

    SQL Server details

    ===================

    Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)

    Feb 15 2016 12:12:43

    Copyright (c) Microsoft Corporation

    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    OS information

    =====================

    OS Name Microsoft Windows Server 2012 R2 Datacenter

    Version 6.3.9600 Build 9600

    Other OS Description Not Available

    OS Manufacturer Microsoft Corporation

    System Name xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

    System Manufacturer Microsoft Corporation

    System Model Virtual Machine

    System Type x64-based PC

    System SKU Unsupported

    Processor Intel(R) Xeon(R) CPU E5-4650L 0 @ 2.60GHz, 2600 Mhz, 8 Core(s), 8 Logical Processor(s)

    Installed Physical Memory (RAM) 56.0 GB

    Total Physical Memory 56.0 GB

    Available Physical Memory 21.1 GB

    Total Virtual Memory 75.9 GB

    Available Virtual Memory 38.2 GB

    Page File Space 19.9 GB

    Thanks,

    Sam

  • Hi Experts,

    Any thoughts??

  • vsamantha35 (9/24/2016)


    Hi Experts,

    Any thoughts??

    Why not apply SP2 since it addresses some issues with SSISDB?

    https://support.microsoft.com/en-us/kb/2958429

    Sue

  • Thanks Sue. Will do that and monitor.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply