We are currently investigating the issue and we will contact you tomorrow to discuss this issue further.

Hi Mustafa,

You can contact me today about this very urgent issue. Arjan is on the road today.
I'll send you an email with my skype details.

Thanks.

Donald and Mustafa,

Please see topic: http://forums.visokio.com/discussion/2451/scheduler-pdf-batch-error-

Schedulers are not stable at the moment. This is causing serious issues again.
Please contact us ASAP. Paola already knows about this new problem.

Thanks.

We have created a build with a fix and extended diagnostics for running multiple schedulers.

It is available for download now, daily builds, Omniscope 2.8 b1199 23rd of January 2014.

1.
Stop all your schedulers.

2.
Install the version above or later.

3.
Enable function not supported debug
Open Omniscope on the Desktop and "Enable function not supported debug", Select Settings -> Advanced->Debugging & Diagnostics, check "Enable function not supported debug".
Exit the Desktop.

4.
Separate the log for each of your schedulers.
In the batch file you use to start schedulers modify or add the paramater -DserverLogFilename to the java.exe command line you use.

Set a different log file name for each of the scheduler instances
e.g.
-DserverLogFilename="SchedulerSpecificLogFileName.txt"

5.
Start all your schedulers


If you do not experience the problem again over the next couple of days you can switch off the "Enable function not supported debug", repeat the above process and uncheck "Enable function not supported debug".

With the new builds of 2.8 and 2.9 running problemfree since friday morning, this problem seems to be resolved.
Thanks

Hi Donald,

This problem is occuring again and is showing up all of the time on random processes.
Could you check if the fix is still working?

Which Omniscope build version number are you experiencing the problem with ?

2.8 b1250

Will check with the developers that the fix is still in place.

Can you restart the schedulers ?

How quickly does the error start to appear ?

Sure, we can restart the schedulers. I just tested a task that normally takes a few seconds to run. And now it took 2 minutes and came back with the result Function not supported....

Schedulers restarted

Restarting did not solve the issue.

Have you had any luck with the custom build we sent last week?

Hi Mustafa,

I just sent you an email.

Alexander,

Thank you for all the help and valuable testing you are carrying out for us to help diagnose the issue. One of my colleagues will be in touch later on today in regards to this.