Failed to run the task: The task has not been executed. How to fix this problem?
Hi
I have computer with Windows 10 Home 1709 os and Acronis true image 2018 using incremental backup. Its been tasked to run at shutdown or restart once per day. When i run first backup manually it works and makes the backup file to usb hard drive. After that when i try to run backup manually it gives this "Failed to run the task: The task has not been executed." error. I reinstalled True image and i used cleaner tool before reinstall but still same problem. I cleaned all task and remake them and still same problem. At shutdown or restart acronis tries to make backup but it fails after couple seconds.
At another computer with Windows 10 Pro 1709 it gives same error if i try to run backup manually after first successful backup but automatic once per day incremental backup works. So there must be some kind of compatibility problem with acronis true image 2018 and windows 10 1709 version.
I noticed that when i switch off "once per day" setting everything works. So i think this setting is broken somehow. But i want to use this setting so how to get it to work? i dont need many backups per day, i need just once per day.
Any ideas?
Exactly same settings but backup works if i switch off "once per day" settings.
ti_demon logs doesnt give any clues about this error but ti_console logs gives me this:
2017-11-02T15:11:43:723+02:00 12124 E0064023B: Error 0x64023b: Failed to run the task: The task has not been executed.
| trace level: error
| line: 0xdb369304f624a7dc
| file: k:\70\products\imager\home\console\logic\task_object.cpp:3291
| function: TrueImage::UI::TaskObject::BackupNow
| line: 0xdb369304f624a7dc, k:\70\products\imager\home\console\logic\task_object.cpp:3291, TrueImage::UI::TaskObject::BackupNow
| $module: ti_console_vs_9850
|
| error 0x900012: Failed to run the task: The task has not been executed.
| line: 0x96edab22042dcf31
| file: k:\70\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1178
| function: TrueImage::Managers::TaskManagerImpl::RunNow
| line: 0x96edab22042dcf31, k:\70\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1178, TrueImage::Managers::TaskManagerImpl::RunNow
| $module: ti_managers_vs_9850
|
| error 0x9005e: Failed to run the task: The task has not been executed.
| line: 0xd6e6b1a4069ca50c
| file: k:\70\schedule\manager_api\sch_mapi_run_now.cpp:142
| function: ScheduleManagement::SchedulerManager::RunInt
| line: 0xd6e6b1a4069ca50c, k:\70\schedule\manager_api\sch_mapi_run_now.cpp:142, ScheduleManagement::SchedulerManager::RunInt
| failedFlags: 0x40
| $module: ti_managers_vs_9850
satelite, I have never used "Upon event" to schedule a backup. I normally schedule a daily backup at a set time.
I have created a new file/folder task using "Upon event" with "Once a day only" selected. When I hit the "Backup now" button the first time, the backup completes. If I hit the "backup now" button again, I get the same error message that you get.
I have reviewed the user manual para 4.5.1.4, and it does not discuss the issue.
My belief is that the program is performing "as designed". The "Once a day only" takes precedence. Once a backup has been performed that day, the "backup now" button is essentially disabled.
The other MVPs may weigh in, but that's the way I see it.
Regards,
FtrPilot
Satelite, looking at your scheduling setting, you need to check the Schedul2 log entries for the time when you are either shutting down or restarting your computer, which is the event that you are basing the task execution on.
I have tried a similar, very small Files & Folders backup, using the same Once a day schedule option to run the backup upon either the Shutdown or Restart event, and when I then shutdown my system, the event tried to run but then the computer shutdown before it could be completed!
In the ATI 2018 GUI I see the following in the Activity page information.
In the Schedul2 log I see the following entries:
02/11/2017 15:46:35 :048 00000E5C OnServiceSessionChange: wtsID=1 event=6 (SESSION_LOGOFF)
02/11/2017 15:46:35 :048 00000E5C Session 1 state is 1 (WTSConnected) - locked
02/11/2017 15:46:35 :048 00000F70 Runner wait for 4294967295 ms
02/11/2017 15:46:35 :408 00000E5C OnServiceControlStop: shutdown
02/11/2017 15:46:35 :408 00000EEC OnServiceGlobStop begin
02/11/2017 15:46:35 :408 00000EEC ExecuteShutdownTasks begin
02/11/2017 15:46:35 :408 00000EEC Sent wait result SHUTDOWN_STARTED notification: WaitID = 220
02/11/2017 15:46:35 :408 00000EEC Sent wait result SHUTDOWN_STARTED notification: WaitID = 219
02/11/2017 15:46:35 :408 00000EEC Trying task 1-30 as SHUTDOWN
02/11/2017 15:46:35 :408 00000EEC Stored token 0000000000000000 replaced with 0000000000000000
02/11/2017 15:46:35 :423 00002B90 API Reply: OP=WAIT_CHANGES_EX Ver=4 Status=0 Task=0-0 Result=10(SHUTDOWN_STARTED) Extra=0
02/11/2017 15:46:35 :423 000011F8 API Reply: OP=WAIT_CHANGES_EX Ver=4 Status=0 Task=0-0 Result=10(SHUTDOWN_STARTED) Extra=0
02/11/2017 15:46:35 :423 00000F70 Running task 1-30
02/11/2017 15:46:35 :423 00000F70 DuplicateTokenEx: error=0 token=0000000000000390
02/11/2017 15:46:35 :423 00000F70 NewSecurityDescriptor: > error=0
02/11/2017 15:46:35 :423 00000F70 SetTokenInformation: > error=0
02/11/2017 15:46:35 :423 00002B90 API Entry: OP=WAIT_CHANGES_EX Ver=4 Misc=0 Id=0 IntUser=-1 LogonSid= User="NT AUTHORITY\SYSTEM" (S-1-5-18)
02/11/2017 15:46:35 :439 00000F70 GetTokenUserName: > error=0 domain="NT AUTHORITY" user="SYSTEM"
02/11/2017 15:46:35 :439 00000EEC Awaiting for running task completion
02/11/2017 15:46:35 :439 00000F70 DsGetDcName: error=1212
02/11/2017 15:46:35 :439 00000F70 GetUserProfileDirectory > error=0.
02/11/2017 15:46:35 :439 00000F70 LoadUserProfile: error=0
02/11/2017 15:46:35 :455 00000F70 CreateEnvironmentBlock: > error=0
02/11/2017 15:46:36 :533 000011F8 API Entry: OP=STOP_WAIT_CHANGES Ver=4 Misc=0 Id=219 IntUser=1 LogonSid= User="NT AUTHORITY\SYSTEM" (S-1-5-18)
02/11/2017 15:46:36 :642 00000F70 CreateProcessAsUser: error=0
02/11/2017 15:46:36 :642 00000F70 Prevented from sleep: on
02/11/2017 15:46:36 :642 00000F70 Stored token 0000000000000000 replaced with 0000000000000000
02/11/2017 15:46:36 :642 00000F70 Runner wait for 4294967295 ms
02/11/2017 15:46:36 :642 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
02/11/2017 15:46:36 :642 00000EEC runnerWait done
02/11/2017 15:46:36 :642 000011F8 API Reply: OP=STOP_WAIT_CHANGES Ver=4 Status=0 Misc=0 Id=219
02/11/2017 15:46:36 :642 00002B90 WaitId=219 Product=2 (ATI)
02/11/2017 15:46:36 :642 00002B90 API Reply: OP=WAIT_CHANGES_EX Ver=4 Status=1223 Task=1-30 Result=3(RUN_WAITED) Extra=22(POSTPONE_RUN)
02/11/2017 15:46:36 :642 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
02/11/2017 15:46:36 :845 00000F70 Deleted session
02/11/2017 15:46:36 :845 00000EEC runnerWait done
02/11/2017 15:46:36 :845 00000F70 Runner wait for 4294967295 ms
02/11/2017 15:46:36 :861 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
02/11/2017 15:46:40 :830 0000223C New API: > WtsId=0 LogonSid=S-1-5-5-0-13330709 User="NT AUTHORITY\SYSTEM" (S-1-5-18)
02/11/2017 15:46:40 :830 0000223C Created non-interactive session
02/11/2017 15:46:40 :830 00000F70 Runner wait for 4294967295 ms
02/11/2017 15:46:40 :830 00000EEC runnerWait done
02/11/2017 15:46:40 :830 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
02/11/2017 15:46:40 :830 0000223C API Entry: OP=CREATE_TASK Ver=4 Misc=0 Id=0 IntUser=0 LogonSid=S-1-5-5-0-13330709 User="NT AUTHORITY\SYSTEM" (S-1-5-18)
02/11/2017 15:46:40 :830 0000223C API Reply: OP=CREATE_TASK Ver=4 Status=0 Misc=0 Id=2
02/11/2017 15:46:40 :845 0000223C API Entry: OP=GET_WAIT_ID Ver=4 Misc=0 Id=2 IntUser=2 LogonSid=S-1-5-5-0-13330709 User="NT AUTHORITY\SYSTEM" (S-1-5-18)
02/11/2017 15:46:40 :845 0000223C API Reply: OP=GET_WAIT_ID Ver=4 Status=0 Misc=0 Id=221
02/11/2017 15:46:40 :845 0000223C API Entry: OP=WAIT_CHANGES_EX Ver=4 Misc=0 Id=2 IntUser=0 LogonSid=S-1-5-5-0-13330709 User="NT AUTHORITY\SYSTEM" (S-1-5-18)
02/11/2017 15:46:40 :845 0000223C WaitId=221 Product=0 (TEST)
02/11/2017 15:46:45 :830 00000EEC runnerWait timeout
02/11/2017 15:46:45 :830 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
02/11/2017 15:46:50 :830 00000EEC runnerWait timeout
02/11/2017 15:46:50 :830 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
02/11/2017 15:46:55 :845 00000EEC runnerWait timeout
02/11/2017 15:46:55 :845 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
02/11/2017 15:47:00 :857 00000EEC runnerWait timeout
02/11/2017 15:47:00 :857 00000EEC runnerIsIdle=1 running=1 waiting=0 doWait=1
Log ends due to shutdown!
In the ti_demon task log, the task shows that it was started but doesn't complete due to the shutdown.
02/11/2017 15:46:40 :861 +00:00 10640 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
02/11/2017 15:46:40 :861 +00:00 10640 I00640002: Operation Camera Uploads started by schedule.
02/11/2017 15:46:41 :767 +00:00 10640 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
02/11/2017 15:46:41 :767 +00:00 10640 I013C0000: Operation: Backup
02/11/2017 15:46:41 :767 +00:00 10640 I0064000B: Priority changed to Low.
02/11/2017 15:46:56 :283 +00:00 10640 I000B03F0: Create Backup Archive From: E:\Dropbox\Camera Uploads\
To file: Camera Uploads_full_b1_s1_v1.tib Compression: Normal Exclude: System files
Start: 02/11/2017 15:46:40
Stop: 02/11/2017 15:46:56
Total Time: 00:00:16
Using the Acronis Scheduler Manager, the task 1-30 shown in the Schedul2 log is shown to be the new backup task I created.
inst=rlx start=yes loc task=0-0 > get list
Id ExecApp ExecCmd
--- ---------------
CurUser 1 (DELL-STUDIO\Smiths):
1-30 ~*TrueImageHomeNotify* /dummy /script:"0B1C01B3-0C4E-4E7C-B6F8-7F02C9A8DB13" /uuid:"0B1C01B3-0C4E-4E7C-B6F8-7F02C9A8DB13" /run_mode:?RunMode?
This is confirmed by the name of the ti_demon log file which is:
ti_demon_0B1C01B3-0C4E-4E7C-B6F8-7F02C9A8DB13_D4A09AF8-D7B6-40B8-B727-198A9486425F_2017-11-02-15-46-40.log
My conclusion from looking at the above is that there is an issue here when using Schedule On Event of Shutdown or Restart where ATI is not able to prevent Windows from shutting down or restarting to allow the backup task to run to completion.
If this concurs with what you have been seeing for this topic, then I would recommend opening a Support Case with Acronis for this problem and refer them to this forum topic.
Note: I can also reproduce the further issue of getting the same error message as this topic title if trying to use 'Back up now' for this task.
Support Case # 03174362 submitted for these issues (using email).
In reply to Support Case # 03174362… by truwrikodrorow…
Can you keep me updated about this support ticket? I have been using older versions with same settings without problem so there must be some kind of compatibility problem between new windows 10 1709 version and Acronis True Image 2018.
You were faster than me for making that support ticket. I need this setting to work becouse i want my computers make backup at shutdown or restart so i can leave my computer on to make backup and it shut itself off automatically after backup is done. In my case making backup when i use computer is not an option for multiple reasons.
In the Advanced Options, down at the bottom is the Computer Shutdown section.
The first checkbox is:
Stop all current operations when I shut down the computer. I'm not sure, but I think this is checked by default. That sounds like an interesting conflict when scheduling the backup on shutdown.Could you all check to see that that is not checked and if so, uncheck to see what happens.
The second checkbox is:
Shut down the computer after the backup is complete. @satelite, perhaps this is what you want to do. That's what it sound like on your just prior post.
Bruno, good spot on the Computer Shutdown option - by default it has to stop all current operations on shutdown enabled, which explains why my test worked as it did on shutdown but not why the task gives the error per the subject of this topic when the Once a day only scheduling option is selected, and no error with this not selected!
Steve, if the Once a day only option is selected, shouldn't the task fail to run a second time during the day regardless of whether it was a manual attempt or a shutdown/restart initiating the backup task?
I've reread this thread a few times and not seeing that there is a problem if the proper options are set. Maybe something is missing.
It seems to be more of a 'catch22' situation with the Once a day only option as the backup didn't run on Shutdown and had never run but you couldn't use the Back up now option to run it either!
If this is purely down to that ATI believes that the task has already been run once on that day, then a more meaningful message should be given than saying "Failed to run the task: The task has not been executed." and pointing to non-existent Knowledgebase information for obscure error codes than no-one can interpret!
It would be better to post a message saying, "Task has already run today - do you want to run it again?" with a Yes/No set of buttons.
OK, let me see if I understand this.
With the Stop all current operations on shutdown checked, and the Once a day only option set, the task in fact did run -- it just didn't complete successfully. So then the next attempt would cause it not to run because it already had. Yosarrian's dilemma.
I agree that the messaging is confusing and your proposed solution of giving the user the option to run it again on a manual request is quite appropriate. But it sound like the @satelite's issue is easily dealt with by turning off the shutdown option.
I agree with Steve's recommendation... "It would be better to post a message saying, "Task has already run today - do you want to run it again?" with a Yes/No set of buttons."
Yeah i know i can set Acronis to shudown the computer after backup is done BUT i need it to do this when user shutdown the computer once per day without opening the Acronis software and starting backup manually or timed backup becouse i dont know when user wants to shutdown the computer. With same settings it has been working before but not now... why?
in my case this option is allready unchecked so that is not the answer for my problem! Stop all current operations on shutdown
I have tried various different tests and cannot get this option to work correctly for my own computer situation.
The Once a day only option is a bit of a diversion as that only prevents the backup from trying to run should the user shutdown or restart more than one time in a day, plus triggers the misleading "Failed to run the task..." message.
What I have found is that if there is minimal data to be backed up, then the backup will be triggered "Upon event" for Shutdown or Restart and provided the task can complete in less than approximately 2 minutes, then all is successful.
If the backup is a Full image or there are many changes to be captured, then the task is ended before it can complete - Acronis puts up the "terminating tasks, will shutdown in 2 minutes" message and the system shuts down or restarts.
Strangely, the task in the GUI shows a nice green tick to say the backup was successful on the main Backup page, but says differently on the Activity page as shown in the screen shots below:
Note: the dates on these two pages are very different! The Backup page referring to the previous successful backup task run, the Activity page referring to the 'upon event' failed run.
I am still waiting for any response to my Support Case for this issue - just the automated reply so far!
satelite, did this problem start with the Windows 10 Version 1709 update? Was everything OK on Windows 10 Version 1703?
Does it work OK for you on the Windows 10 PRO version, but fail on Windows 10 Home?
Just to toss another thing in... there is a Computer Policy to look at.
Local Computer Policy\Computer Configuration\Administrative Templates\System\Shutdown Options
Turn off automatic termination of applications that block or cancel shutdown
On my system, this is not configured meaning that "...these applications will be automatically terminated during shutdown...". Might be an explanation why very short backup tasks work but longer ones don't.
Steve, have you used the Acronis Scheduler Manager to look at the details of the task at different times to see if there are any clues there?
I'm running Windows 10 Pro Version 1703 and have not tested this here.
Bruno, I am doing all my testing on Windows 10 Home 1709 so no access to GPEDIT.MSC that is available in the Pro or Ultimate editions.
I haven't seen anything in the Scheduler Manager other than confirmation of the task id that is shown in the Schedl2 log entries.
In reply to satelite, did this problem… by truwrikodrorow…
Same error with Pro if i try to run backup manually before 24 hours between backups BUT this acronis true image has been installed BEFORE 1709 upgrade. Automatic upgrade works normal. So i dont know fully if this 1709 related problem or not.
At Home version Acronis is installed after 1709 upgrade (brand new computer)
Everything was okay at 1703 but there was acronis updates and 1709 windows upgrade allmost at same time and i noticed this problem some time after those updates and upgrade so im not so sure what caused this problem.
In reply to Bruno, I am doing all my… by truwrikodrorow…
Just small correction for you... Windows Ultimate version is thing in the past. With Windows 10 there is only 3 versions... home, pro and enterprise :)
Thanks, Satelite, all my Windows 10 versions are either Home or Pro (mainly depending on what I did the free upgrade from originally).
Is there any updates for solving this problem and any updates from support ticket?
This need to be fixed becouse at that brand new computer i cant even make manual backup anymore after first backup with this once per day setting on.
I have asked for the support case to be reviewed by the Acronis expert team as was hitting a wall otherwise where I was being asked to collect a process monitor log trace when that is impossible at shutdown or restart.
So this can be a long wait for a fix to get my backups working again :(
The latest update from this afternoon was:
Thank you for your email. I understand your concern, let me check with our resources and we will get back to you. Feel free to contact us for any further questions.
This was in response to my replying to the request for a Process Monitor trace log where I said:
In order to collect a Process monitor log, the process monitor tool has to be open before the recreation of the issue and then to use the File > Save options of the tool as described in KB 2295: Collecting Process Monitor Log <https://kb.acronis.com/content/2295> 1. Reproduce the issue without closing the utility; 2. Click/File ->Save/in the main Process Monitor window: The problem I have in being able to do this is that the problem happens at system shutdown or restart, when ATI is scheduled using 'Upon Event' to perform a backup task - so how can I collect this log when the computer is in this state? I can see no point collecting this log data after the computer has restarted again because there is no Acronis backup task active then. Please pass this case to your experts team and ask them to review it. I have provided very clear steps on how to recreate this issue so I see no reason why either you or they could not do this and see for yourselves.
Further update from Acronis on my support ticket this evening:
I am following up on your case 03174362. Due to the complex nature of the issue I’m escalating the case to our Expert Team to find the proper solution for this issue. This may involve multiple subject matter experts, resulting in additional investigation time. During this time, we may reach out to you for additional information or request you to try troubleshooting steps suggested by our Expert Team. Thank you for your support and cooperation while we work on resolving your case.
Nothing since my last post..!
Just upgraded from Acronis 2017 to 2018 today and started encountering this issue as well.
Please open a Support Case with Acronis and reference both this forum topic and my support case # 03174362 so that they know there are more users seeing this same issue.
Latest update on my case # 03174362 and conclusions from Acronis Expert team...!
My name is Ivan. I am member of Acronis expert’s team and have taken over your case #03174362. I sincerely apologize for the long processing time, and thank you for your patience. As I can see from your case you have issue with backup that should start at system shut down. I will be glad to help you I have checked your logs and with the help of your data I was able to find an internal task where this issue is already being investigated. I have forwarded your logs to the developers as well and have discussed the situation about this scenario with them whether we can expect quick solution or any ETA for the solution. Unfortunately, due to the issue complexity and very random nature, we will not have any fix for this problem soon and the developers plan to fix it in one of the next versions of the software. That is why after having talked to my manager, we have figured out that we currently only have two options to propose you: 1. Refund your license; 2. Put the current ticket into archive and notify you once we have a fix available. For now you can use any other scheduling option to create backup automatically. I would not really like to propose you the first option as I see that you are a long-term Acronis Customer and I really appreciate it but in the current case as we are unable to provide you any solution or any ETA for the solution, this seems like an option. Please, let me know what you think.
For myself, this issue is purely one of interest as I was only recreating it to help the OP satelite so I will be accepting option 2 proposed above. For other users experiencing this issue where this may be far more critical, then you need to contact Acronis Support quoting my support case #03174362 and enter a discussion for yourselves on the option(s) you may wish to pursue here.
I did as you suggested yesterday creating a ticket and referencing your request number. I hadn't yet heard a response back so this is good info. The only time this bothered me was after making heavy modifications during the day I wanted to back up my critical files a second time and was unable to - which led to a Google search which led me to this page. Hopefully they can get this figured out as 99% of the time it's a non-issue however occasionally it is.
New email received for my Support Case today:
Hello Steve, thank you for your email. I have rechecked your case and see that there was a misunderstanding from my side. The issue I have found in our internal system concerns only Windows logs that contain such an error but the backup still works. As far as I see now the issue you have concerns the backup that does not work. In this regard we need to investigate the issue. Please do following 1. Install the latest update that you can download from this link: http://dl2.acronis.com/s/AcronisTrueImage2018_10410.exe 2. As soon as the build is installed restart the PC. 3. Try to create backup with the settings you have configured before and collect following logs: 3.1. AcroInfo after reproducing the problem (here you can find the instructions how this log can be collected) https://kb.acronis.com/acroinfo 3.2. Scheduler log: https://kb.acronis.com/de/content/20521 3.3. Step by step screenshots how you reproduce the problem. Thank you for your cooperation! I am very sorry, but we can not continue the investigation without these logs. Please, upload the files to this FTP server:
I have replied as follows:
Hello Ivan,
Thank you for the latest update / feedback on this case.
I have been running the latest ATI 2018 build #10410 since the day it was released and this problem is not resolved.
The recreate steps given previous are still 100% valid - the backup task is scheduled to run "On Event" of Shutdown or Restart but never runs because Acronis terminates all operations on system shutdown giving the 2 minute warning panel.
There are no Scheduler Manager logs created because this does not appear to run in these circumstances!
Regards, Steve
Further email exchange today for this issue / support case # 3174362
I have forwarded the case to our quality and testing department and the colleagues were not able to reproduce the issue according to your description. After having discussed the situation with them they have requested the Scheduler logs which still should be created under following folder when you activate the logging: C:\ProgramData\Acronis\Schedule2 Please follow the steps given before and provide the logs so that the issue can be escalated to the developers: 3. Try to create backup with the settings you have configured before and collect following logs: 3.1. AcroInfo after reproducing the problem (here you can find the instructions how this log can be collected) https://kb.acronis.com/acroinfo 3.2. Scheduler log: https://kb.acronis.com/de/content/20521 3.3. Step by step screenshots how you reproduce the problem. Thank you for your cooperation! I am very sorry, but we can not continue the investigation without these logs. Please, upload the files to this FTP server: ....
My reply to the above response:
Sorry but this is becoming unbelievable.
The logs being requested are not created by this issue and others are impossible to collect because the whole point of reporting this problem is that it occurs when a backup is scheduled to be performed at Shutdown.
The computer does the shutdown but the Acronis event does not execute.
I have already provided all the information available.
I also do not understand why you are asking for AcroInfo when, if you follow the link you provided, this is then asking for an Acronis System Report (already provided).
There are no Scheduler logs regardless of the logging levels enabled.
No screen shots are possible because the problem is on Shutdown when nothing else is allowed.
I have already given detailed information on how this issue is reproduced along with directions to the Acronis True Image 2018 Forum topic where another user reported the same issue - which in turn was my whole reason for reproducing this problem and submitting this Support Case in my role as an Acronis MVP.
I am able to recreate this issue on every attempt by doing nothing more than setting up a backup task that would run for more than 5 minutes which is configured to run "On Event" of Shutdown or Restart, this using ATI 2018 build 10410 on a Windows 10 computer with build 1709 Fall Creators Update.
No remote connection would be possible to allow your second level team to see this problem because that is also denied by the fact that the computer is in the process of doing a shutdown in order to trigger the Acronis Backup task! Catch22 situation.
Based on the information you have received, we can not therefore expect a correction to the problem in the near future.
(google translator maded text)
what a shame... in my case backup at every shutdown is not an option or timed backup. So this once per day setting is vital. Now its broken and seems to stay at broken state.
Let me toss out a workaround using pre command and post command.
Have a post command that creates a simple file which tells when the backup successfully ran.
Have a pre command that looks at that file and determines whether to continue with the backup (ie, a day has passed or the file does not exist).
Then, set it to run on shutdown.
If you want to run it manually, just delete that small file first.
Any fix update for this problem? my parents computer still needs manual backup becouse of this problem. I want backup run daily at shutdown but only once per day. Multiple backups per day is not option for me.
satelite, the last update that I received for the support case (03174362) I submitted was from January and stated:
If your problem is that the backup does not start at shutdown or reboot event it is a known issue and should be fixed in the update 3 that we are planning to release in 2-3 months starting from now.
There has not been a new build #3 released so far this year, so we are still waiting on this fix.
Now i installed Update 3. This failed to run task error is gone but still having problems. Backup tries to run at shutdown but after some time computer just shuts down. Acronis tells to me that backup was stopped by user. In reality user has nothing to do with this.
How to fix this... its been allmost year and no working automatic backup with those settings that i want to use with this computer.
I removed old backup settings and maded new by cloning. Still there is same problem.
satelite, I have not tried to reproduce this issue since Update #3 came out and I installed it, but I will do so as soon as possible.
I received the following update on my support case (03174362) this afternoon:
Hello Steve,
here is Ivan Lapushenkov from Acronis support.
I have checked the status of your case today. Unfortunately there is no solution for this issue yet.
I have checked with the developers about the possible ETA for the fix.
Unfortunately, due to the issue complexity and very random nature, we will not have any fix for your issue soon. The developers plan to implement the fix in the next version.
That is why after having talked to my manager, we have figured out that we currently only one option to propose you:
Put the current ticket into archive and notify you once we have a fix available.
I would not really like to propose you this option as I see that you are a long-term Acronis Customer and I really appreciate it but in the current case as we are unable to provide you any solution or any ETA for the solution, this seems like an option.
Please, let me know what you think.
If you have any questions, feel free to ask!
Have a nice day!
Ok, just did a very quick test and the problem is not fixed by Update #3 - and from the tone of Ivan's message above, it doesn't sound like a fix is likely to be forthcoming anytime soon! I am not sure where the reference to "very random nature" of this issue comes from as I can reproduce without fail.
I suspect that we will need to wait for "The developers plan to implement the fix in the next version." and hope that that next version isn't actually ATI 2019 rather than Update #4 !