Azure Data Factory - Self Hosted Integration Runtime with SSIS package The Execute method must succeed, and indicate the result using an \"out\" parameter.\

Wojciech Bukowski 1

I have SSIS Package that pulls data from On-premise data Source and push data to Azure Blob.
SSIS Package has been deployed to Azure SQL DB (SSISDB) and ADF Pipeline is created with this package.

On ADF Pipeline level I select Azure-SSIS IR (Self Hosted Integration Runtime that is using Virtual Machine inside Corporate Network)
Both: On Premise Data Source & Blob Destination has "ConnectByProxy" set to TRUE

Package Run Successfully on Visual Studio Debug

When I run (Debug) from ADF Pipeline:

Package Pulls data successfully from On Premise Source
Package push data successfully to Blob
Steps 1 and 2 works super fast (10 sec)
Now package hangs for around 10-11 minutes and returns error

Data Flow Task:Error: The Execute method on the task returned error code 0x80131505 (Timeout when reading from staging). The Execute method must succeed, and indicate the result using an \"out\" parameter.\r\n\n4/19/2021 11:11:19 AM +00:00 : Data Flow Task:Error: The Execute method on the task returned error code 0x80131505 (Timeout when reading from staging). The Execute method must succeed, and indicate the result using an \"out\" parameter.\r\n\n",

Last log entry from SH IR is:

LOAD Table to BLOB:Information: Cleanup phase is beginning.,,,OnInformation,LOAD Table to BLOB,{ID},SSIS.Pipeline,\Package\LOAD Table to BLOB,{ID}\LOAD LOAD Table to BLOB,9404,,,1074016265

I have also created another SSIS package that copy data inside of Machine that is used as Self-Hosted IR.
File is copied but package fails with same error.

Any suggestion how to fix / debug it further ?

MadhaviB 76 Reputation points

2021-04-20T21:41:26.883+00:00

We encountered similar issue earlier. Please set CommandTimeout to 0 for your Data flow source and destination. This should resolve the timeout issue.
Monalv-MSFT 5,896 Reputation points

2021-04-21T09:27:58.92+00:00

Hi @Wojciech Bukowski ,

Please check if you set the ssis package correctly in the ADF Pipeline.

With Azure-SSIS IR, you can easily run the SSIS packages that are deployed into the SSIS catalog database, hosted in an Azure SQL Database server or an Azure SQL Database Managed Instance using the Project deployment model, or run the packages that are deployed into the file system, Azure Files, or SQL Server MSDB database that is hosted in an Azure SQL Database Managed Instance using the Package Deployment model.

Please refer to Run SSIS packages in Azure Data Factory.

Best regards,
Mona

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Wojciech Bukowski 1 Reputation point

2021-04-21T10:27:17.553+00:00

Tried:
-SSISDB on Azure SQL Database using Project deployment model
-run the packages that are deployed into the file system (hosted on Storage Account) - both Package and Project
-Embedded Package (inside of ADF)

Always same error and result.
Today I tried Execute package in Azure from Visual Studio.
Same result.
What is interesting, in VS data is being copied to Blob before Exulting phase begins (At Least graphically) and package fails again after ~10 minutes
Wojciech Bukowski 1 Reputation point

2021-04-21T10:28:28.053+00:00

Dont have those options in my Source and Destination. I am also not getting timeous from my Source and Destination as data is successfully loaded
Monalv-MSFT 5,896 Reputation points

2021-04-26T02:51:55.55+00:00

Hi @Wojciech Bukowski ,

May I know if you set any parameter in your ssis package?

Please check if you set the ssis package correctly in Azure Data Factory pipeline.

We can refer to Run an SSIS package with the Execute SSIS Package activity in Azure Data Factory.

Best regards,
Mona
KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2021-04-27T17:51:21.767+00:00

Hi @Wojciech Bukowski ,

To better assist on this issue, could you please confirm the details requested by @Monalv-MSFT ? Thanks
KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2021-04-28T17:05:57.363+00:00

Hi @Wojciech Bukowski ,

We still have not heard back from you. Just wanted to check if you are still facing the issue or need assistance on this? In case If you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.
Wojciech Bukowski 1 Reputation point

2021-05-04T08:13:39.313+00:00

Hi,
this is not parameter fault as I do not have parameters in my package.
I made this package as simple as possible to minimize possibilities of failure.

Wojciech
Jayasree Ramu 1 Reputation point

2021-06-15T12:41:18.2+00:00

Hi, I am also facing the same issue.. Did you got it resolved.. If yes, kindly share the solution
Wojciech Bukowski 116 Reputation points

2021-06-15T14:41:17.623+00:00

I think this is related to some kind of Bug.

MS Pointed to following error in log files:

Load Selfhosted IR web proxy setting failed. Error in line 1 position 163. Expecting element 'ProxySettings' from namespace 'http://schemas.datacontract.org/2004/07/Microsoft.DataTransfer.Common.Http'.. Encountered 'Element' with name 'ProxySettings', namespace 'http://schemas.datacontract.org/2004/07/Microsoft.DataTransfer.DIAgentCommon.Contracts'. . Ignore web proxy setting.

Unfortunately this is not yet resolved by MS :(
Jayasree Ramu 1 Reputation point

2021-06-15T14:55:54.467+00:00

:( can u share the location of this log?
Wojciech Bukowski 116 Reputation points

2021-06-15T15:06:35.96+00:00

You can find this error on EVENT VIEWER on Machine / Virtual Machine that is used as Self-Hosted IR Proxy
Either it was on Connectors - Integration Runtime
or
Integration Runtime

under Applications and Services Logs on Event Viewer

You can Filter Logs for timestamp between Start and End (failed time) of your ADF Pipeline
Jayasree Ramu 1 Reputation point

2021-07-02T12:16:52.017+00:00

Hi @Wojciech Bukowski ,

For me problem was solved by following the below document and also by overriding the proxy properties while execution.

https://learn.microsoft.com/en-us/azure/data-factory/self-hosted-integration-runtime-proxy-ssis

Try this.

Regards,
Jayasree

1 answer

Kasa Vinod 6 Reputation points

2021-12-16T19:37:26.7+00:00

Not sure if this is safe option but after setting TSL to 1.0 from 1.2 the issue got resolved!
Please sign in to rate this answer.

1 person found this answer helpful.
Ayoub KETATA 0 Reputation points

2023-02-26T12:52:10.7266667+00:00

Great, that resolved the issue !
Sign in to comment