Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Anonymous
Not applicable

Dataflow Refresh Failure: Container unexpectedly exited.

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.

 

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

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.

View solution in original post

1 REPLY 1
Anonymous
Not applicable

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.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors