topic Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February in Management & Governance

QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February 2019

piotr-bratek — Sat, 16 Nov 2024 06:10:18 GMT

Hi All,

I smoothly installed QS Server on my laptop. For some reason neither QMC, nor Hub open up. I decided to write an article with detailed procedure of troubleshooting. Yet, I need your input 🙂 Despite the fact there is sth like that in Help, the article is quite selective.

Environment:

# Laptop with Win10 Pro
# Qlik Sense Enterprise February 2019 installad on ...
# Hyper-V with Win Server 2016 Essentials

Before the installation started I had been informed by QS installer that ports 80 & 443 are use by other services. So I:

1. uninstalled IIS first - a short video how to on YT:

2. stopped Firewall

3. stopped HTTP (HTTP.SYS) Hidden Driver/Service - more here

It worked. Installation went smoothly. To start services, I used a new account created during Win Server configuration - Admin (not Administrator - the default account, you can't use it anyway). This account is by default created in local domain.

After the installation was completed and system restarted, I finally tried to open (hit the desktop shortcut) the QMC first and Hub then. Didn't work.

Troubleshooting procedure: ------------------------------------------------------------------------------------------

1. Check if QS services are up

Yes, they are. Local System user for QSRDB? I found it's fine.

2. Check if Admin belongs to Administrators group

Initially, this user belonged to Administrators group. Once QS has been installed he's re-assigned to Qlik Sense Service Users

3. Check if Proxy is set up

No, it's not.

4. Specific settings - as e.g. need to use LOCALHOST instead of <server name> in Win Server 2016 described here

5. OK, what the heck... let's check LOGs (attached as log file as well)

It seems there is sth wrong with QRS - I can see errors in couple of LOG files. Yet, in Services window (presented above), it shows it's working. Certificates seem to be fine looking at the screenshot below.

one more:

and one more comment:

qlik No connection could be made because the target machine actively refused it

I was so excited I'll finally find some nasty service blocking my 4242 but my finding was very disappointing

What's next ? I'm not good at things listed below (above as well 😉 ) so maybe you'll give me some useful hints so I finally can fire up my server and update this article.

# Sth more regarding Certificates? Security? Firewall?
# What's the issue with QRS
# Firewall
# Issues with QS version \ VM \ System
# Anything else ?

One more hint. I change DNS to 8.8.8.8 to make my VM-internet working, but I don't thing it has an impact as I also turned back to default settings.

Any Savior? I'm pretty close to commit a suicide by smashing my head against my old desktop computer with 386 processor..

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

Giuseppe_Novello — Wed, 03 Apr 2019 13:43:23 GMT

Go to Sense/logs/repo/trace/repo_system logs, check the last line, what does it say? The other logs, basically is saying I am waiting for repo to start, that log I pointed out will tell you where it is standing in the start process of the service.

Gio

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & ...

Anonymous — Wed, 03 Apr 2019 14:03:24 GMT

Excellent write up of your issue! Hopefully someone will have a good recommendation for you soon.

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

piotr-bratek — Wed, 03 Apr 2019 19:26:32 GMT

Hi,

thanks for reply. My logs attached.

cheers

Piotr

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

Giuseppe_Novello — Wed, 03 Apr 2019 19:30:06 GMT

Nope, again, I requested the logs\repo\TRACE\sytem_repository.log. The one attached are from \Log\Repository\System, which that one won't tell me anything.

Gio

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

Giuseppe_Novello — Wed, 03 Apr 2019 19:32:11 GMT

Anyways, try the following article:

https://support.qlik.com/articles/000040002

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

piotr-bratek — Wed, 03 Apr 2019 19:39:32 GMT

Sure thing... here it is. Not sure if the first one from 09:35 is relevant but I attached it as well just in case...

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

Giuseppe_Novello — Wed, 03 Apr 2019 19:41:48 GMT

Thanks! Okay like I thought it was, try the following article:

https://support.qlik.com/articles/000040002

Gio

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

piotr-bratek — Thu, 04 Apr 2019 06:47:29 GMT

OK, it seems no difference. Just in case I did it on two separate installations:

# First, as before QS February 2019 on Win Server 2016 Essentials
# Then, QS November 2018 on Win Server 2019 Essentials

The issue still occurs. See logs attached and screenshots from the registry key.

The other QS and WIN version - no Reg Keys at all (1). Shall I also remove (2)? Anyway, it's not allowed (3).

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

Giuseppe_Novello — Thu, 04 Apr 2019 12:17:29 GMT

I am assuming that after this change you rebooted the machine for the registry to take effect.

Then if you have a Qlik support maintenance agreement, then I would open a support ticket for further assistance.

GIo

Re: QMC \ Hub does do not open - troubleshooting step-by-step procedure - Hyper-V & QS February

piotr-bratek — Tue, 09 Apr 2019 06:05:31 GMT

Hio Gio, maintanace only 😞 Let me know if you get to know sth new. I'm still wondering if you I got correct information that the WS Essentials version is fine. Yet, I can remember I was using it in the past and it worked...