none
RD Connection Broker service failed to start. HRESULT = 0x8007139F RRS feed

  • Question

  • Hi,

    I have a Windows Server 2012 R2 there i have installed:

    RD Web Access

    RD Connection Broker

    RD Session Host

    But RD Connection Broker service will not starta I get this 3 errors:

    Event ID: 833 Source: TerminalServices-SessionBroker

    The VMResource plugin failed to load. Error: VMResource is not a valid Win32 application. 

    Event ID: 833 Source: TerminalServices-SessionBroker

    The MS Default Provisioning Plugin plugin failed to load. Error: The group or resource is not in the correct state to perform the requested operation. 

    Event ID: 898 Source: TerminalServices-SessionBroker

    RD Connection Broker service failed to start. HRESULT = 0x8007139F.

    I have checked VMResource in register in it´s look fine.

    Regards Pierre

    Friday, November 15, 2019 2:14 PM

All replies

  • HI
    1 is your RDCB server only used to one collection in your environment ?
      is there only one rds environment in your company ?
        for example  there are 3 collections in rds environment and RDCB on server 1 is used for these 3 collections.
     server1: is installed RDCB,RDWEB,RDSH role and in collection 1 (like your mention)
     server2: is installed RDSH and in collection 2
     server3: is installed RDVH and in collection 3
    2 when the problem first happen ,did you install update to cause your issue and did you change any then cause your issue ?
    run below powershell command on problematical server then check the update installed history with your issue.
    $QFE = Get-hotfix -computername $server | select-object -property Description,HotFixID,InstalledBy,InstalledOn | out-file c:\windows\temp\$server.txt
    change $server to host name of problematical server

    3 did you install problematical w2012r2 on vmware ESXI virtual platform ?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 18, 2019 3:13 AM
    Moderator
  • Hi,

    1.

    Yes it´s only one RDS Enviroment, used for 2 different applikation on 2 diffrent servers.

    Server 1 RDCB, RDWEB, RDSH

    Server 2 RDSH

    2.

    yes the problem did come after we did run Windows update on the server.

    3.

    And yes it´s installed on  vmware ESXI virtual platform.

    Regards Pierre


    • Edited by Bobergp Tuesday, November 19, 2019 8:12 AM
    Tuesday, November 19, 2019 7:55 AM
  • HI
    4 could you please enter below powershell command on RDCB server then check which update patch you had installed before your issue first happened ?

    $QFE = Get-hotfix -computername $server | select-object -property Description,HotFixID,InstalledBy,InstalledOn | out-file c:\windows\temp\$server.txt
    change $server to host name of problematical server

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 19, 2019 1:39 PM
    Moderator
  • Hi,

    here it is:

    Update KB3024755 NT AUTHORITY\SYSTEM 11/13/2019 12:00:00 AM
    Update KB3045717 NT AUTHORITY\SYSTEM 11/12/2019 12:00:00 AM
    Update KB3055323 NT AUTHORITY\SYSTEM 11/13/2019 12:00:00 AM
    Update KB3094486 NT AUTHORITY\SYSTEM 11/12/2019 12:00:00 AM
    Update KB3100473 NT AUTHORITY\SYSTEM 11/13/2019 12:00:00 AM
    Update KB4339284 NT AUTHORITY\SYSTEM 11/12/2019 12:00:00 AM
    Update KB4462901 NT AUTHORITY\SYSTEM 11/12/2019 12:00:00 AM
    Update KB4468323 NT AUTHORITY\SYSTEM 11/12/2019 12:00:00 AM
    Update KB4486105 NT AUTHORITY\SYSTEM 11/12/2019 12:00:00 AM
    Update KB4514371 NT AUTHORITY\SYSTEM 11/13/2019 12:00:00 AM
    Update KB4515846 NT AUTHORITY\SYSTEM 11/13/2019 12:00:00 AM
    Security Update KB4521864 NT AUTHORITY\SYSTEM 11/12/2019 12:00:00 AM
    Security Update KB4525243 NT AUTHORITY\SYSTEM 11/13/2019 12:00:00 AM
       

    Regards Pierre


    • Edited by Bobergp Wednesday, November 20, 2019 9:03 AM
    Wednesday, November 20, 2019 8:37 AM
  • HI
    5 could you please run below command(open as admin) on problematical sever then check if we can find thread ?
    sfc scannow
    dism /online /cleanup-image /scanhealth   
    dism /online /cleanup-image /restorehealth 

    6 download and install process monitor v3.5 on problematical sever
    7 Open the process monitor, press “Ctrl+E” to “suspend” it, “Ctrl+X” to clear present process information.
    8 Press “Ctrl+E” to start the process monitor again.
    9 restart "remote desktop connection broker" service on RDCB and wait it stop then Press “Ctrl+E” to “Suspend” it again then save the present log(Ctrl+S).save all event as logfile.pml
    10 open the logfile.pml to check which process to stop "remote desktop connection broker" service
       we can check the event log of event id 898 then confirm the detail fail time then look the logfile.pml and check wich process to stop "remote desktop connection broker" service at the fail time.
    https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, November 21, 2019 10:00 AM
    Moderator
  • HI
    Is there any progress on your question?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 26, 2019 10:11 AM
    Moderator
  • HI
    Is there anything to help you?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Saturday, November 30, 2019 5:10 AM
    Moderator
  • Hi,

    sorry about the delay.

    sfc scannow did not help

    I did run Procmon and that helped me to find:VMResource

    that is an dll file that is called vmplugin.dll located in system32

    the question is if it´s valid, the size of the file is 68.9 KB, date modified 1/25/2019 but it has no File version or Product name on the file.

    Shoulde it not be signed by Microsoft?

    Regards Pierre

    Tuesday, December 3, 2019 10:32 AM
  • HI

    11.your vmplugin.dll seems damaged.
    we can backup or snapshot our server first then do below things.
    we can copy the damaged vmplugin.dll to another disk location then try to replace it with new one from other normal w2012r2 server. Finally run below command in command prompt(open as admin) to reregister this vmplugin.dll file.
    regsvr32 vmplugin.dll 


    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Wednesday, December 4, 2019 2:17 AM
    Moderator
  • Hi,

    I did come a bit longer, now I get this error insted:

    source: TerminalServices-SessionBroker

    event ID: 833

    The VMResource plugin failed to load. Error: The group or resource is not in the correct state to perform the requested operation. 

    Regards Pierre

    Wednesday, December 4, 2019 3:12 PM
  • HI
    12.we can run below command in command prompt (open as admin) on RDCB server.
    sfc /scannow
    dism /online /cleanup-image /scanhealth  
    dism /online /cleanup-image /restorehealth

    13.Please check the symptom in a clean boot (refer to windows 10 steps) environment if it is possible. 

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, December 9, 2019 2:57 AM
    Moderator