Windows could not start the UiPath Robot service on Local Computer With Error Code 1053 or 1064

News Knowledge Base
1

Why is Error 1053: The service did not respond to the start or control request in a timely fashion, thrown?

Issue Description

While attempting to start or reboot the UiPath Robot service, the following errors are received:

  • "Windows could not start the UiPath Robot service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."

  • "Windows could not start the UiPath Robot service on Local Computer. Error 1064: An exception occurred In the service when handling the control request."

Root Cause

  • The issue arose due to a incorrect configuration values located at C:\Program Files\UiPath\Studio\uipath.config, which caused the parser to misinterpret the resultant data.
    • For Example: The XML comment contains a start tag but does not contain a matching end tag.
  • Incompatible .Net Framework installed on Robot Machine
  • If the Robot Service is taking longer than the defined timeframe

Resolution

For Root Cause #1

For example, in this case, this error is thrown in the Application Event Viewer logs for (C:\Program Files\UiPath\Studio\uipath.config line 32):

"UiPath.Service.Host 22.10.5.0 

Topshelf.ServiceBuilderException: An exception occurred creating the service: RobotNTService


—> System.TypeInitializationException: The type initializer for ‘UiPath.Service.Api.Communication’ threw an exception.


—> System.TypeInitializationException: The type initializer for ‘UiPath.Shared.Configuration.SharedAppConfiguration’ threw an exception.


—> System.Configuration.ConfigurationErrorsException: An error occurred while parsing EntityName. Line 32, position 63. (C:\Program Files\UiPath\Studio\UiPath.config line 32)


—> System.Xml.XmlException: An error occurred while parsing EntityName. Line 32, position 63.


at System.Xml.XmlTextReaderImpl.Throw(Exception e)


…"

Resolution:

  • Escape the ampersand "&" character or check internally if a proxy script can be provided without an ampersand "&" character.
  • Change this line from:

3.png

  • To this line:

4.png

More details here: Escaping XML Data.

For example, in this case, this error is thrown in the Application Event Viewer logs for (C:\Program Files\UiPath\Studio\uipath.config line 34):

"

UiPath.Service.Host 22.10.5.0


Topshelf.ServiceBuilderException: An exception occurred creating the service: RobotNTService


—> System.TypeInitializationException: The type initializer for ‘UiPath.Service.Api.Communication’ threw an exception.


—> System.TypeInitializationException: The type initializer for ‘UiPath.Shared.Configuration.SharedAppConfiguration’ threw an exception.


—> System.Configuration.ConfigurationErrorsException: The ‘add’ start tag on line 33 position 6 does not match the end tag of ‘webProxySettings’. Line 34, position 3. (C:\Program Files\UiPath\Studio\UiPath.config line 34)


—> System.Xml.XmlException: The ‘add’ start tag on line 33 position 6 does not match the end tag of ‘webProxySettings’. Line 34, position 3.


at System.Xml.XmlTextReaderImpl.Throw(Exception e)


…"

Resolution:

  • Add an end tag that matches the start tag.

or

  • If the tag contains no inner text, such as , specify a forward slash before the closing angle bracket.
  • Change this line from

1.png

  • To this line:

2.png

    For Root Cause #2

    UiPath Robot service utilizes .NET Framework. Ensure the latest version of .NET Framework is installed.

    For Root Cause #3

    1. Press Win+R and type 'Regedit'

    2. Navigate to 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control'

    3. Look for the 'ServicesPipeTimeout' entry

    4. If it doesn't exist, create a new DWORD value with that name

    5. Set the value to 180000 (in decimal)

    Important:

    1. After correcting the C:\Program Files\UiPath\Studio\uipath.config file, Save the file as Administrator,
    2. Search for services.msc in Windows Start Menu and restart the UiPath Robot service to apply the change.

    More details can be found below: