Forum Discussion
Semantic Model Refresh Error - Microsoft Fabric
When I tried to refresh the semantic model, I got the following error. (Microsoft Fabric)
Please note that this semantic model was created by one of our former employees. After he left, we took over the semantic model and created a gateway to take over successful.
Hello kasun_rumesh,
Thank you for reaching out with the details of the error you're encountering during the semantic model refresh. The error message indicates an issue with the Delta table DimFlushingMethod, specifically an "invalid delta log," which is causing the refresh to fail.Here are some steps you can take to resolve this:
- Check if the DimFlushingMethod table exists and is accessible in the Lakehouse.
- If the log is corrupted, you may need to recreate the table. Export the data (if accessible), drop the table, recreate it with the same schema, and reload the data.
- Since the semantic model ownership changed, ensure the new gateway and workspace permissions are correctly configured to access the table and its storage.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
5 Replies
Hi kasun_rumesh ,
I have also faced similar kind of issue , so i took over the underlying lakehouse or warehouse along with semantic model and it started working.
Regards,
Srisakthi
Hi Srisakthi,
Thanks for sharing your valuable insights. we appreciate your commitment towards community.
Hello kasun_rumesh,
Thank you for reaching out with the details of the error you're encountering during the semantic model refresh. The error message indicates an issue with the Delta table DimFlushingMethod, specifically an "invalid delta log," which is causing the refresh to fail.Here are some steps you can take to resolve this:
- Check if the DimFlushingMethod table exists and is accessible in the Lakehouse.
- If the log is corrupted, you may need to recreate the table. Export the data (if accessible), drop the table, recreate it with the same schema, and reload the data.
- Since the semantic model ownership changed, ensure the new gateway and workspace permissions are correctly configured to access the table and its storage.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.Hello kasun_rumesh,
Could you please confirm if your query have been resolved by the solution provided? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.Thank you.
Hi kasun_rumesh,
May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
