Microsoft SQL Server
--
Questions
--
Followers
Top Experts
SQL Server Setup Failed to compile the Managed Object Format (MOF)
HI there,
I have a system that was upgrade from XP to Vista Business 32 bit.
I am trying to install SQL 2005 Express with the Advanced Tools.
The PC meets all the requirements finds and then begins the install process.
Everything is fine until we get to. SQL Server Database Services.
The progress bar is showing Installing WMI registration.
The install process fails with the error "SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
Below is a copy of the log that was generated.
Can any one help
Thanks
Paul
LOG:
Setting status of unmanaged components and removing unmanaged resources
Error Code: -2147023538
MSI (s) (E4!D0) [15:17:41:274]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
MSI (c) (18:60) [15:12:30:805]: Entering MsiProvideComponentFromDes
MSI (c) (18:60) [15:12:30:805]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (18:60) [15:12:30:852]: MsiProvideComponentFromDes
MSI (c) (18:60) [15:12:30:868]: Entering MsiProvideComponentFromDes
MSI (c) (18:60) [15:12:30:868]: MsiProvideComponentFromDes
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Tue Aug 28 15:17:41 2007
<Func Name='InstallMOF'>
Failed to compile file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
An error occured while processing item 2 defined on lines 10 - 13
Error occured in phase 3, Error number: 0x8007054e
Compiler returned error 0x8007054e
<EndFunc Name='InstallMOF' Return='-2147023538' GetLastError='0'>
    Error Code: -2147023538
Windows Error Text: Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.
 Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Thu Oct  5 12:22:41 2006
   Function Name: Do_sqlMofcomp
Source Line Number: 608
---- Context --------------------------
Setting status of unmanaged components and removing unmanaged resources
Error Code: -2147023538
I have a system that was upgrade from XP to Vista Business 32 bit.
I am trying to install SQL 2005 Express with the Advanced Tools.
The PC meets all the requirements finds and then begins the install process.
Everything is fine until we get to. SQL Server Database Services.
The progress bar is showing Installing WMI registration.
The install process fails with the error "SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
Below is a copy of the log that was generated.
Can any one help
Thanks
Paul
LOG:
Setting status of unmanaged components and removing unmanaged resources
Error Code: -2147023538
MSI (s) (E4!D0) [15:17:41:274]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
MSI (c) (18:60) [15:12:30:805]: Entering MsiProvideComponentFromDes
MSI (c) (18:60) [15:12:30:805]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (18:60) [15:12:30:852]: MsiProvideComponentFromDes
MSI (c) (18:60) [15:12:30:868]: Entering MsiProvideComponentFromDes
MSI (c) (18:60) [15:12:30:868]: MsiProvideComponentFromDes
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Tue Aug 28 15:17:41 2007
<Func Name='InstallMOF'>
Failed to compile file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmpro
An error occured while processing item 2 defined on lines 10 - 13
Error occured in phase 3, Error number: 0x8007054e
Compiler returned error 0x8007054e
<EndFunc Name='InstallMOF' Return='-2147023538' GetLastError='0'>
    Error Code: -2147023538
Windows Error Text: Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.
 Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Thu Oct  5 12:22:41 2006
   Function Name: Do_sqlMofcomp
Source Line Number: 608
---- Context --------------------------
Setting status of unmanaged components and removing unmanaged resources
Error Code: -2147023538
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Microsoft is pretty vague on their KB article about this at:
http://support.microsoft.com/?kbid=926623
but they suggest the following:
1. Start to install the release version of SQL Server 2005.
2. On the Installing Prerequisites page, click Next when the installation of the SQL Server 2005 Setup Support Files is complete.
3. On the next page, click Cancel.
http://support.microsoft.com/?kbid=926623
but they suggest the following:
1. Start to install the release version of SQL Server 2005.
2. On the Installing Prerequisites page, click Next when the installation of the SQL Server 2005 Setup Support Files is complete.
3. On the next page, click Cancel.
Hi there,
Thanks for the quick reply.
I've been to that page - what a load of help Microsoft are !
Didn't help me I'm afraid - I think it has something to do with WMI and the upgrade I have done from XP SP2 to Vista Business
Thanks Again for your post
Paul
Thanks for the quick reply.
I've been to that page - what a load of help Microsoft are !
Didn't help me I'm afraid - I think it has something to do with WMI and the upgrade I have done from XP SP2 to Vista Business
Thanks Again for your post
Paul
Did you by any chance try the WMI Diagnosis Utility to see if there are any problems with WMI and repair them if it can?
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Funny you should mention that.
I have just downloaded it and enclosed the basic report below.
I have no idea what it is saying yet, but I have picked out the first error of "catastrophic media failure or a data structure corruption" and am running a chkdsk and defrag to eliminate this as a problem.
If you can make any sense of the report then please help, if you need the full log then just ask.
Many Thanks
Paul
33570 16:07:20 (0) ** WMIDiag v2.0 started on 28 August 2007 at 15:25.
33571 16:07:20 (0) **
33572 16:07:20 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
33573 16:07:20 (0) **
33574 16:07:20 (0) ** This script is not supported under any Microsoft standard support program or service.
33575 16:07:20 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
33576 16:07:20 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
33577 16:07:20 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
33578 16:07:20 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
33579 16:07:20 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
33580 16:07:20 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
33581 16:07:20 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
33582 16:07:20 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
33583 16:07:20 (0) ** of the possibility of such damages.
33584 16:07:20 (0) **
33585 16:07:20 (0) **
33586 16:07:20 (0) ** --------------------------
33587 16:07:20 (0) ** --------------------------
33588 16:07:20 (0) ** --------------------------
33589 16:07:20 (0) **
33590 16:07:20 (0) ** --------------------------
33591 16:07:20 (0) ** Windows Vista - No service pack - 32-bit (6000) - User 'MYTELCRM\PAUL.ELLAWAY' on computer 'PAUL-PC'.
33592 16:07:20 (0) ** --------------------------
33593 16:07:20 (0) ** INFO: Environment: ..........................
33594 16:07:20 (0) ** INFO: => 34 incorrect shutdown(s) detected on:
33595 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 24 August 2007 13:42:19 (GMT-0).
33596 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 06 August 2007 11:25:10 (GMT-0).
33597 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 06 August 2007 11:03:19 (GMT-0).
33598 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 06 August 2007 07:03:14 (GMT-0).
33599 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 02 August 2007 10:23:01 (GMT-0).
33600 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 12 July 2007 09:29:33 (GMT-0).
33601 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 July 2007 08:28:37 (GMT-0).
33602 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 July 2007 06:33:58 (GMT-0).
33603 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 18 June 2007 06:12:38 (GMT-0).
33604 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 08 June 2007 14:37:18 (GMT-0).
33605 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 08 June 2007 13:40:54 (GMT-0).
33606 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 01 June 2007 06:03:36 (GMT-0).
33607 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 25 May 2007 08:40:30 (GMT-0).
33608 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 25 May 2007 06:37:07 (GMT-0).
33609 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 21 May 2007 07:20:25 (GMT-0).
33610 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 21 May 2007 07:09:33 (GMT-0).
33611 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 14 May 2007 11:28:29 (GMT-0).
33612 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 14 May 2007 11:20:21 (GMT-0).
33613 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 10 May 2007 11:49:30 (GMT-0).
33614 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 May 2007 06:25:23 (GMT-0).
33615 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 May 2007 04:59:35 (GMT-0).
33616 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 02 May 2007 04:33:54 (GMT-0).
33617 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 27 April 2007 09:51:35 (GMT-0).
33618 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 26 April 2007 19:46:41 (GMT-0).
33619 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 20 April 2007 06:13:36 (GMT-0).
33620 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 11 April 2007 10:13:37 (GMT-0).
33621 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 05 April 2007 08:56:16 (GMT-0).
33622 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 05 April 2007 07:40:19 (GMT-0).
33623 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 05 April 2007 07:32:36 (GMT-0).
33624 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 26 March 2007 12:41:16 (GMT-0).
33625 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 16 March 2007 10:08:52 (GMT-0).
33626 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 13 March 2007 08:04:02 (GMT-0).
33627 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 16 February 2007 09:34:17 (GMT-0).
33628 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 08 February 2007 09:24:08 (GMT-0).
33629 16:07:20 (0) **
33630 16:07:20 (0) ** System drive: ..........................
33631 16:07:20 (0) ** Drive type: ..........................
33632 16:07:20 (0) ** There are no missing WMI system files: ..........................
33633 16:07:20 (0) ** There are no missing WMI repository files: ..........................
33634 16:07:20 (0) ** WMI repository state: ..........................
33635 16:07:20 (0) ** BEFORE running WMIDiag:
33636 16:07:20 (0) ** The WMI repository has a size of: ..........................
33637 16:07:20 (0) ** - Disk free space on 'C:': ..........................
33638 16:07:20 (0) ** Â - INDEX.BTR, Â Â Â Â Â Â Â Â Â Â 3571712 bytes, Â Â Â 28/08/2007 15:17:52
33639 16:07:20 (0) ** Â - MAPPING1.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 15:17:52
33640 16:07:20 (0) ** Â - MAPPING2.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 15:12:52
33641 16:07:20 (0) ** Â - OBJECTS.DATA, Â Â Â Â Â Â Â Â Â 23986176 bytes, Â Â 28/08/2007 15:17:52
33642 16:07:20 (0) ** AFTER running WMIDiag:
33643 16:07:20 (0) ** The WMI repository has a size of: ..........................
33644 16:07:20 (0) ** - Disk free space on 'C:': ..........................
33645 16:07:20 (0) ** Â - INDEX.BTR, Â Â Â Â Â Â Â Â Â Â 3571712 bytes, Â Â Â 28/08/2007 16:00:52
33646 16:07:20 (0) ** Â - MAPPING1.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 16:00:52
33647 16:07:20 (0) ** Â - MAPPING2.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 15:56:22
33648 16:07:20 (0) ** Â - OBJECTS.DATA, Â Â Â Â Â Â Â Â Â 23986176 bytes, Â Â 28/08/2007 16:00:52
33649 16:07:20 (0) ** --------------------------
33650 16:07:20 (0) ** INFO: Windows Firewall status: ..........................
33651 16:07:20 (0) ** Windows Firewall Profile: ..........................
33652 16:07:20 (0) ** Inbound connections that do not match a rule BLOCKED: ..........................
33653 16:07:20 (0) ** => This will prevent any WMI remote connectivity to this computer except
33654 16:07:20 (0) ** Â Â if the following three inbound rules are ENABLED and non-BLOCKING:
33655 16:07:20 (0) ** Â Â - 'Windows Management Instrumentation (DCOM-In)'
33656 16:07:20 (0) ** Â Â - 'Windows Management Instrumentation (WMI-In)'
33657 16:07:20 (0) ** Â Â - 'Windows Management Instrumentation (ASync-In)'
33658 16:07:20 (0) ** Â Â Verify the reported status for each of these three inbound rules below.
33659 16:07:20 (0) **
33660 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ..........................
33661 16:07:20 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
33662 16:07:20 (0) ** Â Â - You can adjust the configuration by executing the following command:
33663 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
33664 16:07:20 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
33665 16:07:20 (0) ** Â Â Â You can also enable each individual rule instead of activating the group rule.
33666 16:07:20 (0) **
33667 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: ..........................
33668 16:07:20 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
33669 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33670 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
33671 16:07:20 (0) **
33672 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ..........................
33673 16:07:20 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine.
33674 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33675 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES'
33676 16:07:20 (0) **
33677 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ..........................
33678 16:07:20 (0) ** => This will prevent any WMI inbound connectivity to this machine.
33679 16:07:20 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
33680 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33681 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
33682 16:07:20 (0) **
33683 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ..........................
33684 16:07:20 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
33685 16:07:20 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
33686 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33687 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
33688 16:07:20 (0) **
33689 16:07:20 (0) ** --------------------------
33690 16:07:20 (0) ** DCOM Status: ..........................
33691 16:07:20 (0) ** WMI registry setup: ..........................
33692 16:07:20 (0) ** INFO: WMI service has dependents: ..........................
33693 16:07:20 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
33694 16:07:20 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
33695 16:07:20 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
33696 16:07:20 (0) ** Â Â Note: If the service is marked with (*), it means that the service/application uses WMI but
33697 16:07:20 (0) ** Â Â Â Â Â there is no hard dependency on WMI. However, if the WMI service is stopped,
33698 16:07:20 (0) ** Â Â Â Â Â this can prevent the service/application to work as expected.
33699 16:07:20 (0) **
33700 16:07:20 (0) ** RPCSS service: ..........................
33701 16:07:20 (0) ** WINMGMT service: ..........................
33702 16:07:20 (0) ** --------------------------
33703 16:07:20 (0) ** WMI service DCOM setup: ..........................
33704 16:07:20 (0) ** WMI components DCOM registrations: ..........................
33705 16:07:20 (0) ** WMI ProgID registrations: ..........................
33706 16:07:20 (0) ** WMI provider DCOM registrations: ..........................
33707 16:07:20 (0) ** WMI provider CIM registrations: ..........................
33708 16:07:20 (0) ** WMI provider CLSIDs: ..........................
33709 16:07:20 (0) ** WMI providers EXE/DLL availability: ..........................
33710 16:07:20 (0) ** --------------------------
33711 16:07:20 (0) ** INFO: User Account Control (UAC): ..........................
33712 16:07:20 (0) ** INFO: Local Account Filtering: ..........................
33713 16:07:20 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
33714 16:07:20 (0) ** Â Â privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
33715 16:07:20 (0) ** Â Â to ensure that administrative privileges are granted. If a Local User account is used for remote
33716 16:07:20 (0) ** Â Â accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
33717 16:07:20 (0) **
33718 16:07:20 (0) ** Overall DCOM security status: ..........................
33719 16:07:20 (0) ** Overall WMI security status: ..........................
33720 16:07:20 (0) ** - Started at 'Root' --------------------------
33721 16:07:20 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ..........................
33722 16:07:20 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Na
33723 16:07:20 (0) ** Â 'select * from MSFT_SCMEventLogEvent'
33724 16:07:20 (0) **
33725 16:07:20 (0) ** WMI TIMER instruction(s): ..........................
33726 16:07:20 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: ..........................
33727 16:07:20 (0) ** - ROOT/CIMV2/SECURITY/MICROS
33728 16:07:20 (0) ** - ROOT/CIMV2/TERMINALSERVICE
33729 16:07:20 (0) ** - ROOT/MICROSOFTIISV2.
33730 16:07:20 (0) ** - ROOT/WEBADMINISTRATION.
33731 16:07:20 (0) ** - ROOT/SERVICEMODEL.
33732 16:07:20 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
33733 16:07:20 (0) ** Â Â use an encrypted connection by specifying the PACKET PRIVACY authentication level.
33734 16:07:20 (0) ** Â Â (RPC_C_AUTHN_LEVEL_PKT_PRI
33735 16:07:20 (0) ** Â Â i.e. 'WMIC.EXE /NODE:"PAUL-PC" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEM
33736 16:07:20 (0) **
33737 16:07:20 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: ..........................
33738 16:07:20 (0) ** - ROOT/CIMV2/APPLICATIONS, 0x80070002 - Unable to open registry key "HKLM\SOFTWARE\Microsoft\W
33739 16:07:20 (0) ** - ROOT/SECURITYCENTER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33740 16:07:20 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33741 16:07:20 (0) **
33742 16:07:20 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: ..........................
33743 16:07:20 (0) ** - ROOT/CIMV2/APPLICATIONS, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33744 16:07:20 (0) ** - ROOT/SECURITYCENTER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33745 16:07:20 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33746 16:07:20 (0) ** - Root/CIMV2/Applications, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33747 16:07:20 (0) ** - Root/SecurityCenter, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33748 16:07:20 (0) **
33749 16:07:20 (1) !! ERROR: WMI GET operation errors reported: ..........................
33750 16:07:20 (0) ** - Root/CIMV2, Win32_ShadowProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33751 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33752 16:07:21 (0) ** - Root/WMI, MSNdis_CoDriverVersion, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33753 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33754 16:07:21 (0) ** - Root/WMI, MSNdis_CoLinkSpeed, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33755 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33756 16:07:21 (0) ** - Root/WMI, MSNdis_CoVendorDescription
33757 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33758 16:07:21 (0) ** - Root/WMI, MSNdis_CoMacOptions, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33759 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33760 16:07:21 (0) ** - Root/WMI, MSNdis_CoVendorId, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33761 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33762 16:07:21 (0) ** - Root/aspnet, BaseErrorEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33763 16:07:21 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33764 16:07:21 (0) ** - Root/aspnet, RequestErrorEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33765 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33766 16:07:22 (0) ** - Root/aspnet, ErrorEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33767 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33768 16:07:22 (0) ** - Root/aspnet, RequestEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33769 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33770 16:07:22 (0) ** - Root/aspnet, HeartbeatEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33771 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33772 16:07:22 (0) **
33773 16:07:22 (0) ** WMI MOF representations: ..........................
33774 16:07:22 (0) ** WMI QUALIFIER access operations: ..........................
33775 16:07:22 (1) !! ERROR: WMI ENUMERATION operation errors reported: ..........................
33776 16:07:22 (0) ** - ROOT/MICROSOFT/HOMENET, InstancesOfAsync, 'HNet_IcsSettings', 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33777 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33778 16:07:22 (0) **
33779 16:07:22 (0) ** WMI EXECQUERY operations: ..........................
33780 16:07:22 (0) ** WMI GET VALUE operations: ..........................
33781 16:07:22 (0) ** WMI WRITE operations: ..........................
33782 16:07:22 (0) ** WMI PUT operations: ..........................
33783 16:07:22 (0) ** WMI DELETE operations: ..........................
33784 16:07:22 (0) ** WMI static instances retrieved: ..........................
33785 16:07:22 (0) ** WMI dynamic instances retrieved: ..........................
33786 16:07:22 (0) ** WMI instance request cancellations (to limit performance impact): ..........................
33787 16:07:22 (0) ** --------------------------
33788 16:07:22 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
33789 16:07:22 (0) ** Â DCOM: ..........................
33790 16:07:22 (0) ** Â WINMGMT: ..........................
33791 16:07:22 (0) ** Â WMIADAPTER: ..........................
33792 16:07:22 (0) **
33793 16:07:22 (0) ** # of additional Event Log events AFTER WMIDiag execution:
33794 16:07:22 (0) ** Â DCOM: ..........................
33795 16:07:22 (0) ** Â WINMGMT: ..........................
33796 16:07:22 (0) ** Â WMIADAPTER: ..........................
33797 16:07:22 (0) **
33798 16:07:22 (0) ** 1 error(s) 0x80070002 - (WBEM_UNKNOWN) This error code is external to WMI.
33799 16:07:22 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
33800 16:07:22 (0) ** Â Â with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x0002)
33801 16:07:22 (0) ** Â Â converted in decimal (2).
33802 16:07:22 (0) ** Â Â - NET HELPMSG 2
33803 16:07:22 (0) **
33804 16:07:22 (0) **
33805 16:07:22 (0) ** 8 error(s) 0x8007054E - (WBEM_UNKNOWN) This error code is external to WMI.
33806 16:07:22 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
33807 16:07:22 (0) ** Â Â with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x054E)
33808 16:07:22 (0) ** Â Â converted in decimal (1358).
33809 16:07:22 (0) ** Â Â - NET HELPMSG 1358
33810 16:07:22 (0) **
33811 16:07:22 (0) **
33812 16:07:22 (0) ** 11 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
33813 16:07:22 (0) ** => This error is typically a WMI error. This WMI error is due to:
33814 16:07:22 (0) ** Â Â - a missing WMI class definition or object.
33815 16:07:22 (0) ** Â Â Â (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
33816 16:07:22 (0) ** Â Â Â You can correct the missing class definitions by:
33817 16:07:22 (0) ** Â Â Â - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
33818 16:07:22 (0) ** Â Â Â Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
33819 16:07:22 (0) ** Â Â Â Â Â Â (This list can be built on a similar and working WMI Windows installation)
33820 16:07:22 (0) ** Â Â Â Â Â Â The following command line must be used:
33821 16:07:22 (0) ** Â Â Â Â Â Â i.e. 'WMIDiag CorrelateClassAndProvider'
33822 16:07:22 (0) ** Â Â - a WMI repository corruption.
33823 16:07:22 (0) ** Â Â Â In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
33824 16:07:22 (0) ** Â Â Â to validate the WMI repository operations.
33825 16:07:22 (0) ** Â Â Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
33826 16:07:22 (0) ** Â Â Â Â Â executing the WriteInRepository command. To write temporary data from the Root namespace, use:
33827 16:07:22 (0) ** Â Â Â Â Â i.e. 'WMIDiag WriteInRepository=Root'
33828 16:07:22 (0) ** Â Â - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
33829 16:07:22 (0) ** Â Â Â the WMI repository must be reconstructed.
33830 16:07:22 (0) ** Â Â Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
33831 16:07:22 (0) ** Â Â Â Â Â otherwise some applications may fail after the reconstruction.
33832 16:07:22 (0) ** Â Â Â Â Â This can be achieved with the following command:
33833 16:07:22 (0) ** Â Â Â Â Â i.e. 'WMIDiag ShowMOFErrors'
33834 16:07:22 (0) ** Â Â Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
33835 16:07:22 (0) ** Â Â Â Â Â ALL fixes previously mentioned.
33836 16:07:22 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
33837 16:07:22 (0) **
33838 16:07:22 (0) ** --------------------------
33839 16:07:22 (0) ** WMI Registry key setup: ..........................
33840 16:07:22 (0) ** --------------------------
33841 16:07:22 (0) ** --------------------------
33842 16:07:22 (0) ** --------------------------
33843 16:07:22 (0) ** --------------------------
33844 16:07:22 (0) **
33845 16:07:22 (0) ** --------------------------
33846 16:07:22 (0) ** --------------------------
33847 16:07:22 (0) ** --------------------------
33848 16:07:22 (0) **
33849 16:07:22 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Â Check 'C:\USERS\PAUL.ELLAWAY.MYT
33850 16:07:22 (0) **
33851 16:07:22 (0) ** WMIDiag v2.0 ended on 28 August 2007 at 16:07 (W:92 E:21 S:1).
I have just downloaded it and enclosed the basic report below.
I have no idea what it is saying yet, but I have picked out the first error of "catastrophic media failure or a data structure corruption" and am running a chkdsk and defrag to eliminate this as a problem.
If you can make any sense of the report then please help, if you need the full log then just ask.
Many Thanks
Paul
33570 16:07:20 (0) ** WMIDiag v2.0 started on 28 August 2007 at 15:25.
33571 16:07:20 (0) **
33572 16:07:20 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
33573 16:07:20 (0) **
33574 16:07:20 (0) ** This script is not supported under any Microsoft standard support program or service.
33575 16:07:20 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
33576 16:07:20 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
33577 16:07:20 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
33578 16:07:20 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
33579 16:07:20 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
33580 16:07:20 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
33581 16:07:20 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
33582 16:07:20 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
33583 16:07:20 (0) ** of the possibility of such damages.
33584 16:07:20 (0) **
33585 16:07:20 (0) **
33586 16:07:20 (0) ** --------------------------
33587 16:07:20 (0) ** --------------------------
33588 16:07:20 (0) ** --------------------------
33589 16:07:20 (0) **
33590 16:07:20 (0) ** --------------------------
33591 16:07:20 (0) ** Windows Vista - No service pack - 32-bit (6000) - User 'MYTELCRM\PAUL.ELLAWAY' on computer 'PAUL-PC'.
33592 16:07:20 (0) ** --------------------------
33593 16:07:20 (0) ** INFO: Environment: ..........................
33594 16:07:20 (0) ** INFO: => 34 incorrect shutdown(s) detected on:
33595 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 24 August 2007 13:42:19 (GMT-0).
33596 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 06 August 2007 11:25:10 (GMT-0).
33597 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 06 August 2007 11:03:19 (GMT-0).
33598 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 06 August 2007 07:03:14 (GMT-0).
33599 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 02 August 2007 10:23:01 (GMT-0).
33600 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 12 July 2007 09:29:33 (GMT-0).
33601 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 July 2007 08:28:37 (GMT-0).
33602 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 July 2007 06:33:58 (GMT-0).
33603 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 18 June 2007 06:12:38 (GMT-0).
33604 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 08 June 2007 14:37:18 (GMT-0).
33605 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 08 June 2007 13:40:54 (GMT-0).
33606 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 01 June 2007 06:03:36 (GMT-0).
33607 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 25 May 2007 08:40:30 (GMT-0).
33608 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 25 May 2007 06:37:07 (GMT-0).
33609 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 21 May 2007 07:20:25 (GMT-0).
33610 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 21 May 2007 07:09:33 (GMT-0).
33611 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 14 May 2007 11:28:29 (GMT-0).
33612 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 14 May 2007 11:20:21 (GMT-0).
33613 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 10 May 2007 11:49:30 (GMT-0).
33614 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 May 2007 06:25:23 (GMT-0).
33615 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 09 May 2007 04:59:35 (GMT-0).
33616 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 02 May 2007 04:33:54 (GMT-0).
33617 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 27 April 2007 09:51:35 (GMT-0).
33618 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 26 April 2007 19:46:41 (GMT-0).
33619 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 20 April 2007 06:13:36 (GMT-0).
33620 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 11 April 2007 10:13:37 (GMT-0).
33621 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 05 April 2007 08:56:16 (GMT-0).
33622 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 05 April 2007 07:40:19 (GMT-0).
33623 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 05 April 2007 07:32:36 (GMT-0).
33624 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 26 March 2007 12:41:16 (GMT-0).
33625 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 16 March 2007 10:08:52 (GMT-0).
33626 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 13 March 2007 08:04:02 (GMT-0).
33627 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 16 February 2007 09:34:17 (GMT-0).
33628 16:07:20 (0) ** Â Â Â Â Â - Shutdown on 08 February 2007 09:24:08 (GMT-0).
33629 16:07:20 (0) **
33630 16:07:20 (0) ** System drive: ..........................
33631 16:07:20 (0) ** Drive type: ..........................
33632 16:07:20 (0) ** There are no missing WMI system files: ..........................
33633 16:07:20 (0) ** There are no missing WMI repository files: ..........................
33634 16:07:20 (0) ** WMI repository state: ..........................
33635 16:07:20 (0) ** BEFORE running WMIDiag:
33636 16:07:20 (0) ** The WMI repository has a size of: ..........................
33637 16:07:20 (0) ** - Disk free space on 'C:': ..........................
33638 16:07:20 (0) ** Â - INDEX.BTR, Â Â Â Â Â Â Â Â Â Â 3571712 bytes, Â Â Â 28/08/2007 15:17:52
33639 16:07:20 (0) ** Â - MAPPING1.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 15:17:52
33640 16:07:20 (0) ** Â - MAPPING2.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 15:12:52
33641 16:07:20 (0) ** Â - OBJECTS.DATA, Â Â Â Â Â Â Â Â Â 23986176 bytes, Â Â 28/08/2007 15:17:52
33642 16:07:20 (0) ** AFTER running WMIDiag:
33643 16:07:20 (0) ** The WMI repository has a size of: ..........................
33644 16:07:20 (0) ** - Disk free space on 'C:': ..........................
33645 16:07:20 (0) ** Â - INDEX.BTR, Â Â Â Â Â Â Â Â Â Â 3571712 bytes, Â Â Â 28/08/2007 16:00:52
33646 16:07:20 (0) ** Â - MAPPING1.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 16:00:52
33647 16:07:20 (0) ** Â - MAPPING2.MAP, Â Â Â Â Â Â Â Â Â 78616 bytes, Â Â Â Â 28/08/2007 15:56:22
33648 16:07:20 (0) ** Â - OBJECTS.DATA, Â Â Â Â Â Â Â Â Â 23986176 bytes, Â Â 28/08/2007 16:00:52
33649 16:07:20 (0) ** --------------------------
33650 16:07:20 (0) ** INFO: Windows Firewall status: ..........................
33651 16:07:20 (0) ** Windows Firewall Profile: ..........................
33652 16:07:20 (0) ** Inbound connections that do not match a rule BLOCKED: ..........................
33653 16:07:20 (0) ** => This will prevent any WMI remote connectivity to this computer except
33654 16:07:20 (0) ** Â Â if the following three inbound rules are ENABLED and non-BLOCKING:
33655 16:07:20 (0) ** Â Â - 'Windows Management Instrumentation (DCOM-In)'
33656 16:07:20 (0) ** Â Â - 'Windows Management Instrumentation (WMI-In)'
33657 16:07:20 (0) ** Â Â - 'Windows Management Instrumentation (ASync-In)'
33658 16:07:20 (0) ** Â Â Verify the reported status for each of these three inbound rules below.
33659 16:07:20 (0) **
33660 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ..........................
33661 16:07:20 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
33662 16:07:20 (0) ** Â Â - You can adjust the configuration by executing the following command:
33663 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
33664 16:07:20 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
33665 16:07:20 (0) ** Â Â Â You can also enable each individual rule instead of activating the group rule.
33666 16:07:20 (0) **
33667 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: ..........................
33668 16:07:20 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
33669 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33670 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
33671 16:07:20 (0) **
33672 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ..........................
33673 16:07:20 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine.
33674 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33675 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES'
33676 16:07:20 (0) **
33677 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ..........................
33678 16:07:20 (0) ** => This will prevent any WMI inbound connectivity to this machine.
33679 16:07:20 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
33680 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33681 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
33682 16:07:20 (0) **
33683 16:07:20 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ..........................
33684 16:07:20 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
33685 16:07:20 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
33686 16:07:20 (0) ** Â Â - You can adjust the configuration of this rule by executing the following command:
33687 16:07:20 (0) ** Â Â i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
33688 16:07:20 (0) **
33689 16:07:20 (0) ** --------------------------
33690 16:07:20 (0) ** DCOM Status: ..........................
33691 16:07:20 (0) ** WMI registry setup: ..........................
33692 16:07:20 (0) ** INFO: WMI service has dependents: ..........................
33693 16:07:20 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
33694 16:07:20 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
33695 16:07:20 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
33696 16:07:20 (0) ** Â Â Note: If the service is marked with (*), it means that the service/application uses WMI but
33697 16:07:20 (0) ** Â Â Â Â Â there is no hard dependency on WMI. However, if the WMI service is stopped,
33698 16:07:20 (0) ** Â Â Â Â Â this can prevent the service/application to work as expected.
33699 16:07:20 (0) **
33700 16:07:20 (0) ** RPCSS service: ..........................
33701 16:07:20 (0) ** WINMGMT service: ..........................
33702 16:07:20 (0) ** --------------------------
33703 16:07:20 (0) ** WMI service DCOM setup: ..........................
33704 16:07:20 (0) ** WMI components DCOM registrations: ..........................
33705 16:07:20 (0) ** WMI ProgID registrations: ..........................
33706 16:07:20 (0) ** WMI provider DCOM registrations: ..........................
33707 16:07:20 (0) ** WMI provider CIM registrations: ..........................
33708 16:07:20 (0) ** WMI provider CLSIDs: ..........................
33709 16:07:20 (0) ** WMI providers EXE/DLL availability: ..........................
33710 16:07:20 (0) ** --------------------------
33711 16:07:20 (0) ** INFO: User Account Control (UAC): ..........................
33712 16:07:20 (0) ** INFO: Local Account Filtering: ..........................
33713 16:07:20 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
33714 16:07:20 (0) ** Â Â privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
33715 16:07:20 (0) ** Â Â to ensure that administrative privileges are granted. If a Local User account is used for remote
33716 16:07:20 (0) ** Â Â accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
33717 16:07:20 (0) **
33718 16:07:20 (0) ** Overall DCOM security status: ..........................
33719 16:07:20 (0) ** Overall WMI security status: ..........................
33720 16:07:20 (0) ** - Started at 'Root' --------------------------
33721 16:07:20 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ..........................
33722 16:07:20 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Na
33723 16:07:20 (0) ** Â 'select * from MSFT_SCMEventLogEvent'
33724 16:07:20 (0) **
33725 16:07:20 (0) ** WMI TIMER instruction(s): ..........................
33726 16:07:20 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: ..........................
33727 16:07:20 (0) ** - ROOT/CIMV2/SECURITY/MICROS
33728 16:07:20 (0) ** - ROOT/CIMV2/TERMINALSERVICE
33729 16:07:20 (0) ** - ROOT/MICROSOFTIISV2.
33730 16:07:20 (0) ** - ROOT/WEBADMINISTRATION.
33731 16:07:20 (0) ** - ROOT/SERVICEMODEL.
33732 16:07:20 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
33733 16:07:20 (0) ** Â Â use an encrypted connection by specifying the PACKET PRIVACY authentication level.
33734 16:07:20 (0) ** Â Â (RPC_C_AUTHN_LEVEL_PKT_PRI
33735 16:07:20 (0) ** Â Â i.e. 'WMIC.EXE /NODE:"PAUL-PC" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEM
33736 16:07:20 (0) **
33737 16:07:20 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: ..........................
33738 16:07:20 (0) ** - ROOT/CIMV2/APPLICATIONS, 0x80070002 - Unable to open registry key "HKLM\SOFTWARE\Microsoft\W
33739 16:07:20 (0) ** - ROOT/SECURITYCENTER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33740 16:07:20 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33741 16:07:20 (0) **
33742 16:07:20 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: ..........................
33743 16:07:20 (0) ** - ROOT/CIMV2/APPLICATIONS, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33744 16:07:20 (0) ** - ROOT/SECURITYCENTER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33745 16:07:20 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33746 16:07:20 (0) ** - Root/CIMV2/Applications, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33747 16:07:20 (0) ** - Root/SecurityCenter, 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33748 16:07:20 (0) **
33749 16:07:20 (1) !! ERROR: WMI GET operation errors reported: ..........................
33750 16:07:20 (0) ** - Root/CIMV2, Win32_ShadowProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33751 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33752 16:07:21 (0) ** - Root/WMI, MSNdis_CoDriverVersion, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33753 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33754 16:07:21 (0) ** - Root/WMI, MSNdis_CoLinkSpeed, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33755 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33756 16:07:21 (0) ** - Root/WMI, MSNdis_CoVendorDescription
33757 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33758 16:07:21 (0) ** - Root/WMI, MSNdis_CoMacOptions, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33759 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33760 16:07:21 (0) ** - Root/WMI, MSNdis_CoVendorId, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33761 16:07:21 (0) ** Â MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\
33762 16:07:21 (0) ** - Root/aspnet, BaseErrorEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33763 16:07:21 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33764 16:07:21 (0) ** - Root/aspnet, RequestErrorEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33765 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33766 16:07:22 (0) ** - Root/aspnet, ErrorEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33767 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33768 16:07:22 (0) ** - Root/aspnet, RequestEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33769 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33770 16:07:22 (0) ** - Root/aspnet, HeartbeatEvent, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
33771 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33772 16:07:22 (0) **
33773 16:07:22 (0) ** WMI MOF representations: ..........................
33774 16:07:22 (0) ** WMI QUALIFIER access operations: ..........................
33775 16:07:22 (1) !! ERROR: WMI ENUMERATION operation errors reported: ..........................
33776 16:07:22 (0) ** - ROOT/MICROSOFT/HOMENET, InstancesOfAsync, 'HNet_IcsSettings', 0x8007054E - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk..
33777 16:07:22 (0) ** Â MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
33778 16:07:22 (0) **
33779 16:07:22 (0) ** WMI EXECQUERY operations: ..........................
33780 16:07:22 (0) ** WMI GET VALUE operations: ..........................
33781 16:07:22 (0) ** WMI WRITE operations: ..........................
33782 16:07:22 (0) ** WMI PUT operations: ..........................
33783 16:07:22 (0) ** WMI DELETE operations: ..........................
33784 16:07:22 (0) ** WMI static instances retrieved: ..........................
33785 16:07:22 (0) ** WMI dynamic instances retrieved: ..........................
33786 16:07:22 (0) ** WMI instance request cancellations (to limit performance impact): ..........................
33787 16:07:22 (0) ** --------------------------
33788 16:07:22 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
33789 16:07:22 (0) ** Â DCOM: ..........................
33790 16:07:22 (0) ** Â WINMGMT: ..........................
33791 16:07:22 (0) ** Â WMIADAPTER: ..........................
33792 16:07:22 (0) **
33793 16:07:22 (0) ** # of additional Event Log events AFTER WMIDiag execution:
33794 16:07:22 (0) ** Â DCOM: ..........................
33795 16:07:22 (0) ** Â WINMGMT: ..........................
33796 16:07:22 (0) ** Â WMIADAPTER: ..........................
33797 16:07:22 (0) **
33798 16:07:22 (0) ** 1 error(s) 0x80070002 - (WBEM_UNKNOWN) This error code is external to WMI.
33799 16:07:22 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
33800 16:07:22 (0) ** Â Â with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x0002)
33801 16:07:22 (0) ** Â Â converted in decimal (2).
33802 16:07:22 (0) ** Â Â - NET HELPMSG 2
33803 16:07:22 (0) **
33804 16:07:22 (0) **
33805 16:07:22 (0) ** 8 error(s) 0x8007054E - (WBEM_UNKNOWN) This error code is external to WMI.
33806 16:07:22 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found
33807 16:07:22 (0) ** Â Â with the 'NET.EXE HELPMSG <dddd>' command, where <dddd> is the last four hex digits (0x054E)
33808 16:07:22 (0) ** Â Â converted in decimal (1358).
33809 16:07:22 (0) ** Â Â - NET HELPMSG 1358
33810 16:07:22 (0) **
33811 16:07:22 (0) **
33812 16:07:22 (0) ** 11 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
33813 16:07:22 (0) ** => This error is typically a WMI error. This WMI error is due to:
33814 16:07:22 (0) ** Â Â - a missing WMI class definition or object.
33815 16:07:22 (0) ** Â Â Â (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
33816 16:07:22 (0) ** Â Â Â You can correct the missing class definitions by:
33817 16:07:22 (0) ** Â Â Â - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
33818 16:07:22 (0) ** Â Â Â Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
33819 16:07:22 (0) ** Â Â Â Â Â Â (This list can be built on a similar and working WMI Windows installation)
33820 16:07:22 (0) ** Â Â Â Â Â Â The following command line must be used:
33821 16:07:22 (0) ** Â Â Â Â Â Â i.e. 'WMIDiag CorrelateClassAndProvider'
33822 16:07:22 (0) ** Â Â - a WMI repository corruption.
33823 16:07:22 (0) ** Â Â Â In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
33824 16:07:22 (0) ** Â Â Â to validate the WMI repository operations.
33825 16:07:22 (0) ** Â Â Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
33826 16:07:22 (0) ** Â Â Â Â Â executing the WriteInRepository command. To write temporary data from the Root namespace, use:
33827 16:07:22 (0) ** Â Â Â Â Â i.e. 'WMIDiag WriteInRepository=Root'
33828 16:07:22 (0) ** Â Â - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
33829 16:07:22 (0) ** Â Â Â the WMI repository must be reconstructed.
33830 16:07:22 (0) ** Â Â Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
33831 16:07:22 (0) ** Â Â Â Â Â otherwise some applications may fail after the reconstruction.
33832 16:07:22 (0) ** Â Â Â Â Â This can be achieved with the following command:
33833 16:07:22 (0) ** Â Â Â Â Â i.e. 'WMIDiag ShowMOFErrors'
33834 16:07:22 (0) ** Â Â Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
33835 16:07:22 (0) ** Â Â Â Â Â ALL fixes previously mentioned.
33836 16:07:22 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
33837 16:07:22 (0) **
33838 16:07:22 (0) ** --------------------------
33839 16:07:22 (0) ** WMI Registry key setup: ..........................
33840 16:07:22 (0) ** --------------------------
33841 16:07:22 (0) ** --------------------------
33842 16:07:22 (0) ** --------------------------
33843 16:07:22 (0) ** --------------------------
33844 16:07:22 (0) **
33845 16:07:22 (0) ** --------------------------
33846 16:07:22 (0) ** --------------------------
33847 16:07:22 (0) ** --------------------------
33848 16:07:22 (0) **
33849 16:07:22 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Â Check 'C:\USERS\PAUL.ELLAWAY.MYT
33850 16:07:22 (0) **
33851 16:07:22 (0) ** WMIDiag v2.0 ended on 28 August 2007 at 16:07 (W:92 E:21 S:1).
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Thanks for all the help.
Amending the Wbem solved the install error that I was being faced with.
After this part was solved there were still many hurdles to overcome, but finally SQL Express was installed.
Thanks Again
Paul
Amending the Wbem solved the install error that I was being faced with.
After this part was solved there were still many hurdles to overcome, but finally SQL Express was installed.
Thanks Again
Paul
Swindle that was excellent! I've been hunting round Microsoft for ages for a solution to this and your answer fixed it for me.
Thanks a million.
Chris.
Thanks a million.
Chris.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
i had the same problem here try to reinstall WMI, re register dll files that refer to WMI
also stop WMI amd rename repository folder and start the service again but it dident help me out. unable to install sql 2005 express on windows 2003 server
also stop WMI amd rename repository folder and start the service again but it dident help me out. unable to install sql 2005 express on windows 2003 server
Microsoft SQL Server
--
Questions
--
Followers
Top Experts
Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.