Location

Where you can find the SDT tool:

Go to the server wherever the SDT tool configured (usually SQL server) > C: Drive > SDT > Synergetic.Application.SDT.exe

Always run the application as Administrator to make life easy make the shortcut of the application to your desktop so that you don't have to go again and again to the file location.
After that you will come to a login page
Enter Username and password provided by Upgrades team

Commence Upgrade

On the left hand there are Environments which are usually ‘Test’ and ‘Production’, though you may also have other environments in use at your ogranisation.
Select which environment that you want to do the upgrade on.

Make sure you select the correct environment that you want to upgrade

Click Check Health in the middle. It will check all the files locations and permissions on those.
Wait until Jobs in progress reduces to 0 confirming that all products are ready to be upgraded.
If there are any issues here please raise a case in the help portal.
Click on View releases on the right hand side.

You will be offered a list of available versions.
Simply highlight the version you would like to install, tick the check box ‘I have verified…’ then click Apply.

The SDT will download the product packages.
Once complete these will begin deploying.
When all packages have installed with no error the upgrade is complete.

Make sure your Service suite is stopped during the upgrade process (you will be prompted for this before the upgrade will commence).

To identify the respective server where the Synergetic Service Suite is sitting next go to windows>search services>synergetic service suite

You will have to start and stop manually before and after the upgrade process.

First it will start upgrading with the Database Patcher. One thing you have make sure during the process is that at the moment you can it showing database patcher running but it actually you don’t know it working because there is no information. wait for few minutes.

To check the database patcher working or not you can go to the working path and see it created the patchlog folder or not. PatchLog is the folder where all the logs files are stored. If it created the log

Database Patcher usually take 5 minutes for patcher it all depends on the size of the database

After the upgrade is finish the release and last updated information will automatically changed as well. Which confirms that the upgrade was successful. Below image for reference.

Sometime check health failed on certain products in that case what you can do is either check heath again 2-3 time or close the tool and run again. If the check health still comes failed it means it missing some value of the products or it haven’t been configured in that case you can call support or log a another ticket where we can join you and help you in the process.

All the products successfully upgraded but not windows client upgrade failed on windows client or your can say synmain it usually fails when somebody using your synmain during the upgrade process. Resolution: for that is make sure everybody out from the systems during the upgrade. One way to do is go to your windows right click>go to computer management>Shared folder>open file close file which are in use. After that trying again untick all the other products expect only those who failed in previous process.

We have a minor bug in the tool which comes at end of the upgrade process or when it finish with the upgrade it just a pop with a dialog which says object reference when you came across this issue don’t worry about it. Its just a trying to start the service suite automatically (which you have to do manually).