Forum Discussion
Our SQL Endpoint is down
Hello everyone,
Our SQL endpoint has completely failed
- Zugrunde liegender FehlerPowerBI service client received error HTTP response. HttpStatus: 400. PowerBIErrorCode: QueryUserError
- QueryUserErrorEs konnte keine Verbindung mit der Datenquelle mit dem Namen "{"protocol":"tds","address":{"server":"xxxx","database":"xxxx"},"authentication":null,"query":null}" hergestellt werden.
and our notebooks are displaying the following error message:
Message: MwcTokenError: Failed to retrieve MWC token for "Notebook"
We need help!
Best regards
11 Replies
- v-venuppuCommunity Support
Hi HarderT ,
Thank you for reaching out to Microsoft Fabric Community.
If your SQL Endpoint isn’t working, try these below steps:
Make sure your workspace is in Direct Lake mode – SQL Endpoints don’t work in classic workspaces.Check if your Lakehouse has at least one table – it won’t start if there’s no data.Refresh the SQL Endpoint – go to the SQL Endpoint tab and click the refresh icon.Check your permissions – you need to be a Contributor or higher.Try using a different browser or incognito mode – sometimes browser issues cause problems.
If it’s still not working, restarting the Lakehouse might help.
Thank you.
- HarderTHelper II
Hi v-venuppu,
I have already tried everything you suggested, but nothing helps. Is there a way to reinitialise the workspace, since other workspaces are functioning?
It must be the workspace, since no connection can be established in SSMS either, but unfortunately other workspaces are functioning. Even when I'm trying to create a new object, I got the error that there is no connection possible.
How can I restart a Lakehouse?
Thank you!
- DataGuru412Resolver I
Hi,
I am not sure whether it is relevant or not but I saw similar token error earlier. I fyou are running something in South East Asia there might chance you will get this error.
Solved: Spark SQL error: MetaException(message: Unable to ... - Microsoft Fabric Community
- v-venuppuCommunity Support
Hi HarderT ,
Thank you DataGuru412 for the prompt response.
Currently, Microsoft Fabric doesn’t offer a direct “restart” button for Lakehouses, but here are a few steps you can try:
Use the Fabric REST API to delete and recreate the Lakehouse in the same workspace. This can help reset the SQL endpoint and resolve connection issues.
Visit the Admin Portal to see if the Lakehouse is stuck in provisioning or showing any alerts.
Try creating a new Lakehouse in the same workspace to confirm if the issue is workspace-specific.
If using notebooks, reattach the Lakehouse using the %%configure magic command to reset the session reference.
If the issue still persists,I recommend submitting your issue through Microsoft's official Support Ticket channel, such as the:How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you.
- HarderTHelper II
Hello,
somehow it works again.
The only thing that does not work is the source code management. - v-venuppuCommunity Support
Hi HarderT ,
Thanks for the update..!!
After the SQL Endpoint outage, SCM may still fail until you reset the Git link.
Here are some steps that will help:Disconnect and reconnect Git in Workspace > Source control.Check repo & branch still exist and your permissions are correct.Clear browser cache or try an incognito window.If still failing, re-link SCM to a new branch/folder.
If issues still persist, you can raise a Support Ticket as suggested earlier.
Thank you.