|
| 1 | +--- |
| 2 | +title: "Troubleshooting package execution in SSIS integration runtime | Microsoft Docs" |
| 3 | +description: "This article provides the troubleshooting guidance for SSIS Package Execution in SSIS Integration Runtime" |
| 4 | +services: data-factory |
| 5 | +documentationcenter: "" |
| 6 | +ms.service: data-factory |
| 7 | +ms.workload: data-services |
| 8 | +ms.tgt_pltfrm: na |
| 9 | + |
| 10 | +ms.topic: conceptual |
| 11 | +ms.date: 04/15/2019 |
| 12 | +author: wenjiefu |
| 13 | +ms.author: wenjiefu |
| 14 | +ms.reviewer: sawinark |
| 15 | +manager: craigg |
| 16 | +--- |
| 17 | + |
| 18 | +# Troubleshooting package execution in SSIS integration runtime |
| 19 | + |
| 20 | +This article includes the most common errors that you might hit when executing SSIS packages in SSIS Integration Runtime, the potential causes, and actions to solve the errors. |
| 21 | + |
| 22 | +## Where can I find logs for troubleshoot |
| 23 | + |
| 24 | +* The ADF Portal can be used to check the output of the SSIS Package Execution Activity including the execution result, error messages, and operation ID. Details can be found at [Monitor the pipeline](how-to-invoke-ssis-package-ssis-activity.md#monitor-the-pipeline) |
| 25 | + |
| 26 | +* The SSIS Catalog (SSISDB) can be used to check the detail logs for the execution. Detail can be found at [Monitor Running Packages and Other Operations](https://docs.microsoft.com/sql/integration-services/performance/monitor-running-packages-and-other-operations?view=sql-server-2017) |
| 27 | + |
| 28 | +## Common errors, causes, and solution |
| 29 | + |
| 30 | +### Error message: `"Connection Timeout Expired."` or `"The service has encountered an error processing your request. Please try again."` |
| 31 | + |
| 32 | +* Potential cause & recommended action: |
| 33 | + * The Data Source/Destination is overloaded. Check the load on your Data Source/Destination and see whether it has enough capacity. For example, if Azure SQL is used, it's suggested to consider scale up if the Database is likely to time out. |
| 34 | + * The network between SSIS Integration Runtime and the Data Source/Destination is unstable, especially when the connection is cross-region or between on-premise and azure. It's suggested to apply retry pattern in SSIS Package by following steps: |
| 35 | + * Make sure your SSIS Packages can rerun on failure without side effect (For example. data loss, data dup...) |
| 36 | + * Configure the **Retry** and **Retry interval** of Execute SSIS Package Activity in the General Tab |
| 37 | +  |
| 38 | + * For ADO.NET and OLEDB Source/Destination component, ConnectRetryCount and ConnectRetryInterval can be set in the Connection Manager in SSIS package or SSIS Activity |
| 39 | + |
| 40 | +### Error message: `"ADO NET Source has failed to acquire the connection '...' with the following error message: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible."` |
| 41 | + |
| 42 | +* Potential cause & recommended action: |
| 43 | + * This issue usually means the Data Source/Destination is inaccessible from SSIS Integration Runtime, which can be caused by different reasons: |
| 44 | + * Make sure you're passing the Data Source/Destination Name/IP correctly |
| 45 | + * Make sure the firewall is set properly |
| 46 | + * Make sure your vNet is configured properly if your Data Source/Destination are in on-premise. |
| 47 | + * You can verify whether the issue is from vNet configuration by provisioning an Azure VM in the same vNet. And then check whether the Data Source/Destination can be accessed from the Azure VM |
| 48 | + * You can find more details about using vNet with SSIS Integration Runtime at [Join an Azure-SSIS integration runtime to a virtual network](join-azure-ssis-integration-runtime-virtual-network.md) |
| 49 | + |
| 50 | +### Error message: "`ADO NET Source has failed to acquire the connection '...' with the following error message: "Could not create a managed connection manager.`" |
| 51 | + |
| 52 | +* Potential cause & recommended action: |
| 53 | + * The ADO.NET provider used in the package isn't installed in SSIS Integration Runtime. You can install the provider by using the Custom Setup. More details about Custom Setup can be found in [Customize setup for the Azure-SSIS integration runtime](how-to-configure-azure-ssis-ir-custom-setup.md) |
| 54 | + |
| 55 | +### Error message: "`The connection '...' is not found`" |
| 56 | + |
| 57 | +* Potential cause & recommended action: |
| 58 | + * This error may be because a known issue in old version SSMS. If the package contains a custom component (For example, SSIS Azure Feature Pack or 3rd party components) which isn't installed on the machine where SSMS is used to do the deployment, the component will be removed by SSMS and cause the error. Upgrade [SSMS](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms) to the latest version that has the issue fixed. |
| 59 | + |
| 60 | +### Error message: "There is not enough space on the disk" |
| 61 | + |
| 62 | +* Potential cause & recommended action: |
| 63 | + * This error means the local disk is used up in SSIS Integration Runtime node. Check whether your package or Custom Setup would consume many disk spaces. |
| 64 | + * If the disk is consumed by your package, it will be freed up after the package execution finishes. |
| 65 | + * If the disk is consumed by your Custom Setup, you'll need to stop SSIS Integration Runtime, modify your Script, and start the SSIS Integration Runtime again. The whole Azure Blob Container you specified for Custom Setup will be copied over to SSIS IR node, so verify whether there is any unnecessary content under that container. |
| 66 | + |
| 67 | +### Error message: "Cannot open file '...'" |
| 68 | + |
| 69 | +* Potential cause & recommended action: |
| 70 | + * This error occurs when package execution can't find file in local disk in SSIS Integration Runtime. |
| 71 | + * It's not suggested to use absolute path in package executing in SSIS Integration Runtime. Use current execution working directory (.) or temp folder (%TEMP%) instead. |
| 72 | + * If it's needed to persist some files on SSIS Integration Runtime nodes, it's suggested to prepare the files through [Customize Setup](how-to-configure-azure-ssis-ir-custom-setup.md). All the files in the execution working directory will be cleaned up after the execution is finished. |
| 73 | + * Another option is to use Azure File instead of storing the file in SSIS Integration Runtime node. More detail can be found at [https://docs.microsoft.com/sql/integration-services/lift-shift/ssis-azure-files-file-shares?view=sql-server-2017#use-azure-file-shares](https://docs.microsoft.com/sql/integration-services/lift-shift/ssis-azure-files-file-shares?view=sql-server-2017#use-azure-file-shares). |
| 74 | + |
| 75 | +### Error message: "The database 'SSISDB' has reached its size quota" |
| 76 | + |
| 77 | +* Potential cause & recommended action: |
| 78 | + * The SSISDB created in the Azure SQL or Managed Instance when creating SSIS Integration Runtime has reached its quota. |
| 79 | + * Consider increasing the DTU of your Database to resolve this issue. Details can be found at [https://docs.microsoft.com/azure/sql-database/sql-database-resource-limits-logical-server](https://docs.microsoft.com/azure/sql-database/sql-database-resource-limits-logical-server) |
| 80 | + * Check whether your Package would generate many logs. If so, elastic job can be configured to clean up these logs. Refer to [Clean up SSISDB logs with Azure Elastic Database Jobs](how-to-clean-up-ssisdb-logs-with-elastic-jobs.md) for detail. |
| 81 | + |
| 82 | +### Error message: "The request limit for the database is ... and has been reached." |
| 83 | + |
| 84 | +* Potential cause & recommended action: |
| 85 | + * If many packages are executing in parallel in SSIS Integration Runtime, this error may occur because the request limitation of SSISDB is hit. Consider increasing the DTC of your SSISDB to resolve this issue. Details can be found at [https://docs.microsoft.com/azure/sql-database/sql-database-resource-limits-logical-server](https://docs.microsoft.com/azure/sql-database/sql-database-resource-limits-logical-server) |
| 86 | + |
| 87 | +### Error message: "SSIS Operation failed with unexpected operation status: ..." |
| 88 | + |
| 89 | +* Potential cause & recommended action: |
| 90 | + * The error is mostly caused by a transient error, so try to rerun the package execution. It's suggested to apply retry pattern in SSIS Package by following steps: |
| 91 | + * Make sure your SSIS Packages can rerun on failure without side effect(For example, data loss, data dup...) |
| 92 | + * Configure the **Retry** and **Retry interval** of Execute SSIS Package Activity in the General Tab |
| 93 | +  |
| 94 | + * For ADO.NET and OLEDB Source/Destination component, ConnectRetryCount and ConnectRetryInterval can be set in the Connection Manager in SSIS package or SSIS Activity |
| 95 | + |
| 96 | +### Error message: "There is no active worker." |
| 97 | + |
| 98 | +* Potential cause & recommended action: |
| 99 | + * This error usually means the SSIS Integration Runtime is in an unhealthy status. Check Azure portal for the status and detail errors: [https://docs.microsoft.com/azure/data-factory/monitor-integration-runtime#azure-ssis-integration-runtime](https://docs.microsoft.com/azure/data-factory/monitor-integration-runtime#azure-ssis-integration-runtime) |
| 100 | + |
| 101 | +### Error message: "Your integration runtime cannot be upgraded and will eventually stop working, since we cannot access the Azure Blob container you provided for custom setup." |
| 102 | + |
| 103 | +* This error occurs when SSIS Integration Runtime can't access the storage configured for Custom Setup. Check whether the SAS Uri you provided is valid and hasn't expired. |
| 104 | + |
| 105 | +### Package takes unexpected long time to execute |
| 106 | + |
| 107 | +* Potential cause & recommended action: |
| 108 | + * Too many package executions have been scheduled on the SSIS Integration Runtime. In this case, all these executions will be waiting in a queue for their turn to execute. |
| 109 | + * Max Parallel Execution Count per IR = Node Count * Max Parallel Execution per Node |
| 110 | + * Refer to [Create Azure-SSIS Integration Runtime in Azure Data Factory](create-azure-ssis-integration-runtime.md) for how to set the Node Count and Max Parallel Execution per Node. |
| 111 | + * SSIS Integration Runtime is stopped or in an unhealthy status. Check [Azure-SSIS integration runtime](monitor-integration-runtime.md#azure-ssis-integration-runtime) for how to check the SSIS Integration Runtime status and errors. |
| 112 | + * It's suggested to set the timeout if you're sure the package execution should be finished in a certain time: |
| 113 | +  |
| 114 | + |
| 115 | +### Poor performance in package execution |
| 116 | + |
| 117 | +* Potential cause & recommended action: |
| 118 | + |
| 119 | + * Check if the SSIS Integration Runtime is in the same region as the Data Source and Destination. |
| 120 | + |
| 121 | + * Enable "Performance" Logging Level |
| 122 | + |
| 123 | + You can set the Logging Level of package execution to "Performance" to collect more detail duration information for each component in the execution. Details can be found at: [https://docs.microsoft.com/sql/integration-services/performance/integration-services-ssis-logging](https://docs.microsoft.com/sql/integration-services/performance/integration-services-ssis-logging) |
| 124 | + |
| 125 | + * Check IR node performance in IR monitor page in Azure portal. |
| 126 | + * How to monitor SSIS Integration Runtime: [Azure-SSIS integration runtime](monitor-integration-runtime.md#azure-ssis-integration-runtime) |
| 127 | + * The history CPU/Memory usage of SSIS Integration Runtime is available at the Metrics of the Data Factory in Azure portal |
| 128 | + |
0 commit comments