How To Fix Server Manager Roles Error In Windows 2008 R2

August 17, 2021 By Justin Fernando Off


In this user guide, we are going to identify some potential causes that can cause the Windows 2008 r2 Server Manager role error, and then provide some possible fixes that you can try to resolve the issue.

Recommended: Fortect

  • 1. Download and install Fortect
  • 2. Open the program and click "Scan"
  • 3. Click "Repair" to start the repair process
  • Download this software and fix your PC in minutes.



    • Read 2 minutes

    This hardware provides a solution to the problem of inability to set roles and functions, and the error code can be found in Server Manager 0x800706be.

    Applies to: Windows Server 2012 R2
    Original Knowledge Base Number: 2461206


    1. You have a private computer running Windows Server or Windows Server 2008 R2 2008.
    2. You have unlocked the Server Manager window to view / add / remove roles and features.

    In this scenario, professions and functions are not highlighted in yellow in the Server Manager window. You get the following error in the message at the end of Server Manager when you try to open it:

    Server Manager
    Unexpected error while updating Server Manager: Could not call remote methods. (Exception from HRESULT: 0x800706BE)
    For more information, see Auditing Events: Event Diagnostics, Viewer, Application and Service Logs, Microsoft, Windows, Server Manager, Operations.)

    At the same time, an event is added that is smaller than Microsoft Windows Server Manager / Run Your journal:

    Protocol name: Microsoft-Windows-ServerManager / Operational
    Source: Microsoft-Windows-ServerManager
    Event ID: 1601
    Task category: none
    Level: Error
    Unable to determine the state of the system. Unexpected exception encountered:
    System.Runtime.InteropServices.COMException (0x800706BE): The call interrupt routine failed. (HRESULT Exception: Caused by 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 selection state)


    Some files, manifest files, or MUM file types are corrupted on the computer.


    1. Download the Microsoft Preparedness Tool for a personal update from anyFrom the location: .

    2. Run the Microsoft Update Readiness Tool on the problem computer.

    3. After the check is complete, you unlock the% Systemroot% Windows logs CBS Checksur.log file.

    4. Recommended: Fortect

      Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

    5. 1. Download and install Fortect
    6. 2. Open the program and click "Scan"
    7. 3. Click "Repair" to start the repair process

    They check if the information used in the files is corrupted. Here are some examples:

    (f) CBS MUM corrupted 0x00000000 Maintenance Packages Package_for_KB978601 ~ 31bf3856ad364e35 ~ amd64 ~~ Expected filename Package_for_KB978601_server ~ 31bf3856ad364e35 ~ amd64 ~~ The actual filename does not match the actual filename
    (f) Corrupted MUM 0x00000000 service Packages Package_for_KB979309 ~ 31bf3856ad364e35 ~ amd64 ~~ Expected filename Package_for_KB979309_server ~ 31bf3856ad364e35 ~ amd64 ~~ does not match actual filename


    (f) MUM Corrupt 0x800B0100 maintenance Packages Package_for_KB978601 ~ 31bf3856ad364e35 ~ amd64 ~~ maintenance Packages Package_for_KB978601 ~ 31bf3856ad364e35 ~ amd64 ~~ manifest directory cannot be confirmed by the add-on manifest directory packages(f) CBS Corrupt mum 0x800B0100 maintenance Packages Package_for_KB979309 ~ 31bf3856ad364e35 ~ amd64 ~~ maintenance Packages Package_for_KB979309 ~ 31bf3856ad364e35 ~ amd64 ~~ p> Unable to verify package


    (f) MUM cbs Missing 0x00000002 maintenance packages Package_114_for_KB955839 ~ 31bf3856ad364e35 ~ amd64 ~~ CBS MUM 0x00000002 is missing under servicing Packages Package_83_for_KB955839 ~ 31bf3856ad364e35 ~ amd64 ~~

    Below you will probably see:

    Recovery files not available:
    service packages Package_for_KB978601 ~ 31bf3856ad364e35 ~ amd64 ~~
    service packages Package_for_KB979309 ~ 31bf3856ad364e35 ~ amd64 ~~
    service packages Package_for_KB978601 ~ 31bf3856ad364e35 ~ amd64 ~~
    service packages Package_for_KB979309 ~ 31bf3856ad364e35 ~ amd64 ~~

    1. First of all, you need to manage and take control of this folder. The following commands are available for this:

        takeown / F c:  Windows  Servicing  Packages / D Fitnessstudio / R 
    2. Now give full control with the new command below. This gives the person complete control over the directory:

        cacls c:  Windows  Serving  Packages / E / T / C / G "Username": F 
    3. Now you need to recover missing or damaged files from a specific checkur log:Download KB files because files are missing.

      Maintenance Packages Package_for_ KB978601 ~ 31bf3856ad364e35 ~ amd64 ~~

    4. Unzip them with the following command:

        Expand -F:  * UpdateKBXXXX.msu x:  DestinationDirectory 
    5. When expanded, you will see a large file. Also expand it exactly:

        UpdateKBXXXX expand -f:  *. CAB x:  DestinationDirectoryCAB 

      In such a taxi, you need five files: update.mum and

    6. Rename the resulting files update.mum and exactly as they are in checkur.log:

      Example: update.mum KB978601 for sera Package_for_ KB978601 ~ 31bf3856ad364e35 ~ amd64 ~~
      Do the same for all other badly missing / corrupted files and place the group in the directory specified in the checkur.log file (/ serviceing / packages).

    After these steps, the problem should be resolved, no reboot required.

    If Server Manager does not follow these steps as expected, run the Readiness Updater again and re-check the above steps.

    • 2 minutes to read.

    This text offers a solution specifically to the Windows Server problem when roles are resolvedthose using Server Manager generate an incredible error message and event 1601.


    windows 2008 r2 server manager roles error

    The next time you click Roles in Server Manager on a new Windows Server computer, your profile will not load correctly and you will receive a powerful error message. If you select the error details, you will see the correct message:

    Server Manager:
    Unexpected error while updating Server Manager; reading cannot be an anonymous gift of security. (Exception from HRESULT: 0x00070543)For more information, see Event Log: Diagnostics, Event Viewer, Application and Service Logs, Microsoft, Windows, Manager, Production Server.

    To view the details of an event, open the Event Viewer on A. go



    Download this software and fix your PC in minutes.




    Windows 2008 R2 Serverhanterare Roller Fel
    Windows 2008 R2 서버 관리자 역할 오류
    Erreur De Roles De Gestionnaire De Serveur Windows 2008 R2
    Errore Dei Ruoli Del Gestore Server Di Windows 2008 R2
    Windows 2008 R2 Server Manager Rollenfehler
    Oshibka Rolej Dispetchera Serverov Windows 2008 R2
    Blad Rol Menedzera Serwera Windows 2008 R2
    Erro De Funcoes Do Gerenciador De Servidor Windows 2008 R2
    Windows 2008 R2 Servermanager Rollen Fout
    Error De Roles De Administrador De Servidor De Windows 2008 R2