Lakehouse SQL to Dataflow Keeps Failing

[JP8991]

Hello,

For the last few days I am getting a failed Gen 1 Dataflow when returning a table from an SQL table in my Fabric Lakehouse.

DataSource.Error: Microsoft SQL: 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.)

It was working absolutely fine the other day and now it has stopped working and no changes have been made.

It works fine when copying all tables from the Dataflow to a PBIX and running it from there.

Can anyone help me please?

[miguel]

@JP8991  Could you please confirm if this is only happening in Gen1 Dataflows or is it something that you're also experiencing in Gen2 Dataflows?

The error is coming directly from the source and not directly from the Dataflow, so that's another aspect of it and that's what @v-cboorla-msft  was primarily referring to. If you can repro this on a Gen2 Dataflow, please let us know.

[JP8991]

@v-cboorla-msft thanks for reply I really do appreciate it however unless I have misunderstood your reply it would be great if you understood my issue fully.

Network issues will not be an issue as this is all housed within the Microsoft environment on a P2 SKU, I am querying data from a SQL table in a Fabric Lakehouse using a Dataflow, the query itself is not complicated at all containing just one where clause and returning less than 10,000 results.

Server Issues not sure how this can be a problem as the SQL database itself is currently only being queried by this dataflow. Also there is absoluteley no issue using a Power BI Desktop file to do the same thing.

Look forward to hearing from you.

[v-cboorla-msft]

Hi @JP8991 

Thanks for using Microsoft Fabric Community.

The error "DataSource.Error: Microsoft SQL: 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.)" in Microsoft Fabric indicates an issue with the connection between your application and the SQL Server.

Network Issues: Temporary network glitches, firewall restrictions, or overloaded routers can disrupt communication. SQL Server Issues: The SQL Server itself might be overloaded, experiencing software bugs, or configured incorrectly. TLS Mismatch: Outdated client-side libraries or server-side configurations that don't support the required TLS (Transport Layer Security) version can cause connection issues.

For more details please refer : An existing connection was forcibly closed by the remote host.

If the issue still persists, please do let us know. Glad to help.

I hope this information helps.

Thank you.