Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
| Error: PipelineException: Container exited unexpectedly with code 0x0000DEAD. PID: 9640. .. RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24.Param1 = PipelineException: Container exited unexpectedly with code 0x0000DEAD. PID: 9640. Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
| Error: The current operation was canceled because one or more operations failed... RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24 Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
| Error: One or more upstream operations failed... RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24 Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
| Error: One or more upstream operations failed... RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24 Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
| Error: One or more upstream operations failed... RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24 Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
| Error: One or more upstream operations failed... RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24 Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
| Error: One or more upstream operations failed... RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24 Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
| Error: One or more upstream operations failed... RootActivityId = fa36fb16-7bff-4577-913e-06b7b1ef7d24 Request ID: 0e2e0b45-650e-4bcf-878e-ad9f94523b3e. |
Thanks for the answer @v-xulin-mstf
a doubt, if i use a ppu license, would this problem stop occurring? Our environment is shared and it is difficult to make this change in atual scenario.
@Anonymous Hey Try this.
Found something similer on this group.
I went to the local cache for Power Bi (something along the lines of C:\Users\username\AppData\Local\Microsoft\Power BI Desktop\Cache) and deleted all files found there. Once I did that I went back into my existing data model and everything is working again.
Hi @Anonymous
Please try below suggestions:
There is a semantic difference when the entities are referenced from DF in same workspace vs DF is a different workspace with respect to the compute engine. In the same workspace case, the dataflows have a strong reference to each other and are updated in the same transaction. Hence we do not need to cache data and can refer to the data from the upstream entity. However, when they come from different workspace, the references are weak references and in order to be self-contained within a workspace we do need to re-cache the data. The re-caching step is what adds the additional time in processing.
To mitigate this we suggest
Best Regards,
Link
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 68 | |
| 68 | |
| 33 | |
| 31 | |
| 31 |