Sage 300 CRE Upgrade Guide for anterraDataCenter

Sage 300 CRE Upgrade Guide for anterraDataCenter



Background


Upgrading Sage 300 CRE to V17 or V18 can interrupt ADC syncs and disable your Windows Server Scheduled Tasks.
We have prepared this guide to assist you in upgrading anterraDataCenter and preventing sync and scheduled task outages.  Please contact us if you would like to schedule an appointment for assistance.


Checklist to upgrade anterraDataCenter with a Sage 300 Upgrade to V20.1 or later:


  1. CLICK HERE  to view the latest status of a Sage installation upgrade issue, if the issue is still open you will need to take screenshots of all Windows Server Scheduled tasks (including ones in subfolders) prior to installing the Sage Upgrade.  The Sage 300 upgrade will disable all scheduled tasks but will not delete task schedules.  

  1. Upgrade Sage following their checklist steps and reboot your server.

  1. If necessary, re-enable your scheduled tasks based on the screenshots you took in step 1.  All ADC scheduled syncs tasks should be set to “Enabled” in the Task Scheduler.  Check to ensure that the data sync tasks will not run during your anterraDataCenter software update.  If they will run set them to Disabled.




  1. Download and install the latest version of ADC from this link:  https://adc.anterrasoftware.com/Build/ADCsetup.5.5.11747.4.exe
    T he installer password is Keats

  1. Check the account used by anterraDataCenter to synchronize data.   We strongly recommend that an account be set up for the sync separate from your system admin account.  We have many support calls from clients that use their system admin account.  When the system admin account password is changed the sync fails.

  1. Check the sync account credentials in Sage and SQL Connection, if it is not a Service Account, you will need to request a Service Account.

  1. If you upgraded to Sage CRE 17.1 or newer from pre 17.1 you need to drop the existing SQL tables and let anterraDataCenter run an Update which will automatically recreate the tables to match the new Sage schema.  There are at least 2 new fields added to every table in Sage CRE 17.1 and above.

  1. Do a SQL Backup of the existing SQL Databases use by anterraDataCenter, normally called ADCData. To find out which SQL Databases to backup, open anterraDataCenter, and for each Connection, go to the “Destination Database” box and look at the SQL Server and SQL database settings as shown in this screenshot.  In this example, the DB to backup is ADCConst on the Localhost SQL Server. 




  1. Once all the SQL DBs are backed-up, you can drop the Tables in the DB using SSMS, or using the Script below to create the drop statements.  Review the output of the script before executing them to make sure it does not remove any custom tables that you may have.

    SELECT 'DROP TABLE [' + Table_name + ']' FROM INFORMATION_Schema.Tables where Table_Type = 'Base Table' 

AND TABLE_NAME like '%[_]%[__]%'

Order by Table_Name


The Script will generate the following output:






  1. Open a New Query Dialog in SQL Server Management Studio and paste in the output of the script.  After the SQL DB has been backed up and the script has been reviewed, execute the script to drop the tables.  




  1.  After the tables are dropped, Re-Enable anterraDataCenter tasks from step 3 (if necessary).  The tasks should show Ready instead of Disabled.



The next time anterraDataCenter runs a full synchronization it will automatically build all table schemas and data.  Please review the sync logs after the next ADC full sync.


Sage has released a Knowledge Base article - Upgrading to Sage 17.1 and later affects Crystal Reports using anterraDataCenter replicated SQL data.  The error on a crystal report is “"There was an error retrieving the connection info for the data folder. Please check to make sure there is an associated SQL database."   The Sage KB article can be accessed by CLICKING HERE.

    • Related Articles

    • Set up SQL Data connections for Sage Crystal Reports

      32 Bit DSN Manager 1. Create a DSN pointing to the SQL Database. 2. Connect to Sage SQL Server and Instance that has anterraDataCenter database. 3. Use Windows Authentication. 4. Change the database to your anterraDateCenter database. 5. Use Defaults ...

    • Allow Non-Administrator Users to Run ADC Updates

      Running All Connections This is the easiest configuration and allows any user to run the configured connections for all active tables. Create a shortcut to ADCUpdate.exe (located in the anterraDataCenter installation folder).  You can place this ...

    • 'Timberline Version Changed' appears when anterraDataCenter opens

      Background When anterraDataCenter opens, a dialog box with the title "Timberline Version Changed" appears Each time anterraDataCenter opens, a message appears that has the following text in it: "Timberline version has recently been updated. SQL ...

    • Troubleshooting Problems Data Sync to AnterraBI

      Some of the common reasons for the anterraDataCenter sync to stop running are as follows: The local or active directory account that is used by Windows Task Scheduler to run the data update has had its password changed. Your ERP system (Sage, ...

    • Invoice Sync: Setup Sage 300 CRE with ADC

      Once you have Invoice Sync installed, use the following steps to complete setup. Configuring Sage 300 CRE with ADC Clicking the Config menu (shown below) then choosing Setup ADC Sage 300 CRE will bring up the Config ADC Sage 300 CRE window. In the ...