A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Joe — Fri, 17 May 2013 14:21:58 GMT

I have been struggling with this script and trying to get it work. It turns out that many of my servers had bigger problems with the performance counters. To resolve them, I simply rebuilt them using:

lodctr /r

This seemed to take care of the issue. Prior to executing this command, the script would hang for a very long time and then return an error. Now, it returns what looks like XML in about 30 seconds.

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Leigh S — Thu, 23 Aug 2012 07:01:05 GMT

Microsoft has removed the 2000 Resource kit from its download site.

The same thing can be accomplished by modify the following registry value.

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance

Disable Performance Counters from 1 to 0

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

bobgreen84 — Wed, 30 May 2012 14:21:20 GMT

technet.microsoft.com/.../dd279686.aspx

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Alph — Thu, 11 Aug 2011 08:20:05 GMT

Thanks a lot ! Good explanation and solution works like a charme :)

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Stephen Leuthold — Wed, 23 Feb 2011 17:08:16 GMT

Worked on most of my servers. In one case I had to stop winmgmt and run wmiadap /f.

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Kevin Holman — Fri, 04 Feb 2011 16:18:09 GMT

@Stewart -

If 2008 R2 - make sure WMI isnt leaking memory per my other article.

If not 2008 R2 - make sure cscript is updated to 5.7, and WMI is functional, then walk through the script and try and determin which steps are failing to return data.

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Stewart Anderson — Fri, 04 Feb 2011 04:33:54 GMT

Kevin, ive got an issue whereby this script returns

The process started at 2:28:15 PM failed to create System.PropertyBagData, no errors detected in the output. The process exited with 0

Command executed: "C:\Windows\system32\cscript.exe" /nologo "SCOMpercentageCPUTimeCounter.vbs" BACVSDWH01.domain.net false 3

Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\1674\

One or more workflows were affected by this.

Workflow name: Microsoft.SystemCenter.HealthService.SCOMpercentageCPUTimeMonitor

Instance name: BACVSDWH0.domain.net

Instance ID: {BE9C744E-D538-DB04-6F2C-5AEF157DBFC0}

Management group: BACSCOM

The server has been rebooted and is functioing fine so not sure where to go? If i manually run the script i get nothing back also.

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Yury Habets — Tue, 27 Jul 2010 13:21:29 GMT

Kevin, I have one server at our customers' with the issue, and I noticed that all rules dealing with "Process" performance object are not collecting any data. This affects not only "agent processor utilization" workflows, but also w3wp.exe monitoring and so on.

I've asked to apply the fix. I'll post back if everything is OK.

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Stephen — Mon, 05 Jul 2010 07:01:50 GMT

IBM X3950

X64

32GB Mem

Server 2008 R2

I found this article over the weekend and applied the hotfix. I think this has resolved my issue as 5 of the servers has not come back with any issues

blogs.technet.com/.../wmi-leaks-memory-on-server-2008-r2-monitored-agents.aspx

Thanks

re: A new script error - SCOMpercentageCPUTimeCounter.vbs - Invalid class

Kevin Holman — Fri, 02 Jul 2010 14:26:23 GMT

On:

SCOMpercentageCPUTimeCounter.vbs(212, 2) SWbemObjectSet: Out of memory Assuming Issue with WMI

SCOMpercentageCPUTimeCounter.vbs(125, 5) SWbemRefresher: No more threads can be created in the system. Assuming Issue with WMI

I have seen both of these - and both times it appeared to be an issue with WMI. It didnt need a WMI rebuild - it needed the WMI service restarted or a reboot of the OS. Can you please find out on the majorty of systems with these errors - what OS are they running? Also - how much memory (private bytes) are the WMI processes using in Task manager?