SCOMpercentageCPUTimeMonitor disable?

Has anyone received this warning constantly on machines? If so, do you have a way to silence this one or at least change the threshold to make it not occur? Thanks. Gary

 

Microsoft.SystemCenter.HealthService.SCOMpercentageCPUTimeMonitor

 

The PowerShell script failed with below exception

System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.At line:106 char:15

  • … $checker = Get-CimInstance -ComputerName $ComputerName -Namespace "r …

at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at Microsoft.EnterpriseManagement.Common.PowerShell.RunspaceController.RunScript[T](String scriptName, String scriptBody, Dictionary`2 parameters, Object[] constructorArgs, IScriptDebug iScriptDebug, Boolean bSerializeOutput)

Script Name: SCOMpercentageCPUTimeCounter.ps1

One or more workflows were affected by this.

Workflow name: Microsoft.SystemCenter.HealthService.SCOMpercentageCPUTimeMonitor

1 Like

Have you upgraded to UR4 yet? This is one of the fixed issues:

Fix: SCOMpercentageCPUTimeCounter.ps1 script generates WMI errors that are caused by Service Principle Name (SPN) configuration issues. (servers configured with HTTP SPN’s)

Might be related to your problem!

1 Like

Ahh no. I’m on RU3. However, my problem says the script can’t even run right?

 

The PowerShell script failed with below exception

System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.At line:106 char:15

  • $checker = Get-CimInstance -ComputerName $ComputerName -Namespace "root\cimv2 …

at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Script Name: SCOMpercentageCPUTimeCounter.ps1

One or more workflows were affected by this.

Sounds like winrm is not responding on http?

check the config:

https://msdn.microsoft.com/en-us/library/aa384372(v=vs.85).aspx

1 Like

Looks like this resolves the issue…

 

https://gallery.technet.microsoft.com/SCOM-2016-System-Center-1611d6c8

 

:slight_smile:

2 Likes

Gary Jackson’s response above will resolve the issue, though this was only ever meant to be a temporary solution to resolve a bug in the MS MPs.

This is a temporary fix for rules and monitors in the System Center Core Monitoring MP shipped with SCOM 2016 (UR3). Issues arise when using WinRM to extract WMI information for some configurations. The issue is reported to Microsoft, though until they make a fix this is the only workaround except from disabling them.
SCOM 2016 UR4 does contain the fix for this:

https://support.microsoft.com/en-gb/help/4024941/update-rollup-4-for-system-center-2016-operations-manager

1 Like

It’s basically a bug in the MS MP. The link that Gary does resolve the issue, however, as UR4 has the fix from MS, upgrading will be a better solution moving forward -
https://support.microsoft.com/en-gb/help/4024941/update-rollup-4-for-system-center-2016-operations-manager