Azure Synapse: Failure happened on 'Sink' side, when copying data from ADLS2 to Cosmos database

Question

Azure Synapse: Failure happened on 'Sink' side, when copying data from ADLS2 to Cosmos database

Rosi Reddy 21 Microsoft Employee

Only for one specific dataset, copying data from ADLS2 to Cosmos database is failing. This is a consistent repro. But error details not providing any information on the reason for this issue.
I see input data is working as expected.

Error:
{
"errorCode": "2200",
"message": "Failure happened on 'Sink' side. 'Type=System.NullReferenceException,Message=Object reference not set to an instance of an object.,Source=Microsoft.DataTransfer.ClientLibrary.CosmosDbSqlApiV3,'",
"failureType": "UserError",
"target": "act-push-egress-to-cosmosDB",
"details": []
}

RunIds:
146460b3-0766-40c0-b3c9-1a1a068c0fec
77c95066-d8f5-4c9b-b526-5a89a5237b12
9904dc89-fd43-49a6-bfda-607bd6150661

Accepted answer

0 additional answers

Your answer

Answer 1

ShaikMaheer-MSFT 38,546 Microsoft Employee Moderator

Hi @Rosi Reddy ,

Thank you for posting query in Microsoft Q&A Platform.

Usually Object reference not set to an instance of object error will come when we are trying to refer some null.

Could you please recheck and confirm is everything good with your Sink dataset? The account or db or table to which its pointing actually exists?

Rosi Reddy 21 Reputation points Microsoft Employee

2022-11-28T18:46:00.847+00:00

Yes, I already fixed this issue. As you said, this issue was related to null and invalid characters for the id column. Once I removed these rows, then everything worked fine.
It should be good to see a valid error message instead of an object reference exception.
ShaikMaheer-MSFT 38,546 Reputation points Microsoft Employee Moderator

2022-11-29T04:39:46.613+00:00

Hi @Rosi Reddy - Glad to know your issue resolved and sharing exact root cause in your case. This helps community as well. Kindly consider marking it as Accepted Answer. Accepted answers help community as well.
Gorie, Maria 0 Reputation points

2025-05-27T12:50:14.95+00:00

I am having the same issue the target very much exists. Not only that, the pipeline started failing at some point after running with success numerous times. So no, it is not the lack of the target object, it is an ADF/Synapse error that Microsoft should fix (or provide explicit error message)

Share via

Azure Synapse: Failure happened on 'Sink' side, when copying data from ADLS2 to Cosmos database

0 additional answers

Your answer