locked
Remote Desktop Management service not starting. service-specific error: %%2284126209 - Event ID: 7024 RRS feed

  • Question

  • Hi Forum members,

    We have a client that has intermittent issues with RDS on a 2012 R2 server.

    As an overview of the environment, the client has a single VMWare host support 2 x Windows 2012 R2 VMs one is the File/Print/Email server and the 2nd is the RDS server used to allow the client to run MYOB Enterprise. Both servers have the AD DS role and DNS roles amongst others.

    The 1st issue is that the RD Connection Broker shows the error: "The server pool does not match the RD Connection Brokers that are in it. and then "1. Cannot connect to any of the specified RD Connection Broker servers".

    The above issue seems to be caused by the RDMS service not starting. When you attempt to start it, the service stops and the error in the title is logged in the "System" event log. Full transcript below:

    Log Name:      System
    Source:        Service Control Manager
    Date:          21/01/2015 4:50:32 PM
    Event ID:      7024
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      intentionally removed.local
    Description:
    The Remote Desktop Management service terminated with the following service-specific error: %%2284126209
    Event Xml:
    <Event xmlns="
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7024</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2015-01-21T05:50:32.129949400Z" />
        <EventRecordID>53721</EventRecordID>
        <Correlation />
        <Execution ProcessID="568" ThreadID="12436" />
        <Channel>System</Channel>
        <Computer> intentionally removed.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Remote Desktop Management</Data>
        <Data Name="param2">%%2284126209</Data>
        <Binary>520044004D0053000000</Binary>
      </EventData>
    </Event>

    In addition in the "Application" event log, the following error is logged:

    Log Name:      Application
    Source:        MSSQL$MICROSOFT##WID
    Date:          21/01/2015 5:24:47 PM
    Event ID:      18456
    Task Category: Logon
    Level:         Information
    Keywords:      Classic,Audit Failure
    User:          NETWORK SERVICE
    Computer:      intentionally removed.local
    Description:
    Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Could not find a login matching the name provided. [CLIENT: <named pipe>]
    Event Xml:
    <Event xmlns="
      <System>
        <Provider Name="MSSQL$MICROSOFT##WID" />
        <EventID Qualifiers="49152">18456</EventID>
        <Level>0</Level>
        <Task>4</Task>
        <Keywords>0x90000000000000</Keywords>
        <TimeCreated SystemTime="2015-01-21T06:24:47.000000000Z" />
        <EventRecordID>4228336</EventRecordID>
        <Channel>Application</Channel>
        <Computer>intentionally removed.local</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>NT AUTHORITY\NETWORK SERVICE</Data>
        <Data> Reason: Could not find a login matching the name provided.</Data>
        <Data> [CLIENT: &lt;named pipe&gt;]</Data>
        <Binary>184800000E0000001F00000055004E0047004500520045005200410055005300530056005200300033005C004D004900430052004F0053004F0046005400230023005700490044000000070000006D00610073007400650072000000</Binary>
      </EventData>
    </Event>

    I have been attempting to resolve these errors for some time, without success. I have read the many KBs and forum entries related to the above and applied a number of the suggested fixes, including the one which suggests to add the NT SERVICE\ALL SERVICES to the "Logon as a Service" in the "User Rights Assignment" of the "Default Domain Policy" which is linked to the domain level, that both servers are objects of.

    My question to the forum is, can anyone come up with a solution to resolve the above issues and all the RDMS service to start which will then hopefully resolve the broker error?

    Regards,
    David West.

    • Moved by Amy Wang_ Thursday, January 22, 2015 7:12 AM RDS related from Windows Server 2012 Setup forum
    Wednesday, January 21, 2015 6:39 AM

Answers

  • Hi David,

    If virtual machines on the server are Windows Server 2012, then it is not supported to install Remote Desktop Connection Broker on a Domain Controller.

    More information for you:

    Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012

    http://support.microsoft.com/kb/2799605/de

    Guidelines for installing the Remote Desktop Session Host role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service

    http://support.microsoft.com/kb/2833839

    If the VMs are Windows Server 2012 R2, I suggest you install RDS on a separate machine to see if the issue persists.

    Best Regards,

    Amy


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Amy Wang_ Tuesday, February 3, 2015 12:11 PM
    • Marked as answer by Amy Wang_ Wednesday, February 4, 2015 11:55 AM
    Thursday, January 22, 2015 7:37 AM