This error is shown when Redgate Monitor can't connect to the base monitor (also called the monitoring service). You might also see the error "No connection could be made because the target machine actively refused it".
The error has several possible causes.
The monitoring service is disconnected, or there's a problem with the network
Make sure the machine that hosts the monitoring service is turned on and connected to the network.
The monitoring service is stopped
To make sure the monitoring service is running:
- Log into the machine that hosts the monitoring service.
- In the Start menu, type services.msc
Services opens. - In the list, find Redgate Monitor Base Monitor.
- If the service is running correctly, its status should be Running.
If the status is something else, or if there's no status, right-click the service and select Start.
The monitoring service connection details are incorrect
If the machine hosting the monitoring service or its port number have changed, reconfigure Redgate Monitor with the correct connection.
- Log into the machine where the web server is installed.
- Open the Redgate Monitor web interface.
- Enter the connection details.
The web server isn't authorized to access this base monitor
See: The web server isn't authorized to access this base monitor.
10
-10
Was this article helpful?
0 out of 10 found this helpful
Articles in this section
- Redgate Monitor migration guide to version 14
- "Your browser does not seem to be accepting cookies." error message
- Setting up OpenID Connect (OIDC) with Entra ID in Redgate Monitor
- Proxy Configuration in Redgate Monitor
- WMI error after DCOM hardening patch
- Redgate Monitor alert tuning
- Redgate Monitor set up for optimal performance
- Redgate Monitor Base Monitor Service Account
- Configuring Metrics and Alerts in Redgate Monitor
- Getting started with Redgate Monitor