• Management Pack:  SCOM 2016
  • MP Version:  1.0
  • Released:  10/19/2018
  • Publisher:  Microsoft

Alert on Failed Power Shell Scripts Rule

  • ID:  Microsoft.SystemCenter.PowerShellModule.AlertOnFailedResponses
  • Description:  Alerts on failed Power Shell scripts.
  • Target:  Health Service
  • Enabled:  Yes

Overridable Parameters

Parameter Name Default Value Description Override
Priority 1  
Severity 1  

Run As Profiles

Name
Default

Alert Details

Message Priority Severity
Power Shell Script failed to run Medium Warning

Rule Knowledgebase

Summary

The PowerShell failed to execute successfully.

This may affect some monitoring or discovery.

Causes

This can be caused by:

  • An incorrectly written script.

  • Incorrect configuration for the PowerShell Script (missing Data Item reference, incorrectly configured timeout).

  • Lack of permissions to access a resource used by script (Registry, File system, Service, etc...).

  • Resource (Registry, File system, Service, etc...) is slow, offline, or in a corrupted state.

  • The computer does not have enough resources (for example; memory) to run the executable.

Resolutions

The alert description and context has information indicating which rule or monitor failed. The following link will display all events indicating a failure to run the executable:

View PowerShell Events

After reviewing the error in the context, check:

That the PowerShell script executes on the computer without error.

That the PowerShell script is configured correctly Data Item references are valid and present.

That the Action Account has access to the resources used by the PowerShell script.

That the computer is not over utilized.

  • Save the PowerShell script to a file and run it through PowerShell.exe.

  • Check Task Manager to see if there is enough free memory.

  • Check Task Manager to see if there are any processes consuming all the CPU.

Another error can be caused by the misconfiguration of the workflow executing this script. The configuration Snap Ins, Parameters, or Timeout Seconds could be incorrect.

External References
This rule does not contain any external references.

See Also for SCOM 2016 Management Pack


Downloads for SCOM 2016 Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED