Jump to content


  • 0
xstatic411

SCCM Client Center - The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Asked by xstatic411

Question

xstatic411 Newbie

xstatic411

Posted
Posted

I appear to be going in circles trying to troubleshoot a connectivity issue with SCCM Client Center.

 

I am getting "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)" when trying to connect to another XP workstation (Hostname: SW755) on my network. I am able to remote into SW755 and run Client Center with no issues. I am a bit stumped.

 

No Firewall Service is running.

RPC Service is running.

Workstation is receiving correct advertisements from SCCM 2007.

WMI appears to be intact and Security verified against a known good machine.

 

Workstation in question is running XP SP3

 

I am positive I am leaving out some details. Feel free to ask and I will answer the best I can.


Thanks in advance for the assistance.

Share this post

Link to post
Share on other sites

8 answers to this question

Recommended Posts

  • 0
xstatic411 Newbie

xstatic411

Posted
Posted

Here is the WMIDiag Log

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

 

43892 10:13:28 (0) ** WMIDiag v2.1 started on Thursday, January 17, 2013 at 10:01.
43893 10:13:28 (0) **
43894 10:13:28 (0) ** Copyright © Microsoft Corporation. All rights reserved - July 2007.
43895 10:13:28 (0) **
43896 10:13:28 (0) ** This script is not supported under any Microsoft standard support program or service.
43897 10:13:28 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
43898 10:13:28 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
43899 10:13:28 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
43900 10:13:28 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
43901 10:13:28 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
43902 10:13:28 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
43903 10:13:28 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
43904 10:13:28 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
43905 10:13:28 (0) ** of the possibility of such damages.
43906 10:13:28 (0) **
43907 10:13:28 (0) **
43908 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43909 10:13:28 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
43910 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43911 10:13:28 (0) **
43912 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43913 10:13:28 (0) ** Windows XP - Service pack 3 - 32-bit (2600) - User 'SWNTDOMAIN\CBURGMAN' on computer 'SW755'.
43914 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43915 10:13:28 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
43916 10:13:28 (0) ** INFO: => 1 possible incorrect shutdown(s) detected on:
43917 10:13:28 (0) ** - Shutdown on 26 December 2012 07:58:24 (GMT+6).
43918 10:13:28 (0) **
43919 10:13:28 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
43920 10:13:28 (0) ** Drive type: ......................................................................................................... IDE (ST380815AS).
43921 10:13:28 (0) ** There are no missing WMI system files: .............................................................................. OK.
43922 10:13:28 (0) ** There are no missing WMI repository files: .......................................................................... OK.
43923 10:13:28 (0) ** WMI repository state: ............................................................................................... NOT TESTED.
43924 10:13:28 (0) ** AFTER running WMIDiag:
43925 10:13:28 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
43926 10:13:28 (0) ** - Disk free space on 'C:': .......................................................................................... 41171 MB.
43927 10:13:28 (0) ** - INDEX.BTR, 5234688 bytes, 01/17/2013 10:12:59
43928 10:13:28 (0) ** - INDEX.MAP, 3060 bytes, 01/17/2013 10:12:59
43929 10:13:28 (0) ** - MAPPING.VER, 4 bytes, 01/17/2013 10:13:00
43930 10:13:28 (0) ** - MAPPING1.MAP, 15128 bytes, 01/17/2013 10:12:29
43931 10:13:28 (0) ** - MAPPING2.MAP, 15128 bytes, 01/17/2013 10:13:00
43932 10:13:28 (0) ** - OBJECTS.DATA, 22126592 bytes, 01/17/2013 10:12:59
43933 10:13:28 (0) ** - OBJECTS.MAP, 12068 bytes, 01/17/2013 10:13:00
43934 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43935 10:13:28 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
43936 10:13:28 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
43937 10:13:28 (0) ** Windows Firewall 'RemoteAdmin' status: .............................................................................. DISABLED.
43938 10:13:28 (0) ** => This will prevent any WMI remote connectivity to this machine.
43939 10:13:28 (0) ** - You can adjust the configuration by executing the following command:
43940 10:13:28 (0) ** i.e. 'NETSH.EXE FIREWALL SET SERVICE REMOTEADMIN ENABLE SUBNET'
43941 10:13:28 (0) **
43942 10:13:28 (0) ** Windows Firewall application exception for 'UNSECAPP.EXE': .......................................................... MISSING.
43943 10:13:28 (0) ** => This will prevent any script and MMC application asynchronous callbacks to this machine.
43944 10:13:28 (0) ** - You can adjust the configuration by executing the following command:
43945 10:13:28 (0) ** i.e. 'NETSH.EXE FIREWALL SET ALLOWEDPROGRAM C:\WINDOWS\SYSTEM32\WBEM\UNSECAPP.EXE WMICALLBACKS ENABLE'
43946 10:13:28 (0) **
43947 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43948 10:13:28 (0) ** DCOM Status: ........................................................................................................ OK.
43949 10:13:28 (0) ** WMI registry setup: ................................................................................................. OK.
43950 10:13:28 (0) ** INFO: WMI service has dependents: ................................................................................... 3 SERVICE(S)!
43951 10:13:28 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
43952 10:13:28 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Automatic')
43953 10:13:28 (0) ** - SMS Agent Host (CCMEXEC, StartMode='Automatic')
43954 10:13:28 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
43955 10:13:28 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
43956 10:13:28 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
43957 10:13:28 (0) ** this can prevent the service/application to work as expected.
43958 10:13:28 (0) **
43959 10:13:28 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
43960 10:13:28 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
43961 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43962 10:13:28 (0) ** WMI service DCOM setup: ............................................................................................. OK.
43963 10:13:28 (0) ** WMI components DCOM registrations: .................................................................................. OK.
43964 10:13:28 (0) ** WMI ProgID registrations: ........................................................................................... OK.
43965 10:13:28 (2) !! WARNING: WMI provider DCOM registrations missing for the following provider(s): ..................................... 1 WARNING(S)!
43966 10:13:28 (0) ** - ROOT/MSAPPS11, OffProv11 ({F7107F37-C761-4748-B686-055F45889DCD}) (i.e. WMI Class 'Win32_ExcelComAddins')
43967 10:13:28 (0) ** Provider DLL: ''
43968 10:13:28 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
43969 10:13:28 (0) ** while the DCOM registration is wrong or missing. This can be due to:
43970 10:13:28 (0) ** - a de-installation of the software.
43971 10:13:28 (0) ** - a deletion of some registry key data.
43972 10:13:28 (0) ** - a registry corruption.
43973 10:13:28 (0) ** => You can correct the DCOM configuration by:
43974 10:13:28 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>' command.
43975 10:13:28 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
43976 10:13:28 (0) ** (This list can be built on a similar and working WMI Windows installation)
43977 10:13:28 (0) ** The following command line must be used:
43978 10:13:28 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
43979 10:13:28 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
43980 10:13:28 (0) ** may not solve the problem as the DLL supporting the WMI class(es)
43981 10:13:28 (0) ** can be located in a different folder.
43982 10:13:28 (0) ** You must refer to the class name to determine the software delivering the related DLL.
43983 10:13:28 (0) ** => If the software has been de-installed intentionally, then this information must be
43984 10:13:28 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
43985 10:13:28 (0) ** the provider registration data.
43986 10:13:28 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MSAPPS11 path __Win32Provider Where Name='OffProv11' DELETE'
43987 10:13:28 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
43988 10:13:28 (0) ** the namespace and ALL its content can be ENTIRELY deleted.
43989 10:13:28 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='MSAPPS11' DELETE'
43990 10:13:28 (0) ** - Re-installing the software.
43991 10:13:28 (0) **
43992 10:13:28 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
43993 10:13:28 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
43994 10:13:28 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
43995 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
43996 10:13:28 (0) ** Overall DCOM security status: ....................................................................................... OK.
43997 10:13:28 (0) ** Overall WMI security status: ........................................................................................ OK.
43998 10:13:28 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
43999 10:13:28 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 6.
44000 10:13:28 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
44001 10:13:28 (0) ** 'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_Config"'
44002 10:13:28 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
44003 10:13:28 (0) ** 'SELECT * FROM __NamespaceCreationEvent'
44004 10:13:28 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
44005 10:13:28 (0) ** 'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy"'
44006 10:13:28 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
44007 10:13:28 (0) ** 'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_EmbeddedObject"'
44008 10:13:28 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
44009 10:13:28 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
44010 10:13:28 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
44011 10:13:28 (0) ** 'select * from MSFT_SCMEventLogEvent'
44012 10:13:28 (0) **
44013 10:13:28 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
44014 10:13:28 (0) ** INFO: WMI ADAP status: .............................................................................................. 1.
44015 10:13:28 (0) ** => The WMI ADAP process is currently running (1).
44016 10:13:28 (0) ** Some WMI performance classes could be missing at the time WMIDiag was executed.
44017 10:13:28 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
44018 10:13:28 (0) ** - ROOT/SERVICEMODEL.
44019 10:13:28 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
44020 10:13:28 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
44021 10:13:28 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
44022 10:13:28 (0) ** i.e. 'WMIC.EXE /NODE:"SW755" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
44023 10:13:28 (0) **
44024 10:13:28 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
44025 10:13:28 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
44026 10:13:28 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 2 ERROR(S)!
44027 10:13:28 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
44028 10:13:28 (0) ** MOF Registration: ''
44029 10:13:28 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
44030 10:13:28 (0) ** MOF Registration: ''
44031 10:13:28 (0) **
44032 10:13:28 (0) ** WMI MOF representations: ............................................................................................ OK.
44033 10:13:28 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
44034 10:13:28 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
44035 10:13:28 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 2 WARNING(S)!
44036 10:13:28 (0) ** - Root/CIMv2, 'SELECT * FROM Win32_PointingDevice WHERE Status = "OK"' did not return any instance while AT LEAST 1 instance is expected.
44037 10:13:28 (0) ** - Root/CIMv2, 'SELECT * FROM Win32_Keyboard' did not return any instance while AT LEAST 1 instance is expected.
44038 10:13:28 (0) **
44039 10:13:28 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
44040 10:13:28 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
44041 10:13:28 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
44042 10:13:28 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
44043 10:13:28 (0) ** WMI static instances retrieved: ..................................................................................... 6748.
44044 10:13:28 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
44045 10:13:28 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 2.
44046 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44047 10:13:28 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
44048 10:13:28 (0) ** DCOM: ............................................................................................................. 36.
44049 10:13:28 (0) ** WINMGMT: .......................................................................................................... 112.
44050 10:13:28 (0) ** WMIADAPTER: ....................................................................................................... 0.
44051 10:13:28 (0) ** => Verify the WMIDiag LOG at line #42758 for more details.
44052 10:13:28 (0) **
44053 10:13:28 (0) ** # of additional Event Log events AFTER WMIDiag execution:
44054 10:13:28 (0) ** DCOM: ............................................................................................................. 0.
44055 10:13:28 (0) ** WINMGMT: .......................................................................................................... 0.
44056 10:13:28 (0) ** WMIADAPTER: ....................................................................................................... 0.
44057 10:13:28 (0) **
44058 10:13:28 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
44059 10:13:28 (0) ** => This error is typically a WMI error. This WMI error is due to:
44060 10:13:28 (0) ** - a missing WMI class definition or object.
44061 10:13:28 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
44062 10:13:28 (0) ** You can correct the missing class definitions by:
44063 10:13:28 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
44064 10:13:28 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
44065 10:13:28 (0) ** (This list can be built on a similar and working WMI Windows installation)
44066 10:13:28 (0) ** The following command line must be used:
44067 10:13:28 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
44068 10:13:28 (0) ** - a WMI repository corruption.
44069 10:13:28 (0) ** Under Windows XP SP2 and SP3, you can validate the repository consistency
44070 10:13:28 (0) ** by executing the following command:
44071 10:13:28 (0) ** i.e. 'WMIDiag CheckConsistency'
44072 10:13:28 (0) ** Note: Under Windows XP SP2 and SP3, when the repository is checked and detected INCONSISTENT,
44073 10:13:28 (0) ** a new repository is automatically re-created based on Auto-Recovery mechanism.
44074 10:13:28 (0) ** Note that some information can be lost during this process (i.e. static data, CIM registration).
44075 10:13:28 (0) ** However, the original repository is located at 'C:\WINDOWS\SYSTEM32\WBEM\Repository.001'.
44076 10:13:28 (0) ** The computer must be rebooted for the system to work with the re-created repository.
44077 10:13:28 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
44078 10:13:28 (0) ** otherwise some applications may fail after the reconstruction.
44079 10:13:28 (0) ** This can be achieved with the following command:
44080 10:13:28 (0) ** i.e. 'WMIDiag ShowMOFErrors'
44081 10:13:28 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
44082 10:13:28 (0) ** ALL fixes previously mentioned.
44083 10:13:28 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
44084 10:13:28 (0) **
44085 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44086 10:13:28 (0) ** WMI Registry key setup: ............................................................................................. OK.
44087 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44088 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44089 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44090 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44091 10:13:28 (0) **
44092 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44093 10:13:28 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
44094 10:13:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
44095 10:13:28 (0) **
44096 10:13:28 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\TEMP\WMIDIAG-V2.1_XP___.CLI.SP3.32_SW755_2013.01.17_10.01.00.LOG' for details.
44097 10:13:28 (0) **
44098 10:13:28 (0) ** WMIDiag v2.1 ended on Thursday, January 17, 2013 at 10:13 (W:205 E:127 S:1).

Share this post

Link to post
Share on other sites
  • 0
xstatic411 Newbie

xstatic411

Posted
Posted

Looks like to problem was identified. Checked my DCOM configuration on the problem workstation against a known good one. Found a missing DCOM Protocol for TCP/IP. Added the protocol, verified the securities were identical for DCOM and WMI. Once the workstation was rebooted, I was able to connect via SCCM Client Center.

  • Like 1

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
Go to question listing
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.