Forum Discussion
Transport-level Error using Dataflows Gen2
I came here to create a post detailing almost the same problem. We are now able to successfully move tables from our On-prem SQL database to the Lakehouse using dataflows, but are getting this issue whenever we either try to move the tables from a Lakehouse to a Warehouse using a dataflow, or when we try to move data from our on-prem SQL database direct to a Warehouse. To slighly add to the mystery, it doesn't happen every time. Just mostly. Time to failure seems to decrease consistently with the row count of the table being moved.
Example error code:
DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;Message = A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.);ErrorCode = -2146232060;Number = 10054;Class = 20 GatewayObjectId: f563ceac-bba5-4f31-bd45-7e2c8dfa4b54
I've been having the same issue. I have a ticket open with Microsoft and they keep trying to get me to open the already open firewall. If I only try a a handfull of rows--say 100 or so--it works consistently. Sometimes I can get it to transfer a few thousand. Then it will simply stop working...almost like I've run too many tests and it needs a break for a while.
Agree with everything you said
This is finally working--going directly from on-prem SQL to a warehouse--for me. The first time I run to load data to a new table, I have to limit the load to just a few rows or I get the transport-level error. Once the new table is in the warehouse, though, I can load the full 5 million plus row dataset.
- What version is your gateway?
