Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join 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

Reply
Element115
Super User
Super User

BUG::MS SQL error when connecting to a lakehouse directly from LH name list in UI

STEPS:

 

0__open existing Dataflow Gen2

1__right click in query pane and select New Query-->More...

2__In the Get Data-Choose data source dialog that opens, click on the name of the exisiting lakehouse (that the user created in a previous step) in the OneLake data hub pane under the New sources section

3__here is the screenshot of the error message that appears:

MSSQL_error_connecting2LH_in_Fabric.jpg

 

And the same occurs when selecting More... from the New Sources section and proceeding to choose Lakehouse and just going through all the prompts after that:

MSSQL_error_connecting2LH_in_Fabric_1.jpg

4 REPLIES 4
v-cboorla-msft
Microsoft Employee
Microsoft Employee

Hi @Element115 

 

Thanks for using Microsoft Fabric Community.

Apologies for the inconvenience that you are facing here.

I tried to repro the same steps mentioned in the ask. I didn't find any difficulty in accessing the Lakehouse. Please find the screenshots for reference.

vcboorlamsft_0-1706033372624.png

vcboorlamsft_3-1706033642620.png

vcboorlamsft_2-1706033421064.png

Could you please try once and let us know if the issue still persists. Gald to help.

 

Hope this helps.

 

 

 

After posting, I realized something that might have a bearing on this.  The DF I had re-opened for edit--I was trying to add a second query in it--well, the DF had already run with one query, and the DF was published without specifying a destination, so that the one query would not get persisted to any user created LH.  

 

When I tried to add a second query to the second DF in the chain, DF which was persisted this time to a user created LH, no such error message would pop up.  

 

If that is the cause, it might be a good idea to generate a more user-friendly error message explaining better what the cause of the error or rather, why some action cannot be performed as intended.

Hi @Element115 

 

Apologies for the delay in response from my end.

Following up to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.


Thanks.

Hi @Element115 


We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
If you have any question relating to the current thread, please do let us know and we will try out best to help you.
In case if you have any other question on a different issue, we request you to open a new thread.


Thanks.

Helpful resources

Announcements
May FBC25 Carousel

Fabric Monthly Update - May 2025

Check out the May 2025 Fabric update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.