Supportworks services start order- v8 and above

From support-works
Revision as of 13:46, 1 August 2018 by Pamelal (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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. MariaDBserver
  2. SwServerService
  3. SwSchedulerService
  4. SwMessengerService
  5. SwMailService
  6. SwMailSchedule
  7. SwLogService
  8. SwIndexServer
  9. SwFileService
  10. SwCalendarService
  11. ApacheServer

To STOP all services the above should be performed in reverse order.

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

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

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

net start MariaDBserver
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 ApacheServer

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

net stop ApacheServer
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 MariaDBserver

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