Description

During normal IT operations the Foundation servers may need to be restarted. To ensure Winshuttle Foundation is operational after a restart, certain Windows server components will need to be running. Most of these components automatically start themselves after restarting, but if there is an issue that causes one of these components to fail you may not be aware of until users encounter errors.

Some Windows server components rely on other components to start correctly. If one component fails it may cascades into a failure of other components. Sometimes, even order of operations and the speed at which a server can start certain components can cause a disruption long enough to cause another component to fail.

Windows Server 2012 R2 and later are typically robust at ensuring all components come up without issue.

Applies To

Foundation 11

Winshuttle Services on the Application Server

These services need to be running after a restart.

• RabbitMQ
• Winshuttle LMS Background Service
• WinshuttleWorker (this has a 2 minute delay in starting, so it will not be running immediately after a restart)
• WinshuttleWorkerLaunchGUI (this has a 2 minute delay in starting, so it will not be running immediately after a restart)

Services on the SharePoint Server

There are no Winshuttle services on a SharePoint server unless Winshuttle Foundation LMS and Winshuttle Foundation SAPIS have installed on the SharePoint server. This might be the case in Development or QA environments, but is not supported for Production environments.

IIS Sites​ on the Application Server

• Winshuttle LMS
• WinshuttleServer (SAPIS Manager)
• Winshuttle Composer

IIS Sites​ on the SharePoint Server

These IIS sites need to be started. It's rare for a site to be stopped on restart and will usually be related to application pool credentials being wrong (the service account needs a password change, is locked out, or was entered incorrectly).

• Winshuttle Workflow Administration

Application Pools

Each of the corresponding application pools for the above sites needs to be a running state.

SharePoint Sites, Services, and Application Pools

In order for Winshuttle Foundation User Governance and Workflow functionality and Studio connectivity, all SharePoint standard services, sites, and application pools should be operating normally. These include, but are no limited to:

• SharePoint Timer service.
• SharePoint Administration service.
• SharePoint site and application pool for each web application hosting Winshuttle.