Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
agigliotti
Partner - Champion
Partner - Champion

Issues after upgrading qlik sense to version 3.0

Hello,

I'm facing problems after upgrading customer's qlik sense multi-node site from version 2.2.4 to version 3.0.

I upgraded successfully both the central node first and the rim node after.

It ended with no errors in both server.

Now either the QMC and Hub doesn't works anymore in both nodes.

Before upgrading the central node I made a backup of repository using repositorySnapshotManager (RSM) utility.

Calling the hub I get the following error message:

"An error occurred. The load balancing module did not return any engine service for the following app: __hub"

Someone can help me ???

However I submitted a new case to the support portal.

Many thanks in advance.

Best Regards

Andrea

17 Replies
agigliotti
Partner - Champion
Partner - Champion
Author

I applied the upgrade successfully to version 3.0.1 on both nodes right now.

However I still get the same error message accessing the RIM node hub.

How can I fix it ?

Anonymous
Not applicable

Does your RIM Node has engine installed in it. If not, you have to route your RIM node to Central node.

Proxies>>RIM Node>>Load balancing>>Add>> central node.

Thanks,

Nithesh

agigliotti
Partner - Champion
Partner - Champion
Author

yes I did it on the default virtual proxy of rim node.

the support told me there was a bug in version 3.0 fixed in 3.0.1 but it's not true.

i need a customer patch urgently.

agigliotti
Partner - Champion
Partner - Champion
Author

below the issue i'm facing opening hub on rim node:

Rim_Error_01.jpg

pablolabbe
Luminary Alumni
Luminary Alumni

Did you solved this issue ?

agigliotti
Partner - Champion
Partner - Champion
Author

Yes finally I solved opening the port 4900 (two-ways) on the firewall and disabling IPv6 in TCP settings.

Anonymous
Not applicable

Thanks!

This solved my problem.

hugo_andrade
Partner - Creator II
Partner - Creator II

I wouldn't call this a valid solution since it changes the environment design.