Error 1053 - Windows could not start the Nintex RPA Central service on local computer

[JohannesC]

RPA central fails to load. When restarting the RPA Central service it throws the error in the attached screenshot. When I try to open Foxtrot it says Nintex could not reach the configured URL. We did not change the URL at all. Restarting the server that rpa central is hosted on does not fix the issue

[Sasan]

We are in the process of investigating the issue and resolving.

[Sasan · Accepted solution]

Issue now has been resolved and service is back on-line.  Thanks for reporting and your patience.

[kwilliams]

What was the solution?  I'm having the same issue.

[Sasan]

This was due to a service outage.  However, we have not had a service outage since then.  Would you be able to provide more details on your issue with possibly screenshots.

Thanks

Sasan

[devinweber]

I'd like to see a documented workaround so that Nintex Bot could be launched anytime the RPA Central Service cannot be started because of a service disruption on the remote end.

This is preventing us from running any scheduled or on-demand bots today.

[schriste]

Agree, we're also having issues where it will not start and users can't run the bots.

We're getting error 1604: an exception occurred in the service when handling the control request.

If there's a way we can run the bot without having the connection to RPA Central, we're interested in hearing a solution.  Thank you!

[Sasan]

In the past few hours Nintex RPA Central incurred a service disruption.  Please follow these steps to resume service:

1. Go to Task Manager
2. Search for RPACentral.ServiceHost
3. Right click and End Task
4. Go to Services
5. Search for Nintex RPA Central
6. Start the service

As another option you can also restart your machine/server.