Skip to main content

Qlik

cancel
Turn on suggestions
Showing results for 
Search instead for 
Did you mean: 
Announcements
Qlik Launches Open Lakehouse and advanced agentic AI experience in Qlik Answers! | LEARN MORE
cancel
Turn on suggestions
Showing results for 
Search instead for 
Did you mean: 
zahidrahim_ocp
Partner - Creator
‎2018-01-17 12:38 AM

QMC is not working after successful installation

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

14,822 Views
0 Likes
18 Replies
zahidrahim_ocp
Partner - Creator
‎2018-01-17 04:55 AM
Author

In response to siddharth_s3

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]

7,433 Views
0 Likes
siddharth_s3
Partner - Creator II
‎2018-01-17 09:14 AM

In response to zahidrahim_ocp

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.

7,433 Views
0 Likes
siddharth_s3
Partner - Creator II
‎2018-01-18 02:12 AM

In response to zahidrahim_ocp

Did you manage to solve it?

7,433 Views
0 Likes
pauljohansson
Creator III
‎2018-08-30 04:18 PM

In response to siddharth_s3

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

br

Paul

7,433 Views
0 Likes
morenoju
Partner - Specialist
‎2018-09-04 11:09 AM

In response to siddharth_s3

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!

7,433 Views
0 Likes
siddharth_s3
Partner - Creator II
‎2018-09-05 10:45 AM

In response to morenoju

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

7,433 Views
0 Likes
morenoju
Partner - Specialist
‎2018-09-05 10:56 AM

In response to siddharth_s3

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.

7,433 Views
tcarolus
Partner - Contributor III
‎2019-02-19 07:04 AM

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-Sep...

 

 

7,256 Views
0 Likes
Top