Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Boa tarde,
Meu relatório está carregando dados de uma tabela de sql-server localizada na nuvem, e algumas vezes ocorre esse erro TDSConnectionFailed. O erro não ocorre sempre na mesma tabela, já realizei um teste e o banco retorna quando ocorre o erro, caso acontecer e iniciar novamente a carga ela volta a funcionar. Esse problema já aconteceu com algum dos senhores, alguém tem alguma ideia do que é possível fazer.
Desde já agradeço.
Exemplo do erro no log do QMC em anexo
Hi @Ruan_Sasse
Good afternoon 🙂
As I mentioned, it's mainly network or database server related.
So indeed a communication issue between QS and SQL server.
Could you provide the question in english?
My report is loading data from a SQL Server table located in the cloud, and sometimes I encounter this error: TDSConnectionFailed. The error does not always occur on the same table. I have conducted a test, and when the error occurs, the database does respond. If I restart the load, it works again.
Has anyone experienced this issue before? Does anyone have any ideas on what can be done to resolve it?
Thank you in advance.
Example of the error in the QMC log attached.
Sure! Below is the text in English
Hi @Ruan_Sasse check
Also
It's mainly network or database server related, does not have to be more than a glitch so if you check database connectivity after the error you will not able to verify the issue.
That's also why it does not happen regularly or on the same table.
Good morning, everything alright? Thanks for your response. In the first link, the information refers to an ODBC connection, but in my case, the native Qlik Sense connector for Microsoft SQL Server was used, so I believe the suggestions mentioned there do not apply. As for the second link, it seems that the topic was left without a solution as well.
So, is the most likely cause the communication between the Qlik Sense server and the SQL Server database located in the cloud?
Hi @Ruan_Sasse
Good afternoon 🙂
As I mentioned, it's mainly network or database server related.
So indeed a communication issue between QS and SQL server.
Thank you very much!