Direct query visuals showing - an exception occurred due to an on premise service issue in PBI Servi

[RudraReddy]

Hi

I have a dataset with multiple Database connections (Oracle DB & Microsoft DB) and having queries with Import and Direct connectivity.The overall report is working good and refreshing also completed properly in desktop but I am facing some errors especially the visuals using fields from the direct query connection.

Error :

1.An exception occurred due to an on premise service issue.

2.Visual has exceeded the available resources.

Please help which is actually causing this issue.

[v-tianyich-msft · Accepted solution]

Hi @RudraReddy ,

According to the survey, it's the concurrency limit that's the problem.

There are multiple ways to workaround the throttling/timeouts caused by max concurrent DQ connections limit:

1. Move to larger SKU which has higher limits on Max concurrent DirectQuery connections (per semantic model) as per https://learn.microsoft.com/en-us/power-bi/enterprise/service-premium-what-is#semantic-model-sku-lim.... 

2. Use DirectLake mode instead of DirectQuery to SQL endpoint. Learn about Direct Lake in Power BI and Microsoft Fabric - Power BI | Microsoft Learn Keep in mind the limitations of using DirectLake mode if you are using T-SQL views.

Hope it helps!

Best regards,
Community Support Team_ Scott Chang

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[v-tianyich-msft]

Hi @RudraReddy ，

Hi all,

We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

Best regards.
Community Support Team_Scott Chang

[v-tianyich-msft]

Hi @RudraReddy ,

It looks like you're using mixed connection mode, I think the main reason is that you're not creating full connections for them, make sure the gateway is working properly. Also the single visual exceeds the line limit.

Hope it helps!

Best regards,
Community Support Team_ Scott Chang

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

Grab the queries for these visuals with Performance Analyzer and then study them with DAX Studio.  Usually the issue is that a join columns has a high cardinality over 50k.