Start task from an external scheduler

Jean, the syntax for the task launcher is correct and as you say, if you create a shortcut on the desktop with this syntax it will launch the task correctly.

What external task scheduler are you using and how are you entering the launcher details into this?

With Windows 10 Task Scheduler you should be breaking the line so that you give the full path to the launcher as one entry and put the /script:... details in to the second box, see screen shot attached.

I have set up a test doing this myself but this won't run for a couple of hours as I have another backup active at the moment so set the scheduler to fire at 8pm UK time this evening.

Thanks Steve for your answer.

As i said in my first post, I am using under W10 and TI2014 and AutoTask 2000: AT2000 running as Administrator.

I do not know why this is working under TI2014 and not under TI2017...

Jean, my own test looks to mirror your results, in that I can launch an Acronis task from the desktop with no issue but the tast I added to the Windows 10 Task Scheduler did not run as scheduled and I could not get this to run on demand either.

I have no experience with AutoTask 2000 but from looking at their website, it doesn't look to have been updated since Windows XP or 2003 OS versions as these are stated as the minimum system requirements.

Sounds like Windows UAC at play here.  In Task Scheduler open Task Scheduler Library, double click the task and select Run with Highest Privilege at the bottom of resultant window.

Since the OP has an outdated app such a provision may not be available.

Jean, an update, I was able to get this running in the Windows 10 Task Scheduler by running at highest privileges (as advised by Bob above) and by putting the full command string into a simple batch command file and setting that bat file as the program to be executed on schedule.

Hello Steve & Bob,

The problem is still alive...

I tried from AT2000 to start the task from the command line itself, and it works..

But if i start the task, the task stay in the running state, and the "TrueImageLauncher.exe" is in the "suspended" state in tne task manager...

why ??? do you have an idea ??

I tried also to set the launcher as administrator... no effect (the AT2000 run as administrator...)

Jean, sorry but I cannot help you further with getting this to work with your ATI2000 task scheduler as I do not have that application available, but it did work for me when using the Windows 10 Task Scheduler by using a batch command file to pass the ATI launcher command string.

Hello Steve,

So i need a batch file for each task started by the W10 scheduler (i have 17 tasks...). Then i have to declare each batch file as administrator ??? (highest privilege in your post)

Thanks for your answer.

Jean, using an external scheduler should only be for exceptions that cannot be handled by the built-in Acronis Scheduler provided with the Acronis True Image application, so there should be no need for you to have all 17 of your tasks configured only by an external scheduler.

If there is a requirement in terms of how your task are scheduled that cannot be satisfied by the Acronis Scheduler, then I would encourage you to open a Support Case and work with Acronis Support to see if the scheduler can be enhanced to meet this requirement, plus also use the Feedback tool within the application to request this too.

Finally, if you feel strongly about this requirement, then send a Private Message (PM) to Gaidar, General Manager Acronis True Image who can put this requirement to the development team for consideration.

Thanks Steve for your answer....

I think i found a solution to circumvent the problem:

Based from your post saying that using a bath file, it works...:

I found in AT2000 the possibility to start a Dos command instead of a StartProgram..., then i set up this dos command:

cd "%ProgramFiles%\Acronis\\TrueImageHome\" & Start TrueImageLauncher.exe /script:C2F9DD2E-2FFF-4CC7-B535-CADB3A3B2DDF

And the dos command is executed correctly....

So i modified all the tasks in AT2000...

Many thanks for your help...

Jean, glad to hear that you have found a solution using your AT2000 scheduler, thanks for documenting this, it may help someone else in the future.

Hello Steve & Bob,

Back with my problem....

Some time it is working, and some times not, and Acronis return a message in french:

"Impossible de trouver les parametres de sauvegarde pointés par ce raccourci"

translated by me:

'Cannot find backup parameters pointed by this shortcut"

Also, do you have an answer to the problem pointed by your post (#3 of this discussion) ??

Thanks...

Jean, the problem from post #3 was answered in the following posts #4 & 5 where the task needed to be run with the highest privileges for the Windows 10 Task Scheduler, plus I used a batch file to launch the backup string with just the one line in the file.

Hello Steve,

I understand the answer in post 4 and 5, but there is no reason that TI cannot be launched directly by the Windows task scheduler (without the use of a bat file), like in TI2014. May be you can report this problem to the developpers.

Jean, there is no need to raise this as an issue - I am able to run a scheduled Acronis backup task via the Windows 10 task scheduler - I just needed to enter the full path and parameters in one line and not separate these as the options would suggest.

See screen shots below of working task scheduler settings.

Hello Steve, 

Thanks again for your answer.

I followed your indications/screen shots to create a new task in W10 task scheduler...

Unfortunatly the task does not start, and the task scheduler return me an error: 2147942402.

In french:

"Le Planificateur de tâches n’a pas pu lancer l’action « C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe /script:AAEA1A8A-5240-40C5-AA3B-D8CA0F6DD50C » dans l’instance « {f3bdd224-ab73-4c21-8c95-a26db5b438a6} » de la tâche « \StartTiBU1 ». Données supplémentaires : Valeur de l’erreur : 2147942402."

Note that if i send the same command:

"C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:AAEA1A8A-5240-40C5-AA3B-D8CA0F6DD50C

via the keyboard "Win+r", the task is launched.....

Any idea ??

Jean, the error code (according to a Google search) means 'File not found' and references I found suggest it can be caused by setting the task to be deleted after it has been triggered?  See webpage: http://serverfault.com/questions/559288/what-causes-scheduled-task-error-2147942402

Other suggestions are to delete the scheduled task and create a new one??

See webpage: http://automatingmyworld.blogspot.co.uk/2013/08/task-scheduler-error-value-2147942402.html which speaks about the formatting of the path when there are spaces..

I have exported my working Windows 10 Task scheduler entry and attached below - do the same with yours and then do a comparison to see if there are any obvious differences other than those related to my system & user etc.

Steve Smith wrote:

Jean, the error code (according to a Google search) means 'File not found' and references I found suggest it can be caused by setting the task to be deleted after it has been triggered?  See webpage: http://serverfault.com/questions/559288/what-causes-scheduled-task-error-2147942402

Steve, I already saw this discussion, but it address a batch command (move),... also, why the same line of command works via the keyboard "Win+r" (in this case the task is launched).

Other suggestions are to delete the scheduled task and create a new one??

I saw also this suggestion, and i did it, without success

See webpage: http://automatingmyworld.blogspot.co.uk/2013/08/task-scheduler-error-value-2147942402.html which speaks about the formatting of the path when there are spaces..

Tried this also... no success

I have exported my working Windows 10 Task scheduler entry and attached below - do the same with yours and then do a comparison to see if there are any obvious differences other than those related to my system & user etc.

Found the problem:

I imported your task and modified the task id and it works....

In fact the "/script:xxx" parameter must be in the argument text box and not on the command line as you said in your post #15:

I just needed to enter the full path and parameters in one line and not separate these as the options would suggest.

Good help, thanks again...

Regards

Jean, glad that you have this working now even though it wasn't as obvious as it should have been!