Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
Need your help to understand and solve the error message I am getting in June 2018 version.
Before I was using September 2017 version of Qlik Sense Desktop and then also when I was opening data manager it shows 'The connector is not responding. Contact your system administrator.'
I again upgraded the version to June 2018 but still getting the same error message.
Because of this issue I am not able to create any data connection. OLE DB providers are also not getting loaded.
I found the below post related to this issue but it did not work for me.
FAILED TO LOAD CONNECTION ISSUE AT QS HUB | Qlik Community
Any help and suggestion is highly appreciated.
Regards,
Ipsita
I also get the same error did you find a workaround?
I had the exact same problem. Had a 1 hour call with Qlik Support.
It turns out my McAfee Virus Protection was blocking the Connector exe's in the folder C:\Users\<Name>\AppData\Local\Programs\Common Files\Qlik\Custom Data.
Sense June 2018 works fine now.
Hi Bharat,
Unfortunately I am still getting the same error. I have no clue why I am not getting this error in my laptop where i freshly installed Qlik sense for first time. However, this connector issue still persist in my desktop where I upgraded the version. Even on getting this error I uninstalled and reinstall QS. At final error still persist.
@ Hi Qlik Team. please guide.
Thanks,
Ipsita
All you need to do is reinstall (or repair/upgrade) Qlik Sense with Administrator permissions.
This is the only thing that helps me.
Thanks Vasiliy for your reply.
I tried twice the tradition of reinstall/uninstall/upgrade but its still an issue.
Regards,
Ipsita
May be, do the configuration mentioned like in below link:
May be, because of the Antivirus setup, it's blocking the connectors.
The root cause - issues with connectors are in this case caused by McAfee - ADAPTIVE THREAT PROTECTION. When turned off the connectors and ODBC work.
This could be McAfee issue or threat policy set by company's security.
The same thing happened to me, I had to turn off McAfee real-time scanning