Skip to main content

Ghost task created every day after backup

Thread needs solution
Frequent Poster
Posts: 72
Comments: 460

I've had this issue in both ATI 2017 and ATI 2018. I posted about it on the forum last during 2018 beta. I'm posting here to see if anyone has it on ATI 2019 as I'm still using the 2018 version.

Every evening I run a scheduled task to backup the day's updated data (Files and Folders incremental backup). When I shutdown the PC later, I get the following error reported in the Windows Logs-->Application events with Event ID 1:

Scheduler failed to run task >> "" with GUID '2B6231CD-C984-4151-B604-C422B8B13D83' because of error 87> (Scheduler has received a request with an invalid parameter.).

Running the Acronis Scheduler Manager before nightly backups shows the following tasks (I've eliminated a few redundant lines to keep it shorter)

inst=rlx start=yes loc task=0-0 > get list
 Id ExecApp ExecCmd
--- ---------------
<snip>
  1-49 ~*TrueImageHomeNotify* /dummy /script:"BF5CCF85-FCCD-4CED-A786-320EA890026A" /uuid:"BF5CCF85-FCCD-4CED-A786-320EA890026A" /run_mode:?RunMode?
  1-63  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe
  1-64  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe /ransomware
  1-75 ~*TrueImageHomeNotify* /dummy /script:"E7C641CD-D775-4954-AA18-50D4F6FB21AC" /uuid:"E7C641CD-D775-4954-AA18-50D4F6FB21AC" /run_mode:?RunMode?
  1-76  C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe /shutup
User 2 (NT AUTHORITY\SYSTEM):
  2-1   C:\Program Files (x86)\Acronis\TrueImageHome\prl_stat.exe for_scheduler
inst=rlx start=yes loc task=0-0 >

Checking the list again after the nightly backup shows this:

inst=rlx start=yes loc task=0-0 > get list
 Id ExecApp ExecCmd
--- ---------------
<snip>
1-49 ~*TrueImageHomeNotify* /dummy /script:"BF5CCF85-FCCD-4CED-A786-320EA890026A" /uuid:"BF5CCF85-FCCD-4CED-A786-320EA890026A" /run_mode:?RunMode?
  1-63  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe
  1-64  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe /ransomware
  1-75 ~*TrueImageHomeNotify* /dummy /script:"E7C641CD-D775-4954-AA18-50D4F6FB21AC" /uuid:"E7C641CD-D775-4954-AA18-50D4F6FB21AC" /run_mode:?RunMode?
  1-76  C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe /shutup
User 2 (NT AUTHORITY\SYSTEM):
  2-1   C:\Program Files (x86)\Acronis\TrueImageHome\prl_stat.exe for_scheduler
  2-2
inst=rlx start=yes loc task=0-0 >

Where did the mysterious task 2-2 come from? What is it for? Here are the task details:

inst=rlx start=yes loc task=0-0 > task 2-2
inst=rlx start=yes loc task=2-2 > get task
Flags: 0x4207 ( enabled autodelete once shutdown temporary )
Type: daily
ExecCmd:
Product: 2
Last changed: 20.05.2019 19:00:02
R/O Flags: 0x2 ( vista_elevated )
Guid: 2B6231CD-C984-4151-B604-C422B8B13D83
ProductSpecificFlags: 0x1
AutoDeleteDelay: 300
inst=rlx start=yes loc task=2-2 >

The Flags imply that it is run once at system shutdown and then is deleted, which seems to be what is happening. But the task is not fully defined. The Last changed time is right at completion of the scheduled daily backup. There is no ExecCmd.

After the next reboot, it's gone again. But this cycle repeats every night.The only differences are that the GUID changes each time.

If it was logged as a warning and not an error, I probably would be less concerned.

inst=rlx start=yes loc task=0-0 > get list
 Id ExecApp ExecCmd
--- ---------------
<snip>
  1-49 ~*TrueImageHomeNotify* /dummy /script:"BF5CCF85-FCCD-4CED-A786-320EA890026A" /uuid:"BF5CCF85-FCCD-4CED-A786-320EA890026A" /run_mode:?RunMode?
  1-63  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe
  1-64  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe /ransomware
  1-75 ~*TrueImageHomeNotify* /dummy /script:"E7C641CD-D775-4954-AA18-50D4F6FB21AC" /uuid:"E7C641CD-D775-4954-AA18-50D4F6FB21AC" /run_mode:?RunMode?
  1-76  C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe /shutup
User 2 (NT AUTHORITY\SYSTEM):
  2-1   C:\Program Files (x86)\Acronis\TrueImageHome\prl_stat.exe for_scheduler
inst=rlx start=yes loc task=0-0 >

Any thoughts from the others?

0 Users found this helpful
Legend
Posts: 59
Comments: 16106

Bruno, I have not seen any similar issues as far as I am aware on my systems which do regular scheduled backups using any of ATI 2017, 2018 or 2019, but I also haven't taken time to start trawling through the Windows Application Event logs to check for this.

I would suggest checking exactly what options you are setting for your scheduled task to see if there is any correlation there to this ghost task?  Are you setting the task to shudown after completion?

Frequent Poster
Posts: 72
Comments: 460

Steve, there are no other symptoms of this oddity so the only way you'd know if it's happening is to look in the Event Viewer to see if the error appears, or look at the tasks with the Acronis Scheduler Manager.

The backup task is about as simple as they come. It's a File and Folders incremental backup using mostly default settings.

Forum Hero
Posts: 61
Comments: 7381

I took a look at my 2019 event logs and can't find any reference to a similar error.

I have seen those "dummy" scripts when I run task scheduler, but assume they are temp scripts run to check the status of services such as AAP, scheduler or notify.  That said, I have all other ATI services but scheduler and AAP manually disabled on my system to (don't use the cloud console, archive, mobile, etc.)

There are some other (older, non 2019) threads about the dummy scripts, but nothing specific to this error.

https://forum.acronis.com/forum/acronis-true-image-home-forum-older-versions/b6514-atih-not-managing-tasks

https://forum.acronis.com/forum/acronis-true-image-2016-forum/scheduled-backup-stuck-0-unable-stop

 

Frequent Poster
Posts: 72
Comments: 460

I created a new very small backup and monitored the tasks using the Acronis Scheduler Monitor. When I ran the backup, it created the task 2-2. I deleted the task and ran the backup again and the task was recreated. I then ran the backup without deleting the task. It was still there although the update time and GUID had changed.

I ran it with the "Stop all current operations when I shut down the computer" checked and again unchecked and it made no difference.

In the Schedul2 log I see the following lines which shows the task being deleted and recreated right at the beginning of my backup being run (within the first 2 seconds):

5/23/2019 3:52:02 PM: 000014BC API Entry: OP=DELETE_TASK Ver=4 Misc=0 Id=2 IntUser=2 LogonSid=S-1-5-5-0-37071994 User="NT AUTHORITY\SYSTEM" (S-1-5-18)
5/23/2019 3:52:02 PM: 000014BC API Reply: OP=DELETE_TASK Ver=4 Status=0 Misc=0 Id=2
5/23/2019 3:52:02 PM: 00001CE0 API Reply: OP=WAIT_CHANGES_EX Ver=4 Status=0 Task=2-2 Result=2(DELETED) Extra=0
5/23/2019 3:52:02 PM: 00001CE0 API Entry: OP=WAIT_CHANGES_EX Ver=4 Misc=0 Id=0 IntUser=-1 LogonSid=S-1-5-5-0-180583 User="ZOMO\BRUNO" (S-1-5-21-2421686853-2596532319-3253155375-1001)
5/23/2019 3:52:02 PM: 00001CE0 WaitId=228 Product=2 (ATI)
5/23/2019 3:52:02 PM: 000014BC API Entry: OP=CREATE_TASK Ver=4 Misc=0 Id=0 IntUser=0 LogonSid=S-1-5-5-0-37071994 User="NT AUTHORITY\SYSTEM" (S-1-5-18)
5/23/2019 3:52:02 PM: 000014BC API Reply: OP=CREATE_TASK Ver=4 Status=0 Misc=0 Id=2
 

Forum Hero
Posts: 61
Comments: 7381

No idea if that's "normal" or not.  Seeing as the backup run successfully, I wouldn't stress it too much.  Not much more you can really do than open a ticket and see if it is a bug or working as intended.