WMI error RPC_E_CALL_CANCELED

mschoene · ‎02-11-2009

A lot of our clients could not be inventoried because of the following error:

Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED)) BRGRSXXXX (BRGRSXXXX)

Connection tester shows the following:

Ping test OK
-----------------------------------------------
Remote registry test OK
-----------------------------------------------
Remote WMI access test FAILED
Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
-----------------------------------------------
Remote \\BRGRSXXXX\c$ access test OK

WMI check according to LS Knowledgebase is o.k.

The WMIDiag.vbs brings this errors up:

22089 12:44:48 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
22090 12:44:48 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
22091 12:44:48 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
22092 12:44:48 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
22093 12:44:48 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
22094 12:44:48 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
22095 12:44:48 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
22096 12:44:48 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
22097 12:44:48 (0) ** fail depending on the operation requested.
22098 12:44:48 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command

Regsvr32 with both DLLs succeded but the inventory still dosn't work!

The Errorlog.txt shows no relevant entries according to the machine BRGRSXXXX.

Any help or suggestions?

mschoene · ‎02-16-2009

After endless tests I can say yes. I was on the false track because I stopped the fw services long ago at the beginning! Thinking the matter over at least I disbaled the vpn layer from the network device and this stopped producing this "wmi error". And the funniest thing is that not even the vpn specialist knows this behavior of the fw software because they didn't create this rule. It seems to be "default".
O.K. Geert, you were right with your guess! Thanks a lot!

Hemoco · ‎02-16-2009

If you disable this firewall everything works?

mschoene · ‎02-16-2009

Yes, they all have XP installed.
It seems to be a problem with the Non-MS-Firewall we use in our company. It's silly because inside our VPN no rule drop any packets. But in the FW Log I can see that the client first accepts a packet/connection on port 135 but after that the rest of the communication is rejected.

Hemoco · ‎02-13-2009

The remote connection tester does this, but there you got:

Remote WMI access test FAILED
Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))

Your clients affected by this problem do they all have the same operating system?

mschoene · ‎02-13-2009

I'm not sure if the local WMI installation is the problem since I see for this computers the following system event error:

DCOM was unable to communicate with the computer PC0815 using any of the configured protocols.

Do you know a test program which can simulate the remote DCOM or WMI access??

Hemoco · ‎02-12-2009

From what can be found on microsoft support:

If the error is not related to WMI not correctly installed it's most likely:

-Some sort of firewall blocking access (If xp try :net stop "Windows Firewall/Internet Connection Sharing (ICS)" as a test)
-Network problems to the client.

mschoene · ‎02-12-2009

O.K. WMI reinstall done according to the manual http://windowsxp.mvps.org/repairwmi.htm.

1. Re-registering all the DLLs and EXEs dosn't change anything.

2. Re-Building WMI: napclientschema.mof was missing during installation; I found this file and copied it to the installdir--> LS inventory dosn't work.

After that I took again a nearer look at the wmidiag-Log and saw that some Groups were missing:

WMI namespace security for 'ROOT/RSOP': ............................................................................. MODIFIED.
18828 11:45:34 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
18829 11:45:34 (0) ** - REMOVED ACE:
18830 11:45:34 (0) ** ACEType: &h0
18831 11:45:34 (0) ** ACCESS_ALLOWED_ACE_TYPE
18832 11:45:34 (0) ** ACEFlags: &h12
18833 11:45:34 (0) ** CONTAINER_INHERIT_ACE
18834 11:45:34 (0) ** INHERITED_ACE
18835 11:45:34 (0) ** ACEMask: &h6003F
18836 11:45:34 (0) ** WBEM_ENABLE
18837 11:45:34 (0) ** WBEM_METHOD_EXECUTE
18838 11:45:34 (0) ** WBEM_FULL_WRITE_REP
18839 11:45:34 (0) ** WBEM_PARTIAL_WRITE_REP
18840 11:45:34 (0) ** WBEM_WRITE_PROVIDER
18841 11:45:34 (0) ** WBEM_REMOTE_ACCESS
18842 11:45:34 (0) ** WBEM_WRITE_DAC
18843 11:45:34 (0) ** WBEM_READ_CONTROL
18844 11:45:34 (0) **
18845 11:45:34 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
18846 11:45:34 (0) ** Removing default security will cause some operations to fail!
18847 11:45:34 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
18848 11:45:34 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
18849 11:45:34 (0) **
18850 11:45:34 (0) ** WMI namespace security for 'ROOT/RSOP': ............................................................................. MODIFIED.
18851 11:45:34 (1) !! ERROR: Default trustee 'NT AUTHORITY\AUTHENTICATED USERS' has been REMOVED!
18852 11:45:34 (0) ** - REMOVED ACE:
18853 11:45:34 (0) ** ACEType: &h0
18854 11:45:34 (0) ** ACCESS_ALLOWED_ACE_TYPE
18855 11:45:34 (0) ** ACEFlags: &h12
18856 11:45:34 (0) ** CONTAINER_INHERIT_ACE
18857 11:45:34 (0) ** INHERITED_ACE
18858 11:45:34 (0) ** ACEMask: &h20023
18859 11:45:34 (0) ** WBEM_ENABLE
18860 11:45:34 (0) ** WBEM_METHOD_EXECUTE
18861 11:45:34 (0) ** WBEM_REMOTE_ACCESS
18862 11:45:34 (0) ** WBEM_READ_CONTROL
18863 11:45:34 (0) **
18864 11:45:34 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
18865 11:45:34 (0) ** Removing default security will cause some operations to fail!
18866 11:45:34 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
18867 11:45:34 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
18868 11:45:34 (0) **
18869 11:45:34 (0) ** WMI namespace security for 'ROOT/RSOP/USER': ........................................................................ MODIFIED.
18870 11:45:34 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
18871 11:45:34 (0) ** - REMOVED ACE:
18872 11:45:34 (0) ** ACEType: &h0
18873 11:45:34 (0) ** ACCESS_ALLOWED_ACE_TYPE
18874 11:45:34 (0) ** ACEFlags: &h12
18875 11:45:34 (0) ** CONTAINER_INHERIT_ACE
18876 11:45:34 (0) ** INHERITED_ACE
18877 11:45:34 (0) ** ACEMask: &h6003F
18878 11:45:34 (0) ** WBEM_ENABLE
18879 11:45:34 (0) ** WBEM_METHOD_EXECUTE
18880 11:45:34 (0) ** WBEM_FULL_WRITE_REP
18881 11:45:34 (0) ** WBEM_PARTIAL_WRITE_REP
18882 11:45:34 (0) ** WBEM_WRITE_PROVIDER
18883 11:45:34 (0) ** WBEM_REMOTE_ACCESS
18884 11:45:34 (0) ** WBEM_WRITE_DAC
18885 11:45:34 (0) ** WBEM_READ_CONTROL
18886 11:45:34 (0) **
18887 11:45:34 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
18888 11:45:34 (0) ** Removing default security will cause some operations to fail!
18889 11:45:34 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
18890 11:45:34 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
18891 11:45:34 (0) **
18892 11:45:34 (0) ** WMI namespace security for 'ROOT/RSOP/USER': ........................................................................ MODIFIED.
18893 11:45:34 (1) !! ERROR: Default trustee 'NT AUTHORITY\AUTHENTICATED USERS' has been REMOVED!
18894 11:45:34 (0) ** - REMOVED ACE:
18895 11:45:34 (0) ** ACEType: &h0
18896 11:45:34 (0) ** ACCESS_ALLOWED_ACE_TYPE
18897 11:45:34 (0) ** ACEFlags: &h12
18898 11:45:34 (0) ** CONTAINER_INHERIT_ACE
18899 11:45:34 (0) ** INHERITED_ACE
18900 11:45:34 (0) ** ACEMask: &h20023
18901 11:45:34 (0) ** WBEM_ENABLE
18902 11:45:34 (0) ** WBEM_METHOD_EXECUTE
18903 11:45:34 (0) ** WBEM_REMOTE_ACCESS
18904 11:45:34 (0) ** WBEM_READ_CONTROL
18905 11:45:34 (0) **
18906 11:45:34 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
18907 11:45:34 (0) ** Removing default security will cause some operations to fail!
18908 11:45:34 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
18909 11:45:34 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
18910 11:45:34 (0) **
18911 11:45:34 (0) ** WMI namespace security for 'ROOT/RSOP/COMPUTER': .................................................................... MODIFIED.
18912 11:45:34 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
18913 11:45:34 (0) ** - REMOVED ACE:
18914 11:45:34 (0) ** ACEType: &h0
18915 11:45:34 (0) ** ACCESS_ALLOWED_ACE_TYPE
18916 11:45:34 (0) ** ACEFlags: &h12
18917 11:45:34 (0) ** CONTAINER_INHERIT_ACE
18918 11:45:34 (0) ** INHERITED_ACE
18919 11:45:34 (0) ** ACEMask: &h6003F
18920 11:45:34 (0) ** WBEM_ENABLE
18921 11:45:34 (0) ** WBEM_METHOD_EXECUTE
18922 11:45:34 (0) ** WBEM_FULL_WRITE_REP
18923 11:45:34 (0) ** WBEM_PARTIAL_WRITE_REP
18924 11:45:34 (0) ** WBEM_WRITE_PROVIDER
18925 11:45:34 (0) ** WBEM_REMOTE_ACCESS
18926 11:45:34 (0) ** WBEM_WRITE_DAC
18927 11:45:34 (0) ** WBEM_READ_CONTROL
18928 11:45:34 (0) **
18929 11:45:34 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
18930 11:45:34 (0) ** Removing default security will cause some operations to fail!
18931 11:45:34 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
18932 11:45:34 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
18933 11:45:34 (0) **
18934 11:45:34 (0) ** WMI namespace security for 'ROOT/RSOP/COMPUTER': .................................................................... MODIFIED.
18935 11:45:34 (1) !! ERROR: Default trustee 'NT AUTHORITY\AUTHENTICATED USERS' has been REMOVED!
18936 11:45:34 (0) ** - REMOVED ACE:
18937 11:45:34 (0) ** ACEType: &h0
18938 11:45:34 (0) ** ACCESS_ALLOWED_ACE_TYPE
18939 11:45:34 (0) ** ACEFlags: &h12
18940 11:45:34 (0) ** CONTAINER_INHERIT_ACE
18941 11:45:34 (0) ** INHERITED_ACE
18942 11:45:34 (0) ** ACEMask: &h20023
18943 11:45:34 (0) ** WBEM_ENABLE
18944 11:45:34 (0) ** WBEM_METHOD_EXECUTE
18945 11:45:34 (0) ** WBEM_REMOTE_ACCESS
18946 11:45:34 (0) ** WBEM_READ_CONTROL
18947 11:45:34 (0) **
18948 11:45:34 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
18949 11:45:34 (0) ** Removing default security will cause some operations to fail!
18950 11:45:34 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
18951 11:45:34 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
18952 11:45:34 (0) **

#########################################################

I added the groups and gave the rights to them but the inventory STILL DOSN'T work

which means that no WMI information (hardware or software) can be seen!

The following wmidiag-Log I got after all this steps:

########################################################

18662 12:12:44 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
18663 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18664 12:12:44 (0) **
18665 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18666 12:12:44 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'DOM\User123' on computer 'PC0815'.
18667 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18668 12:12:44 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
18669 12:12:44 (0) ** INFO: => 1 incorrect shutdown(s) detected on:
18670 12:12:44 (0) ** - Shutdown on 11 February 2009 14:34:50 (GMT+1).
18671 12:12:44 (0) **
18672 12:12:44 (0) ** System drive: ....................................................................................................... C: (Datenträger Nr. 0 Partition Nr. 0).
18673 12:12:44 (0) ** Drive type: ......................................................................................................... IDE (ST96023AS).
18674 12:12:44 (0) ** INFO: The following UNEXPECTED binary files are/is found in the WBEM folder: ........................................ 1 FILE(S)!
18675 12:12:44 (0) ** - NIWMIPROV.DLL, 114688 bytes, 06.09.2007 14:09:21
18676 12:12:44 (0) ** => This list is provided for information. Unexpected binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
18677 12:12:44 (0) ** do not necessarily represent an error. For instance, the file(s) listed can be added by
18678 12:12:44 (0) ** any applications implementing WMI providers.
18679 12:12:44 (0) ** => NO ACTION is required.
18680 12:12:44 (0) **
18681 12:12:44 (0) ** There are no missing WMI system files: .............................................................................. OK.
18682 12:12:44 (0) ** There are no missing WMI repository files: .......................................................................... OK.
18683 12:12:44 (0) ** WMI repository state: ............................................................................................... N/A.
18684 12:12:44 (0) ** BEFORE running WMIDiag:
18685 12:12:44 (0) ** The WMI repository has a size of: ................................................................................... 24 MB.
18686 12:12:44 (0) ** - Disk free space on 'C:': .......................................................................................... 28740 MB.
18687 12:12:44 (0) ** - INDEX.BTR, 1581056 bytes, 12.02.2009 12:08:37
18688 12:12:44 (0) ** - INDEX.MAP, 796 bytes, 12.02.2009 12:08:37
18689 12:12:44 (0) ** - OBJECTS.DATA, 24010752 bytes, 12.02.2009 12:08:37
18690 12:12:44 (0) ** - OBJECTS.MAP, 11748 bytes, 12.02.2009 12:08:37
18691 12:12:44 (0) ** AFTER running WMIDiag:
18692 12:12:44 (0) ** The WMI repository has a size of: ................................................................................... 24 MB.
18693 12:12:44 (0) ** - Disk free space on 'C:': .......................................................................................... 28739 MB.
18694 12:12:44 (0) ** - INDEX.BTR, 1581056 bytes, 12.02.2009 12:09:37
18695 12:12:44 (0) ** - INDEX.MAP, 796 bytes, 12.02.2009 12:09:37
18696 12:12:44 (0) ** - OBJECTS.DATA, 24010752 bytes, 12.02.2009 12:09:37
18697 12:12:44 (0) ** - OBJECTS.MAP, 11748 bytes, 12.02.2009 12:09:37
18698 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18699 12:12:44 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
18700 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18701 12:12:44 (0) ** DCOM Status: ........................................................................................................ OK.
18702 12:12:44 (0) ** WMI registry setup: ................................................................................................. OK.
18703 12:12:44 (0) ** WMI Service has no dependents: ...................................................................................... OK.
18704 12:12:44 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
18705 12:12:44 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
18706 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18707 12:12:44 (0) ** WMI service DCOM setup: ............................................................................................. OK.
18708 12:12:44 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
18709 12:12:44 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
18710 12:12:44 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
18711 12:12:44 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
18712 12:12:44 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
18713 12:12:44 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
18714 12:12:44 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
18715 12:12:44 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
18716 12:12:44 (0) ** fail depending on the operation requested.
18717 12:12:44 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
18718 12:12:44 (0) **
18719 12:12:44 (0) ** WMI ProgID registrations: ........................................................................................... OK.
18720 12:12:44 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
18721 12:12:44 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
18722 12:12:44 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
18723 12:12:44 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
18724 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18725 12:12:44 (0) ** Overall DCOM security status: ....................................................................................... OK.
18726 12:12:44 (0) ** Overall WMI security status: ........................................................................................ OK.
18727 12:12:44 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
18728 12:12:44 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
18729 12:12:44 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
18730 12:12:44 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
18731 12:12:44 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
18732 12:12:44 (0) ** 'select * from MSFT_SCMEventLogEvent'
18733 12:12:44 (0) **
18734 12:12:44 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
18735 12:12:44 (0) ** WMI ADAP status: .................................................................................................... OK.
18736 12:12:44 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
18737 12:12:44 (0) ** - ROOT/SERVICEMODEL.
18738 12:12:44 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
18739 12:12:44 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
18740 12:12:44 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
18741 12:12:44 (0) ** i.e. 'WMIC.EXE /NODE:"PC0815" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
18742 12:12:44 (0) **
18743 12:12:44 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
18744 12:12:44 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
18745 12:12:44 (0) ** WMI GET operations: ................................................................................................. OK.
18746 12:12:44 (0) ** WMI MOF representations: ............................................................................................ OK.
18747 12:12:44 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
18748 12:12:44 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
18749 12:12:44 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
18750 12:12:44 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
18751 12:12:44 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
18752 12:12:44 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
18753 12:12:44 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
18754 12:12:44 (0) ** WMI static instances retrieved: ..................................................................................... 731.
18755 12:12:44 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
18756 12:12:44 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
18757 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18758 12:12:44 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
18759 12:12:44 (0) ** DCOM: ............................................................................................................. 1.
18760 12:12:44 (0) ** WINMGMT: .......................................................................................................... 78.
18761 12:12:44 (0) ** WMIADAPTER: ....................................................................................................... 0.
18762 12:12:44 (0) ** => Verify the WMIDiag LOG at line #17965 for more details.
18763 12:12:44 (0) **
18764 12:12:44 (0) ** # of additional Event Log events AFTER WMIDiag execution:
18765 12:12:44 (0) ** DCOM: ............................................................................................................. 0.
18766 12:12:44 (0) ** WINMGMT: .......................................................................................................... 0.
18767 12:12:44 (0) ** WMIADAPTER: ....................................................................................................... 0.
18768 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18769 12:12:44 (0) ** WMI Registry key setup: ............................................................................................. OK.
18770 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18771 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18772 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18773 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18774 12:12:44 (0) **
18775 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18776 12:12:44 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
18777 12:12:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
18778 12:12:44 (0) **
18779 12:12:44 (0) ** WARNING: WMIDiag determined that WMI works CORRECTLY. HOWEVER, some issues were detected. Check 'C:\DOKUMENTE UND EINSTELLUNGEN\User0815\LOKALE EINSTELLUNGEN\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_PC0815_2009.02.12_12.09.00.LOG' for details.
18780 12:12:44 (0) **
18781 12:12:44 (0) ** WMIDiag v2.0 ended on Donnerstag, 12. Februar 2009 at 12:12 (W:63 E:12 S:2)

Hemoco · ‎02-11-2009

First try to reinstall WMI : http://windowsxp.mvps.org/repairwmi.htm
Try if you have the same error afterwards.

Does your clients get this for all scan sections?

mschoene · ‎02-11-2009

Perhaps I should mention that there is no difference with the WMI error if I use active scan, lstrigger oder lsclient.exe!

Archive

New to Lansweeper?

Try Lansweeper For Free