Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Dear Community,
I am experiencing issues when connecting to NAV via Odata feed.
With no specific pattern, the SQL database log the following error and afterwards all the NAV services lose connection to the SQL database.
"All schedulers on Node 0 appear deadlocked due to a large number of worker theads waiting on ASYNC_NETWORK_IO"
The issue is observed when updating from Power BI desktop and when using scheduled update via the datagateway on Power BI Service and on two different environments.
Have anyone experienced the same issues and did you find a solution?
@Anonymous,
Please kill the process which is consuming the majority of Worker Threads in SQL Server using the dedicated administrator connection (DAC), then increase the “Max Worker Threads” configuration option following the instructions in this blog: https://blogs.msdn.microsoft.com/nav/2015/06/03/sql-server-worker-threads-and-microsoft-dynamics-nav/.
Regards,
Lydia
@v-yuezhe-msft,
Thank you for your input.
We already tried increasing the "Max Worker Threads" without resolving the issue.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
8 | |
6 | |
6 | |
6 | |
5 |
User | Count |
---|---|
9 | |
9 | |
8 | |
6 | |
6 |