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
Hi,
I have faced an issue this afternoon of creating a new lakehouse in Fabric workspace. There are lots of errors me and other people used Microsoft Fabric got this week.
1. I can't connect to Lakehouse SQL Analytics Endpoint using pyODBC in python. It returnes the error:
System.Private.CoreLib: Exception while executing function: Functions.tenant-onboarding-fabric-provisioner. System.Private.CoreLib: Result: Failure
Exception: OperationalError: ('08S01', '[08S01] [Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host.\r\n (10054) (SQLDriverConnect); [08S01] [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure (10054)')
2. After creating a lakehouse, its Semantic model and SQL Analytics Endpoint failed to be created
In Fabric UI, it keeps showing "Creating SQL Analytics Endpoint" which took for like 2 hours and then failed.
3. With the Lakehouse we created before, now I can't run SQL query (SELECT, CREATE SCHEMA...) within the SQL Analytics Endpoint tab inside the Fabric Lakehouse.
There are so many issues with Lakehouse/Warehouse's SQL Analytics Endpoint now, i guess.
Thank you!
Solved! Go to Solution.
The issues you're experiencing with connecting to and using the Lakehouse SQL Analytics Endpoint in Microsoft Fabric can stem from several known problems and limitations.
Connection Issues with PyODBC
The error you encountered (OperationalError: ('08S01', '[08S01] [Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host')) suggests a network or configuration issue.
Here are possible causes and solutions:
Driver Version: Ensure you're using ODBC Driver 18 or higher, as this is required for Microsoft Fabric connections.
Authentication Issues: If you're using service principal authentication, verify that the client ID, tenant ID, and client secret are correctly configured. Use ActiveDirectoryServicePrincipal for authentication.
Network Configuration: Check if your network allows outbound traffic to the SQL Endpoint. Firewalls or network policies might block the connection.
TLS Negotiation: Some users have reported intermittent TLS negotiation issues (error code 0x2746). Using an updated driver and ensuring proper certificate trust settings can help.
Retry Mechanism: Add retries in your connection logic, as transient issues may resolve on subsequent attempts.
Sample connection string:
connection_string = f"Driver={{ODBC Driver 18 for SQL Server}};Server={server};Database={database};Authentication=ActiveDirectoryServicePrincipal;UID={clientId};PWD={clientSecret};Encrypt=Yes;TrustServerCertificate=No"
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Hi @lyjavier ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you as Accept as Solution or sharing your solution. It would be greatly appreciated by others in the community who may have the same question.
Thank you for being a valued member of the Microsoft Fabric Community Forum!
Hi @lyjavier ,
We wanted to follow up since we haven't heard back from you regarding our last response. We hope the issue has been resolved.If the answer resolved your query, please mark it as "Accept as Solution" and select "Yes" if it was helpful. Still needed any further assistance, feel free to reach out.
Thank you for being a valued member of the Microsoft Fabric Community Forum!
Hi @lyjavier ,
I just wanted to kindly follow up to see if you had a chance to review the previous response provided by community members. I hope it was helpful. If yes, please Accept the answer so that it will be helpful to others to find it quickly.
Thank you for being a part of Microsoft Fabric Community Forum!
The issues you're experiencing with connecting to and using the Lakehouse SQL Analytics Endpoint in Microsoft Fabric can stem from several known problems and limitations.
Connection Issues with PyODBC
The error you encountered (OperationalError: ('08S01', '[08S01] [Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host')) suggests a network or configuration issue.
Here are possible causes and solutions:
Driver Version: Ensure you're using ODBC Driver 18 or higher, as this is required for Microsoft Fabric connections.
Authentication Issues: If you're using service principal authentication, verify that the client ID, tenant ID, and client secret are correctly configured. Use ActiveDirectoryServicePrincipal for authentication.
Network Configuration: Check if your network allows outbound traffic to the SQL Endpoint. Firewalls or network policies might block the connection.
TLS Negotiation: Some users have reported intermittent TLS negotiation issues (error code 0x2746). Using an updated driver and ensuring proper certificate trust settings can help.
Retry Mechanism: Add retries in your connection logic, as transient issues may resolve on subsequent attempts.
Sample connection string:
connection_string = f"Driver={{ODBC Driver 18 for SQL Server}};Server={server};Database={database};Authentication=ActiveDirectoryServicePrincipal;UID={clientId};PWD={clientSecret};Encrypt=Yes;TrustServerCertificate=No"
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Hi @lyjavier ,
Thank you for reaching out to the Microsoft Fabric Community Forum about the issue you're encountering.
Upon reviewing the error message, the error might be because of configuration issue where the connection may be getting disrupted due to a timeout or SQL server connectivity problems.
1.Try to update the ODBC drivers with the latest.
Try checking the workspace capacity, if it hits capacity this could cause the connection to fail.
Try connecting to the SQL Analytics Endpoint using a different tool like SSMS or Azure Data Studio using same connection parameters.If connections succeeds, the problem might be with the code.
2.For th second one,issue might be transient, retrying after some time may help to resolve the issue.
Ensure that your workspace has enough capacity to create and support a new Lakehouse.
3.For third one,if the SQL Analytics Endpoint is stuck in the "Creating" state or if it failed to initialize, you may not be able to run any queries.
If this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
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 |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
3 | |
3 | |
2 | |
2 | |
1 |