Submit a ticketCall us
Home > Success Center > Network Performance Monitor (NPM) > Continuous SQL event errors in the SolarWinds.Net application log every 2-10 minutes

Continuous SQL event errors in the SolarWinds.Net application log every 2-10 minutes

Created by Marjune Obana, last modified by MindTouch on Jun 23, 2016

Views: 38 Votes: 1 Revisions: 5

Overview

There are continuous errors in the Windows SolarWinds.Net Applications log every 2 to 10 minutes.

The following are the errors that occur if the SQL query seems to have malformed from the Advanced Alert option. When you check the AlertService log, you will notice the message:
'Error in UpdateRowsThatAreTriggered' pertaining to the Trigger query and that query contains 'NodeID' but unable to find from the table. 
'Error in UpdateRowsThatAreTriggered' pertaining to the Trigger query and that query contains 'NodeID' but unable to find from the table.

[AlertCheckingThread] ERROR Error - Error in UpdateRowsThatAreTriggered() - GetNetObjects
System.Data.SqlClient.SqlException (0x80131904): Ambiguous column name 'NodeID'. Ambiguous column name 'NodeID'.

This will be the same error message from the Even Viewer SolarWinds.Net Applications log.

Environment

All NPM versions

Resolution

Do the following steps to resolve the issue
  1. Open c:\Program Files (x86)\SolarWinds\Orion\AlertingEngine.exe.config and look for the following section:
    <logger name="UpdateResetRows" >
    <additivity value="true" />
    <level value="NONE" / >
    </logger >
  2. Edit <level value="NONE" / > to <level value="ALL" / >
 
To see the error(s) in c:\Program Files\SolarWinds\Orion\swAlert.log.x files.
  1. Open Database Manager and run the following SQL Query:
    SELECT AlertName, LastErrorTime, LastError FROM [dbo].[AlertDefinitions]
    WHERE LastError is NOT NULL
    order by LastErrorTime DESC
  2. This query will show which alerts are causing the errors.
  3. Disable the alert(s) that is causing the error(s).

    Check in Advanced Alert and ensure that the alert condition is correct, for example:

    In trigger type, if Interface is selected, ensure that the condition selected is for Interface and not for Node when using Custom SWQL Alert.

 

Last modified
21:57, 22 Jun 2016

Tags

This page has no custom tags.

Classifications

Public