Forum Discussion

AnitaCrook's avatar
AnitaCrook
Frequent Visitor
9 months ago
Solved

Invoke Pipeline fails with Error code 2015: 'Value cannot be null. Parameter name: source '.

We have a parent pipeline with a Lookup and a ForEach loop.  The Lookup reads a list of tables from an ETL Control table in a Fabric SqlDb database, then inside the ForEach loop, calls a child pipeli...
admin
  • v-achippa's avatar
    v-achippa
    9 months ago

    Hi AnitaCrook,

     

    Currently there is no additional setting in the new Invoke Pipeline activity that can be changed to resolve this. The behaviour you are seeing looks like a service side issue that affects DB2 sources when invoked through the new activity.

    For now, please continue using the Legacy Invoke Pipeline, as it works for your DB2 copy scenario.

     

    We recommend opening a Microsoft Fabric support ticket with the failed run id's and pipeline details so the product team can investigate and address this issue.

    To raise a support ticke, kindly follow the steps outlined in the following guide:

    Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

     

    Thanks and regards,

    Anjan Kumar Chippa

svenchio's avatar
svenchio
Super User
9 months ago

Hi AnitaCrook  this case seems very interesting, I don't have an answer for you because I don't think I have ever seen this behavior but I can certanly try to replicate it on my environment and see what I can find! 

 

 

How many tables are you processing during the loop (e.g. dozens, hundreds, ?), have you observed any pattern in the error? I guess the copy activity varies in time, for instance, some copy activities take seconds, some of them minutes?  I'll try to do some codign meanwhile and share my observations, all the best and good luck.