We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hi,
I am facing an issue enabling incremental refresh on a table inside a data flow. The same table loads without any problem when the Incremental Refresh settings are disabled. Issue details available in Refresh logs are given below:
Error: PipelineException: Container exited unexpectedly with code 0x0000DEAD. PID: 38640. . RootActivityId = c2e5436f-174c-46ef-ba64-e3ead2e12888.Param1 = PipelineException: Container exited unexpectedly with code 0x0000DEAD. PID: 38640. Request ID: 09060eae-74aa-0932-2d6d-f5852ff41bd8.
Here are a few things I have already done to overcome this problem:
This dataflow is in a workspace with premium capacity.
Hi,
I'm facing exactly the same situation, except my dataflow doesn't have anyincremental refresh.
Microsoft support told me it was a memory issue and ask me to upscale to a P2 capacity license (I had a P1).
The issue remains and the dataflows stops refreshing (after the same time as on P1) with error 0x0000DEAD.
I suspect Microsoft has set new limits on the capacities (e.g. max number of tables per dataflow, etc.).
What a waste of time and money...
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.