nPrinting 17 Installation Failed - RabbitMQ Node is Down

If the installation failed and rollback check that RabbitMQ service is running. If it is, open the RabbitMQ command prompt (cd to C:\Program Files\NPrintingServer\rabbitmq_server-x.x.x\sbin) in the start menu > run > cmd, and then type and run the command rabbitmqctl.bat list_permissions

The following lines must be displayed:
Listing permissions in vhost "/" ...
guest .* .* .*
remote .* .* .*

If instead you have an error like Error: unable to connect to node 'rabbit@xxx': nodedown 
It's usually a erlang cookie problem and you can check this link for more details: https://www.rabbitmq.com/clustering.html

One of the possible reasons for this error is that the user who install nPrinting has the variable %HOMEDRIVE% pointing on a Network Drive instead of the default C:\users\username.
When installing RabbitMQ, it will try to create a erlang cookie file in %HOMEDRIVE%
RabbitMQ seems not being able to create the Erlang cookies file on a network path.
This variable is usually changed by a GPO in the customer environment in order to redirect the user profile to a Network Path. 

Environment:

• Qlik NPrinting 17 and newer

The workaround currently is to uninstall properly NPrinting, RabbitMQ and Erlang. (Check for residual files in C:\Program Files x86 & C:\Program Files & C:\Programdata\)
Create a Local User on the server, add it to the Local Administrators Group and to Allow logon as a Batch Job.
Connect with this user and run the QlikView_NPrinting_Server.exe as administrator