We just started to use Omniscope ServerPlus Edition Scheduler (running as a Windows Service) and during the refreshing of a iok file with data from a SQL Server 2008 r2 database, in the scheduler log file we got the following error message:

2013.05.30 11:00:36.083 Info: SCHEDULER LOG BEGUN
2013.05.30 11:00:36.083 Info: Version: 2.7 b485
2013.05.30 11:00:36.083 Info: Fork: false
2013.05.30 11:00:36.105 Info: Il pianificatore sembra essere già attivo - port (24679) in uso. Avvio del pianificatore in modalità solo-configurazione.
2013.05.30 11:01:00.211 Info: Executing task "Aggiorna raccolta giornaliera" (Azione file su "\\10.10.5.90\de…", ogni giorno da 30-mag-2013 11.01, per sempre)...
2013.05.30 11:02:14.010 ERROR: Could not execute action

Impossibile connettersi al database: Il server ha impiegato troppo tempo per rispondere.

2013.05.30 11:02:14.012 Warning: Action completed successfully but warnings generated:

Could not execute action:
Impossibile connettersi al database: Il server ha impiegato troppo tempo per rispondere.


We had the same problem running Omniscope and we solved it adding the following line in the installconfig.properties file:

ADDITIONAL_JVM_ARGS=-Dvisokio.disableCustomProxySelector=true -DenableProxyDebug=true -Dvisokio.disableSystemProxies=true

Later we also tried to restart the Scheduler Windows service but nothing changed.

How to solve it? Do we also have to add this line to some scheduler configuration file?

Thanks