Updating ODBC Replicator Configuration
Updating the ODBC Replicator Configuration
This guide will instruct you on how to update the configuration of the ODBC Replicator Tool following a Sage update. If Sage has been updated and a new ODBC Driver is required, for example v27 > v28, you will need to change the replicator tool to use the new driver. You will need access to the server running the ODBC Replicator application and also the SQL Database this replicates to.
Updating the connection settings
- Ensure the correct version of the ODBC driver is installed on the server running the replication.
- The ODBC tool can only utilize 32-bit drivers
- In the driver, ensure this is pointing to the correct data location for Sage
- Stop the ODBC Replicator Service
- Open the ODBC Replicator Application
- Right-Click the source connection and then Edit Connection
- We have censored the name of the source connection in this example
- Ensure the DSN Name is the name of the new ODBC driver connection we created earlier
- Click Test and if this succeeds, you will be able to click Update to apply the changes.
- Close the ODBC Replicator Tool
- Start the ODBC Replicator Service
- The replication runs on a schedule interval, the status of this can be checked in the logs located here: C:\ProgramData\IT@Spectrum Ltd\ODBC Replicator\Logs
You may come across errors in the logs when this runs stating that a certain column does not exist - this will be additional columns added to Sage due to the update and these do not exist in the current SQL tables. To resolve this, you will need to re-create the relevant tables in SQL. This is a matter of renaming the relevant tables and letting the replication run again. Please ensure the ODBC Replicator Service is stopped before renaming tables in SQL - start the service once you have renamed the relevant tables. Once the replication runs, new tables will be created with the new columns added.
You can find the SQL destination by right-clicking the destination connection in the ODBC Replicator application and editing the connection. In here, you can see the SQL Server/Database where the data is replicating to.
If you run into any issues when doing this, feel free to get in touch at firstname.lastname@example.org and our support team will be happy to assist where possible.
Updating a Therefore > Sage DLL in a Workflow
Updating the custom Sage DLL Over time, you may have Sage updated to a new major version for various reasons. However once this is updated, you may come across some issues the a customer DLL task in the Therefore workflow for posting data into Sage. ...
Changing SMTP Settings in UniFLOW
Changing SMTP Setting in UniFLOW This short guide will instruct you how to change the SMTP configuration in UniFLOW for email notifications or scan to email on the Canon devices. You will need access to the "Server Config." section in the UniFLOW ...
Unable to Connect Via DCOM Message
Unable to connect to Therefore If Therefore has been freshly installed or network settings have changed, you may see a message advising that Therefore cannot connect to the server via DCOM. There are a few causes of this message so this guide will ...
Editing Report Recipients in UniFLOW
Editing Report Recipients This guide will show you how to edit the recipients in existing UniFLOW reports. This will allow you to change who UniFLOW reports are sent to when they are produced as long as you have the relevant access to the UniFLOW ...
Prevent Spindle from Using a License
Preventing Users from claiming a Spindle license This article will describe how to stop a certain machine or user from claiming a Spindle license when they log into their PC. This can be handy for machines which require Spindle installed but do not ...