Learn how to fix ConfigMgr DP Issue RPC server is Unavailable Error Code 0x800706ba. I have seen issues like SCCM package distribution is not working for a particular remote DP. When you see the issue is for all the packages, then this is something with network connectivity and Distribution point configuration.
0x800706ba – RPC server is unavailable
The meaning of error code 0x800706ba is RPC server is unavailable. RPC is one of the core components of Windows. SCCM uses that component in many scenarios.
In the context of ConfigMgr, an RPC server unavailable error might occur when the site server tries to connect to remote DP’s Windows Management Instrumentation (WMI). There could be several reasons for the error code 0x800706ba. More details available in the following sections.
You need to check event logs (Applications/Systems) on the remote DP server to understand whether there is something wrong with the WMI repository or not. There could be health issues with WMI and that could also cause similar issues with SCCM package distribution.
I have seen the scenarios like security hardening policies impact the connectivity to remote DP. This could also cause issues with package distribution. Event logs might give you some hints about the new security policies implemented on remote distribution points.
The other important point that you have to check for RPC-related issues is firewall ports. Well, this is not necessarily mean that the firewall application installed on your remote DP or primary server. Rather it’s more to do with firewall appliance from the network team. There might be many firewall devices in between two data centers where remote DP and primary server are located.
|Site Server||DP||135||445/135/All the ports between 49152 to 65535||RPC EPM/RPC Dynamic/SMB||Unidirection|
Test the following port communication to confirm that there is no connectivity issues. Run the following commands from primary/secondary site server.
- You can use port query(portqry.exe) to test the connectivity between the site server and remote distribution point.
- portqry -n REMOTE_DP’s_IP -p TCP –o 445,135 -l TCP445portqry.log
- portqry -n REMOTE_DP’s_IP -p UDP –e 135 -l UDP135portqry.log
- portqry -n REMOTE_DP’s_IP -p TCP –r 49152:65535 -l Dynamicportqry.log
WMI Connectivity Test
Let’s check whether you are able to connect to remote DP’s WMI or not. You can try connecting to remote DP’s WMI using the WBEMTest tool available in Windows. There are a couple of considerations here. You can use either an admin user account or system account to connect to remote WMI or
- You can try connecting to remote WMI using the site server system account
- psexec -i -s cmd.exe
- Type WBEMTest from the command prompt
- Connect to the default WMI location of remote DP \\MEMCMSecondary\root\cimv2 where MEMCMSecondary is my remote DP server
- Click on Connect button
- Make sure the remote DP’s WMI is connected successfully
I have seen in many blogs/forums that recompiling of MOF file (smsdpprov.mof) could help to fix the 0x800706ba error. But personally, I have not used this method to resolve the issues. I recommend raising a ticket with Microsoft support before you do this step.
- Browse to Drive Letter:\Program Files\Microsoft Configuration Manager\bin\x64
- Search for smsdpprov.mof file
- Copy the above file to remote DP
- Run the following command (as administrator) from remote DP
- mofcomp.exe smsdpprov.mof
SCCM DP Logs
Check the SCCM log files related to DPs. The PkgXferMgr.log file is your best friend for remote DP distribution/package replication issues.
|distmgr.log||Package Application distribution process|
|PkgXferMgr.log||Records the actions of the SMS_Executive component that is responsible for sending content from an SCCM primary site to a remote DP.|
- Content distribution failure on a newly configured DP – How To Manage Devices Community Forum
- Troubleshoot – Content distribution in Configuration Manager
- Fix SCCM SendFiles Failed 0x80070003 Error | ConfigMgr
- SCCM package distribution failed to remote DP