Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > RabbitMQ stops on the Main Polling Engine and generates Orion Web Console issues

RabbitMQ stops on the Main Polling Engine and generates Orion Web Console issues

Updated July 30, 2018


The RabbitMQ service stops on the Main Polling Engine and generates issues with the Orion Web Console, such as missing menus or events that do not trigger an alert.

If you start the RabbitMQ service, it starts momentarily and then shuts down, generating issues with the Core Business Layer and Information Service version 3.


  • NPM 12.2
  • Orion Platform 2018.1
  • Microsoft Windows Server 2012 R2


Corrupted recovery dets file. The file size displays as 0 bytes in size, causing RabbitMQ to fail when started.

The log file displays the following:

Error in C:\ProgramData\Solarwinds\Orion\RabbitMQ\log, "rabbit@HOSTNAME.log":
17-Jul-2018::10:17:04 ===
Error description:


Enable the RabbitMQ server to perform a correct boot-up sequence to allow the service to run. 

  1. Log in to the server. 
  2. Go to:
  3. Copy the recovery dets file to your desktop.
  4. Open the Orion Service Manager and restart the RabbitMQ service.
  5. Verify that the recovery.dets file was recreated. The file should be about 6KB in size.
Last modified