Forum Discussion
Solved
Failed to complete the command because the underlying location does not exist
I am experiencing an issue with Microsoft Fabric where my audit table shows data successfully loaded into Delta tables, but the underlying files are not accessible through the SQL Analytics Endpoint....
The possible reasons behind this issue as outlined below
- Column Mapping issue: If your Delta table has some colmun types that are not supporrted, and you have enabled aspecific setting (delta.columnMapping.mode), the system might struggle to sync the metadata properly. To fix this issue, you can try removing the unsupported column from the table in your lakahouse. That might help things work smoothly again. read more about this here Known issue - SQL analytics endpoint sync failure when columnMapping is enabled - Microsoft Fabric | Microsoft Learn
- run length encoding (RLE) issue: If the Delta writer comprressed the data using a method called RLE, queries in the SQL Analytiics Endpoint might not work and colud show an error saying 'Unknown encoding type.' To fix this, you can turrn off RLE and create the Delta table again. That should help the queries run properly. read more about this here Known issue - SQL analytics endpoint table queries fail due to RLE - Microsoft Fabric | Microsoft Learn
- linked function issue: If your Delta tablas have security rules like Row Levell Security (RLS), the synicing process might not work. To fix this, you can remove the security filter, update the table, force the sync, and then put the filter back again. read more about this here Known issue - SQL analytics endpoint table sync fails when table contains linked functions - Microsoft Fabric | Microsoft Learn
Check the above once in your workspace.
Thank you!
burakkaragoz
Super User
Super UserHi ranjith_fabric ,
This issue usually pops up when the metadata and physical files in your Delta table get out of sync. Here’s a quick checklist to help you troubleshoot:
- Check if the table was recently altered (e.g., schema changes or column mapping updates). Sometimes the SQL Endpoint doesn’t pick up those changes right away.
- Try forcing a metadata refresh by running a simple DESCRIBE TABLE or querying the table from a Notebook first – this can trigger a sync.
- If you’re using RLS or any linked functions, temporarily disable them and see if the table becomes accessible.
- Also, make sure the files actually exist in OneLake – sometimes the audit log shows success even if the write partially failed.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.