This article provides a resolution for the issue that you are unable to view Roles and Features and receive error code 0x800706BE in Server Manager.
Original KB number: 2461206
Symptoms
Consider the following scenario:
- You have a computer that is running Windows Server 2008 or Windows Server 2008 R2.
- You open the Server Manager window to view/add/remove roles and features.
In this scenario, roles and features are not displayed with a yellow bang against them in the Server Manager window. You receive the following error message at the bottom of Server Manager if you try to open it:
Server Manager
Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
For more information, see the event log: Diagnostics, Event Viewer, Applications and Services Logs, Microsoft, Windows, Server Manager, Operational.)
At the same time, the event below is added into the Microsoft-Windows-ServerManager/Operational log:
Log Name: Microsoft-Windows-ServerManager/Operational
Source: Microsoft-Windows-ServerManager
Date: <date & time>
Event ID: 1601
Task Category: None
Level: Error
Keywords:
User: <user name>
Computer: <computer name>
Description:
Could not discover the state of the system. An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
at Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery()
at Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery()
at Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult(RefreshType refreshType)
at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)
Cause
Some catalog files, manifest files, or MUM files are corrupted on the computer.
Resolution
Here are the steps to fix the issue:
-
Get the Microsoft Update Readiness Tool from the location: https://support.microsoft.com/kb/947821.
-
Run the Microsoft Update Readiness Tool on the problematic computer.
-
You open the %Systemroot%\Windows\logs\CBS\Checksur.log file after the scan was completed.
-
You check corrupt information in the files. Here are some samples:
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum Expected file name Package_for_KB978601_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum Expected file name Package_for_KB979309_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file nameOr
(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog (f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog
Or
(f) CBS MUM Missing 0x00000002 servicing\packages\Package_114_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum (f) CBS MUM Missing 0x00000002 servicing\packages\Package_83_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum
Further down you will see:
Unavailable repair files:
servicing\packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum
servicing\packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum
servicing\packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.cat
servicing\packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.cat
Copy these files into: %systemroot\Windows\Servicing\Packages.
-
You first need to gain control over that folder. In order to do this, use the following commands:
takeown /F c:\Windows\Servicing\Packages /D y /R -
Now assign full control using the following command. It will grant you full control over the directory:
cacls c:\Windows\Servicing\Packages /E /T /C /G "UserName": F -
Now you need to gather the missing or corrupted files from the
checksurlog: download the KB files for the missing files.servicing\packages\Package_for_ KB978601 ~31bf3856ad364e35~amd64~~6.0.1.0.mum
-
Unpack them using the following command:
Expand -F:\* UpdateKBXXXX.msu x:\DestinationDirectory -
After you expand, you will see an UpdateKBXXXX.cab File. Expand it as well:
Expand -F:\* UpdateKBXXXX.CAB x:\DestinationDirectoryCABInside of this cab you will need to grab two files: update.mum and update.cat.
-
Rename the gathered update.mum and update.cab files exactly as they are in the checksur.log:
Ex.: update.mum for KB978601 will be Package_for_ KB978601 ~31bf3856ad364e35~amd64~~6.0.1.0.mum
Do the same for all the other missing/corrupt files and place them into the directory specified in checksur.log (/servicing/packages).
After these steps, the problem should be fixed, no reboot required.
Note: If Server Manager is not working even after doing these steps, run the Update Readiness Tool again and double check the steps described above.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
