Got the Direct Access-1512 error on qlik cloud

[Fenil]

Hi everyone, 

So I got this error day before yesterday, I am also looking into source side But please confirm if it is from qlik side or not

Thanks,

Fenil Jain.

[rubenmarin · Accepted solution]

Hi, that looks like an error from the source db, maybe the query has grown an now it returns the timeout error.

If you do a simpler and faster query it works? If it works that would confirm something on the source db.

Possible solutions on this case would be to increase the timeout value, or do incremental loads to keep the querys below the timeout values.

[Fenil]

@rubenmarin 

Ok, This Dashboard usually takes 4 minutes to load, there are 3 datasets in script which runs. So qlik was running for 10 minutes and then gave this error becuase I have set up 10 minutes query timeout.
So I also think it is from source. Thanks for reply, I will check on source side.

[mayuringale25]

Hi @Fenil ,

I am getting this error after upgrade to 1.7.7

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)) if you have resolved can you please guide

Spoiler

[Andrea_Bertazzo]

hi @mayuringale25 
The message you got seems different from the original in the post.

In particular, the error "Internal error. (Connector error: StatusCode=Unavailable)" could be related to connectivity issuesor to network problems.

I would try the following:

1. Ensure your Qlik Data Gateway server meets system requirements, particularly CPU and RAM.
2. Verify that the gateway is installed on a dedicated machine, not shared with other Qlik components.
3. Check that the server time is correctly synchronized.

If these steps don't resolve the problem, I would suggest to contact Qlik Support and send all the information listed in this article.

[Fenil]

@mayuringale25 You can follow the suggestion from @Andrea_Bertazzo , And we have not solved this error, We are now retrying through automation if it fails first time and then we are reloading again and if it fails second time we send the mail to developers. So we are not getting this error continuosuly in rare case it fails both times.

Even now it often comes, but for the error i got this is the solution qlik support has provided.

They have also asked us to change some configuration for gateway but that didn't work also so we went with automation.

Thanks,

Fenil Jain.

[mayuringale25]

HI @Fenil  I have tried using automation but still same error

@Andrea_Bertazzo Dateway server looks fine as my other sources via gateway are working fine but some databricks table are creating this issue

We have raise this to Qlik Support also to databricks team