Forum Discussion
Invoke Pipeline fails with Error code 2015: 'Value cannot be null. Parameter name: source '.
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
Ohhh wow AnitaCrook , seems like you having a big data process 👉 400 tables! 👏😎 I don't have a DB2 source to even try to reproduce your issue, I guess that won't be a surprise to you, I bet you're on a middele of a platform modernization to either move or make the data accessible to Fabric (clarify if neccesary for this case)... back to the case, I would be suspecious of the DB2 connector, of course, but this would not explain why using using the legacy invoke pipeline works! Both are calling the exact same Inner pipeline, that means, both are calling the exact same DB2 connectino and therefore, if one works and the other don't, this suggest that is not the DB2 per se, but perhaps the Invoke pipelie and it's interaction with the inner pipeline. So far, some test that I've done works just fine ... but in your case, this has to be reproduce with a DB2 connector to figure this one out ... I suggest you to at least try to identify if there any pattern on the error and open a case with MSFT.
Hope at least this brainstorming session helps in the resolution of the issue ... kudos if you find this useful. All the very best!
Hi AnitaCrook,
Thank you for reaching out to Microsoft Fabric Community.
Thank you svenchio for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi @AnitaCrook,
We wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi v-achippa ,
No solution yet, the only way we can invoke a pipeline which copies from DB2 as a source is to use the Legacy Invoke Pipeline.
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
