WMI Madness

I'm working in a Server 2003 Standard machine the locks up and stops responding. A reboot is a temporary fix. In the Event Log I found this event every five minutes.

Event 1090
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy.

I found this page:

http://www.eventid.net/display.asp?e...serenv&phase=1

The first two things didn't work and the third thing is this:

"I use this whenever I have this error and it works better than deleting and refreshing the repository:
cd /d %windir%\system32.
regsvr32 /n /I userenv.dll.
cd wbem.
mofcomp scersop.mof.
gpupdate /force

When I try it I get:

Error # 0x80040154 Class not registered.

This error also appears in the WMI log that is created when I run WMIDIAG.

What is going on here?

Can anyone point me in some direction?

Quote:

---

Originally Posted by jimmm33

I'm working in a Server 2003 Standard machine the locks up and stops responding. A reboot is a temporary fix. In the Event Log I found this event every five minutes.

Event 1090
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy.

---

First off I would ignore the error message entirely at this point, as it is unlikely to be related to your problem.

Second off we need to find out why the system is freezing up. If there is no entry in the Event Log that directly corresponds to the loss of the server then we need to consider hardware problems. Bad memory, bad CPU, bad cooling fan somewhere in the unit, bad power going to the unit, or any failing or failed hardware component.