more quick actions
minimize quick actions
Hi everyone,
I want to share with you my experience of last week when I want to configure remote desktop session in version 11.2.
As you know, remote desktop server is now an indenpendant server from the communication server.
The Remote Desktop server needs to run the "SV Core Session Host service"to be fully operational.
In the customer Remote desktop server,this services was not able to start. I had this message (attachment1.png) : "Error 1053: The service did not respond to the start or control request in a timely fashion"
To fix this issue, you need to increase the service timeout period :
The Service Control Manager will generate an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds). To resolve this problem, use the Registry Editor to change the default timeout value for all services.
Click Start, click Run, type regedit, and then click OK.
In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl
In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value, then typing ServicesPipeTimeout, and clicking Enter.
Click Decimal, enter the new timeout value in milliseconds (i prefer 180000), and then click OK.
Restart the computer.
And it works. :woohoo: :woohoo: :woohoo:
Posted : 06/02/2017 4:58 pm
Thank you for the report.
Thierry has found something that locked the service.
So it should be fixed in a futur version.
Posted : 07/02/2017 4:45 pm
Thierry integrates the changeset 19983.
- Fixed an issue that affects both svCoreDaemon and svCoreSessionHost services: the process that hosts the service blocks itself indefinitely on the main thread when an unhandled exception occurs. The Service Control Manager then terminates the process after the usual 30-second time-out and logs the following error message: "Error 1053: The service did not respond to the start or control request in a timely fashion".
- Added a new diagnostic message using the NLog library when an unhandled exception occurs in svCoreDaemon or svCoreSessionHost service.
Posted : 10/02/2017 2:29 pm
Just for info: This fix has not been validated yet.
I am still encountering an issue. I will have a check with Thierry to clarify...
Nico
Posted : 24/03/2017 2:38 pm
Hi Nico,
I update this post again to be sure of the answer we should give from now to our customers.
Have you checked the validation of changeset 19983 (and 19984) with Thierry?
The issue can still happen?
Yet we have a support file #113410 (I guess dealing with this problem) and either we can suggest him to modify Windows registry or use the latest qualified 11.2 version.
Thanks
Edouard
Posted : 03/04/2018 1:38 pm
Yes it has been validated
Posted : 03/04/2018 2:49 pm