Salesforce V2 Link Service doens't work. error message: a task was canceled Source=mscorlib

ChoiLiamhehimhis-5365 25

I am migrating the ADF salesforce connector to the new V2 connector and now testing it.

When testing the connection for the link service, it is good.

However, it failed in the copy activity. with message:

Failure happened on 'Source' side. 'Type=System.Threading.Tasks.TaskCanceledException,Message=A task was canceled.,Source=mscorlib,'

Sometimes it works, and sometimes it fails.

I also enable the debug run in salesforce, it shows the query is with status 'completed'. But the SHIR doesn't receive any records from the source and the copy activity is failed.

Bhargava-MSFT 29,266 Reputation points Microsoft Employee

2024-05-16T16:45:34.02+00:00

Hello Choi, Liam (he/him/his),

Welcome to the Microsoft Q&A forum.

How much is your dataset size? if you are using a larger dataset, can you please try using a smaller dataset?

also, as this is a transient issue with ADF IR, could you please install SHIR and test the copy activity with SHIR and see the results?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
ChoiLiamhehimhis-5365 25 Reputation points

2024-05-16T19:02:25.5266667+00:00

From the success run, the data read is 306 MB and data written to ADLS gen 2 is 20.8MB.

I am already using the self-host IR for the copy activity.
ChoiLiamhehimhis-5365 25 Reputation points

2024-05-16T21:03:23.1266667+00:00

Hi @Bhargava-MSFT

Thanks for letting me know the workaround.

Actually, we plan to switch to the V2 connector because we saw the message in ADF saying the legacy connector will be deprecated. If there are bugs in the V2 connector, I think I will postpone the migration until the issue is resolved.

Do you have the schedule of when the legacy connector will be deprecated? And I have to report to my team for better planning on the migration.
Bhargava-MSFT 29,266 Reputation points Microsoft Employee

2024-05-16T22:15:18.8+00:00

ChoiLiamhehimhis-5365,

The notification has been sent out to all subscriptions who is using the Legacy connector.

The end of date for legacy connector is 11 Oct, 2024

I hope this answers your question.

If you don't have any further questions, please consider accepting the answer by hitting the Accept answer and up-vote as it helps the community look for answers to similar questions.
Lionel Dsouza 0 Reputation points

2024-05-23T10:24:31.64+00:00

Hi, I face similar issue : For example, with the Legacy connector for Accounthistory object it could retrieve all the rows : 1,224,726 rows but with the new Salesforce connector only retrieves 285,618 rows.
thara kollu 0 Reputation points

2024-05-28T19:30:28.1+00:00

We are facing similar issue, new Salesforce connector times out for 1million records. Is there any ETA for SalesforceV2 connector bug fixes?

1 answer

Bhargava-MSFT 29,266 Reputation points Microsoft Employee

2024-05-16T20:18:59.35+00:00

Hello Choi, Liam (he/him/his),

Thanks for the additonal details.

The new salesforce connector leverages bulk API for better user experience. But recently we did find there are some bugs when using SalesforceV2 connector comapring with legacy Salesforce connector.

Workarounds:
Please use Power Shell command to generate legacy Salesforce linked service and pipelines.

https://learn.microsoft.com/en-us/powershell/module/az.datafactory/new-azdatafactorylinkedservice?view=azps-11.6.0&viewFallbackFrom=azps-11.2.0

The salesforce related definiation can be found here. https://github.com/Azure/azure-rest-api-specs/blob/7e9e559d09a11686c132aaf4e1759b29f79517d7/specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/entityTypes/LinkedService.json#L2885C6-L2885C29

(or)

You can use UX feature flag '&feature.enableSalesforceV2=false' to temporarily switch back to legacy salesforce connector to unblock you here. In order to use the feature flag, just add above in data factory URL.

If the new created linked service is with type 'Salesforce' rather than 'SalesforceV2', then it works.

Please try this and let me know if you still having the issue.
Please sign in to rate this answer.
Lionel Dsouza 0 Reputation points

2024-05-23T10:15:48.61+00:00

Hi Bhargava,

I face the similar issue. If I use the legacy connector, it extracts 1,224,726 rows for accounthistory object but with the new connector it only extracts 285,618 rows.

Is this a known issue with the new Salesforce connector?

Bhargava-MSFT 29,266 Reputation points Microsoft Employee

2024-05-23T15:09:41.2133333+00:00

Hello Lionel Dsouza,

There are some known issues with Salesforce V2. You can follow the workaround mentioned in the answer.
Sign in to comment

Share via

Salesforce V2 Link Service doens't work. error message: a task was canceled Source=mscorlib

1 answer