Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

DamoUK

Refresh failures to Databricks from the PBI Service

Submitted by on ‎03-19-2025 06:50 AM

I have a long-standing connection to databricks, using a cloud connection in the online service, connecting to a Unity-catalog. All refreshes failed today with the error:

Expression.Error: The provided options are not valid.. {"DefaultTypeParameters"}. . The exception was raised by the IDbCommand interface.

My data engineers and I have been going round in circles on this for the last 6 hours. Nothing has been changed, and every single report is failing if it connects to Databricks. All other repots are fine. This randomly started failing at around 7am UK time today.

Any ideas or has anything been changed in the PBI Service that might cause this?

Status: Investigating
See more ideas labeled with:
5 Comments (5 New)
Comments
Anonymous
Not applicable
‎03-19-2025 10:49 PM

Hi  @DamoUK ,

 

it seems that the issue might be related to network configurations, authentication errors, or recent changes in the Power BI Service. Here are a few steps you can try:

  1. Check Network Configurations: Ensure that there are no network misconfigurations or firewall restrictions that might be causing the issue.
  2. Verify Authentication: Double-check the authentication settings and ensure that the correct credentials are being used.
  3. Review Recent Changes: Look into any recent changes in the Power BI Service or Databricks configurations that might have triggered the issue.

 

Best Regards,
Community Support Team _ Caitlyn

DamoUK
Frequent Visitor
‎03-20-2025 01:32 AM
The issue is resolved. It was a change put in by Microsoft which has been backed out. The NHS (National Health Service) had the same issue and their update says that it was a change that had to be backed out.
Jackie0607
Regular Visitor
‎03-20-2025 07:14 PM
We encountered the same issue too. Thank you for raising this vote in the community. Otherwise, we might have spent a long time troubleshooting issues. But we are still facing this error. Is it possible to roll it back?
Jackie0607
Regular Visitor
‎03-21-2025 01:38 AM
Hi @DamoUK, Here is a solution that was shared: https://community.fabric.microsoft.com/t5/Service/Databricks-VNet-DM-GWPipeline-Gateway-MashupDataAc... The issue only occurs when using Databricks.Query() in custom queries. If the data is selected directly through the UI, it works without any problems. You might want to try using Value.NativeQuery() instead. It was also mentioned that this issue is expected to be resolved around April.
DamoUK
Frequent Visitor
‎03-21-2025 08:32 AM
Hi @Jackie0607 thanks for the info. Our problem was resolved the following day and from a notification today from Microsoft, this is now resolved in all areas and has been closed. 4 people in my team spent 7 hours each investigating this as it coincided with an upgrade to Unity Catalog in Databricks so we thought it was self-inflicted. I'm glad my issue saved you going through the same pain as us.
Idea Statuses