How to Fix InsightCM if the Server Name Was Changed After Installation

Issue Details

When attempting to log in to the InsightCM web client at http://<server IP>:82, the browser returns HTTP Error 500.37 — ANCM Failed to Start Within Startup Time Limit.

Checking the server shows that the InsightCM Windows service is not running. The Windows Event Viewer Application log contains repeated InsightCMService crash entries with the exception "Could not connect to RabbitMQ broker", along with IIS AspNetCore Module V2 Event 1007 errors.

This behavior occurs when the Windows server was renamed after InsightCM was installed. The RabbitMQ message broker used by InsightCM binds its configuration to the server name at installation time, so after a rename the broker can no longer start, which prevents the InsightCM service and web client from starting.

 

Prerequisites

- Access to the InsightCM server (local or remote desktop session)

- Administrator rights on the server

- Command Prompt (CMD) opened as Administrator

- InsightCM 26 or 3.10.x (see Additional Information for earlier versions)


 

Table of Contents

Prerequisites

Instructions

Outcome


 

Instructions

1. Log in to the InsightCM server and open Command Prompt as Administrator.

2. Navigate to the folder containing InsightCMConsole.exe. The location depends on your InsightCM version:

For InsightCM 26:

cd "C:\Program Files\Cutsforth\InsightCM\InsightCMConsole"

For InsightCM 3.10.x:

cd "C:\Program Files\Cutsforth\InsightCM"

3. Execute the following command to re-establish the RabbitMQ initial configuration with the current server name:

InsightCMConsole.exe configure-rabbitmq

4. Restart the InsightCM service: open the Services console (services.msc), locate InsightCM, and click Restart (or Start if the service is stopped).

 


 

Outcome

The InsightCM service shows a Running status in the Services console, and the InsightCM web client at http://<server IP>:82 loads the login page normally.


 

Additional Information

Avoid renaming the Windows server after InsightCM has been installed. If a server rename is required, plan to run the configure-rabbitmq command immediately afterward to restore RabbitMQ connectivity.

The configure-rabbitmq command is available in InsightCM 3.10.x and later. In earlier versions, this command does not exist and a reinstallation of InsightCM may be required to recover from a server rename.


 

Do you need more help?

Submit your questions or requests using the Support Ticket Submission form.

Was this article helpful?
0 out of 0 found this helpful