Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago
Solved

Dataflows Gen2 not connecting to lakehouse

Hello everyone,

 

Since this morning the dataflows gen2 are no longer connecting to the lakehouses. Notebooks, datasets and the UI can still connect to the lakehouse. I can write and read data from it using those methods.

 

However, existing and new dataflows gen2 are getting a timeout after 30 seconds of trying to connect.

"Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"

 

Neither the SQL endpoint, or the Lakehouse itself works. I can see them in the workspace through dataflows gen2, but cannot connect to any of them (Not the normal Lakehouse or the "hidden" DataflowsStagingLakehouse).

 

Does anyone have a solution for this? Currenly it breaks my workflows.

Dataflows
Need Help

6 Replies

  • miguel's avatar
    miguel
    Icon for Community Admin rankCommunity Admin
    2 years ago

    Hi

     

    Please go ahead and reach out to our support team by creating a support ticket. An engineer will be able to perform an investigation to determine what might be happening with your specific tenant and the connections to the Lakehouse with Dataflows.


    Link to support: https://support.fabric.microsoft.com/support

     

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    I did, but i did not get an answer within the 4 hour time period. Are there any costs associated with putting a ticket into there?

  • v-cboorla-msft's avatar
    v-cboorla-msft
    Icon for Microsoft Employee rankMicrosoft Employee
    2 years ago

    Hi Anonymous 

     

    Thanks for using Microsoft Fabric Community.

    Apologies for the inconvenience that you are facing here.

    I found an article where a thorough list of troubleshooting methods that can be used to connect to the SQL server are mentioned.

    This might help in resolving your issue.

     

    Please do let us know if you have any further questions.

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi Jonan,

    Did it used to work before yesterday?

    We're seeing issues in the same sort of area, and are trying to trace through our networks.

    Is your SQL instance in Azure or on-prem?

     

    Interesting to see if it was a change in the solution, or we are all seeing the same problem that could be resolved with config.

    Cheers

    Richard