Server 2003 running in Virtual Host, Logging errors (WBEM_E_NOT_FO

[rpittman]

The cvirtual Server is logging errors (WBEM_E_NOT_FOUND) when I run WMiDiag.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>mofcomp
c:\windows\system32\wbem\wmi.mof
Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959
Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
Parsing MOF file: c:\windows\system32\wbem\wmi.mof
MOF file has been successfully parsed
Storing data in the repository...
An error occurred while opening the namespace for object 1 defined on lines
14 - 17:
0X80041002 Class, instance, or property '' was not found.
Compiler returned error 0x80041002
C:\Documents and Settings\Administrator>wmic path "Win32_Process" get Name
Please wait while WMIC is being installed.
Parsing Mof File: C:\WINDOWS\system32\wbem\Cli.mof(Phase Error - 3)
Compiler returned error 0x80041002

C:\Documents and Settings\Administrator>

Can't clear this error and get this error cleared:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1090
Date: 4/14/2008
Time: 4:42:04 PM
User: NT AUTHORITY\SYSTEM
Computer: RUSS-ENTSRVR02
Description:
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.

The following is what WMIDiag is reporting:

..1517 15:49:36 (0) ** 7 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object
cannot be found
..1518 15:49:36 (0) ** => This error is typically a WMI error. This WMI error
is due to:
..1519 15:49:36 (0) ** - a missing WMI class definition or object.
..1520 15:49:36 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET
VALUE operation failures).
..1521 15:49:36 (0) ** You can correct the missing class definitions by:
..1522 15:49:36 (0) ** - Manually recompiling the MOF file(s) with the
'MOFCOMP <FileName.MOF>' command.
..1523 15:49:36 (0) ** Note: You can build a list of classes in relation
with their WMI provider and MOF file with WMIDiag.
..1524 15:49:36 (0) ** (This list can be built on a similar and
working WMI Windows installation)
..1525 15:49:36 (0) ** The following command line must be used:
..1526 15:49:36 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
..1527 15:49:36 (0) ** - a WMI repository corruption.
..1528 15:49:36 (0) ** In such a case, you must rerun WMIDiag with
'WriteInRepository' parameter
..1529 15:49:36 (0) ** to validate the WMI repository operations.
..1530 15:49:36 (0) ** Note: ENSURE you are an administrator with FULL
access to WMI EVERY namespaces of the computer before
..1531 15:49:36 (0) ** executing the WriteInRepository command. To
write temporary data from the Root namespace, use:
..1532 15:49:36 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
..1533 15:49:36 (0) ** - If the WriteInRepository command fails, while
being an Administrator with ALL accesses to ALL namespaces
..1534 15:49:36 (0) ** the WMI repository must be reconstructed.
..1535 15:49:36 (0) ** Note: The WMI repository reconstruction requires to
locate all MOF files needed to rebuild the repository,
..1536 15:49:36 (0) ** otherwise some applications may fail after
the reconstruction.
..1537 15:49:36 (0) ** This can be achieved with the following
command:
..1538 15:49:36 (0) ** i.e. 'WMIDiag ShowMOFErrors'
..1539 15:49:36 (0) ** Note: The repository reconstruction must be a LAST
RESORT solution and ONLY after executing
..1540 15:49:36 (0) ** ALL fixes previously mentioned.
..1541 15:49:36 (2) !! WARNING: Static information stored by external
applications in the repository will be LOST! (i.e. SMS Inventory)
..1542 15:49:36 (0) **

I have tried everything I can think of, suggestions would be helpful?