Re: wmiprvse.exe using an average 95% CPU
- From: nick_oss <nickoss@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Jan 2007 16:06:00 -0800
Hi Rob
Thanks for the advice. Process explorer helped me isolate the problem to the
event log alerts (account lockout and sbs backup failure). Once turned of
using the "changing alert notifications" wizard the CPU problem goes away.
All other standard alerts do not cause the problem and can be left enabled. A
restart is may be required once these alerts are turned off to stop the
wmiprvse.exe process using high CPU (or you can end the wmiprvse.exe process,
would still advise a restart to make sure the process is running in the
correct user context).
Have not resolved the problem completely as event log alerting needs to be
turned off but it is a good start as now my customer is not experiencing slow
server response. Any ideas on troubleshooting the event log alerting further
would be much appreciated.
Once again thanks very much for your assistance with this.
--
Regards
Nick
MCSE, Small Business Specialist
"Rob C" wrote:
Have you used process explorer.
(http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx)
to find what process is really being nasty under wmiprvse.exe? That may lead
you on the right path...
"nick_oss" wrote:
Thanks for all your helpful replies.
I have tried reinstalling the monitoring and this appeared to work for about
30 seconds then the problem started again. Tried this twice. It appears to
stop using the wmiprvse.exe process briefly while reseting the counters which
may mean the problem is related to monitoring (or it just briefly resets the
process!).
Does anyone know how I can temporily stop monitoring completely to see if
this is the root cause?
I have tried stopping the MSSQL$SBSMONITORING service but this appears to
make no difference (do I need to restart the server with this service set to
disabled?).
Once again any assistance is much appreciated.
--
Regards
Nick
MCSE, Small Business Specialist
"Rob C" wrote:
And by 'resetting' I mean 'reinstalling monitoring features'
FYI you will loose the stats already generated
"Rob C" wrote:
This may help:
It happened to one of my SBS servers too last year and in my case was
related to monitoring and reporting.
My CPU levels would spike at 100% for about 15-20 minutes every hour. Whilst
folks assured me this was 'normal'. I disagreed.
I bumped into a thread somewhere that said 'try resetting monitoring and
reporting through MMC'. I did and sure enough, when the server did it's
hourly report generating it only took the CPU to about 80% for a minute or
two.
Seemed to fix the problem...
HTH
"rrafiringa" wrote:
I've seen it on many SBS servers.
It usually happens when the server is gathering statistical data on the
system to create reports usage and performance reports.
--
rrafiringa
------------------------------------------------------------------------
rrafiringa's Profile: http://forums.techarena.in/member.php?userid=18734
View this thread: http://forums.techarena.in/showthread.php?t=659836
http://forums.techarena.in
- Follow-Ups:
- Re: wmiprvse.exe using an average 95% CPU
- From: Rob C
- Re: wmiprvse.exe using an average 95% CPU
- References:
- wmiprvse.exe using an average 95% CPU
- From: nick_oss
- Re: wmiprvse.exe using an average 95% CPU
- From: rrafiringa
- Re: wmiprvse.exe using an average 95% CPU
- From: nick_oss
- Re: wmiprvse.exe using an average 95% CPU
- From: Rob C
- wmiprvse.exe using an average 95% CPU
- Prev by Date: Re: companyweb, page cannot be displayed
- Next by Date: Re: wmiprvse.exe using an average 95% CPU
- Previous by thread: Re: wmiprvse.exe using an average 95% CPU
- Next by thread: Re: wmiprvse.exe using an average 95% CPU
- Index(es):
Relevant Pages
|
Loading