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
Hey together,
since last week our Data Warehouse connection had errors:
"Message=<ccon>Warning: Fatal error 615 occurred at May 26 2025 8:08AM. Note the error and time, and contact your system administrator.\r\nLogin failed for user '<token-identified principal>'.</ccon>, Code=21, State=1"
AND
ErrorCode=SqlFailedToConnect,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Cannot connect to SQL Database. Please contact SQL server team for further support. Server: 'xxx', Database: 'xxx', User: ''. Check the connection configuration is correct, and make sure the SQL Database firewall allows the Data Factory runtime to access.,Source=Microsoft.DataTransfer.Connectors.MSSQL,''Type=Microsoft.Data.SqlClient.SqlException,Message=Warning: Fatal error 615 occurred at May 22 2025 12:15AM. Note the error and time, and contact your system administrator.
Login failed for user '<token-identified principal>'.,Source=Framework Microsoft SqlClient Data Provider,'
I have restored the database, but the lakehouses have the same errors. When I look at the tables in the Lakehouse view, I see data but when I switch to the SQL endpoint, I no longer see any data and the error message appears. This is all since May 22nd, since the MS Fabric update.
Is there a Solution for the Lakehouse
Many thanks
Solved! Go to Solution.
Hi @HarderT ,
You can utilise Semantic Link Labs to repoint to new lakehouse.
Hi @HarderT,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Vinay Pabbu
Hi @HarderT,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Vinay Pabbu
Hi @v-vpabbu,
the Problem now is when we change the connection it creates a new report and does not overwrite the old one.
Hi @HarderT ,
You can utilise Semantic Link Labs to repoint to new lakehouse.
Hi @HarderT,
Thats the Default behaviour. Power BI treats it as a new data source, which results in a new report being created instead of overwriting the existing one.
if you're using Power BI Desktop, you can try updating the connection string from within the file and republish it, which should overwrite the existing report.
Regards,
Vinay Pabbu
@v-vpabbu thanks for your quick respond. But I need a quicker solution.
Is there any way, where I can rebind a semantic model from one lakehouse to an other?
Because I want to save myself the work of recreating everything. That's why I want to create a new lakehouse and connect the source data there and then convert the semantic model on which reports are already based to it
Hi @HarderT,
Yes, you can rebind the semantic model to a new Lakehouse. Just make sure the new Lakehouse has the same table names and structure. Then open the semantic model in Power BI Desktop, go to Data source settings, and point it to the new Lakehouse’s SQL endpoint. After that, publish it back.
Regards,
Vinay Pabbu
Hi @HarderT,
Thank you for reaching out to Microsoft Fabric Community Forum.
At this time, there is no option in Fabric to disable or re-enable the SQL endpoint manually, and the issue requires backend support from Microsoft to resolve.
As a temporary workaround, copy your tables to a new Lakehouse using a Spark notebook, which will reinitialize the SQL endpoint properly.
Since error 615 is a fatal metadata/page-level error and the SQL endpoint is broken even though data is visible in Lakehouse Explorer, it likely needs backend repair by the Microsoft Fabric team.
Please raise a support ticket with Microsoft, referencing the exact error message and timestamp.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Vinay Pabbu
Hi @HarderT,
As we haven't heard back from you, I hope you have raised a support ticket. At this time we are closing this thread. If you have any further issues, please start a new thread in the community forum, and we are here to assist you. Thankyou for your understanding and continuous support.
Thank you for being part of the Microsoft Fabric Community.
Regards,
Vinay Pabbu
User | Count |
---|---|
13 | |
4 | |
3 | |
3 | |
3 |
User | Count |
---|---|
8 | |
8 | |
7 | |
6 | |
5 |