Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
April 13–15 - Dare to Unleash a New Professional You at Qlik Connect 2026: Register Now!
cancel
Showing results for 
Search instead for 
Did you mean: 
RickyK
Contributor III
Contributor III

ERROR [08S01] TDSConnectionBroken, TDSConnectionFailed

Hi All,

Greetings!!

This is my first post in Qlik community, hope this goes well!

I'm facing the below error  while trying to connect to production server through an AZURE SQL Database Connection from Qlik Sense.

ERROR [08S01] TDSConnectionBroken, TDSConnectionFailed

The error is consistent but the table it was hitting is inconsistent.

It means, sometimes it is throwing an error while fetching the records from X table but next time there is no issue in fetching the data from the same table.

Note: we already check with DB team and no issues from their end

Can you please advice on the above issue at earliest? Thanks in advance!

 

Ricky

Labels (1)
9 Replies
Jack_Guo
Support
Support

Hi @RickyK ,

It sounds like a network connection issue between Qlik Sense server and database server. You may need to contact the network admin to trace the traffic between Qlik Sense server and data source server.

RickyK
Contributor III
Contributor III
Author

Hi Jack_Guo,

Thanks for your reply.

we have already check with network team and they confirmed no network glitch from their end.

Regards,

Ricky

Jayrathod2
Partner - Contributor II
Partner - Contributor II

Hi,

I am getting the same issue If is any solution then please share.

It will help us.

 

Thanks,

Jay

Michele-Gava
Partner - Contributor II
Partner - Contributor II

Same error here (Azure SQL via DirectAccess):

The complete error message in the log is:

Error: Internal error. (Connector error: Status(StatusCode="Internal", Detail="ERROR [08S01] TDSConnectionBroken, TDSConnectionFailed, ") (DirectAccess-1512))

 

Any help would be highly appreciated

 

Thanks,

Michele

krishna20
Specialist II
Specialist II

Hi @Michele-Gava 

Typically indicates a network or database connection issue, often related to communication failure between the Qlik Sense server and the database server.

Possible Causes:
Network Issues:
Firewall or Network Configuration: Check if firewalls or network configurations are blocking communication between the Qlik Sense server and the database server.
VPN Issues: If using a VPN, ensure the VPN tunnel is configured correctly for the Qlik Sense Live Server.
Network Glitches: Temporary network disruptions can also cause this error.
Database Server Issues:
Server Downtime: Ensure the database server is running and accessible.
Database Connection Settings: Verify the database connection settings (username, password, host, etc.) are correct.
SQL Server Configuration: Ensure TCP/IP protocol is enabled in the SQL Server Configuration.
Long-Running Queries: A long-running query might cause the connection to become idle and timeout.

Verify Network Connectivity:
Ping Test: Use the ping command to check if the Qlik Sense server can reach the database server.
Trace Route: Use traceroute to trace the network path between the Qlik Sense server and the database server.

mayuringale25
Partner - Creator
Partner - Creator

Hi @Michele-Gava ,

 

I am getting same error. Have you got the solution?

 

Internal error. (Connector error: Status(StatusCode="Unavailable", Detail="Error reading next message. IOException: The request was aborted. IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. SocketException: An existing connection was forcibly closed by the remote host.", DebugException="System.IO.IOException: The request was aborted.") (DirectAccess-1512))

 

Thanks and Regards
Mayur Ingale
Vegar
MVP
MVP

I suggest you reach out to someone responsible for your source system and ask them to troubleshoot this on their end.

I ran into this ERROR [08S01] issue recently. It was not the network, but the source system that was the cause In my case.

I ran Qlik extracts from a Dremio cluster that thew this error. The reason for these errors turned out to be instability issues in some executor nodes and the master node in the Dremio setup.  Once these instability issues was fixed then the errors in Qlik stopped. 

 

mayuringale25
Partner - Creator
Partner - Creator

Hi @Vegar will check with DB team but

same connection is working for on-prem 

Thanks and Regards
Mayur Ingale
Michele-Gava
Partner - Contributor II
Partner - Contributor II

Hi

not yet

We figured out that the issue is randomly firing during extraction of quite large tables (~15M records), so we suppose connection getting timed-out

We are working with db administrators to check Azure Sql instance settings

Let you know if we can work it out

Thanks

Michele