Share via

Receving many "Power Shell Script failed to run" alerts

shankar431 471 Reputation points
2021-01-04T15:34:10.583+00:00

Hi All,

We have been receiving lots of alerts related to "Forced to terminate the following PowerShell script because it ran past the configured timeout 300 seconds"

Work flow names shows as below:
Microsoft.Windows.Server.10.0.LogicalDiskDiscovery.ModuleType.ps1
SystemCenterCentral.Utilities.Certificates.LocalScriptProbe.CRL.Discovery
SystemCenterCentral.Utilities.Certificates.LocalScriptProbe.NonRootCertificate.Discovery
Microsoft.Windows.HyperV.2012.R2.HeterogeneousGPUMonitor
Microsoft.Windows.HyperV.2012.R2.RemoteFxCapableMonitor

For the second alert says the below.
The following PowerShell script was forcibly terminated because it exceeded the configured timeout by 30.

Work flow names shows as below:
Microsoft.Windows.HyperV.2012.R2.VMReplicationResyncRequiredState.Monitor
Microsoft.Windows.HyperV.2012.R2.VMReplicationHealth33406.Monitor
Microsoft.Windows.HyperV.2012.R2.VMReplicationCriticalSuspendedState.Monitor
Microsoft.Windows.HyperV.2012.R2.VMReplicationHealth33418.Monitor
Microsoft.Windows.HyperV.2012.R2.HeterogeneousGPUMonitor
Microsoft.Windows.HyperV.2012.R2.RemoteFxCapableMonitor

For the 3rd alert says the below.
Forced to terminate the following PowerShell script because it ran past the configured timeout 900 seconds.

Work flow name:
Microsoft.Windows.Server.10.0.LogicalDisk.Discovery

Can any one help how we can solve this issue.

Regards,
Ravi shankar

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,474 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. CyrAz 5,181 Reputation points
    2021-01-05T08:37:11.87+00:00

    Each of these alerts can happen for different reasons. You need to run these scripts manually on the servers where they are failing to try to identify the cause of their failure.
    You'll find the scripts inside the management packs by exporting them (export-scommanagementpack) or you can also find them on systemcenter.wiki

    0 comments
  2. Chris Lumpkin 1 Reputation point
    2022-02-15T15:25:17.17+00:00

    I keep reading that you need to run the scripts manually (I agree)--what are the parameters that need to be passed? Those are passed from SCOM, are they not?

    0 comments
  3. Chris Lumpkin 1 Reputation point
    2022-02-15T15:27:11.223+00:00

    Param([string]$ComputerName, [string]$ConfigForRun, [int]$ProcessIterationCount)

    I get $ComputerName. What are the others? Are they found in the MP settings?

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.