Forum Discussion

caomayan's avatar
caomayan
Helper I
2 years ago
Solved

Gen2 Dataflows can't load data into Lakehouse

Hi folks,

 

We are trying to load data using on-prem gateway from Dataflow gen2 to lakehouse, but encountered the issue, even we open the firewall rule on these endpoints on gateway servers:

 

*.datawarehouse.pbidedicated.windows.net    1433
*.datawarehouse.fabric.microsoft.com    1433

*.dfs.fabric.microsoft.com    1433 

 

The error message is showing below no matter with non-gateway or gateway lakehouse connection, is there anything we have missed?

 

 

Appreciate for any help!

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi caomayan 

     

    Despite having the necessary firewall rules turned on, you are still experiencing problems connecting to Lake Warehouse One.

     

    This error message indicates that the connection was established, but failed during the login process due to an SSL provider error.

     

    You can try the following steps:

     

    Ensure that the local data gateway has been updated to the latest version. Sometimes, updating the gateway can solve similar problems.

     

    Verify that the SSL/TLS settings on the gateway and server are properly configured. This error message indicates an SSL-related problem, so ensuring the correct protocol and certificate may be helpful.

     

    Check the logs on the local data gateway for any other error messages or clues that may help diagnose the problem.

     

    Regards,

    Nono Chen

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi caomayan 

     

    Despite having the necessary firewall rules turned on, you are still experiencing problems connecting to Lake Warehouse One.

     

    This error message indicates that the connection was established, but failed during the login process due to an SSL provider error.

     

    You can try the following steps:

     

    Ensure that the local data gateway has been updated to the latest version. Sometimes, updating the gateway can solve similar problems.

     

    Verify that the SSL/TLS settings on the gateway and server are properly configured. This error message indicates an SSL-related problem, so ensuring the correct protocol and certificate may be helpful.

     

    Check the logs on the local data gateway for any other error messages or clues that may help diagnose the problem.

     

    Regards,

    Nono Chen

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • caomayan's avatar
      caomayan
      Helper I

      Thanks a lot Nono for the reply! I'll upgrade the gateway to the latest version and try again

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi caomayan 

     

    Can you tell me if your problem is solved? If yes, please accept it as solution.

     

    Regards,

    Nono Chen

    • caomayan's avatar
      caomayan
      Helper I

      Unfortunately the issue was not fixed yet, we upgraded the gateway version, checked the log with MS support, server team has just applied the TLS protocal on the gateway, we are still investigating