Skip to main content
Announcements
Accelerate Your Success: Fuel your data and AI journey with the right services, delivered by our experts. Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
Selvapriya_Thevar
Contributor II
Contributor II

After installing not able to connect the Qlik Sense Hub and QMC

Facing this issue while accessing Qlik sense hub and QMC 

so, kindly assist me.

 Thanks in advance.

 

Selvapriya_Thevar_0-1701336700260.png

 

Labels (1)
  • QMC

1 Solution

Accepted Solutions
Sebastian_Linser

7 1692961d-4eb9-4b24-aad1-1c94a8570cd2 DOMAIN\qvservice Started '' SSL authentication server on port '4244' 1692961d-4eb9-4b24-aad1-1c94a8570cd2
34 20231130T015020.675-0800 INFO QlikServer1 System.Proxy.Proxy.Core.RequestListener 7 f41eeb17-293f-4d1c-b7f6-76c61df88dcb DOMAIN\qvservice Started 'ssl' listener at port '443' f41eeb17-293f-4d1c-b7f6-76c61df88dcb
35 20231130T015020.699-0800 INFO QlikServer1 System.Proxy.Proxy.Core.QPSMain 7 b148f216-5ce6-42b3-b036-71470ed6afbe DOMAIN\qvservice Proxy is running b148f216-5ce6-42b3-b036-71470ed6afbe

that is how it would be logged at service startup. If you dont see that then open a ticket with support. In your case as mentioned you defined a non standard port during installation (according to the screenshot above)

so it will be something like

b7f6-76c61df88dcb DOMAIN\qvservice Started 'ssl' listener at port '4435' f41eeb17-293f-4d1c-b7f6-76c61df88dcb
35 20231130T015020.699-0800 INFO QlikServer1 System.Proxy.Proxy.Core.QPSMain 7 b148f216-5ce6-42b3-b036-

Help users find answers! Don't forget to mark a solution that worked for you! 🙂

View solution in original post

3 Replies
Sebastian_Linser

Hello,

 

can you see if the Repository Service did start up fully?

C:\ProgramData\Qlik\Sense\Log\Repository\Trace\servername_system_repository.txt

If that one shows Startup phase completed move to the proxy logs

C:\ProgramData\Qlik\Sense\Log\proxy\Trace\servername_system_proxy.txt

and check for  Started 'ssl' listener at port '443' / or in your case non standard port 4435

if the repository does not start up fully the proxy cannot get the startup information. If repository did start up but proxy didn't we should see the reason in the proxy log above.

 

best regards

Sebastian

Help users find answers! Don't forget to mark a solution that worked for you! 🙂
Selvapriya_Thevar
Contributor II
Contributor II
Author

I'm not able to find 'ssl' listener at port '443' in this file servername_system_proxy.txt so could you please elaborate what exactly need to check in the above file.

Sebastian_Linser

7 1692961d-4eb9-4b24-aad1-1c94a8570cd2 DOMAIN\qvservice Started '' SSL authentication server on port '4244' 1692961d-4eb9-4b24-aad1-1c94a8570cd2
34 20231130T015020.675-0800 INFO QlikServer1 System.Proxy.Proxy.Core.RequestListener 7 f41eeb17-293f-4d1c-b7f6-76c61df88dcb DOMAIN\qvservice Started 'ssl' listener at port '443' f41eeb17-293f-4d1c-b7f6-76c61df88dcb
35 20231130T015020.699-0800 INFO QlikServer1 System.Proxy.Proxy.Core.QPSMain 7 b148f216-5ce6-42b3-b036-71470ed6afbe DOMAIN\qvservice Proxy is running b148f216-5ce6-42b3-b036-71470ed6afbe

that is how it would be logged at service startup. If you dont see that then open a ticket with support. In your case as mentioned you defined a non standard port during installation (according to the screenshot above)

so it will be something like

b7f6-76c61df88dcb DOMAIN\qvservice Started 'ssl' listener at port '4435' f41eeb17-293f-4d1c-b7f6-76c61df88dcb
35 20231130T015020.699-0800 INFO QlikServer1 System.Proxy.Proxy.Core.QPSMain 7 b148f216-5ce6-42b3-b036-

Help users find answers! Don't forget to mark a solution that worked for you! 🙂