![]() Rename the gathered update.mum and update.cab files exactly as they are in the checksur.log:Įx.: update.mum for KB978601 will be Package_for_ KB978601 ~31bf3856ad364e35~amd64~~6.0.1.0.mumĭo the same for all the other missing/corrupt files and place them into the directory specified in checksur.log (/servicing/packages).Īfter these steps, the problem should be fixed, no reboot required.I have a. Inside of this cab you will need to grab two files: update.mum and update.cat. Expand it as well: Expand -F:\* UpdateKBXXXX.CAB x:\DestinationDirector圜AB Unpack them using the following command: Expand -F:\* UpdateKBXXXX.msu x:\DestinationDirectoryĪfter you expand, you will see an UpdateKBXXXX.cab File. ![]() Now you need to gather the missing or corrupted files from the checksur log:ĭownload the KB files for the missing files. It will grant you full control over the directory: cacls c:\Windows\Servicing\Packages /E /T /C /G "UserName": F Now assign full control using the following command. In order to do this, use the following commands: takeown /F c:\Windows\Servicing\Packages /D y /R You first need to gain control over that folder. Servicing\packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.catĬopy these files into: %systemroot\Windows\Servicing\Packages. You check corrupt information in the files. You open the %Systemroot%\Windows\logs\CBS\Checksur.log file after the scan was completed. Run the Microsoft Update Readiness Tool on the problematic computer. Get the Microsoft Update Readiness Tool from the location. Some catalog files, manifest files, or MUM files are corrupted on the computer. (Exception from HRESULT: 0x800706BE)Īt .ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)Īt .CreateSessionAndPackage(IntPtr& session, IntPtr& package)Īt .InitializeUpdateInfo()Īt .Initialize()Īt .Provider.RefreshDiscovery()Īt .PerformDiscovery()Īt .CreateLocalResult(RefreshType refreshType)Īt .InternalRefreshModelResult(Object state) Cause (0x800706BE): The remote procedure call failed. Log Name: Microsoft-Windows-ServerManager/OperationalĬould not discover the state of the system. (Exception from HRESULT: 0x800706BE)įor more information, see the event log: Diagnostics, Event Viewer, Applications and Services Logs, Microsoft, Windows, Server Manager, Operational.)Īt the same time, the event below is added into the Microsoft-Windows-ServerManager/Operational log: Unexpected error refreshing Server Manager: The remote procedure call failed. You receive the following error message at the bottom of Server Manager if you try to open it: ![]() In this scenario, roles and features are not displayed with a yellow bang against them in the Server Manager window. You open the Server Manager window to view/add/remove roles and features.You have a computer that is running Windows Server 2008 or Windows Server 2008 R2.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.Īpplies to: Windows Server 2012 R2 Original KB number: 2461206 Symptoms
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |