Hello,
We are working to integrate data from Sage 50 CA 2017 (General Ledger transactions mainly) to a Microsoft SQL Server table as a staging place to then bring into another application. We are able to this successfully by creating a MySQL ODBC (5.a driver) connection to the simply database and then using SQL statements and Openquery functions to insert the data into the staging table. This part works great, but what happens is that it seems that either when the end user is either restarting their machine or switches between their two databases in Sage the port number the Simply database is running on switches from one port to another so any scheduled integration fails since the Linked Server we created to the ODBC driver cannot connect to the MySQL database.
Changing the port in the ODBC driver corrects the issue, but how can we prevent this from happening? Has this happen to anyone else?
I found this link which describes the firewall access to allow connections and the port range described (13540-13545) I believe is our issue. The ODBC driver will connect just fine with 13540 one day, but the next it cannot so we change to 13541 and it works again.
There are two end users of Sage 50 and two databases so is there a unique port per user or could it change if they switch between the databases?
Thank you for any assistance,
Matthew Fanning