Problem installing in Azure

Hi,

My team are getting this error when they are trying to install SolarWinds Platform on an Azure based Server, just wondering if anyone else has come across it?

Configuring Certificate Management FAILED

Services configuration failed:
• Status(StatusCode="Unavailable", Detail="Error starting gRPC call. HttpRequestException: An error occurred while sending the request. WebException: Unable to connect to the remote server SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:17732", DebugException="System.Net.Http.HttpRequestException: An error occurred while sending the request.")

Any help would be great.

Find more posts tagged with

Accepted answers

All comments

DaHaole

Aloha....

I have been getting this as well. I ran into it when the version came out, and had to rebuild my entire environment (I know I should have patched PPE before deploying into Prod). I waited until a week or so ago to try again (moving from 2024.2.1) and ran into this again. I have started a case. As a part of the case I also redeployed PPE directly as 2024.4 and run into the same error (at least with the upgrade the environment would "run" only with no RabbitMQ).

alankar.srivastava

we are also facing same problem, did you get any resolution to fix this error? Appreciate if your help in advance.

pankaj.mahajan

We have also noted same error while installation on Azure, SolarWinds Support team is working on case. Let's hope they give the solution.

@LeBeauUK Did your team got any solution ?

mklemovitch

Posting my experience for info:

I ran into this with an on-premise upgrade from 2022.4.1 to 2025.1.1. Examination of the error seemed to point to Rabbit MQ. Looking at the folder for it under c:\Programdata indicated the database had not been built/initialized and the service not installed as part of the online installer inline upgrade. I followed Steps 9 and 10 listed in this support article: https://solarwindscore.my.site.com/SuccessCenter/s/article/Rabbit-MQ?language=en_US ).

After that was done, we were able to run through the Configuration Wizard, restart services and see all everything working as expected.

james.kluza

I don't think this an issue with AzureDB rather an under-documented additional service added in the 2024.4 platform release. Full write up is here, SolarWinds Certificate Management Service but basically in 2024.4 they added a port requirement for a Certificate Management Service that also has an additional executable attached with it. If you are doing any kind of lock down or executable exclusions from an antivirus or similar perspective, you'll need to allow this additional service located here:

<INSTALL_LOCATION>\SolarWinds\Orion\Net\SolarWinds.CertificateManagement.Service.exe

There is also a known issue reported in the 2024.4 release notes about version mismatches between Core and Runtime .NET versions, which you can find here: https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/solarwinds_platform_2024-4_release_notes.htm