Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > PowerShell script alert action fails: Exit code 3221225794

PowerShell script alert action fails: Exit code 3221225794

Table of contents

Updated July 13, 2017


A PowerShell script with domain credentials fails or does not execute the alert trigger action. The script runs without defined credentials and only fails when a user and password is specified.

Errors similar to the following are found in the actionsexecution.log and actionsexecutionalert.log files:

2017-07-06 14:10:12,906 [95] ERROR AlertingLogger - (null) Execute program D:\Powershell.exe -File "$filename" failed...
SolarWinds.Orion.Core.Actions.Exceptions.ActionExecutionFailedException: Execute program failed with exit code 3221225794

2017-07-06 14:11:27,344 [126] ERROR SolarWinds.Orion.Core.Actions.Utility.ProcessExecutor - (null) Exception create process by CreateProcessWithLogonW method command: D:\Powershell.exe -File "$filename", username ... error code: 1326


All Orion Platform versions


  1. Establish a remote connection to the main Orion server.
  2. Open Control Panel, and then go to Administrative Tools > Computer Settings > Windows Settings > Security Settings > Local Policies > Security Options.
  3. Locate and turn off the User Account Control: Run all administrators in Admin Approval Mode policy.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified