Description

Each time our server is rebooted, the Winshuttle Worker services don't seem to start correctly. I can start them at a later time. They are set to delayed start and Recovery was set to restart the services (first and second failures). I have changed it now so subsequent failures also attempt to restart the service. Here is the error. Do you know what causes this? Is there some prerequisite service that is taking a long time to start?

Service cannot be started. System.ServiceModel.FaultException: Error from Manager while registering worker.
InnerException Message: Connection failed

The only thing that changes is some amount of time passes and then the services will start.  I’m not sure about how much time is needed, but it is probably >10 minutes.  So we may have services that are not starting as quickly as they should and it would be nice to be able to identify them.

Applies To

11x;12x

Solution/Immediate Workaround

This  depends upon machine config; When a service is set to delayed automatic
it gets started when all IIS services and Windows features for machine get activated.
User would need to check with their IT team to check why it takes so long.

However if our services are not starting attached article can be reviewed Winshuttle Worker Services Not Start