Qlik NPrinting Engine Offline status due to RabbitMQ corruption

[Rakesh_HB]

The status of the Qlik NPrinting Engine consistently appears as Offline on the Engine Manager page.

The Qlik NPrinting Engine Logs read:

RabbitMq server is not connected - trying diagnoser queue creation again in 5 seconds
Qlik.NPrinting.Engine 24.4.14.0 Qlik.NPrinting.Engine.EngineService 20250521T190411.917+05:30 
ERROR NBHI-DC-APP-69 RabbitMq service is not connected - trying again in 60 seconds. 
ERROR: RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable 
---> RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: 
AMQP close-reason, initiated by Peer, code=541, text='INTERNAL_ERROR - access to vhost '/' refused for user 'client_engine': 
vhost '/' is down', classId=10, methodId=40

Additionally, the RabbitMQ logs may read:

EXTERNAL login refused: user 'client_engine' - invalid credentials
[info] closing AMQP connection ([::1]:60918 -> [::1]:5672)
[info] accepting AMQP connection ([::1]:60921 -> [::1]:5672)
[error] Error on AMQP connection ([::1]:60921 -> [::1]:5672, state: starting):
[error] EXTERNAL login refused: user 'client_engine' - invalid credentials
[info] closing AMQP connection ([::1]:60921 -> [::1]:5672)

For information about how to obtain log files, see How to collect the Qlik NPrinting Platform Log Files.

Resolution

Initial checks:

1. Follow the instructions in Qlik NPrinting Engine Offline status 
2. Continue with How to Resolve Qlik NPrinting Engine Offline Status.

If the issue persists, the RabbitMQ installation needs to be repaired. To do so effectively may require multiple rounds of reinstalling the Qlik NPrinting engine, as well as the RabbitMQ certificates to be recreated. 

Our expected result is:

• The Qlik NPrinting Engine comes online
• RabbitMQ logs do not include errors
• We do not receive errors when checking the RabbitMQ status

RabbitMQ repair:

All Qlik NPrinting services must be running for this procedure to work.

1. Recreate the RabbitMQ certificates (see Recreate the messaging service certificates).
2. Reinstall the Qlik NPrinting engine (see Installing Qlik NPrinting Engine).
3. Does the issue persist? Review the Qlik NPrinting and RabbitMQ logs to verify if the two errors (RabbitMq service is not connected and EXTERNAL login refused: user 'client_engine' - invalid credentials) continue to be logged.
4. Check the RabbitMQ service status (see Check the node status on the RabbitMQ console).
5. Repeat: Recreate the RabbitMQ certificates (see Recreate the messaging service certificates).
6. Repeat: Reinstall the Qlik NPrinting engine (see Installing Qlik NPrinting Engine).
7. Verify RabbitMQ permissions for the client_engine user (see Check the messaging service users and permissions).
8. Repeat: Check the RabbitMQ service status (see Check the node status on the RabbitMQ console).
9. If you continue to see errors when checking the RabbitMQ status (rabbitmqctl.bat status), repeat from Step 1. 

This cycle should be completed only twice at the most, but it is necessary to reestablish a connection between the Qlik NPrinting Engine and RabbitMQ.

If this fails to resolve the issue, log a support case with Qlik Support, including detailed information about all troubleshooting steps that have already been performed.

Cause

This indicates the RabbitMQ installation is corrupted or otherwise damaged. Multiple root causes exist:

• A Qlik NPrinting Upgrade corrupted the files
• C:\ Drive was full, or the Qlik NPrinting installation drive was full
• RabbitMQ crashed due to Antivirus scanning
• Unsupported items; for Qlik Sense see Qlik NPrinting and Qlik Sense Object Support and Limitations, for QlikView see Qlik NPrinting: Unsupported QlikView Document items, System Configurations and other limitations.
   

Environment

• Qlik NPrinting