topic Re: Qlik Management Console Does Not Open in Management & Governance

Qlik Management Console Does Not Open

Wed, 25 Nov 2015 19:20:10 GMT

Hi all,

I am currently going through a Qlik deployment. I cannot open QMC on a server running Windows Server 2012 R2; also, there is no internet access on the server. Currently, the following Qlik services are running: Qlik Sense Engine Service, Qlik Sense Printing Service, Qlik Sense Proxy Service, Qlik Sense Repository Database, Qlik Sense Scheduler Service, and Qlik Sense Service Dispatcher. Does QMC need internet access to open for the first time? If so, what links does it need access to? Is it port related, or something completely different?

Thanks,

Re: Qlik Management Console Does Not Open

JonnyPoole — Wed, 25 Nov 2015 20:54:42 GMT

Once the install is complete there should be a screen that confirms the status of each service. Following that the QMC launches and you should be asked to enter license information.

Are you at that screen ?

A machine that is disconnected from the internet cannot be licensed with a serial/control number only, you need to get the LEF from Qlik to do that.

Please note the licensing is done via the browser and you'll need IE10+ , chrome or firefox to do that as websockets is required (and only exists in those versions).

can you upload a screenshot of where you are ?

Re: Qlik Management Console Does Not Open

Wed, 25 Nov 2015 21:03:06 GMT

I don't have access at the moment and I won't have access to the environment for the next 4-5 days. But, I will post an update as soon I get access again.

Thanks

Re: Qlik Management Console Does Not Open

Thu, 03 Dec 2015 19:50:29 GMT

The issue has been resolved. The part I forgot to mention was that we had Qlik installed on the "wrong" drive. So, we uninstalled it. But some of the Qlik processes/services continued to run. So I forcefully stopped them, then I re-installed qlik on a separate drive. The re-install didn't go smoothly because of the way we uninstalled the application to begin with. We reverted to an earlier VM snapshot and did a clean install - which worked.