Running IOServer in NT 4.0, 2000 or XP
Home » Running IOServer in NT 4.0, 2000 or XP
Printer Friendly Version
 

Running IOServer as a service in NT 4.0, 2000 or XP

To Run IOServer as an Application

Register IOServer as an application by issuing the following command
        IOServer /RegServer

Run IOServer by issuing the following command
        IOServer

IOServer will run in all versions of Microsoft Windows from NT 4.0 to current versions of Microsoft Operating System.

System Tray

Configuring IOServer to run minimized in a shortcut will minimize IOServer to the system tray on startup. The close button will minimized IOServer to the system tray. Clicking on the IOServer icon in the system tray will restore the IOServer user interface.

To Run IOServer as a NT Service

Before attempting to run IOServer as a NT Service, IOServer must be run as an application first with the desired configuration. Only the registered version of IOServer can be run as a NT service.

Register IOServer as a NT service by issuing the following command
    IOServer /service

After IOServer is registered as a NT Service, it can only be started and stopped with Start->Settings->Control Panel->Services->IOServer. Do not start IOServer by running IOServer.exe 

Enable "Services.Log on.Log on as Local System Account.Allow service to interact with desktop" to show IOServer on the desktop. The user interface is not accessible when running IOServer as a service in Vista, Windows 7,  2008 / 8 or 2012.

Before installing a new version of IOServer when IOServer is already running as a service,  stop the IOServer service and set it to run as an application.

IOServer Start up and shutdown

If IOServer is started by an external OPC client, IOServer will automatically shutdown when the last external OPC client releases it.

If IOServer is started manually by a user, IOServer can only be shutdown manually by a user.

To Uninstall IOServer

Run
    ioserver /UnRegServer
    unwise.exe

Accessing IOServer from another machine

OpcEnum.exe needs to be running on the machine that is running IOServer. This program allows the remote OPC clients to access OPC Server that is running on the machine. You can obtain OPCEnum.exe from the OPC Foundation.

DCOM Properties of IOServer.exe

The "Interactive user" is the user that have control of the mouse and keyboard.
The "Launching user" is the user that launched the application.

It is best to use "interactive user" so that you don't have to use a password.

To remove all securities in DCOM Properties.COM Security create the user 'Everyone' on both machines
with local and remote access permissions in Edit Limits and Edit Default
with local and remote launch and activation permission in Edit Limits and Edit Default. 

Plesae run the 32 version of dcomcnfg on 64 bit operating systems.
mmc comexp.msc /32

User Privilege

The user must be at least a power user. It must be able to read and write to the HKEY_LOCAL_MACHINE\Software in the registry.

Registering IOServer

IOServer will registering itself every time it is run.

Multiple instances of IOServer running on the same machine

At start up, when IOServer detects that another instance of IOServer is running, it will shut itself down.

This feature will not work if the second instance of IOServer is started by a user whose identity is different from that which starts the first instance of IOServer.

Make sure that all IOServer OPC clients are started by users with the same identity.

 
© Copyright IOServer Pty Ltd. All rights reserved.
E-mail:  Phone/Fax: +61 2 9805 0356 (Australia)

Last updated: 15 July 2017