Supportworks services start order

The following is the required order to ensure all services start and that no errors occur (i.e Non Friendly Names in reports etc).

Start the Services in the Following Order:

1. SwSQLServer
2. SwServerService
3. SwSchedulerService
4. SwMessengerService
5. SwMailService
6. SwMailScheduler
7. SwLogService
8. SwIndexService
9. SwFileService
10. SwCalendarService
11. SwAdminService
12. SwHTTPServer

Please note that the SwSQLServer are found on the windows services panel and the others are found on the Supportworks server configuration. Once complete STOP and START SwHTTPServer. To STOP all services the above should be performed in reverse order.

Start the Services in the Following Order:

1. SwHTTPServer
2. SwSQLServer
3. SwServerService
4. SwSchedulerService
5. SwMessengerService
6. SwMailService
7. SwMailSchedule
8. SwLogService
9. SwIndexServer
10. SwFileService
11. SwCalendarService

You can create windows batch jobs to stop and start the services:

To stop the services, create a Windows batch job that contains:

net stop SwHTTPServer
net stop SwCalendarService
net stop SwFileService
net stop SwIndexServer
net stop SwLogService
net stop SwMailSchedule
net stop SwMailService 
net stop SwMessengerService
net stop SwSchedulerService
net stop SwServerService
net stop SwSQLServer

To Start the services, create a Windows batch job that contains:

net start SwSQLServer
net start SwServerService
net start SwSchedulerService
net start SwMessengerService
net start SwMailService 
net start SwMailSchedule
net start SwLogService
net start SwIndexServer
net start SwFileService
net start SwCalendarService 
net start SwHTTPServer

Save them on the Supportworks server and set up a Windows Scheduled Job to run the stop batch job before any backups or network tests are done. Set up another scheduled job to run the batch job to start the services after any backups are done.