Resolved Windows Scheduler : The task's XML file contains too many nodes

[Frank.P]

Unable to synchronize task eb918e8fd4d28e77e351c1e23f254f00 with Windows Scheduler: System.Runtime.InteropServices.COMException (0x8004131D): El archivo XML de tarea contiene demasiados nodos del mismo tipo. (Excepción de HRESULT: 0x8004131D)
   en System.Runtime.InteropServices.ComTypes.IPersistFile.Save(String pszFileName, Boolean fRemember)
   en TaskScheduler.Task.Save()
   en psa.scheduler.device.PSASchedulerTask.UpdateWindowsSchedulerTask(PleskSchedulesCollection scheduledTasks, String account)
   en psa.scheduler.device.PSAScheduler.SyncWithWindowsScheduler(String userName)

CRONTAB

Always in days from 1 to 4
Every 4 minutes if hour is (From 0h to 9h and from 21h to 23h)

1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 0,1,2,3,4,5,6,7,8,9,21,22,23 1,2,3,4 * *


In linux will be : */5 0-9,21-23 1-4 * * , but in windows not allow */5 and dash
How can I do ?

 

[PavelV]

Current implementation of Task Scheduler in Plesk means that there will be task with lot of triggers defined:
0:1, 0:4, 0:8, ..., 1:1, 1:4, 1:8, ... 23:1, 23:4, 23:8, ..., 23:56
created.
This means that there will be 12*15=180 triggers for one task.
However in Windows, there is a limitation that one task can have only 48 triggers.

So for your scenario currently there is workaround:
you need to configure 4 tasks, and every task should have no more than 48 triggers, for example:
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 0,1,2,3 1,2,3,4 * *
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 4,5,6,7 1,2,3,4 * *
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 8,9 1,2,3,4 * *
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 21,22,23 1,2,3,4 * *

I see 2 improvements for Plesk here:
1) in case some problem appeared with Task scheduling, error should be reported properly in UI
2) this also should be considered as feature request for us to support syntax like "*/5" on Windows platform. In this case it will be configured as one trigger with "repeat every 5 minutes".

 

[Frank.P]

Current implementation of Task Scheduler in Plesk means that there will be task with lot of triggers defined:
0:1, 0:4, 0:8, ..., 1:1, 1:4, 1:8, ... 23:1, 23:4, 23:8, ..., 23:56
created.
This means that there will be 12*15=180 triggers for one task.
However in Windows, there is a limitation that one task can have only 48 triggers.

So for your scenario currently there is workaround:
you need to configure 4 tasks, and every task should have no more than 48 triggers, for example:
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 0,1,2,3 1,2,3,4 * *
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 4,5,6,7 1,2,3,4 * *
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 8,9 1,2,3,4 * *
1,4,8,12,16,20,24,28,32,36,40,44,48,52,56 21,22,23 1,2,3,4 * *

I see 2 improvements for Plesk here:
1) in case some problem appeared with Task scheduling, error should be reported properly in UI
2) this also should be considered as feature request for us to support syntax like "*/5" on Windows platform. In this case it will be configured as one trigger with "repeat every 5 minutes".

I hope in next release will be fixed or add improvement 2