We are currently having an issue at the moment with regards to packaging a version of the QlikView desktop client where we have the QlikView access point appear when the application starts up for end users.
We had an issue that when a user first open up the new QlikView Desktop Client application a Windows Security Warning ActiveX prompt appears. The user has to click the Yes button on the warning prompt before the access point is loaded.
We found out that doing the following resolves this issue.
As this will be rolled out to all business end user users, the above cannot be done due to our company IT security policy so to overcome this, we have looked into creating a registry entry that will do the above to listed sites when the application is installed. (Qlik Access Point). Unfortunately, we cannot seem to get this working. I know that we may need the CLSID for ActiveX component of the QlikView desktop client.
Link to description of the above solution:
Any help on this would greatly appreciated.
Any particular reason why you want to distribute QV Desktop to end-users as an AccessPoint client (assuming that they are not developers for which the QV Desktop is actually intended) and not the IE-plugin or the AJAX client which are much lighter?
Thanks very much for getting back to me. The reason we use the desktop client is that we found it to be far more stable than AJAX or the IE plugin with our application, also business users are used to accessing QlikView using the desktop client. Is there anything we can do to stop the above prompt happening?
I think you will need to die one death - either in adjusting the windows security settings or to live with these messages or to use a browser with the ajax-client.
What are the instable issues which you experienced with the browsers and with which releases did this happens?
Just to give closure to this is that we decided to go ahead with the release. Our IT Security team said the issue would be resolved if Qlik registered their ActiveX scripts with Microsoft.
Thanks again for responding to this thread.