topic Re: QMC is not working after successful installation in Management & Governance

QMC is not working after successful installation

zahidrahim_ocp — Wed, 17 Jan 2018 05:38:41 GMT

Dear Experts,

We have successfully installed and using Qlik Test Server. Now on a separate machine we have installed QLIK Production Server after complete successful installation QMC page is not appearing neither on Production Machine itself nor from clients.

Clients are seeing error message:

This site can’t be reached

On Server using the URL: https://qlik/qmc/

This page can’t be displayed

After clicking Fix Connection Problems, We saw error:

The remote device or resource won't accept the connection Detected

We have tried both url: https://qlik/qmc/ https://localhost/qmc/

Best Regards,

Zahid Rahim

Re: QMC is not working after successful installation

shraddha_g — Wed, 17 Jan 2018 07:05:53 GMT

did you check QlikSense Services? all the services are running?

also check any error in Logs

Re: QMC is not working after successful installation

zahidrahim_ocp — Wed, 17 Jan 2018 07:32:25 GMT

Yes, All services are running perfectly even after restart.

Further can you please guide me to the log location as i could not find any logs.

Re: QMC is not working after successful installation

shraddha_g — Wed, 17 Jan 2018 08:03:44 GMT

Logs at ProgramData/Qlik/Sense/Logs

Re: QMC is not working after successful installation

zahidrahim_ocp — Wed, 17 Jan 2018 08:35:19 GMT

Below are the few last lines from proxy\logs

360 20180117T132605.297+0500 ERROR QLIK System.Proxy.Proxy.Communication.Rest.ProxyRestClient 12 b7cb33da-4421-4b77-8b6c-59deb0995403 QLIK\Qservice When contacting https://localhost:4242/ No connection could be made because the target machine actively refused it 127.0.0.1:4242↵↓Unable to connect to the remote server at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)↵↓ at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)↵↓ at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)↵↓ at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)↵↓ at Qlik.Sense.Common.Communication.REST.Client.WebClientEx.GetWebResponse(WebRequest request, IAsyncResult result)↵↓ at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result) b7cb33da-4421-4b77-8b6c-59deb0995403

361 20180117T132605.297+0500 WARN QLIK System.Proxy.Proxy.Settings.SettingsHandler 9 5df44c80-912f-4942-8e73-bfd318df5596 QLIK\Qservice Could not contact local repository to retrieve proxy service settings No connection could be made because the target machine actively refused it 127.0.0.1:4242↵↓Unable to connect to the remote server at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)↵↓ at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)↵↓ at Proxy.Communication.Rest.ProxyRestClient.CallSync[TR](String restCommand, RESTMethod method, Object jsonObject, IDictionary`2 additionalHeaders)↵↓ at Proxy.Communication.Rest.QrsRestClient.GetLocalProxyService()↵↓ at Proxy.Settings.SettingsHandler.TryRetrieveSettingsFor(Func`1 call, String resourceName) 5df44c80-912f-4942-8e73-bfd318df5596

362 20180117T132612.333+0500 ERROR QLIK System.Proxy.Proxy.Communication.Rest.ProxyRestClient 16 d9b06b4f-39ed-4cab-8ece-4d2df430e6eb QLIK\Qservice When contacting https://localhost:4242/ No connection could be made because the target machine actively refused it 127.0.0.1:4242↵↓Unable to connect to the remote server at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)↵↓ at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)↵↓ at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)↵↓ at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)↵↓ at Qlik.Sense.Common.Communication.REST.Client.WebClientEx.GetWebResponse(WebRequest request, IAsyncResult result)↵↓ at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result) d9b06b4f-39ed-4cab-8ece-4d2df430e6eb

363 20180117T132612.333+0500 WARN QLIK System.Proxy.Proxy.Settings.SettingsHandler 7 ccff8bf2-68d0-4565-8be1-ffd5783d8520 QLIK\Qservice Could not contact local repository to retrieve local server node configuration No connection could be made because the target machine actively refused it 127.0.0.1:4242↵↓Unable to connect to the remote server at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)↵↓ at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)↵↓ at Proxy.Communication.Rest.ProxyRestClient.CallSync(String restCommand, RESTMethod method, Object jsonObject, IDictionary`2 additionalHeaders)↵↓ at Proxy.Communication.Rest.QrsRestClient.GetLocalServerNodeConfiguration()↵↓ at Proxy.Settings.SettingsHandler.TryRetrieveSettingsFor(Func`1 call, String resourceName) ccff8bf2-68d0-4565-8be1-ffd5783d8520

Re: QMC is not working after successful installation

siddharth_s3 — Wed, 17 Jan 2018 08:44:49 GMT

Is it only QMC? Can you open the hub?

Re: QMC is not working after successful installation

zahidrahim_ocp — Wed, 17 Jan 2018 08:54:24 GMT

BOTH, HUB also giving same issue.

Re: QMC is not working after successful installation

siddharth_s3 — Wed, 17 Jan 2018 09:05:59 GMT

Did it ever work?

Did you make any changes to the proxy settings?

If you are using a proxy, make sure the "bypass proxy server for local address" option is checked.

It might be that the QPS is trying to use the regular way and your internet works differently.

Re: QMC is not working after successful installation

zahidrahim_ocp — Wed, 17 Jan 2018 09:10:02 GMT

No it never worked after the installation.

I have disabled the proxy server and also matched the setting with my other running server.

Re: QMC is not working after successful installation

siddharth_s3 — Wed, 17 Jan 2018 09:24:42 GMT

Did you change the proxy settings now? If so, try restarting the Qlik services.

Otherwise, do you have IIS or skype installed on the server?

Try this in CMD: This will check which service is running on which port.

C:/> netstat -anob >%USERPROFILE%\ports.txt

C:/> start %USERPROFILE%\ports.txt

The above 2 commands will open a .txt file.

Check which "PID" is listening to port 443. Then open task manager and go to "Details" sections. Find the PID which is listening on port 443.

If it is anything other than QlikSense proxy service, there is your problem.

Re: QMC is not working after successful installation

zahidrahim_ocp — Wed, 17 Jan 2018 09:55:03 GMT

Dear Siddharth,

Proxy Settings are: Automatically Detect setting is checked, rest everything is unchecked and i have tried restarting server.

Further first command is not giving anything the second command generated pots.txt file.

Active Connections

Proto Local Address Foreign Address State PID

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 704

RpcSs

[svchost.exe]

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4

Can not obtain ownership information

TCP 0.0.0.0:3003 0.0.0.0:0 LISTENING 2256

[node.exe]

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1780

TermService

[svchost.exe]

TCP 0.0.0.0:4900 0.0.0.0:0 LISTENING 3240

[node.exe]

TCP 0.0.0.0:9028 0.0.0.0:0 LISTENING 2516

[node.exe]

TCP 0.0.0.0:9031 0.0.0.0:0 LISTENING 2888

[node.exe]

TCP 0.0.0.0:9032 0.0.0.0:0 LISTENING 1736

[node.exe]

TCP 0.0.0.0:9098 0.0.0.0:0 LISTENING 2212

[node.exe]

TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4

Can not obtain ownership information

TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 408

[wininit.exe]

TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 784

eventlog

[svchost.exe]

TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 848

Schedule

[svchost.exe]

TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 512

[services.exe]

TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 1824

PolicyAgent

[svchost.exe]

TCP 0.0.0.0:49159 0.0.0.0:0 LISTENING 520

[lsass.exe]

TCP 127.0.0.1:4432 0.0.0.0:0 LISTENING 436

[postgres.exe]

TCP 127.0.0.1:49599 127.0.0.1:4444 SYN_SENT 5104

[Engine.exe]

TCP 172.16.1.46:139 0.0.0.0:0 LISTENING 4

Can not obtain ownership information

TCP 172.16.1.46:3389 172.16.1.35:53465 ESTABLISHED 1780

TermService

[svchost.exe]

TCP 172.16.1.46:49598 172.16.1.46:4242 SYN_SENT 596

[node.exe]

TCP 192.168.1.109:139 0.0.0.0:0 LISTENING 4

Can not obtain ownership information

TCP 192.168.1.109:49161 216.58.205.138:443 TIME_WAIT 0

TCP 192.168.1.109:49162 216.58.205.131:443 TIME_WAIT 0

TCP 192.168.1.109:49164 216.58.205.131:443 TIME_WAIT 0

TCP 192.168.1.109:49330 216.58.205.131:443 ESTABLISHED 2588

[chrome.exe]

TCP 192.168.1.109:49331 216.58.205.138:443 ESTABLISHED 2588

[chrome.exe]

TCP 192.168.1.109:49368 216.58.205.131:443 ESTABLISHED 2588

[chrome.exe]

TCP [::]:135 [::]:0 LISTENING 704

RpcSs

[svchost.exe]

TCP [::]:445 [::]:0 LISTENING 4

Can not obtain ownership information

TCP [::]:3003 [::]:0 LISTENING 2256

[node.exe]

TCP [::]:3389 [::]:0 LISTENING 1780

TermService

[svchost.exe]

TCP [::]:4900 [::]:0 LISTENING 3240

[node.exe]

TCP [::]:9028 [::]:0 LISTENING 2516

[node.exe]

TCP [::]:9031 [::]:0 LISTENING 2888

[node.exe]

TCP [::]:9032 [::]:0 LISTENING 1736

[node.exe]

TCP [::]:9098 [::]:0 LISTENING 2212

[node.exe]

TCP [::]:47001 [::]:0 LISTENING 4

Can not obtain ownership information

TCP [::]:49152 [::]:0 LISTENING 408

[wininit.exe]

TCP [::]:49153 [::]:0 LISTENING 784

eventlog

[svchost.exe]

TCP [::]:49154 [::]:0 LISTENING 848

Schedule

[svchost.exe]

TCP [::]:49155 [::]:0 LISTENING 512

[services.exe]

TCP [::]:49156 [::]:0 LISTENING 1824

PolicyAgent

[svchost.exe]

TCP [::]:49159 [::]:0 LISTENING 520

[lsass.exe]

TCP [::1]:4432 [::]:0 LISTENING 436

[postgres.exe]

TCP [::1]:4432 [::1]:49172 ESTABLISHED 436

[postgres.exe]

TCP [::1]:4432 [::1]:49251 ESTABLISHED 436

[postgres.exe]

TCP [::1]:4432 [::1]:49253 ESTABLISHED 436

[postgres.exe]

TCP [::1]:4432 [::1]:49254 ESTABLISHED 436

[postgres.exe]

TCP [::1]:4432 [::1]:49255 ESTABLISHED 436

[postgres.exe]

TCP [::1]:4432 [::1]:49256 ESTABLISHED 436

[postgres.exe]

TCP [::1]:49172 [::1]:4432 ESTABLISHED 500

[Repository.exe]

TCP [::1]:49251 [::1]:4432 ESTABLISHED 500

[Repository.exe]

TCP [::1]:49253 [::1]:4432 ESTABLISHED 500

[Repository.exe]

TCP [::1]:49254 [::1]:4432 ESTABLISHED 500

[Repository.exe]

TCP [::1]:49255 [::1]:4432 ESTABLISHED 500

[Repository.exe]

TCP [::1]:49256 [::1]:4432 ESTABLISHED 500

[Repository.exe]

TCP [fe80::2053:65b0:ee70:e70a%12]:49596 [fe80::2053:65b0:ee70:e70a%12]:4242 SYN_SENT 4424

[Printing.exe]

UDP 0.0.0.0:500 *:* 848

IKEEXT

[svchost.exe]

UDP 0.0.0.0:4500 *:* 848

IKEEXT

[svchost.exe]

UDP 0.0.0.0:5353 *:* 2588

[chrome.exe]

UDP 0.0.0.0:5353 *:* 2588

[chrome.exe]

UDP 0.0.0.0:5353 *:* 2588

[chrome.exe]

UDP 0.0.0.0:5353 *:* 2588

[chrome.exe]

UDP 0.0.0.0:5355 *:* 988

Dnscache

[svchost.exe]

UDP 172.16.1.46:137 *:* 4

Can not obtain ownership information

UDP 172.16.1.46:138 *:* 4

Can not obtain ownership information

UDP 192.168.1.109:137 *:* 4

Can not obtain ownership information

UDP 192.168.1.109:138 *:* 4

Can not obtain ownership information

UDP [::]:500 *:* 848

IKEEXT

[svchost.exe]

UDP [::]:4500 *:* 848

IKEEXT

[svchost.exe]

UDP [::]:5353 *:* 2588

[chrome.exe]

UDP [::]:5353 *:* 2588

[chrome.exe]

UDP [::]:5355 *:* 988

Dnscache

[svchost.exe]

UDP [::1]:52783 *:* 436

[postgres.exe]

Re: QMC is not working after successful installation

siddharth_s3 — Wed, 17 Jan 2018 14:14:03 GMT

The first command generates the result and stores it in the file.

The second command opens the saved file.

Anyways, looking at the netstat output, the proxy is not listening at port 443, which is why you are getting the error.

What is more weird is that there is noting running on port 443.

Try the following and let me know what you see

Run (win+r) --> mmc --> File --> Add or remove snap in --> Choose certificates --> Add --> Computer account --> Finish and okay
Now go to certificates --> Personal --> Certificates .
Here let me know if you see a certificated issued by <{YourMachineName}>

If there are no certificates, it means that your proxy service is not even trying to start.

Re: QMC is not working after successful installation

awhitfield — Wed, 17 Jan 2018 16:03:57 GMT

Have you worked through this?

https://help.qlik.com/en-US/sense/November2017/Content/Deploying.htm

and

https://help.qlik.com/en-US/sense/November2017/Subsystems/ManagementConsole/Content/troubleshooting-starting-QMC.htm

Andy

Re: QMC is not working after successful installation

siddharth_s3 — Thu, 18 Jan 2018 07:12:30 GMT

Did you manage to solve it?

Re: QMC is not working after successful installation

pauljohansson — Thu, 30 Aug 2018 20:18:10 GMT

any progress on this? I have the exact same issue,

Paul

Re: QMC is not working after successful installation

morenoju — Tue, 04 Sep 2018 15:09:18 GMT

Siddharth, I'm having the same issue as Zahid after installing Qlik Sense 3.2 SR5 in a Windows 7 machine.

I went to Personal/Certificates, and there is one issues to qlik (name of my machine) by qlik-CA.

Nobody is listening to port 443 though.

Any idea of what I can do about this? Thanks!

Re: QMC is not working after successful installation

siddharth_s3 — Wed, 05 Sep 2018 14:45:58 GMT

You can try staring your proxy service in bootstrap mode.

Let me know if you still need help since I am late to the party

Re: QMC is not working after successful installation

morenoju — Wed, 05 Sep 2018 14:56:34 GMT

Thank you Siddharth. I decided to start all over again but in a clean server. The server I was using had a Qlikview installed and maybe its uninstall didn't go as well as it should.

Re: QMC is not working after successful installation

tcarolus — Tue, 19 Feb 2019 12:05:24 GMT

Hi All,

This post has been active for a few months with no specific solution. I just encountered the same problem when upgrading from Sep2017 version to Feb2019.

I was looking around in the community and found this post with the solution for this issue. It just made my, and my customers day. So here is the URL and see the post marked as the solution.

https://community.qlik.com/t5/Qlik-Sense-Deployment-Management/Troubles-after-upgrade-QLIK-Sense-September-2017-release-to/m-p/1546299#M12632