Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

OmniServer Upgrade Procedure - V2.0

I currently have OmniServer V2.0 installed and want to migrate to the current version.  What is the procedure I need to follow to make sure my protocols and configuration still work in the current version?

Versions since 2.5 use a new licensing scheme completely different from the older scheme. You will need your new license number available to remove the current version demo mode. Please contact us for information on obtaining a new license.  If you already have your new license number, you can register here or please contact us if you require assistance.


As the current version is, in fact, a complete and separate installation from Version 2.0, this is technically not an upgrade. However, if you follow the steps below, your configuration and protocols will work normally in the current version.

The OPC DA ProgID has changed since V2.0 to SWToolbox.OmniServer. No changes were made to the DDE, FastDDE, or Suitelink application names.

To upgrade from Version 2.0:

  1. IMPORTANT: Please make a backup of your V2.0 installation directory. Although nothing in this procedure will destroy the V2.0 installation, it's always best to have a backup.
  2. If you are running V2.0 as a service, stop the service. To do this, first launch the OmniServer Configuration and select View ⇒ Runtime options from the OmniServer menu. Uncheck the "Run as a service" option, then exit. Finally, check the Services section in your system's Administrative tools and insure that the server has been stopped and is disabled.
  3. If you are not running V2.0 as a service, stop the polling for V2.0 by right-clicking on the icon in the system/icon tray and selecting Exit. If you do not see the icon, then V2.0 is not running.
  4. Install the current version.
  5. Browse to the OmniServer V2.0 directory.
  6. Inside the V2.0 directory, you need to copy the following files for transfer to the current version:
    1. omnisrv.cfg - Configuration file containing your Topic and Device configurations
    2. .DPD files - Each protocol you have will have a corresponding DPD protocol file.
  7. Open the OmniServer Configuration in the current version (if it is not already open) and go to the Protocols view.
    1. On the left-hand side, right-click Protocols. Go to Import -> Protocol and browse to each of your DPD files to import them into OmniServer
    2. Go to File -> Import CFG and browse to your omnisrv.cfg file to import your topics and devices into OmniServer
  8. If you have more than one protocol (DPD) file, you can also manually copy the files to one of the following directories (first, make sure OmniServer Poller is stopped by right-click on the system tray icon and selecting Exit):
    1. XP/2003 Server - C:\Documents and Settings\All Users\Application Data\Software Toolbox\OmniServer
    2. Vista/7/8/2008/2012 Server or newer - C:\ProgramData\Software Toolbox\OmniServer
  9. Your topics, devices and protocols should now be available in the current version of OmniServer.
  10. Register the current version with the new license number provided with your purchase.  The required unlock code can be obtained by going to our online registration center.
  11. Uninstall OmniServer v2.0

And that's all there is to it! Your next step will be to test the new installation with your configuration and protocols just to make sure that everything works.