Re: SP3 Inventory causing 100% CPU issues
- From: "Samson Li [MSFT]" <samsonli@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 May 2007 16:35:34 -0700
Hello,
We have identified this issue is caused by one bug in SMS_AutoStartSoftware
class. This new class added in SP3 collects auto run software information
from the clients. When you have some files in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run (or some
other auto run locacations), the file language is a mixed language, and also
the current user locale is different than the file language,
SMS_AutoStartSoftware class cannot handle that correctly. The result is it
went into a dead loop, and generated high CPU ulilization.
The workaround is: backup sms_def.mof under sms\inboxes\clifiles.src\hinv,
and then modify sms_def.mof to disable the SMS_AutoStartSoftware class.
Search SMS_AutoStartSoftware in sms_def.mof, you can find information as
below:
[ dynamic, provider("AAInstProv"),
SMS_Report (TRUE),
SMS_Group_Name ("AutoStart Software"),
SMS_Namespace (TRUE),
SMS_Class_ID ("MICROSOFT|AUTOSTART_SOFTWARE|1.0") ]
class SMS_AutoStartSoftware : SMS_Class_Template
Change " SMS_Report (TRUE)" to "SMS_Report (FALSE)", and save the
file.
This class only collects auto run software information. After disabling this
class, you can still get all license data.
"Phil Ashling" <PhilAshling@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:880D518A-F0C3-4247-A7F1-592A2AE7ABAB@xxxxxxxxxxxxxxxx
I'm getting the following error on affected machines
Unknown error encountered processing an instance of class
SMS_AutoStartSoftware: 800706BE
I see a similar post in SMS-setup board relating to TightVNC but we don't
use that software.
"Samson Li [MSFT]" wrote:
InventoryAgent log gives you the WQL queries that it ran to get data. You
can use wbemtest to find out which query caused the problem.
You mentioned that the high CPU issue disappeared after you disable some
new
classes in sms_def.mof. You can search those new classes in sms_def.mof,
find the WQL query for them, and then use wbemtest to run the query one
by
one, until you reproduce the high CPU issue. Please let me know which
query
caused the problem. I am intertested to reproduce the issue and find the
root cause.
For example, if the class is SMS_SystemConsoleUse, and you find the WQL
entry in inventoryagent.log is:
Collection: Namespace = \\.\root\cimv2\sms; Query = SELECT __CLASS,
__PATH,
__RELPATH, LastConsoleUse, NumberOfConsoleLogons, SystemConsoleUser,
TotalUserConsoleMinutes FROM SMS_SystemConsoleUser; Timeout = 600 secs.
You can run wbemtest, connect to root\cimv2\sms, and then run SELECT
__CLASS, __PATH, __RELPATH, LastConsoleUse, NumberOfConsoleLogons,
SystemConsoleUser, TotalUserConsoleMinutes FROM SMS_SystemConsoleUser.
Different WQL query might have different namespace.
Good luck!
Samson Li
"Phil Ashling" <PhilAshling@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4E0F26C8-449B-4BA5-A553-2AFF8410CAD1@xxxxxxxxxxxxxxxx
I'm having an issue with about 5% of my xp sp2 clients whereby wmiprvse
runs
at 100% cpu for hours causing the clients to be unusable since
upgrading
to
SP3.
Through production support services we have commented out the various
new
classes within sms_def.mof and the clients are now stable but the new
classes
cannot now be reported on.
The InventoryAgent log only shows the class from sms_def.mof it is
querying
- is it possible to make the log more verbose so I can see specific
issues
and find out exactly what is breaking the hardware inventory agent?
.
- Follow-Ups:
- Re: SP3 Inventory causing 100% CPU issues
- From: Phil Ashling
- Re: SP3 Inventory causing 100% CPU issues
- References:
- Re: SP3 Inventory causing 100% CPU issues
- From: Samson Li [MSFT]
- Re: SP3 Inventory causing 100% CPU issues
- Prev by Date: Re: Client Install
- Next by Date: Re: SP3 Inventory causing 100% CPU issues
- Previous by thread: Re: SP3 Inventory causing 100% CPU issues
- Next by thread: Re: SP3 Inventory causing 100% CPU issues
- Index(es):
Relevant Pages
|
