RabbitMQ – “Failed to create cookie file (drive:)/erlang”

RPI Consultants discovered an issue relating to the installation of Perceptive Content versions 7.1.4 and beyond. Fortunately, we also discovered the solution! All of the steps he used to solve this problem are detailed here.

RabbitMQ is 3rd party software that runs on Erlang (a programming language). In the Perceptive Content Suite, this replaces the Message Queuing Agent from previous versions. Message queuing refers to how the system sends messages back and forth between the server and various components in the Perceptive Content Suite.

Prior to version 7.1.4, the message queuing agent was installed with ImageNow as a part of the core services. Lexmark was having various reliability issues with the Message Queuing agent such as system-wide performance issues and an inability for the product to scale with Perceptive Content’s evolution. Due to this, Lexmark decided to move away from using the Message Queuing agent. Starting with version 7.1.4, RabbitMQ and Erlang are now a required part of the Perceptive Content Suite installation.

Issue

When installing RabbitMQ, the process creates a dump file with the error “Failed to create cookie file (drive:)/erlang”.

This typically occurs when your organization has a policy set to direct the home drive to a directory other than the C: drive.

One way to help determine the state of the installed service is to look at the description in windows services. If the description is blank, there is a good chance that there was an issue with the installation.

Resolution

1) Open command prompt as administrator

2) Change directory to the Program FilesRabbitMQ Serverrabbitmq_server-3.5.5sbin directory

3) Run the following commands:

SET HOMEDRIVE=C:

rabbitmq-plugins.bat enable rabbitmq_management

rabbitmq-service.bat stop

rabbitmq-service.bat remove

rabbitmq-service.bat install

rabbitmq-service.bat start

SET HOMEDRIVE=(drive:) (set to home drive letter)

Take these steps to ensure you have the new messaging tools on your server. This way you can be sure the Perceptive Content Suite is successfully relaying messages between the server and Perceptive software.