I am trying to install Qlick Sense 3.1 on the machine (Windows Server 2012). Even though all the services are running, the Qlik Management Console fails to load. I have been looking at the logs and it seems that there is some sort of a communication error.
I would like to mention that the machine I am trying to install Qlik Sense on is an IPV6 machine. We have Qlik running on IPV4 boxes, not on IPV6.
Here is a snippet of the logs for SYSTEM_Repository log file under Log/Repository/Trace
273 20171205T070425.733-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 102 b4b0056c-5b6a-4570-90a4-7719029535f1 CAROCNXEBIPA1V\QVAdmin No reply from migration service. Migration service may not be up running (yet) on this host, or there is no migration service associated with this host b4b0056c-5b6a-4570-90a4-7719029535f1
274 20171205T070425.733-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 103 3d7b15f2-83bb-44c2-acb9-de07a5208299 CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://url:5151/qss/' (Unable to connect to the remote server) 3d7b15f2-83bb-44c2-acb9-de07a5208299
275 20171205T070440.726-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 102 92bade70-3f8f-4acb-8f79-c094e0e5029a CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://url:4243/qps/' (Unable to connect to the remote server) 92bade70-3f8f-4acb-8f79-c094e0e5029a
276 20171205T070440.742-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 103 6f6ae227-7e6f-4bd5-84b6-820d6b50f7aa CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://url:5151/qss/' (Unable to connect to the remote server) 6f6ae227-7e6f-4bd5-84b6-820d6b50f7aa
277 20171205T070440.742-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 102 01e0b8dd-a9fc-4983-af99-e15af13ba16c CAROCNXEBIPA1V\QVAdmin No reply from migration service. Migration service may not be up running (yet) on this host, or there is no migration service associated with this host 01e0b8dd-a9fc-4983-af99-e15af13ba16c
278 20171205T070455.730-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 103 dc936e41-7fe3-4287-89b3-2188d80a65b5 CAROCNXEBIPA1V\QVAdmin No reply from migration service. Migration service may not be up running (yet) on this host, or there is no migration service associated with this host dc936e41-7fe3-4287-89b3-2188d80a65b5
279 20171205T070455.730-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 102 584fbccb-71da-41d8-9d0c-0040f42d9e60 CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://carocnxebipa1v.nss.vzwnet.com:4243/qps/' (Unable to connect to the remote server) 584fbccb-71da-41d8-9d0c-0040f42d9e60
280 20171205T070455.730-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 103 41788e35-e58d-4a2f-bee6-6027c3602b4f CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://url:5151/qss/' (Unable to connect to the remote server) 41788e35-e58d-4a2f-bee6-6027c3602b4f
281 20171205T070510.746-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 102 51fd2ebf-7a73-4600-8262-fc7e8487cf1f CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://url:5151/qss/' (Unable to connect to the remote server) 51fd2ebf-7a73-4600-8262-fc7e8487cf1f
282 20171205T070510.746-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 103 796f645d-29dc-4d6b-bba0-d3e882651855 CAROCNXEBIPA1V\QVAdmin No reply from migration service. Migration service may not be up running (yet) on this host, or there is no migration service associated with this host 796f645d-29dc-4d6b-bba0-d3e882651855
283 20171205T070510.762-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 103 3e64c0f3-9168-4aca-95bb-4a33b564f5b3 CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://url:4243/qps/' (Unable to connect to the remote server) 3e64c0f3-9168-4aca-95bb-4a33b564f5b3
284 20171205T070524.737-0800 INFO carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 102 1ad35866-f99f-4ad4-9db3-750e0d6c56c3 CAROCNXEBIPA1V\QVAdmin Reply from migration service (migration service is up) 1ad35866-f99f-4ad4-9db3-750e0d6c56c3
285 20171205T070525.753-0800 WARN carocnxebipa1v System.Repository.Repository.Core.Status.ServiceStatusWorker 103 687050f5-0b74-4b77-abac-42a29f7d49a3 CAROCNXEBIPA1V\QVAdmin Failed to request service alive response from 'https://url:5151/qss/' (Unable to connect to the remote server) 687050f5-0b74-4b77-abac-42a29f7d49a3
Ok, try creating a new inbound rule and specify the two ports, outbound ports are normally open by default. check that sql server isn't running on the server, i have experienced this at a few clients where sql somehow locks the ports used by sense. As a quick test you could temporarily disable the firewall on the server, restart and test as well to confirm if its not the firewall blocking comms.
