积极答复者
sql2008 R2安装程序支持规则检测失败 windows management instrumentation服务 无法启动

问题
答案
-
One more thing can try, copy those files from good machine.
- 已建议为答案 Molly Chen_Moderator 2012年8月17日 3:21
- 已标记为答案 Molly Chen_Moderator 2012年8月21日 3:04
全部回复
-
也许你的WMI服务毁损了,或许你可以参考这个帖子来重新安装WMI服务之后,接着再安装SQL Server看看。
-
You may ask your windows admin to work on it. Can download wmidiag here http://www.microsoft.com/en-us/download/details.aspx?id=7684, run it on the machine to generate report that tells what's the problem and how to fix.
-
诊断报告出来了,有32个错误,看不太懂怎么解决。麻烦帮忙看下!
报告如下:
30983 00:48:19 (0) ** WMIDiag v2.1 started on 2012年8月15日 at 00:26.
30984 00:48:19 (0) **
30985 00:48:19 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
30986 00:48:19 (0) **
30987 00:48:19 (0) ** This script is not supported under any Microsoft standard support program or service.
30988 00:48:19 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
30989 00:48:19 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
30990 00:48:19 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
30991 00:48:19 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
30992 00:48:19 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
30993 00:48:19 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
30994 00:48:19 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
30995 00:48:19 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
30996 00:48:19 (0) ** of the possibility of such damages.
30997 00:48:19 (0) **
30998 00:48:19 (0) **
30999 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31000 00:48:19 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
31001 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31002 00:48:19 (0) **
31003 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31004 00:48:19 (0) ** Windows 7 - Service Pack 1 - 32-bit (7601) - User 'HEQIN-PC\ADMINISTRATOR' on computer 'HEQIN-PC'.
31005 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31006 00:48:19 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
31007 00:48:19 (0) ** INFO: => 30 possible incorrect shutdown(s) detected on:
31008 00:48:19 (0) ** - Shutdown on 11 April 2012 01:12:13 (GMT-0).
31009 00:48:19 (0) ** - Shutdown on 06 June 2012 04:03:02 (GMT-0).
31010 00:48:19 (0) ** - Shutdown on 15 June 2012 12:05:25 (GMT-0).
31011 00:48:19 (0) ** - Shutdown on 19 June 2012 11:33:08 (GMT-0).
31012 00:48:19 (0) ** - Shutdown on 21 June 2012 16:31:49 (GMT-0).
31013 00:48:19 (0) ** - Shutdown on 28 June 2012 02:34:18 (GMT-0).
31014 00:48:19 (0) ** - Shutdown on 28 June 2012 04:45:35 (GMT-0).
31015 00:48:19 (0) ** - Shutdown on 28 June 2012 12:02:13 (GMT-0).
31016 00:48:19 (0) ** - Shutdown on 28 June 2012 14:02:02 (GMT-0).
31017 00:48:19 (0) ** - Shutdown on 29 June 2012 03:42:50 (GMT-0).
31018 00:48:19 (0) ** - Shutdown on 29 June 2012 15:57:18 (GMT-0).
31019 00:48:19 (0) ** - Shutdown on 04 July 2012 12:34:33 (GMT-0).
31020 00:48:19 (0) ** - Shutdown on 04 July 2012 13:25:02 (GMT-0).
31021 00:48:19 (0) ** - Shutdown on 05 July 2012 15:02:39 (GMT-0).
31022 00:48:19 (0) ** - Shutdown on 05 July 2012 15:39:47 (GMT-0).
31023 00:48:19 (0) ** - Shutdown on 05 July 2012 15:55:27 (GMT-0).
31024 00:48:19 (0) ** - Shutdown on 05 July 2012 16:06:16 (GMT-0).
31025 00:48:19 (0) ** - Shutdown on 05 July 2012 16:26:01 (GMT-0).
31026 00:48:19 (0) ** - Shutdown on 06 July 2012 06:03:17 (GMT-0).
31027 00:48:19 (0) ** - Shutdown on 13 July 2012 19:10:40 (GMT-0).
31028 00:48:19 (0) ** - Shutdown on 21 July 2012 02:39:02 (GMT-0).
31029 00:48:19 (0) ** - Shutdown on 25 July 2012 01:00:04 (GMT-0).
31030 00:48:19 (0) ** - Shutdown on 26 July 2012 01:06:59 (GMT-0).
31031 00:48:19 (0) ** - Shutdown on 28 July 2012 12:27:05 (GMT-0).
31032 00:48:19 (0) ** - Shutdown on 28 July 2012 13:24:41 (GMT-0).
31033 00:48:19 (0) ** - Shutdown on 29 July 2012 01:51:26 (GMT-0).
31034 00:48:19 (0) ** - Shutdown on 03 August 2012 01:23:12 (GMT-0).
31035 00:48:19 (0) ** - Shutdown on 06 August 2012 09:59:56 (GMT-0).
31036 00:48:19 (0) ** - Shutdown on 06 August 2012 10:31:01 (GMT-0).
31037 00:48:19 (0) ** - Shutdown on 12 August 2012 08:51:04 (GMT-0).
31038 00:48:19 (0) **
31039 00:48:19 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
31040 00:48:19 (0) ** Drive type: ......................................................................................................... IDE (SAMSUNG HM250HI ATA Device).
31041 00:48:19 (0) ** There are no missing WMI system files: .............................................................................. OK.
31042 00:48:19 (0) ** There are no missing WMI repository files: .......................................................................... OK.
31043 00:48:19 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
31044 00:48:19 (0) ** AFTER running WMIDiag:
31045 00:48:19 (0) ** The WMI repository has a size of: ................................................................................... 29 MB.
31046 00:48:19 (0) ** - Disk free space on 'C:': .......................................................................................... 9340 MB.
31047 00:48:19 (0) ** - INDEX.BTR, 4939776 bytes, 2012/8/15 0:05:45
31048 00:48:19 (0) ** - MAPPING1.MAP, 68484 bytes, 2012/8/14 23:17:55
31049 00:48:19 (0) ** - MAPPING2.MAP, 68484 bytes, 2012/8/14 23:59:26
31050 00:48:19 (0) ** - OBJECTS.DATA, 25739264 bytes, 2012/8/15 0:05:45
31051 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31052 00:48:19 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
31053 00:48:19 (0) ** Windows Firewall Profile: ........................................................................................... PRIVATE.
31054 00:48:19 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
31055 00:48:19 (0) ** => This will prevent any WMI remote connectivity to this computer except
31056 00:48:19 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
31057 00:48:19 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
31058 00:48:19 (0) ** - 'Windows Management Instrumentation (WMI-In)'
31059 00:48:19 (0) ** - 'Windows Management Instrumentation (ASync-In)'
31060 00:48:19 (0) ** Verify the reported status for each of these three inbound rules below.
31061 00:48:19 (0) **
31062 00:48:19 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
31063 00:48:19 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
31064 00:48:19 (0) ** - You can adjust the configuration by executing the following command:
31065 00:48:19 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
31066 00:48:19 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
31067 00:48:19 (0) ** You can also enable each individual rule instead of activating the group rule.
31068 00:48:19 (0) **
31069 00:48:19 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. DISABLED.
31070 00:48:19 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
31071 00:48:19 (0) ** - You can adjust the configuration of this rule by executing the following command:
31072 00:48:19 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
31073 00:48:19 (0) **
31074 00:48:19 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... DISABLED.
31075 00:48:19 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine.
31076 00:48:19 (0) ** - You can adjust the configuration of this rule by executing the following command:
31077 00:48:19 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES'
31078 00:48:19 (0) **
31079 00:48:19 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ DISABLED.
31080 00:48:19 (0) ** => This will prevent any WMI inbound connectivity to this machine.
31081 00:48:19 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
31082 00:48:19 (0) ** - You can adjust the configuration of this rule by executing the following command:
31083 00:48:19 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
31084 00:48:19 (0) **
31085 00:48:19 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... DISABLED.
31086 00:48:19 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
31087 00:48:19 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
31088 00:48:19 (0) ** - You can adjust the configuration of this rule by executing the following command:
31089 00:48:19 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
31090 00:48:19 (0) **
31091 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31092 00:48:19 (0) ** DCOM Status: ........................................................................................................ OK.
31093 00:48:19 (0) ** WMI registry setup: ................................................................................................. OK.
31094 00:48:19 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
31095 00:48:19 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
31096 00:48:19 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
31097 00:48:19 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
31098 00:48:19 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
31099 00:48:19 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
31100 00:48:19 (0) ** this can prevent the service/application to work as expected.
31101 00:48:19 (0) **
31102 00:48:19 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
31103 00:48:19 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
31104 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31105 00:48:19 (0) ** WMI service DCOM setup: ............................................................................................. OK.
31106 00:48:19 (0) ** WMI components DCOM registrations: .................................................................................. OK.
31107 00:48:19 (0) ** WMI ProgID registrations: ........................................................................................... OK.
31108 00:48:19 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
31109 00:48:19 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
31110 00:48:19 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
31111 00:48:19 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
31112 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31113 00:48:19 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
31114 00:48:19 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
31115 00:48:19 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
31116 00:48:19 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
31117 00:48:19 (0) ** selecting 'Run as Administrator'.
31118 00:48:19 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
31119 00:48:19 (0) ** in the Task Scheduler within the right security context.
31120 00:48:19 (0) **
31121 00:48:19 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
31122 00:48:19 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
31123 00:48:19 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
31124 00:48:19 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
31125 00:48:19 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
31126 00:48:19 (0) **
31127 00:48:19 (0) ** Overall DCOM security status: ....................................................................................... OK.
31128 00:48:19 (0) ** Overall WMI security status: ........................................................................................ OK.
31129 00:48:19 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
31130 00:48:19 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
31131 00:48:19 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
31132 00:48:19 (0) ** 'select * from MSFT_SCMEventLogEvent'
31133 00:48:19 (0) **
31134 00:48:19 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
31135 00:48:19 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
31136 00:48:19 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
31137 00:48:19 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
31138 00:48:19 (0) ** - ROOT/SERVICEMODEL.
31139 00:48:19 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
31140 00:48:19 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
31141 00:48:19 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
31142 00:48:19 (0) ** i.e. 'WMIC.EXE /NODE:"HEQIN-PC" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
31143 00:48:19 (0) **
31144 00:48:19 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
31145 00:48:19 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
31146 00:48:19 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 32 ERROR(S)!
31147 00:48:19 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31148 00:48:19 (0) ** MOF Registration: ''
31149 00:48:19 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31150 00:48:19 (0) ** MOF Registration: ''
31151 00:48:19 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31152 00:48:19 (0) ** MOF Registration: ''
31153 00:48:19 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31154 00:48:19 (0) ** MOF Registration: ''
31155 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31156 00:48:19 (0) ** MOF Registration: ''
31157 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31158 00:48:19 (0) ** MOF Registration: ''
31159 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31160 00:48:19 (0) ** MOF Registration: ''
31161 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31162 00:48:19 (0) ** MOF Registration: ''
31163 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31164 00:48:19 (0) ** MOF Registration: ''
31165 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31166 00:48:19 (0) ** MOF Registration: ''
31167 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31168 00:48:19 (0) ** MOF Registration: ''
31169 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31170 00:48:19 (0) ** MOF Registration: ''
31171 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31172 00:48:19 (0) ** MOF Registration: ''
31173 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31174 00:48:19 (0) ** MOF Registration: ''
31175 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31176 00:48:19 (0) ** MOF Registration: ''
31177 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31178 00:48:19 (0) ** MOF Registration: ''
31179 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31180 00:48:19 (0) ** MOF Registration: ''
31181 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31182 00:48:19 (0) ** MOF Registration: ''
31183 00:48:19 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31184 00:48:19 (0) ** MOF Registration: ''
31185 00:48:19 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31186 00:48:19 (0) ** MOF Registration: ''
31187 00:48:19 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31188 00:48:19 (0) ** MOF Registration: ''
31189 00:48:19 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31190 00:48:19 (0) ** MOF Registration: ''
31191 00:48:19 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31192 00:48:19 (0) ** MOF Registration: ''
31193 00:48:19 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31194 00:48:19 (0) ** MOF Registration: ''
31195 00:48:19 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31196 00:48:19 (0) ** MOF Registration: ''
31197 00:48:19 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31198 00:48:19 (0) ** MOF Registration: ''
31199 00:48:19 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31200 00:48:19 (0) ** MOF Registration: ''
31201 00:48:19 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31202 00:48:19 (0) ** MOF Registration: ''
31203 00:48:19 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31204 00:48:19 (0) ** MOF Registration: ''
31205 00:48:19 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31206 00:48:19 (0) ** MOF Registration: ''
31207 00:48:19 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31208 00:48:19 (0) ** MOF Registration: ''
31209 00:48:19 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31210 00:48:19 (0) ** MOF Registration: ''
31211 00:48:19 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
31212 00:48:19 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
31213 00:48:19 (0) ** You can refresh the WMI class provider buffer with the following command:
31214 00:48:19 (0) **
31215 00:48:19 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
31216 00:48:19 (0) **
31217 00:48:19 (0) ** WMI MOF representations: ............................................................................................ OK.
31218 00:48:19 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
31219 00:48:19 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
31220 00:48:19 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
31221 00:48:19 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
31222 00:48:19 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
31223 00:48:19 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
31224 00:48:19 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
31225 00:48:19 (0) ** WMI static instances retrieved: ..................................................................................... 1764.
31226 00:48:19 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
31227 00:48:19 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
31228 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31229 00:48:19 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
31230 00:48:19 (0) ** DCOM: ............................................................................................................. 0.
31231 00:48:19 (0) ** WINMGMT: .......................................................................................................... 0.
31232 00:48:19 (0) ** WMIADAPTER: ....................................................................................................... 0.
31233 00:48:19 (0) **
31234 00:48:19 (0) ** # of additional Event Log events AFTER WMIDiag execution:
31235 00:48:19 (0) ** DCOM: ............................................................................................................. 0.
31236 00:48:19 (0) ** WINMGMT: .......................................................................................................... 0.
31237 00:48:19 (0) ** WMIADAPTER: ....................................................................................................... 0.
31238 00:48:19 (0) **
31239 00:48:19 (0) ** 32 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
31240 00:48:19 (0) ** => This error is typically a WMI error. This WMI error is due to:
31241 00:48:19 (0) ** - a missing WMI class definition or object.
31242 00:48:19 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
31243 00:48:19 (0) ** You can correct the missing class definitions by:
31244 00:48:19 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
31245 00:48:19 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
31246 00:48:19 (0) ** (This list can be built on a similar and working WMI Windows installation)
31247 00:48:19 (0) ** The following command line must be used:
31248 00:48:19 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
31249 00:48:19 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
31250 00:48:19 (0) ** with WMI by starting the ADAP process.
31251 00:48:19 (0) ** - a WMI repository corruption.
31252 00:48:19 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
31253 00:48:19 (0) ** to validate the WMI repository operations.
31254 00:48:19 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
31255 00:48:19 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
31256 00:48:19 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
31257 00:48:19 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
31258 00:48:19 (0) ** the WMI repository must be reconstructed.
31259 00:48:19 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
31260 00:48:19 (0) ** otherwise some applications may fail after the reconstruction.
31261 00:48:19 (0) ** This can be achieved with the following command:
31262 00:48:19 (0) ** i.e. 'WMIDiag ShowMOFErrors'
31263 00:48:19 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
31264 00:48:19 (0) ** ALL fixes previously mentioned.
31265 00:48:19 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
31266 00:48:19 (0) **
31267 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31268 00:48:19 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
31269 00:48:19 (0) ** INFO: Unexpected registry key value:
31270 00:48:19 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
31271 00:48:19 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
31272 00:48:19 (0) ** From the command line, the registry configuration can be corrected with the following command:
31273 00:48:19 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
31274 00:48:19 (0) **
31275 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31276 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31277 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31278 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31279 00:48:19 (0) **
31280 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31281 00:48:19 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
31282 00:48:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31283 00:48:19 (0) **
31284 00:48:19 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\ADMINISTRATOR\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_WIN7_.CLI.SP1.32_HEQIN-PC_2012.08.15_00.25.58.LOG' for details.
31285 00:48:19 (0) **
31286 00:48:19 (0) ** WMIDiag v2.1 ended on 2012年8月15日 at 00:48 (W:79 E:45 S:1).<filename.mof></filename.mof> -
* Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
31269 00:48:19 (0) ** INFO: Unexpected registry key value:
31270 00:48:19 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
31271 00:48:19 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
31272 00:48:19 (0) ** From the command line, the registry configuration can be corrected with the following command:
31273 00:48:19 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'根据出错信息:
应该把键值改为1
-
多谢!但还是存在这部分错误:
31146 00:48:19 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 32 ERROR(S)!
31147 00:48:19 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31148 00:48:19 (0) ** MOF Registration: ''
31149 00:48:19 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31150 00:48:19 (0) ** MOF Registration: ''
31151 00:48:19 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31152 00:48:19 (0) ** MOF Registration: ''
31153 00:48:19 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31154 00:48:19 (0) ** MOF Registration: ''
31155 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31156 00:48:19 (0) ** MOF Registration: ''
31157 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31158 00:48:19 (0) ** MOF Registration: ''
31159 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31160 00:48:19 (0) ** MOF Registration: ''
31161 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31162 00:48:19 (0) ** MOF Registration: ''
31163 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31164 00:48:19 (0) ** MOF Registration: ''
31165 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31166 00:48:19 (0) ** MOF Registration: ''
31167 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31168 00:48:19 (0) ** MOF Registration: ''
31169 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31170 00:48:19 (0) ** MOF Registration: ''
31171 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31172 00:48:19 (0) ** MOF Registration: ''
31173 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31174 00:48:19 (0) ** MOF Registration: ''
31175 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31176 00:48:19 (0) ** MOF Registration: ''
31177 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31178 00:48:19 (0) ** MOF Registration: ''
31179 00:48:19 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31180 00:48:19 (0) ** MOF Registration: ''
31181 00:48:19 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31182 00:48:19 (0) ** MOF Registration: ''
31183 00:48:19 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31184 00:48:19 (0) ** MOF Registration: ''
31185 00:48:19 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31186 00:48:19 (0) ** MOF Registration: ''
31187 00:48:19 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31188 00:48:19 (0) ** MOF Registration: ''
31189 00:48:19 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31190 00:48:19 (0) ** MOF Registration: ''
31191 00:48:19 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31192 00:48:19 (0) ** MOF Registration: ''
31193 00:48:19 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31194 00:48:19 (0) ** MOF Registration: ''
31195 00:48:19 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31196 00:48:19 (0) ** MOF Registration: ''
31197 00:48:19 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31198 00:48:19 (0) ** MOF Registration: ''
31199 00:48:19 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31200 00:48:19 (0) ** MOF Registration: ''
31201 00:48:19 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31202 00:48:19 (0) ** MOF Registration: ''
31203 00:48:19 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31204 00:48:19 (0) ** MOF Registration: ''
31205 00:48:19 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31206 00:48:19 (0) ** MOF Registration: ''
31207 00:48:19 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31208 00:48:19 (0) ** MOF Registration: ''
31209 00:48:19 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
31210 00:48:19 (0) ** MOF Registration: ''
31211 00:48:19 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
31212 00:48:19 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
31213 00:48:19 (0) ** You can refresh the WMI class provider buffer with the following command:
31214 00:48:19 (0) **
31215 00:48:19 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF' -
One more thing can try, copy those files from good machine.
- 已建议为答案 Molly Chen_Moderator 2012年8月17日 3:21
- 已标记为答案 Molly Chen_Moderator 2012年8月21日 3:04