Forum Discussion
SQL Endpoint error: Failed to complete the command because the underlying location does not exist.
Sorry for the late response. I don't find a specific API or something else that can help refresh the SQL Endpoint of a lakehouse automatically. I captured the trace of the "refresh" action in Explorer. It seems trigger a metadata refresh of the SQL endpoint. But I failed to covert it into a valid call we can use for the automation process.
You may try setting a longer waiting time after starting the capacity. If this still doesn't work, I would suggest creating a support ticket to ask escalation engineers to help check the failue. This looks more like a synchronization issue.
In addition, a lakehouse generates a default semantic model. You can manage the default semantic model or create customized semantic models from it. Maybe you can consider using the default semantic model or customized semantic models for your reports. Default Power BI semantic models - Microsoft Fabric | Microsoft Learn
Best Regards,
Jing
From this documentation, I learned that Dataverse will generate a lakehouse, SQL endpoint, and a default Power BI semantic model in the Fabric workspace. Do you run a Logic App to refresh the default semantic model generated by Dataverse? Or do you customize another semantic model then use a Logic App to refresh it?
May I know how you manually refresh the SQL Endpoint? To my knowledge, the associated SQL Endpoint will be updated automatically after the lakehouse has been updated. I don't find where I can refresh a SQL Endpoint. Can you help point it out? Maybe I have missed it.
Additionally, if you want to refresh a semantic model at a scheduled time, there is a preview Semantic model refresh pipeline activity in Data Factory currently. You can create a data pipeline in Data Factory and add a Semantic model refresh activity for refreshing a specific semantic model. Then schedule to run the pipeline. Maybe this could be an alternative.
Data Factory Spotlight: Semantic model refresh activity | Microsoft Fabric Blog | Microsoft Fabric
Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!
This has been discussed in other threads. The SQL endpoints refresh, but not immediately. There is a random delay that makes things unpredictable.
Hello!
I refresh first the Lakehouse semantic model, then the Power BI semantic model.I read in another thread that the Lakehouse semantic model doesn't affect the SQL endpoint refreshness, is that true? If so, refreshing it would not affect the error in the endpoint.
Edit: I refresh the SQL Endpoint by entering and manually click on refresh button:Sorry, I misunderstood what you meant. So you have created a Power BI dataset which is getting data from a Fabric lakehouse by connecting to the SQL Endpoint. Then you use a Logic App to refresh the Power BI dataset, right?
Regards,
JingHi Anonymous
Let me explain better:
I created a Link to Fabric connection to get data from D365 CE (Dataverse).
After that, I created some views that read a few tables from the Lakehouse, and those views I connected them to a Power BI report (desktop to be specific) and then published my report.
Then I created a Logic App automation that starts the capacity in the morning, waits for around 20min, then refreshes the report.
Even after waiting 20min, I get the error of this case.
If I manually refresh the SQL Endpoint (by entering the SQL Endpoint and click on refresh button), I can refresh the report, but going this way I lose all the intention of automate the process..
