Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Additional polling engine install - Multiple polling engines detected

I'm trying to install APE on an updated 2016 server. During the configuration wizard, when choosing my existing database, I get a screen that says "Multiple Polling Engines Detected!" and "Please ensure the primary Orion server is updated first and all the services on the primary Orion are running before continuing.". It shows my primary polling engine and the IP. When I click OK, it just takes me back to the Configuration Wizard where I can choose the existing database. It is an infinite loop and no "errors" are displayed. I've already deleted the old polling engine from the database. I've also already updated the primary server to the latest patch. I'm on SAM 6.8, 2018.4.

Find more posts tagged with

Accepted answers

kacperm

Your problem seems similar to the case described here - After migration of a poller Configuration Wizard loops the popup Multiple polling Engines Detected - SolarWinds Worldwid… . Have you tried maybe to apply mentioned workaround?

All comments

kacperm

terryhallal

That totally worked!

So the installation completed, but now the poller reports as "Down" on the polling engines page. The "Last database sync" reports that it last synced when it was installed. The only way I've been able to make it update is by running the config wizard again. But then it stops updating and still reports as "down".

monitoringlife

Got a working link? Looks like the SolarWinds support website changes broke the link.

EDIT:

Apply View Server State permission on the database account for the master database.

From the log: "VIEW SERVER STATE permission was denied on object 'server', database 'master'."

serena

monitoringlife wrote:
Got a working like? Looks like the SolarWinds support website changes broke the link.
EDIT:
Apply View Server State permission on the database account for the master database.
From the log: "VIEW SERVER STATE permission was denied on object 'server', database 'master'."

Here's the updated link Success Center

aaguilar1

Resolution

Open SQL Management Studio and connect to the instance

Run the script below change the <user_name> to the one used on the Configuration Wizard

use master

GRANT VIEW SERVER STATE TO <user_name>

After the above is performed just run the Configuration Wizard again