Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

"Connector is not responding" - contact the system administrator

Good morning

In recent days I installed the latest version of QS.

On all the old apps, and when I create new ones I always have the error:

An error occurred

"Connector is not responding" - contact the system administrator

please help

29 Replies
agigliotti
Partner - Champion
Partner - Champion

Great!

Anonymous
Not applicable
Author

Not great ! because on the main pc there is always the problem with the connector error !!!!!!!!

the other pc is only a second pc more limited

agigliotti
Partner - Champion
Partner - Champion

i'd not know how to help you further.

Anonymous
Not applicable
Author

In this topic:

Connector is not responding in Qlik sense desktop with MySQL ODBC driver

I have seen that there were the same problem, due to Mcafee, and I have Mcafee installed,

can this be the problem? But Mcafee I've already installed for a long time....

agigliotti
Partner - Champion
Partner - Champion

let's try to disable it for a while and check.

Anonymous
Not applicable
Author

YESSSSSSSSSSSSSSSSSSSSSS  !!!!!!!!!!!!!!!!!!!!!!


end of the NIGHTMARE, is the real-time scan of Mcafee that generates all these problems with Qlik Sense, slowness, connector error.

For other reasons I already found Mcafee too invasive, still a few days and expires the license, then I uninstall it and replace it with another antivirus

Anonymous
Not applicable
Author

Please, Can some Qlik Sense technician warn Mcafee that the antivirus creates all these problems with QS??


This is not the first topic on this problem, it is not possible to lose three days on a problem of this type.

Anonymous
Not applicable
Author

a really dirty solution ... in my opinion

Anonymous
Not applicable
Author

I always have problems with Mcafee, which does not allow to exclude entire paths from the antivirus, but only one file at a time.

I can only work by excluding, the antivirus (!!!!)

I hope that Qlik will quickly remedy this situation in the next release of QS