Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Error while executing script- Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression

Error while executing script- Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression

Updated March 13, 2017

Overview

While doing an NPM upgrade, you may see below error message:

Error while executing script- Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

Applying Core platform HF4 does not help.

Environment

NPM 12 upgrade, fixed in next release

Cause 

There are duplicate entries in the views table.

Specifically ViewKey field in Views Table

or

There may be two primary pollers in the database left from an incomplete / failed migration.

Resolution

DELETE FROM Views WHERE ViewID = "of duplicate view"

 

If delete is not possible, you can just update or rename the Duplicate ViewKey

 

To determine the duplicate ViewKey

 

Run below query

SELECT viewkey, COUNT(ViewKey) from Views where ViewKey is not null group by ViewKey

Column1 should only have 1

 

Then you need to update the duplicate ViewKey

 

Click Enable table editing

Rename the ViewKey that has duplicate

E.G Virutalization Summary > Backup Virtualization Summary

 

Re-run the Configuration Wizard

 

For two primary pollers:

Open the Database Manager as administrator.

Open the Engines, OrionServers, Websites, and NodesData Tables.

Enable table editing and delete the row containing the older duplicate primary poller in the Engines, OrionServers, Websites.

tables. 

 

Verify that the Nodes in the NodesData have the same EngineID as the remaining primary poller.

 

Re-run the Configuration Wizard.

 

 

 

Last modified

Tags

Classifications

Public