We have received the following error. Most noted is the 'Out Of Memory'and Caught exception while collecting cpu properties. The complete error is this. However a team member found a bug in theWmiPrvSE.exe which gets hung. There are two corrections. 1. Kill the WMIPrvSe.exe process on the server itself. 2. Restart the server, or failover if it is a cluster, then reboot the inactive node.
...xception : System.Management.ManagementException: Out of memory at System.Management.ManagementException.ThrowWithExt endedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.Manag ementObjectEnumerator.MoveNext() at Microsoft.PowerShell.Commands.GetWmiObjectCommand. BeginProcessing() TargetObject : CategoryInfo : InvalidOperation: (:) [Get-WmiObject], ManagementExcepti on FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands. GetWmiObjectCommand ErrorDetails : InvocationInfo : System.Management.Automation.InvocationInfo PipelineIterationInfo : {0, 0} WARNING : 11/29/2013 9:02:01 PM : MyCommand : Get-WmiObject BoundParameters : {[Class, Win32_Processor]} UnboundArguments : {} ScriptLineNumber : 731 OffsetInLine : 21
HistoryId : -1 ScriptName : Line : (Get-WmiObject Win32_Processor) | PositionMessage : At line:731 char:21 + (Get-WmiObject <<<< Win32_Processor) | InvocationName : Get-WmiObject PipelineLength
: 1 Pipelinenbsp; ExpectingInput
: False CommandOrigin : Internal WARNING : 11/29/2013 9:02:01 PM : 00000000000000000000000000000000000000000000000000000000000000000000000000000000 WARNING : 11/29/2013 9:02:01 PM : ErrorInformation : System.Management.ManagementBaseObject ErrorCode : OutOfMemory Message
: Out of memory Data : {} InnerException : TargetSite : Void ThrowWithExtendedInfo(System.Management.ManagementStatus ) StackTrace
: at System.Management.ManagementException.ThrowWithExtended Info(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.Management ObjectEnumerator.MoveNext() at Microsoft.PowerShell.Commands.GetWmiObjectCommand.Begin Processing() HelpLink : Source : System.Management ERROR : 11/29/2013 9:02:01 PM : Caught exception while collecting cpu properties. A WMI query might have failed. WARNING : 11/29/2013 9:02:01 PM : Error occurred during execution of script. WARNING : 11/29/2013 9:02:01 PM : Transaction will be rolled back. WARNING : 11/29/2013 9:02:01 PM : PSMessageDetails : Exception : Microsoft.PowerShell.Commands.WriteErrorException: 11/29 /2013 9:02:01 PM : Caught exception while collecting cpu properties. A WMI query might have failed.
TargetObject : CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write- ScriptError ErrorDetails : InvocationInfo : System.Management.Automation.InvocationInfo PipelineIterationInfo : {0, 0} WARNING : 11/29/2013 9:02:01 PM : MyCommand : Write-ScriptError BoundParameters
: {[object, Caught exception while collecting cpu properties. A WMI query might have failed.]} UnboundArguments : {} ScriptLineNumber : 752 OffsetInLine : 24 HistoryId : -1 ScriptName : Line : Write-ScriptError "Caught exception while collecting cp u properties. A WMI query might have failed." PositionMessage : At line:752 char:24 + Write-ScriptError <<<< "Caught exception while colle cting cpu properties. A WM... Process Exit Code -1. The step failed.
Akinja