The Qlik NPrinting messaging service and the Qlik NPrinting Scheduler service go down just after restart
Article Number: 000044459 | Last Modified: 2019/01/14
The Qlik NPrinting messaging service and the Qlik NPrinting Scheduler service go down just after restart. The services run for some seconds, than they stop automatically. You are not able to run any tasks. The Engine status stays on Offline.
You can try to
1. Open a new command prompt as Administrator
2. Navigate to the RabbitMQ sbin folder: cd %ProgramFiles%\NPrintingServer\rabbitmq_server-3.5.7\sbin
3. Run: rabbitmqctl.bat status
The command line shows that the node is down or unreachable.
The problem is due to a corruption of some files that the Rabbit service needs to run. This corruption may occur after a change in the OS, like an update or after an upgrade of NPrinting.
1. Stop all the NPrinting services
2. Copy the file ".erlang.cookie" from the %SystemRoot% folder (C:\Windows).
For NPrinting 2018 November release and higher, the ".erlang.coockie" file is in C:\Windows\System32\config\systemprofile.
3. Go to to the %USERPROFILE% folder (C:\Users\npadmin) remove the ".erlang.cookie" file that you can find there and replace it with the file you found in point 2.
4. Restart the NPrinting services
If the problem persists, proceed with the following steps
5. Stop all the NPrinting services
6. Open a new command prompt as Administrator
7. Navigate to the RabbitMQ sbin folder: cd %ProgramFiles%\NPrintingServer\rabbitmq_server-3.5.7\sbin
8. Run: rabbitmq-service.bat stop
9. Run: rabbitmq-service.bat remove
10. Go to the "C:\ProgramData\NPrinting\RabbitMQ" folder
11. Remove all the files and folders, keep only "rabbitmq.config" and "enabled_plugins".
12. Run: rabbitmq-service.bat install
13. Run: rabbitmq-service.bat start
14. Start the NPrinting services (the Qlik NPrinting Messaging service should be already running)