Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Power BI connecting to NAV via Odata result in deadlock on SQL server and NAV service tier shutdown
math2841
Member Posts: 1
in SQL General
Dear Community,
I am experiencing issues when connecting to NAV via Odata feed in Power BI
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?
I am experiencing issues when connecting to NAV via Odata feed in Power BI
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?
0