Discussion board where members can get started with Qlik Sense.
I am working with Qlik Sense Enterprise on amazon ec2.
Almost all day I am working fine, doing reloads and working without problems. But sometimes when the reload completes i get the following error.
after 30-40 seconds after I receive the message, and I reload the engine is working fine. No outside users have this error. It happens only when I reload, and it doesn't happen every time. How can I identify what the problem is?PS: I have whitelisted everything neccessary in the proxy settings
I had a similar issue with an earlier release of Qlik Sense (~April 2018) and it turned out to be due to having the Extended Security Environment option checked under the virtual proxy.
The end result was if I had the data load editor and another window open eg the App Overview then I would receive the error.
The workaround was to only have one window open at a time for the selected user and it appears to have been fixed in the June release.
Hope this helps.
I don't have the extended properties checked. If i have to work on a single window it may prove quite slow, usually I work with 3-5 different tabs open...
Anybody have other suggestions?Or perhaps some logs that I can check to find where the problem lies?
Agreed - if you are on the September release the error I referred to should have been addressed.
This seems like a proxy / virtual proxy issue so I would suggest checking the proxy log files.
Also, are you on working on a standalone server or is this part of a cluster?
If there is nothing obvious in the log then I would lodge a call with support as it may be a repository or security issue.
Yes the server is a standalone one, but I have a virtual proxy which is connected to azure and serves as a authentication method.But I will check the proxy log files now.
From the Proxy logs I have only one error, which is repeating it self from time to time.
Error during stream authentication as Server
Authentication failed because the remote party has closed the transport stream.
Have you encountered this error before ?