msinfo32.exe gives "connection to could not be established..." ???

J

jbclem

I'm trying to run msinfo32.exe, which is the System Information/System

Summary module. But I keep getting this response: "the connection to could

not be established. Check to see that the network path name is correct,

that you have sufficient permission to access Windows Management".



All of the other modules (Hardware Resources, Components, etc...) give the

same response. I've tried refreshing, but still the same response. Looking

in the Event Viewer, there are plenty of errors that say "WinMgmt cannot

open the repository file..." could that have something to do with this.

But I have plenty of disk space and memory. These WinMgmt errors seem to

have started a month ago.



Can someone show me what's wrong here...the computer seems to be working

normally, and I checked Services to see if I might have turned something

off. I started Windows Management Instrumentation, in case that was

it...but no difference.



John
 
J

John John - MVP

msinfo32.exe gives "connection to could not be established..."???

Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

folder. Administrators and the System account should have Full Control

on this folder.



John



jbclem wrote:

> I'm trying to run msinfo32.exe, which is the System Information/System

> Summary module. But I keep getting this response: "the connection to could

> not be established. Check to see that the network path name is correct,

> that you have sufficient permission to access Windows Management".

>

> All of the other modules (Hardware Resources, Components, etc...) give the

> same response. I've tried refreshing, but still the same response. Looking

> in the Event Viewer, there are plenty of errors that say "WinMgmt cannot

> open the repository file..." could that have something to do with this.

> But I have plenty of disk space and memory. These WinMgmt errors seem to

> have started a month ago.

>

> Can someone show me what's wrong here...the computer seems to be working

> normally, and I checked Services to see if I might have turned something

> off. I started Windows Management Instrumentation, in case that was

> it...but no difference.

>

> John

>

>
 
J

jbclem

I'm not sure how to verify permissions...I found some instructions(from

support.microsoft.com) and went to Computer Management/Services and

Applications/WMI Control/properties and was supposed to go to the Security

tab but I can't get out of the General tab. The other tabs were

non-responsive. The box below says :"failed to connect to

because WMI: "initialization failure" . Above the box there is a line with

the word "Connected" and to it's right a Change button which allows me to

change the WMI logon. It's currently set to Log on as Current User.



That's as much as I've been able to do. Can you point me to a specific way

to check the permissions for he WBEM repository folder.



John







"John John - MVP" wrote in message

news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

> folder. Administrators and the System account should have Full Control

> on this folder.

>

> John

>

> jbclem wrote:

> > I'm trying to run msinfo32.exe, which is the System Information/System

> > Summary module. But I keep getting this response: "the connection to

could

> > not be established. Check to see that the network path name is

correct,

> > that you have sufficient permission to access Windows Management".

> >

> > All of the other modules (Hardware Resources, Components, etc...) give

the

> > same response. I've tried refreshing, but still the same response.

Looking

> > in the Event Viewer, there are plenty of errors that say "WinMgmt cannot

> > open the repository file..." could that have something to do with this.

> > But I have plenty of disk space and memory. These WinMgmt errors seem

to

> > have started a month ago.

> >

> > Can someone show me what's wrong here...the computer seems to be working

> > normally, and I checked Services to see if I might have turned something

> > off. I started Windows Management Instrumentation, in case that was

> > it...but no difference.

> >

> > John

> >

> >
 
J

jbclem

I've installed and run WMIDiag v2.0_2000. It shows this:



..737 19:14:17 (1) !! ERROR: DCOM Status:

.............................................................................

...................... ERROR!

...738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer is

DISABLED.

...739 19:14:17 (0) ** This prevents WMI to work correctly.

...740 19:14:17 (0) ** You can fix the DCOM configuration by:

...741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

...742 19:14:17 (0) ** - Expanding 'Component Services' and 'Computers'

nodes.

...743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

...744 19:14:17 (0) ** - Editing the 'Default properties' tab.

...745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

computer' checkbox.

...746 19:14:17 (0) **



I ran DCOMCNFG.exe but couldn't find the Component Services or Computer

nodes.



Actually, here's the entire report...there are some more errors towards the

bottom.

========================================================================

...697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14, 2010 at

19:14.

...698 19:14:17 (0) **

...699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

reserved - January 2007.

...700 19:14:17 (0) **

...701 19:14:17 (0) ** This script is not supported under any Microsoft

standard support program or service.

...702 19:14:17 (0) ** The script is provided AS IS without warranty of any

kind. Microsoft further disclaims all

...703 19:14:17 (0) ** implied warranties including, without limitation, any

implied warranties of merchantability

...704 19:14:17 (0) ** or of fitness for a particular purpose. The entire

risk arising out of the use or performance

...705 19:14:17 (0) ** of the scripts and documentation remains with you. In

no event shall Microsoft, its authors,

...706 19:14:17 (0) ** or anyone else involved in the creation, production,

or delivery of the script be liable for

...707 19:14:17 (0) ** any damages whatsoever (including, without limitation,

damages for loss of business profits,

...708 19:14:17 (0) ** business interruption, loss of business information,

or other pecuniary loss) arising out of

...709 19:14:17 (0) ** the use of or inability to use the script or

documentation, even if Microsoft has been advised

...710 19:14:17 (0) ** of the possibility of such damages.

...711 19:14:17 (0) **

...712 19:14:17 (0) **

...713 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...714 19:14:17 (0) ** -----------------------------------------------------

WMI REPORT: BEGIN ----------------------------------------------------------

...715 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...716 19:14:17 (0) **

...717 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit (2195) -

User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

...719 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...720 19:14:17 (0) ** Environment:

.............................................................................

............................. OK..

...721 19:14:17 (0) ** There are no missing WMI system files:

.............................................................................

... OK.

...722 19:14:17 (0) ** There are no missing WMI repository files:

...........................................................................

OK.

...723 19:14:17 (0) ** WMI repository state:

.............................................................................

.................... N/A.

...724 19:14:17 (0) ** BEFORE running WMIDiag:

...725 19:14:17 (0) ** The WMI repository has a size of:

.............................................................................

........ 1 MB.

...726 19:14:17 (0) ** - Disk free space on 'C:':

.............................................................................

............... 2149 MB.

...727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

3/12/2010 11:22:16 PM

...728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

4/14/2010 7:02:40 PM

...729 19:14:17 (0) ** AFTER running WMIDiag:

...730 19:14:17 (0) ** The WMI repository has a size of:

.............................................................................

........ 1 MB.

...731 19:14:17 (0) ** - Disk free space on 'C:':

.............................................................................

............... 2149 MB.

...732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

3/12/2010 11:22:16 PM

...733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

4/14/2010 7:02:40 PM

...734 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...735 19:14:17 (0) ** Windows Firewall:

.............................................................................

........................ NOT INSTALLED.

...736 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...737 19:14:17 (1) !! ERROR: DCOM Status:

.............................................................................

...................... ERROR!

...738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer is

DISABLED.

...739 19:14:17 (0) ** This prevents WMI to work correctly.

...740 19:14:17 (0) ** You can fix the DCOM configuration by:

...741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

...742 19:14:17 (0) ** - Expanding 'Component Services' and 'Computers'

nodes.

...743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

...744 19:14:17 (0) ** - Editing the 'Default properties' tab.

...745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

computer' checkbox.

...746 19:14:17 (0) **

...747 19:14:17 (0) ** WMI registry setup:

.............................................................................

...................... OK.

...748 19:14:17 (0) ** WMI Service has no dependents:

.............................................................................

........... OK.

...749 19:14:17 (0) ** RPCSS service:

.............................................................................

........................... OK (Already started).

...750 19:14:17 (0) ** WINMGMT service:

.............................................................................

......................... OK (Successfully started).

...751 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...752 19:14:17 (0) ** WMI service DCOM setup:

.............................................................................

.................. OK.

...753 19:14:17 (0) ** WMI components DCOM registrations:

.............................................................................

....... OK.

...754 19:14:17 (0) ** WMI ProgID registrations:

.............................................................................

................ OK.

...755 19:14:17 (0) ** WMI provider DCOM registrations:

.............................................................................

......... OK.

...756 19:14:17 (0) ** WMI provider CIM registrations:

.............................................................................

.......... OK.

...757 19:14:17 (0) ** WMI provider CLSIDs:

.............................................................................

..................... OK.

...758 19:14:17 (0) ** WMI providers EXE/DLL availability:

.............................................................................

...... OK.

...759 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...760 19:14:17 (0) ** Overall security status:

.............................................................................

................. NOT TESTED.

...761 19:14:17 (0) ** - Started at

'Root' ---------------------------------------------------------------------

-----------------------------------------

...762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

.............................................................................

........... NONE.

...763 19:14:17 (0) ** WMI TIMER instruction(s):

.............................................................................

................ NONE.

...764 19:14:17 (1) !! ERROR: WMI ADAP status:

.............................................................................

.................. NOT AVAILABLE.

...765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

(ADAP) process to resynchronize

...766 19:14:17 (0) ** the performance counters with the WMI performance

classes with the following commands:

...767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

...768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF '

...769 19:14:17 (0) ** The ADAP process logs informative events in the

Windows NT event log.

...770 19:14:17 (0) ** More information can be found on MSDN at:

...771 19:14:17 (0) **

http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

...772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the

following namespaces: .......................................... 1 ERROR(S)!

...773 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

Component such as a provider failed to initialize for internal reasons.

...774 19:14:17 (0) **

...775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the following

namespaces: .................................................. 5 ERROR(S)!

...776 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

Component such as a provider failed to initialize for internal reasons.

...777 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

Component such as a provider failed to initialize for internal reasons.

...778 19:14:17 (0) ** - Root/Default, 0x80041014 -

(WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

initialize for internal reasons.

...779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

(WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

initialize for internal reasons.

...780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

(WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

initialize for internal reasons.

...781 19:14:17 (0) **

...782 19:14:17 (0) ** WMI GET operations:

.............................................................................

...................... OK.

...783 19:14:17 (0) ** WMI MOF representations:

.............................................................................

................. OK.

...784 19:14:17 (0) ** WMI QUALIFIER access operations:

.............................................................................

......... OK.

...785 19:14:17 (0) ** WMI ENUMERATION operations:

.............................................................................

.............. OK.

...786 19:14:17 (0) ** WMI EXECQUERY operations:

.............................................................................

................ OK.

...787 19:14:17 (0) ** WMI GET VALUE operations:

.............................................................................

................ OK.

...788 19:14:17 (0) ** WMI WRITE operations:

.............................................................................

.................... NOT TESTED.

...789 19:14:17 (0) ** WMI PUT operations:

.............................................................................

...................... NOT TESTED.

...790 19:14:17 (0) ** WMI DELETE operations:

.............................................................................

................... NOT TESTED.

...791 19:14:17 (0) ** WMI static instances retrieved:

.............................................................................

.......... 0.

...792 19:14:17 (0) ** WMI dynamic instances retrieved:

.............................................................................

......... 0.

...793 19:14:17 (0) ** WMI instance request cancellations (to limit

performance impact): ................................................... 0.

...794 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...795 19:14:17 (0) **

...796 19:14:17 (0) ** 6 error(s) 0x80041014 -

(WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

initialize for internal reasons

...797 19:14:17 (0) ** => This error is typically a WMI system error. WMI

system errors can find their origin in:

...798 19:14:17 (0) ** - Failing WMI system components (see any missing

WMI system files or DCOM registration

...799 19:14:17 (0) ** issues previously mentioned).

...800 19:14:17 (0) ** - Failing WMI providers (see any DCOM registration

issues previously mentioned).

...801 19:14:17 (0) ** - a WMI repository corruption.

...802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

'WriteInRepository' parameter

...803 19:14:17 (0) ** to validate the WMI repository operations.

...804 19:14:17 (0) ** Note: ENSURE you are an administrator with FULL

access to WMI EVERY namespaces of the computer before

...805 19:14:17 (0) ** executing the WriteInRepository command. To

write temporary data from the Root namespace, use:

...806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

...807 19:14:17 (0) ** - If the WriteInRepository command fails, while

being an Administrator with ALL accesses to ALL namespaces

...808 19:14:17 (0) ** the WMI repository must be reconstructed.

...809 19:14:17 (0) ** Note: The WMI repository reconstruction requires to

locate all MOF files needed to rebuild the repository,

...810 19:14:17 (0) ** otherwise some applications may fail after

the reconstruction.

...811 19:14:17 (0) ** This can be achieved with the following

command:

...812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

...813 19:14:17 (0) ** Note: The repository reconstruction must be a LAST

RESORT solution and ONLY after executing

...814 19:14:17 (0) ** ALL fixes previously mentioned.

...815 19:14:17 (2) !! WARNING: Static information stored by external

applications in the repository will be LOST! (i.e. SMS Inventory)

...816 19:14:17 (0) **

...817 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...818 19:14:17 (0) ** WMI Registry key setup:

.............................................................................

.................. OK.

...819 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder not

referenced in the Auto-Recovery list: ............................. 13

ERROR(S)!

...821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

...822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

...823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

...824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

...825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

...826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

...827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

...828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

...829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

...830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

...831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

...832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

...833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

...834 19:14:17 (0) ** => After fixing all other issues previously mentioned,

if the WMI repository is rebuilt,

...835 19:14:17 (0) ** the listed MOF file(s) will not be recompiled, and

therefore the definition they contain

...836 19:14:17 (0) ** will not be available in the WMI repository.

...837 19:14:17 (0) ** => You must manually recompile the MOF file(s) with

the 'MOFCOMP.EXE ' command.

...838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

Auto-Recovery list, make sure the

...839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

...840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

included AT SETUP in the auto-recovery process.

...841 19:14:17 (0) ** MOF file(s) containing UNINSTALL statements

(i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery

process.

...842 19:14:17 (0) ** Refer to the list of MOF files below NOT

containing the '#PRAGMA AUTORECOVER' statement' for more information.

...843 19:14:17 (0) **

...844 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...845 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

AUTORECOVER' statement: .............................................. 14

FILE(S)!

...847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

...848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

...849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

...850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

...851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

...852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

...853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

...854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

...855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

...856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

...857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

...858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

...859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

...860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

...861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in the

AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER'

statement.

...862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed MOF

files not included in the AUTO-RECOVERY LIST and

...863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement when

they are compiled the first time will NOT

...864 19:14:17 (0) ** be recompiled during the repository reconstruction.

...865 19:14:17 (0) ** Note: If you want the MOF file to be part of the

AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

...866 19:14:17 (0) ** is included and recompile the MOF/MFL with

the following command:

...867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

...868 19:14:17 (0) **

...869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains class and

instance DELETE statements.

...870 19:14:17 (0) ** Usually, MOF with DELETE statements are used to

UNinstall components and they should NOT be listed in the AUTORECOVERY LIST

...871 19:14:17 (0) ** and therefore they should NOT specify the '#PRAGMA

AUTORECOVER' statement.

...872 19:14:17 (0) ** Note: It happens that some MOF files do contain

DELETE statements for installation purposes to delete

...873 19:14:17 (0) ** existing information before it is recreated.

...874 19:14:17 (0) **

...875 19:14:17 (0) ** Note: It is also possible that the application

implemented its own recovery mechanism.

...876 19:14:17 (0) ** In that case, no action is required. You must

verify with the application vendor

...877 19:14:17 (0) ** if the application has this capability (i.e.

Microsoft SMS)

...878 19:14:17 (0) **

...879 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...880 19:14:17 (0) **

...881 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...882 19:14:17 (0) ** ------------------------------------------------------

WMI REPORT: END -----------------------------------------------------------

...883 19:14:17 (0)

** -------------------------------------------------------------------------

---------------------------------------------------------

...884 19:14:17 (0) **

...885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could prevent WMI

to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

..29.LOG' for details.

...886 19:14:17 (0) **

...887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010 at

19:14 (W:30 E:16 S:1).

-===========================================================================

====











"John John - MVP" wrote in message

news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

> folder. Administrators and the System account should have Full Control

> on this folder.

>

> John

>

> jbclem wrote:

> > I'm trying to run msinfo32.exe, which is the System Information/System

> > Summary module. But I keep getting this response: "the connection to

could

> > not be established. Check to see that the network path name is

correct,

> > that you have sufficient permission to access Windows Management".

> >

> > All of the other modules (Hardware Resources, Components, etc...) give

the

> > same response. I've tried refreshing, but still the same response.

Looking

> > in the Event Viewer, there are plenty of errors that say "WinMgmt cannot

> > open the repository file..." could that have something to do with this.

> > But I have plenty of disk space and memory. These WinMgmt errors seem

to

> > have started a month ago.

> >

> > Can someone show me what's wrong here...the computer seems to be working

> > normally, and I checked Services to see if I might have turned something

> > off. I started Windows Management Instrumentation, in case that was

> > it...but no difference.

> >

> > John

> >

> >
 
D

Dave Patrick

Component Services should be within Console Root (maybe click / double

click) Computers within Component Services





--



Regards,



Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect



"jbclem" wrote:

> I've installed and run WMIDiag v2.0_2000. It shows this:

>

> .737 19:14:17 (1) !! ERROR: DCOM Status:

> ............................................................................

> ..................... ERROR!

> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer is

> DISABLED.

> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> ..742 19:14:17 (0) ** - Expanding 'Component Services' and 'Computers'

> nodes.

> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

> computer' checkbox.

> ..746 19:14:17 (0) **

>

> I ran DCOMCNFG.exe but couldn't find the Component Services or Computer

> nodes.

>

> Actually, here's the entire report...there are some more errors towards

> the

> bottom.

> ========================================================================

> ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14, 2010 at

> 19:14.

> ..698 19:14:17 (0) **

> ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

> reserved - January 2007.

> ..700 19:14:17 (0) **

> ..701 19:14:17 (0) ** This script is not supported under any Microsoft

> standard support program or service.

> ..702 19:14:17 (0) ** The script is provided AS IS without warranty of any

> kind. Microsoft further disclaims all

> ..703 19:14:17 (0) ** implied warranties including, without limitation,

> any

> implied warranties of merchantability

> ..704 19:14:17 (0) ** or of fitness for a particular purpose. The entire

> risk arising out of the use or performance

> ..705 19:14:17 (0) ** of the scripts and documentation remains with you.

> In

> no event shall Microsoft, its authors,

> ..706 19:14:17 (0) ** or anyone else involved in the creation, production,

> or delivery of the script be liable for

> ..707 19:14:17 (0) ** any damages whatsoever (including, without

> limitation,

> damages for loss of business profits,

> ..708 19:14:17 (0) ** business interruption, loss of business information,

> or other pecuniary loss) arising out of

> ..709 19:14:17 (0) ** the use of or inability to use the script or

> documentation, even if Microsoft has been advised

> ..710 19:14:17 (0) ** of the possibility of such damages.

> ..711 19:14:17 (0) **

> ..712 19:14:17 (0) **

> ..713 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..714 19:14:17 (0)

> ** -----------------------------------------------------

> WMI REPORT:

> BEGIN ----------------------------------------------------------

> ..715 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..716 19:14:17 (0) **

> ..717 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit

> (2195) -

> User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

> ..719 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..720 19:14:17 (0) ** Environment:

> ............................................................................

> ............................ OK..

> ..721 19:14:17 (0) ** There are no missing WMI system files:

> ............................................................................

> .. OK.

> ..722 19:14:17 (0) ** There are no missing WMI repository files:

> ..........................................................................

> OK.

> ..723 19:14:17 (0) ** WMI repository state:

> ............................................................................

> ................... N/A.

> ..724 19:14:17 (0) ** BEFORE running WMIDiag:

> ..725 19:14:17 (0) ** The WMI repository has a size of:

> ............................................................................

> ....... 1 MB.

> ..726 19:14:17 (0) ** - Disk free space on 'C:':

> ............................................................................

> .............. 2149 MB.

> ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> 3/12/2010 11:22:16 PM

> ..728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> 4/14/2010 7:02:40 PM

> ..729 19:14:17 (0) ** AFTER running WMIDiag:

> ..730 19:14:17 (0) ** The WMI repository has a size of:

> ............................................................................

> ....... 1 MB.

> ..731 19:14:17 (0) ** - Disk free space on 'C:':

> ............................................................................

> .............. 2149 MB.

> ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> 3/12/2010 11:22:16 PM

> ..733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> 4/14/2010 7:02:40 PM

> ..734 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..735 19:14:17 (0) ** Windows Firewall:

> ............................................................................

> ....................... NOT INSTALLED.

> ..736 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..737 19:14:17 (1) !! ERROR: DCOM Status:

> ............................................................................

> ..................... ERROR!

> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer is

> DISABLED.

> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> ..742 19:14:17 (0) ** - Expanding 'Component Services' and 'Computers'

> nodes.

> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

> computer' checkbox.

> ..746 19:14:17 (0) **

> ..747 19:14:17 (0) ** WMI registry setup:

> ............................................................................

> ..................... OK.

> ..748 19:14:17 (0) ** WMI Service has no dependents:

> ............................................................................

> .......... OK.

> ..749 19:14:17 (0) ** RPCSS service:

> ............................................................................

> .......................... OK (Already started).

> ..750 19:14:17 (0) ** WINMGMT service:

> ............................................................................

> ........................ OK (Successfully started).

> ..751 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..752 19:14:17 (0) ** WMI service DCOM setup:

> ............................................................................

> ................. OK.

> ..753 19:14:17 (0) ** WMI components DCOM registrations:

> ............................................................................

> ...... OK.

> ..754 19:14:17 (0) ** WMI ProgID registrations:

> ............................................................................

> ............... OK.

> ..755 19:14:17 (0) ** WMI provider DCOM registrations:

> ............................................................................

> ........ OK.

> ..756 19:14:17 (0) ** WMI provider CIM registrations:

> ............................................................................

> ......... OK.

> ..757 19:14:17 (0) ** WMI provider CLSIDs:

> ............................................................................

> .................... OK.

> ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

> ............................................................................

> ..... OK.

> ..759 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..760 19:14:17 (0) ** Overall security status:

> ............................................................................

> ................ NOT TESTED.

> ..761 19:14:17 (0) ** - Started at

> 'Root' ---------------------------------------------------------------------

> -----------------------------------------

> ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

> ............................................................................

> .......... NONE.

> ..763 19:14:17 (0) ** WMI TIMER instruction(s):

> ............................................................................

> ............... NONE.

> ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

> ............................................................................

> ................. NOT AVAILABLE.

> ..765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

> (ADAP) process to resynchronize

> ..766 19:14:17 (0) ** the performance counters with the WMI performance

> classes with the following commands:

> ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

> ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF

> '

> ..769 19:14:17 (0) ** The ADAP process logs informative events in the

> Windows NT event log.

> ..770 19:14:17 (0) ** More information can be found on MSDN at:

> ..771 19:14:17 (0) **

> http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

> ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the

> following namespaces: .......................................... 1

> ERROR(S)!

> ..773 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

> Component such as a provider failed to initialize for internal reasons.

> ..774 19:14:17 (0) **

> ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the

> following

> namespaces: .................................................. 5 ERROR(S)!

> ..776 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

> Component such as a provider failed to initialize for internal reasons.

> ..777 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

> Component such as a provider failed to initialize for internal reasons.

> ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons.

> ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons.

> ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons.

> ..781 19:14:17 (0) **

> ..782 19:14:17 (0) ** WMI GET operations:

> ............................................................................

> ..................... OK.

> ..783 19:14:17 (0) ** WMI MOF representations:

> ............................................................................

> ................ OK.

> ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

> ............................................................................

> ........ OK.

> ..785 19:14:17 (0) ** WMI ENUMERATION operations:

> ............................................................................

> ............. OK.

> ..786 19:14:17 (0) ** WMI EXECQUERY operations:

> ............................................................................

> ............... OK.

> ..787 19:14:17 (0) ** WMI GET VALUE operations:

> ............................................................................

> ............... OK.

> ..788 19:14:17 (0) ** WMI WRITE operations:

> ............................................................................

> ................... NOT TESTED.

> ..789 19:14:17 (0) ** WMI PUT operations:

> ............................................................................

> ..................... NOT TESTED.

> ..790 19:14:17 (0) ** WMI DELETE operations:

> ............................................................................

> .................. NOT TESTED.

> ..791 19:14:17 (0) ** WMI static instances retrieved:

> ............................................................................

> ......... 0.

> ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

> ............................................................................

> ........ 0.

> ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

> performance impact): ...................................................

> 0.

> ..794 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..795 19:14:17 (0) **

> ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons

> ..797 19:14:17 (0) ** => This error is typically a WMI system error. WMI

> system errors can find their origin in:

> ..798 19:14:17 (0) ** - Failing WMI system components (see any missing

> WMI system files or DCOM registration

> ..799 19:14:17 (0) ** issues previously mentioned).

> ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM

> registration

> issues previously mentioned).

> ..801 19:14:17 (0) ** - a WMI repository corruption.

> ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

> 'WriteInRepository' parameter

> ..803 19:14:17 (0) ** to validate the WMI repository operations.

> ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with FULL

> access to WMI EVERY namespaces of the computer before

> ..805 19:14:17 (0) ** executing the WriteInRepository command. To

> write temporary data from the Root namespace, use:

> ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

> ..807 19:14:17 (0) ** - If the WriteInRepository command fails, while

> being an Administrator with ALL accesses to ALL namespaces

> ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

> ..809 19:14:17 (0) ** Note: The WMI repository reconstruction requires

> to

> locate all MOF files needed to rebuild the repository,

> ..810 19:14:17 (0) ** otherwise some applications may fail after

> the reconstruction.

> ..811 19:14:17 (0) ** This can be achieved with the following

> command:

> ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

> ..813 19:14:17 (0) ** Note: The repository reconstruction must be a

> LAST

> RESORT solution and ONLY after executing

> ..814 19:14:17 (0) ** ALL fixes previously mentioned.

> ..815 19:14:17 (2) !! WARNING: Static information stored by external

> applications in the repository will be LOST! (i.e. SMS Inventory)

> ..816 19:14:17 (0) **

> ..817 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..818 19:14:17 (0) ** WMI Registry key setup:

> ............................................................................

> ................. OK.

> ..819 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder not

> referenced in the Auto-Recovery list: ............................. 13

> ERROR(S)!

> ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

> ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

> ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

> ..834 19:14:17 (0) ** => After fixing all other issues previously

> mentioned,

> if the WMI repository is rebuilt,

> ..835 19:14:17 (0) ** the listed MOF file(s) will not be recompiled,

> and

> therefore the definition they contain

> ..836 19:14:17 (0) ** will not be available in the WMI repository.

> ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s) with

> the 'MOFCOMP.EXE ' command.

> ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

> Auto-Recovery list, make sure the

> ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

> ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

> included AT SETUP in the auto-recovery process.

> ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL statements

> (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery

> process.

> ..842 19:14:17 (0) ** Refer to the list of MOF files below NOT

> containing the '#PRAGMA AUTORECOVER' statement' for more information.

> ..843 19:14:17 (0) **

> ..844 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..845 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

> AUTORECOVER' statement: .............................................. 14

> FILE(S)!

> ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

> ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

> ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

> ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

> ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in the

> AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER'

> statement.

> ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed MOF

> files not included in the AUTO-RECOVERY LIST and

> ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement when

> they are compiled the first time will NOT

> ..864 19:14:17 (0) ** be recompiled during the repository

> reconstruction.

> ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of the

> AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

> ..866 19:14:17 (0) ** is included and recompile the MOF/MFL with

> the following command:

> ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

> ..868 19:14:17 (0) **

> ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains class

> and

> instance DELETE statements.

> ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used to

> UNinstall components and they should NOT be listed in the AUTORECOVERY

> LIST

> ..871 19:14:17 (0) ** and therefore they should NOT specify the

> '#PRAGMA

> AUTORECOVER' statement.

> ..872 19:14:17 (0) ** Note: It happens that some MOF files do contain

> DELETE statements for installation purposes to delete

> ..873 19:14:17 (0) ** existing information before it is

> recreated.

> ..874 19:14:17 (0) **

> ..875 19:14:17 (0) ** Note: It is also possible that the application

> implemented its own recovery mechanism.

> ..876 19:14:17 (0) ** In that case, no action is required. You

> must

> verify with the application vendor

> ..877 19:14:17 (0) ** if the application has this capability

> (i.e.

> Microsoft SMS)

> ..878 19:14:17 (0) **

> ..879 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..880 19:14:17 (0) **

> ..881 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..882 19:14:17 (0)

> ** ------------------------------------------------------

> WMI REPORT:

> END -----------------------------------------------------------

> ..883 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..884 19:14:17 (0) **

> ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could prevent

> WMI

> to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

> SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

> .29.LOG' for details.

> ..886 19:14:17 (0) **

> ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010 at

> 19:14 (W:30 E:16 S:1).

> -===========================================================================

> ====

>

>

>

>

>

> "John John - MVP" wrote in message

> news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

>> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

>> folder. Administrators and the System account should have Full Control

>> on this folder.

>>

>> John

>>

>> jbclem wrote:

>> > I'm trying to run msinfo32.exe, which is the System Information/System

>> > Summary module. But I keep getting this response: "the connection to

> could

>> > not be established. Check to see that the network path name is

> correct,

>> > that you have sufficient permission to access Windows Management".

>> >

>> > All of the other modules (Hardware Resources, Components, etc...) give

> the

>> > same response. I've tried refreshing, but still the same response.

> Looking

>> > in the Event Viewer, there are plenty of errors that say "WinMgmt

>> > cannot

>> > open the repository file..." could that have something to do with

>> > this.

>> > But I have plenty of disk space and memory. These WinMgmt errors seem

> to

>> > have started a month ago.

>> >

>> > Can someone show me what's wrong here...the computer seems to be

>> > working

>> > normally, and I checked Services to see if I might have turned

>> > something

>> > off. I started Windows Management Instrumentation, in case that was

>> > it...but no difference.

>> >

>> > John

>> >

>> >

>

>
 
J

John John - MVP

msinfo32.exe gives "connection to could not be established..."???

On Windows 2000 the Dcomcnfg command returns a different GUI, see here:



http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/comdcom/dcom_enable.html



or run this command instead to get to the Component Services snap-in:



%windir%\System32\Com\Comexp.msc



John



jbclem wrote:

> I've installed and run WMIDiag v2.0_2000. It shows this:

>

> .737 19:14:17 (1) !! ERROR: DCOM Status:

> ............................................................................

> ..................... ERROR!

> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer is

> DISABLED.

> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> ..742 19:14:17 (0) ** - Expanding 'Component Services' and 'Computers'

> nodes.

> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

> computer' checkbox.

> ..746 19:14:17 (0) **

>

> I ran DCOMCNFG.exe but couldn't find the Component Services or Computer

> nodes.

>

> Actually, here's the entire report...there are some more errors towards the

> bottom.

> ========================================================================

> ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14, 2010 at

> 19:14.

> ..698 19:14:17 (0) **

> ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

> reserved - January 2007.

> ..700 19:14:17 (0) **

> ..701 19:14:17 (0) ** This script is not supported under any Microsoft

> standard support program or service.

> ..702 19:14:17 (0) ** The script is provided AS IS without warranty of any

> kind. Microsoft further disclaims all

> ..703 19:14:17 (0) ** implied warranties including, without limitation, any

> implied warranties of merchantability

> ..704 19:14:17 (0) ** or of fitness for a particular purpose. The entire

> risk arising out of the use or performance

> ..705 19:14:17 (0) ** of the scripts and documentation remains with you. In

> no event shall Microsoft, its authors,

> ..706 19:14:17 (0) ** or anyone else involved in the creation, production,

> or delivery of the script be liable for

> ..707 19:14:17 (0) ** any damages whatsoever (including, without limitation,

> damages for loss of business profits,

> ..708 19:14:17 (0) ** business interruption, loss of business information,

> or other pecuniary loss) arising out of

> ..709 19:14:17 (0) ** the use of or inability to use the script or

> documentation, even if Microsoft has been advised

> ..710 19:14:17 (0) ** of the possibility of such damages.

> ..711 19:14:17 (0) **

> ..712 19:14:17 (0) **

> ..713 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..714 19:14:17 (0) ** -----------------------------------------------------

> WMI REPORT: BEGIN ----------------------------------------------------------

> ..715 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..716 19:14:17 (0) **

> ..717 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit (2195) -

> User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

> ..719 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..720 19:14:17 (0) ** Environment:

> ............................................................................

> ............................ OK..

> ..721 19:14:17 (0) ** There are no missing WMI system files:

> ............................................................................

> .. OK.

> ..722 19:14:17 (0) ** There are no missing WMI repository files:

> ..........................................................................

> OK.

> ..723 19:14:17 (0) ** WMI repository state:

> ............................................................................

> ................... N/A.

> ..724 19:14:17 (0) ** BEFORE running WMIDiag:

> ..725 19:14:17 (0) ** The WMI repository has a size of:

> ............................................................................

> ....... 1 MB.

> ..726 19:14:17 (0) ** - Disk free space on 'C:':

> ............................................................................

> .............. 2149 MB.

> ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> 3/12/2010 11:22:16 PM

> ..728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> 4/14/2010 7:02:40 PM

> ..729 19:14:17 (0) ** AFTER running WMIDiag:

> ..730 19:14:17 (0) ** The WMI repository has a size of:

> ............................................................................

> ....... 1 MB.

> ..731 19:14:17 (0) ** - Disk free space on 'C:':

> ............................................................................

> .............. 2149 MB.

> ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> 3/12/2010 11:22:16 PM

> ..733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> 4/14/2010 7:02:40 PM

> ..734 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..735 19:14:17 (0) ** Windows Firewall:

> ............................................................................

> ....................... NOT INSTALLED.

> ..736 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..737 19:14:17 (1) !! ERROR: DCOM Status:

> ............................................................................

> ..................... ERROR!

> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer is

> DISABLED.

> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> ..742 19:14:17 (0) ** - Expanding 'Component Services' and 'Computers'

> nodes.

> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

> computer' checkbox.

> ..746 19:14:17 (0) **

> ..747 19:14:17 (0) ** WMI registry setup:

> ............................................................................

> ..................... OK.

> ..748 19:14:17 (0) ** WMI Service has no dependents:

> ............................................................................

> .......... OK.

> ..749 19:14:17 (0) ** RPCSS service:

> ............................................................................

> .......................... OK (Already started).

> ..750 19:14:17 (0) ** WINMGMT service:

> ............................................................................

> ........................ OK (Successfully started).

> ..751 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..752 19:14:17 (0) ** WMI service DCOM setup:

> ............................................................................

> ................. OK.

> ..753 19:14:17 (0) ** WMI components DCOM registrations:

> ............................................................................

> ...... OK.

> ..754 19:14:17 (0) ** WMI ProgID registrations:

> ............................................................................

> ............... OK.

> ..755 19:14:17 (0) ** WMI provider DCOM registrations:

> ............................................................................

> ........ OK.

> ..756 19:14:17 (0) ** WMI provider CIM registrations:

> ............................................................................

> ......... OK.

> ..757 19:14:17 (0) ** WMI provider CLSIDs:

> ............................................................................

> .................... OK.

> ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

> ............................................................................

> ..... OK.

> ..759 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..760 19:14:17 (0) ** Overall security status:

> ............................................................................

> ................ NOT TESTED.

> ..761 19:14:17 (0) ** - Started at

> 'Root' ---------------------------------------------------------------------

> -----------------------------------------

> ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

> ............................................................................

> .......... NONE.

> ..763 19:14:17 (0) ** WMI TIMER instruction(s):

> ............................................................................

> ............... NONE.

> ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

> ............................................................................

> ................. NOT AVAILABLE.

> ..765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

> (ADAP) process to resynchronize

> ..766 19:14:17 (0) ** the performance counters with the WMI performance

> classes with the following commands:

> ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

> ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF '

> ..769 19:14:17 (0) ** The ADAP process logs informative events in the

> Windows NT event log.

> ..770 19:14:17 (0) ** More information can be found on MSDN at:

> ..771 19:14:17 (0) **

> http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

> ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the

> following namespaces: .......................................... 1 ERROR(S)!

> ..773 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

> Component such as a provider failed to initialize for internal reasons.

> ..774 19:14:17 (0) **

> ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the following

> namespaces: .................................................. 5 ERROR(S)!

> ..776 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

> Component such as a provider failed to initialize for internal reasons.

> ..777 19:14:17 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE)

> Component such as a provider failed to initialize for internal reasons.

> ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons.

> ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons.

> ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons.

> ..781 19:14:17 (0) **

> ..782 19:14:17 (0) ** WMI GET operations:

> ............................................................................

> ..................... OK.

> ..783 19:14:17 (0) ** WMI MOF representations:

> ............................................................................

> ................ OK.

> ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

> ............................................................................

> ........ OK.

> ..785 19:14:17 (0) ** WMI ENUMERATION operations:

> ............................................................................

> ............. OK.

> ..786 19:14:17 (0) ** WMI EXECQUERY operations:

> ............................................................................

> ............... OK.

> ..787 19:14:17 (0) ** WMI GET VALUE operations:

> ............................................................................

> ............... OK.

> ..788 19:14:17 (0) ** WMI WRITE operations:

> ............................................................................

> ................... NOT TESTED.

> ..789 19:14:17 (0) ** WMI PUT operations:

> ............................................................................

> ..................... NOT TESTED.

> ..790 19:14:17 (0) ** WMI DELETE operations:

> ............................................................................

> .................. NOT TESTED.

> ..791 19:14:17 (0) ** WMI static instances retrieved:

> ............................................................................

> ......... 0.

> ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

> ............................................................................

> ........ 0.

> ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

> performance impact): ................................................... 0.

> ..794 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..795 19:14:17 (0) **

> ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> initialize for internal reasons

> ..797 19:14:17 (0) ** => This error is typically a WMI system error. WMI

> system errors can find their origin in:

> ..798 19:14:17 (0) ** - Failing WMI system components (see any missing

> WMI system files or DCOM registration

> ..799 19:14:17 (0) ** issues previously mentioned).

> ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM registration

> issues previously mentioned).

> ..801 19:14:17 (0) ** - a WMI repository corruption.

> ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

> 'WriteInRepository' parameter

> ..803 19:14:17 (0) ** to validate the WMI repository operations.

> ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with FULL

> access to WMI EVERY namespaces of the computer before

> ..805 19:14:17 (0) ** executing the WriteInRepository command. To

> write temporary data from the Root namespace, use:

> ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

> ..807 19:14:17 (0) ** - If the WriteInRepository command fails, while

> being an Administrator with ALL accesses to ALL namespaces

> ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

> ..809 19:14:17 (0) ** Note: The WMI repository reconstruction requires to

> locate all MOF files needed to rebuild the repository,

> ..810 19:14:17 (0) ** otherwise some applications may fail after

> the reconstruction.

> ..811 19:14:17 (0) ** This can be achieved with the following

> command:

> ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

> ..813 19:14:17 (0) ** Note: The repository reconstruction must be a LAST

> RESORT solution and ONLY after executing

> ..814 19:14:17 (0) ** ALL fixes previously mentioned.

> ..815 19:14:17 (2) !! WARNING: Static information stored by external

> applications in the repository will be LOST! (i.e. SMS Inventory)

> ..816 19:14:17 (0) **

> ..817 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..818 19:14:17 (0) ** WMI Registry key setup:

> ............................................................................

> ................. OK.

> ..819 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder not

> referenced in the Auto-Recovery list: ............................. 13

> ERROR(S)!

> ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

> ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

> ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

> ..834 19:14:17 (0) ** => After fixing all other issues previously mentioned,

> if the WMI repository is rebuilt,

> ..835 19:14:17 (0) ** the listed MOF file(s) will not be recompiled, and

> therefore the definition they contain

> ..836 19:14:17 (0) ** will not be available in the WMI repository.

> ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s) with

> the 'MOFCOMP.EXE ' command.

> ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

> Auto-Recovery list, make sure the

> ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

> ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

> included AT SETUP in the auto-recovery process.

> ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL statements

> (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery

> process.

> ..842 19:14:17 (0) ** Refer to the list of MOF files below NOT

> containing the '#PRAGMA AUTORECOVER' statement' for more information.

> ..843 19:14:17 (0) **

> ..844 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..845 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

> AUTORECOVER' statement: .............................................. 14

> FILE(S)!

> ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

> ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

> ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

> ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

> ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in the

> AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER'

> statement.

> ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed MOF

> files not included in the AUTO-RECOVERY LIST and

> ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement when

> they are compiled the first time will NOT

> ..864 19:14:17 (0) ** be recompiled during the repository reconstruction.

> ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of the

> AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

> ..866 19:14:17 (0) ** is included and recompile the MOF/MFL with

> the following command:

> ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

> ..868 19:14:17 (0) **

> ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains class and

> instance DELETE statements.

> ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used to

> UNinstall components and they should NOT be listed in the AUTORECOVERY LIST

> ..871 19:14:17 (0) ** and therefore they should NOT specify the '#PRAGMA

> AUTORECOVER' statement.

> ..872 19:14:17 (0) ** Note: It happens that some MOF files do contain

> DELETE statements for installation purposes to delete

> ..873 19:14:17 (0) ** existing information before it is recreated.

> ..874 19:14:17 (0) **

> ..875 19:14:17 (0) ** Note: It is also possible that the application

> implemented its own recovery mechanism.

> ..876 19:14:17 (0) ** In that case, no action is required. You must

> verify with the application vendor

> ..877 19:14:17 (0) ** if the application has this capability (i.e.

> Microsoft SMS)

> ..878 19:14:17 (0) **

> ..879 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..880 19:14:17 (0) **

> ..881 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..882 19:14:17 (0) ** ------------------------------------------------------

> WMI REPORT: END -----------------------------------------------------------

> ..883 19:14:17 (0)

> ** -------------------------------------------------------------------------

> ---------------------------------------------------------

> ..884 19:14:17 (0) **

> ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could prevent WMI

> to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

> SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

> .29.LOG' for details.

> ..886 19:14:17 (0) **

> ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010 at

> 19:14 (W:30 E:16 S:1).

> -===========================================================================

> ====

>

>

>

>

>

> "John John - MVP" wrote in message

> news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

>> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

>> folder. Administrators and the System account should have Full Control

>> on this folder.

>>

>> John

>>

>> jbclem wrote:

>>> I'm trying to run msinfo32.exe, which is the System Information/System

>>> Summary module. But I keep getting this response: "the connection to

> could

>>> not be established. Check to see that the network path name is

> correct,

>>> that you have sufficient permission to access Windows Management".

>>>

>>> All of the other modules (Hardware Resources, Components, etc...) give

> the

>>> same response. I've tried refreshing, but still the same response.

> Looking

>>> in the Event Viewer, there are plenty of errors that say "WinMgmt cannot

>>> open the repository file..." could that have something to do with this.

>>> But I have plenty of disk space and memory. These WinMgmt errors seem

> to

>>> have started a month ago.

>>>

>>> Can someone show me what's wrong here...the computer seems to be working

>>> normally, and I checked Services to see if I might have turned something

>>> off. I started Windows Management Instrumentation, in case that was

>>> it...but no difference.

>>>

>>> John

>>>

>>>

>

>
 
J

jbclem

I've got DCOM enabled now. And just in case, I rebooted the computer. But

the problem still exists. Looking in the event viewer, the latest(a few

minutes ago) WinMgmt error states: WinMgmt could not open the repository

file. This could be due to insufficient security access to the

"\System32\WBEM\Repository", insufficient disk space or

insufficient memory.



I checked the properties of the Repository folder, it was set to "do not

share". I changed that to "share this folder" and checked the permissions.

All three were set to Allow.



Checked the original problem, but it's still there. I'm going to reboot

again, just in case.



Any other thoughts on this?



















"John John - MVP" wrote in message

news:Ouyo$EJ3KHA.1016@TK2MSFTNGP02.phx.gbl...

> On Windows 2000 the Dcomcnfg command returns a different GUI, see here:

>

>

http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/comdcom/dcom_enable.html

>

> or run this command instead to get to the Component Services snap-in:

>

> %windir%\System32\Com\Comexp.msc

>

> John

>

> jbclem wrote:

> > I've installed and run WMIDiag v2.0_2000. It shows this:

> >

> > .737 19:14:17 (1) !! ERROR: DCOM Status:

> >

.............................................................................

> > ..................... ERROR!

> > ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer

is

> > DISABLED.

> > ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> > ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> > ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> > ..742 19:14:17 (0) ** - Expanding 'Component Services' and

'Computers'

> > nodes.

> > ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> > ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> > ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

> > computer' checkbox.

> > ..746 19:14:17 (0) **

> >

> > I ran DCOMCNFG.exe but couldn't find the Component Services or Computer

> > nodes.

> >

> > Actually, here's the entire report...there are some more errors towards

the

> > bottom.

> > ========================================================================

> > ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14, 2010

at

> > 19:14.

> > ..698 19:14:17 (0) **

> > ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

> > reserved - January 2007.

> > ..700 19:14:17 (0) **

> > ..701 19:14:17 (0) ** This script is not supported under any Microsoft

> > standard support program or service.

> > ..702 19:14:17 (0) ** The script is provided AS IS without warranty of

any

> > kind. Microsoft further disclaims all

> > ..703 19:14:17 (0) ** implied warranties including, without limitation,

any

> > implied warranties of merchantability

> > ..704 19:14:17 (0) ** or of fitness for a particular purpose. The entire

> > risk arising out of the use or performance

> > ..705 19:14:17 (0) ** of the scripts and documentation remains with you.

In

> > no event shall Microsoft, its authors,

> > ..706 19:14:17 (0) ** or anyone else involved in the creation,

production,

> > or delivery of the script be liable for

> > ..707 19:14:17 (0) ** any damages whatsoever (including, without

limitation,

> > damages for loss of business profits,

> > ..708 19:14:17 (0) ** business interruption, loss of business

information,

> > or other pecuniary loss) arising out of

> > ..709 19:14:17 (0) ** the use of or inability to use the script or

> > documentation, even if Microsoft has been advised

> > ..710 19:14:17 (0) ** of the possibility of such damages.

> > ..711 19:14:17 (0) **

> > ..712 19:14:17 (0) **

> > ..713 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..714 19:14:17 (0)

** -----------------------------------------------------

> > WMI REPORT:

BEGIN ----------------------------------------------------------

> > ..715 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..716 19:14:17 (0) **

> > ..717 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit

(2195) -

> > User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

> > ..719 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..720 19:14:17 (0) ** Environment:

> >

.............................................................................

> > ............................ OK..

> > ..721 19:14:17 (0) ** There are no missing WMI system files:

> >

.............................................................................

> > .. OK.

> > ..722 19:14:17 (0) ** There are no missing WMI repository files:

> >

...........................................................................

> > OK.

> > ..723 19:14:17 (0) ** WMI repository state:

> >

.............................................................................

> > ................... N/A.

> > ..724 19:14:17 (0) ** BEFORE running WMIDiag:

> > ..725 19:14:17 (0) ** The WMI repository has a size of:

> >

.............................................................................

> > ....... 1 MB.

> > ..726 19:14:17 (0) ** - Disk free space on 'C:':

> >

.............................................................................

> > .............. 2149 MB.

> > ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> > 3/12/2010 11:22:16 PM

> > ..728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> > 4/14/2010 7:02:40 PM

> > ..729 19:14:17 (0) ** AFTER running WMIDiag:

> > ..730 19:14:17 (0) ** The WMI repository has a size of:

> >

.............................................................................

> > ....... 1 MB.

> > ..731 19:14:17 (0) ** - Disk free space on 'C:':

> >

.............................................................................

> > .............. 2149 MB.

> > ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> > 3/12/2010 11:22:16 PM

> > ..733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> > 4/14/2010 7:02:40 PM

> > ..734 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..735 19:14:17 (0) ** Windows Firewall:

> >

.............................................................................

> > ....................... NOT INSTALLED.

> > ..736 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..737 19:14:17 (1) !! ERROR: DCOM Status:

> >

.............................................................................

> > ..................... ERROR!

> > ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer

is

> > DISABLED.

> > ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> > ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> > ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> > ..742 19:14:17 (0) ** - Expanding 'Component Services' and

'Computers'

> > nodes.

> > ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> > ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> > ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

> > computer' checkbox.

> > ..746 19:14:17 (0) **

> > ..747 19:14:17 (0) ** WMI registry setup:

> >

.............................................................................

> > ..................... OK.

> > ..748 19:14:17 (0) ** WMI Service has no dependents:

> >

.............................................................................

> > .......... OK.

> > ..749 19:14:17 (0) ** RPCSS service:

> >

.............................................................................

> > .......................... OK (Already started).

> > ..750 19:14:17 (0) ** WINMGMT service:

> >

.............................................................................

> > ........................ OK (Successfully started).

> > ..751 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..752 19:14:17 (0) ** WMI service DCOM setup:

> >

.............................................................................

> > ................. OK.

> > ..753 19:14:17 (0) ** WMI components DCOM registrations:

> >

.............................................................................

> > ...... OK.

> > ..754 19:14:17 (0) ** WMI ProgID registrations:

> >

.............................................................................

> > ............... OK.

> > ..755 19:14:17 (0) ** WMI provider DCOM registrations:

> >

.............................................................................

> > ........ OK.

> > ..756 19:14:17 (0) ** WMI provider CIM registrations:

> >

.............................................................................

> > ......... OK.

> > ..757 19:14:17 (0) ** WMI provider CLSIDs:

> >

.............................................................................

> > .................... OK.

> > ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

> >

.............................................................................

> > ..... OK.

> > ..759 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..760 19:14:17 (0) ** Overall security status:

> >

.............................................................................

> > ................ NOT TESTED.

> > ..761 19:14:17 (0) ** - Started at

> >

'Root' ---------------------------------------------------------------------

> > -----------------------------------------

> > ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

> >

.............................................................................

> > .......... NONE.

> > ..763 19:14:17 (0) ** WMI TIMER instruction(s):

> >

.............................................................................

> > ............... NONE.

> > ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

> >

.............................................................................

> > ................. NOT AVAILABLE.

> > ..765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

> > (ADAP) process to resynchronize

> > ..766 19:14:17 (0) ** the performance counters with the WMI

performance

> > classes with the following commands:

> > ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

> > ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF

'

> > ..769 19:14:17 (0) ** The ADAP process logs informative events in the

> > Windows NT event log.

> > ..770 19:14:17 (0) ** More information can be found on MSDN at:

> > ..771 19:14:17 (0) **

> >

http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

> > ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for

the

> > following namespaces: .......................................... 1

ERROR(S)!

> > ..773 19:14:17 (0) ** - Root, 0x80041014 -

(WBEM_E_INITIALIZATION_FAILURE)

> > Component such as a provider failed to initialize for internal reasons.

> > ..774 19:14:17 (0) **

> > ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the

following

> > namespaces: .................................................. 5

ERROR(S)!

> > ..776 19:14:17 (0) ** - Root, 0x80041014 -

(WBEM_E_INITIALIZATION_FAILURE)

> > Component such as a provider failed to initialize for internal reasons.

> > ..777 19:14:17 (0) ** - Root, 0x80041014 -

(WBEM_E_INITIALIZATION_FAILURE)

> > Component such as a provider failed to initialize for internal reasons.

> > ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

> > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > initialize for internal reasons.

> > ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

> > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > initialize for internal reasons.

> > ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

> > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > initialize for internal reasons.

> > ..781 19:14:17 (0) **

> > ..782 19:14:17 (0) ** WMI GET operations:

> >

.............................................................................

> > ..................... OK.

> > ..783 19:14:17 (0) ** WMI MOF representations:

> >

.............................................................................

> > ................ OK.

> > ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

> >

.............................................................................

> > ........ OK.

> > ..785 19:14:17 (0) ** WMI ENUMERATION operations:

> >

.............................................................................

> > ............. OK.

> > ..786 19:14:17 (0) ** WMI EXECQUERY operations:

> >

.............................................................................

> > ............... OK.

> > ..787 19:14:17 (0) ** WMI GET VALUE operations:

> >

.............................................................................

> > ............... OK.

> > ..788 19:14:17 (0) ** WMI WRITE operations:

> >

.............................................................................

> > ................... NOT TESTED.

> > ..789 19:14:17 (0) ** WMI PUT operations:

> >

.............................................................................

> > ..................... NOT TESTED.

> > ..790 19:14:17 (0) ** WMI DELETE operations:

> >

.............................................................................

> > .................. NOT TESTED.

> > ..791 19:14:17 (0) ** WMI static instances retrieved:

> >

.............................................................................

> > ......... 0.

> > ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

> >

.............................................................................

> > ........ 0.

> > ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

> > performance impact): ...................................................

0.

> > ..794 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..795 19:14:17 (0) **

> > ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

> > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > initialize for internal reasons

> > ..797 19:14:17 (0) ** => This error is typically a WMI system error. WMI

> > system errors can find their origin in:

> > ..798 19:14:17 (0) ** - Failing WMI system components (see any

missing

> > WMI system files or DCOM registration

> > ..799 19:14:17 (0) ** issues previously mentioned).

> > ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM

registration

> > issues previously mentioned).

> > ..801 19:14:17 (0) ** - a WMI repository corruption.

> > ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

> > 'WriteInRepository' parameter

> > ..803 19:14:17 (0) ** to validate the WMI repository operations.

> > ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with FULL

> > access to WMI EVERY namespaces of the computer before

> > ..805 19:14:17 (0) ** executing the WriteInRepository command.

To

> > write temporary data from the Root namespace, use:

> > ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

> > ..807 19:14:17 (0) ** - If the WriteInRepository command fails, while

> > being an Administrator with ALL accesses to ALL namespaces

> > ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

> > ..809 19:14:17 (0) ** Note: The WMI repository reconstruction

requires to

> > locate all MOF files needed to rebuild the repository,

> > ..810 19:14:17 (0) ** otherwise some applications may fail

after

> > the reconstruction.

> > ..811 19:14:17 (0) ** This can be achieved with the following

> > command:

> > ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

> > ..813 19:14:17 (0) ** Note: The repository reconstruction must be a

LAST

> > RESORT solution and ONLY after executing

> > ..814 19:14:17 (0) ** ALL fixes previously mentioned.

> > ..815 19:14:17 (2) !! WARNING: Static information stored by external

> > applications in the repository will be LOST! (i.e. SMS Inventory)

> > ..816 19:14:17 (0) **

> > ..817 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..818 19:14:17 (0) ** WMI Registry key setup:

> >

.............................................................................

> > ................. OK.

> > ..819 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder not

> > referenced in the Auto-Recovery list: ............................. 13

> > ERROR(S)!

> > ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> > ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> > ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> > ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> > ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> > ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> > ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> > ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> > ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> > ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> > ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

> > ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

> > ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

> > ..834 19:14:17 (0) ** => After fixing all other issues previously

mentioned,

> > if the WMI repository is rebuilt,

> > ..835 19:14:17 (0) ** the listed MOF file(s) will not be recompiled,

and

> > therefore the definition they contain

> > ..836 19:14:17 (0) ** will not be available in the WMI repository.

> > ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s)

with

> > the 'MOFCOMP.EXE ' command.

> > ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

> > Auto-Recovery list, make sure the

> > ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

> > ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

> > included AT SETUP in the auto-recovery process.

> > ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL

statements

> > (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the

auto-recovery

> > process.

> > ..842 19:14:17 (0) ** Refer to the list of MOF files below NOT

> > containing the '#PRAGMA AUTORECOVER' statement' for more information.

> > ..843 19:14:17 (0) **

> > ..844 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..845 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

> > AUTORECOVER' statement: ..............................................

14

> > FILE(S)!

> > ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> > ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> > ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> > ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> > ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> > ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> > ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> > ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> > ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> > ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> > ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

> > ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

> > ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

> > ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

> > ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in the

> > AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER'

> > statement.

> > ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed

MOF

> > files not included in the AUTO-RECOVERY LIST and

> > ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement

when

> > they are compiled the first time will NOT

> > ..864 19:14:17 (0) ** be recompiled during the repository

reconstruction.

> > ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of

the

> > AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

> > ..866 19:14:17 (0) ** is included and recompile the MOF/MFL

with

> > the following command:

> > ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

> > ..868 19:14:17 (0) **

> > ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains class

and

> > instance DELETE statements.

> > ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used to

> > UNinstall components and they should NOT be listed in the AUTORECOVERY

LIST

> > ..871 19:14:17 (0) ** and therefore they should NOT specify the

'#PRAGMA

> > AUTORECOVER' statement.

> > ..872 19:14:17 (0) ** Note: It happens that some MOF files do contain

> > DELETE statements for installation purposes to delete

> > ..873 19:14:17 (0) ** existing information before it is

recreated.

> > ..874 19:14:17 (0) **

> > ..875 19:14:17 (0) ** Note: It is also possible that the application

> > implemented its own recovery mechanism.

> > ..876 19:14:17 (0) ** In that case, no action is required. You

must

> > verify with the application vendor

> > ..877 19:14:17 (0) ** if the application has this capability

(i.e.

> > Microsoft SMS)

> > ..878 19:14:17 (0) **

> > ..879 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..880 19:14:17 (0) **

> > ..881 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..882 19:14:17 (0)

** ------------------------------------------------------

> > WMI REPORT:

END -----------------------------------------------------------

> > ..883 19:14:17 (0)

> >

** -------------------------------------------------------------------------

> > ---------------------------------------------------------

> > ..884 19:14:17 (0) **

> > ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could prevent

WMI

> > to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

> >

SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

> > .29.LOG' for details.

> > ..886 19:14:17 (0) **

> > ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010 at

> > 19:14 (W:30 E:16 S:1).

>

> -=========================================================================

==

> > ====

> >

> >

> >

> >

> >

> > "John John - MVP" wrote in message

> > news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

> >> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

> >> folder. Administrators and the System account should have Full Control

> >> on this folder.

> >>

> >> John

> >>

> >> jbclem wrote:

> >>> I'm trying to run msinfo32.exe, which is the System Information/System

> >>> Summary module. But I keep getting this response: "the connection to

> > could

> >>> not be established. Check to see that the network path name is

> > correct,

> >>> that you have sufficient permission to access Windows Management".

> >>>

> >>> All of the other modules (Hardware Resources, Components, etc...) give

> > the

> >>> same response. I've tried refreshing, but still the same response.

> > Looking

> >>> in the Event Viewer, there are plenty of errors that say "WinMgmt

cannot

> >>> open the repository file..." could that have something to do with

this.

> >>> But I have plenty of disk space and memory. These WinMgmt errors seem

> > to

> >>> have started a month ago.

> >>>

> >>> Can someone show me what's wrong here...the computer seems to be

working

> >>> normally, and I checked Services to see if I might have turned

something

> >>> off. I started Windows Management Instrumentation, in case that was

> >>> it...but no difference.

> >>>

> >>> John

> >>>

> >>>

> >

> >
 
J

jbclem

Rebooting didn't help.





"jbclem" wrote in message

news:8OVxn.133690$gF5.79182@newsfe13.iad...

> I've got DCOM enabled now. And just in case, I rebooted the computer.

But

> the problem still exists. Looking in the event viewer, the latest(a few

> minutes ago) WinMgmt error states: WinMgmt could not open the repository

> file. This could be due to insufficient security access to the

> "\System32\WBEM\Repository", insufficient disk space or

> insufficient memory.

>

> I checked the properties of the Repository folder, it was set to "do not

> share". I changed that to "share this folder" and checked the

permissions.

> All three were set to Allow.

>

> Checked the original problem, but it's still there. I'm going to reboot

> again, just in case.

>

> Any other thoughts on this?

>

>

>

>

>

>

>

>

>

> "John John - MVP" wrote in message

> news:Ouyo$EJ3KHA.1016@TK2MSFTNGP02.phx.gbl...

> > On Windows 2000 the Dcomcnfg command returns a different GUI, see here:

> >

> >

>

http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/comdcom/dcom_enable.html

> >

> > or run this command instead to get to the Component Services snap-in:

> >

> > %windir%\System32\Com\Comexp.msc

> >

> > John

> >

> > jbclem wrote:

> > > I've installed and run WMIDiag v2.0_2000. It shows this:

> > >

> > > .737 19:14:17 (1) !! ERROR: DCOM Status:

> > >

>

.............................................................................

> > > ..................... ERROR!

> > > ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

computer

> is

> > > DISABLED.

> > > ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> > > ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> > > ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> > > ..742 19:14:17 (0) ** - Expanding 'Component Services' and

> 'Computers'

> > > nodes.

> > > ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> > > ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> > > ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

this

> > > computer' checkbox.

> > > ..746 19:14:17 (0) **

> > >

> > > I ran DCOMCNFG.exe but couldn't find the Component Services or

Computer

> > > nodes.

> > >

> > > Actually, here's the entire report...there are some more errors

towards

> the

> > > bottom.

> > >

========================================================================

> > > ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14,

2010

> at

> > > 19:14.

> > > ..698 19:14:17 (0) **

> > > ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

> > > reserved - January 2007.

> > > ..700 19:14:17 (0) **

> > > ..701 19:14:17 (0) ** This script is not supported under any Microsoft

> > > standard support program or service.

> > > ..702 19:14:17 (0) ** The script is provided AS IS without warranty of

> any

> > > kind. Microsoft further disclaims all

> > > ..703 19:14:17 (0) ** implied warranties including, without

limitation,

> any

> > > implied warranties of merchantability

> > > ..704 19:14:17 (0) ** or of fitness for a particular purpose. The

entire

> > > risk arising out of the use or performance

> > > ..705 19:14:17 (0) ** of the scripts and documentation remains with

you.

> In

> > > no event shall Microsoft, its authors,

> > > ..706 19:14:17 (0) ** or anyone else involved in the creation,

> production,

> > > or delivery of the script be liable for

> > > ..707 19:14:17 (0) ** any damages whatsoever (including, without

> limitation,

> > > damages for loss of business profits,

> > > ..708 19:14:17 (0) ** business interruption, loss of business

> information,

> > > or other pecuniary loss) arising out of

> > > ..709 19:14:17 (0) ** the use of or inability to use the script or

> > > documentation, even if Microsoft has been advised

> > > ..710 19:14:17 (0) ** of the possibility of such damages.

> > > ..711 19:14:17 (0) **

> > > ..712 19:14:17 (0) **

> > > ..713 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..714 19:14:17 (0)

> ** -----------------------------------------------------

> > > WMI REPORT:

> BEGIN ----------------------------------------------------------

> > > ..715 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..716 19:14:17 (0) **

> > > ..717 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit

> (2195) -

> > > User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

> > > ..719 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..720 19:14:17 (0) ** Environment:

> > >

>

.............................................................................

> > > ............................ OK..

> > > ..721 19:14:17 (0) ** There are no missing WMI system files:

> > >

>

.............................................................................

> > > .. OK.

> > > ..722 19:14:17 (0) ** There are no missing WMI repository files:

> > >

> ..........................................................................

> > > OK.

> > > ..723 19:14:17 (0) ** WMI repository state:

> > >

>

.............................................................................

> > > ................... N/A.

> > > ..724 19:14:17 (0) ** BEFORE running WMIDiag:

> > > ..725 19:14:17 (0) ** The WMI repository has a size of:

> > >

>

.............................................................................

> > > ....... 1 MB.

> > > ..726 19:14:17 (0) ** - Disk free space on 'C:':

> > >

>

.............................................................................

> > > .............. 2149 MB.

> > > ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> > > 3/12/2010 11:22:16 PM

> > > ..728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> > > 4/14/2010 7:02:40 PM

> > > ..729 19:14:17 (0) ** AFTER running WMIDiag:

> > > ..730 19:14:17 (0) ** The WMI repository has a size of:

> > >

>

.............................................................................

> > > ....... 1 MB.

> > > ..731 19:14:17 (0) ** - Disk free space on 'C:':

> > >

>

.............................................................................

> > > .............. 2149 MB.

> > > ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> > > 3/12/2010 11:22:16 PM

> > > ..733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> > > 4/14/2010 7:02:40 PM

> > > ..734 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..735 19:14:17 (0) ** Windows Firewall:

> > >

>

.............................................................................

> > > ....................... NOT INSTALLED.

> > > ..736 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..737 19:14:17 (1) !! ERROR: DCOM Status:

> > >

>

.............................................................................

> > > ..................... ERROR!

> > > ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

computer

> is

> > > DISABLED.

> > > ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> > > ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> > > ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> > > ..742 19:14:17 (0) ** - Expanding 'Component Services' and

> 'Computers'

> > > nodes.

> > > ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> > > ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> > > ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

this

> > > computer' checkbox.

> > > ..746 19:14:17 (0) **

> > > ..747 19:14:17 (0) ** WMI registry setup:

> > >

>

.............................................................................

> > > ..................... OK.

> > > ..748 19:14:17 (0) ** WMI Service has no dependents:

> > >

>

.............................................................................

> > > .......... OK.

> > > ..749 19:14:17 (0) ** RPCSS service:

> > >

>

.............................................................................

> > > .......................... OK (Already started).

> > > ..750 19:14:17 (0) ** WINMGMT service:

> > >

>

.............................................................................

> > > ........................ OK (Successfully started).

> > > ..751 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..752 19:14:17 (0) ** WMI service DCOM setup:

> > >

>

.............................................................................

> > > ................. OK.

> > > ..753 19:14:17 (0) ** WMI components DCOM registrations:

> > >

>

.............................................................................

> > > ...... OK.

> > > ..754 19:14:17 (0) ** WMI ProgID registrations:

> > >

>

.............................................................................

> > > ............... OK.

> > > ..755 19:14:17 (0) ** WMI provider DCOM registrations:

> > >

>

.............................................................................

> > > ........ OK.

> > > ..756 19:14:17 (0) ** WMI provider CIM registrations:

> > >

>

.............................................................................

> > > ......... OK.

> > > ..757 19:14:17 (0) ** WMI provider CLSIDs:

> > >

>

.............................................................................

> > > .................... OK.

> > > ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

> > >

>

.............................................................................

> > > ..... OK.

> > > ..759 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..760 19:14:17 (0) ** Overall security status:

> > >

>

.............................................................................

> > > ................ NOT TESTED.

> > > ..761 19:14:17 (0) ** - Started at

> > >

>

'Root' ---------------------------------------------------------------------

> > > -----------------------------------------

> > > ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

> > >

>

.............................................................................

> > > .......... NONE.

> > > ..763 19:14:17 (0) ** WMI TIMER instruction(s):

> > >

>

.............................................................................

> > > ............... NONE.

> > > ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

> > >

>

.............................................................................

> > > ................. NOT AVAILABLE.

> > > ..765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

> > > (ADAP) process to resynchronize

> > > ..766 19:14:17 (0) ** the performance counters with the WMI

> performance

> > > classes with the following commands:

> > > ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

> > > ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF

> '

> > > ..769 19:14:17 (0) ** The ADAP process logs informative events in

the

> > > Windows NT event log.

> > > ..770 19:14:17 (0) ** More information can be found on MSDN at:

> > > ..771 19:14:17 (0) **

> > >

>

http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

> > > ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for

> the

> > > following namespaces: .......................................... 1

> ERROR(S)!

> > > ..773 19:14:17 (0) ** - Root, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE)

> > > Component such as a provider failed to initialize for internal

reasons.

> > > ..774 19:14:17 (0) **

> > > ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the

> following

> > > namespaces: .................................................. 5

> ERROR(S)!

> > > ..776 19:14:17 (0) ** - Root, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE)

> > > Component such as a provider failed to initialize for internal

reasons.

> > > ..777 19:14:17 (0) ** - Root, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE)

> > > Component such as a provider failed to initialize for internal

reasons.

> > > ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

> > > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > > initialize for internal reasons.

> > > ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

> > > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > > initialize for internal reasons.

> > > ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

> > > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > > initialize for internal reasons.

> > > ..781 19:14:17 (0) **

> > > ..782 19:14:17 (0) ** WMI GET operations:

> > >

>

.............................................................................

> > > ..................... OK.

> > > ..783 19:14:17 (0) ** WMI MOF representations:

> > >

>

.............................................................................

> > > ................ OK.

> > > ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

> > >

>

.............................................................................

> > > ........ OK.

> > > ..785 19:14:17 (0) ** WMI ENUMERATION operations:

> > >

>

.............................................................................

> > > ............. OK.

> > > ..786 19:14:17 (0) ** WMI EXECQUERY operations:

> > >

>

.............................................................................

> > > ............... OK.

> > > ..787 19:14:17 (0) ** WMI GET VALUE operations:

> > >

>

.............................................................................

> > > ............... OK.

> > > ..788 19:14:17 (0) ** WMI WRITE operations:

> > >

>

.............................................................................

> > > ................... NOT TESTED.

> > > ..789 19:14:17 (0) ** WMI PUT operations:

> > >

>

.............................................................................

> > > ..................... NOT TESTED.

> > > ..790 19:14:17 (0) ** WMI DELETE operations:

> > >

>

.............................................................................

> > > .................. NOT TESTED.

> > > ..791 19:14:17 (0) ** WMI static instances retrieved:

> > >

>

.............................................................................

> > > ......... 0.

> > > ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

> > >

>

.............................................................................

> > > ........ 0.

> > > ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

> > > performance impact):

....................................................

> 0.

> > > ..794 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..795 19:14:17 (0) **

> > > ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

> > > (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> > > initialize for internal reasons

> > > ..797 19:14:17 (0) ** => This error is typically a WMI system error.

WMI

> > > system errors can find their origin in:

> > > ..798 19:14:17 (0) ** - Failing WMI system components (see any

> missing

> > > WMI system files or DCOM registration

> > > ..799 19:14:17 (0) ** issues previously mentioned).

> > > ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM

> registration

> > > issues previously mentioned).

> > > ..801 19:14:17 (0) ** - a WMI repository corruption.

> > > ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

> > > 'WriteInRepository' parameter

> > > ..803 19:14:17 (0) ** to validate the WMI repository operations.

> > > ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with

FULL

> > > access to WMI EVERY namespaces of the computer before

> > > ..805 19:14:17 (0) ** executing the WriteInRepository

command.

> To

> > > write temporary data from the Root namespace, use:

> > > ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

> > > ..807 19:14:17 (0) ** - If the WriteInRepository command fails,

while

> > > being an Administrator with ALL accesses to ALL namespaces

> > > ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

> > > ..809 19:14:17 (0) ** Note: The WMI repository reconstruction

> requires to

> > > locate all MOF files needed to rebuild the repository,

> > > ..810 19:14:17 (0) ** otherwise some applications may fail

> after

> > > the reconstruction.

> > > ..811 19:14:17 (0) ** This can be achieved with the following

> > > command:

> > > ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

> > > ..813 19:14:17 (0) ** Note: The repository reconstruction must be a

> LAST

> > > RESORT solution and ONLY after executing

> > > ..814 19:14:17 (0) ** ALL fixes previously mentioned.

> > > ..815 19:14:17 (2) !! WARNING: Static information stored by external

> > > applications in the repository will be LOST! (i.e. SMS Inventory)

> > > ..816 19:14:17 (0) **

> > > ..817 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..818 19:14:17 (0) ** WMI Registry key setup:

> > >

>

.............................................................................

> > > ................. OK.

> > > ..819 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder

not

> > > referenced in the Auto-Recovery list: ............................. 13

> > > ERROR(S)!

> > > ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> > > ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> > > ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> > > ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> > > ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> > > ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> > > ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> > > ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> > > ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> > > ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> > > ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

> > > ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

> > > ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

> > > ..834 19:14:17 (0) ** => After fixing all other issues previously

> mentioned,

> > > if the WMI repository is rebuilt,

> > > ..835 19:14:17 (0) ** the listed MOF file(s) will not be

recompiled,

> and

> > > therefore the definition they contain

> > > ..836 19:14:17 (0) ** will not be available in the WMI repository.

> > > ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s)

> with

> > > the 'MOFCOMP.EXE ' command.

> > > ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

> > > Auto-Recovery list, make sure the

> > > ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

> > > ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

> > > included AT SETUP in the auto-recovery process.

> > > ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL

> statements

> > > (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the

> auto-recovery

> > > process.

> > > ..842 19:14:17 (0) ** Refer to the list of MOF files below

NOT

> > > containing the '#PRAGMA AUTORECOVER' statement' for more information.

> > > ..843 19:14:17 (0) **

> > > ..844 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..845 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

> > > AUTORECOVER' statement: ..............................................

> 14

> > > FILE(S)!

> > > ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> > > ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> > > ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> > > ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> > > ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> > > ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> > > ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> > > ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> > > ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> > > ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> > > ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

> > > ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

> > > ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

> > > ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

> > > ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in

the

> > > AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA

AUTORECOVER'

> > > statement.

> > > ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed

> MOF

> > > files not included in the AUTO-RECOVERY LIST and

> > > ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement

> when

> > > they are compiled the first time will NOT

> > > ..864 19:14:17 (0) ** be recompiled during the repository

> reconstruction.

> > > ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of

> the

> > > AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

> > > ..866 19:14:17 (0) ** is included and recompile the MOF/MFL

> with

> > > the following command:

> > > ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

> > > ..868 19:14:17 (0) **

> > > ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains

class

> and

> > > instance DELETE statements.

> > > ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used

to

> > > UNinstall components and they should NOT be listed in the AUTORECOVERY

> LIST

> > > ..871 19:14:17 (0) ** and therefore they should NOT specify the

> '#PRAGMA

> > > AUTORECOVER' statement.

> > > ..872 19:14:17 (0) ** Note: It happens that some MOF files do

contain

> > > DELETE statements for installation purposes to delete

> > > ..873 19:14:17 (0) ** existing information before it is

> recreated.

> > > ..874 19:14:17 (0) **

> > > ..875 19:14:17 (0) ** Note: It is also possible that the

application

> > > implemented its own recovery mechanism.

> > > ..876 19:14:17 (0) ** In that case, no action is required.

You

> must

> > > verify with the application vendor

> > > ..877 19:14:17 (0) ** if the application has this capability

> (i.e.

> > > Microsoft SMS)

> > > ..878 19:14:17 (0) **

> > > ..879 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..880 19:14:17 (0) **

> > > ..881 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..882 19:14:17 (0)

> ** ------------------------------------------------------

> > > WMI REPORT:

> END -----------------------------------------------------------

> > > ..883 19:14:17 (0)

> > >

>

** -------------------------------------------------------------------------

> > > ---------------------------------------------------------

> > > ..884 19:14:17 (0) **

> > > ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could

prevent

> WMI

> > > to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

> > >

>

SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

> > > .29.LOG' for details.

> > > ..886 19:14:17 (0) **

> > > ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010

at

> > > 19:14 (W:30 E:16 S:1).

> >

>

> -=========================================================================

> ==

> > > ====

> > >

> > >

> > >

> > >

> > >

> > > "John John - MVP" wrote in message

> > > news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

> > >> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

> > >> folder. Administrators and the System account should have Full

Control

> > >> on this folder.

> > >>

> > >> John

> > >>

> > >> jbclem wrote:

> > >>> I'm trying to run msinfo32.exe, which is the System

Information/System

> > >>> Summary module. But I keep getting this response: "the connection

to

> > > could

> > >>> not be established. Check to see that the network path name is

> > > correct,

> > >>> that you have sufficient permission to access Windows Management".

> > >>>

> > >>> All of the other modules (Hardware Resources, Components, etc...)

give

> > > the

> > >>> same response. I've tried refreshing, but still the same response.

> > > Looking

> > >>> in the Event Viewer, there are plenty of errors that say "WinMgmt

> cannot

> > >>> open the repository file..." could that have something to do with

> this.

> > >>> But I have plenty of disk space and memory. These WinMgmt errors

seem

> > > to

> > >>> have started a month ago.

> > >>>

> > >>> Can someone show me what's wrong here...the computer seems to be

> working

> > >>> normally, and I checked Services to see if I might have turned

> something

> > >>> off. I started Windows Management Instrumentation, in case that was

> > >>> it...but no difference.

> > >>>

> > >>> John

> > >>>

> > >>>

> > >

> > >

>

>

>
 
J

John John - MVP

msinfo32.exe gives "connection to could not be established..."???

First make sure that the Windows Management Instrumentation service is

set to Automatic start.



Are you running the command on a local machine or over the network? You

don't need to share the Repository folder, you need to look at the

Security tab in the folder's Properties (right click on the folder) and

make sure that you have sufficient permissions on the folder and its

contents.



John



jbclem wrote:

> I've got DCOM enabled now. And just in case, I rebooted the computer. But

> the problem still exists. Looking in the event viewer, the latest(a few

> minutes ago) WinMgmt error states: WinMgmt could not open the repository

> file. This could be due to insufficient security access to the

> "\System32\WBEM\Repository", insufficient disk space or

> insufficient memory.

>

> I checked the properties of the Repository folder, it was set to "do not

> share". I changed that to "share this folder" and checked the permissions.

> All three were set to Allow.

>

> Checked the original problem, but it's still there. I'm going to reboot

> again, just in case.

>

> Any other thoughts on this?

>

>

>

>

>

>

>

>

>

> "John John - MVP" wrote in message

> news:Ouyo$EJ3KHA.1016@TK2MSFTNGP02.phx.gbl...

>> On Windows 2000 the Dcomcnfg command returns a different GUI, see here:

>>

>>

> http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/comdcom/dcom_enable.html

>> or run this command instead to get to the Component Services snap-in:

>>

>> %windir%\System32\Com\Comexp.msc

>>

>> John

>>

>> jbclem wrote:

>>> I've installed and run WMIDiag v2.0_2000. It shows this:

>>>

>>> .737 19:14:17 (1) !! ERROR: DCOM Status:

>>>

> ............................................................................

>>> ..................... ERROR!

>>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer

> is

>>> DISABLED.

>>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

>>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

>>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

>>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

> 'Computers'

>>> nodes.

>>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

>>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

>>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

>>> computer' checkbox.

>>> ..746 19:14:17 (0) **

>>>

>>> I ran DCOMCNFG.exe but couldn't find the Component Services or Computer

>>> nodes.

>>>

>>> Actually, here's the entire report...there are some more errors towards

> the

>>> bottom.

>>> ========================================================================

>>> ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14, 2010

> at

>>> 19:14.

>>> ..698 19:14:17 (0) **

>>> ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

>>> reserved - January 2007.

>>> ..700 19:14:17 (0) **

>>> ..701 19:14:17 (0) ** This script is not supported under any Microsoft

>>> standard support program or service.

>>> ..702 19:14:17 (0) ** The script is provided AS IS without warranty of

> any

>>> kind. Microsoft further disclaims all

>>> ..703 19:14:17 (0) ** implied warranties including, without limitation,

> any

>>> implied warranties of merchantability

>>> ..704 19:14:17 (0) ** or of fitness for a particular purpose. The entire

>>> risk arising out of the use or performance

>>> ..705 19:14:17 (0) ** of the scripts and documentation remains with you.

> In

>>> no event shall Microsoft, its authors,

>>> ..706 19:14:17 (0) ** or anyone else involved in the creation,

> production,

>>> or delivery of the script be liable for

>>> ..707 19:14:17 (0) ** any damages whatsoever (including, without

> limitation,

>>> damages for loss of business profits,

>>> ..708 19:14:17 (0) ** business interruption, loss of business

> information,

>>> or other pecuniary loss) arising out of

>>> ..709 19:14:17 (0) ** the use of or inability to use the script or

>>> documentation, even if Microsoft has been advised

>>> ..710 19:14:17 (0) ** of the possibility of such damages.

>>> ..711 19:14:17 (0) **

>>> ..712 19:14:17 (0) **

>>> ..713 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..714 19:14:17 (0)

> ** -----------------------------------------------------

>>> WMI REPORT:

> BEGIN ----------------------------------------------------------

>>> ..715 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..716 19:14:17 (0) **

>>> ..717 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit

> (2195) -

>>> User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

>>> ..719 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..720 19:14:17 (0) ** Environment:

>>>

> ............................................................................

>>> ............................ OK..

>>> ..721 19:14:17 (0) ** There are no missing WMI system files:

>>>

> ............................................................................

>>> .. OK.

>>> ..722 19:14:17 (0) ** There are no missing WMI repository files:

>>>

> ..........................................................................

>>> OK.

>>> ..723 19:14:17 (0) ** WMI repository state:

>>>

> ............................................................................

>>> ................... N/A.

>>> ..724 19:14:17 (0) ** BEFORE running WMIDiag:

>>> ..725 19:14:17 (0) ** The WMI repository has a size of:

>>>

> ............................................................................

>>> ....... 1 MB.

>>> ..726 19:14:17 (0) ** - Disk free space on 'C:':

>>>

> ............................................................................

>>> .............. 2149 MB.

>>> ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

>>> 3/12/2010 11:22:16 PM

>>> ..728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

>>> 4/14/2010 7:02:40 PM

>>> ..729 19:14:17 (0) ** AFTER running WMIDiag:

>>> ..730 19:14:17 (0) ** The WMI repository has a size of:

>>>

> ............................................................................

>>> ....... 1 MB.

>>> ..731 19:14:17 (0) ** - Disk free space on 'C:':

>>>

> ............................................................................

>>> .............. 2149 MB.

>>> ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

>>> 3/12/2010 11:22:16 PM

>>> ..733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

>>> 4/14/2010 7:02:40 PM

>>> ..734 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..735 19:14:17 (0) ** Windows Firewall:

>>>

> ............................................................................

>>> ....................... NOT INSTALLED.

>>> ..736 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..737 19:14:17 (1) !! ERROR: DCOM Status:

>>>

> ............................................................................

>>> ..................... ERROR!

>>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this computer

> is

>>> DISABLED.

>>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

>>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

>>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

>>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

> 'Computers'

>>> nodes.

>>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

>>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

>>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on this

>>> computer' checkbox.

>>> ..746 19:14:17 (0) **

>>> ..747 19:14:17 (0) ** WMI registry setup:

>>>

> ............................................................................

>>> ..................... OK.

>>> ..748 19:14:17 (0) ** WMI Service has no dependents:

>>>

> ............................................................................

>>> .......... OK.

>>> ..749 19:14:17 (0) ** RPCSS service:

>>>

> ............................................................................

>>> .......................... OK (Already started).

>>> ..750 19:14:17 (0) ** WINMGMT service:

>>>

> ............................................................................

>>> ........................ OK (Successfully started).

>>> ..751 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..752 19:14:17 (0) ** WMI service DCOM setup:

>>>

> ............................................................................

>>> ................. OK.

>>> ..753 19:14:17 (0) ** WMI components DCOM registrations:

>>>

> ............................................................................

>>> ...... OK.

>>> ..754 19:14:17 (0) ** WMI ProgID registrations:

>>>

> ............................................................................

>>> ............... OK.

>>> ..755 19:14:17 (0) ** WMI provider DCOM registrations:

>>>

> ............................................................................

>>> ........ OK.

>>> ..756 19:14:17 (0) ** WMI provider CIM registrations:

>>>

> ............................................................................

>>> ......... OK.

>>> ..757 19:14:17 (0) ** WMI provider CLSIDs:

>>>

> ............................................................................

>>> .................... OK.

>>> ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

>>>

> ............................................................................

>>> ..... OK.

>>> ..759 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..760 19:14:17 (0) ** Overall security status:

>>>

> ............................................................................

>>> ................ NOT TESTED.

>>> ..761 19:14:17 (0) ** - Started at

>>>

> 'Root' ---------------------------------------------------------------------

>>> -----------------------------------------

>>> ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

>>>

> ............................................................................

>>> .......... NONE.

>>> ..763 19:14:17 (0) ** WMI TIMER instruction(s):

>>>

> ............................................................................

>>> ............... NONE.

>>> ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

>>>

> ............................................................................

>>> ................. NOT AVAILABLE.

>>> ..765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

>>> (ADAP) process to resynchronize

>>> ..766 19:14:17 (0) ** the performance counters with the WMI

> performance

>>> classes with the following commands:

>>> ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

>>> ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF

> '

>>> ..769 19:14:17 (0) ** The ADAP process logs informative events in the

>>> Windows NT event log.

>>> ..770 19:14:17 (0) ** More information can be found on MSDN at:

>>> ..771 19:14:17 (0) **

>>>

> http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

>>> ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for

> the

>>> following namespaces: .......................................... 1

> ERROR(S)!

>>> ..773 19:14:17 (0) ** - Root, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE)

>>> Component such as a provider failed to initialize for internal reasons.

>>> ..774 19:14:17 (0) **

>>> ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the

> following

>>> namespaces: .................................................. 5

> ERROR(S)!

>>> ..776 19:14:17 (0) ** - Root, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE)

>>> Component such as a provider failed to initialize for internal reasons.

>>> ..777 19:14:17 (0) ** - Root, 0x80041014 -

> (WBEM_E_INITIALIZATION_FAILURE)

>>> Component such as a provider failed to initialize for internal reasons.

>>> ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>> initialize for internal reasons.

>>> ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>> initialize for internal reasons.

>>> ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>> initialize for internal reasons.

>>> ..781 19:14:17 (0) **

>>> ..782 19:14:17 (0) ** WMI GET operations:

>>>

> ............................................................................

>>> ..................... OK.

>>> ..783 19:14:17 (0) ** WMI MOF representations:

>>>

> ............................................................................

>>> ................ OK.

>>> ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

>>>

> ............................................................................

>>> ........ OK.

>>> ..785 19:14:17 (0) ** WMI ENUMERATION operations:

>>>

> ............................................................................

>>> ............. OK.

>>> ..786 19:14:17 (0) ** WMI EXECQUERY operations:

>>>

> ............................................................................

>>> ............... OK.

>>> ..787 19:14:17 (0) ** WMI GET VALUE operations:

>>>

> ............................................................................

>>> ............... OK.

>>> ..788 19:14:17 (0) ** WMI WRITE operations:

>>>

> ............................................................................

>>> ................... NOT TESTED.

>>> ..789 19:14:17 (0) ** WMI PUT operations:

>>>

> ............................................................................

>>> ..................... NOT TESTED.

>>> ..790 19:14:17 (0) ** WMI DELETE operations:

>>>

> ............................................................................

>>> .................. NOT TESTED.

>>> ..791 19:14:17 (0) ** WMI static instances retrieved:

>>>

> ............................................................................

>>> ......... 0.

>>> ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

>>>

> ............................................................................

>>> ........ 0.

>>> ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

>>> performance impact): ...................................................

> 0.

>>> ..794 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..795 19:14:17 (0) **

>>> ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>> initialize for internal reasons

>>> ..797 19:14:17 (0) ** => This error is typically a WMI system error. WMI

>>> system errors can find their origin in:

>>> ..798 19:14:17 (0) ** - Failing WMI system components (see any

> missing

>>> WMI system files or DCOM registration

>>> ..799 19:14:17 (0) ** issues previously mentioned).

>>> ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM

> registration

>>> issues previously mentioned).

>>> ..801 19:14:17 (0) ** - a WMI repository corruption.

>>> ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

>>> 'WriteInRepository' parameter

>>> ..803 19:14:17 (0) ** to validate the WMI repository operations.

>>> ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with FULL

>>> access to WMI EVERY namespaces of the computer before

>>> ..805 19:14:17 (0) ** executing the WriteInRepository command.

> To

>>> write temporary data from the Root namespace, use:

>>> ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

>>> ..807 19:14:17 (0) ** - If the WriteInRepository command fails, while

>>> being an Administrator with ALL accesses to ALL namespaces

>>> ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

>>> ..809 19:14:17 (0) ** Note: The WMI repository reconstruction

> requires to

>>> locate all MOF files needed to rebuild the repository,

>>> ..810 19:14:17 (0) ** otherwise some applications may fail

> after

>>> the reconstruction.

>>> ..811 19:14:17 (0) ** This can be achieved with the following

>>> command:

>>> ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

>>> ..813 19:14:17 (0) ** Note: The repository reconstruction must be a

> LAST

>>> RESORT solution and ONLY after executing

>>> ..814 19:14:17 (0) ** ALL fixes previously mentioned.

>>> ..815 19:14:17 (2) !! WARNING: Static information stored by external

>>> applications in the repository will be LOST! (i.e. SMS Inventory)

>>> ..816 19:14:17 (0) **

>>> ..817 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..818 19:14:17 (0) ** WMI Registry key setup:

>>>

> ............................................................................

>>> ................. OK.

>>> ..819 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder not

>>> referenced in the Auto-Recovery list: ............................. 13

>>> ERROR(S)!

>>> ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

>>> ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

>>> ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

>>> ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

>>> ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

>>> ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

>>> ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

>>> ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

>>> ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

>>> ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

>>> ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

>>> ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

>>> ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

>>> ..834 19:14:17 (0) ** => After fixing all other issues previously

> mentioned,

>>> if the WMI repository is rebuilt,

>>> ..835 19:14:17 (0) ** the listed MOF file(s) will not be recompiled,

> and

>>> therefore the definition they contain

>>> ..836 19:14:17 (0) ** will not be available in the WMI repository.

>>> ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s)

> with

>>> the 'MOFCOMP.EXE ' command.

>>> ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

>>> Auto-Recovery list, make sure the

>>> ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

>>> ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

>>> included AT SETUP in the auto-recovery process.

>>> ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL

> statements

>>> (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the

> auto-recovery

>>> process.

>>> ..842 19:14:17 (0) ** Refer to the list of MOF files below NOT

>>> containing the '#PRAGMA AUTORECOVER' statement' for more information.

>>> ..843 19:14:17 (0) **

>>> ..844 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..845 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

>>> AUTORECOVER' statement: ..............................................

> 14

>>> FILE(S)!

>>> ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

>>> ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

>>> ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

>>> ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

>>> ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

>>> ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

>>> ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

>>> ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

>>> ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

>>> ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

>>> ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

>>> ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

>>> ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

>>> ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

>>> ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in the

>>> AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER'

>>> statement.

>>> ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed

> MOF

>>> files not included in the AUTO-RECOVERY LIST and

>>> ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement

> when

>>> they are compiled the first time will NOT

>>> ..864 19:14:17 (0) ** be recompiled during the repository

> reconstruction.

>>> ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of

> the

>>> AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

>>> ..866 19:14:17 (0) ** is included and recompile the MOF/MFL

> with

>>> the following command:

>>> ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

>>> ..868 19:14:17 (0) **

>>> ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains class

> and

>>> instance DELETE statements.

>>> ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used to

>>> UNinstall components and they should NOT be listed in the AUTORECOVERY

> LIST

>>> ..871 19:14:17 (0) ** and therefore they should NOT specify the

> '#PRAGMA

>>> AUTORECOVER' statement.

>>> ..872 19:14:17 (0) ** Note: It happens that some MOF files do contain

>>> DELETE statements for installation purposes to delete

>>> ..873 19:14:17 (0) ** existing information before it is

> recreated.

>>> ..874 19:14:17 (0) **

>>> ..875 19:14:17 (0) ** Note: It is also possible that the application

>>> implemented its own recovery mechanism.

>>> ..876 19:14:17 (0) ** In that case, no action is required. You

> must

>>> verify with the application vendor

>>> ..877 19:14:17 (0) ** if the application has this capability

> (i.e.

>>> Microsoft SMS)

>>> ..878 19:14:17 (0) **

>>> ..879 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..880 19:14:17 (0) **

>>> ..881 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..882 19:14:17 (0)

> ** ------------------------------------------------------

>>> WMI REPORT:

> END -----------------------------------------------------------

>>> ..883 19:14:17 (0)

>>>

> ** -------------------------------------------------------------------------

>>> ---------------------------------------------------------

>>> ..884 19:14:17 (0) **

>>> ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could prevent

> WMI

>>> to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

>>>

> SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

>>> .29.LOG' for details.

>>> ..886 19:14:17 (0) **

>>> ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010 at

>>> 19:14 (W:30 E:16 S:1).

>> -=========================================================================

> ==

>>> ====

>>>

>>>

>>>

>>>

>>>

>>> "John John - MVP" wrote in message

>>> news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

>>>> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

>>>> folder. Administrators and the System account should have Full Control

>>>> on this folder.

>>>>

>>>> John

>>>>

>>>> jbclem wrote:

>>>>> I'm trying to run msinfo32.exe, which is the System Information/System

>>>>> Summary module. But I keep getting this response: "the connection to

>>> could

>>>>> not be established. Check to see that the network path name is

>>> correct,

>>>>> that you have sufficient permission to access Windows Management".

>>>>>

>>>>> All of the other modules (Hardware Resources, Components, etc...) give

>>> the

>>>>> same response. I've tried refreshing, but still the same response.

>>> Looking

>>>>> in the Event Viewer, there are plenty of errors that say "WinMgmt

> cannot

>>>>> open the repository file..." could that have something to do with

> this.

>>>>> But I have plenty of disk space and memory. These WinMgmt errors seem

>>> to

>>>>> have started a month ago.

>>>>>

>>>>> Can someone show me what's wrong here...the computer seems to be

> working

>>>>> normally, and I checked Services to see if I might have turned

> something

>>>>> off. I started Windows Management Instrumentation, in case that was

>>>>> it...but no difference.

>>>>>

>>>>> John

>>>>>

>>>>>

>>>

>

>
 
J

jbclem

Windows Management Instrumentation service is set to automatic start. But

it isn't starting automatically. I can start it, and the service status

(under properties) will list it as Started for about 5 seconds, then that

changes to Stopped.



About sharing the Repository folder, I didn't think it needed to be shared,

but that was the only way to active the permissions tab so I tried it. I

have two computers on a LAN, but I've only used sharing to be able to

transfer files back and forth.



When I right click on the folder and open Properties, there are only two

tabs: General and Sharing. Is there a way to activate the Security tab and

make it visible under Properties? Also, there are three files in the

Repository folder and their Properties only show one tab: General.





"John John - MVP" wrote in message

news:u%23MJfrV3KHA.4752@TK2MSFTNGP02.phx.gbl...

> First make sure that the Windows Management Instrumentation service is

> set to Automatic start.

>

> Are you running the command on a local machine or over the network? You

> don't need to share the Repository folder, you need to look at the

> Security tab in the folder's Properties (right click on the folder) and

> make sure that you have sufficient permissions on the folder and its

> contents.

>

> John

>

> jbclem wrote:

> > I've got DCOM enabled now. And just in case, I rebooted the computer.

But

> > the problem still exists. Looking in the event viewer, the latest(a few

> > minutes ago) WinMgmt error states: WinMgmt could not open the repository

> > file. This could be due to insufficient security access to the

> > "\System32\WBEM\Repository", insufficient disk space or

> > insufficient memory.

> >

> > I checked the properties of the Repository folder, it was set to "do not

> > share". I changed that to "share this folder" and checked the

permissions.

> > All three were set to Allow.

> >

> > Checked the original problem, but it's still there. I'm going to reboot

> > again, just in case.

> >

> > Any other thoughts on this?

> >

> >

> >

> >

> >

> >

> >

> >

> >

> > "John John - MVP" wrote in message

> > news:Ouyo$EJ3KHA.1016@TK2MSFTNGP02.phx.gbl...

> >> On Windows 2000 the Dcomcnfg command returns a different GUI, see here:

> >>

> >>

> >

http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/comdcom/dcom_enable.html

> >> or run this command instead to get to the Component Services snap-in:

> >>

> >> %windir%\System32\Com\Comexp.msc

> >>

> >> John

> >>

> >> jbclem wrote:

> >>> I've installed and run WMIDiag v2.0_2000. It shows this:

> >>>

> >>> .737 19:14:17 (1) !! ERROR: DCOM Status:

> >>>

> >

.............................................................................

> >>> ..................... ERROR!

> >>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

computer

> > is

> >>> DISABLED.

> >>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> >>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> >>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> >>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

> > 'Computers'

> >>> nodes.

> >>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> >>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> >>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

this

> >>> computer' checkbox.

> >>> ..746 19:14:17 (0) **

> >>>

> >>> I ran DCOMCNFG.exe but couldn't find the Component Services or

Computer

> >>> nodes.

> >>>

> >>> Actually, here's the entire report...there are some more errors

towards

> > the

> >>> bottom.

> >>>

========================================================================

> >>> ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14,

2010

> > at

> >>> 19:14.

> >>> ..698 19:14:17 (0) **

> >>> ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

> >>> reserved - January 2007.

> >>> ..700 19:14:17 (0) **

> >>> ..701 19:14:17 (0) ** This script is not supported under any Microsoft

> >>> standard support program or service.

> >>> ..702 19:14:17 (0) ** The script is provided AS IS without warranty of

> > any

> >>> kind. Microsoft further disclaims all

> >>> ..703 19:14:17 (0) ** implied warranties including, without

limitation,

> > any

> >>> implied warranties of merchantability

> >>> ..704 19:14:17 (0) ** or of fitness for a particular purpose. The

entire

> >>> risk arising out of the use or performance

> >>> ..705 19:14:17 (0) ** of the scripts and documentation remains with

you.

> > In

> >>> no event shall Microsoft, its authors,

> >>> ..706 19:14:17 (0) ** or anyone else involved in the creation,

> > production,

> >>> or delivery of the script be liable for

> >>> ..707 19:14:17 (0) ** any damages whatsoever (including, without

> > limitation,

> >>> damages for loss of business profits,

> >>> ..708 19:14:17 (0) ** business interruption, loss of business

> > information,

> >>> or other pecuniary loss) arising out of

> >>> ..709 19:14:17 (0) ** the use of or inability to use the script or

> >>> documentation, even if Microsoft has been advised

> >>> ..710 19:14:17 (0) ** of the possibility of such damages.

> >>> ..711 19:14:17 (0) **

> >>> ..712 19:14:17 (0) **

> >>> ..713 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..714 19:14:17 (0)

> > ** -----------------------------------------------------

> >>> WMI REPORT:

> > BEGIN ----------------------------------------------------------

> >>> ..715 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..716 19:14:17 (0) **

> >>> ..717 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit

> > (2195) -

> >>> User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

> >>> ..719 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..720 19:14:17 (0) ** Environment:

> >>>

> >

.............................................................................

> >>> ............................ OK..

> >>> ..721 19:14:17 (0) ** There are no missing WMI system files:

> >>>

> >

.............................................................................

> >>> .. OK.

> >>> ..722 19:14:17 (0) ** There are no missing WMI repository files:

> >>>

> >

...........................................................................

> >>> OK.

> >>> ..723 19:14:17 (0) ** WMI repository state:

> >>>

> >

.............................................................................

> >>> ................... N/A.

> >>> ..724 19:14:17 (0) ** BEFORE running WMIDiag:

> >>> ..725 19:14:17 (0) ** The WMI repository has a size of:

> >>>

> >

.............................................................................

> >>> ....... 1 MB.

> >>> ..726 19:14:17 (0) ** - Disk free space on 'C:':

> >>>

> >

.............................................................................

> >>> .............. 2149 MB.

> >>> ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> >>> 3/12/2010 11:22:16 PM

> >>> ..728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> >>> 4/14/2010 7:02:40 PM

> >>> ..729 19:14:17 (0) ** AFTER running WMIDiag:

> >>> ..730 19:14:17 (0) ** The WMI repository has a size of:

> >>>

> >

.............................................................................

> >>> ....... 1 MB.

> >>> ..731 19:14:17 (0) ** - Disk free space on 'C:':

> >>>

> >

.............................................................................

> >>> .............. 2149 MB.

> >>> ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

> >>> 3/12/2010 11:22:16 PM

> >>> ..733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

> >>> 4/14/2010 7:02:40 PM

> >>> ..734 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..735 19:14:17 (0) ** Windows Firewall:

> >>>

> >

.............................................................................

> >>> ....................... NOT INSTALLED.

> >>> ..736 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..737 19:14:17 (1) !! ERROR: DCOM Status:

> >>>

> >

.............................................................................

> >>> ..................... ERROR!

> >>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

computer

> > is

> >>> DISABLED.

> >>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

> >>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

> >>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

> >>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

> > 'Computers'

> >>> nodes.

> >>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

> >>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

> >>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

this

> >>> computer' checkbox.

> >>> ..746 19:14:17 (0) **

> >>> ..747 19:14:17 (0) ** WMI registry setup:

> >>>

> >

.............................................................................

> >>> ..................... OK.

> >>> ..748 19:14:17 (0) ** WMI Service has no dependents:

> >>>

> >

.............................................................................

> >>> .......... OK.

> >>> ..749 19:14:17 (0) ** RPCSS service:

> >>>

> >

.............................................................................

> >>> .......................... OK (Already started).

> >>> ..750 19:14:17 (0) ** WINMGMT service:

> >>>

> >

.............................................................................

> >>> ........................ OK (Successfully started).

> >>> ..751 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..752 19:14:17 (0) ** WMI service DCOM setup:

> >>>

> >

.............................................................................

> >>> ................. OK.

> >>> ..753 19:14:17 (0) ** WMI components DCOM registrations:

> >>>

> >

.............................................................................

> >>> ...... OK.

> >>> ..754 19:14:17 (0) ** WMI ProgID registrations:

> >>>

> >

.............................................................................

> >>> ............... OK.

> >>> ..755 19:14:17 (0) ** WMI provider DCOM registrations:

> >>>

> >

.............................................................................

> >>> ........ OK.

> >>> ..756 19:14:17 (0) ** WMI provider CIM registrations:

> >>>

> >

.............................................................................

> >>> ......... OK.

> >>> ..757 19:14:17 (0) ** WMI provider CLSIDs:

> >>>

> >

.............................................................................

> >>> .................... OK.

> >>> ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

> >>>

> >

.............................................................................

> >>> ..... OK.

> >>> ..759 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..760 19:14:17 (0) ** Overall security status:

> >>>

> >

.............................................................................

> >>> ................ NOT TESTED.

> >>> ..761 19:14:17 (0) ** - Started at

> >>>

> >

'Root' ---------------------------------------------------------------------

> >>> -----------------------------------------

> >>> ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

> >>>

> >

.............................................................................

> >>> .......... NONE.

> >>> ..763 19:14:17 (0) ** WMI TIMER instruction(s):

> >>>

> >

.............................................................................

> >>> ............... NONE.

> >>> ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

> >>>

> >

.............................................................................

> >>> ................. NOT AVAILABLE.

> >>> ..765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

> >>> (ADAP) process to resynchronize

> >>> ..766 19:14:17 (0) ** the performance counters with the WMI

> > performance

> >>> classes with the following commands:

> >>> ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

> >>> ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF

> > '

> >>> ..769 19:14:17 (0) ** The ADAP process logs informative events in

the

> >>> Windows NT event log.

> >>> ..770 19:14:17 (0) ** More information can be found on MSDN at:

> >>> ..771 19:14:17 (0) **

> >>>

> >

http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

> >>> ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for

> > the

> >>> following namespaces: .......................................... 1

> > ERROR(S)!

> >>> ..773 19:14:17 (0) ** - Root, 0x80041014 -

> > (WBEM_E_INITIALIZATION_FAILURE)

> >>> Component such as a provider failed to initialize for internal

reasons.

> >>> ..774 19:14:17 (0) **

> >>> ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the

> > following

> >>> namespaces: .................................................. 5

> > ERROR(S)!

> >>> ..776 19:14:17 (0) ** - Root, 0x80041014 -

> > (WBEM_E_INITIALIZATION_FAILURE)

> >>> Component such as a provider failed to initialize for internal

reasons.

> >>> ..777 19:14:17 (0) ** - Root, 0x80041014 -

> > (WBEM_E_INITIALIZATION_FAILURE)

> >>> Component such as a provider failed to initialize for internal

reasons.

> >>> ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> >>> initialize for internal reasons.

> >>> ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> >>> initialize for internal reasons.

> >>> ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> >>> initialize for internal reasons.

> >>> ..781 19:14:17 (0) **

> >>> ..782 19:14:17 (0) ** WMI GET operations:

> >>>

> >

.............................................................................

> >>> ..................... OK.

> >>> ..783 19:14:17 (0) ** WMI MOF representations:

> >>>

> >

.............................................................................

> >>> ................ OK.

> >>> ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

> >>>

> >

.............................................................................

> >>> ........ OK.

> >>> ..785 19:14:17 (0) ** WMI ENUMERATION operations:

> >>>

> >

.............................................................................

> >>> ............. OK.

> >>> ..786 19:14:17 (0) ** WMI EXECQUERY operations:

> >>>

> >

.............................................................................

> >>> ............... OK.

> >>> ..787 19:14:17 (0) ** WMI GET VALUE operations:

> >>>

> >

.............................................................................

> >>> ............... OK.

> >>> ..788 19:14:17 (0) ** WMI WRITE operations:

> >>>

> >

.............................................................................

> >>> ................... NOT TESTED.

> >>> ..789 19:14:17 (0) ** WMI PUT operations:

> >>>

> >

.............................................................................

> >>> ..................... NOT TESTED.

> >>> ..790 19:14:17 (0) ** WMI DELETE operations:

> >>>

> >

.............................................................................

> >>> .................. NOT TESTED.

> >>> ..791 19:14:17 (0) ** WMI static instances retrieved:

> >>>

> >

.............................................................................

> >>> ......... 0.

> >>> ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

> >>>

> >

.............................................................................

> >>> ........ 0.

> >>> ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

> >>> performance impact):

....................................................

> > 0.

> >>> ..794 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..795 19:14:17 (0) **

> >>> ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

> >>> initialize for internal reasons

> >>> ..797 19:14:17 (0) ** => This error is typically a WMI system error.

WMI

> >>> system errors can find their origin in:

> >>> ..798 19:14:17 (0) ** - Failing WMI system components (see any

> > missing

> >>> WMI system files or DCOM registration

> >>> ..799 19:14:17 (0) ** issues previously mentioned).

> >>> ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM

> > registration

> >>> issues previously mentioned).

> >>> ..801 19:14:17 (0) ** - a WMI repository corruption.

> >>> ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

> >>> 'WriteInRepository' parameter

> >>> ..803 19:14:17 (0) ** to validate the WMI repository operations.

> >>> ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with

FULL

> >>> access to WMI EVERY namespaces of the computer before

> >>> ..805 19:14:17 (0) ** executing the WriteInRepository

command.

> > To

> >>> write temporary data from the Root namespace, use:

> >>> ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

> >>> ..807 19:14:17 (0) ** - If the WriteInRepository command fails,

while

> >>> being an Administrator with ALL accesses to ALL namespaces

> >>> ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

> >>> ..809 19:14:17 (0) ** Note: The WMI repository reconstruction

> > requires to

> >>> locate all MOF files needed to rebuild the repository,

> >>> ..810 19:14:17 (0) ** otherwise some applications may fail

> > after

> >>> the reconstruction.

> >>> ..811 19:14:17 (0) ** This can be achieved with the following

> >>> command:

> >>> ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

> >>> ..813 19:14:17 (0) ** Note: The repository reconstruction must be a

> > LAST

> >>> RESORT solution and ONLY after executing

> >>> ..814 19:14:17 (0) ** ALL fixes previously mentioned.

> >>> ..815 19:14:17 (2) !! WARNING: Static information stored by external

> >>> applications in the repository will be LOST! (i.e. SMS Inventory)

> >>> ..816 19:14:17 (0) **

> >>> ..817 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..818 19:14:17 (0) ** WMI Registry key setup:

> >>>

> >

.............................................................................

> >>> ................. OK.

> >>> ..819 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder

not

> >>> referenced in the Auto-Recovery list: ............................. 13

> >>> ERROR(S)!

> >>> ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> >>> ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> >>> ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> >>> ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> >>> ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> >>> ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> >>> ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> >>> ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> >>> ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> >>> ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> >>> ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

> >>> ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

> >>> ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

> >>> ..834 19:14:17 (0) ** => After fixing all other issues previously

> > mentioned,

> >>> if the WMI repository is rebuilt,

> >>> ..835 19:14:17 (0) ** the listed MOF file(s) will not be

recompiled,

> > and

> >>> therefore the definition they contain

> >>> ..836 19:14:17 (0) ** will not be available in the WMI repository.

> >>> ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s)

> > with

> >>> the 'MOFCOMP.EXE ' command.

> >>> ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

> >>> Auto-Recovery list, make sure the

> >>> ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

> >>> ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

> >>> included AT SETUP in the auto-recovery process.

> >>> ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL

> > statements

> >>> (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the

> > auto-recovery

> >>> process.

> >>> ..842 19:14:17 (0) ** Refer to the list of MOF files below

NOT

> >>> containing the '#PRAGMA AUTORECOVER' statement' for more information.

> >>> ..843 19:14:17 (0) **

> >>> ..844 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..845 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

> >>> AUTORECOVER' statement: ..............................................

> > 14

> >>> FILE(S)!

> >>> ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

> >>> ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

> >>> ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

> >>> ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

> >>> ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

> >>> ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

> >>> ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

> >>> ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

> >>> ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

> >>> ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

> >>> ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

> >>> ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

> >>> ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

> >>> ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

> >>> ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in

the

> >>> AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA

AUTORECOVER'

> >>> statement.

> >>> ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed

> > MOF

> >>> files not included in the AUTO-RECOVERY LIST and

> >>> ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement

> > when

> >>> they are compiled the first time will NOT

> >>> ..864 19:14:17 (0) ** be recompiled during the repository

> > reconstruction.

> >>> ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of

> > the

> >>> AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

> >>> ..866 19:14:17 (0) ** is included and recompile the MOF/MFL

> > with

> >>> the following command:

> >>> ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

> >>> ..868 19:14:17 (0) **

> >>> ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains

class

> > and

> >>> instance DELETE statements.

> >>> ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used

to

> >>> UNinstall components and they should NOT be listed in the AUTORECOVERY

> > LIST

> >>> ..871 19:14:17 (0) ** and therefore they should NOT specify the

> > '#PRAGMA

> >>> AUTORECOVER' statement.

> >>> ..872 19:14:17 (0) ** Note: It happens that some MOF files do

contain

> >>> DELETE statements for installation purposes to delete

> >>> ..873 19:14:17 (0) ** existing information before it is

> > recreated.

> >>> ..874 19:14:17 (0) **

> >>> ..875 19:14:17 (0) ** Note: It is also possible that the

application

> >>> implemented its own recovery mechanism.

> >>> ..876 19:14:17 (0) ** In that case, no action is required.

You

> > must

> >>> verify with the application vendor

> >>> ..877 19:14:17 (0) ** if the application has this capability

> > (i.e.

> >>> Microsoft SMS)

> >>> ..878 19:14:17 (0) **

> >>> ..879 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..880 19:14:17 (0) **

> >>> ..881 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..882 19:14:17 (0)

> > ** ------------------------------------------------------

> >>> WMI REPORT:

> > END -----------------------------------------------------------

> >>> ..883 19:14:17 (0)

> >>>

> >

** -------------------------------------------------------------------------

> >>> ---------------------------------------------------------

> >>> ..884 19:14:17 (0) **

> >>> ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could

prevent

> > WMI

> >>> to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

> >>>

> >

SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

> >>> .29.LOG' for details.

> >>> ..886 19:14:17 (0) **

> >>> ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010

at

> >>> 19:14 (W:30 E:16 S:1).

>

>> -========================================================================

=

> > ==

> >>> ====

> >>>

> >>>

> >>>

> >>>

> >>>

> >>> "John John - MVP" wrote in message

> >>> news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

> >>>> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

> >>>> folder. Administrators and the System account should have Full

Control

> >>>> on this folder.

> >>>>

> >>>> John

> >>>>

> >>>> jbclem wrote:

> >>>>> I'm trying to run msinfo32.exe, which is the System

Information/System

> >>>>> Summary module. But I keep getting this response: "the connection

to

> >>> could

> >>>>> not be established. Check to see that the network path name is

> >>> correct,

> >>>>> that you have sufficient permission to access Windows Management".

> >>>>>

> >>>>> All of the other modules (Hardware Resources, Components, etc...)

give

> >>> the

> >>>>> same response. I've tried refreshing, but still the same response.

> >>> Looking

> >>>>> in the Event Viewer, there are plenty of errors that say "WinMgmt

> > cannot

> >>>>> open the repository file..." could that have something to do with

> > this.

> >>>>> But I have plenty of disk space and memory. These WinMgmt errors

seem

> >>> to

> >>>>> have started a month ago.

> >>>>>

> >>>>> Can someone show me what's wrong here...the computer seems to be

> > working

> >>>>> normally, and I checked Services to see if I might have turned

> > something

> >>>>> off. I started Windows Management Instrumentation, in case that was

> >>>>> it...but no difference.

> >>>>>

> >>>>> John

> >>>>>

> >>>>>

> >>>

> >

> >

>
 
D

Dave Patrick

I'd run the tool again after each repair or change.



Failing that these might help.



How to Perform an In-Place Upgrade of Windows 2000

http://support.microsoft.com/default.aspx?kbid=292175



What an In-Place Windows 2000 Upgrade Changes and What It Does Not Change

http://support.microsoft.com/default.aspx?kbid=306952



Be sure to apply these to your repair install before connecting to any

network. Internet included. (sasser, msblast)

http://download.microsoft.com/download/E/6/A/E6A04295-D2A8-40D0-A0C5-241BFECD095E/W2KSP4_EN.EXE

http://www.microsoft.com/technet/security/bulletin/MS03-043.mspx

http://www.microsoft.com/technet/security/bulletin/MS03-049.mspx



Then



Rollup 1 for Microsoft Windows 2000 Service Pack 4

http://www.microsoft.com/downloads/...CF-8850-4531-B52B-BF28B324C662&displaylang=en

and

http://www.microsoft.com/technet/security/bulletin/MS08-067.mspx









--



Regards,



Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect



"jbclem" wrote:

> Windows Management Instrumentation service is set to automatic start. But

> it isn't starting automatically. I can start it, and the service status

> (under properties) will list it as Started for about 5 seconds, then that

> changes to Stopped.

>

> About sharing the Repository folder, I didn't think it needed to be

> shared,

> but that was the only way to active the permissions tab so I tried it. I

> have two computers on a LAN, but I've only used sharing to be able to

> transfer files back and forth.

>

> When I right click on the folder and open Properties, there are only two

> tabs: General and Sharing. Is there a way to activate the Security tab

> and

> make it visible under Properties? Also, there are three files in the

> Repository folder and their Properties only show one tab: General.

>

>

> "John John - MVP" wrote in message

> news:u%23MJfrV3KHA.4752@TK2MSFTNGP02.phx.gbl...

>> First make sure that the Windows Management Instrumentation service is

>> set to Automatic start.

>>

>> Are you running the command on a local machine or over the network? You

>> don't need to share the Repository folder, you need to look at the

>> Security tab in the folder's Properties (right click on the folder) and

>> make sure that you have sufficient permissions on the folder and its

>> contents.

>>

>> John

>>

>> jbclem wrote:

>> > I've got DCOM enabled now. And just in case, I rebooted the computer.

> But

>> > the problem still exists. Looking in the event viewer, the latest(a

>> > few

>> > minutes ago) WinMgmt error states: WinMgmt could not open the

>> > repository

>> > file. This could be due to insufficient security access to the

>> > "\System32\WBEM\Repository", insufficient disk space or

>> > insufficient memory.

>> >

>> > I checked the properties of the Repository folder, it was set to "do

>> > not

>> > share". I changed that to "share this folder" and checked the

> permissions.

>> > All three were set to Allow.

>> >

>> > Checked the original problem, but it's still there. I'm going to

>> > reboot

>> > again, just in case.

>> >

>> > Any other thoughts on this?

>> >

>> >

>> >

>> >

>> >

>> >

>> >

>> >

>> >

>> > "John John - MVP" wrote in message

>> > news:Ouyo$EJ3KHA.1016@TK2MSFTNGP02.phx.gbl...

>> >> On Windows 2000 the Dcomcnfg command returns a different GUI, see

>> >> here:

>> >>

>> >>

>> >

> http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/comdcom/dcom_enable.html

>> >> or run this command instead to get to the Component Services snap-in:

>> >>

>> >> %windir%\System32\Com\Comexp.msc

>> >>

>> >> John

>> >>

>> >> jbclem wrote:

>> >>> I've installed and run WMIDiag v2.0_2000. It shows this:

>> >>>

>> >>> .737 19:14:17 (1) !! ERROR: DCOM Status:

>> >>>

>> >

> ............................................................................

>> >>> ..................... ERROR!

>> >>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

> computer

>> > is

>> >>> DISABLED.

>> >>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

>> >>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

>> >>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

>> >>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

>> > 'Computers'

>> >>> nodes.

>> >>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

>> >>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

>> >>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

> this

>> >>> computer' checkbox.

>> >>> ..746 19:14:17 (0) **

>> >>>

>> >>> I ran DCOMCNFG.exe but couldn't find the Component Services or

> Computer

>> >>> nodes.

>> >>>

>> >>> Actually, here's the entire report...there are some more errors

> towards

>> > the

>> >>> bottom.

>> >>>

> ========================================================================

>> >>> ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14,

> 2010

>> > at

>> >>> 19:14.

>> >>> ..698 19:14:17 (0) **

>> >>> ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

>> >>> reserved - January 2007.

>> >>> ..700 19:14:17 (0) **

>> >>> ..701 19:14:17 (0) ** This script is not supported under any

>> >>> Microsoft

>> >>> standard support program or service.

>> >>> ..702 19:14:17 (0) ** The script is provided AS IS without warranty

>> >>> of

>> > any

>> >>> kind. Microsoft further disclaims all

>> >>> ..703 19:14:17 (0) ** implied warranties including, without

> limitation,

>> > any

>> >>> implied warranties of merchantability

>> >>> ..704 19:14:17 (0) ** or of fitness for a particular purpose. The

> entire

>> >>> risk arising out of the use or performance

>> >>> ..705 19:14:17 (0) ** of the scripts and documentation remains with

> you.

>> > In

>> >>> no event shall Microsoft, its authors,

>> >>> ..706 19:14:17 (0) ** or anyone else involved in the creation,

>> > production,

>> >>> or delivery of the script be liable for

>> >>> ..707 19:14:17 (0) ** any damages whatsoever (including, without

>> > limitation,

>> >>> damages for loss of business profits,

>> >>> ..708 19:14:17 (0) ** business interruption, loss of business

>> > information,

>> >>> or other pecuniary loss) arising out of

>> >>> ..709 19:14:17 (0) ** the use of or inability to use the script or

>> >>> documentation, even if Microsoft has been advised

>> >>> ..710 19:14:17 (0) ** of the possibility of such damages.

>> >>> ..711 19:14:17 (0) **

>> >>> ..712 19:14:17 (0) **

>> >>> ..713 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..714 19:14:17 (0)

>> > ** -----------------------------------------------------

>> >>> WMI REPORT:

>> > BEGIN ----------------------------------------------------------

>> >>> ..715 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..716 19:14:17 (0) **

>> >>> ..717 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit

>> > (2195) -

>> >>> User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

>> >>> ..719 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..720 19:14:17 (0) ** Environment:

>> >>>

>> >

> ............................................................................

>> >>> ............................ OK..

>> >>> ..721 19:14:17 (0) ** There are no missing WMI system files:

>> >>>

>> >

> ............................................................................

>> >>> .. OK.

>> >>> ..722 19:14:17 (0) ** There are no missing WMI repository files:

>> >>>

>> >

> ..........................................................................

>> >>> OK.

>> >>> ..723 19:14:17 (0) ** WMI repository state:

>> >>>

>> >

> ............................................................................

>> >>> ................... N/A.

>> >>> ..724 19:14:17 (0) ** BEFORE running WMIDiag:

>> >>> ..725 19:14:17 (0) ** The WMI repository has a size of:

>> >>>

>> >

> ............................................................................

>> >>> ....... 1 MB.

>> >>> ..726 19:14:17 (0) ** - Disk free space on 'C:':

>> >>>

>> >

> ............................................................................

>> >>> .............. 2149 MB.

>> >>> ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

>> >>> 3/12/2010 11:22:16 PM

>> >>> ..728 19:14:17 (0) ** - CIM.REP, 262144

>> >>> bytes,

>> >>> 4/14/2010 7:02:40 PM

>> >>> ..729 19:14:17 (0) ** AFTER running WMIDiag:

>> >>> ..730 19:14:17 (0) ** The WMI repository has a size of:

>> >>>

>> >

> ............................................................................

>> >>> ....... 1 MB.

>> >>> ..731 19:14:17 (0) ** - Disk free space on 'C:':

>> >>>

>> >

> ............................................................................

>> >>> .............. 2149 MB.

>> >>> ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

>> >>> 3/12/2010 11:22:16 PM

>> >>> ..733 19:14:17 (0) ** - CIM.REP, 262144

>> >>> bytes,

>> >>> 4/14/2010 7:02:40 PM

>> >>> ..734 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..735 19:14:17 (0) ** Windows Firewall:

>> >>>

>> >

> ............................................................................

>> >>> ....................... NOT INSTALLED.

>> >>> ..736 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..737 19:14:17 (1) !! ERROR: DCOM Status:

>> >>>

>> >

> ............................................................................

>> >>> ..................... ERROR!

>> >>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

> computer

>> > is

>> >>> DISABLED.

>> >>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

>> >>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

>> >>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

>> >>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

>> > 'Computers'

>> >>> nodes.

>> >>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

>> >>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

>> >>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

> this

>> >>> computer' checkbox.

>> >>> ..746 19:14:17 (0) **

>> >>> ..747 19:14:17 (0) ** WMI registry setup:

>> >>>

>> >

> ............................................................................

>> >>> ..................... OK.

>> >>> ..748 19:14:17 (0) ** WMI Service has no dependents:

>> >>>

>> >

> ............................................................................

>> >>> .......... OK.

>> >>> ..749 19:14:17 (0) ** RPCSS service:

>> >>>

>> >

> ............................................................................

>> >>> .......................... OK (Already started).

>> >>> ..750 19:14:17 (0) ** WINMGMT service:

>> >>>

>> >

> ............................................................................

>> >>> ........................ OK (Successfully started).

>> >>> ..751 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..752 19:14:17 (0) ** WMI service DCOM setup:

>> >>>

>> >

> ............................................................................

>> >>> ................. OK.

>> >>> ..753 19:14:17 (0) ** WMI components DCOM registrations:

>> >>>

>> >

> ............................................................................

>> >>> ...... OK.

>> >>> ..754 19:14:17 (0) ** WMI ProgID registrations:

>> >>>

>> >

> ............................................................................

>> >>> ............... OK.

>> >>> ..755 19:14:17 (0) ** WMI provider DCOM registrations:

>> >>>

>> >

> ............................................................................

>> >>> ........ OK.

>> >>> ..756 19:14:17 (0) ** WMI provider CIM registrations:

>> >>>

>> >

> ............................................................................

>> >>> ......... OK.

>> >>> ..757 19:14:17 (0) ** WMI provider CLSIDs:

>> >>>

>> >

> ............................................................................

>> >>> .................... OK.

>> >>> ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

>> >>>

>> >

> ............................................................................

>> >>> ..... OK.

>> >>> ..759 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..760 19:14:17 (0) ** Overall security status:

>> >>>

>> >

> ............................................................................

>> >>> ................ NOT TESTED.

>> >>> ..761 19:14:17 (0) ** - Started at

>> >>>

>> >

> 'Root' ---------------------------------------------------------------------

>> >>> -----------------------------------------

>> >>> ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

>> >>>

>> >

> ............................................................................

>> >>> .......... NONE.

>> >>> ..763 19:14:17 (0) ** WMI TIMER instruction(s):

>> >>>

>> >

> ............................................................................

>> >>> ............... NONE.

>> >>> ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

>> >>>

>> >

> ............................................................................

>> >>> ................. NOT AVAILABLE.

>> >>> ..765 19:14:17 (0) ** You can start the WMI

>> >>> AutoDiscovery/AutoPurge

>> >>> (ADAP) process to resynchronize

>> >>> ..766 19:14:17 (0) ** the performance counters with the WMI

>> > performance

>> >>> classes with the following commands:

>> >>> ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

>> >>> ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF

>> > '

>> >>> ..769 19:14:17 (0) ** The ADAP process logs informative events in

> the

>> >>> Windows NT event log.

>> >>> ..770 19:14:17 (0) ** More information can be found on MSDN at:

>> >>> ..771 19:14:17 (0) **

>> >>>

>> >

> http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

>> >>> ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured

>> >>> for

>> > the

>> >>> following namespaces: .......................................... 1

>> > ERROR(S)!

>> >>> ..773 19:14:17 (0) ** - Root, 0x80041014 -

>> > (WBEM_E_INITIALIZATION_FAILURE)

>> >>> Component such as a provider failed to initialize for internal

> reasons.

>> >>> ..774 19:14:17 (0) **

>> >>> ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the

>> > following

>> >>> namespaces: .................................................. 5

>> > ERROR(S)!

>> >>> ..776 19:14:17 (0) ** - Root, 0x80041014 -

>> > (WBEM_E_INITIALIZATION_FAILURE)

>> >>> Component such as a provider failed to initialize for internal

> reasons.

>> >>> ..777 19:14:17 (0) ** - Root, 0x80041014 -

>> > (WBEM_E_INITIALIZATION_FAILURE)

>> >>> Component such as a provider failed to initialize for internal

> reasons.

>> >>> ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

>> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed

>> >>> to

>> >>> initialize for internal reasons.

>> >>> ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

>> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed

>> >>> to

>> >>> initialize for internal reasons.

>> >>> ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

>> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed

>> >>> to

>> >>> initialize for internal reasons.

>> >>> ..781 19:14:17 (0) **

>> >>> ..782 19:14:17 (0) ** WMI GET operations:

>> >>>

>> >

> ............................................................................

>> >>> ..................... OK.

>> >>> ..783 19:14:17 (0) ** WMI MOF representations:

>> >>>

>> >

> ............................................................................

>> >>> ................ OK.

>> >>> ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

>> >>>

>> >

> ............................................................................

>> >>> ........ OK.

>> >>> ..785 19:14:17 (0) ** WMI ENUMERATION operations:

>> >>>

>> >

> ............................................................................

>> >>> ............. OK.

>> >>> ..786 19:14:17 (0) ** WMI EXECQUERY operations:

>> >>>

>> >

> ............................................................................

>> >>> ............... OK.

>> >>> ..787 19:14:17 (0) ** WMI GET VALUE operations:

>> >>>

>> >

> ............................................................................

>> >>> ............... OK.

>> >>> ..788 19:14:17 (0) ** WMI WRITE operations:

>> >>>

>> >

> ............................................................................

>> >>> ................... NOT TESTED.

>> >>> ..789 19:14:17 (0) ** WMI PUT operations:

>> >>>

>> >

> ............................................................................

>> >>> ..................... NOT TESTED.

>> >>> ..790 19:14:17 (0) ** WMI DELETE operations:

>> >>>

>> >

> ............................................................................

>> >>> .................. NOT TESTED.

>> >>> ..791 19:14:17 (0) ** WMI static instances retrieved:

>> >>>

>> >

> ............................................................................

>> >>> ......... 0.

>> >>> ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

>> >>>

>> >

> ............................................................................

>> >>> ........ 0.

>> >>> ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

>> >>> performance impact):

> ...................................................

>> > 0.

>> >>> ..794 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..795 19:14:17 (0) **

>> >>> ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

>> >>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed

>> >>> to

>> >>> initialize for internal reasons

>> >>> ..797 19:14:17 (0) ** => This error is typically a WMI system error.

> WMI

>> >>> system errors can find their origin in:

>> >>> ..798 19:14:17 (0) ** - Failing WMI system components (see any

>> > missing

>> >>> WMI system files or DCOM registration

>> >>> ..799 19:14:17 (0) ** issues previously mentioned).

>> >>> ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM

>> > registration

>> >>> issues previously mentioned).

>> >>> ..801 19:14:17 (0) ** - a WMI repository corruption.

>> >>> ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag

>> >>> with

>> >>> 'WriteInRepository' parameter

>> >>> ..803 19:14:17 (0) ** to validate the WMI repository operations.

>> >>> ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with

> FULL

>> >>> access to WMI EVERY namespaces of the computer before

>> >>> ..805 19:14:17 (0) ** executing the WriteInRepository

> command.

>> > To

>> >>> write temporary data from the Root namespace, use:

>> >>> ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

>> >>> ..807 19:14:17 (0) ** - If the WriteInRepository command fails,

> while

>> >>> being an Administrator with ALL accesses to ALL namespaces

>> >>> ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

>> >>> ..809 19:14:17 (0) ** Note: The WMI repository reconstruction

>> > requires to

>> >>> locate all MOF files needed to rebuild the repository,

>> >>> ..810 19:14:17 (0) ** otherwise some applications may fail

>> > after

>> >>> the reconstruction.

>> >>> ..811 19:14:17 (0) ** This can be achieved with the

>> >>> following

>> >>> command:

>> >>> ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

>> >>> ..813 19:14:17 (0) ** Note: The repository reconstruction must be

>> >>> a

>> > LAST

>> >>> RESORT solution and ONLY after executing

>> >>> ..814 19:14:17 (0) ** ALL fixes previously mentioned.

>> >>> ..815 19:14:17 (2) !! WARNING: Static information stored by external

>> >>> applications in the repository will be LOST! (i.e. SMS Inventory)

>> >>> ..816 19:14:17 (0) **

>> >>> ..817 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..818 19:14:17 (0) ** WMI Registry key setup:

>> >>>

>> >

> ............................................................................

>> >>> ................. OK.

>> >>> ..819 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder

> not

>> >>> referenced in the Auto-Recovery list: .............................

>> >>> 13

>> >>> ERROR(S)!

>> >>> ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

>> >>> ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

>> >>> ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

>> >>> ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

>> >>> ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

>> >>> ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

>> >>> ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

>> >>> ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

>> >>> ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

>> >>> ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

>> >>> ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

>> >>> ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

>> >>> ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

>> >>> ..834 19:14:17 (0) ** => After fixing all other issues previously

>> > mentioned,

>> >>> if the WMI repository is rebuilt,

>> >>> ..835 19:14:17 (0) ** the listed MOF file(s) will not be

> recompiled,

>> > and

>> >>> therefore the definition they contain

>> >>> ..836 19:14:17 (0) ** will not be available in the WMI repository.

>> >>> ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s)

>> > with

>> >>> the 'MOFCOMP.EXE ' command.

>> >>> ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of

>> >>> the

>> >>> Auto-Recovery list, make sure the

>> >>> ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

>> >>> ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

>> >>> included AT SETUP in the auto-recovery process.

>> >>> ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL

>> > statements

>> >>> (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the

>> > auto-recovery

>> >>> process.

>> >>> ..842 19:14:17 (0) ** Refer to the list of MOF files below

> NOT

>> >>> containing the '#PRAGMA AUTORECOVER' statement' for more information.

>> >>> ..843 19:14:17 (0) **

>> >>> ..844 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..845 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

>> >>> AUTORECOVER' statement:

>> >>> ..............................................

>> > 14

>> >>> FILE(S)!

>> >>> ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

>> >>> ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

>> >>> ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

>> >>> ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

>> >>> ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

>> >>> ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

>> >>> ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

>> >>> ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

>> >>> ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

>> >>> ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

>> >>> ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

>> >>> ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

>> >>> ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

>> >>> ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

>> >>> ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in

> the

>> >>> AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA

> AUTORECOVER'

>> >>> statement.

>> >>> ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed

>> > MOF

>> >>> files not included in the AUTO-RECOVERY LIST and

>> >>> ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement

>> > when

>> >>> they are compiled the first time will NOT

>> >>> ..864 19:14:17 (0) ** be recompiled during the repository

>> > reconstruction.

>> >>> ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of

>> > the

>> >>> AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

>> >>> ..866 19:14:17 (0) ** is included and recompile the MOF/MFL

>> > with

>> >>> the following command:

>> >>> ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

>> >>> ..868 19:14:17 (0) **

>> >>> ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains

> class

>> > and

>> >>> instance DELETE statements.

>> >>> ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used

> to

>> >>> UNinstall components and they should NOT be listed in the

>> >>> AUTORECOVERY

>> > LIST

>> >>> ..871 19:14:17 (0) ** and therefore they should NOT specify the

>> > '#PRAGMA

>> >>> AUTORECOVER' statement.

>> >>> ..872 19:14:17 (0) ** Note: It happens that some MOF files do

> contain

>> >>> DELETE statements for installation purposes to delete

>> >>> ..873 19:14:17 (0) ** existing information before it is

>> > recreated.

>> >>> ..874 19:14:17 (0) **

>> >>> ..875 19:14:17 (0) ** Note: It is also possible that the

> application

>> >>> implemented its own recovery mechanism.

>> >>> ..876 19:14:17 (0) ** In that case, no action is required.

> You

>> > must

>> >>> verify with the application vendor

>> >>> ..877 19:14:17 (0) ** if the application has this capability

>> > (i.e.

>> >>> Microsoft SMS)

>> >>> ..878 19:14:17 (0) **

>> >>> ..879 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..880 19:14:17 (0) **

>> >>> ..881 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..882 19:14:17 (0)

>> > ** ------------------------------------------------------

>> >>> WMI REPORT:

>> > END -----------------------------------------------------------

>> >>> ..883 19:14:17 (0)

>> >>>

>> >

> ** -------------------------------------------------------------------------

>> >>> ---------------------------------------------------------

>> >>> ..884 19:14:17 (0) **

>> >>> ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could

> prevent

>> > WMI

>> >>> to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

>> >>>

>> >

> SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

>> >>> .29.LOG' for details.

>> >>> ..886 19:14:17 (0) **

>> >>> ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010

> at

>> >>> 19:14 (W:30 E:16 S:1).

>>

>>> -========================================================================

> =

>> > ==

>> >>> ====

>> >>>

>> >>>

>> >>>

>> >>>

>> >>>

>> >>> "John John - MVP" wrote in message

>> >>> news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

>> >>>> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

>> >>>> folder. Administrators and the System account should have Full

> Control

>> >>>> on this folder.

>> >>>>

>> >>>> John

>> >>>>

>> >>>> jbclem wrote:

>> >>>>> I'm trying to run msinfo32.exe, which is the System

> Information/System

>> >>>>> Summary module. But I keep getting this response: "the connection

> to

>> >>> could

>> >>>>> not be established. Check to see that the network path name is

>> >>> correct,

>> >>>>> that you have sufficient permission to access Windows Management".

>> >>>>>

>> >>>>> All of the other modules (Hardware Resources, Components, etc...)

> give

>> >>> the

>> >>>>> same response. I've tried refreshing, but still the same response.

>> >>> Looking

>> >>>>> in the Event Viewer, there are plenty of errors that say "WinMgmt

>> > cannot

>> >>>>> open the repository file..." could that have something to do with

>> > this.

>> >>>>> But I have plenty of disk space and memory. These WinMgmt errors

> seem

>> >>> to

>> >>>>> have started a month ago.

>> >>>>>

>> >>>>> Can someone show me what's wrong here...the computer seems to be

>> > working

>> >>>>> normally, and I checked Services to see if I might have turned

>> > something

>> >>>>> off. I started Windows Management Instrumentation, in case that

>> >>>>> was

>> >>>>> it...but no difference.

>> >>>>>

>> >>>>> John

>> >>>>>

>> >>>>>

>> >>>

>> >

>> >

>>

>

>
 
J

John John - MVP

msinfo32.exe gives "connection to could not be established..."???

Sounds to me like you are running on a FAT32 drive, FAT32 has no

security. I suggest that you follow Dave's advice and do an in-place

upgrade.



John



jbclem wrote:

> Windows Management Instrumentation service is set to automatic start. But

> it isn't starting automatically. I can start it, and the service status

> (under properties) will list it as Started for about 5 seconds, then that

> changes to Stopped.

>

> About sharing the Repository folder, I didn't think it needed to be shared,

> but that was the only way to active the permissions tab so I tried it. I

> have two computers on a LAN, but I've only used sharing to be able to

> transfer files back and forth.

>

> When I right click on the folder and open Properties, there are only two

> tabs: General and Sharing. Is there a way to activate the Security tab and

> make it visible under Properties? Also, there are three files in the

> Repository folder and their Properties only show one tab: General.

>

>

> "John John - MVP" wrote in message

> news:u%23MJfrV3KHA.4752@TK2MSFTNGP02.phx.gbl...

>> First make sure that the Windows Management Instrumentation service is

>> set to Automatic start.

>>

>> Are you running the command on a local machine or over the network? You

>> don't need to share the Repository folder, you need to look at the

>> Security tab in the folder's Properties (right click on the folder) and

>> make sure that you have sufficient permissions on the folder and its

>> contents.

>>

>> John

>>

>> jbclem wrote:

>>> I've got DCOM enabled now. And just in case, I rebooted the computer.

> But

>>> the problem still exists. Looking in the event viewer, the latest(a few

>>> minutes ago) WinMgmt error states: WinMgmt could not open the repository

>>> file. This could be due to insufficient security access to the

>>> "\System32\WBEM\Repository", insufficient disk space or

>>> insufficient memory.

>>>

>>> I checked the properties of the Repository folder, it was set to "do not

>>> share". I changed that to "share this folder" and checked the

> permissions.

>>> All three were set to Allow.

>>>

>>> Checked the original problem, but it's still there. I'm going to reboot

>>> again, just in case.

>>>

>>> Any other thoughts on this?

>>>

>>>

>>>

>>>

>>>

>>>

>>>

>>>

>>>

>>> "John John - MVP" wrote in message

>>> news:Ouyo$EJ3KHA.1016@TK2MSFTNGP02.phx.gbl...

>>>> On Windows 2000 the Dcomcnfg command returns a different GUI, see here:

>>>>

>>>>

> http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/comdcom/dcom_enable.html

>>>> or run this command instead to get to the Component Services snap-in:

>>>>

>>>> %windir%\System32\Com\Comexp.msc

>>>>

>>>> John

>>>>

>>>> jbclem wrote:

>>>>> I've installed and run WMIDiag v2.0_2000. It shows this:

>>>>>

>>>>> .737 19:14:17 (1) !! ERROR: DCOM Status:

>>>>>

> ............................................................................

>>>>> ..................... ERROR!

>>>>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

> computer

>>> is

>>>>> DISABLED.

>>>>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

>>>>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

>>>>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

>>>>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

>>> 'Computers'

>>>>> nodes.

>>>>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

>>>>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

>>>>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

> this

>>>>> computer' checkbox.

>>>>> ..746 19:14:17 (0) **

>>>>>

>>>>> I ran DCOMCNFG.exe but couldn't find the Component Services or

> Computer

>>>>> nodes.

>>>>>

>>>>> Actually, here's the entire report...there are some more errors

> towards

>>> the

>>>>> bottom.

>>>>>

> ========================================================================

>>>>> ..697 19:14:17 (0) ** WMIDiag v2.0 started on Wednesday, April 14,

> 2010

>>> at

>>>>> 19:14.

>>>>> ..698 19:14:17 (0) **

>>>>> ..699 19:14:17 (0) ** Copyright (c) Microsoft Corporation. All rights

>>>>> reserved - January 2007.

>>>>> ..700 19:14:17 (0) **

>>>>> ..701 19:14:17 (0) ** This script is not supported under any Microsoft

>>>>> standard support program or service.

>>>>> ..702 19:14:17 (0) ** The script is provided AS IS without warranty of

>>> any

>>>>> kind. Microsoft further disclaims all

>>>>> ..703 19:14:17 (0) ** implied warranties including, without

> limitation,

>>> any

>>>>> implied warranties of merchantability

>>>>> ..704 19:14:17 (0) ** or of fitness for a particular purpose. The

> entire

>>>>> risk arising out of the use or performance

>>>>> ..705 19:14:17 (0) ** of the scripts and documentation remains with

> you.

>>> In

>>>>> no event shall Microsoft, its authors,

>>>>> ..706 19:14:17 (0) ** or anyone else involved in the creation,

>>> production,

>>>>> or delivery of the script be liable for

>>>>> ..707 19:14:17 (0) ** any damages whatsoever (including, without

>>> limitation,

>>>>> damages for loss of business profits,

>>>>> ..708 19:14:17 (0) ** business interruption, loss of business

>>> information,

>>>>> or other pecuniary loss) arising out of

>>>>> ..709 19:14:17 (0) ** the use of or inability to use the script or

>>>>> documentation, even if Microsoft has been advised

>>>>> ..710 19:14:17 (0) ** of the possibility of such damages.

>>>>> ..711 19:14:17 (0) **

>>>>> ..712 19:14:17 (0) **

>>>>> ..713 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..714 19:14:17 (0)

>>> ** -----------------------------------------------------

>>>>> WMI REPORT:

>>> BEGIN ----------------------------------------------------------

>>>>> ..715 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..716 19:14:17 (0) **

>>>>> ..717 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..718 19:14:17 (0) ** Windows 2000 Client - Service pack 4 - 32-bit

>>> (2195) -

>>>>> User 'DOWNSTAIRSDELTA\DOWNSTAIRS' on computer 'DOWNSTAIRSDELTA'.

>>>>> ..719 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..720 19:14:17 (0) ** Environment:

>>>>>

> ............................................................................

>>>>> ............................ OK..

>>>>> ..721 19:14:17 (0) ** There are no missing WMI system files:

>>>>>

> ............................................................................

>>>>> .. OK.

>>>>> ..722 19:14:17 (0) ** There are no missing WMI repository files:

>>>>>

> ..........................................................................

>>>>> OK.

>>>>> ..723 19:14:17 (0) ** WMI repository state:

>>>>>

> ............................................................................

>>>>> ................... N/A.

>>>>> ..724 19:14:17 (0) ** BEFORE running WMIDiag:

>>>>> ..725 19:14:17 (0) ** The WMI repository has a size of:

>>>>>

> ............................................................................

>>>>> ....... 1 MB.

>>>>> ..726 19:14:17 (0) ** - Disk free space on 'C:':

>>>>>

> ............................................................................

>>>>> .............. 2149 MB.

>>>>> ..727 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

>>>>> 3/12/2010 11:22:16 PM

>>>>> ..728 19:14:17 (0) ** - CIM.REP, 262144 bytes,

>>>>> 4/14/2010 7:02:40 PM

>>>>> ..729 19:14:17 (0) ** AFTER running WMIDiag:

>>>>> ..730 19:14:17 (0) ** The WMI repository has a size of:

>>>>>

> ............................................................................

>>>>> ....... 1 MB.

>>>>> ..731 19:14:17 (0) ** - Disk free space on 'C:':

>>>>>

> ............................................................................

>>>>> .............. 2149 MB.

>>>>> ..732 19:14:17 (0) ** - $WINMGMT.CFG, 12 bytes,

>>>>> 3/12/2010 11:22:16 PM

>>>>> ..733 19:14:17 (0) ** - CIM.REP, 262144 bytes,

>>>>> 4/14/2010 7:02:40 PM

>>>>> ..734 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..735 19:14:17 (0) ** Windows Firewall:

>>>>>

> ............................................................................

>>>>> ....................... NOT INSTALLED.

>>>>> ..736 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..737 19:14:17 (1) !! ERROR: DCOM Status:

>>>>>

> ............................................................................

>>>>> ..................... ERROR!

>>>>> ..738 19:14:17 (1) !! ERROR: => The DCOM configuration on this

> computer

>>> is

>>>>> DISABLED.

>>>>> ..739 19:14:17 (0) ** This prevents WMI to work correctly.

>>>>> ..740 19:14:17 (0) ** You can fix the DCOM configuration by:

>>>>> ..741 19:14:17 (0) ** - Executing the 'DCOMCNFG.EXE' command.

>>>>> ..742 19:14:17 (0) ** - Expanding 'Component Services' and

>>> 'Computers'

>>>>> nodes.

>>>>> ..743 19:14:17 (0) ** - Editing properties of 'My Computer' node.

>>>>> ..744 19:14:17 (0) ** - Editing the 'Default properties' tab.

>>>>> ..745 19:14:17 (0) ** - Activate the 'Enable Distributed COM on

> this

>>>>> computer' checkbox.

>>>>> ..746 19:14:17 (0) **

>>>>> ..747 19:14:17 (0) ** WMI registry setup:

>>>>>

> ............................................................................

>>>>> ..................... OK.

>>>>> ..748 19:14:17 (0) ** WMI Service has no dependents:

>>>>>

> ............................................................................

>>>>> .......... OK.

>>>>> ..749 19:14:17 (0) ** RPCSS service:

>>>>>

> ............................................................................

>>>>> .......................... OK (Already started).

>>>>> ..750 19:14:17 (0) ** WINMGMT service:

>>>>>

> ............................................................................

>>>>> ........................ OK (Successfully started).

>>>>> ..751 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..752 19:14:17 (0) ** WMI service DCOM setup:

>>>>>

> ............................................................................

>>>>> ................. OK.

>>>>> ..753 19:14:17 (0) ** WMI components DCOM registrations:

>>>>>

> ............................................................................

>>>>> ...... OK.

>>>>> ..754 19:14:17 (0) ** WMI ProgID registrations:

>>>>>

> ............................................................................

>>>>> ............... OK.

>>>>> ..755 19:14:17 (0) ** WMI provider DCOM registrations:

>>>>>

> ............................................................................

>>>>> ........ OK.

>>>>> ..756 19:14:17 (0) ** WMI provider CIM registrations:

>>>>>

> ............................................................................

>>>>> ......... OK.

>>>>> ..757 19:14:17 (0) ** WMI provider CLSIDs:

>>>>>

> ............................................................................

>>>>> .................... OK.

>>>>> ..758 19:14:17 (0) ** WMI providers EXE/DLL availability:

>>>>>

> ............................................................................

>>>>> ..... OK.

>>>>> ..759 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..760 19:14:17 (0) ** Overall security status:

>>>>>

> ............................................................................

>>>>> ................ NOT TESTED.

>>>>> ..761 19:14:17 (0) ** - Started at

>>>>>

> 'Root' ---------------------------------------------------------------------

>>>>> -----------------------------------------

>>>>> ..762 19:14:17 (0) ** WMI permanent SUBSCRIPTION(S):

>>>>>

> ............................................................................

>>>>> .......... NONE.

>>>>> ..763 19:14:17 (0) ** WMI TIMER instruction(s):

>>>>>

> ............................................................................

>>>>> ............... NONE.

>>>>> ..764 19:14:17 (1) !! ERROR: WMI ADAP status:

>>>>>

> ............................................................................

>>>>> ................. NOT AVAILABLE.

>>>>> ..765 19:14:17 (0) ** You can start the WMI AutoDiscovery/AutoPurge

>>>>> (ADAP) process to resynchronize

>>>>> ..766 19:14:17 (0) ** the performance counters with the WMI

>>> performance

>>>>> classes with the following commands:

>>>>> ..767 19:14:17 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

>>>>> ..768 19:14:17 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF

>>> '

>>>>> ..769 19:14:17 (0) ** The ADAP process logs informative events in

> the

>>>>> Windows NT event log.

>>>>> ..770 19:14:17 (0) ** More information can be found on MSDN at:

>>>>> ..771 19:14:17 (0) **

>>>>>

> http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp

>>>>> ..772 19:14:17 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for

>>> the

>>>>> following namespaces: .......................................... 1

>>> ERROR(S)!

>>>>> ..773 19:14:17 (0) ** - Root, 0x80041014 -

>>> (WBEM_E_INITIALIZATION_FAILURE)

>>>>> Component such as a provider failed to initialize for internal

> reasons.

>>>>> ..774 19:14:17 (0) **

>>>>> ..775 19:14:17 (1) !! ERROR: WMI CONNECTION errors occured for the

>>> following

>>>>> namespaces: .................................................. 5

>>> ERROR(S)!

>>>>> ..776 19:14:17 (0) ** - Root, 0x80041014 -

>>> (WBEM_E_INITIALIZATION_FAILURE)

>>>>> Component such as a provider failed to initialize for internal

> reasons.

>>>>> ..777 19:14:17 (0) ** - Root, 0x80041014 -

>>> (WBEM_E_INITIALIZATION_FAILURE)

>>>>> Component such as a provider failed to initialize for internal

> reasons.

>>>>> ..778 19:14:17 (0) ** - Root/Default, 0x80041014 -

>>>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>>>> initialize for internal reasons.

>>>>> ..779 19:14:17 (0) ** - Root/CIMv2, 0x80041014 -

>>>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>>>> initialize for internal reasons.

>>>>> ..780 19:14:17 (0) ** - Root/WMI, 0x80041014 -

>>>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>>>> initialize for internal reasons.

>>>>> ..781 19:14:17 (0) **

>>>>> ..782 19:14:17 (0) ** WMI GET operations:

>>>>>

> ............................................................................

>>>>> ..................... OK.

>>>>> ..783 19:14:17 (0) ** WMI MOF representations:

>>>>>

> ............................................................................

>>>>> ................ OK.

>>>>> ..784 19:14:17 (0) ** WMI QUALIFIER access operations:

>>>>>

> ............................................................................

>>>>> ........ OK.

>>>>> ..785 19:14:17 (0) ** WMI ENUMERATION operations:

>>>>>

> ............................................................................

>>>>> ............. OK.

>>>>> ..786 19:14:17 (0) ** WMI EXECQUERY operations:

>>>>>

> ............................................................................

>>>>> ............... OK.

>>>>> ..787 19:14:17 (0) ** WMI GET VALUE operations:

>>>>>

> ............................................................................

>>>>> ............... OK.

>>>>> ..788 19:14:17 (0) ** WMI WRITE operations:

>>>>>

> ............................................................................

>>>>> ................... NOT TESTED.

>>>>> ..789 19:14:17 (0) ** WMI PUT operations:

>>>>>

> ............................................................................

>>>>> ..................... NOT TESTED.

>>>>> ..790 19:14:17 (0) ** WMI DELETE operations:

>>>>>

> ............................................................................

>>>>> .................. NOT TESTED.

>>>>> ..791 19:14:17 (0) ** WMI static instances retrieved:

>>>>>

> ............................................................................

>>>>> ......... 0.

>>>>> ..792 19:14:17 (0) ** WMI dynamic instances retrieved:

>>>>>

> ............................................................................

>>>>> ........ 0.

>>>>> ..793 19:14:17 (0) ** WMI instance request cancellations (to limit

>>>>> performance impact):

> ...................................................

>>> 0.

>>>>> ..794 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..795 19:14:17 (0) **

>>>>> ..796 19:14:17 (0) ** 6 error(s) 0x80041014 -

>>>>> (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to

>>>>> initialize for internal reasons

>>>>> ..797 19:14:17 (0) ** => This error is typically a WMI system error.

> WMI

>>>>> system errors can find their origin in:

>>>>> ..798 19:14:17 (0) ** - Failing WMI system components (see any

>>> missing

>>>>> WMI system files or DCOM registration

>>>>> ..799 19:14:17 (0) ** issues previously mentioned).

>>>>> ..800 19:14:17 (0) ** - Failing WMI providers (see any DCOM

>>> registration

>>>>> issues previously mentioned).

>>>>> ..801 19:14:17 (0) ** - a WMI repository corruption.

>>>>> ..802 19:14:17 (0) ** In such a case, you must rerun WMIDiag with

>>>>> 'WriteInRepository' parameter

>>>>> ..803 19:14:17 (0) ** to validate the WMI repository operations.

>>>>> ..804 19:14:17 (0) ** Note: ENSURE you are an administrator with

> FULL

>>>>> access to WMI EVERY namespaces of the computer before

>>>>> ..805 19:14:17 (0) ** executing the WriteInRepository

> command.

>>> To

>>>>> write temporary data from the Root namespace, use:

>>>>> ..806 19:14:17 (0) ** i.e. 'WMIDiag WriteInRepository=Root'

>>>>> ..807 19:14:17 (0) ** - If the WriteInRepository command fails,

> while

>>>>> being an Administrator with ALL accesses to ALL namespaces

>>>>> ..808 19:14:17 (0) ** the WMI repository must be reconstructed.

>>>>> ..809 19:14:17 (0) ** Note: The WMI repository reconstruction

>>> requires to

>>>>> locate all MOF files needed to rebuild the repository,

>>>>> ..810 19:14:17 (0) ** otherwise some applications may fail

>>> after

>>>>> the reconstruction.

>>>>> ..811 19:14:17 (0) ** This can be achieved with the following

>>>>> command:

>>>>> ..812 19:14:17 (0) ** i.e. 'WMIDiag ShowMOFErrors'

>>>>> ..813 19:14:17 (0) ** Note: The repository reconstruction must be a

>>> LAST

>>>>> RESORT solution and ONLY after executing

>>>>> ..814 19:14:17 (0) ** ALL fixes previously mentioned.

>>>>> ..815 19:14:17 (2) !! WARNING: Static information stored by external

>>>>> applications in the repository will be LOST! (i.e. SMS Inventory)

>>>>> ..816 19:14:17 (0) **

>>>>> ..817 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..818 19:14:17 (0) ** WMI Registry key setup:

>>>>>

> ............................................................................

>>>>> ................. OK.

>>>>> ..819 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..820 19:14:17 (1) !! ERROR: MOF file(s) present in the WBEM folder

> not

>>>>> referenced in the Auto-Recovery list: ............................. 13

>>>>> ERROR(S)!

>>>>> ..821 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

>>>>> ..822 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

>>>>> ..823 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

>>>>> ..824 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

>>>>> ..825 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

>>>>> ..826 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

>>>>> ..827 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

>>>>> ..828 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

>>>>> ..829 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

>>>>> ..830 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

>>>>> ..831 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF (*)

>>>>> ..832 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF (*)

>>>>> ..833 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF

>>>>> ..834 19:14:17 (0) ** => After fixing all other issues previously

>>> mentioned,

>>>>> if the WMI repository is rebuilt,

>>>>> ..835 19:14:17 (0) ** the listed MOF file(s) will not be

> recompiled,

>>> and

>>>>> therefore the definition they contain

>>>>> ..836 19:14:17 (0) ** will not be available in the WMI repository.

>>>>> ..837 19:14:17 (0) ** => You must manually recompile the MOF file(s)

>>> with

>>>>> the 'MOFCOMP.EXE ' command.

>>>>> ..838 19:14:17 (0) ** => If you want the MOF file(s) to be part of the

>>>>> Auto-Recovery list, make sure the

>>>>> ..839 19:14:17 (0) ** statement '#PRAGMA AUTORECOVER' is included.

>>>>> ..840 19:14:17 (0) ** Note: MOF file(s) marked with (*) are NEVER

>>>>> included AT SETUP in the auto-recovery process.

>>>>> ..841 19:14:17 (0) ** MOF file(s) containing UNINSTALL

>>> statements

>>>>> (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the

>>> auto-recovery

>>>>> process.

>>>>> ..842 19:14:17 (0) ** Refer to the list of MOF files below

> NOT

>>>>> containing the '#PRAGMA AUTORECOVER' statement' for more information.

>>>>> ..843 19:14:17 (0) **

>>>>> ..844 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..845 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..846 19:14:17 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA

>>>>> AUTORECOVER' statement: ..............................................

>>> 14

>>>>> FILE(S)!

>>>>> ..847 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MFL

>>>>> ..848 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFCTRS.MOF

>>>>> ..849 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MFL

>>>>> ..850 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFDISK.MOF

>>>>> ..851 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MFL

>>>>> ..852 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFNET.MOF

>>>>> ..853 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MFL

>>>>> ..854 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFOS.MOF

>>>>> ..855 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MFL

>>>>> ..856 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\PERFPROC.MOF

>>>>> ..857 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SCRCONS.MOF

>>>>> ..858 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\SMTPCONS.MOF

>>>>> ..859 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\WBEMPERF.MOF (DELETE)

>>>>> ..860 19:14:17 (0) ** - C:\WINNT\SYSTEM32\WBEM\DSPROV.MOF (*)

>>>>> ..861 19:14:17 (0) ** => MOF file(s) marked with (*) are INCLUDED in

> the

>>>>> AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA

> AUTORECOVER'

>>>>> statement.

>>>>> ..862 19:14:17 (0) ** If the WMI repository is rebuilt, the listed

>>> MOF

>>>>> files not included in the AUTO-RECOVERY LIST and

>>>>> ..863 19:14:17 (0) ** missing the '#PRAGMA AUTORECOVERY' statement

>>> when

>>>>> they are compiled the first time will NOT

>>>>> ..864 19:14:17 (0) ** be recompiled during the repository

>>> reconstruction.

>>>>> ..865 19:14:17 (0) ** Note: If you want the MOF file to be part of

>>> the

>>>>> AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

>>>>> ..866 19:14:17 (0) ** is included and recompile the MOF/MFL

>>> with

>>>>> the following command:

>>>>> ..867 19:14:17 (0) ** i.e. 'MOFCOMP.EXE '

>>>>> ..868 19:14:17 (0) **

>>>>> ..869 19:14:17 (0) ** => MOF file(s) marked with (DELETE) contains

> class

>>> and

>>>>> instance DELETE statements.

>>>>> ..870 19:14:17 (0) ** Usually, MOF with DELETE statements are used

> to

>>>>> UNinstall components and they should NOT be listed in the AUTORECOVERY

>>> LIST

>>>>> ..871 19:14:17 (0) ** and therefore they should NOT specify the

>>> '#PRAGMA

>>>>> AUTORECOVER' statement.

>>>>> ..872 19:14:17 (0) ** Note: It happens that some MOF files do

> contain

>>>>> DELETE statements for installation purposes to delete

>>>>> ..873 19:14:17 (0) ** existing information before it is

>>> recreated.

>>>>> ..874 19:14:17 (0) **

>>>>> ..875 19:14:17 (0) ** Note: It is also possible that the

> application

>>>>> implemented its own recovery mechanism.

>>>>> ..876 19:14:17 (0) ** In that case, no action is required.

> You

>>> must

>>>>> verify with the application vendor

>>>>> ..877 19:14:17 (0) ** if the application has this capability

>>> (i.e.

>>>>> Microsoft SMS)

>>>>> ..878 19:14:17 (0) **

>>>>> ..879 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..880 19:14:17 (0) **

>>>>> ..881 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..882 19:14:17 (0)

>>> ** ------------------------------------------------------

>>>>> WMI REPORT:

>>> END -----------------------------------------------------------

>>>>> ..883 19:14:17 (0)

>>>>>

> ** -------------------------------------------------------------------------

>>>>> ---------------------------------------------------------

>>>>> ..884 19:14:17 (0) **

>>>>> ..885 19:14:17 (0) ** ERROR: WMIDiag detected issues that could

> prevent

>>> WMI

>>>>> to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\DOWNSTAIRS\LOCAL

>>>>>

> SETTINGS\TEMP\WMIDIAG-V2.0_2000_.CLI.SP4.32_DOWNSTAIRSDELTA_2010.04.14_19.13

>>>>> .29.LOG' for details.

>>>>> ..886 19:14:17 (0) **

>>>>> ..887 19:14:17 (0) ** WMIDiag v2.0 ended on Wednesday, April 14, 2010

> at

>>>>> 19:14 (W:30 E:16 S:1).

>>> -========================================================================

> =

>>> ==

>>>>> ====

>>>>>

>>>>>

>>>>>

>>>>>

>>>>>

>>>>> "John John - MVP" wrote in message

>>>>> news:%237$0Jy%232KHA.4716@TK2MSFTNGP06.phx.gbl...

>>>>>> Verify the permissions on the %SystemRoot%\System32\WBEM\Repository

>>>>>> folder. Administrators and the System account should have Full

> Control

>>>>>> on this folder.

>>>>>>

>>>>>> John

>>>>>>

>>>>>> jbclem wrote:

>>>>>>> I'm trying to run msinfo32.exe, which is the System

> Information/System

>>>>>>> Summary module. But I keep getting this response: "the connection

> to

>>>>> could

>>>>>>> not be established. Check to see that the network path name is

>>>>> correct,

>>>>>>> that you have sufficient permission to access Windows Management".

>>>>>>>

>>>>>>> All of the other modules (Hardware Resources, Components, etc...)

> give

>>>>> the

>>>>>>> same response. I've tried refreshing, but still the same response.

>>>>> Looking

>>>>>>> in the Event Viewer, there are plenty of errors that say "WinMgmt

>>> cannot

>>>>>>> open the repository file..." could that have something to do with

>>> this.

>>>>>>> But I have plenty of disk space and memory. These WinMgmt errors

> seem

>>>>> to

>>>>>>> have started a month ago.

>>>>>>>

>>>>>>> Can someone show me what's wrong here...the computer seems to be

>>> working

>>>>>>> normally, and I checked Services to see if I might have turned

>>> something

>>>>>>> off. I started Windows Management Instrumentation, in case that was

>>>>>>> it...but no difference.

>>>>>>>

>>>>>>> John

>>>>>>>

>>>>>>>

>>>

>

>
 
You must log in or register to reply here.

Similar threads

J
I keep getting errors that i have no connection.... But i checked and ethernet is connected and connection is strong.... what could the problem be ?
Replies
0
Views
22
jojo2GO
J
Z
Could not load file or assembly .NET
Replies
0
Views
26
Zoey XCX
Z
M
Frequent bluescreen errors randomly started happening
Replies
0
Views
62
Mitch B615
M
M
Graphics buggy during wireless display connection to a TV
Replies
0
Views
29
Michal Filipek1
M
J
“Specified procedure could not be found” along with “credui.dll is either not designed to run on Windows or it contains an error” how do I fix this is
Replies
0
Views
39
Jonah Garrason
J
Back
Top Bottom