Folgende Fehlermeldung wird genau um 04.00 Uhr generiert (Windows-Applikationslog):

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

  <Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />

  <EventID Qualifiers="0">513</EventID>

  <Version>0</Version>

  <Level>2</Level>

  <Task>0</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8080000000000000</Keywords>

  <TimeCreated SystemTime="2016-06-09T02:00:10.534410800Z" />

  <EventRecordID>11099</EventRecordID>

  <Correlation />

  <Execution ProcessID="1560" ThreadID="1652" />

  <Channel>Application</Channel>

  <Computer>PC</Computer>

  <Security />

  </System>

<EventData>

  <Data>Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft-Verbindungsschichterkennungsprotokoll. System Error: Zugriff verweigert</Data>

  </EventData>

  </Event>

Hi Merlin,

There's a bit of information lost in translation from Google translate here.  You may want to post in the German thread as well for some additional help.  It seems like your previously working scheduled task that is set to run at 0400 is no longer working correctly, but after a reboot, it will then run at log on as it is a missed task... is that correct?

There could be an issue of the system not waking up (if it is asleep or hibernating at that time of day).  Why that would have changed on your system, I cannot say.  Take a look at this thread with a similar issue.  The user created a scheduled task in Windows (not Acronis), to wake the system up a few minutes before the Acronis scheduled task and that worked for him:  https://forum.acronis.com/forum/115265

This may be another solution/option to look into as well:  https://forum.acronis.com/forum/117622  .  "In Windows advanced power options I set wake timers from "enabled" to "Only important wake timers" and than switched it back to "enabled"."  Apparently, something in those settings was being ignored by Windows, but changing it, saving it and changing it back forced the correct behavior again. 

FYI, I also get those CAPI errors and they seem to be common when VSS is being called upon.  

You can disable VSS for backups and have it revert to the Acronis SNAPAPI backup method which was the default in versions before 2015 as well.  If VSS is the issue on the machine, this should work just fine.  The only downside is that VSS is needed to backup SQL and Oracle databases that are actively in use.  If you don't have any (which I suspect most home users don't), then disabling VSS in your backup task should be just fine. 

Disable VSS 3 different ways

Option 1 would be the most ideal since it only disables VSS for a particular backup task and is pretty easy to implement. 

hi

thanks very much for your help. yes, it is correct the backup jobs do not work anymore after around 5 days. when i do restart the computer, all is fine again for about another 5 days. i do not use hybernate or others, the computer is running 7/24.

and vss is disabled all the time. as i did read the thread about vss, i did recognize that i do not have any script folders at C:\Program Files (x86)\Acronis\TrueImageHome.

what can i do, it is very strange that it is working for about 5 days. when i restart all processes before the job will run, then it works. but this is not a real solution for me.

thanks again for the help.

Hi Merlin, the scripts are not in program files, but the hidden folder "programdata"

C:\programdata\Acronis\TrueImageHome.

If the backup runs afters a reboot and continues to run for a few days OK, I am wondering if something else may be killing a background service like VSS or somethign else at times - Windows updates/patches perhaps.  I'ts really hard to say at this point.  If VSS is completely disabled on the machine, then it's probably already using the SNAPAPI backup method, but worth trying with the script change anyway.  

Worse case scenario, you could download the full installer from your account and right click and "run as administrator" and attempt to repair the application.  If you have upgraded the OS before with Acronis installed at that time, or if you have upgraded Acronis several times on top of itself, sometimes, removing it completely with the clean tool (see below for the link in this post), rebooting, and then installing with the full download from your account and running with "run as administrator" can help ensure that any issues with the application are fixed.  

Unfortunately, I can't say if it's Acronis or your system at this time, since it does seem to be working for a few days and then is stopping at some point in time. 

thank you very much for supporting me. i will go on like you did say with the scripts.

i will post the results - hopefully with success :)

ok, after 5 days, it did stop again with running the scheduled tasks. i did stop the scheduler service and started it again, then i was able to run the task again. so there must be something with the scheduler service i guess.

can i run this scripts also as normal windows scheduling task? if so, how would i do this?

thanks a lot for helping me out of that misery :)

ok, i did the worst case szenario. i did delete the program, then i did run the cleanup tool, i did check the registry entries. then i did restart computer, then i did update windows (was an update outstanding, new one). i did install - with admin rights - acronis again. i did all jobs new.

so i hope now, all good. but i have a feeling that this will not work. because i did this all already once, but without cleanup tool. so lets hope.

Fingers crossed!  Seems to be strange indeed that it was running for a few days and would stop.  I hope the clean install will resolve it too. 

If not, the next step would be to run the schedulemanager tool.  There may be leftover hidden scheduled tasks from past installs or upgrades.  If the problem comes back, you can kill indvidual tasks or run taskzap to kill them which will get rid of all current and possibly hidden/old tasks that may be conflicting if they somehow still exist after the cleanup.  Hopefully though, the cleanup did the trick.

1859: Acronis Scheduler Manager

thank you very much!

Merlin, if the problem will re-occur, I advise you to submit a support ticket at http://www.acronis.com/support/contact-us.html. If your license is not subscription-based and 30-days period after product purchase is over, you would need to pay a small fee which would be refunded later, if we will discover that the problem with backups was caused by an issue with the program itself.

Regards,

Slava

thanks Slava, i will do so because it happend again - but first i will try to restart the scheduler in front of the backup job. if this doesnt work, i will make a ticket as you did describe above.

thanks again.

Regards

so it seems to be working now, but only whith this batch file running in front of the backup scheduled tast (10 mins befor backup starts):

Net stop AcrSch2Svc

timeout 10 /nobreak

taskkill /F /IM TrueImageHomeService.exe /T
taskkill /F /IM TrueImageHomeNotify.exe /T

Net start AcrSch2Svc

for me it looks like your scheduler has a problem.

i will post in a week if this is still working with that workaround.

ok, i can confirm now that this workaround is fine. the jobs are done as planed. but when i reboot the computer, all scheduled jobs do run for once in serial mode. when 1st job is done, the 2nd is starting and so on.

i can live with that, but if you could fix that it would be good.

thanks for supporting me in that case.

so all is working fine, until i try to restore a file. i do start the program to do so, all good so far. i can restore the file without any problem. but the scheduler isn't working after this.

you really should try to fix this please. for sure not a windows problem.

thanks a lot.