Forum Discussion
Helper IISession diagnostics error
Hi
Since the June 2026 version of power BI, if I enable 'Start Diagnostics' in the Tools menu of Power Query (for Query Editor only), I get an error when I refresh the data preview:
Container exited unexpectedly with code 0x80131623. PID: 5844.
This didn't happen on older versions, but I get the error in June and July 2026 versions. I haven't tried August - we haven't installed it on our tenant yet.
Has anybody come across this error before? It is a known bug that is fixed in later versions? Thanks
Hi Matthew_Martell,
Thanks for confirming that the issue also occurs in the August 2026 release.Microsoft’s documentation explains that Start Diagnostics records evaluations triggered during actions such as Refresh Preview, while Diagnose Step performs a separate evaluation for the selected step.
Since the "0x80131623" error persists when using Start Diagnostics -> Refresh Preview, I recommend reaching out to Microsoft Support for further investigation. You can provide them with the affected Power BI Desktop versions, the error code, and the observations already confirmed in this thread.
You can submit a support request from Power BI Desktop -> Help -> Support -> Submit a ticket, or use the Microsoft Learn link below:
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft LearnFor more details, please refer to the below Official Microsoft Documentation:
Query diagnostics - Power Query | Microsoft Learn
Record Query Diagnostics in Power BI - Power Query | Microsoft LearnI hope this helps. Please feel free to reach out if you have any further questions.
Thank you.
10 Replies
ronrsnfldSuper User
Yes, I have had the same problem for some time now when starting diagnostics and selecting "Refresh Preview". Also in the August edition. I do not get an error if I "diagnose" a single step (right click dropdown from any step). And the complexity of the query makes no difference. Very simple queries also return that error.
I have reported it using the tool within Power BI desktop, but yours is the first I've seen of someone else experiencing this issue.been affected all year with this. regardless of the query complexity it will error on start diagnostics. Diagnose step works.
v-abhinavmuCommunity Support
Hi Matthew_Martell,
Thanks for confirming that the issue also occurs in the August 2026 release.Microsoft’s documentation explains that Start Diagnostics records evaluations triggered during actions such as Refresh Preview, while Diagnose Step performs a separate evaluation for the selected step.
Since the "0x80131623" error persists when using Start Diagnostics -> Refresh Preview, I recommend reaching out to Microsoft Support for further investigation. You can provide them with the affected Power BI Desktop versions, the error code, and the observations already confirmed in this thread.
You can submit a support request from Power BI Desktop -> Help -> Support -> Submit a ticket, or use the Microsoft Learn link below:
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft LearnFor more details, please refer to the below Official Microsoft Documentation:
Query diagnostics - Power Query | Microsoft Learn
Record Query Diagnostics in Power BI - Power Query | Microsoft LearnI hope this helps. Please feel free to reach out if you have any further questions.
Thank you.- Matthew_Martell
Unfortunately I cannot submit support requests.
If I go to https://support.fabric.microsoft.com/ and click on 'Submit a ticket' it opens a link to https://go.microsoft.com/fwlink/?linkid=2230733 which simply takes me to the standard https://app.powerbi.com/home page. If I click on Support Centre from the help pane, it opens link https://aka.ms/contact-support which takes me to a page about government clouds: Sovereign Clouds | Microsoft Power BIBasically, I just go round in circles.
- v-abhinavmu
Hi Matthew_Martell,
This is the documented process for creating a Fabric and Power BI support ticket. Please follow the step-by-step instructions provided in the Microsoft Learn article below:
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
I hope this helps you submit your support request.
- v-abhinavmu
Hi Matthew_Martell,
Thanks for reaching out to the Microsoft Fabric Community forum.Query Diagnostics is designed to help understand what Power Query is doing during authoring and refresh time. When you start diagnostics, Power Query traces evaluations caused by actions such as refreshing the data preview.
For Query Editor scenarios, you can use Enable in Query Editor under the Diagnostics settings in Power BI Desktop. This allows Query Diagnostics to be used when previewing and authoring without requiring Power BI Desktop to run as administrator.
If you use Start Diagnostics, make sure to select Stop Diagnostics after reproducing the behavior. This allows Power Query to collect and parse the recorded traces.
For more details, please refer to the below Official Microsoft Documentation:
Query diagnostics - Power Query | Microsoft LearnI hope this helps. Please feel free to reach out if you have any further questions.
Thank you. - Matthew_Martell
I received a reply from Microsoft support after raising a ticket:
"This is a known behaviour that our Product Group has already identified and is actively working on. The behavior is caused by a regression related to diagnostics tracing in the Power Query engine in recent Power BI Desktop builds. Based on the information currently available, the issue is not caused by your report, your data source, or your environment.
I realize that knowing this is a product issue does not remove the inconvenience it is causing you, but I hope it at least provides some reassurance that you do not need to spend additional time troubleshooting your report or environment for the underlying cause.
Unfortunately, we cannot provide an ETA for the permanent fix because the work is still in progress."- v-abhinavmu
Hi Matthew_Martell,
Thank you for the update and for sharing the information provided by Microsoft Support.
It is helpful to know that the behavior has been identified as a regression related to diagnostics tracing in the Power Query engine and that the Product Group is actively working on it.
Thanks again for sharing the Support findings and the additional details. This information should be helpful to others experiencing the same behavior.
Best regards,
Abhinav
- Matthew_Martell
Thanks ronrsnfld for confirming that.
- Matthew_Martell
Thanks, v-abhinavmu. I'm aware of how to raise a support ticket. 🙂
The issue is that when following that process I did not get a 'Contact Support' option at the bottom. Instead I saw a 'Helpdesk' button which just took me to my own internal community forum.
I have now resolved the issue with raising a ticket by changing the tenant settings so that it no longer points at our internal help resources.
