Remote Procedure Call failed HRESULT 0x800706BE when opening up Roles and Features on Windows 2008 R2

Today when I opened up Server Manager on one of my Windows 2008 R2 servers I encountered an error while accessing the Roles and Features option.

I saw an RPC error 0X800706BE and in the event log I saw an error 1000 for the TrustedInstaller.exe faulting application

==========================================

============================================

I looked around on the internet and found that I needed to download a "System Update Readiness Tool" for the version of my server and install it, which can be found at http://support.microsoft.com/kb/947821

After I downloaded the appropriate version for my R2 box and installed it the error went away and now I am able to open up Server Manager and install the Roles and Features I wanted.

====================================

If that did not fix it for you then follow the below procedure:

You have to look at the log file the tool generates under C:\Windows\logs\CBS\CheckSUR.log and try and see at what package it is failing on.

For example you might see something like this

Unavailable repair files:

servicing\packages\Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat

Checking Windows Servicing Packages
Checking Package Manifests and Catalogs(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:Seconds executed: 1081 Found 1 errors  CBS MUM Corrupt Total count: 1
Unavailable repair files: servicing\packages\Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum servicing\packages\Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat

  • So what you need to do is first go ahead and download the KB2518867 (In your case it might be a different number so download the appropriate update for your system)
  • After you have downloaded the update use the below commands to gain ownership and give your user account full control over the C:\Windows\Servicing\Packages folder:

takeown /F c:\Windows\Servicing\Packages /D y /R     and 

cacls c:\Windows\Servicing\Packages /E /T /C /G "UserName":F 

You can download the xcacls utility to run the second command from here.

  • Now that you have downloaded the update in the CheckSUR.log we need to expand the file.

So use:

 Unpack them using the following command: 

Expand -F:* UpdateKBXXXX.msu x:\DestinationDirectory 

After you expand you will see a UpdateKBXXXX.cab File. Expand it as well: 

Expand -F:* UpdateKBXXXX.CAB x:\DestinationDirectoryCAB 

  • After you expand the CAB file go inside the folder and grab the 2 files with the same name as the one which is failing in the logs:

Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum

 Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat

If you cannot find them at first have another close look inside the folder you WILL find them.

Make sure you grab the correct files and check the names because you will see many similar files in the CAB folder but with sightly different names.

After you have successfully copied the above 2 files go ahead and place them in the C:\Windows\servicing\Packages folder and replace the existing corrupted files.

Now start the Server Manager again and as you can tell the issue has been fixed!

-Alstar