Search

Language:  
Search for:

Available article translations:

Parallels Terminal Server Agents are offline after reboot (ServicesPipeTimeout)

APPLIES TO:
  • Parallels Remote Application Server

Symptoms

  • After every service reboot, the Parallels Terminal Server 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 2X Terminal Server Agent 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 2X Terminal Server Agent service to connect.
    Event Xml:
    

Cause

This issue occurs because the Windows Service Control Manager does not receive a timely response back from the Parallels service’s start request. The service start fails, and the service remains in the "stopped" state.

Resolution

  1. Go to Start > Run > type regedit.
  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
  3. With the control folder selected, right click in the pane on the right and select new DWORD Value.
  4. Name the new DWORD: ServicesPipeTimeout.
  5. Right-click ServicesPipeTimeout, and then click Modify.
  6. Click Decimal, type 180000, and then click OK.
  7. Restart the computer.

Search words:

Terminal Server stopped

service remains stopped

timeout has reached

registry change

RAS




1d70d1f9c41d01c5f7202a4290e434e1

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No