sysutility_mi_collect_and_upload job failng

Question

Hi,

i have enrolled a new instance into the existing UCP. In that server job "sysutility_mi_collect_and_upload" is failing at step 2 with below error.

 

 Exception             : System.Management.ManagementException: Invalid class                              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 : 1/13/2011 5:40:16 PM :     MyCommand        : Get-WmiObject  BoundParameters  : {[Filter, IDProcess = '1068'], [Class, Win32_PerfRawData_Perf                     Proc_Process]}  UnboundArguments : {}  ScriptLineNumber : 716  OffsetInLine     : 21  HistoryId        : -1  ScriptName       :   Line             :       (Get-WmiObject Win32_PerfRawData_PerfProc_Process -filt                     er "IDProcess = '$processId'") |   PositionMessage  :                      At line:716 char:21                     +       (Get-WmiObject <<<<  Win32_PerfRawData_PerfProc_Proce                     ss -filter "IDProcess = '$processId'") |   InvocationName   : Get-WmiObject  PipelineLength   : 1  PipelinePosition : 1  ExpectingInput   : False  CommandOrigin    : Internal          WARNING : 1/13/2011 5:40:16 PM : 00000000000000000000000000000000000000000000000000000000000000000000000000000000  WARNING : 1/13/2011 5:40:16 PM :     ErrorInformation : System.Management.ManagementBaseObject  ErrorCode        : InvalidClass  Message          : Invalid class   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 : 1/13/2011 5:40:16 PM : Caught exception while collecting cpu properties.  A WMI query might have failed.  WARNING : 1/13/2011 5:40:16 PM : Error occurred during execution of script.  WARNING : 1/13/2011 5:40:16 PM : Transaction will be rolled back.  WARNING : 1/13/2011 5:40:16 PM :     PSMessageDetails      :   Exception             : Microsoft.PowerShell.Commands.WriteErrorException: 1/13/                          2011 5:40:16 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 : 1/13/2011 5:40:16 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...  Process Exit Code -1.  The step failed.

please let me know the workaround

---

Jyothi

Answer 1

Both the Untility control point server and Enrolled instance servers are running on SQL 2k8 R2 - 64 bit version.

Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   Apr  2 2010 15:48:46   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

---

Jyothi

Answer 2

Thanks for posting the issue. Looking into the job error log, there seems to be problem with executing WMI queries for Win32_PerfRawData_PerfProc_Process class on the machine that hosts the managed instance. This could possibly be due to WMI repository corruption on that machine. Follow the instruction in the below link to troubleshoot WMI related errors in utility setup. Please respond to this thread in case you see further problems.

http://msdn.microsoft.com/en-us/library/ee210592.aspx   

 

Thx,

Narayan

Answer 3

hi Narayan

i have executed the Wmidag utility and found the below information in log

 

...98 22:23:27 (0) ** WMIDiag v2.0 started on Thursday, January 13, 2011 at 22:23.
...99 22:23:27 (0) **
..100 22:23:27 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
..101 22:23:27 (0) **
..102 22:23:27 (0) ** This script is not supported under any Microsoft standard support program or service.
..103 22:23:27 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
..104 22:23:27 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
..105 22:23:27 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
..106 22:23:27 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
..107 22:23:27 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
..108 22:23:27 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
..109 22:23:27 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
..110 22:23:27 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
..111 22:23:27 (0) ** of the possibility of such damages.
..112 22:23:27 (0) **
..113 22:23:27 (0) **
..114 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..115 22:23:27 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
..116 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..117 22:23:27 (0) **
..118 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..119 22:23:27 (0) ** Unsupported Windows version - 64-bit (7600) - User 'PHX\xxxxxxxx' on computer 'TK2MSDNSQLMTP21'.
..120 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..121 22:23:27 (0) **
..122 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..123 22:23:27 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
..124 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..125 22:23:27 (0) **
..126 22:23:27 (0) ** ABORT: WMIDiag execution aborted.  Check 'C:\USERS\JYOTHIV\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___TK2MSDNSQLMTP21_2011.01.13_22.23.26.LOG' for details.
..127 22:23:27 (0) **
..128 22:23:27 (0) ** WMIDiag v2.0 ended on Thursday, January 13, 2011 at 22:23 (W:0 E:1 S:4).

 

At present this machine is having Microsoft Windows [Version 6.1.7600]

 

 

---

Jyothi

Answer 4

hi Narayan

i have executed the WMIDiag.exe on this machine and i see the below message in errorlog

...98 22:23:27 (0) ** WMIDiag v2.0 started on Thursday, January 13, 2011 at 22:23.
...99 22:23:27 (0) **
..100 22:23:27 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
..101 22:23:27 (0) **
..102 22:23:27 (0) ** This script is not supported under any Microsoft standard support program or service.
..103 22:23:27 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
..104 22:23:27 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
..105 22:23:27 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
..106 22:23:27 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
..107 22:23:27 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
..108 22:23:27 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
..109 22:23:27 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
..110 22:23:27 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
..111 22:23:27 (0) ** of the possibility of such damages.
..112 22:23:27 (0) **
..113 22:23:27 (0) **
..114 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..115 22:23:27 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
..116 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..117 22:23:27 (0) **
..118 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..119 22:23:27 (0) ** Unsupported Windows version - 64-bit (7600) - User 'PHX\xxxxxx' on computer 'zzzzzzzzzzzzzzzzz'.
..120 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..121 22:23:27 (0) **
..122 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..123 22:23:27 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
..124 22:23:27 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..125 22:23:27 (0) **
..126 22:23:27 (0) ** ABORT: WMIDiag execution aborted.  Check 'C:\USERS\xxxxxxxx\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___TK2MSDNSQLMTP21_2011.01.13_22.23.26.LOG' for details.
..127 22:23:27 (0) **
..128 22:23:27 (0) ** WMIDiag v2.0 ended on Thursday, January 13, 2011 at 22:23 (W:0 E:1 S:4).

Thi server is running on the windows version

Microsoft Windows [Version 6.1.7600]

 

 

 

---

Jyothi

Answer 5

Hi

i have executed the below two commads as per the blog http://blogs.technet.com/b/askperf/archive/2008/07/11/wmi-troubleshooting-the-repository-on-vista-server-2008.aspx and those are succeded

C:\>winmgmt /verifyrepository
WMI repository is consistent

C:\>winmgmt /salvagerepository
WMI repository is consistent

---

Jyothi

Answer 6

Since you are seeing problem with WMI execution, we had a discussion with the WMI team and below are their recommendations. Please try it and let us know in case you see any issues.

 

To generate ETW traces with WMI Activity you need to enable it ->http://blogs.technet.com/b/askperf/archive/2008/03/04/wmi-debug-logging.aspx

Since Windows 2008 WMI isn’t using ADAP to sync Performance Data, it uses a WMIPerfClass Provider for that(http://msdn.microsoft.com/en-us/library/aa394546(VS.85).aspx ).

Could be important to validate if there’s any event/error on the event logs related with Perf libraries.

 

You could also run the winmgmt with /resyncperf <PID of the WMI Management Process>  -> a SQL Server case:http://blogs.msdn.com/b/psssql/archive/2009/03/03/troubleshooting-sql-server-2005-2008-performance-counter-collection-problems.aspx

http://msdn.microsoft.com/en-us/library/aa394525(VS.85).aspx

 

Review the list of hotfixes related with WMI for Windows Server 2008 R2:

http://blogs.technet.com/b/yongrhee/archive/2010/08/17/list-of-windows-management-instrumentation-wmi-related-hotfixes-post-rtm-for-windows-server-2008-r2.aspx

 

There’s one very interesting:

http://support.microsoft.com/?id=977589

Thanks,

Narayan

Answer 7

Hi

 

I have verified the event ewer and did not notice any errors related to perflib.

I have followed the steps given in this (http://blogs.technet.com/b/askperf/archive/2008/03/04/wmi-debug-logging.aspx) blog to enable wmi logging. I have changed logging to verbose and did not see any trace events in EVENTVWR -> Application and Services Logs à Microsoft à WMI-Activity à Trace

I have restarted the WMI services and see the below errors in WKIPROV.log file in wbem /log folder

(Mon Jan 17 08:54:57 2011.1002391959) : ***************************************

(Mon Jan 17 08:54:57 2011.1002391959) : Could not get pointer to binary resource for file:

(Mon Jan 17 08:54:57 2011.1002391959) : C:\Windows\system32\drivers\ndis.sys[MofResourceName](Mon Jan 17 08:54:57 2011.1002391959) :

(Mon Jan 17 08:54:57 2011.1002391959) : ***************************************

(Mon Jan 17 08:54:57 2011.1002391959) : ***************************************

(Mon Jan 17 08:54:57 2011.1002391959) : Could not get pointer to binary resource for file:

(Mon Jan 17 08:54:57 2011.1002391959) : C:\Windows\system32\drivers\en-US\ndis.sys.mui[MofResourceName](Mon Jan 17 08:54:57 2011.1002391959) :

(Mon Jan 17 08:54:57 2011.1002391959) : ***************************************

(Mon Jan 17 08:54:57 2011.1002391974) : ***************************************

(Mon Jan 17 08:54:57 2011.1002391974) : Could not get pointer to binary resource for file:

(Mon Jan 17 08:54:57 2011.1002391974) : C:\Windows\system32\DRIVERS\en-US\IPMIDrv.sys.mui[MofResource](Mon Jan 17 08:54:57 2011.1002391974) :

(Mon Jan 17 08:54:57 2011.1002391974) : ***************************************

(Mon Jan 17 08:54:57 2011.1002391974) : ***************************************

(Mon Jan 17 08:54:57 2011.1002391974) : Could not get pointer to binary resource for file:

(Mon Jan 17 08:54:57 2011.1002391974) : C:\Windows\system32\DRIVERS\monitor.sys[MonitorWMI](Mon Jan 17 08:54:57 2011.1002391974) :

(Mon Jan 17 08:54:57 2011.1002391974) : ***************************************

(Mon Jan 17 08:54:57 2011.1002392661) : WDM call returned error: 4200

(Mon Jan 17 08:54:57 2011.1002392661) : WDM call returned error: 4200

(Mon Jan 17 08:54:57 2011.1002392661) : WDM call returned error: 4200

(Mon Jan 17 08:54:57 2011.1002392661) : WDM call returned error: 4200

(Mon Jan 17 08:54:57 2011.1002392661) : WDM call returned error: 4200

(Mon Jan 17 08:54:57 2011.1002392661) : WDM call returned error: 4200

(Mon Jan 17 08:54:57 2011.1002392676) : WDM call returned error: 4200

(Mon Jan 17 08:54:57 2011.1002392676) : WDM call returned error: 4200

 

I did not tried the steps given in the blog (http://blogs.msdn.com/b/psssql/archive/2009/03/03/troubleshooting-sql-server-2005-2008-performance-counter-collection-problems.aspx). I feel its more comfortable, if we did it with the help of CSS engineer

I have upgraded the OS with latest ipaks. Still no luck . upload job is failing with the same error and i have notcied this error in Eventviewer

Event filter with query "select * from HP_PowerSupplyEvent" could not be reactivated in namespace "//./root/WMI" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

Event filter with query "select * from HP_TempSensorFailureEvent" could not be reactivated in namespace "//./root/WMI" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

Event filter with query "select * from HP_IMLUpdatedEvent" could not be reactivated in namespace "//./root/WMI" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

Event filter with query "select * from HP_ASRStateChangeEvent" could not be reactivated in namespace "//./root/WMI" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

Event filter with query "select * from HP_UIDStateChangeEvent" could not be reactivated in namespace "//./root/WMI" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

Event filter with query "select * from HP_FanEvent" could not be reactivated in namespace "//./root/WMI" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

 

---

Jyothi

Answer 8

This issue has be taken offline with WMI team for further follow up. The troubleshooting findings would be posted back to this forum for educational purpose to the rest of audience.

 

Thanks,

Narayan

Answer 9

Hi

So could you please let us know the solution ?

Thanks.

Answer 10

We have the excat same issue on several machines. Our monitoring tool cannot find the Win32_PerfRawData_PerfProc_Process class.

What's the status of this issue?

 

Best regards,

James