WMI Config Error Installing SQL2K5 Standard Edition


E

Eric

I am dealing with a WMI error that completely prevents me from
installing SQL 2005 on my system.

Almost as soon as I start to install SQL 2005 on my Windows XP Pro
Version 2002 Service Pack 2 machine at work it pops up a dialog with
one of the following 2 error messages (they alternate randomly):

The SQL Server System Configuration Checker cannot be executed due to
WMI configuration on the machine PCF092191 Error:2147500034
(0x80004002).

The SQL Server System Configuration Checker cannot be executed due to
WMI configuration on the machine PCF092191 Error:2147749907
(0x80041013).

After clicking OK the installation just closes.

I also discovered when I load wmimgmt.msc and click Properties on the
WMI Control, I get the following errors on the General tab, AND it
does not allow me to click on any other tabs:

Failed to initialize all required WMI classes.
Win32_Processor: <Null>: No such interface supported
Win32_WMISetting: Successful
Security information: Successful
Win32_OperatingSystem: <Null>: No such interface supported

I have been searching online for days and tried doing virtually
everything I found that I could understand and nothing works.
Reinstalling WMI off the XP CD doesn't work, rebuilding the WMI
repository doesn't work, registering all the WMI DLLs and MOF files
doesn't work, running all the various scripts to fix WMI that are
posted all over online doesn't work.

I downloaded the Microsoft WMI Diagnostics tool and ran it. It printed
a ton of errors in a 466-line report that I can't make head or tail
of. 6 here, 33 there, 27 over there...almost too many to count. The
suggestions it gives to fix them range from vague and incomplete to
incomprehensible. I'll paste those error results into a followup post.

I installed the WMI Tools package and can't figure out what to do with
any of the tools at all. The only thing I noticed is that when
examining a section under Win32_Processor, most entries for various
properties are marked <empty>, while I have seen people discussing
what I think are those same properties online and talking about seeing
stuff typed into theirs (such as the HostingModel having
LocalServiceHost typed in and ImpersonationLevel having 1 typed in).
But there are so many properties and I'm not sure what should be typed
into all of them or if I'm even looking in the right place.

I've seen some suggestions in WMI documentation that not all WMI
errors may be related to WMI itself at all, which I think might be the
case here, but I don't know. Some material said DCOM may be the
problem, but I didn't have much luck figuring out how to fix that
either. From the WMI Diagnostics it looks like there may be multiple
errors of different kinds, but if it's that bad, I don't know how my
computer's been working at all.

I've been using this computer for 9 months and had no major problems
with it, although I did have a problem installing Microsoft Windows
Genuine Advantage Notification, for which Microsoft sent me a script
that fixed it. One other person here at work is suffering from this
same WMI error, but most people have been able to install SQL 2005
here with no problem.

My boss does not want me to just do a full XP reinstall. He wants me
to identify the specific problem and fix it. If this was my home
computer I wouldn't spend so much time banging my head over this
incomprehensible problem. But a full reinstall is not really an option
for me in this case, unless maybe Microsoft says that's the only way
to fix it.

I am available to deal with this issue during 9 to 5 eastern time
Monday to Friday.

Thanks in advance for any help...
Eric
 
Ad

Advertisements

E

Eric

Below is the error report from the WMI Diagnostics tool. By the way I
did re-register OLE32.DLL and OLEAUT32.DLL as it suggests to fix the
DCOM error, but of course it didn't fix my original problem nor it did
stop the same message from appearing in this report when I run it
again:

16669 15:07:36 (0) ** WMIDiag v2.0 started on Friday, June 01, 2007 at
15:03.
16670 15:07:36 (0) **
16671 15:07:36 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
16672 15:07:36 (0) **
16673 15:07:36 (0) ** This script is not supported under any Microsoft
standard support program or service.
16674 15:07:36 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
16675 15:07:36 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
16676 15:07:36 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
16677 15:07:36 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
16678 15:07:36 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
16679 15:07:36 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
16680 15:07:36 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
16681 15:07:36 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
16682 15:07:36 (0) ** of the possibility of such damages.
16683 15:07:36 (0) **
16684 15:07:36 (0) **
16685 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16686 15:07:36 (0) **
----------------------------------------------------- WMI REPORT:
BEGIN ----------------------------------------------------------
16687 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16688 15:07:36 (0) **
16689 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16690 15:07:36 (0) ** Windows XP - Service pack 2 - 32-bit (2600) -
User 'COMPANY\EBSMITH' on computer 'PCF093920'.
16691 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16692 15:07:36 (0) **
Environment: ........................................................................................................
OK..
16693 15:07:36 (0) ** There are no missing WMI system
files: ..............................................................................
OK.
16694 15:07:36 (0) ** There are no missing WMI repository
files: ..........................................................................
OK.
16695 15:07:36 (0) ** WMI repository
state: ...............................................................................................
NOT TESTED.
16696 15:07:36 (0) ** BEFORE running WMIDiag:
16697 15:07:36 (0) ** The WMI repository has a size
of: ...................................................................................
26 MB.
16698 15:07:36 (0) ** - Disk free space on
'C:': ..........................................................................................
60108 MB.
16699 15:07:36 (0) ** - INDEX.BTR, 1245184 bytes, 6/1/2007 11:38:33 AM
16700 15:07:36 (0) ** - INDEX.MAP, 632 bytes, 6/1/2007 2:56:45 PM
16701 15:07:36 (0) ** - MAPPING.VER, 4 bytes, 6/1/2007 2:56:45 PM
16702 15:07:36 (0) ** - MAPPING1.MAP, 13584 bytes, 6/1/2007 2:56:45 PM
16703 15:07:36 (0) ** - MAPPING2.MAP, 13584 bytes, 6/1/2007 2:40:45 PM
16704 15:07:36 (0) ** - OBJECTS.DATA, 26476544 bytes, 6/1/2007 2:40:45
PM
16705 15:07:36 (0) ** - OBJECTS.MAP, 12952 bytes, 6/1/2007 2:56:45 PM
16706 15:07:36 (0) ** AFTER running WMIDiag:
16707 15:07:36 (0) ** The WMI repository has a size
of: ...................................................................................
26 MB.
16708 15:07:36 (0) ** - Disk free space on
'C:': ..........................................................................................
60106 MB.
16709 15:07:36 (0) ** - INDEX.BTR, 1245184 bytes, 6/1/2007 11:38:33 AM
16710 15:07:36 (0) ** - INDEX.MAP, 632 bytes, 6/1/2007 2:56:45 PM
16711 15:07:36 (0) ** - MAPPING.VER, 4 bytes, 6/1/2007 2:56:45 PM
16712 15:07:36 (0) ** - MAPPING1.MAP, 13584 bytes, 6/1/2007 2:56:45 PM
16713 15:07:36 (0) ** - MAPPING2.MAP, 13584 bytes, 6/1/2007 2:40:45 PM
16714 15:07:36 (0) ** - OBJECTS.DATA, 26476544 bytes, 6/1/2007 2:40:45
PM
16715 15:07:36 (0) ** - OBJECTS.MAP, 12952 bytes, 6/1/2007 2:56:45 PM
16716 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16717 15:07:36 (0) ** INFO: Windows Firewall
status: ......................................................................................
ENABLED.
16718 15:07:36 (0) ** Windows Firewall
Profile: ...........................................................................................
DOMAIN.
16719 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16720 15:07:36 (0) ** DCOM
Status: ........................................................................................................
OK.
16721 15:07:36 (0) ** WMI registry
setup: .................................................................................................
OK.
16722 15:07:36 (0) ** INFO: WMI service has
dependents: ...................................................................................
2 SERVICE(S)!
16723 15:07:36 (0) ** - Security Center (WSCSVC,
StartMode='Automatic')
16724 15:07:36 (0) ** - Windows Firewall/Internet Connection Sharing
(ICS) (SHAREDACCESS, StartMode='Automatic')
16725 15:07:36 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
16726 15:07:36 (0) ** Note: If the service is marked with (*), it
means that the service/application uses WMI but
16727 15:07:36 (0) ** there is no hard dependency on WMI. However, if
the WMI service is stopped,
16728 15:07:36 (0) ** this can prevent the service/application to work
as expected.
16729 15:07:36 (0) **
16730 15:07:36 (0) ** RPCSS
service: ......................................................................................................
OK (Already started).
16731 15:07:36 (0) ** WINMGMT
service: ....................................................................................................
OK (Already started).
16732 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16733 15:07:36 (0) ** WMI service DCOM
setup: .............................................................................................
OK.
16734 15:07:36 (0) ** WMI components DCOM
registrations: ..................................................................................
OK.
16735 15:07:36 (0) ** WMI ProgID
registrations: ...........................................................................................
OK.
16736 15:07:36 (0) ** WMI provider DCOM
registrations: ....................................................................................
OK.
16737 15:07:36 (0) ** WMI provider CIM
registrations: .....................................................................................
OK.
16738 15:07:36 (0) ** WMI provider
CLSIDs: ................................................................................................
OK.
16739 15:07:36 (0) ** WMI providers EXE/DLL
availability: .................................................................................
OK.
16740 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16741 15:07:36 (0) ** WMI namespace security for 'ROOT/
RSOP': .............................................................................
MODIFIED.
16742 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
16743 15:07:36 (0) ** - REMOVED ACE:
16744 15:07:36 (0) ** ACEType: &h0
16745 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16746 15:07:36 (0) ** ACEFlags: &h12
16747 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16748 15:07:36 (0) ** INHERITED_ACE
16749 15:07:36 (0) ** ACEMask: &h6003F
16750 15:07:36 (0) ** WBEM_ENABLE
16751 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16752 15:07:36 (0) ** WBEM_FULL_WRITE_REP
16753 15:07:36 (0) ** WBEM_PARTIAL_WRITE_REP
16754 15:07:36 (0) ** WBEM_WRITE_PROVIDER
16755 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16756 15:07:36 (0) ** WBEM_WRITE_DAC
16757 15:07:36 (0) ** WBEM_READ_CONTROL
16758 15:07:36 (0) **
16759 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16760 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16761 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16762 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16763 15:07:36 (0) **
16764 15:07:36 (0) ** WMI namespace security for 'ROOT/
RSOP': .............................................................................
MODIFIED.
16765 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
16766 15:07:36 (0) ** - REMOVED ACE:
16767 15:07:36 (0) ** ACEType: &h0
16768 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16769 15:07:36 (0) ** ACEFlags: &h12
16770 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16771 15:07:36 (0) ** INHERITED_ACE
16772 15:07:36 (0) ** ACEMask: &h20023
16773 15:07:36 (0) ** WBEM_ENABLE
16774 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16775 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16776 15:07:36 (0) ** WBEM_READ_CONTROL
16777 15:07:36 (0) **
16778 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16779 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16780 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16781 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16782 15:07:36 (0) **
16783 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
USER': ........................................................................
MODIFIED.
16784 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
16785 15:07:36 (0) ** - REMOVED ACE:
16786 15:07:36 (0) ** ACEType: &h0
16787 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16788 15:07:36 (0) ** ACEFlags: &h12
16789 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16790 15:07:36 (0) ** INHERITED_ACE
16791 15:07:36 (0) ** ACEMask: &h6003F
16792 15:07:36 (0) ** WBEM_ENABLE
16793 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16794 15:07:36 (0) ** WBEM_FULL_WRITE_REP
16795 15:07:36 (0) ** WBEM_PARTIAL_WRITE_REP
16796 15:07:36 (0) ** WBEM_WRITE_PROVIDER
16797 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16798 15:07:36 (0) ** WBEM_WRITE_DAC
16799 15:07:36 (0) ** WBEM_READ_CONTROL
16800 15:07:36 (0) **
16801 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16802 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16803 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16804 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16805 15:07:36 (0) **
16806 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
USER': ........................................................................
MODIFIED.
16807 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
16808 15:07:36 (0) ** - REMOVED ACE:
16809 15:07:36 (0) ** ACEType: &h0
16810 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16811 15:07:36 (0) ** ACEFlags: &h12
16812 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16813 15:07:36 (0) ** INHERITED_ACE
16814 15:07:36 (0) ** ACEMask: &h20023
16815 15:07:36 (0) ** WBEM_ENABLE
16816 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16817 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16818 15:07:36 (0) ** WBEM_READ_CONTROL
16819 15:07:36 (0) **
16820 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16821 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16822 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16823 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16824 15:07:36 (0) **
16825 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
COMPUTER': ....................................................................
MODIFIED.
16826 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
16827 15:07:36 (0) ** - REMOVED ACE:
16828 15:07:36 (0) ** ACEType: &h0
16829 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16830 15:07:36 (0) ** ACEFlags: &h12
16831 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16832 15:07:36 (0) ** INHERITED_ACE
16833 15:07:36 (0) ** ACEMask: &h6003F
16834 15:07:36 (0) ** WBEM_ENABLE
16835 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16836 15:07:36 (0) ** WBEM_FULL_WRITE_REP
16837 15:07:36 (0) ** WBEM_PARTIAL_WRITE_REP
16838 15:07:36 (0) ** WBEM_WRITE_PROVIDER
16839 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16840 15:07:36 (0) ** WBEM_WRITE_DAC
16841 15:07:36 (0) ** WBEM_READ_CONTROL
16842 15:07:36 (0) **
16843 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16844 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16845 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16846 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16847 15:07:36 (0) **
16848 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
COMPUTER': ....................................................................
MODIFIED.
16849 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
16850 15:07:36 (0) ** - REMOVED ACE:
16851 15:07:36 (0) ** ACEType: &h0
16852 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16853 15:07:36 (0) ** ACEFlags: &h12
16854 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16855 15:07:36 (0) ** INHERITED_ACE
16856 15:07:36 (0) ** ACEMask: &h20023
16857 15:07:36 (0) ** WBEM_ENABLE
16858 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16859 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16860 15:07:36 (0) ** WBEM_READ_CONTROL
16861 15:07:36 (0) **
16862 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16863 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16864 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16865 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16866 15:07:36 (0) **
16867 15:07:36 (0) **
16868 15:07:36 (0) ** DCOM security warning(s)
detected: ..................................................................................
0.
16869 15:07:36 (0) ** DCOM security error(s)
detected: ....................................................................................
0.
16870 15:07:36 (0) ** WMI security warning(s)
detected: ...................................................................................
0.
16871 15:07:36 (0) ** WMI security error(s)
detected: .....................................................................................
6.
16872 15:07:36 (0) **
16873 15:07:36 (0) ** Overall DCOM security
status: .......................................................................................
OK.
16874 15:07:36 (1) !! ERROR: Overall WMI security
status: .................................................................................
ERROR!
16875 15:07:36 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------------------------------------
16876 15:07:36 (0) ** INFO: WMI permanent
SUBSCRIPTION(S): ................................................................................
3.
16877 15:07:36 (0) ** - ROOT/DEFAULT,
MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario
Control".
16878 15:07:36 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE
TargetInstance ISA 'MSFT_UCScenario''
16879 15:07:36 (0) ** - ROOT/SUBSCRIPTION,
MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario
Control".
16880 15:07:36 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE
TargetInstance ISA 'MSFT_UCScenario''
16881 15:07:36 (0) ** - ROOT/SUBSCRIPTION,
NTEventLogEventConsumer.Name="SCM Event Log Consumer".
16882 15:07:36 (0) ** 'select * from MSFT_SCMEventLogEvent'
16883 15:07:36 (0) **
16884 15:07:36 (0) ** WMI TIMER
instruction(s): ...........................................................................................
NONE.
16885 15:07:36 (0) ** WMI ADAP
status: ....................................................................................................
OK.
16886 15:07:36 (0) ** INFO: WMI namespace(s) requiring PACKET
PRIVACY: ....................................................................
1 NAMESPACE(S)!
16887 15:07:36 (0) ** - ROOT/SERVICEMODEL.
16888 15:07:36 (0) ** => When remotely connecting, the namespace(s)
listed require(s) the WMI client to
16889 15:07:36 (0) ** use an encrypted connection by specifying the
PACKET PRIVACY authentication level.
16890 15:07:36 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy
flags)
16891 15:07:36 (0) ** i.e. 'WMIC.EXE /NODE:"PCF093920" /AUTHLEVEL:
Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
16892 15:07:36 (0) **
16893 15:07:36 (0) ** WMI MONIKER
CONNECTIONS: ............................................................................................
OK.
16894 15:07:36 (0) ** WMI
CONNECTIONS: ....................................................................................................
OK.
16895 15:07:36 (1) !! ERROR: WMI GET operation errors
reported: ...........................................................................
6 ERROR(S)!
16896 15:07:36 (0) ** - Root/CIMv2, Win32_Process.Handle=1056,
0x80004002 - No such interface supported.
16897 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16898 15:07:36 (0) ** - Root/CIMv2, Win32_Process.Handle=1056,
0x80004002 - No such interface supported.
16899 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16900 15:07:36 (0) ** - Root/CIMv2, Win32_Process.Handle=1056,
0x80004002 - No such interface supported.
16901 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16902 15:07:36 (0) ** - Root/CIMv2, Win32_Process.Handle=1056,
0x80004002 - No such interface supported.
16903 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16904 15:07:36 (0) ** - Root/CIMv2, Win32_Process.Handle=3868,
0x80004002 - No such interface supported.
16905 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16906 15:07:36 (0) ** - Root/CIMv2, Win32_Process.Handle=3868,
0x80004002 - No such interface supported.
16907 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16908 15:07:36 (0) **
16909 15:07:36 (0) ** WMI MOF
representations: ............................................................................................
OK.
16910 15:07:36 (0) ** WMI QUALIFIER access
operations: ....................................................................................
OK.
16911 15:07:36 (1) !! ERROR: WMI ENUMERATION operation errors
reported: ...................................................................
32 ERROR(S)!
16912 15:07:36 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBDevice',
0x80004002 - .
16913 15:07:36 (0) ** MOF Registration: 'WMI information not available
(This could be the case for an external application or a third party
WMI provider)'
16914 15:07:36 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBHub',
0x80004002 - .
16915 15:07:36 (0) ** MOF Registration: 'WMI information not available
(This could be the case for an external application or a third party
WMI provider)'
16916 15:07:36 (0) ** - Root/Default, InstancesOf, 'SystemRestore',
0x80004002 - No such interface supported.
16917 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\SR.MOF'
16918 15:07:36 (0) ** - Root/CIMv2, InstancesOf, 'Win32_Process',
0x80004002 - No such interface supported.
16919 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16920 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_OperatingSystem', 0x80004002 - No such interface supported.
16921 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16922 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_ComputerSystem', 0x80004002 - No such interface supported.
16923 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16924 15:07:36 (0) ** - Root/CIMv2, InstancesOf, 'Win32_Service',
0x80004002 - No such interface supported.
16925 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16926 15:07:36 (0) ** - Root/CIMv2, InstancesOf, 'Win32_Bios',
0x80004002 - No such interface supported.
16927 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'
16928 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_Tcpip_IP', 0x80004002 - No such interface
supported.
16929 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16930 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_Tcpip_TCP', 0x80004002 - No such interface
supported.
16931 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16932 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_Tcpip_UDP', 0x80004002 - No such interface
supported.
16933 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16934 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_Tcpip_ICMP', 0x80004002 - No such interface
supported.
16935 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16936 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfOS_Cache', 0x80004002 - No such interface
supported.
16937 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16938 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfOS_Memory', 0x80004002 - No such interface
supported.
16939 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16940 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfOS_Objects', 0x80004002 - No such interface
supported.
16941 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16942 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfOS_PagingFile', 0x80004002 - No such interface
supported.
16943 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16944 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfOS_Processor', 0x80004002 - No such interface
supported.
16945 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16946 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfOS_System', 0x80004002 - No such interface
supported.
16947 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16948 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfProc_Process', 0x80004002 - No such interface
supported.
16949 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16950 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfRawData_PerfProc_Thread', 0x80004002 - No such interface
supported.
16951 15:07:36 (0) ** MOF Registration: 'No located MOF file
(exception)'
16952 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_Tcpip_IP', 0x80004002 - No such interface
supported.
16953 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16954 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_Tcpip_TCP', 0x80004002 - No such interface
supported.
16955 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16956 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_Tcpip_UDP', 0x80004002 - No such interface
supported.
16957 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16958 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_Tcpip_ICMP', 0x80004002 - No such interface
supported.
16959 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16960 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfOS_Cache', 0x80004002 - No such interface
supported.
16961 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16962 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfOS_Memory', 0x80004002 - No such
interface supported.
16963 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16964 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfOS_Objects', 0x80004002 - No such
interface supported.
16965 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16966 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfOS_PagingFile', 0x80004002 - No such
interface supported.
16967 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16968 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfOS_Processor', 0x80004002 - No such
interface supported.
16969 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16970 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfOS_System', 0x80004002 - No such
interface supported.
16971 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16972 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfProc_Process', 0x80004002 - No such
interface supported.
16973 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16974 15:07:36 (0) ** - Root/CIMv2, InstancesOf,
'Win32_PerfFormattedData_PerfProc_Thread', 0x80004002 - No such
interface supported.
16975 15:07:36 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMI.MOF'
16976 15:07:36 (0) **
16977 15:07:36 (1) !! ERROR: WMI EXECQUERY operation errors
reported: .....................................................................
17 ERROR(S)!
16978 15:07:36 (0) ** - Root/Default, SELECT * FROM SystemRestore,
0x80004002 - No such interface supported.
16979 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_LogicalDisk
WHERE FreeSpace > 10000000 AND DriveType = 3, 0x80004002 - No such
interface supported.
16980 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_PageFileUsage,
0x80004002 - No such interface supported.
16981 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_BIOS WHERE
Version IS NOT NULL, 0x80004002 - No such interface supported.
16982 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_NetworkAdapter
WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network
(WAN)" AND Description != "Packet Scheduler Miniport", 0x80004002 - No
such interface supported.
16983 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_Processor
WHERE Name IS NOT NULL, 0x80004002 - No such interface supported.
16984 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_DiskDrive,
0x80004002 - No such interface supported.
16985 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM
Win32_ComputerSystem, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM
cannot locate a provider referenced in the schema.
16986 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_DiskPartition,
0x80004002 - No such interface supported.
16987 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_LogicalDisk
WHERE Description != "Network Connection", 0x80041013 -
(WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced
in the schema.
16988 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_SoundDevice,
0x80004002 - No such interface supported.
16989 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM
Win32_VideoController, 0x80004002 - No such interface supported.
16990 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_USBController,
0x80004002 - No such interface supported.
16991 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM
Win32_DesktopMonitor, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM
cannot locate a provider referenced in the schema.
16992 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_PointingDevice
WHERE Status = "OK", 0x80004002 - No such interface supported.
16993 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_Keyboard,
0x80004002 - No such interface supported.
16994 15:07:36 (0) ** - Root/CIMv2, SELECT * FROM Win32_SystemDriver
WHERE StartMode != "Disabled", 0x80004002 - No such interface
supported.
16995 15:07:36 (0) **
16996 15:07:36 (0) ** WMI GET VALUE
operations: ...........................................................................................
OK.
16997 15:07:36 (0) ** WMI WRITE
operations: ...............................................................................................
NOT TESTED.
16998 15:07:36 (0) ** WMI PUT
operations: .................................................................................................
NOT TESTED.
16999 15:07:36 (0) ** WMI DELETE
operations: ..............................................................................................
NOT TESTED.
17000 15:07:36 (0) ** WMI static instances
retrieved: .....................................................................................
691.
17001 15:07:36 (0) ** WMI dynamic instances
retrieved: ....................................................................................
0.
17002 15:07:36 (0) ** WMI instance request cancellations (to limit
performance
impact): ................................................... 0.
17003 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17004 15:07:36 (0) ** # of Event Log events BEFORE WMIDiag execution
since the last 20 day(s):
17005 15:07:36 (0) **
DCOM: .............................................................................................................
ERROR!
17006 15:07:36 (0) **
WINMGMT: ..........................................................................................................
ERROR!
17007 15:07:36 (0) **
WMIADAPTER: .......................................................................................................
ERROR!
17008 15:07:36 (0) **
17009 15:07:36 (0) ** # of additional Event Log events AFTER WMIDiag
execution:
17010 15:07:36 (0) **
DCOM: .............................................................................................................
ERROR!
17011 15:07:36 (0) **
WINMGMT: ..........................................................................................................
ERROR!
17012 15:07:36 (0) **
WMIADAPTER: .......................................................................................................
ERROR!
17013 15:07:36 (0) **
17014 15:07:36 (0) ** 52 error(s) 0x80004002 - (WBEM_UNKNOWN) This
error code is external to WMI.
17015 15:07:36 (0) ** => This error is not a WMI error. It is a DCOM
error due to the following reasons:
17016 15:07:36 (0) ** - An application has changed the COM/DCOM
settings of OLE32.DLL and/or OLEAUT32.DLL.
17017 15:07:36 (0) ** - The registry settings of COM/DCOM has been
damage or wrongly modified.
17018 15:07:36 (0) ** => To correct this situation, you must re-
register the original COM/DCOM DLLs with REGSVR32.EXE
17019 15:07:36 (0) ** i.e. 'REGSVR32.EXE OLE32.DLL'
17020 15:07:36 (0) ** i.e. 'REGSVR32.EXE OLEAUT32.DLL'
17021 15:07:36 (0) **
17022 15:07:36 (0) **
17023 15:07:36 (0) ** 3 error(s) 0x80041013 -
(WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced
in the schema
17024 15:07:36 (0) ** => This error is typically due to the following
major reasons:
17025 15:07:36 (0) ** - The application queried by the WMI provider is
not installed, not available or not running
17026 15:07:36 (0) ** at the time of the request was made. This error
can also be generated because
17027 15:07:36 (0) ** the application supporting the providers has
been uninstalled.
17028 15:07:36 (0) ** - Some WMI providers (i.e. RSOP Planning Mode,
Exchange 2003) are implemented as a WMI service.
17029 15:07:36 (0) ** Make sure the required services are successfully
started.
17030 15:07:36 (0) ** - The WMI provider binary files are not
accessible (i.e. access denied ACL).
17031 15:07:36 (0) ** - A WMI provider registration problem at the CIM
level (MOFCOMP.EXE) or at the COM level (REGSVR32.EXE).
17032 15:07:36 (0) ** You must re-register the WMI provider by
recompiling its associated MOF file with MOFCOMP.EXE
17033 15:07:36 (0) ** Note: - If the WMI provider DLL CIM and COM
registrations are correct, this error can
17034 15:07:36 (0) ** be returned because the provider has a
dependency on another DLL that cannot be
17035 15:07:36 (0) ** loaded (missing or bad DLL)
17036 15:07:36 (0) ** - Dependencies can be found with the DEPENDS.EXE
tool coming with the
17037 15:07:36 (0) ** Windows XP and Windows 2003 Support Tools. The
command line is as follows:
17038 15:07:36 (0) ** i.e. DEPENDS.EXE <PATH><Provider.DLL>
17039 15:07:36 (0) ** => When a WMI provider fails to load, it is
possible to trace the provider load process by
17040 15:07:36 (0) ** submitting, via WBEMTEST and asynchronously, the
following WMI event query:
17041 15:07:36 (0) ** 'Select * From MSFT_WmiSelfEvent'
17042 15:07:36 (0) ** Then you can trace the following WMI events:
17043 15:07:36 (0) ** - Msft_WmiProvider_ComServerLoadOperationEvent
17044 15:07:36 (0) ** - Msft_WmiProvider_InitializationOperationEvent
17045 15:07:36 (0) ** - Msft_WmiProvider_LoadOperationEvent
17046 15:07:36 (0) ** and depending on the WMI operation executed, you
can trace the following WMI events:
17047 15:07:36 (0) ** i.e. for an enumeration:
17048 15:07:36 (0) ** -
Msft_WmiProvider_CreateInstanceEnumAsyncEvent_Pre and
Msft_WmiProvider_CreateInstanceEnumAsyncEvent_Post
17049 15:07:36 (0) ** i.e. for a put operation:
17050 15:07:36 (0) ** - Msft_WmiProvider_PutInstanceAsyncEvent_Pre and
Msft_WmiProvider_PutInstanceAsyncEvent_Post
17051 15:07:36 (0) **
17052 15:07:36 (0) ** => If the software has been de-installed
intentionally, then this information must be
17053 15:07:36 (0) ** removed from the WMI repository. You can use the
'WMIC.EXE' command to remove the provider
17054 15:07:36 (0) ** registration data and its set of associated
classes.
17055 15:07:36 (0) ** => To correct this situation, you can:
17056 15:07:36 (0) ** - Install or start the application supporting
these providers.
17057 15:07:36 (0) ** - Register the providers in CIM (MOFCOMP) or
DCOM (REGSVR32).
17058 15:07:36 (0) ** Note: In this case the provider should also be
listed in the 'missing WMI
17059 15:07:36 (0) ** provider DCOM registrations' or in the 'missing
WMI provider files' section.
17060 15:07:36 (2) !! WARNING: Re-registering with REGSVR32.EXE all
DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
17061 15:07:36 (0) ** may not solve the problem as the DLL supporting
the WMI class(es)
17062 15:07:36 (0) ** can be located in a different folder.
17063 15:07:36 (0) ** You must refer to the class name to determine
the software delivering the related DLL.
17064 15:07:36 (0) **
17065 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17066 15:07:36 (0) ** WMI Registry key
setup: .............................................................................................
OK.
17067 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17068 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17069 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17070 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17071 15:07:36 (0) **
17072 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17073 15:07:36 (0) **
------------------------------------------------------ WMI REPORT: END
-----------------------------------------------------------
17074 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
17075 15:07:36 (0) **
17076 15:07:36 (0) ** ERROR: WMIDiag detected issues that could
prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\EBSMITH
\LOCAL SETTINGS\TEMP\WMIDIAG-
V2.0_XP___.CLI.SP2.32_PCF093920_2007.06.01_15.03.08.LOG' for details.
17077 15:07:36 (0) **
17078 15:07:36 (0) ** WMIDiag v2.0 ended on Friday, June 01, 2007 at
15:07 (W:76 E:91 S:1).
 
E

Eric

After much searching I found a fix posted online that got me past this
error. Someone posted on his blog that he was getting the same error
on another installation and he had called Microsoft Support about it.
Here is the link to his blog and the fix he said Microsoft gave him:

*****************************************************************************************

http://michalferber.com/index.php/page/6/

I started installing Visual Studio 2005 the other day and kept getting
this error.

"The SQL Server System Configuration Checker cannot be executed due to
WMI configuration on the machine FERBER Error:2147500034
(0×80004002)."

I searched high and low and found nothing of any value. So I called in
the experts (Microsoft Support).

It turns out that something was screwy with WMI on my machine. We did
the following after a few hours trying different things and then the
install was successful.

1. Add network service account to administrators group.
2. Add authenticated users to following registry keys:

* HKCR\CLSID\{73E709EA-5D93-4B2E-BBB0-99B7938DA9E4}
* HKCR\CLSID\{7C857801-7381-11CF-884D-00AA004B2E24}
* HKLM\Software\Microsoft\WBEM\CIMOM

*****************************************************************************************

I would also add...

To do step 1, you go to Control Panel, User Accounts, Advanced tab,
click Advanced button, and open Groups folder.

To do step 2, right click on those registry keys, click Permissions,
and add Authenticated Users. I gave them Full Control permissions,
but I'm not sure if that was necessary or not.

Lastly, I don't think this is a pure fix to the way the WMI
configuration is supposed to be. When I run the WMI diagnostics
again, most of the errors are gone, but I still get the errors related
to namespace security and default trustees being removed. And at the
bottom it still says "ERROR: WMIDiag detected issues that could
prevent WMI to work properly." My guess is these permissions changes
to the registry overrided whatever missing permissions the diagnostics
tool is looking for. Nevertheless the diagnostics tool is still
looking for the permissions in the original places and not finding
them. But since this solution came from Microsoft and it seems to
work, I'm satisfied with it.
 
G

guzarva16

Eric said:
I am dealing with a WMI error that completely prevents me from
installing SQL 2005 on my system.

Almost as soon as I start to install SQL 2005 on my Windows XP Pro
Version 2002 Service Pack 2 machine at work it pops up a dialog with
one of the following 2 error messages (they alternate randomly):

The SQL Server System Configuration Checker cannot be executed due to
WMI configuration on the machine PCF092191 Error:2147500034
(0x80004002).

The SQL Server System Configuration Checker cannot be executed due to
WMI configuration on the machine PCF092191 Error:2147749907
(0x80041013).

After clicking OK the installation just closes.

I also discovered when I load wmimgmt.msc and click Properties on the
WMI Control, I get the following errors on the General tab, AND it
does not allow me to click on any other tabs:

Failed to initialize all required WMI classes.
Win32_Processor: <Null>: No such interface supported
Win32_WMISetting: Successful
Security information: Successful
Win32_OperatingSystem: <Null>: No such interface supported

I have been searching online for days and tried doing virtually
everything I found that I could understand and nothing works.
Reinstalling WMI off the XP CD doesn't work, rebuilding the WMI
repository doesn't work, registering all the WMI DLLs and MOF files
doesn't work, running all the various scripts to fix WMI that are
posted all over online doesn't work.

I downloaded the Microsoft WMI Diagnostics tool and ran it. It printed
a ton of errors in a 466-line report that I can't make head or tail
of. 6 here, 33 there, 27 over there...almost too many to count. The
suggestions it gives to fix them range from vague and incomplete to
incomprehensible. I'll paste those error results into a followup post.

I installed the WMI Tools package and can't figure out what to do with
any of the tools at all. The only thing I noticed is that when
examining a section under Win32_Processor, most entries for various
properties are marked <empty>, while I have seen people discussing
what I think are those same properties online and talking about seeing
stuff typed into theirs (such as the HostingModel having
LocalServiceHost typed in and ImpersonationLevel having 1 typed in).
But there are so many properties and I'm not sure what should be typed
into all of them or if I'm even looking in the right place.

I've seen some suggestions in WMI documentation that not all WMI
errors may be related to WMI itself at all, which I think might be the
case here, but I don't know. Some material said DCOM may be the
problem, but I didn't have much luck figuring out how to fix that
either. From the WMI Diagnostics it looks like there may be multiple
errors of different kinds, but if it's that bad, I don't know how my
computer's been working at all.

I've been using this computer for 9 months and had no major problems
with it, although I did have a problem installing Microsoft Windows
Genuine Advantage Notification, for which Microsoft sent me a script
that fixed it. One other person here at work is suffering from this
same WMI error, but most people have been able to install SQL 2005
here with no problem.

My boss does not want me to just do a full XP reinstall. He wants me
to identify the specific problem and fix it. If this was my home
computer I wouldn't spend so much time banging my head over this
incomprehensible problem. But a full reinstall is not really an option
for me in this case, unless maybe Microsoft says that's the only way
to fix it.

I am available to deal with this issue during 9 to 5 eastern time
Monday to Friday.

Thanks in advance for any help...
Eric
 
G

guzarva16

Eric said:
After much searching I found a fix posted online that got me past this
error. Someone posted on his blog that he was getting the same error
on another installation and he had called Microsoft Support about it.
Here is the link to his blog and the fix he said Microsoft gave him:

*****************************************************************************************

http://michalferber.com/index.php/page/6/

I started installing Visual Studio 2005 the other day and kept getting
this error.

"The SQL Server System Configuration Checker cannot be executed due to
WMI configuration on the machine FERBER Error:2147500034
(0W80004002)."

I searched high and low and found nothing of any value. So I called in
the experts (Microsoft Support).

It turns out that something was screwy with WMI on my machine. We did
the following after a few hours trying different things and then the
install was successful.

1. Add network service account to administrators group.
2. Add authenticated users to following registry keys:

* HKCR\CLSID\{73E709EA-5D93-4B2E-BBB0-99B7938DA9E4}
* HKCR\CLSID\{7C857801-7381-11CF-884D-00AA004B2E24}
* HKLM\Software\Microsoft\WBEM\CIMOM

*****************************************************************************************

I would also add...

To do step 1, you go to Control Panel, User Accounts, Advanced tab,
click Advanced button, and open Groups folder.

To do step 2, right click on those registry keys, click Permissions,
and add Authenticated Users. I gave them Full Control permissions,
but I'm not sure if that was necessary or not.

Lastly, I don't think this is a pure fix to the way the WMI
configuration is supposed to be. When I run the WMI diagnostics
again, most of the errors are gone, but I still get the errors related
to namespace security and default trustees being removed. And at the
bottom it still says "ERROR: WMIDiag detected issues that could
prevent WMI to work properly." My guess is these permissions changes
to the registry overrided whatever missing permissions the diagnostics
tool is looking for. Nevertheless the diagnostics tool is still
looking for the permissions in the original places and not finding
them. But since this solution came from Microsoft and it seems to
work, I'm satisfied with it.
 
Ad

Advertisements

G

guzarva16

Eric said:
Below is the error report from the WMI Diagnostics tool. By the way I
did re-register OLE32.DLL and OLEAUT32.DLL as it suggests to fix the
DCOM error, but of course it didn't fix my original problem nor it did
stop the same message from appearing in this report when I run it
again:

16669 15:07:36 (0) ** WMIDiag v2.0 started on Friday, June 01, 2007 at
15:03.
16670 15:07:36 (0) **
16671 15:07:36 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
16672 15:07:36 (0) **
16673 15:07:36 (0) ** This script is not supported under any Microsoft
standard support program or service.
16674 15:07:36 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
16675 15:07:36 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
16676 15:07:36 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
16677 15:07:36 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
16678 15:07:36 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
16679 15:07:36 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
16680 15:07:36 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
16681 15:07:36 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
16682 15:07:36 (0) ** of the possibility of such damages.
16683 15:07:36 (0) **
16684 15:07:36 (0) **
16685 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16686 15:07:36 (0) **
----------------------------------------------------- WMI REPORT:
BEGIN ----------------------------------------------------------
16687 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16688 15:07:36 (0) **
16689 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16690 15:07:36 (0) ** Windows XP - Service pack 2 - 32-bit (2600) -
User 'COMPANY\EBSMITH' on computer 'PCF093920'.
16691 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16692 15:07:36 (0) **
Environment: ........................................................................................................
OK..
16693 15:07:36 (0) ** There are no missing WMI system
files: ..............................................................................
OK.
16694 15:07:36 (0) ** There are no missing WMI repository
files: ..........................................................................
OK.
16695 15:07:36 (0) ** WMI repository
state: ...............................................................................................
NOT TESTED.
16696 15:07:36 (0) ** BEFORE running WMIDiag:
16697 15:07:36 (0) ** The WMI repository has a size
of: ...................................................................................
26 MB.
16698 15:07:36 (0) ** - Disk free space on
'C:': ..........................................................................................
60108 MB.
16699 15:07:36 (0) ** - INDEX.BTR, 1245184 bytes, 6/1/2007 11:38:33 AM
16700 15:07:36 (0) ** - INDEX.MAP, 632 bytes, 6/1/2007 2:56:45 PM
16701 15:07:36 (0) ** - MAPPING.VER, 4 bytes, 6/1/2007 2:56:45 PM
16702 15:07:36 (0) ** - MAPPING1.MAP, 13584 bytes, 6/1/2007 2:56:45 PM
16703 15:07:36 (0) ** - MAPPING2.MAP, 13584 bytes, 6/1/2007 2:40:45 PM
16704 15:07:36 (0) ** - OBJECTS.DATA, 26476544 bytes, 6/1/2007 2:40:45
PM
16705 15:07:36 (0) ** - OBJECTS.MAP, 12952 bytes, 6/1/2007 2:56:45 PM
16706 15:07:36 (0) ** AFTER running WMIDiag:
16707 15:07:36 (0) ** The WMI repository has a size
of: ...................................................................................
26 MB.
16708 15:07:36 (0) ** - Disk free space on
'C:': ..........................................................................................
60106 MB.
16709 15:07:36 (0) ** - INDEX.BTR, 1245184 bytes, 6/1/2007 11:38:33 AM
16710 15:07:36 (0) ** - INDEX.MAP, 632 bytes, 6/1/2007 2:56:45 PM
16711 15:07:36 (0) ** - MAPPING.VER, 4 bytes, 6/1/2007 2:56:45 PM
16712 15:07:36 (0) ** - MAPPING1.MAP, 13584 bytes, 6/1/2007 2:56:45 PM
16713 15:07:36 (0) ** - MAPPING2.MAP, 13584 bytes, 6/1/2007 2:40:45 PM
16714 15:07:36 (0) ** - OBJECTS.DATA, 26476544 bytes, 6/1/2007 2:40:45
PM
16715 15:07:36 (0) ** - OBJECTS.MAP, 12952 bytes, 6/1/2007 2:56:45 PM
16716 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16717 15:07:36 (0) ** INFO: Windows Firewall
status: ......................................................................................
ENABLED.
16718 15:07:36 (0) ** Windows Firewall
Profile: ...........................................................................................
DOMAIN.
16719 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16720 15:07:36 (0) ** DCOM
Status: ........................................................................................................
OK.
16721 15:07:36 (0) ** WMI registry
setup: .................................................................................................
OK.
16722 15:07:36 (0) ** INFO: WMI service has
dependents: ...................................................................................
2 SERVICE(S)!
16723 15:07:36 (0) ** - Security Center (WSCSVC,
StartMode='Automatic')
16724 15:07:36 (0) ** - Windows Firewall/Internet Connection Sharing
(ICS) (SHAREDACCESS, StartMode='Automatic')
16725 15:07:36 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
16726 15:07:36 (0) ** Note: If the service is marked with (*), it
means that the service/application uses WMI but
16727 15:07:36 (0) ** there is no hard dependency on WMI. However, if
the WMI service is stopped,
16728 15:07:36 (0) ** this can prevent the service/application to work
as expected.
16729 15:07:36 (0) **
16730 15:07:36 (0) ** RPCSS
service: ......................................................................................................
OK (Already started).
16731 15:07:36 (0) ** WINMGMT
service: ....................................................................................................
OK (Already started).
16732 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16733 15:07:36 (0) ** WMI service DCOM
setup: .............................................................................................
OK.
16734 15:07:36 (0) ** WMI components DCOM
registrations: ..................................................................................
OK.
16735 15:07:36 (0) ** WMI ProgID
registrations: ...........................................................................................
OK.
16736 15:07:36 (0) ** WMI provider DCOM
registrations: ....................................................................................
OK.
16737 15:07:36 (0) ** WMI provider CIM
registrations: .....................................................................................
OK.
16738 15:07:36 (0) ** WMI provider
CLSIDs: ................................................................................................
OK.
16739 15:07:36 (0) ** WMI providers EXE/DLL
availability: .................................................................................
OK.
16740 15:07:36 (0) **
----------------------------------------------------------------------------------------------------------------------------------
16741 15:07:36 (0) ** WMI namespace security for 'ROOT/
RSOP': .............................................................................
MODIFIED.
16742 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
16743 15:07:36 (0) ** - REMOVED ACE:
16744 15:07:36 (0) ** ACEType: &h0
16745 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16746 15:07:36 (0) ** ACEFlags: &h12
16747 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16748 15:07:36 (0) ** INHERITED_ACE
16749 15:07:36 (0) ** ACEMask: &h6003F
16750 15:07:36 (0) ** WBEM_ENABLE
16751 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16752 15:07:36 (0) ** WBEM_FULL_WRITE_REP
16753 15:07:36 (0) ** WBEM_PARTIAL_WRITE_REP
16754 15:07:36 (0) ** WBEM_WRITE_PROVIDER
16755 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16756 15:07:36 (0) ** WBEM_WRITE_DAC
16757 15:07:36 (0) ** WBEM_READ_CONTROL
16758 15:07:36 (0) **
16759 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16760 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16761 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16762 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16763 15:07:36 (0) **
16764 15:07:36 (0) ** WMI namespace security for 'ROOT/
RSOP': .............................................................................
MODIFIED.
16765 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
16766 15:07:36 (0) ** - REMOVED ACE:
16767 15:07:36 (0) ** ACEType: &h0
16768 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16769 15:07:36 (0) ** ACEFlags: &h12
16770 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16771 15:07:36 (0) ** INHERITED_ACE
16772 15:07:36 (0) ** ACEMask: &h20023
16773 15:07:36 (0) ** WBEM_ENABLE
16774 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16775 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16776 15:07:36 (0) ** WBEM_READ_CONTROL
16777 15:07:36 (0) **
16778 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16779 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16780 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16781 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16782 15:07:36 (0) **
16783 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
USER': ........................................................................
MODIFIED.
16784 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
16785 15:07:36 (0) ** - REMOVED ACE:
16786 15:07:36 (0) ** ACEType: &h0
16787 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16788 15:07:36 (0) ** ACEFlags: &h12
16789 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16790 15:07:36 (0) ** INHERITED_ACE
16791 15:07:36 (0) ** ACEMask: &h6003F
16792 15:07:36 (0) ** WBEM_ENABLE
16793 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16794 15:07:36 (0) ** WBEM_FULL_WRITE_REP
16795 15:07:36 (0) ** WBEM_PARTIAL_WRITE_REP
16796 15:07:36 (0) ** WBEM_WRITE_PROVIDER
16797 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16798 15:07:36 (0) ** WBEM_WRITE_DAC
16799 15:07:36 (0) ** WBEM_READ_CONTROL
16800 15:07:36 (0) **
16801 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16802 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16803 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16804 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16805 15:07:36 (0) **
16806 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
USER': ........................................................................
MODIFIED.
16807 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
16808 15:07:36 (0) ** - REMOVED ACE:
16809 15:07:36 (0) ** ACEType: &h0
16810 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16811 15:07:36 (0) ** ACEFlags: &h12
16812 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16813 15:07:36 (0) ** INHERITED_ACE
16814 15:07:36 (0) ** ACEMask: &h20023
16815 15:07:36 (0) ** WBEM_ENABLE
16816 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16817 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16818 15:07:36 (0) ** WBEM_READ_CONTROL
16819 15:07:36 (0) **
16820 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16821 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16822 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16823 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16824 15:07:36 (0) **
16825 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
COMPUTER': ....................................................................
MODIFIED.
16826 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
16827 15:07:36 (0) ** - REMOVED ACE:
16828 15:07:36 (0) ** ACEType: &h0
16829 15:07:36 (0) ** ACCESS_ALLOWED_ACE_TYPE
16830 15:07:36 (0) ** ACEFlags: &h12
16831 15:07:36 (0) ** CONTAINER_INHERIT_ACE
16832 15:07:36 (0) ** INHERITED_ACE
16833 15:07:36 (0) ** ACEMask: &h6003F
16834 15:07:36 (0) ** WBEM_ENABLE
16835 15:07:36 (0) ** WBEM_METHOD_EXECUTE
16836 15:07:36 (0) ** WBEM_FULL_WRITE_REP
16837 15:07:36 (0) ** WBEM_PARTIAL_WRITE_REP
16838 15:07:36 (0) ** WBEM_WRITE_PROVIDER
16839 15:07:36 (0) ** WBEM_REMOTE_ACCESS
16840 15:07:36 (0) ** WBEM_WRITE_DAC
16841 15:07:36 (0) ** WBEM_READ_CONTROL
16842 15:07:36 (0) **
16843 15:07:36 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
16844 15:07:36 (0) ** Removing default security will cause some
operations to fail!
16845 15:07:36 (0) ** It is possible to fix this issue by editing the
security descriptor and adding the ACE.
16846 15:07:36 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
16847 15:07:36 (0) **
16848 15:07:36 (0) ** WMI namespace security for 'ROOT/RSOP/
COMPUTER': ....................................................................
MODIFIED.
16849 15:07:36 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
16850 15:07:36 (0) ** - REMOVED ACE:
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top