Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
mingsum214
Partner - Contributor III
Partner - Contributor III

Changes for Feb 2020

I just upgrade my QS to Feb 2020 ver and find some other product of Qlik (E.g. insight bot / QDC) seems facing different kind of issue. I am still trouble shooting and checking the issue.

But anyone face the same issue ? are there any important changes on Qlik Sense which may be the reason of those issue

Is it because of the change of nodejs and recreating cert for QlikSense?

 

Labels (4)
2 Replies
rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Goodafternoon @mingsum214,

so far I've only upgraded QS from November 2019 to February 2020 and faced an issue with qliksenserepository user.
The environment has been installed on November 2019, so I expected no issues...
From what I've seen, the problem is related to Qlik Sense Service Dispatcher, but I'm not enough into this to say what is the origin of the issue.

What other issues did you find?

Riccardo

rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Little update: in my case, the issue was related to services mobility-registrar and notifier.
I found the error message (authentication with password failed for user qliksenserepository) on mobility-registrar's log, while the notifier's log was fine.

Since I don't need them in my environment, I disabled them, modifying file services.conf (default location: C:\Program Files\Qlik\Sense\ServiceDispatcher) adding the Disabled=true row below [mobility-registrat] and [notifier].
Be sure to make a backup before modifying the file.

I didn't investifate further about the cause of this issue (maybe a character that now is forbidden on qlikseserepository's password?).

I hope this helps,
Riccardo