Qlik Sense Shared Persistence - Rim nodes not coming back online after restart of the service and/or operating systemArticle Number: 000038082 | Last Modified: 2018/06/12
In Qlik Sense 3.x you might experience issues when restarting your rim nodes at about the same time as the central node.
Intermitendly we noticed that the rim node won't come back online in the central node management console.
Looking into the central node Repository -> Trace -> System log you can see:
System.Repository.Repository.QRSMain 11 fa0c0357-2091-4b92-a3c9-6b821d828746 DOMAIN\administrator Fatal exception No connection could be made because the target machine actively refused it 172.16.16.102:4432↵↓The provider did not return a ProviderManifestToken string.↵↓An error occurred accessing the database. This usually means that the connection to the database failed.
This is likely due to a timing issue where the central repository database is not ready to receive request and at the same time the rim node tries to establish a connection
This issue has been resolved in Qlik Sense June 2017 where we introduced a connection retry from the rim node.
As a workaround you can restart the services on the rim node once the central node is completely up and running to make sure that the central node is receiving the connection request.
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.