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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

0

Power BI Intermittently throws Container unexpectedly exited. Exit code: 0xC000012D.

Hi

Facing Issue while DataSet refresh intermittently. 

Failure details: "The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.

<ccon>We're sorry, an error occurred during evaluation.</ccon>;<ccon>Container unexpectedly exited. Exit code: 0xC000012D. PID: 9312 Container unexpectedly exited. Exit code: 0xC000012D. PID: 9312 Container unexpectedly exited. Exit code: 0xC000012D. PID: 9312</ccon>. The exception was raised by the IDbCommand interface. Table: AzDUtilization."

 

Activity Id:

7ca145e8-9ce1-48ac-8837-d80ec9f8a062

 

Request Id:

6fc26aa4-82a9-4c3e-ac85-7f8832469705

 

Cluster Name:

DF-MSIT-SCUS-redirect.analysis.windows.net

 

Refresh Start Time:

July 26, 2022 19:02 UTC

 

Refresh End Time:

July 26, 2022 19:19 UTC

 

The Dataset refresh error is occuring intermittently. 

The above Error was observed on May 11, July 12, July 14, July 26 2022.

 

We are connecting to Kusto Datasource for Power Query to refresh using import query.

When trying in Power BI Desktop during same timeperiod it refreshes fine and also in Diagnostics tool do not see any issue.

 

Need help in finding root cause of the issue. Checked online but could not find any help.

 

Similar Issue :

Container exited unexpectedly power BI service ref... - Microsoft Power BI Community

 

 

 

 

Status: Delivered

Same issue has been submited internal(ICM: 326491560), the potential reason that cause this issue may be ExecuteSql retries many times, perhaps you should investigate why the command failed on the data source side.

 

Best Regards,
Community Support Team _ Yingjie Li

Comments
v-yingjl
Community Support
Status changed to: Delivered

Same issue has been submited internal(ICM: 326491560), the potential reason that cause this issue may be ExecuteSql retries many times, perhaps you should investigate why the command failed on the data source side.

 

Best Regards,
Community Support Team _ Yingjie Li

ykotamraju
Microsoft Employee

I have checked from data source and observed no issue with queries in kusto.

How to trace out more logs / metrics from Power BI side to get more insights on these intermittent failures ?

As mentioned I already tried refreshing queries on Power BI Desktop with Diagnostics and found no issues there.

ykotamraju
Microsoft Employee

Observed Issue again on 18th Aug 2022 9PM IST.

 

An error occurred while processing the data in the dataset.

Refresh failed:

AzD has failed to refresh.
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.

<ccon>We're sorry, an error occurred during evaluation.</ccon>;<ccon>Container unexpectedly exited. Exit code: 0xC000012D. PID: 5976 Container unexpectedly exited. Exit code: 0xC000012D. PID: 5976 Container unexpectedly exited. Exit code: 0xC000012D. PID: 5976</ccon>. The exception was raised by the IDbCommand interface. Table: AzDDteDtr.

Next refresh for AzD is scheduled for August 18, 2022 18:00 UTC.

 

 

Learn more >

 

 

Technical Information

 

 

Activity Id:

a05710ec-0c98-4b50-a70d-cc0d8980bde9

 

Request Id:

a00ac751-636a-43c1-ab97-bacb046b6348

 

Cluster Name:

DF-MSIT-SCUS-redirect.analysis.windows.net

 

Refresh Start Time:

August 18, 2022 15:02 UTC

 

Refresh End Time:

August 18, 2022 15:30 UTC

 

The Datasource we are using is Kusto.

We checked that there are no failed Queries on Kusto side during this Failure.

The ICM -326491560 Created seems specific to other use case connecting to SQL and its already resolved.

 

ykotamraju
Microsoft Employee

Hi

Any update on this ?

Can the Support team see internal Power BI debug logs and see why thsi Error is happening