Fixing SwSQL Replication Issues after Upgrade to Core Services 3.1.2
Jump to navigation
Jump to search
| Status: | Published |
|---|---|
| Version: | 1.3 |
| Authors: | HTL QA |
| Applies to: | Core Services 3.1.2 |
Fixing SwSQL Replication Issues after Upgrade to Core Services 3.1.2
The Problem
If you upgrade to Core Services 3.1.2 and have SwSQL database replication set up, you will find that the replication process no longer works due to a security lockdown.
The Solution
A permanent fix for this issue is scheduled for all releases of Core Services after Version 3.1.2. In the meantime, for Version 3.1.2 itself, we have provided a workaround that entails the replacement of two executable SwSQL files. The instructions are as follows:
- In your Web browser, download the ZIP file located at the following URL:
- Place the downloaded ZIP file in a suitable location on the server.
- From the ZIP file, extract the following two files:
- swsql.exe
- swsqlserver.exe
- In Windows, stop all the Supportworks services by opening a Command Prompt window and entering the following commands (paying particular attention to the order of the last three and the relative order of the mail services versus SwServerService):
- net stop SwAdminService
- 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 SwHttpServer
- net stop SwSqlServer
- Go to the following folder on the Supportworks server:
- C:\Program Files\Hornbill\Core Services\SwSqlServer\bin
- where the exact path would depend on your installation.
- In that folder, find the existing files swsql.exe and swsqlserver.exe, and rename each as a backup.
- Copy the two extracted files into that folder.
- Back in the Services window, start all the Supportworks services by opening a Command Prompt window and entering the following commands (paying particular attention to the order of the first three, the relative order of SwServerService versus the mail services, and the fact that you have to restart SwHttpServer a second time at the end):
- net start SwSqlServer
- net start SwHttpServer
- 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 SwAdminService
- net stop SwHttpServer
- net start SwHttpServer