QlikSense not working after upgrade from nov2023 patch 9 tot may2024IR

[Jio]

Hello Everyone.

I have a problem. After upgrading our QlikSense Enterprise on Windows (Meows)

QlikSense not working after upgrade from november2023 patch 9 to may2024IR.

Situation: a cluster with one Central and one Rim Node. Operating system Windows 2016 server. 

In the past, we update the application many time successfully. However, no after the upgrade to May2024 IR,. we also did an upgrade to feb 2024 IR. But got the same problem.

QlikSense isn't working anymore after the upgrade on the Central node. There were No errors during the upgrade and all QlikServices are up and running. We shut down the Rim Node and only working on the Central node.

The setup of the upgrade went successfully, but after a restart, the QMC or Hub is not accessible anymore.

All the Qlikservices are up and running but we cannot access the QMC or Hub.

Does anyone have this issue before?

Anyone an idea what could be problem of this upgrade?

[rwunderlich]

I recommend you open a case with the Qlik Support team. 

-Rob

[Jio]

In mine environment i have NPrinting may2023 SR3. Maybe this is an issue.

I will first upgrade Nprinting to may2023 SR5 and than do the upgrade again.

[Jio]

The NPrinting update doesn't resolve this problem.

I thinks the problem has been related tot PostgreSQL (started with QPI).

I will try a complete reinstall on the central node.

[Mike_Dickson]

@Jio 

If all Qlik Services are "running" within services.msc and you are not able to get into the QMC, then you need to look at the Repository Logs: C:\ProgramData\Qlik\Sense\Log\Repository\Trace

If you see more than 6-7 log files there, then that means that the repository services is not fully running/connected.  You will need to look at the log file name "servername_System_Repository.txt" and see what error / warning is being displayed at the bottom.

Based on error/warning, you might be able to find an article to help resolve the issue. If not, then yes it would be suggested to open a case with Support.

Thank you!

[Jio]

Hello Mike_Dickson,

thanks for the response.

Indeed I See a lot of log file (20 - 22) in the folder C:\ProgramData\Qlik\Sense\Log\Repository\Trace.

Het is an overview or the system logfile:

sys_namexx System.Repository.Repository.Core.Licensing.LicensesInitializer 3 28a942fe-5966-419f-a Response: . Could not connect to the license service. NO-STACKTRACE 40661146-1022-
sys_namexx System.Repository.Repository.Core.Licensing.LicensesInitializer 3 078ec98b-49eb-4939-b3

It looks like it cannot connect to the license server. But that is as expected. We are using offline license.

In the file services.conf we also check that the [licenses.parameters] is correct.

[licenses.parameters]
-qsefw-mode
-app-settings="..\Licenses\appsettings.json"
-licenses.parameters
-offline

The Window Eventlog also shows this error:

The description for Event ID 300 from source Qlik Sense Service Dispatcher cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Child process (19560) started
Facility = NL App Search
ExePath = ..\NLAppSearch\nl-app-search.exe
Script =
Command Line"..\NLAppSearch\nl-app-search.exe" --mode=server --port=4953 --log-path="C:\ProgramData\Qlik\Sense\Log" --qrs-port=4242 --capability-service-port=9031 --dps-port=4949 --persistant-storage-enabled=true --update-storage-interval=1h

Any help is welcome.

Kindly regrads,

[Mike_Dickson]

With the error of "There was an error contacting the license service. Keep retrying... (430 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: . Could not connect to the license service", you next need to confirm that the License service is showing as running within Task Manager. This will start up with the Qlik Sense Dispatcher Service.

If it is running, then you need to look at the License log file to see what error is being displayed. This can be found C:\ProgramData\Qlik\Sense\Log\Licenses and you will want to sort the folder by date modified and look at the most recent log after restarting the Dispatcher service.

[Jio · Accepted solution]

The problem that we got, was the result op the QPI installer.

We got the advice of Qlik to do the following:

- make a complete backup of QlikSense and the database

- uninstall qliksense and postgreSQL.

-install the same version of QlikSense that you are using with the Qliksense installer.

This will make use of the integrated PostgreSQL deliverd with QlikSense installer.

- -restore the database

- upgrade Qliksense to the new version. 

We done all above and this solve our problem.

Now lets wait and see what will happend with the next upgrade!!!