Hello.
I have a Windows Server 2008 R2 server. The server have a scheduled task to start a little program called Unison (sync tool). The trigger is set to run at startup. This is working well. The scheduler sucessfully start this program on boot of the server. But every day, at 06:07 the process is stopped. It looks like the scheduler is stopping it for some reasons...
Here is a XML dump of the scheduler:
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2016-01-15T07:44:03.6104232</Date>
<Author>RADE\administrator</Author>
</RegistrationInfo>
<Triggers>
<BootTrigger>
<Enabled>true</Enabled>
</BootTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>false</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>false</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>"C:\Program Files (x86)\unison2.40.16\unison2.40.16text.exe"</Command>
<Arguments>-socket 22</Arguments>
<WorkingDirectory>C:\Visma\uq\local</WorkingDirectory>
</Exec>
</Actions>
</Task>
and here is the event that is logged when the process have stopped:
Task Scheduler successfully finished "{37354e59-bc82-49aa-9eea-04fb3b974c26}" instance of the "\VismaSynk Unison" task for user "RADE\RAINTVAARYR$".
The problem began for som weeks ago. Before, this was working without stop. I have rebooted the server, and eaven re-created the scheduler. Some tips?
Best regards Oyvind
