Network Management

Configuration Wizard Fails with Error: Service 'RabbitMQ' Was Not Found on Computer in SolarWinds Platform 2025.4

This article describes the step to fix the issue on RabbitMQ not installed on the SolarWinds Platform server due to RMQ mismatched certificate issue.

First published date

5/29/2025 7:07 AM

Last published date

2/11/2026 6:47 PM

Overview

RabbitMQ fails to install on the SolarWinds server due to the failure to create the  RabbitMQ certificate.  

In the logs you will find below error:

*** Assembly SolarWinds.Orion.Orchestrators.Meraki.Common, Version=2025.1.0.0, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***

 DEBUG ConfigurationProgressScene - Setting lblDescription to Checking FIPS 140-2 state in SolarWinds Platform FINISHED

Updating discovery profiles 0.0%

Updating website configuration file 0.0%

Configuring message bus 4.0% - Creating RabbitMQ certificate

 

 INFO  MessageBusConfigurator - Failed to configure RabbitMQ for Orion. Resetting RabbitMQ and retrying... Details: Status(StatusCode="PermissionDenied", Detail="Bad gRPC response. HTTP status code: 403")

 

Configuration wizard log shows:

CN=SolarWinds CM Client. NotSignatureValid The signature of the certificate cannot be verified.

[.NET TP Worker] INFO  Microsoft.AspNetCore.Authentication.Certificate.CertificateAuthenticationHandler - (null)   Certificate was not authenticated. Failure message: Client certificate failed validation.

Product section

Network Performance Monitor

Cause

Failed  creation RabbitMQ certificate due to mismatched RabbitMQ certificate on certificate store.

Resolution

  • Check for the CM client certificates on the certificate table via Database Manager:

  • Once confirmed, go to Certificate store (mmc.exe)  and match the certificate assigned on the Main Poller. Check the thumbprint of CM Client certificates available in the certificate store.

  • If multiple SolarWinds CM client certificates are found, remove the other CM client certificates that do not match the certificate thumbprint assigned to the Poller.

  • If the issue persists after deleting the duplicate certificate without the related thumbprint in MMC, you may proceed with deleting all SolarWinds certificates within MMC.

    After completing the certificate cleanup, re-run the Configuration Wizard.

    Ensure that only the SolarWinds-related certificates are removed.

     Example: