Running Enterprise Edition as a Windows Service

Keep Scheduler and Generator running regardless of login/logouts

Beginning with version 2.2, it is possible to run Enterprise Edition as a Windows Service. This enables always-on services to remain running regardless of user account logins or logout.

Windows Server 2003, XP etc. (Version 2.4)

When you have installed the application and activated it with a valid Enterprise license, browse to the applications program folder (generally c:\Program Files\Visokio Omniscope) and you will find a folder called 'Service'

Open the folder and double-click on 'Install Visokio Service.bat'. This will install the application as a service and start it. When you install the application as a service, it will run it as the "Local System" user. For security reasons the service cannot run logged on as the "Local System" user. You will need to change the service to make it log on as a user. To do this open the Services Control Manager from Control Panel, click Administrative Tools, and then click Services. Select Visokio Enterprise, right click, then go to Properties, and choose the "Log on" tab, select "This account" and enter your account name and password, then press "OK". Now start the service.

You can now manage the service as you would any other by going to "Administrative Tools" in the Control Panel and choosing 'Services'.

Configuring scheduled tasks within the Scheduler is done in the same way as before (using the 'Visokio Scheduler' item in the Start menu) the only difference being that you cannot stop the application from here and the application continues to run after the interface is closed.

If you wish to uninstall the service you can go to the same folder and double-click on 'Uninstall Visokio Service.bat'.

Windows Vista - Running Enterprise Edition as a Windows Service (Version 2.5)

• Install Omniscope (you have to be an Administrator or have administrator user privileges to do this).
• Activate Omnsicope with an Enterprise key on the user account that the Visokio service is going to run on.
• Install Visokio service as follows:
  • From the Start menu browse to"Command Prompt", right click and "Run as administrator" (This prompts elevation on Vista).
  • Type cd and the location of the Visokio service folder (generally c:\ProgramFiles\Visokio Omnisope\service) and press Enter.
  • Type 'InstallVisokio Service.bat' and press Enter again.
  • This should install your service and start it.
• Open Service Control Manager, select "Visokio Enterprise", right click, then go to Properties, and choose the "Log on" tab, select "This account" and enter name and password of the account that the Visokio service is going to run on, then press "OK". Now start the service.
• From the Start menu, start 'Scheduler', this will open the scheduler interface where you can add and edits tasks.
• Scheduler configuration and logs are located in “user home/scheduler” folder.

Troubleshooting

Service will not install

If you try to install Visokio as a service on Vista, you will get a"OpenSCManager Failed - Access is Denied. (0x5)" error. On Vista, youneed to log on as an administrator. From the Start menu browse to"Command Prompt", right click and "Run as administrator". Type cd andthe location of the Visokio service folder (generally c:\ProgramFiles\Visokio Omnisope\service) and press Enter then type 'InstallVisokio Service.bat' and press Enter again. This should install your service and start it.

Service will not start

If your service will not start after it has been installed, please check that you have Java in your system path. This can be done by going to the Control Panel, opening "System", choosing "Advanced" ("Advanced Settings" in Vista) and clicking the "Environment Variables..." button. A new window will pop up. Under "System variables" find "Path", click edit and, if the path to the "bin" folder in your java installation is not there, type it at the end (including the "bin").

Alternatively, edit the wrapper.conf file in the service folder of Omniscope's program folder. To use a system VM:

wrapper.java.command=C:\Program Files\Java\jre1.6.0_04\bin\java

Or to configure the service to use the bundled Java VM that comes with Omniscope:

wrapper.java.command=C:\Program Files\Visokio Omniscope\pvm6u4\bin\java

Running on a 64-bit platform

If you have 64-bit Windows, and also 64-bit Java and 64-bit Omniscope, the service may not start. Please edit the wrapper.conf file in the service folder of Omniscope's program folder (generally C:\ProgramFiles (x86)\Visokio Omnisope\service\wrapper.conf).

Find this line wrapper.java.command=java
Replace with this line wrapper.java.command=C:\Program Files (x86)\Visokio Omniscope\pvm6u12x64\bin\java

"Out of memory" errors

If you get out of memory errors (in the scheduler or service log files, in the program folder), you need to open the wrapper.conf file in the service folder within Program Files\Visokio Omniscope and edit the line

#wrapper.java.maxmemory=64

Remove the # at the start and change the 64 to be a higher number such as 300.

You need to restart the service for the changes to take effect.

Files on network drives

Scheduler as a service is unable to access files on mapped network drive. The way to get around this issue is by using full UNC paths (\\machine name\path).

Scheduler task will not execute

Before installing the application you need to delete your old wrapper.conf file generally at (c:\Program Files\Visokio Omnisope\Service). As there has been configuration changes to wrapper.conf file, and a new installation does not overwrite old wrapper.conf file.