Supportworks services start order: Difference between revisions
Jump to navigation
Jump to search
(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 3: | Line 3: | ||
Start the Services in the Following Order: | Start the Services in the Following Order: | ||
SwSQLServer | # SwSQLServer | ||
SwHTTPServer | # SwHTTPServer | ||
SwServerService | # SwServerService | ||
SwSchedulerService | # SwSchedulerService | ||
SwMessengerService | # SwMessengerService | ||
SwMailService | # SwMailService | ||
SwMailScheduler | # SwMailScheduler | ||
SwLogService | # SwLogService | ||
SwIndexService | # SwIndexService | ||
SwFileService | # SwFileService | ||
SwCalendarService | # SwCalendarService | ||
SwAdminService | # SwAdminService | ||
Once complete STOP and START SwHTTPServer. To STOP all services the above should be performed in reverse order. | Once complete STOP and START SwHTTPServer. To STOP all services the above should be performed in reverse order. | ||
Revision as of 17:26, 8 November 2017
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:
- SwSQLServer
- SwHTTPServer
- SwServerService
- SwSchedulerService
- SwMessengerService
- SwMailService
- SwMailScheduler
- SwLogService
- SwIndexService
- SwFileService
- SwCalendarService
- SwAdminService
Once complete STOP and START SwHTTPServer. To STOP all services the above should be performed in reverse order.