Efficy Overflow Q&A - Recent questions tagged schedulerservice

SchedulerAdmin modification disapearing

Wed, 16 Aug 2023 11:35:39 +0000

Dear All,

I'm accessing my backend server via RDP to modify the scheduler configuration (using services\SchedulerAdmin.exe).

I add some task, I deactivate another. Then I disconnect my RDP session.

But when coming back to the server 5 minutes later, all my changes are gone.

I'm logging into the server with a privileged account and already tried to run SchedulerAdmin as Admin : no changes.

Any idea why this is happening ?

Thanks for your help,

Alexandre

Impossible to import file without extension in task scheduler service

Wed, 27 Apr 2022 12:06:01 +0000

Hi all,

I want to import some utile files in my script runned by "task scheduler service".

/*
@import General from "dataSynchro/general";
*/

But I get this error :

Error: Cannot open file "[...]\efficy\serverjs\dataSynchro\general".
Le fichier spécifié est introuvable

If I change for this :

/*
@import General from "dataSynchro/general.js";
*/

it works. I don't understand why I couldn't use this notation while I see in the documentation that I can :
Documentation

If someone could explain me what I did wrong, it will be really appreciated :)
Thanks for your help ;)

Log an estimated remaining time for tasks (scheduler)

Wed, 22 Aug 2018 09:48:41 +0000

Hi,

I begin to abandon the use of datasync since I can provide a definitly better job by doing scheduled tasks

I ve made a tool that allow you to log an estimated remaining time for the different tasks you will have to run. Fun fact this would probably work in a datasync as well^^.

this is an exemple of how you can use it :

var dataToWorkOn = new Array();
//-----(Fill your array with Sql, file reading, inputStream, ...)

var chrono = new NL_chrono();

for (var i=0; i<dataToWorkOn.length; i++){
    //-----(do your job here)

    chrono.lap();    //-----(add a new time flag in your chrono)
    log(format("$0/$1 done. Estimated lasting time: $2", i+1, dataToWorkOn.length, chrono.forecast(dataToWorkOn.length)));
}

chrono.reset(); //-----(if you want to reuse chrono)

the log output will look like something like that :

-> 45 / 12598 done. Estimated lasting time: 1d 13h 12min 23s
-> 46 / 12598 done. Estimated lasting time: 1d 13h 11min 19s
-> 47 / 12598 done. Estimated lasting time: 1d 13h 10min 13s

the forecast function will automatically calculate the remaining time depending of the total number of laps and the already achieved laps.

You can of course use chrono for different purpose.
This is the code to use it:

    function NL_chrono(){
    this.start = new Date();
    this.laps = new Array();

    NL_chrono.prototype.stringify = function(){
        return "not yet";
    }

    NL_chrono.prototype.reset = function(){
        this.start = new Date();
        this.laps = new Array();
    }

    NL_chrono.prototype.lap = function(){
        var laptime = new Date();
        var lasttime = this.start;
        if (this.laps.length > 0) lasttime = this.laps[this.laps.length -1].date;

        this.laps.push({
            date: laptime,
            laptime: laptime.getTime() - lasttime.getTime(),
            time: laptime.getTime() - this.start.getTime()
        });

        return this.laps[this.laps.length -1];
    }

    NL_chrono.prototype.forecast = function(_lap, _unit){
        if(this.laps.length === 0 || _lap < this.laps.length) return;

        var result = (_lap / this.laps.length -1) * this.laps[this.laps.length -1].time;

        switch (_unit){
            case "d": result = result / (1000 * 3600 * 24); break;
            case "h": result = result / (1000 * 3600); break;
            case "m": result = result / (1000 * 60); break;
            case "s": result = result / 1000; break;
            case "ms": break;
            default: 
                result = getTimeText(result);
                break;
        }

        return result;
    }

    NL_chrono.prototype.showStats = function(_options){
        _options = _options || {};

        var result = new Array();
        _options.maxwidth = _options["maxwidth"] || 60;

        var maxLapTime = this.laps[0].laptime;
        this.laps.map(function(_item){if (_item.laptime > maxLapTime) maxLapTime = _item.laptime;});

        var temp = "";
        for (var i=0; i<_options.maxwidth +28; i++) temp += "_";
        result.push(temp);

        result.push(format("Lap time evolution | max = $0 | total = $1 |", getTimeText(maxLapTime), getTimeText(this.laps[this.laps.length -1].time)));

        result.push(temp);
        result.push(" ");
        forEach(this.laps, function(_lap, _index){
            var size = Math.round(_options.maxwidth * _lap.laptime / maxLapTime);
            var bar = "";
            for (var i=0; i<size; i++) bar += "=";
            bar += format("(Lap $0: $1)", _index +1, getTimeText(_lap.laptime));
            result.push(bar);
        });
        return result;
    }

    NL_chrono.prototype.getTimeText = getTimeText;

    function getTimeText(_ms){
        var val = _ms;
        if (val == 0) return "";

        var result = "";
        if (val >= (1000 * 3600 * 24)) result = (val - val % (1000 * 3600 * 24)) / (1000 * 3600 * 24) + "d "
        val = val % (1000 * 3600 * 24)
        if (val != 0) {
            if (val >= (1000 * 3600)) result += (val - val % (1000 * 3600)) / (1000 * 3600) + "h "
            val = val % (1000 * 3600)
            if (val != 0) {
                if (val >= (1000 * 60)) result += (val - val % (1000 * 60)) / (1000 * 60) + "min "
                val = val % (1000 * 60)
                if (val != 0) {
                    if (val >= 1000) result += (val - val % 1000) / 1000 + "s"
                    val = val % 1000
                }
            }
        }

        return result;
    }
}

EDIT: I added a function showStats that will show you in the console a graphical representation of the time of your job :

NB the showStats function result is a string array that you ll have to log with something like :

forEach(chrono.showStats(), function(_stat){log(_stat);});

Cheers

Scheduled Workflow Window not able to display UTF-8 Characters

Tue, 13 Jun 2017 09:40:31 +0000

Hi all,

I don't want to believe it, but it looks as the Scheduled Workflow window is not able to display non latin characters :-/

Am I mistaken or is this a bug/feature?

I am dealing with japanese & chinese contacts ;-)

Thank you

Tim

Does anyone has more info about these Efficy scheduler service errors?

Thu, 26 Mar 2015 09:48:00 +0000

Hello,

Does anyone know why this error is raised in our Scheduler service, installed on a Windows 2012 server at our customer Troostwijk.
Problem is that it seems to occur randomly. I can't find anything (accept some warnings) in eventlog. The scheduler executes update/insert data scripts.

In windows:

The following information was included with the event:

Unable to write to C:\Program Files (x86)\Efficy\services\EfficyScheduler.ini

In service log:
Error while executing Script "EOleException" at line 6 char 5.
Message: "Not enough storage is available to complete this operation"

After restarting the service, it's running fine again and scripts will be executed.
(3 scripts are added on two different databases with 2 x 1440 and 1 x 1 min. interval).

Regards, Michael.