Simply Powerful Tracking
  Contact Us | FAQ | Search
 
Home
Features
Screen Shots
Download
Pricing
Purchase
Support
   

 

Upgrading from 4.x to Version 5.x  
 

  1. How much does the upgrade cost?

    If you've purchased in the last 12 months, you're entitled to a free upgrade.  If you purchased before that, you can upgrade to Version 5.1 for half price.

  2. In what order should the various components be upgraded?

    1. Run IV50.exe to upgrade your database, and install the 5.1 desktop client on your machine.  All the other components are optional (but must be upgraded if you are using them).  If you have more than one IssueView database, you can upgrade additional databases just by logging in with the desktop interface, using the 'admin' account - you'll be prompted to do an upgrade when you log in.

    2. Update IssueView-Web on your IIS Server. IVW now requires at least Version 2.0.50727 of the .NET Framework (previous versions could run on 1.1)

    3. Update WebSupport on your IIS Server. IVW now requires at least version 2.0.50727 of the .NET Framework (previous versions could run on 1.1)

    4. Update IvMonitor

  3. Can we upgrade our production database without affecting our existing users?

    Yes, you can install the 5.1 software on a machine, and upgrade the production database.  Database upgrades are very safe - we've been doing them for years and have never had a problem.  Your existing 4.x users can continue using the database and will never know that it has been changed.

    But, if you add or edit an issue with the 5.1 client, users with the 4.x client will see HTML markup when they view the issue.  It makes it almost impossible for them to edit Text Tab entries that were submitted via 5.1  Your best bet is to experiment with 5.1 in a test project.  Or upgrade a group of users who are restricted to a single project.

  4. How do we update all of our users' desktop software?

    Starting with version 4.4, IssueView has a WebUpdate component that will allow you to schedule an upgrade to be rolled out to all your users.  Once you schedule the upgrade, each user will be upgraded the next time they log in.  Any of your users who are not currently using version 4.4, will have to upgrade manually by downloading either the Version 4.4 Client installer or the Version 5.1 Client installer.  To schedule an upgrade:

    1. Log into IssueView with the 'admin' account.

    2. Select 'System Configuration' from the Tools menu.

    3. Click the 'Check for Updates' button.

    4. In the Check for Updates dialog, check the 'Automatically upgrade users to' option.  Version 5.1 will only be available in the list if you are currently using Version 5.1.  If you log in with a Version 4.4 client, you'll only see 4.4 upgrades.

  5. How do we test version 5.1 with a backup copy of our database?


    1. Install 5.1 with the database on a test server.  You'll may want to do the install on a test machine so the 5.1 client software doesn't over-write your production 4.x client.  If you are installing on your own machine, be sure to put the client software into a different folder.

    2. Using the 4.x client, log into your existing database as 'admin', and select 'Backup Database' from the Tools Menu

    3. Copy the backup file to the test SQL Server.

    4. Use RestoreBackup to restore the backup to the second server.

    5. Launch the 5.1 client and log into the test server


  6. Can we merge the experimental data from the backup back into our Production database?

    No, there's no easy way to take changes you make in the backup copy and merge them into your production database.  After your testing, you'll need to go through the db upgrade process a second time on the production db (but it's a painless, automated 10 second operation).  If you enter some issues, you can export the data and import it.