Forum Discussion
Databricks VNet DM_GWPipeline_Gateway_MashupDataAccessError
We are getting the following error when trying to refresh data from databricks via a VNet gateway. We have checked everything we can think of in terms of what might be causing the error though so far have had no joy.
| {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The provided options are not valid."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":null}},{"code":"Microsoft.Data.Mashup.ValueError.Detail","detail":{"type":1,"value":"{\"DefaultTypeParameters\"}"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}} |
Walkaround is possible by native queries
Value.NativeQuery(Databricks.Catalogs(
"adb-xxxxxxxxx.azuredatabricks.net",
"/sql/xx/xx/xx",
[Catalog = "xxx", Database = null, EnableAutomaticProxyDiscovery = null]
){[Name = "xxx", Kind = "Database"]}[Data],
"select * from Sample",
null,
[EnableFolding = true])
11 Replies
- DekuSuper User
I had the same/similar issue and brought up with Microsoft support. The issue is the driver on VNET gateway needs a fix, and Microsoft is waiting on databricks for the updated driver. No timeline available
- DekuSuper User
You can also turn off cloud fetch but that makes refreshes much slower
- bergmaalFrequent Visitor
MS Support says that Databricks has planned to fix this issue "around April", and they suggest disabling cloud fetch as a temporary workaround (as mentioned by Deku).
However, I tested with the workaround proposed by Ni_BI_Żak, using Value.NativeQuery(Databricks.Catalogs()) as a replacement for Databricks.Query(), and that resolved the issue for me. So the culprit seems to be Databricks.Query().
This doesn't work:
let Source = Databricks.Query( "adb-xxxxxxxxxx.x.azuredatabricks.net", "/sql/1.0/warehouses/xxxxxxxxx" ), Query = Source("SELECT * FROM my_catalog.my_database.my_table") in QueryUse this instead:
let Source = Databricks.Catalogs( "adb-xxxxxxxxxx.x.azuredatabricks.net", "/sql/1.0/warehouses/xxxxxxxxx" ){[Name="my_catalog", Kind="Database"]}[Data], Query = Value.NativeQuery(Source, "SELECT * FROM my_database.my_table") in Query - AlasdairLNew Member
Feels like i'm having similar issues with a paginated report that is trying to load data from databricks within powerquery. No gateway involved in this setup but it's the same error message.
Expression.Error: The provided options are not valid.DetailsReason = Expression.ErrorDetail = {"DefaultTypeParameters"}Same query runs fine within PowerBi desktop.
Keeping an eye on this to see if you get a solution.- Ni_BI_ŻakFrequent Visitor
Walkaround is possible by native queries
Value.NativeQuery(Databricks.Catalogs(
"adb-xxxxxxxxx.azuredatabricks.net",
"/sql/xx/xx/xx",
[Catalog = "xxx", Database = null, EnableAutomaticProxyDiscovery = null]
){[Name = "xxx", Kind = "Database"]}[Data],
"select * from Sample",
null,
[EnableFolding = true])
- AnonymousNot applicable
Hi rhartop
Thank you for reaching out microsoft fabric community forum.
Ensure that your VNet Gateway is properly configured in Databricks and is accessible by Power BI. Ensure the on-premises data gateway is running the latest version.
Double-check the data source settings in Power BI, especially if you're using custom queries or transformations in the mashup.
If the issue still persists, please consider raising a support ticket. You can create a Microsoft support ticket using the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketIf this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community.
Thank you.
- AnonymousNot applicable
Hi bergmaal
That's great to hear that you found a workaround 😊. - AnonymousNot applicable
Hi rhartop
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.