wmiprvse.exe and Trigger Scan

[patrickleemart1]

I've noticed that some of my machines don't respond to a 'Trigger Scan' command, but when I go and end task on the existing wmiprvse.exe process (with NETWORK SERVICE username) that the command will work? I know that other items are run under this process name, but any clue as to why this scenario happens?

[Hemoco]

It could be that the WMI process is deadlocked by a wmi query, or a long running wmi process could be taking place.
If the problem continues you can rebuild WMI using point 6 on this page : http://www.lansweeper.com/kb/accessdenied.aspx