Skip to main content

Acronis Incremental Backup on Event (Shutdown/Restart) - Always Takes 30 Min (Logs show normal times)

Beginner
Posts: 1
Comments: 5

I was wondering if anyone had any clue as to why no matter the size of the backup (whether it's the initial/occasional full backup I have it set up to perform, or the usual small incremental backup), it takes Windows exactly 30 min to exit the "Acronis True Image is terminating the current operations" screen during the shutdown/restart process.  Checking the logs, everything is normal and the operation actually completes within the expected time frame: around 7 min for a full backup and 2 min for an incremental one (as is suggested in the default message).  Obviously 30 min makes having this setup very much not worth it however...

I'm running the most updated version of Acronis 2016 on a Windows 10 Pro, 64-bit system.  Thanks!

Legend
Posts: 31
Comments: 11278

Top

Typhoon859, welcome to these User Forums.

I do not recollect seeing any issues related to this type of backup scenario posted in the forums (other than a current one in the ATI 2018 forum where this has been broken / doesn't work and is being investigated via a Support Case with Acronis).

Unfortunately, there is no further free support for ATI 2016 users to allow opening a Support Case and Acronis will not be producing any further fixes for that product version, so the only advice is in the way of suggestions for diagnosing what is happening here?

Is this a single task that is being performed on event for shutdown/restart, and is this being done daily or less frequently?

Do you have the ability to create a new backup task of a similar size source data to see if that also gives the same 30 minutes time to complete the shutdown/restart action?  This may help show if the problem is consistent across any tasks or limited to the original one only?

Are you using the MVP Log Viewer tool to look at the backup task logs, what is shown in that tool for the overall time for the backup task to run to completion?

Beginner
Posts: 1
Comments: 5

Top

Hi, thanks Steve!

This is an event I have set to occur maximum once a day upon shutting down/restarting.  This is done/happens maybe once a week with occasionally a few days in a row if the are updates or perhaps some programs I might be installing.

Prior to this, I actually did create a new backup task just to see (one of the few troubleshooting steps I can think of) and the result was the same.

Yes, I used the MVP Log Viewer tool and as I mentioned, it showed normal times in terms of how long it took.

I don't have this with anything else, but my suspicion is that upon the trigger sent by Acronis I imagine to shut down, Windows doesn't respond to it and maybe just autistically terminates the process after 30 min?  That's probably why it's always that exact amount of time.  I was hoping perhaps one of the devs can point in the right direction as to what in Windows would be responsible for not responding?  Perhaps you may otherwise know?  I suspect the issue would actually be the same on all versions of Acronis.

Thanks again!

Legend
Posts: 31
Comments: 11278

Top

You could try looking at the Schedul2 log at around the time when the backup is executed and the time that is indicated in the backup log for when it completes, and see if this gives any clue as to what Acronis is doing at that time?  The Schedul2 log doesn't make for easy reading but you should see some details that will give you an idea of what was happening.

In reply to by Steve Smith

Beginner
Posts: 1
Comments: 5

Top

Perhaps you can direct me as to where to find this Schedul2 log? XD

Legend
Posts: 31
Comments: 11278

Top

You just need to change the Log type in the MVP Log Viewer.

2017-12-07 16_41_04.png

In reply to by Steve Smith

Beginner
Posts: 1
Comments: 5

Top

Oh, I see.  I was confused cause I thought it was a totally different thing.  Thanks! XD

So yeah, I checked, and it did actually report an issue/error (though I'm not sure it's Acronis that's at fault).  It logged exactly as I thought, an exit error:

06.12.2017 02:35:56.317 00000000000032E4 API Entry: OP=SET_EXIT_ERROR_NOT_RETRY_FLAG Ver=4 Misc=0 Id=1968 IntUser=0 LogonSid=S-1-5-5-0-95351381 User=NT AUTHORITY\SYSTEM
06.12.2017 02:35:56.317 00000000000032E4 API Reply: OP=SET_EXIT_ERROR_NOT_RETRY_FLAG Ver=4 Status=0 Misc=0 Id=1968
06.12.2017 02:35:56.317 00000000000032E4 API Entry: OP=STOP_WAIT_CHANGES Ver=4 Misc=0 Id=219 IntUser=0 LogonSid=S-1-5-5-0-95351381 User=NT AUTHORITY\SYSTEM
06.12.2017 02:35:56.317 00000000000032E4 API Reply: OP=STOP_WAIT_CHANGES Ver=4 Status=0 Misc=0 Id=219
06.12.2017 02:35:56.317 00000000000034B8 API Reply: OP=WAIT_CHANGES_EX Ver=4 Status=1223 Task=0-0 Result=0(?) Extra=0
06.12.2017 02:35:56.317 00000000000034B8 API Entry: OP=DELETE_TASK Ver=4 Misc=0 Id=2 IntUser=2 LogonSid=S-1-5-5-0-95351381 User=NT AUTHORITY\SYSTEM
06.12.2017 02:35:56.317 00000000000034B8 API Reply: OP=DELETE_TASK Ver=4 Status=0 Misc=0 Id=2

After that, all it logs is the following over and over - nothing after (what seems to be in between whatever actual operations):

06.12.2017 02:35:59.490 00000000000012A4 runnerWait timeout
06.12.2017 02:35:59.490 00000000000012A4 runnerIsIdle=1 running=1 waiting=0 doWait=1

Legend
Posts: 31
Comments: 11278

Top

Not sure if the OP=SET_EXIT_ERROR_NOT_RETRY_FLAG entry suggests an actual error or is just saying that it won't do any retries if an error is thrown?

What I would expect to see for your actual backup task are entries similar to:

Trying task 1-18 as TIME_NORMAL
Running task 1-18
Task 1-18 completed with exit code=0

The task 1-18 is taken from the output for the Acronis Scheduler Manager tool when using 'get list' for a list of tasks known to the scheduler, where this then correlates to a Script identifier which you can match to files in the C:\ProgramData\Acronis\TrueImageHome\Scripts folder.

inst=rlx start=yes loc task=0-0 > get list
 Id ExecApp ExecCmd
--- ---------------
CurUser 1 (DELLSTUDIO\smiths):
  1-4  ~*TrueImageHomeNotify* /dummy /script:"3563E983-1E6E-40E9-98DC-09C3613AC021" /uuid:"3563E983-1E6E-40E9-98DC-09C3613AC021" /run_mode:?RunMode?
  1-8  ~*TrueImageHomeNotify* /dummy /script:"F5662F31-11FA-42E5-97D5-68304C0195EF" /uuid:"F5662F31-11FA-42E5-97D5-68304C0195EF" /run_mode:?RunMode?
  1-10 ~*TrueImageHomeNotify* /dummy /script:"C0847DBE-6533-4FB7-9A2A-107FAEA170FF" /uuid:"C0847DBE-6533-4FB7-9A2A-107FAEA170FF" /run_mode:?RunMode?
  1-12  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe
  1-13  C:\Program Files (x86)\Acronis\TrueImageHome\ga_service.exe /ransomware
  1-17 ~*TrueImageHomeNotify* /dummy /script:"9EC3DE40-7C53-ABB0-43CE-061C0EB8CADF" /uuid:"9EC3DE40-7C53-ABB0-43CE-061C0EB8CADF" /run_mode:?RunMode?
  1-18 ~*TrueImageHomeNotify* /dummy /script:"48BB1A99-D59F-4C26-837D-A52FF1C4F0FA" /uuid:"48BB1A99-D59F-4C26-837D-A52FF1C4F0FA" /run_mode:?RunMode?
  1-19 ~*TrueImageHomeNotify* /dummy /script:"68BB57D3-545A-4561-BD70-24B845EE1E70" /uuid:"68BB57D3-545A-4561-BD70-24B845EE1E70" /run_mode:?RunMode?
  1-20 ~*TrueImageHomeNotify* /dummy /script:"6FEE76F4-CE2F-49C0-8579-DE1EEAECA8C3" /uuid:"6FEE76F4-CE2F-49C0-8579-DE1EEAECA8C3" /run_mode:?RunMode?
  1-22 ~*TrueImageHomeNotify* /dummy /script:"A5040CA6-CEFD-48E1-8823-8A4263112EBF" /uuid:"A5040CA6-CEFD-48E1-8823-8A4263112EBF" /run_mode:?RunMode?
  1-23  C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe /shutup
User 2 (NT AUTHORITY\SYSTEM):
  2-3   *TrueImageHomeNotify* /shutdown_now
  2-4   C:\Program Files (x86)\Acronis\TrueImageHome\prl_stat.exe for_scheduler
inst=rlx start=yes loc task=0-0 >
Beginner
Posts: 1
Comments: 5

Top

Hmm, yeah, maybe.  Well, I already pretty much mentioned the main settings I'm using for the backup and nothing else was really specifically altered to have any further effects.

I mean, look, I don't know what it's supposed to be, but I'll give you the logs from a little before the latest backup was initiated and little after:

07.12.2017 15:08:35.722 0000000000001338 Running task 1-2
07.12.2017 15:08:35.722 0000000000001338 DuplicateTokenEx: token=00000000000003FC error=0 token=00000000000003B8
07.12.2017 15:08:35.722 0000000000001338 NewSecurityDescriptor: error=0
07.12.2017 15:08:35.722 0000000000001338 SetTokenInformation: error=0
07.12.2017 15:08:35.722 0000000000001338 Scheduler user for account found
07.12.2017 15:08:35.722 0000000000001338 Session not found
07.12.2017 15:08:35.722 0000000000001338 Duplication of stored token
07.12.2017 15:08:35.722 0000000000001338 GetTokenUserName: error=0 domain=NT AUTHORITY user=SYSTEM
07.12.2017 15:08:35.724 0000000000001338 DsGetDcName: domain=NT AUTHORITY error=1212
07.12.2017 15:08:35.724 0000000000001338 GetUserProfileDirectory error=0.
07.12.2017 15:08:35.724 0000000000001338 LoadUserProfile: user=SYSTEM path=(null) error=0
07.12.2017 15:08:35.726 0000000000001338 CreateEnvironmentBlock: error=0
07.12.2017 15:08:35.726 0000000000001338 CreateProcessAsUser: token=00000000000003B8 error=2
07.12.2017 15:08:35.752 0000000000001338 Runner wait for 4294967295 ms
07.12.2017 15:08:36.721 00000000000012FC OnServiceMainWake: begin
07.12.2017 15:08:36.721 00000000000012FC Trying task 1-2 as RETRY_FAILED
07.12.2017 15:08:36.729 00000000000012FC OnServiceMainWake: next time = 7.12.2017 13:12:42
07.12.2017 15:08:50.770 0000000000001338 Running task 1-2
07.12.2017 15:08:50.770 0000000000001338 DuplicateTokenEx: token=000000000000039C error=0 token=0000000000000364
07.12.2017 15:08:50.770 0000000000001338 NewSecurityDescriptor: error=0
07.12.2017 15:08:50.770 0000000000001338 SetTokenInformation: error=0
07.12.2017 15:08:50.770 0000000000001338 Scheduler user for account found
07.12.2017 15:08:50.770 0000000000001338 Session not found
07.12.2017 15:08:50.770 0000000000001338 Duplication of stored token
07.12.2017 15:08:50.770 0000000000001338 GetTokenUserName: error=0 domain=NT AUTHORITY user=SYSTEM
07.12.2017 15:08:50.770 0000000000001338 DsGetDcName: domain=NT AUTHORITY error=1212
07.12.2017 15:08:50.770 0000000000001338 GetUserProfileDirectory error=0.
07.12.2017 15:08:50.770 0000000000001338 LoadUserProfile: user=SYSTEM path=(null) error=0
07.12.2017 15:08:50.770 0000000000001338 CreateEnvironmentBlock: error=0
07.12.2017 15:08:50.770 0000000000001338 CreateProcessAsUser: token=0000000000000364 error=2
07.12.2017 15:08:50.770 0000000000001338 Runner wait for 4294967295 ms
07.12.2017 15:08:51.724 0000000000000EC0 OnServiceSessionChange: wtsID=1 event=6 (SESSION_LOGOFF)
07.12.2017 15:08:51.724 0000000000000EC0 Session 1 state is 1 (WTSConnected) - locked
07.12.2017 15:08:51.724 0000000000001338 Runner wait for 4294967295 ms
07.12.2017 15:08:51.770 00000000000012FC OnServiceMainWake: begin
07.12.2017 15:08:51.770 00000000000012FC Trying task 1-2 as RETRY_FAILED
07.12.2017 15:08:51.770 00000000000012FC OnServiceMainWake: next time = 7.12.2017 13:12:42
07.12.2017 15:08:51.770 0000000000001338 Running task 1-2
07.12.2017 15:08:51.770 0000000000001338 DuplicateTokenEx: token=00000000000003BC error=0 token=0000000000000384
07.12.2017 15:08:51.770 0000000000001338 NewSecurityDescriptor: error=0
07.12.2017 15:08:51.770 0000000000001338 SetTokenInformation: error=0
07.12.2017 15:08:51.770 0000000000001338 Scheduler user for account found
07.12.2017 15:08:51.770 0000000000001338 Session not found
07.12.2017 15:08:51.770 0000000000001338 Duplication of stored token
07.12.2017 15:08:51.770 0000000000001338 GetTokenUserName: error=0 domain=NT AUTHORITY user=SYSTEM
07.12.2017 15:08:51.770 0000000000001338 DsGetDcName: domain=NT AUTHORITY error=1212
07.12.2017 15:08:51.770 0000000000001338 GetUserProfileDirectory error=0.
07.12.2017 15:08:51.770 0000000000001338 LoadUserProfile: user=SYSTEM path=(null) error=0
07.12.2017 15:08:51.770 0000000000001338 CreateEnvironmentBlock: error=0
07.12.2017 15:08:51.770 0000000000001338 CreateProcessAsUser: token=0000000000000384 error=2
07.12.2017 15:08:51.786 0000000000001338 Runner wait for 4294967295 ms
07.12.2017 15:08:51.864 0000000000000EC0 OnServiceControlStop: shutdown
07.12.2017 15:08:51.864 00000000000012FC OnServiceGlobStop begin
07.12.2017 15:08:51.864 00000000000012FC ExecuteShutdownTasks begin
07.12.2017 15:08:51.864 00000000000012FC Trying task 1-7 as SHUTDOWN
07.12.2017 15:08:51.864 00000000000012FC Awaiting for running task completion
07.12.2017 15:08:51.864 0000000000001338 Running task 1-7
07.12.2017 15:08:51.864 0000000000001338 DuplicateTokenEx: token=0000000000000338 error=0 token=00000000000003A8
07.12.2017 15:08:51.864 0000000000001338 NewSecurityDescriptor: error=0
07.12.2017 15:08:51.864 0000000000001338 SetTokenInformation: error=0
07.12.2017 15:08:51.864 0000000000001338 Duplication of stored token
07.12.2017 15:08:51.864 0000000000001338 GetTokenUserName: error=0 domain=NT AUTHORITY user=SYSTEM
07.12.2017 15:08:51.864 0000000000001338 DsGetDcName: domain=NT AUTHORITY error=1212
07.12.2017 15:08:51.864 0000000000001338 GetUserProfileDirectory error=0.
07.12.2017 15:08:51.864 0000000000001338 LoadUserProfile: user=SYSTEM path=(null) error=0
07.12.2017 15:08:51.864 0000000000001338 CreateEnvironmentBlock: error=0
07.12.2017 15:08:51.880 0000000000001338 CreateProcessAsUser: token=00000000000003A8 error=0
07.12.2017 15:08:51.880 0000000000001338 Runner wait for 4294967295 ms
07.12.2017 15:08:51.880 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:08:51.880 00000000000012FC runnerWait done
07.12.2017 15:08:51.895 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:08:52.020 0000000000002AA4 API Entry: OP=CREATE_TASK Ver=4 Misc=0 Id=0 IntUser=0 LogonSid=S-1-5-5-0-104548316 User=NT AUTHORITY\SYSTEM
07.12.2017 15:08:52.020 0000000000002AA4 API Reply: OP=CREATE_TASK Ver=4 Status=0 Misc=0 Id=2
07.12.2017 15:08:52.020 0000000000002AA4 API Entry: OP=GET_WAIT_ID Ver=4 Misc=0 Id=2 IntUser=2 LogonSid=S-1-5-5-0-104548316 User=NT AUTHORITY\SYSTEM
07.12.2017 15:08:52.020 0000000000002AA4 API Reply: OP=GET_WAIT_ID Ver=4 Status=0 Misc=0 Id=220
07.12.2017 15:08:52.020 0000000000002AA4 API Entry: OP=WAIT_CHANGES_EX Ver=4 Misc=0 Id=2 IntUser=0 LogonSid=S-1-5-5-0-104548316 User=NT AUTHORITY\SYSTEM
07.12.2017 15:08:52.020 0000000000002AA4 WaitId=220 Product=0 (TEST)
07.12.2017 15:08:56.907 00000000000012FC runnerWait timeout
07.12.2017 15:08:56.907 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:01.908 00000000000012FC runnerWait timeout
07.12.2017 15:09:01.908 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:06.909 00000000000012FC runnerWait timeout
07.12.2017 15:09:06.909 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:11.909 00000000000012FC runnerWait timeout
07.12.2017 15:09:11.909 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:16.909 00000000000012FC runnerWait timeout
07.12.2017 15:09:16.909 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:21.910 00000000000012FC runnerWait timeout
07.12.2017 15:09:21.910 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:26.910 00000000000012FC runnerWait timeout
07.12.2017 15:09:26.910 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:31.911 00000000000012FC runnerWait timeout
07.12.2017 15:09:31.911 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:36.911 00000000000012FC runnerWait timeout
07.12.2017 15:09:36.911 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:41.911 00000000000012FC runnerWait timeout
07.12.2017 15:09:41.911 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:46.912 00000000000012FC runnerWait timeout
07.12.2017 15:09:46.912 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:51.913 00000000000012FC runnerWait timeout
07.12.2017 15:09:51.913 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:09:56.913 00000000000012FC runnerWait timeout
07.12.2017 15:09:56.913 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:01.914 00000000000012FC runnerWait timeout
07.12.2017 15:10:01.914 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:06.914 00000000000012FC runnerWait timeout
07.12.2017 15:10:06.914 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:11.915 00000000000012FC runnerWait timeout
07.12.2017 15:10:11.915 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:16.915 00000000000012FC runnerWait timeout
07.12.2017 15:10:16.915 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:21.916 00000000000012FC runnerWait timeout
07.12.2017 15:10:21.916 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:26.917 00000000000012FC runnerWait timeout
07.12.2017 15:10:26.917 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:31.918 00000000000012FC runnerWait timeout
07.12.2017 15:10:31.918 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:36.919 00000000000012FC runnerWait timeout
07.12.2017 15:10:36.919 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:41.920 00000000000012FC runnerWait timeout
07.12.2017 15:10:41.920 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:46.921 00000000000012FC runnerWait timeout
07.12.2017 15:10:46.921 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:51.932 00000000000012FC runnerWait timeout
07.12.2017 15:10:51.932 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:10:56.932 00000000000012FC runnerWait timeout
07.12.2017 15:10:56.932 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:11:01.932 00000000000012FC runnerWait timeout
07.12.2017 15:11:01.932 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:11:06.933 00000000000012FC runnerWait timeout
07.12.2017 15:11:06.933 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:11:08.527 00000000000014F0 API Entry: OP=SET_EXIT_ERROR_NOT_RETRY_FLAG Ver=4 Misc=0 Id=15200 IntUser=0 LogonSid=S-1-5-5-0-104548316 User=NT AUTHORITY\SYSTEM
07.12.2017 15:11:08.527 00000000000014F0 API Reply: OP=SET_EXIT_ERROR_NOT_RETRY_FLAG Ver=4 Status=0 Misc=0 Id=15200
07.12.2017 15:11:08.527 00000000000014F0 API Entry: OP=STOP_WAIT_CHANGES Ver=4 Misc=0 Id=220 IntUser=0 LogonSid=S-1-5-5-0-104548316 User=NT AUTHORITY\SYSTEM
07.12.2017 15:11:08.527 00000000000014F0 API Reply: OP=STOP_WAIT_CHANGES Ver=4 Status=0 Misc=0 Id=220
07.12.2017 15:11:08.527 0000000000002AA4 API Reply: OP=WAIT_CHANGES_EX Ver=4 Status=1223 Task=0-0 Result=0(?) Extra=0
07.12.2017 15:11:08.527 0000000000002AA4 API Entry: OP=DELETE_TASK Ver=4 Misc=0 Id=2 IntUser=2 LogonSid=S-1-5-5-0-104548316 User=NT AUTHORITY\SYSTEM
07.12.2017 15:11:08.527 0000000000002AA4 API Reply: OP=DELETE_TASK Ver=4 Status=0 Misc=0 Id=2
07.12.2017 15:11:11.933 00000000000012FC runnerWait timeout
07.12.2017 15:11:11.933 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:11:16.934 00000000000012FC runnerWait timeout
07.12.2017 15:11:16.934 00000000000012FC runnerIsIdle=1 running=1 waiting=0 doWait=1
07.12.2017 15:11:21.934 00000000000012FC runnerWait timeout

Both before and after, the entries you see looping repeat(ed) many times.  Obviously this is from the Schedul2 log.  Is there any information I may provide which might help?  Personally, I'm at the point where my troubleshooting knowledge and understanding of how this program is further written ends.

Seeing as this issue would likely apply to any version of Acronis, it would be great if it can at least be looked into :/.  I feel like a dev should definitely have a clue as to what might be affecting this, given the provided information.

 

PS- I can't find how to isolate it with the scrollbar the way you did.  It's what I initially was looking for as well.  Putting it in quotes doesn't work >.<

Legend
Posts: 31
Comments: 11278

Top

The further log data shows two specific Acronis tasks 1-2 and 1-7 where the latter looks to be your 'On Event of shutdown/restart' task:

07.12.2017 15:08:51.864 00000000000012FC Trying task 1-7 as SHUTDOWN

I don't see any exit entry for task 1-7 but the log only covers till 15:11.21 (2.5 minutes) for the snippet shown, so can't confirm or deny that the task had registered in the log as having finished and what exit error code value was given.

As I stated early on in this discussion, there is a bug with ATI 2018 that I have an open Support Case for, which prevents any task running 'On Event of shutdown/restart' - they just get killed off within the 2 minute timeout windows!  The developers will not look at unsupported versions.

To get the output as mine was, change the formatting from Normal to be Formatted instead.

2017-12-08 15_02_24.png

In reply to by Steve Smith

Beginner
Posts: 1
Comments: 5

Top

It was only 2.5 minutes because there wasn't anything after besides the same loop of the lines I already showed.  Maybe it is Acronis then in that it fails to make a shutdown request?  Not really sure then.. :/

Also, I understand that they're no longer supporting "2016", but this isn't so much a "2016" issue, as I haven't found it doing this before on other machines, so much as it is an Acronis issue when paired with certain computers.  I would wager that it's in conflict with something, as any version I'd install here would be.

In any case, I'm guessing there aren't any guesses as to what I may try to do for getting this resolved?

Thanks, I appreciate your time!