TI2016 Backups gone bezerk - Daily backup jobs keep executing over and over

What do the actual Acronis service logs show for why the backup task kept repeating itself?

See the link for the Log File Viewer app in my signature if needed.

This is normally caused by the Acronis Advanced Error handling options which by default are set to repeat after x Seconds but which are not processed correctly in ATIH 2016 causing the repetition to run continuously.

Normally the Windows Event logs would stop the Acronis task from running at all, so may be a separate issue.

I would recommend doing a reinstall of ATIH 2016 over the top of what you already have to see if that resolves the Event log issue, but sort out the other issue first.

That Capi error shows up a lot anytime VSS is used.  Your Acronis Service log may show more details that would help.  It looks like VSS (windows service - not Acronis) is not able to get access to files that it needs:

System Error:
Access is denied.

Without more details from your logs, we can only guess.   You could try disabling VSS for your backup task and letting it revert to the ACronis Snapapi backup method (Snapapi was the only method in 2014 and earlier - VSS became the first method in 2015 and later) and see if that would allow the backup to continue running.  Hard to say if it's really VSS or not at this point though.

https://forum.acronis.com/forum/45832#comment-346558

It is also possible to disable VSS usage for a particular backup task without touching Windows VSS service itself:

1) open the folder where your backups settings are saved: C:\ProgramData\Acronis\TrueImageHome\Scripts

2) each file there stores settings for particular backup job. Open files one-by-one in Notepad, or open latest modified file (if you have just modified your task), until you find the one that has backup name on 5th line, e.g. MyBackups

3) click Edit - Replace and replace use_vss="true" with use_vss="false"

4) save changes and close the file

Thanks for your input, and the log viewer.  I viewed a series of logs and all are pretty much the same, basically as follows:

id=9;  level=2;  module=100;  code=0;  date/time=8/27/2016 1:49:24 PM
          message=The following backups have been successfully created: R:\Drive-E\Drive-E-Daily_full_b131_s1_v1.tib
id=10;  level=2;  module=316;  code=6;  date/time=8/27/2016 1:49:24 PM
          message=Operation has succeeded.
Start= 8/27/2016 1:26:18 PM
Finish= 8/27/2016 1:49:24 PM
Total Time= 00:23:06

They all seem to be successful but for some reason the backups just keep rerunning.  It appears that the CAPI event log errors occur first and then the TI event log error.  I simply cannot understand how this just materialized when no updates have been installed since earlier in August.

BTW, when I download the log viewer I noticed a TIB mount utility.  What is it  used for?

Thanks again...

The Tib Mount zip contains a patch to fix a know problem where some users were unable to mount .TIB files via Windows Explorer.

I would suggest creating an Acronis System Report zip file and posting to the forum then we can take a better look at what is happening?  

Thank you for your reply.  I will try the vss="false" change you suggested.

Looking at a number of the logs shows no errors.  Here is a sample from one job that had run numerous times, for no apparant reason:

log uuid=0FA2DE6D-A655-45B1-9FC2-1E43214091D2;  product=True Image;  version=19.0;  build=6571;  task=4834DFD3-F9AE-4BC5-AFD9-7F61D422AC59;  task_name=Drive-E-Daily
Start= 8/27/2016 1:26:18 PM
id=1;  level=2;  module=100;  code=0;  date/time=8/27/2016 1:26:18 PM
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2;  level=2;  module=100;  code=2;  date/time=8/27/2016 1:26:18 PM
          message=Operation Drive-E-Daily started by schedule.
id=3;  level=2;  module=100;  code=0;  date/time=8/27/2016 1:26:21 PM
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=4;  level=2;  module=316;  code=0;  date/time=8/27/2016 1:26:21 PM
          message=Operation: Backup
id=5;  level=2;  module=11;  code=1008;  date/time=8/27/2016 1:26:21 PM
          message=Create Backup Archive From: DATA (E:) To file: R:\Drive-E\Drive-E-Daily_inc_b130_s7_v1.tib Compression: Normal Exclude: Files matching mask Match criterion:
          pagefile.sys
          $Recycle.Bin
          System Volume Information
          *.tib
          *.tib.metadata
          *.~
          *.tmp
          *.db3-journal
          E:\Downloads\
id=6;  level=2;  module=1;  code=504;  date/time=8/27/2016 1:26:21 PM
          message=Pending operation 172 started: 'Creating volume image'.
id=7;  level=2;  module=100;  code=0;  date/time=8/27/2016 1:27:14 PM
          message=Writing full version to file: Drive-E-Daily_full_b131_s1_v1.tib
id=8;  level=2;  module=1;  code=504;  date/time=8/27/2016 1:49:24 PM
          message=Pending operation 172 started: 'Creating volume image'.
id=9;  level=2;  module=100;  code=0;  date/time=8/27/2016 1:49:24 PM
          message=The following backups have been successfully created: R:\Drive-E\Drive-E-Daily_full_b131_s1_v1.tib
id=10;  level=2;  module=316;  code=6;  date/time=8/27/2016 1:49:24 PM
          message=Operation has succeeded.
Start= 8/27/2016 1:26:18 PM
Finish= 8/27/2016 1:49:24 PM
Total Time= 00:23:06

I did change the script settings to vss="false" and ran one of the smaller backup jobs manually.  The log file shows the operation succeeded, no errors, but the Acronis screen shows "The last backup has failed."  Here is the TI log:

log uuid=A9DF6B96-4240-457E-803E-6631CD187A89;  product=True Image;  version=19.0;  build=6571;  task=A0659C74-CE77-4117-9CC6-6A4E7C73E604;  task_name=Drive-G-Vault Daily
Start= 8/30/2016 2:22:17 PM
id=1;  level=2;  module=100;  code=0;  date/time=8/30/2016 2:22:17 PM
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2;  level=2;  module=100;  code=2;  date/time=8/30/2016 2:22:17 PM
          message=Operation Drive-G-Vault Daily started manually.
id=3;  level=2;  module=100;  code=0;  date/time=8/30/2016 2:22:20 PM
          message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=4;  level=2;  module=316;  code=0;  date/time=8/30/2016 2:22:20 PM
          message=Operation: Backup
id=5;  level=2;  module=11;  code=1008;  date/time=8/30/2016 2:22:20 PM
          message=Create Backup Archive From: G:\JGT.bvd  To file: Drive-G-Vault-Daily-Backup_full_b659_s1_v1.tib Compression: Normal Exclude: System files  
id=6;  level=2;  module=100;  code=0;  date/time=8/30/2016 2:22:21 PM
          message=Writing full version to file: Drive-G-Vault-Daily-Backup_full_b659_s1_v1.tib
id=7;  level=2;  module=100;  code=0;  date/time=8/30/2016 2:22:39 PM
          message=The following backups have been successfully created: R:\Vault\Drive-G-Vault-Daily-Backup_full_b659_s1_v1.tib
id=8;  level=2;  module=11;  code=1026;  date/time=8/30/2016 2:22:39 PM
          message=Validate Backup Archive Location: R:\Vault\Drive-G-Vault-Daily-Backup_full_b659_s1_v1.tib  
id=9;  level=2;  module=316;  code=6;  date/time=8/30/2016 2:22:48 PM
          message=Operation has succeeded.
Start= 8/30/2016 2:22:17 PM
Finish= 8/30/2016 2:22:48 PM
Total Time= 00:00:31

The Windows Application event log shows : (no CAPI errors logged)

Log Name:      Application
Source:        Application Error
Date:          8/30/2016 2:24:09 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      JGT-Custom-PC
Description:
Faulting application name: TrueImageHomeNotify.exe, version: 19.0.0.6571, time stamp: 0x5731e638
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
Exception code: 0xc0000409
Fault offset: 0x000a7666
Faulting process id: 0x2204
Faulting application start time: 0x01d2030495b2d7a1
Faulting application path: C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeNotify.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll
Report Id: cf04d88f-00ac-40ac-b347-a4dc28573997
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-08-30T21:24:09.915969000Z" />
    <EventRecordID>7277</EventRecordID>
    <Channel>Application</Channel>
    <Computer>JGT-Custom-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>TrueImageHomeNotify.exe</Data>
    <Data>19.0.0.6571</Data>
    <Data>5731e638</Data>
    <Data>MSVCR120.dll</Data>
    <Data>12.0.21005.1</Data>
    <Data>524f7ce6</Data>
    <Data>c0000409</Data>
    <Data>000a7666</Data>
    <Data>2204</Data>
    <Data>01d2030495b2d7a1</Data>
    <Data>C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeNotify.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\MSVCR120.dll</Data>
    <Data>cf04d88f-00ac-40ac-b347-a4dc28573997</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Okay Steve, I did create one Saturday after I discovered the problem.  I thought I would be able to send it to Acronis Support but I found no way to do so.  The Acronis System Report is attached.  Oops, apparently the file is too large to attach (21.66MB) - probably because of the Windows Event logs.  Do you want me to clear the event logs and rerun the System Report?

The max file size for attachments is 20MB.  If you clear the Windows Event logs, then retry one of your backups again so that it will log any messages for the cleared event logs.  Also check the size of the Monitor.log file in C:\ProgramData\Acronis\TrueImageHome\Logs as this can also grow to very large sizes.

When I had tried to upload the file the error message said the limit was 15MB.  I'll clear my Windows event logs and then run a small backup (which indicates it fails, but the operations is successful), and then I'll run the ASR again.

I have this exact problem, running TI2016, Build 6185, on window 10.  Was there ever a solution to this issue. 

Interactions between

Faulting application path: C:\Program Files (x86)\Common Files\Acronis\TrueImageHome\TrueImageHomeNotify.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll

Thank You..

VanZan, welcome to these user forums.

If you are running ATIH 2016 build 6185 then you are a long way back from the latest build version 6581.

I would recommend downloading the full build 6581 installer from your Acronis account, then doing a clean install of this as follows:

Perform a normal uninstall of the current ATIH software, then download the Acronis Cleanup Tool from the link in my signature below.  Run this as Administrator and remove any residual data then do a restart to complete the action.
Note: The cleanup tool will remove all your backup tasks and task history, plus also remove Acronis Disk Director if installed.  You can backup your task configuration by saving a copy of the C:\ProgramData\Acronis\TrueImageHome\Scripts folder before doing the uninstall.

Sorry that was a typo, I am running the most current version.  When I updated to it I was hoping it would resolve the issue, but it did not. I was trying to avoid the fresh install, as it appears the backups are taking place, just the gui says it failed.  I will perform the steps you've suggested and let you know.. Thanks for the help..

If memory serves, I corrected several issues noted in the Windows System Log, but that alsone did not address my Acronis problem (still, it can't hurt to eliminate log errors).  Then I decided to get rid of my Acronis install and do a clean install of the same (then current) build.  Before doing so I saved all of the Acronis Backup Script files (for my backups).  After the clean install I copied the saved Scripts back to the Acronis folder where they are normally stored.

When I started Acronis TI for the first time it recognized the scripts and I was able to perform my 'normal' backups without any further errors.  It has worked as expected until I just recently updated to the 'latest' build.  Now Acronis decides on its own which of my three daily backup jobs it will run each night, I kid you not.  Some nights it runs one of them, some nights 2, but no longer does it run the 3 that are scheduled; no errors, and no time conflicts.  I even modified each Backup so that it would resave the script, just in case something got 'corrupted' - no help.  I guess I'll have to wait until the next build, unless the fix is in the 2017 version which I may be forced to purchase! 

If you have scheduled jobs that are misbehaving, then use the Acronis Scheduler Manager (link below in my signature) and use this to clean out all the existing scheduled task and then make a clean start by going back into your tasks and configuring your schedule again to create the new entries the Scheduler will follow.

Thanks for the advice Steve, I'll give it a shot.  I was planning to do a clean install over the weekend.  

Much appreciated...

Since I had to reinstall, I uninstalled, cleaned the leftovers and installed 2017.  And of course it all works again, just wish those logs would provide why but at lleast I am back to backing up again..thx for the help..

VanZan, glad to hear your issues are resolved, thanks for feeding back, hope it all stays that way for a long long time.

I followed your instructions (thanks again for that).  The evening after I used the schedule manager to clean out the existing schedules, all 3 backups ran - that day and that day only.  Each evening after only 1 or 2 of the 3 daily jobs ran, and not always the same one(s)!  Another weekend and now I'm trying it once more.  If the problem recurrs I'm just going to blow everthing away and start over clean.

While I appreciate all of your efforts here in these forums, and your suggestions, I have to say that I'll really be ticked off if I have to buy/install 2017 to get things running correctly again.  Over the years I have spent a great deal of money and time on new releases for several machines (and for my clients) and now it has become not only tiresome, but infurating as well.

Regards...

AZMoosie, sorry to hear that problems are still continuing for you.  A clean install is probably the right next step to take - if you still encounter problems after that then please remember that all ATIH 2016 (& 2017) users now have upto 2 years of free support from date of purchase with the changes introduced after 2017 was released.

Appriciate that info, thanks again and have a Merry Christmas.

A Merry Christmas to you too!