Forum Discussion
Refresh error - There is no valid Delta table at this location
Hello,
I have the following error during refresh Semantic model in Service:
Data source error: DataFormat.Error: There is no valid Delta table at this location.. . The exception was raised by the IDbCommand interface.
Cluster URI: WABI-NORTH-EUROPE-C-PRIMARY-redirect.analysis.windows.net
Activity ID: 7e3deab2-59b3-2567-8eaf-55bcd5981de8
Request ID: 609de029-d9ef-de21-9f26-1aedc848ddc1
Time: 2025-10-20 10:54:14Z
PowerBI Desktop is connecting and refresh properly data to Azure Data Lake Storage Gen2 Storage account, but after publishing in Service this cannot be refreshed from there. The connection is to parquet files created by Azure Synapse Analytics / sparkpool.
In PowerBI Desktop I had similar issue after upgrade, but I found the solutions by adding [HierarchicalNavigation=true], as below, which was earlier missing, but worked in previous PowerBI Desktop version.
let
Source = AzureStorage.DataLake("https://XXXX.dfs.core.windows.net/sap/md-silver/", [HierarchicalNavigation=true]),
ToDelta = DeltaLake.Table(Source)
in
ToDelta
Could you advise?
Thank you,
rhoex
Hi rhoex ,
Please verify if this limitations is causing the error you are experiencing
Microsoft doesn't support dataflow or semantic model refresh using OAuth2 authentication when the Azure Data Lake Storage Gen2 (ADLS) account is in a different tenant. This limitation only applies to ADLS when the authentication method is OAuth2, that is, when you attempt to connect to a cross-tenant ADLS using an Microsoft Entra ID account. In this case, we recommend that you use a different authentication method that isn't OAuth2/Microsoft Entra ID, such as the Key authentication method.
Another point is as you have mentioned you are using VNet + Private Endpoints on storage account so please configure a Vnet gateway and re check.
What is a virtual network (VNet) data gateway | Microsoft LearnOverview of virtual network (VNet), private links, and Power BI | Microsoft Learn
Create virtual network (VNet) data gateways | Microsoft Learn
I hope this information helps. Please do let us know if you have any further queries.
Thank you
8 Replies
- ibarrau
Super User
Hi, Power BI Service runs in a different execution context than Desktop. It must have direct access to the Delta Lake folder and its metadata (_delta_log). Any failure in path resolution, authentication, or file structure will break it. Ensure you're pointing directly to the folder containing the Delta table, not just a parent folder. I guess something like:
let Source = AzureStorage.DataLake("https://xxxx.dfs.core.windows.net/sap/md-silver/my_table/", [HierarchicalNavigation=true]), ToDelta = DeltaLake.Table(Source) in ToDeltaOther checks to consider:
- Go to the lake and make sure there is a valid _delta_log folder.
- Validate the azure storage account lakehouse has the hierarchical namespace property enabled.
- Make sure you have edited the credentials at the semantic model settings correctly
- As an alternative you can use AzureLakeStorage function at power query from the azure data lake gen2 connector to navigate the lake until the table and then add a custom step for DeltaLake.Table.
I hope that helps,
- pagaczpagaczFrequent Visitor
Can you please specify networking setup? It looks like a network issue to me. Power BI Service and Power BI Desktop expect to have the same behavior (if networking is configured as it should).
- rhoex
Helper I
Thank you ibarrau for the suggestions.
I’ve reviewed them, but unfortunately they didn’t resolve the issue. Any further advice would be greatly appreciated.
Hi pagaczpagacz , in response to your question about the networking setup — we’re using:VNet + Private Endpoints on storage account
- v-nmadadi-msft
Community Support
Hi rhoex ,
This issue happens when the data source you used, within Power BI Desktop, isn't supported for refresh. You need to find the data source that you're using and compare that against the list of supported data sources at
Data refresh in Power BI - Power BI | Microsoft Learn
Data refresh in the Power BI service will fail when the source column or table is renamed or removed. It fails because the Power BI service doesn't also include a schema refresh. To correct this error, a schema refresh needs to happen in Power BI Desktop and the semantic model needs to be republished to the service.
I hope this information helps. Please do let us know if you have any further queries.
Thank you- rhoex
Helper I
Hi v-nmadadi-msft, thank you for your response.
I reviewed the link you shared and through additional page it can be concluded that Azure Data Lake Storage Gen2 with Delta Lake is supported.
Reminding that Power BI service doesn't include a schema refresh is useful but not in my case. I testing refresh in Servce, without changing anything since publishing this from from PowerBI Desktop.Thank you,
rhoex
- v-nmadadi-msft
Community Support
Hi rhoex ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you. - v-nmadadi-msft
Community Support
Hi rhoex
May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.
Thank you