There is a known issue with upgrading Omniscope between significantly different versions after installing the Omniscope Scheduler windows service.

Currently, the installer does not overwrite the "wrapper.conf" file inside the "services" folder of the installation. This file contains a mix of installation properties and deployment customisations. When you upgrade, the installation properties become out of date, and Omniscope no longer functions correctly at certain scheduler tasks.

This file can typically be found in one of the following locations, depending on type of PC and type of installation:

C:\Program Files\Visokio Omniscope\service\wrapper.conf
C:\Program Files\Visokio Omniscope (x86)\service\wrapper.conf
C:\Documents and Settings\[Username]\Local Settings\Application Data\Visokio Omniscope app\service\wrapper.conf
C:\Users\[Username]\AppData\Local\Visokio Omniscope app\service\wrapper.conf


If you are updating a server with the Omniscope Scheduler windows service, and particularly if the version change is significant (e.g. from 2.6 to 2.7), please follow these steps:

1. Rename "wrapper.conf" (found in one of the above locations) to "wrapper-old.conf"
   
2. Install as usual. This will create a pristine and up to date "wrapper.conf" file
   
3. Re-apply any customisations you previously made. If necessary, compare the two files, e.g. using Beyond Compare.
   (Typically, the only customisation you will have made (and should be making) is to set a memory limit).
   
4. When you are satisfied you have copied any customisations, delete "wrapper-old.conf".