Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hello,
I can no longer use the SQL endpoint of some Lakehouses.
I've tried refreshing the metadata, but I consistently get the error message “Internal error SqlLoginFailureException”
does anyone have any ideas?
Solved! Go to Solution.
Hi @amolt ,
I suggest reaching out to Microsoft Support by raising a ticket. Microsoft will analyze backend logs and provide a resolution
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Regards,
Chaithanya.
Hi @amolt ,
Just checking, have you had a chance to open a support ticket, as suggested. If so, we'd love to hear the current status or any updates from that.
If the issue was resolved through the support ticket, it would be great if you could share the solution here as well. It could really help other community members find answers more quickly.
Warm regards,
Chaithanya.
Hi @amolt ,
Thank you for reaching out to Microsoft Fabric Community Forum.
can you try the below debug to steps to solve your issue.
Ensure you have the correct permissions on the Lakehouse (e.g., Lakehouse Contributor or higher).
Check if the SQL analytics endpoint is enabled in the Lakehouse settings.
Sign out and back in to refresh your authentication token.
Clear browser cache if you're using the Fabric portal.
Verify that the Lakehouse or workspace hasn’t been renamed or moved.
Make sure you're using the latest SQL endpoint URL.
Try connecting using a different tool (e.g., SSMS, Azure Data Studio, Power BI Desktop).
Check the Microsoft Fabric status page for any ongoing issues.
Review the Power BI Support Portal for related incidents.
Raise a Microsoft support ticket if the issue persists.
beow is the link to raise support ticket : https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Regards,
Chaithanya.
Hi @v-kathullac,
Thanks for your reply.
I've checked everything and there's no change.
Regards,
Alexis
Hi @amolt ,
I suggest reaching out to Microsoft Support by raising a ticket. Microsoft will analyze backend logs and provide a resolution
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Regards,
Chaithanya.
Hi @amolt ,
appologies for the prevoius link can you try with the below mentioned link to raise a support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Learn how to create a support ticket for Fabric and Power BI, depending on your role (administrator versus user).
Regards,
Chaithanya
Hi @amolt ,
Can you check who is the owner of the Lakehouse?. This issue may occur if the owner of the lakehouse's credential expired
Regards,
Srisakthi
I've had this problem with other lakehouses, but refresh of the metadata solved the problem.
In this case, I get the error message during the metadata refresh.
Regards,
Alexis
hi @Srisakthi,
Thanks for your reply.
I'm the lakehouse owner and I don't have the problem on all lakehouses.
Regards,
Alexis
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
12 | |
4 | |
3 | |
3 | |
3 |
User | Count |
---|---|
8 | |
7 | |
6 | |
5 | |
5 |