AlexFillingham-6577 avatar image
0 Votes"
AlexFillingham-6577 asked KranthiPakala-MSFT commented

ADF - Index out of range


we're getting the following error in ADF when pulling data from the source side.

"An error happened while reading data from the provider: 'Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index"

we're essentially running a "select * from (table)".

Can anyone shed a light on why this may now be happening? The loads have been working fine previously and now seems to be cropping up more and more on this source / linked service (sybase).


· 10
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @AlexFillingham-6577,

Thanks for reaching out. My understanding is that that pipeline which used to work has suddenly started throwing the above mentioned error. Please correct if I misunderstood your query.
Also please do confirm if you have made any changes recently to the pipeline (which was working fine previously) or the linked service connection to Sybase? Or is this a new pipeline that you are developing? Also please do check if this is happening while querying on a specific table or consistent with all other tables? If it is consistent with all other tables then it could be an issue related to connector.

Please share the failed pipeline runID and activity runID so that we can check with internal team.

We look forward to your response.

Thank you.

0 Votes 0 ·

hello @KranthiPakala-MSFT thanks for reaching out.

This is a pipeline that has been in production for a good while now and we haven't had to amend it.

The error has been happening on a couple of specific tables (a few months ago) and has now gone to other tables but not all in the extract are affected (bizarrely).

Pipeline Run ID - 7752dfa9-8328-47b5-a0a8-3c0ee995ba76
Activity Run ID - 84b38673-07af-4c4e-8e1c-e1fe4f00a14a

These are from the load last night.

Please let me know if you need anything else from me.


0 Votes 0 ·

Hi @AlexFillingham-6577,

Thanks for the response and details. We will look into the runID's and will get back to you soon.

Thank you for your patience

0 Votes 0 ·

Hi @AlexFillingham-6577,

Just wanted to let you know that, I have escalated this issue to internal team and awaiting response. Will keep you posted as soon as I hear back from the team.

Sorry for the delay and we appreciate your patience.

Thank you

0 Votes 0 ·

Hi @AlexFillingham-6577,

Sorry for the delay in response. Could you please confirm whether the table queried is being frequently updated by other application as well, during the pipeline running phase? From the backend log, the issue only happened against the table with the prefix AutoMatchPerson. If yes, could you please stop other applications and see whether this issue is gone? Further if the issue persists, to quickly mitigate, product team has recommended to use ODBC connector to see whether there is similar issue with that connector too.

And if you notice the same issue, please let us know.

We look forward to your confirmation.


0 Votes 0 ·
Show more comments

0 Answers