Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowGet inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.
Error: PipelineException: Container unexpectedly exited. Exit code: 0xC000012D. PID: 13808 . RootActivityId = 2ee6326f-bc03-43f6-8a7f-8ff0378a819a.Param1 = PipelineException: Container unexpectedly exited. Exit code: 0xC000012D. PID: 13808 Request ID: a84f3d36-83d5-a7f2-1bb0-8d1c631a81df.
Getting above error message on scheduled refreshes starting at 08:02:00 am Central. Happening on multiple dataflows. Trying to refresh manually produces same error. Refreshing another dataflows that was scheduled earlier this morning gives the same error. I was able to go into each dataflow and all entitities and see that data is coming through the data gateway. Each dataflow contains entities with sources from either sharepoint or on prem fileshares or both.
Looks like this same issue happened recently: https://community.powerbi.com/t5/Service/Dataflow-PipelineException-Container-unexpectedly-exited/m-...
Troubleshooting steps attempted:
- Take over dataflow from other user.
- Enter dataflow and reauthenticate all entities.
- Manually refresh from workspace
- Enter dataflow, save and close, validate queries.
- Tried copying dataflow via export and inserting into the same workspace. Open dataflow, use different on-prem connector.
New items found since original post:
- 8:34 am: Does not impact all dataflows. One dataflow using a on-prem data gateaway that connects only to Oracle DB is able to refresh successfully.
- 8:52 am: Inexplicably some other dataflows in other workspace are working just fine that utilize the same fileshares and sharepoint connectors over gateway. Continue to get errors in what appears to be only one workspace.
Solved! Go to Solution.
Well that was fun. Ended up going to Workspace Settings > Premium > License Mode (change from existing Premium Capacity to Pro then repeat and flip back to Premium Capacity, selected same capacity and apply)
This solved the issue immediatly.
Update - my dataflow is connected using a pipeline and it was giving the error only in the production workspace and was causing issues with some of my dates as I have my Dim Calendar connected to refresh once a day so the refresh that my other reports does every 15 does not ping my Databricks server all day and night.
Resolution - Attempted edit dataflow and refresh and thought it worked, attempted push from Test workspace to override, etc.
Edited my credentials which is a Personal Access Token and then it worked even though there was no changes and my token exiration is not anywhere near. So touche' Power Bi the wonder of no real meaning behind errors... continues and the forum has to solve it all! #dobetter pretty please, we love you!
This solution worked for me too. Changing workspace licenses from Premium to Pro and back to Premium immediately resolved the problem.
Well that was fun. Ended up going to Workspace Settings > Premium > License Mode (change from existing Premium Capacity to Pro then repeat and flip back to Premium Capacity, selected same capacity and apply)
This solved the issue immediatly.
Thank you so much, Chat GPT couldnt even help but this solved our problem instantly!
Thank you for posting your solution of switching the workspace to Pro and then back to Premium. This just worked for me too, and also resolved another error code I was getting, which was:
PipelineException: Container exited unexpectedly with code 0x0000DEAD.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code FABINSIDER for a $400 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
64 | |
31 | |
28 | |
26 | |
26 |
User | Count |
---|---|
57 | |
50 | |
40 | |
15 | |
12 |