IMOS On-Prem - Upgrading from a Previous Release of IMOS7

View IMOS Documentation in the Help Center.

 This is a Key Topic, with high value for all users.

About IMOS7 Updates

IMOS updates are released to you in a Zip file distributed through the Client Center. The IMOS administrator needs to unzip the file and copy the contents to the installed IMOS home directory (for example, D:\veson\imos).

We do not recommend that any update be deployed to the Production environment without testing. As detailed in Architecture Recommendations, the recommended process is for updates to be released to the Test environment initially and, after changes are validated, rolled into Production. Testing needs to take place with current and valid data. The next section illustrates a possible strategy for refreshing data from Production to any other environment.

Be sure to make a backup copy of currently installed executables, the database, and the Configuration files containing specific flag settings before rolling out the updates to any of the environments.

Upgrading from a Previous Version of IMOS7

If you are already running an older version of IMOS7 and are upgrading to the current version, you must perform the following actions:

1. Back up your current IMOS installation directory and database.
2. Ensure that there are no active users on the system.
3. Stop the relevant IMOS7 Messaging Service.
4. Unregister the existing service(s) in Windows:
   1. imosauth /unregister (if applicable)
   2. imosmsg /unregister
      You may need to execute the following command before unregistering:
      set imosmsginstancename=<instance_name>
      where <instance_name> could be, for example, test.
      This ensures that you are unregistering the correct service.
5. Download the new version of IMOS from the Client Center.
6. Open the file and click Yes when prompted to extract IMOS. After initial decompression, the IMOS Extractor opens.
   
7. Select an easily accessible folder to extract to and select Extract Files for Upgrade.
8. Type your install key, which you can find on the Client Center, and click Start Extraction.
9. Open the folder where you extracted IMOS to.
   
10. Replace your current IMOS installation files with the IMOS installation files you just extracted: Copy the imos folder and paste it over the imos folder in your production IMOS directory.
11. Register the service(s):
    1. imosauth /register (if applicable)
    2. imosmsg /register
12. Start the IMOS7 Messaging Service.
13. Log in to IMOS as an administrator. The following prompt appears:
    • Cannot log in to {environment} because {database} at{host} is {version}. IMOS {version} requires database {version}. Enter administrator credentials for your database to update, or contact your IMOS administrator.
      
14. If you are using SQL authentication, type the SQL authentication user name and password that has admin access to the database.
    • Select Windows authentication if you are logged in as an administrator who has access to the database.
15. Click Upgrade.
16. Restart the IMOS7 Messaging Service.

Tip

During the Upgrade Schema process, you may encounter an error such as "Cannot create a row size of xxxx which is greater than the allowable maximum row size of 8060," as in the illustration below. This error means that a row overflow happened.

SQL Server supports row-overflow storage, but this may have to be explicitly declared using the 'large value types out of row' option (see here). You would need to run this SQL query. See the following sample:

  use MYDBSCHEMA;
  GO
  EXEC sp_tableoption 'DBTABLE', 'large value types out of row', VALUE;

The error in the illustration above happened while the script was doing work on the table 'dbo.userprefs'. Therefore, the SQL query would be customized to:

  use MYDBSCHEMA;
  GO 
  EXEC sp_tableoption 'dbo.userprefs', 'large value types out of row', 0;