Winshuttle Worker and Winshuttle Worker Launch GUI Windows services do not start and attempting to manually start generates an error.
v11, v10, SAPIS
By default, the Winshuttle Worker and Winshuttle Worker Launch GUI Windows services should start and be running to process SAP posting jobs. These services have several dependencies before they can start. If these dependencies fail, the services will also fail and cannot be started until the issue is corrected.
To determine the issue, replicate the error to generate a fresh error event entry in the Windows Event log. Then open the Windows Event Viewer and click on the Application log. The error generated will provide details on why the service failed to start.
Common reasons for these services to fail:
- The RabbitMQ Windows service is not started.
- The RabbitMQ service is not responding.
- This can happen in architectures with multiple applications servers. Restart RabbitMQ on each application server.
- The WinshuttleServer site is stopped.
- The WinshuttleServer site's application pool is stopped.
- The service's web.config file is pointed to the wrong SAPIS URL.
- The service's service account has an issue, such as locked out or the password has changed.
If the Rabbit Mq service is not working check the installation is not corrupted
If the installation is corrupted ; they would need to reinstall the Rabbit MQ and also make sure the registry entry mention in the below article is also removed.