Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Alert not working after alert owner account is disabled

Alert not working after alert owner account is disabled

Updated March 11th, 2016


Alerts owned by an account user that has been deleted/disabled have stopped working.


The Alerting,Service.v2.log file located in C:\ProgramData\Solarwinds\Logs\Orion\ shows the following message:

2017-08-23 09:04:48,105 [54] WARN  SolarWinds.Orion.Core.Alerting.Plugins.Conditions.
Swql.ConditionEvaluatorSwql - Condition evaluation failed : User account is disabled.




  • Orion Core
    • 2015.x
    • 2016.x
    • 2017.1 
  • NPM
    • 11.5.x
    • 12.0
    • 12.0.1
    • 12.1
  • SAM
    • 6.2.x
    • 6.3
    • 6.4


This issue is resolved in NPM 12.2 or any module which ships with Orion Core 2017.1.3 or newer. If you're on an a release listed above the recommendation is to upgrade Orion to the latest release.


Alternatively, there are workarounds below for these older releases:

Reactivate the user account or change the ownership of the alerts:

Warning: Changing the ownership may return different results due to various user limitations.

  1. Create a backup of the database.
  2. Click Start > All Programs > SolarWinds Orion > Advanced Features > Database Manager.
  3. Click Add Default Server and expand down to your SolarWinds database.
  4. Double-click the Alert Configurations table.
  5. Delete the default query and replace with the following: 
    1. If Old users are present:
      UPDATE AlertConfigurations
      SET CreatedBy  = '{new user}'
      WHERE CreatedBy = '{old user}'
    2. If affected alerts have NULL:
      UPDATE AlertConfigurations
      SET CreatedBy = '{new user}'
      WHERE CreatedBy is NULL
  6. Click Execute Query. 
    For a list of accounts, check the Accounts table.
    Pay attention to letter casing in account names.
  7. After updating the DB, restart Alerting Service V2
Last modified
07:46, 19 Sep 2017