An exception occurred due to an on premise service issue- Report not able to connect to data source

[Anonymous]

Hello,

I have a report that uses a Databricks connection on a data gateway. I'm getting the above error regarding an on premise service issue which is causing my report visuals to break. I've confirmed my gateway is online and my credentials with my Databricks connection are correct. Other reports with the same connection work fine, it's just with this one dataset and report that I'm receiving these issues.

Any help would be appreciated.

[v-veshwara-msft]

Hi @Anonymous ,

We’re following up once more regarding your query. If it has been resolved, please mark the helpful reply as the Accepted Solution to assist others facing similar challenges.

If you still need assistance, please let us know.
Thank you.

[v-veshwara-msft]

Hi @Anonymous ,

Following up to see if your query has been resolved. If any of the responses helped, please consider marking the relevant reply as the 'Accepted Solution' to assist others with similar questions.

If you're still facing issues, feel free to reach out.

Thank you.

[v-veshwara-msft]

Hi @Anonymous ,

Just checking in to see if you query is resolved and if any responses were helpful. If so, kindly consider marking the helpful reply as 'Accepted Solution' to help others with similar queries. 

Otherwise, feel free to reach out for further assistance.

Thank you

[v-veshwara-msft · Accepted solution]

Hi @Anonymous ,

Thank you for posting in Microsoft Fabric Community and sharing the details.

Since your gateway is online and other reports using the same Databricks connection are working correctly, the issue may be specific to the dataset or report configuration. Please try the following steps to isolate and resolve the issue:

1. Go to Semantic Model settings and confirm:

   1. The correct gateway connection is selected

   2. The data source credentials are valid

2. Go to the data source credentials of the semantic model in the service and re-authenticate by refreshing all credentials, even if they appear valid.

3. Temporarily switch to a different gateway, save, and then switch back to the correct one. This can help re-establish the binding.

4. Open the affected report in Power BI Desktop and check Transform Data > Data Source Settings. Ensure that the cluster URL, catalog, and authentication settings exactly match those used in the working reports.

5. Ensure that your on-premises data gateway is updated to the latest version. Outdated gateway versions can sometimes cause unexpected connectivity issues.

Similar issues : An exception occurred due to an on premise service... - Microsoft Fabric Community

powerbi an exception occurred due to an on premise... - Microsoft Fabric Community

Hope these help to resolve your issue. Please reach out for further assistance.
If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.

Thank you.

[GilbertQ]

Hi @Anonymous 

Could you please confirm that this has the exact same data source structure as it has with your other files? Sometimes there is something that is slightly different, which is causing the issue. So if you can please compare to make sure they match 100%.

[Anonymous]

Hi @GI ,

The data set that is being used within the table is different than the other reports that work. If the issue is with my data set, how do I identify what is causing the error. I have tried to limit the number of rows, removed fields that potentially caused errors, and removed visualizations that could have been an issue. Tried approaching the issue from different angles, but still unable to isolate the problem and resolve it.