This article is not applicable to 3.0.X, 2.5.X or 2.4.X systems and users of these versions should contact [email protected] for details on upgrading.
We would normally recommend that clients employ the assistance of [email protected] or their [email protected] or [email protected] Reseller in order to assist with an upgrade. However there may be situations where this is not possible and so the following instructions are designed to provide assistance to IT professionals (who we recommend are involved in any upgrade process).
Before undertaking any upgrade please ensure that you ask all users to log off the system.
We recommend that any upgrade is carried out during a non critical time in the financial cycle.
Ensure that you have backed up your database before starting the upgrade.
Ensure that you have taken a copy of the Web.Config file from the [email protected] Web or [email protected] Web folder on the IIS Server. Its important that this is retained as it may contain specific configuration information relating to your setup which you may need to refer to later. For example the name of your database and perhaps settings which populate the login screen with server and database details.
Although the upgrade process will give the option to preserve any report templates and logos etc we recommend that the contents of the ….. [email protected] Web\PSW\Reports\ directory (for [email protected] users) and the ……[email protected] Web\PSW\Reports\directory (for [email protected] users) are also backed up and that specifically the BlankTSH.rpt and BlankEXP.rpt files are copied somewhere safe (these are the files which control the style and contents of the form “Report”.
There may be other specific files (such as Crystal Templates or PSW Images) that you may want to backup and you should consult with us or your service provider if in any doubt.
You should always start by uninstalling all Task Scheduler services. To uninstall Task Scheduler services open the Task Scheduler and choose “Remove Service” button.
You should then install the new version on all PC’s ensuring that none have been left on the old version. This is particularly important because the first PC which opens the database with the new version of the Maintenance Application will cause the database to be upgraded and this may result in no older versions being able to access the data. Its important that the Database is opened in the Maintenance Application (to upgrade the Database) before any users log in via the browser.
Once you have completed the installation of the new version you should review the new Web.Config file and compare it to the previous version for settings which are specific to your environment. You should then edit the Web.Config file in a text editor and replace specific fields as needed. Do not replace the new Web.Config file with the old one.