After each RDS server's reboot, RAS RD Session Host Agent may remain "stopped," possibly requiring a manual start.
Event logs will show the following:
Log Name: System Source: Service Control Manager Date: 07/05/2013 05:20:40 Event ID: 7000 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ***********.LOCAL Description: The RAS RD Session Host service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Log Name: System Source: Service Control Manager Date: 07/05/2013 05:20:40 Event ID: 7009 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ***********.LOCAL Description: A timeout was reached (30000 milliseconds) while waiting for the RAS RD Session Host service to connect. Event Xml:
This issue occurs because the Windows Service Control Manager does not receive a timely response back from the RAS service’s start request. The service start fails, and the service remains in the "stopped" state.
- Go to Start > Run > type regedit.
- Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
- With the control folder selected, right click in the pane on the right and select new DWORD Value.
- Name the new DWORD: ServicesPipeTimeout.
- Right-click ServicesPipeTimeout, and then click Modify.
- Click Decimal, type 180000, and then click OK.
- Restart the computer.
Note: In previous RAS versions RAS RD Session Host Agent service was called 2X Terminal Server Agent
Was this article helpful?
Tell us how we can improve it.