Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Solved! Go to Solution.
Hi @Anonymous ,
Do you have the cloud and on-premise data sources configured in the gateway as shown below?
And try to add an additional parameter in the source step. Please have a try.The issue might be related to Databrick's new Cloud Fetch architecture in runtime 8.3 and above. With a cluster runtime of 7.3 the refresh on service worked smoothly for the same dataset. The issue only occurs, when merging on prem with cloud data in PBI power query and using a on prem Enterprise gateway. As 7.3 has end of support in September the fix below worked for clusters running on 10.4.
let
Source = Databricks.Catalogs("*********************", [EnableQueryResultDownload="0"]),
hive_metastore_Database = Source{[Name="hive_metastore",Kind="Database"]}[Data],
default_Schema = hive_metastore_Database{[Name="default",Kind="Schema"]}[Data],
prod_parts_atb_yearly_forecast_Table = default_Schema{[Name="prod_parts_atb_yearly_forecast",Kind="Table"]}[Data]
in
prod_parts_atb_yearly_forecast_Table
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Lucien
Hello, I have the same problem in Power BI desk top with the same error - any help would be appreaciated:
LE DB or ODBC error: [DataSource.Error] ERROR [HY000] [Microsoft][Hardy] (35) Error from server: error code: '0' error message: '[Microsoft][Hardy] (134) File 53e05d2e-7af6-4ff6-a5da-da9d97bdd24c: A retriable error occurred while attempting to download a result file from the cloud store but the retry limit had been exceeded. Error Detail: File 53e05d2e-7af6-4ff6-a5da-da9d97bdd24c: The result file URL had expired on 1730723653319 (Unix timestamp)'
Hi,
I am trying to connect to databricks via Direct Query and getting the same error.
Sometimes visuals will take almost 1-2 minutes to refresh and most of the times getting the same issue and this is happening for nearly 3 reports.
Can anyone help on it.
This report is a old one that its PBIX file used be saved on the user PC. Since the beggining this year the report is presenting few buggs. I belived that it has been caused by a Power BI upgrade.
This particular issue was happening when I was trying to refresh on the Power BI Desktop. I fixed the issue downsize the table used on the report.
Thank you guys for so my good ideas.
Hi @Anonymous ,
Has your problem been solved, if so, please consider Accept a correct reply as the solution or share your own solution to help others find it.
Best Regards
Lucien
Hi @Anonymous ,
Do you have the cloud and on-premise data sources configured in the gateway as shown below?
And try to add an additional parameter in the source step. Please have a try.The issue might be related to Databrick's new Cloud Fetch architecture in runtime 8.3 and above. With a cluster runtime of 7.3 the refresh on service worked smoothly for the same dataset. The issue only occurs, when merging on prem with cloud data in PBI power query and using a on prem Enterprise gateway. As 7.3 has end of support in September the fix below worked for clusters running on 10.4.
let
Source = Databricks.Catalogs("*********************", [EnableQueryResultDownload="0"]),
hive_metastore_Database = Source{[Name="hive_metastore",Kind="Database"]}[Data],
default_Schema = hive_metastore_Database{[Name="default",Kind="Schema"]}[Data],
prod_parts_atb_yearly_forecast_Table = default_Schema{[Name="prod_parts_atb_yearly_forecast",Kind="Table"]}[Data]
in
prod_parts_atb_yearly_forecast_Table
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Lucien
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
User | Count |
---|---|
84 | |
69 | |
68 | |
39 | |
39 |