Forum Discussion

MBaldo's avatar
MBaldo
Frequent Visitor
2 years ago
Solved

Issue setting destination on dataflow to Lakehouse, data originating from SQL via data gateway

Hi all,

 

So we seem to be having issues creating dataflow gen 2 utilising the data gateway in a fabric trial.

I can configure the dataflow get 2 to with a connection to the local sql instance fine, and I can bring in the preview data and perform all the usual Power Query transformations perform the following actions:

Set destination

Select lakehouse

Configure connection details (using data gateway and an org account 

select next

select workspace and lakehouse (new table)

select next

 

And the following error occures

 

Something went wrong while retrieving the list of tables. Please try again later.: An exception occurred: Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) (Session ID: 38b7176d-7bf7-4d48-a7aa-80db2e79989f, Region: uk)

 

We have port 433 open to everywhere on the gateway server, and I've had the network chaps configure

 

  • Protocol: TCP
  • Endpoints: *.datawarehouse.pbidedicated.windows.net, *.datawarehouse.fabric.microsoft.com, *.dfs.fabric.microsoft.com
  • Port: 1433

Anyone with experiance of this?

 

Dataflow
Need Help
  • MBaldo's avatar
    MBaldo
    2 years ago

    Hi there, just an update to this, the issue was caused by the above URL's still being blocked on port 1433. The network guys had incorrectly configured the firewall rules.

     

    Thanks all who looked.

     

    Matt

5 Replies

  • MBaldo's avatar
    MBaldo
    Frequent Visitor
    2 years ago

    Hi there, just an update to this, the issue was caused by the above URL's still being blocked on port 1433. The network guys had incorrectly configured the firewall rules.

     

    Thanks all who looked.

     

    Matt

    • caomayan's avatar
      caomayan
      Helper I
      2 years ago

      Thanks for the update! so I got the exact same error and asked the network guy to add those endpoints...there should be no more steps for the configuration, right? 

      • Protocol: TCP
      • Endpoints: *.datawarehouse.pbidedicated.windows.net, *.datawarehouse.fabric.microsoft.com, *.dfs.fabric.microsoft.com
      • Port: 1433
  • SaiTejaTalasila's avatar
    SaiTejaTalasila
    Super User
    2 years ago

    Hi MBaldo ,

     

    Are you seeing the same issue when selecting any other data warehouse /lakehouse .Are you using the fabric trail capacity?

     

    Thanks,

    Sai Teja 

    • MBaldo's avatar
      MBaldo
      Frequent Visitor
      2 years ago

      Hi there Sai,

       

      We are using the trial capacity. This issue is across the board, so same result with several workspaces/lakehouses we have tested.

       

  • MBaldo's avatar
    MBaldo
    Frequent Visitor
    2 years ago

    Ok, this seems to be an issue with how the traffic is being handled by our firewalls (Palo Altos) so maybe a bit beyond the scope of this forum. Although if anyone has experiance of this, it wouldn't hurt to share 🙂 I'd be interested.