Skip to main content
Announcements
Global Transformation Awards submissions are open! SUBMIT YOUR STORY
cancel
Showing results for 
Search instead for 
Did you mean: 
Saif1
Partner - Creator

Getting Error when accessing Qlik sense HUB

I never had this happen to me before, everything was going fine until i last checked my Qlik sense HUB, 

I have Qlik sense enterprise on my device and getting this error when accessing the HUB : 

Error requesting "/license/' - Error : Connect ECONNREFUSED ******:****:***::*::**4242

Any solution for this ? 

Last thing i have done on my device is i installed Microsoft Powerautomate desktop  , is this relatable to the issue ?

Chrome updated
Services working

Thanks 

Labels (1)
2 Solutions

Accepted Solutions
Saif1
Partner - Creator
Author

Hello RaviSingh 

I have tried everything, nothing worked on may 2023 version.

The solution was to downgrade so i used the August 2022 version and it worked!!!!!

Try it and report back on this thread if it works for you.

Kind regards

View solution in original post

Proginov
Partner - Contributor II

Bonjour,

J'ai des nouvelles!

Il s'agit d'un souci de communication du service Licence qui n'a pas l'air d'apprécier l'IP v6.

En ajoutant une clé de registre, on peut désactiver l'utilisation de l'IP v6, et permettre au QLS de répondre au QRS, et donc d'ouvrir le Hub, ce qui débloque la situation pour MAY/AUG/NOV2023.

Par contre, dans le cas d'une restauration d'un serveur FEV2023 et en dessous avec changement de nom serveur, ne pas créer cette clé, car le process de restauration bloquera sur le Reporistory.exe en mode "-standalone -bootstrap -restorehostname"

Autre point qui était bloquant chez moi: mon serveur 2K16 QSFEV2023 a été traité avec QPI 1.2 a un moment donné, et cela semble poser problême lors de l'upgrade, avec l'installer qui cherche (et réussi) à installer le service QSRD alors que PostgreSQL est DEJA installé en stand-alone. L'upgrade ne se termine du coup jamais.

La bonne solution de mon côté a été d'installer un nouveau serveur 2019 avec un nouveau nom, utiliser IISCrypto, d'installer QS FEV2023, d'utiliser QPI 1.3, de restaurer mon environnement en suivant les documentations Qlik (Certificats, Bases de données, Shared Repository, exécution de Repository.exe en mode bootstrap/restorhostname), de migrer en NOV2023, de désactiver l'IP v6 via la clé de registre, puis de rebooter.

Et là, tout fonctionne 🙂

La clé de registre a créer:

HKLM\SYSTEM\CurrentControlSet\Services\Tcipip\Parameters -> DisabledComponents (REG_DWORD) 0x0000020 (32)

RegistryKey for QS MAY2023 and Up.png

En espérant que tout ceci puisse aider d'autres personnes qui rencontre ce problème lors d'upgrade ou de restauration.

Cordialement,

Julien

View solution in original post

20 Replies
Chip_Matejowsky
Support

Hi @Saif1,

This error is typically returned due to internet access issues such as a blocked port or disabled cipher suites. Have a look at Qlik KB article Qlik Sense hub fails to connect with: Error requesting "https://SERVERNAME:4242/qrs/license/" Error ...

Best Regards

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
Saif1
Partner - Creator
Author

Hello Chip, 

I have followed the article instructions , i have checked the ports ( i gave full ports access inbound and outbound) for Qlik sense , and i have applied the "Best practices" for the cipher suites through the 3rd party app that was recommended. and it did not help (Same issue) 

Any other help ? 

Thanks

Albert_Candelario

Hello  @Saif1,

Is the port 4242 listening and opened as needed.

What about the PostgreSQL, is listening on that IP addressed?

Do you see further errors on the License logs, if yes, please do share those here.

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer
Saif1
Partner - Creator
Author

Hello Albert,

Here are the licesnse logs : 

{"caller":"qrs_client.go:31","error":"Get \"https://localhost:4242/qrs/servernodeconfiguration/local?xrfkey=InHocSignoVinces\": dial tcp [::1]:4242: connectex: No connection could be made because the target machine actively refused it.","level":"error","logTraceId":"4314117e82f1bdc45f81095892419cc1","message":"failed retrieve central node info from QRS (communication error)","timestamp":"2023-07-22T14:54:45.0338903Z"}
{"caller":"qrs_client.go:31","error":"Get \"https://localhost:4242/qrs/servernodeconfiguration/local?xrfkey=InHocSignoVinces\": dial tcp [::1]:4242: connectex: No connection could be made because the target machine actively refused it.","level":"error","logTraceId":"f01d46cccef3d461a56029100522ac8d","message":"failed retrieve central node info from QRS (communication error)","timestamp":"2023-07-22T14:54:57.4095388Z"}
{"caller":"qrs_client.go:31","error":"Get \"https://localhost:4242/qrs/servernodeconfiguration/local?xrfkey=InHocSignoVinces\": dial tcp [::1]:4242: connectex: No connection could be made because the target machine actively refused it.","level":"error","logTraceId":"8972327ed9ce9f193bcf3e4259b82430","message":"failed retrieve central node info from QRS (communication error)","timestamp":"2023-07-22T14:55:09.7613935Z"}
{"audience":"","caller":"middleware.go:101","level":"info","license":"0009550133082615","logTraceId":"fca0260d33fa7a387d3698a3a1679130","message":"http request","name":"V1LicensesOverviewGet","req.method":"GET","req.url":"/v1/licenses/overview?xrfkey=ichbineinberlinR","res.statusCode":"200","subType":"","tenant":"","timestamp":"2023-07-22T14:55:19.7998577Z","userAgent":""}
{"caller":"qrs_client.go:42","level":"error","logTraceId":"eb3667f912f2028ff4c8fae1c75fe685","message":"failed retrieve central node info from QRS. http status code","statusCode":503,"timestamp":"2023-07-22T14:55:21.1090014Z"}

And the Whole file is attached

And here are the CMD screenshots from checking the port :

Saif1_0-1690038357502.png


Can you please check them , it is urgent I need the Qlik sense hub to work before monday.

Thank you so much

 

RaviSingh
Partner - Contributor II

@Saif1 

I am facing the same issue after new installation of QlikSense. Have you got any solution ? If you have resolved the issue kindly share it.

Saif1
Partner - Creator
Author

Hello RaviSingh 

I have tried everything, nothing worked on may 2023 version.

The solution was to downgrade so i used the August 2022 version and it worked!!!!!

Try it and report back on this thread if it works for you.

Kind regards

Albert_Candelario

Hello @Saif1,

Did do check the TLS/SSL set up? do you have a sandbox where the issue could have been reproduced? 

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer
Saif1
Partner - Creator
Author

I have checked everything , i even opened a support ticket with Qlik support and went through all solutions, we landed on that my environment had mashup ports and need to use a new environment , so what i did is that use a new local user and try different solutions, nothing worked even on the new local user, TLS/SSL setup i tried many times and with the conseltation of the Qlik support. 

The only method worked is i downloaded the Aug 2022 version of Qlik sense and it worked both on my account and the local user account.

Saif1
Partner - Creator
Author

@Albert_Candelario  Hello albert, hope you are doing well, 

What i really want to know is that i tried to update to may 2023 again ( i need the background features and the filter new features) 
and it did not work , it gave the same error, i thought it is a version issue so i decided to try the beta of the August 2023 , it gave the same issue. but the august 2022 works , did anything changed in the 2023 versions ?

How can i solve this issue without formatting my server or change anything in my environment since 2022 version is working ??

Thanks for your help