Knowledgebase
Problem: 2X TerminalServer Agents Offline After Reboot (ServicesPipeTimeout)
Posted by on 13 August 2014 09:03 AM

Problem

After every service reboot the 2X TerminalServer Agent may remain 'stopped', possibly requiring a manual start. 

Event logs will have:

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: ABG-WTS01.ABGRONINGEN.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: ABG-WTS01.ABGRONINGEN.LOCAL
Description:
A timeout was reached (30000 milliseconds) while waiting for the 2X Terminal Server Agent service to connect.
Event Xml:

 

Environment

·         2X Remote Application Server Version 10 and later

·         All Supported Windows Operating Systems

 

Solution

·         Go to Start > Run > and 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

 

Explanation

This issue occurs because the Windows Service Control Manager does not receive a timely response back from the 2X service’s start request. The service start fails and the service will stay on ‘stopped’.

 

 

(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments: