主页 / user-438946

SPottuit's questions

Martin Hope
SPottuit
Asked: 2017-10-18 03:29:13 +0800 CST
  • 0

我的 VM SCCM windows 2012 R2 服务器无法在我的 windows 7 VM 上获取 sccm 客户端。

我尝试了客户端推送并且 CCMSetup.exe 正在运行，但最终停止。

ccmsetup.log 给我GetDPLocations failed with error 0x80004005：

<![LOG[Sending message header '<Msg SchemaVersion="1.1"><ID>{50C62C2C-DD4B-4314-9623-C554140C1312}</ID><SourceHost>DIEDERIKSPC</SourceHost>
<TargetAddress>mp:[http]MP_LocationManager</TargetAddress>
<ReplyTo>direct:DIEDERIKSPC:LS_ReplyLocations</ReplyTo>
<Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion>
<TargetHost>WIN-52BO8J9011M.poliforma.nl</TargetHost>
<TargetEndpoint>MP_LocationManager</TargetEndpoint>
<ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2017-10-09T16:48:38Z</SentTime><Body Type="ByteRange" Offset="0" Length="1120"/><Hooks>
<Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>']LOG]!>
<time="18:48:38.081-120" date="10-09-2017" component="ccmsetup" context="" type="0" thread="868" file="siteinfo.cpp:177">
<![LOG[CCM_POST 'HTTP://WIN-52BO8J9011M.poliforma.nl/ccm_system/request']LOG]!><time="18:48:38.081-120" date="10-09-2017" component="ccmsetup" context="" type="1" thread="868" file="httphelper.cpp:807">
<![LOG[Failed to receive ccm message response. Status code = 404]LOG]!><time="18:48:38.096-120" date="10-09-2017" component="ccmsetup" context="" type="2" thread="868" file="httphelper.cpp:1694">
<![LOG[GetDPLocations failed with error 0x80004005]LOG]!>
<time="18:48:38.096-120" date="10-09-2017" component="ccmsetup" context="" type="3" thread="868" file="siteinfo.cpp:532">
<![LOG[Failed to get DP locations as the expected version from MP 'WIN-52BO8J9011M.poliforma.nl'. Error 0x80004005]LOG]!><time="18:48:38.096-120" date="10-09-2017" component="ccmsetup" context="" type="2" thread="868" file="ccmsetup.cpp:10926">
<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='101' will not be sent.]LOG]!><time="18:48:38.096-120" date="10-09-2017" component="ccmsetup" context="" type="1" thread="868" file="ccmsetup.cpp:9428">
<![LOG[Next retry in 10 minute(s)...]LOG]!><time="18:48:38.096-120" date="10-09-2017" component="ccmsetup" context="" type="0" thread="868" file="ccmsetup.cpp:8498">

我的 SCCM 站点已发布到我的域。我已将 domainadmin 设置为客户端推送安装的帐户。我以管理员身份运行 Extadsch.exe。我有一个系统管理容器，授予我的 sccm 服务器完全权限。我使用组策略允许防火墙上的入站和出站端口：

  • TCP 80,443,445,10123,135,2701,8530,1433,4022
  • UDP 9,25536,67,68,135
  • 文件和打印机共享，
  • WMI

已安装远程差分压缩功能。

我安装了 BITS 功能。我还注意到在 sccm 中找不到用户。我不知道这是否有问题，但我启用了 AD 用户和组发现。

ccmsetup.log 现在不同了：

<![LOG[Received header '<Msg SchemaVersion="1.1">
<ID>{CC1F4564-DD1E-46D2-9771-E10CE01041EE}</ID>
<SourceID>GUID:49295132-F8E6-4600-9903-51390C758F97</SourceID>
<SourceHost>WIN-52BO8J9011M</SourceHost>
<TargetAddress>direct:DIEDERIKSPC:LS_ReplyLocations</TargetAddress>
<ReplyTo>MP_LocationManager</ReplyTo>
<CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
<Priority>3</Priority>
<Timeout>600</Timeout>
<TargetHost>DIEDERIKSPC</TargetHost>
<TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2017-10-17T09:39:15Z</SentTime><Body Type="ByteRange" Offset="0" Length="1254"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019706092A864886F70D010702A082018830820184020101310B300906052B0E03021A0500300B06092A864886F70D010701318201633082015F020101303C3028311830160603550403130F57494E2D3532424F384A393031314D310C300A06035504031303534D53021067DEC56C7E5170A24D46DEBE4A962567300906052B0E03021A0500300D06092A864886F70D0101010500048201004AD7622A1DC0711902608B7CACD3B47F9E5EF7D464AEB04E128F74101056748E8C2BD5ED844C04CEE655D7CE24D0F7EFDD462B0B642C72E2B606CD8B37B402000D1B216039E0856D2A1F9B9F53B9839B3CE065EC476458C67F15433DEBFE528F062DB5BE9E2980002A614C6ED75B9AFF18DEB5365D72526D2201DB25A38AC0C9A7A64C7B3B44FB086519FABF98E7C9E348E98D4D62282FAABC9B3FF164CDAEE9B11927BAF1E5AB755D351B49312583CE7463FAB102BF88EB4ABF1BABC78F63005131F900ADC7264BBB7F861137A0C3FA3AA1D2095BBB38F8A70A6FD118B3B6C401A2F7E063D3C3B78DED76949AF36BDDC242851C620ABCC0F8298305398C42BA</Property><Property Name="AuthSenderMachine">WIN-52BO8J9011M;WIN-52BO8J9011M.poliforma.nl;</Property><Property Name="MPSiteCode">RSP</Property></Hook></Hooks><Payload Type="inline"/></Msg>']LOG]!><time="11:39:15.941-120" date="10-17-2017" component="ccmsetup" context="" type="0" thread="3064" file="httphelper.cpp:1724">
<![LOG[Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags=""><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="RSP" MasterSiteCode="RSP" SiteLocality="LOCAL" IISPreferedPort="" IISSSLPreferedPort=""/><LocationRecords/></Site></Sites><ClientPackage FullPackageID="RSP00001" FullPackageVersion="1" FullPackageHash="5EF3A189C48F3469440A83026EC8ECD36EAD6EAF3B5D35663F8201BDE175413C" MinimumClientVersion="5.00.7804.1000" RandomizeMaxDays="7" ProgramEnabled="false" LastModifiedTime="30621757;2748940928" SiteVersionMatch="true" SiteVersion="5.00.7804.1000" EnablePeerCache="true"/></ContentLocationReply>']LOG]!><time="11:39:15.941-120" date="10-17-2017" component="ccmsetup" context="" type="0" thread="3064" file="siteinfo.cpp:221">
<![LOG[Failed to get DP locations as the expected version from MP 'WIN-52BO8J9011M.poliforma.nl'. Error 0x87d00215]LOG]!><time="11:39:15.941-120" date="10-17-2017" component="ccmsetup" context="" type="2" thread="3064" file="ccmsetup.cpp:10926">
<![LOG[MP 'WIN-52BO8J9011M.poliforma.nl' didn't return DP locations for client package with the expected version. Retrying in 30 minutes.]LOG]!><time="11:39:15.941-120" date="10-17-2017" component="ccmsetup" context="" type="2" thread="3064" file="ccmsetup.cpp:10752">
<![LOG[Next retry in 30 minute(s)...]LOG]!><time="11:39:15.941-120" date="10-17-2017" component="ccmsetup" context="" type="0" thread="3064" file="ccmsetup.cpp:8498">

CCMSetup.exe 现在似乎没有停止。

我从 sccm 服务器重新安装了管理点角色，但这也不起作用。

编辑：

当我从\Win-52bo8j9011m\sms_rsp\Client（sccm 服务器）复制客户端安装文件并尝试安装 sccm-client 时，它只安装了 microsoft silverlight，并且在控制面板的配置管理器中没有任何变化：

在此处输入图像描述

在 sccm 中，对于 windows 7 VM，安装的客户端仍然不可用。

client.msi 日志文件的一部分：

[13:38:32] ERROR: Cannot find the IntallUtil.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe. Please install .NET Framework. Cannot find path C:\Windows\Microsoft.NET\Framework\v4.0.30319\
MSI (s) (88:44) [13:38:37:873]: Windows Installer reconfigured the product. Product Name: Configuration Manager Client. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.

所以我安装了 .NET Framework 并在 Windows 7 VM 上再次运行了 CCMSetup.exe。

在 ccmsetup.log 中再次出现相同的错误：

<![LOG[Failed to get assigned site from AD. Error 0x80004005]LOG]!><time="13:58:04.382-120" date="10-17-2017" component="ccmsetup" context="" type="2" thread="2968" file="ccmsetup.cpp:260">
<![LOG[GetADInstallParams failed with 0x80004005]LOG]!><time="13:58:04.382-120" date="10-17-2017" component="ccmsetup" context="" type="3" thread="2968" file="ccmsetup.cpp:300">

编辑2：

我以为我的 Windows 文件夹中缺少一个名为IComboObject.dll的 DLL 文件（https://www.youtube.com/watch?v=eIgqpQbTcb8）。

我下载了 DLL 文件并在我的 system32 文件夹中运行了一个命令：

regsvr32 MyComobject.dll

我收到一个找不到文件的错误，所以我搜索了更多内容并找到了这个视频。我在我的 system32 文件夹中输入了这个命令：

regsvr32 jscript.dll

之后，错误从我的 client.msi 和 ccmsetup.log 文件中消失了。

我仍然没有工作的 sccm-client。我看到我的 sccm-server 中的 windows 7 上没有安装任何客户端。

错误代码仍然是 0x80004005，但现在消息不同了。

ccmsetup.log 中的错误：

<![LOG[Failed to get assigned site from AD. Error 0x80004005]LOG]!><time="16:54:19.708-120" date="10-17-2017" component="ccmsetup" context="" type="2" thread="304" file="ccmsetup.cpp:260">
<![LOG[GetADInstallParams failed with 0x80004005]LOG]!><time="16:54:19.708-120" date="10-17-2017" component="ccmsetup" context="" type="3" thread="304" file="ccmsetup.cpp:300">
<![LOG[Couldn't find an MP source through AD. Error 0x80004005]LOG]!><time="16:54:19.708-120" date="10-17-2017" component="ccmsetup" context="" type="1" thread="304" file="ccmsetup.cpp:4643">

我在 client.msi 中看到的错误是：

[15:52:18] WARNING: Failed to delete setup in progress time-stamp with error 0x80070002
MSI (s) (A8:1C) [15:52:18:142]: Executing op: ActionStart(Name=SmsRemoteControlRepairConfig,Description=Repair may require to start Remote Control Service if Remote Control is enalbed.,)
[15:52:18] ERROR: Unable to enumerate files in {3DA228BE-34DA-49f4-A081-66465B077429} (0x80070003)
windows-7
Martin Hope
SPottuit
Asked: 2017-10-17 02:22:22 +0800 CST
  • 0

当使用我的 SQL 服务器 windows server 2012 R2 启动我的 VM 时，我收到以下错误： 在此处输入图像描述

如果我启动它或它自动启动，我的 SQL 服务器服务将不会运行。

到目前为止我做了什么：

  • Ran C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\sqlservr.exe，但错误日志中没有什么特别之处。

  • 试图在 SQL Server 配置管理器中启动服务。我什至无法打开应用程序。我收到一个错误： 在此处输入图像描述

    • 为了解决这个错误，我在 cmd 中运行了以下命令：

mofcomp "%programfiles(x86)%\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof"

描述 资源

描述

上面的错误是我尝试启动 SQL-server 服务时得到的。C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log中的日志文件并不那么有趣。除了带有红色文本的 SQL Server Profiler 日志： 在此处输入图像描述

我想知道接下来我能做什么。WMI 服务正在运行。

sql-server
Martin Hope
SPottuit
Asked: 2017-10-16 07:12:46 +0800 CST
  • 0

我今天启动了一台 Windows Server 2012 R2 虚拟机并收到以下警告：

警告：缺少 WMI ProgID 注册

起初我只在服务器管理器中看到一个模糊的错误：

在此处输入图像描述

运行 WMI 诊断实用程序后，我从发现警告的日志文件中获得了更多信息：

.1502 14:35:51 (0) ** Windows Server 2012 R2 - No Service Pack - 64-bit (9600) - User 'POLIFORMA\ADMINISTRATOR' on computer 'WIN-52BO8J9011M'.
.1503 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1504 14:35:51 (0) ** Environment: ........................................................................................................ OK.
.1505 14:35:51 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1506 14:35:51 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1507 14:35:51 (0) ** WMI repository state: ............................................................................................... N/A.
.1508 14:35:51 (0) ** AFTER running WMIDiag:
.1509 14:35:51 (0) ** The WMI repository has a size of: ................................................................................... 31 MB.
.1510 14:35:51 (0) ** - Disk free space on 'C:': .......................................................................................... 6692 MB.
.1511 14:35:51 (0) **   - INDEX.BTR,                     5365760 bytes,      10/15/2017 1:22:46 PM
.1512 14:35:51 (0) **   - MAPPING1.MAP,                  88520 bytes,        10/15/2017 1:03:40 PM
.1513 14:35:51 (0) **   - MAPPING2.MAP,                  88520 bytes,        10/15/2017 1:16:08 PM
.1514 14:35:51 (0) **   - OBJECTS.DATA,                  26607616 bytes,     10/15/2017 1:22:46 PM
.1515 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1516 14:35:51 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
.1517 14:35:51 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
.1518 14:35:51 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
.1519 14:35:51 (0) ** => This will prevent any WMI remote connectivity to this computer except
.1520 14:35:51 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
.1521 14:35:51 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
.1522 14:35:51 (0) **    - 'Windows Management Instrumentation (WMI-In)'
.1523 14:35:51 (0) **    - 'Windows Management Instrumentation (ASync-In)'
.1524 14:35:51 (0) **    Verify the reported status for each of these three inbound rules below.
.1525 14:35:51 (0) ** 
.1526 14:35:51 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' GROUP rule: ............................................. ENABLED.
.1527 14:35:51 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
.1528 14:35:51 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... ENABLED.
.1529 14:35:51 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
.1530 14:35:51 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
.1531 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1532 14:35:51 (0) ** DCOM Status: ........................................................................................................ OK.
.1533 14:35:51 (0) ** WMI registry setup: ................................................................................................. OK.
.1534 14:35:51 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
.1535 14:35:51 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
.1536 14:35:51 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1537 14:35:51 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1538 14:35:51 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1539 14:35:51 (0) **          this can prevent the service/application to work as expected.
.1540 14:35:51 (0) ** 
.1541 14:35:51 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1542 14:35:51 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1543 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1544 14:35:51 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1545 14:35:51 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1546 14:35:51 (2) !! WARNING: WMI ProgID registrations missing: .......................................................................... 7 ProgID(S)!
.1547 14:35:51 (0) ** - WBemscripting.SWBemlocator -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1548 14:35:51 (0) ** - WbemScripting.SWbemDateTime -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1549 14:35:51 (0) ** - WbemScripting.SWbemObjectPath -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1550 14:35:51 (0) ** - WbemScripting.SWbemSink -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1551 14:35:51 (0) ** - WbemScripting.SWbemLocator -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1552 14:35:51 (0) ** - WbemScripting.SWbemNamedValueSet -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1553 14:35:51 (0) ** - WbemScripting.SWbemRefresher -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1554 14:35:51 (0) ** => Missing WMI ProgID(s) could prevent WMI applications to run properly!
.1555 14:35:51 (0) **    To correct this problem, you must re-register the DLL(s) corresponding to the missing ProgID(s)
.1556 14:35:51 (0) **    with the following command:
.1557 14:35:51 (0) **    i.e. 'REGSVR32.EXE C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL'
.1558 14:35:51 (0) ** 
.1559 14:35:51 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1560 14:35:51 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1561 14:35:51 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1562 14:35:51 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1563 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1564 14:35:51 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.1565 14:35:51 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.1566 14:35:51 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
.1567 14:35:51 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.1568 14:35:51 (0) **         selecting 'Run as Administrator'.
.1569 14:35:51 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
.1570 14:35:51 (0) **         in the Task Scheduler within the right security context.
.1571 14:35:51 (0) ** 
.1572 14:35:51 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1573 14:35:51 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1574 14:35:51 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1575 14:35:51 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
.1576 14:35:51 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1577 14:35:51 (0) ** 
.1578 14:35:51 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1579 14:35:51 (0) ** Overall WMI security status: ........................................................................................ OK.
.1580 14:35:51 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1581 14:35:51 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1582 14:35:51 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1583 14:35:51 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1584 14:35:51 (0) ** - Root, 0x1A8 - Object required.
.1585 14:35:51 (0) ** 
.1586 14:35:51 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 20 ERROR(S)!
.1587 14:35:51 (0) ** - Root, 0x1A8 - Object required.
.1588 14:35:51 (0) ** - Root, 0x1A8 - Object required.
.1589 14:35:51 (0) ** - Root/subscription, 0x1A8 - Object required.
.1590 14:35:51 (0) ** - Root/DEFAULT, 0x1A8 - Object required.
.1591 14:35:51 (0) ** - Root/CIMV2, 0x1A8 - Object required.
.1592 14:35:51 (0) ** - Root/CIMV2/Security, 0x1A8 - Object required.
.1593 14:35:51 (0) ** - Root/CIMV2/TerminalServices, 0x1A8 - Object required.
.1594 14:35:51 (0) ** - Root/nap, 0x1A8 - Object required.
.1595 14:35:51 (0) ** - Root/SECURITY, 0x1A8 - Object required.
.1596 14:35:51 (0) ** - Root/STANDARDCIMV2, 0x1A8 - Object required.
.1597 14:35:51 (0) ** - Root/RSOP, 0x1A8 - Object required.
.1598 14:35:51 (0) ** - Root/RSOP/User, 0x1A8 - Object required.
.1599 14:35:51 (0) ** - Root/RSOP/Computer, 0x1A8 - Object required.
.1600 14:35:51 (0) ** - Root/WMI, 0x1A8 - Object required.
.1601 14:35:51 (0) ** - Root/directory, 0x1A8 - Object required.
.1602 14:35:51 (0) ** - Root/directory/LDAP, 0x1A8 - Object required.
.1603 14:35:51 (0) ** - Root/Policy, 0x1A8 - Object required.
.1604 14:35:51 (0) ** - Root/Microsoft, 0x1A8 - Object required.
.1605 14:35:51 (0) ** - Root/Microsoft/HomeNet, 0x1A8 - Object required.
.1606 14:35:51 (0) ** - Root/aspnet, 0x1A8 - Object required.
.1607 14:35:51 (0) ** 
.1608 14:35:51 (0) ** WMI GET operations: ................................................................................................. OK.
.1609 14:35:51 (0) ** WMI MOF representations: ............................................................................................ OK.
.1610 14:35:51 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1611 14:35:51 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1612 14:35:51 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1613 14:35:51 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1614 14:35:51 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1615 14:35:51 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1616 14:35:51 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1617 14:35:51 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1618 14:35:51 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1619 14:35:51 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1620 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1621 14:35:51 (0) ** 
.1622 14:35:51 (0) ** 21 error(s) 0x1A8 - (WBEM_UNKNOWN) This error code is external to WMI.
.1623 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1624 14:35:51 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1625 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1626 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1627 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1628 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1629 14:35:51 (0) ** 
.1630 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1631 14:35:51 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1632 14:35:51 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1633 14:35:51 (0) ** 
.1634 14:35:51 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\ADMINISTRATOR\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_2K12R2.SRV.RTM.64_WIN-52BO8J9011M_2017.10.15_14.35.50.LOG' for details.
.1635 14:35:51 (0) ** 
.1636 14:35:51 (0) ** WMIDiag v2.2 ended on Sunday, October 15, 2017 at 14:35 (W:24 E:26 S:1).

到目前为止我做了什么：

  • 在日志文件中执行建议的命令：REGSVR32.EXE C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
  • 我尝试恢复所有 .mof 文件（可能它们已损坏）。我无法让建议的命令起作用。
  • 在 windows 文件夹中重新注册我的 DLL：Dir *.dll /s /b > c:re-regdll.bat
  • 使用来自tweaking.com 的Windows 修复应用程序来修复WMI。
virtualization