Supportworks services start order- v8 and above: Difference between revisions
(Created page with "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: ...") |
No edit summary |
||
| Line 34: | Line 34: | ||
To Start the services, create a batch job that contains: | To Start the services, create a batch job that contains: | ||
net start MariaDBserver | #: <code>net start MariaDBserver</code> | ||
net start SwServerService | net start SwServerService | ||
net start SwSchedulerService | net start SwSchedulerService | ||
Revision as of 13:40, 1 August 2018
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:
- MariaDBserver
- SwServerService
- SwSchedulerService
- SwMessengerService
- SwMailService
- SwMailSchedule
- SwLogService
- SwIndexServer
- SwFileService
- SwCalendarService
- ApacheServer
To STOP all services the above should be performed in reverse order.
- ApacheServer
- SwCalendarService
- SwFileService
- SwIndexServer
- SwLogService
- SwMailSchedule
- SwMailService
- SwMessengerService
- SwSchedulerService
- SwServerService
- 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