Important upgrade information for chronicle v1.8, Figure 1, Figure 2 – Innotech Chronicle User Manual

Page 8: Figure 3, Database restore errors, Server busy error, Figure 1: figure 2: figure 3, Important upgrade information for chronicle v1.9

Advertising
background image

Chronicle Installation Instructions

Page 8

© Mass Electronics Pty Ltd 2012

Edition 3.1 dated 31/03/2014

Important Upgrade Information for Chronicle v1.9

Figure 1:  Database Restore Errors

After the Schema upgrade, SQL Server may still be working in the background. In the Chronicle

Manager Communication Menu, select "Transfer from Chronicle Server". If the database upgrade

operation is still in progress, you will see the error on the right. Click OK and wait for the process to

complete. If the error does not show after subsequent transfer attempts, the process is complete.

Figure 3:  Server Busy Error

Figure 2:  Communication Menu -

Transfer from Chronicle Server

It is considered good practice that post-installation all the site settings are checked.

• The information on this page is relevant only if you are upgrading from iSEA v1.1 or earlier.

• iSEA v2.1 is installed during the installation of Chronicle Manager. After the installation has completed, the iSEA

Virtual Points window needs to be opened and the existing Virtual Points configuration saved by clicking OK.

IMPORTANT

Database Schema Upgrade

During installation you will be prompted to update the database schema (if a database exists).

Updating the schema could take some time (20 minutes or more) depending on the speed of your

computer, available RAM and the size of your database.

If you receive any error messages similar to the images shown below, you should restart the Chronicle

Server in the Windows Services screen. If your computer appears to not be responding,

do not

restart your computer. If you restart your computer, the upgrading process will need to start over.

Advertising