Upgrading if networked SQL Server AyaNova

Top Previous Next

It is always recommend to read through all instructions first before proceeding.

NOTE: Refer to the AyaNova Pricing web page and AyaNova FAQ Answers web page for details on upgrade pricing

NOTE: AyaNova 5 requires SQL Server 2005 or higher. Microsoft no longer supports SQL 2000 or lower.

NOTE: As per the steps below, you apply your AyaNova 5 Activation key after you have performed the upgrade steps. Make sure that you perform the upgrade steps before the Install By date of your AyaNova 5 Activation key.

Before proceeding, make sure that you know your AyaNova Administrator username and password

•

One of the many new features of AyaNova 5 is that ONLY users of type Administrator have access to grids/features of Administration pane regardless of rights given to prevent viewing by non-Administrator users and accidental changes. So if your AyaNova Administrator is the only user that is of type Administrator and you do not know the AyaNova Administrator username and password, you won't ever be able to edit users, security groups, etc.

•	If you do not know your AyaNova Administrator username and password, before upgrading to AyaNova 5 log in as another user that does have rights to the Users grid, and edit the AyaNova Administrator username and password, and keep that username and password in a safe place (i.e. in a safe).

Upgrading for network SQL Server configuration is a 8 step process

1. Create backup of your SQL Server AyaNova 4 database

2. Remove all AyaNova 4 programs

3. Install stand-alone AyaNova 5 on server

4. Configure the server's AyaNova 5 for network SQL Server database

5. Apply the AyaNova 5 keycode to your AyaNova 4 database

6. Prep and install AyaNova 5 on networked computers

7. Install and configure any additional AyaNova 5 optional server programs (Event Generator, WBI, MBI, and/or DP)

8. Confirm your SQL backup and restore procedures.

1. Create backup of your SQL Server AyaNova 4 database

a. Make a backup of your AyaNova 4 database using an approved SQL Server utility such as SQL Server Management Studio

b. Make a backup of your config.txt file so that you can refer to it as needed in steps further down

2. Remove all AyaNova 4 programs

•	Make sure all users are out of all AyaNova 4 related programs connecting to the database (AyaNova , QBI, PTI, WBI, MBI, AyaNova Data Portal)

•	If was running the network Event Generator 4 service, shut down that service

•	Uninstall any previous AyaNova 4 programs via Control Panel -> Add/Remove Programs

•	Uninstall QBI, PTI and any AyaNova 4 import utilities if applicable

•	Uninstall Event Generator, AyaNova Data Portal, WBI

•	Uninstall AyaNova 4

3. Install stand-alone AyaNova 5 on server

a. Refer to stand-alone AyaNova 5 installation steps

b. Run AyaNova 5 and confirm it loads successfully

•	The first time you run AyaNova 5, it will display with the AyaNova Administrator username and password pre-entered as the trial AyaNova 4 database was installed - this is OK and expected.

c. Make sure you have exited out of AyaNova 5

4. Configure the server's AyaNova 5 for your SQL Server database as per step #6 of the network SQL Server configuration

a. perform step #6 of the network SQL Server configuration Do note that you can instead replace the stand-alone configuration config.txt file that was just installed which your backup config.txt file.

b. Run AyaNova 5 which connects now to your AyaNova 4 database and updates it

•	The first time AyaNova 5 runs, it will update your AyaNova 4 database. It may take a while to first load as it makes internal changes - let it run as it could take 15 seconds up to 15 minutes or more, and the AyaNova 5 log in screen will show up when it is ready

c. Log into AyaNova 5 as the AyaNova Administrator and confirm loads correctly

•	A message will display that the licenses have expired - this is OK and expected because your AyaNova 5 database needs to now be licensed for AyaNova 5.

•	If you encounter an issue connecting to your AyaNova networked database via the server, do go back and double-check each of your steps from the beginning.

d. NOTE: AyaNova 5 has database "fingerprinting" where it compares your database against what is expected. If additional tables or columns have been added or the database schema modified, AyaNova 5 will not start to prevent additional problems arising as a result from those that have modified their database.

If you get a message loading AyaNova that the AyaNova database appears to have been modified and then it lists all the tables in the AyaNova database, and at the end of the list it shows a table called dtproperties, what has occurred is that at some time, someone in your organization created a diagram of the AyaNova database using SQL Enterprise Manager which created this additional table. You need to delete the table dtproperties and then run AyaNova again.

If instead you get a message loading AyaNova 5 that the AyaNova database appears to have been modified and then it lists all the tables in the AyaNova database, and at the end of the list it doesn't show a table called dtproperties, send us the ayalog.txt file from your server where this occurred so that we can see it and help you identify what table/field as been added to the AyaNova database which should not have been done.

5. Apply the AyaNova 5 keycode to your AyaNova 4 database.

a. refer to your AyaNova 5 keycode for steps to apply.

6. Prep and install AyaNova 5 on networked computers as per step #7 of the network SQL Server configuration

a. perform step #7 of the network SQL Server configuration

7. Install and configure any additional AyaNova 5 optional programs on the server (Event Generator, WBI, MBI, and/or DP) as needed