Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
The Qlik NPrinting installation fails with:
0x80070643: Failed to install MSI package when trying to install Messaging server (or RabbitMQ).
Detailed errors logged in the installation logs include:
ERROR in custom action RabbitMQ. The Erlang or RabbitMQ installation paths could not be found
CustomAction RabbitMQPaths returned actual error code 1603 but will be translated to success due to continue marking
In this case, a complete uninstall of NPrinting can enable to install the new version correctly. Before proceeding it is necessary to have a backup of the repository. The backup will be updated at the end of the upgrade process in order to make it compatible with the new NPrinting version.
Hi Benjamin,
We are performing inplace upgrade and facing this error messg. We dont want to lose our old repository, is that ok to continue with above steps in this case?
Thanks
Raj
To elaborate further,
WE have a server-A which already have Npriniting-2019 Nov version working for past 2 years. Now, we would like to upgrade to Nprinting-May-2022 version without losing any work by performing inplace upgrade.
When we tried to follow steps for inpace upgrade we started seeing same error messg as above.
The resolution steps says to completely uninstall the software which I felt abit concerning as it may cause to lose our repository, please suggest what should I do now?
Thanks
Raj
Hi @raj_qlik9
Thanks for the very good question. We've just updated the article providing more complete instructions to uninstall and a new link that explains how the old database backup can be upgraded separately after the new installation.
Be sure to create the backup correctly before uninstalling.
In general, we suggest to upgrade NPrinting more frequently. The update and the repository upgrade works better if the old and the new versions are not so distant.
Thanks a lot @Andrea_Bertazzo for a quick turn around, we will follow above steps and let you know how that goes.
Thanks
Raj
Thanks @Andrea_Bertazzo !
This is helpful!
We got one error related to DB versioning while restoring as below
" The database version 19.40.3.0 is different from the assembly version 21.14.7.0"
So followed another article that was also posted by you, that resolved it
Thanks
Raj