Direkt zum Inhalt

Backup-Plan [Disk to ASZ] failed with Error "Operation canceled by user"

Thread needs solution

After update to the latest build 7641, my Plan for backup to ASZ fails now.

For analyze I tried a backup Disk to HDD -> works well:

image

My second Plan [Disk to ASZ] doesnt work now (as before update):

image

Why will this backup canceled by user? Who ist the "user" who canceled the operation? I don't cancel anything during backup!

If I start a new backup manually by acrocmd, it will be finished without any error:

image

I use the same parameters in Plan as in acrocmd. Why didn't work the plan, but a manually backup to ASZ works?

 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Siegfried,

Can you please post the full error message available from "Details" link on your screen shot? This error may mean some service_process.exe crash during backup (that's when it may give "Cancelled by user" message) and the details should show where the problem could be.

Thank you.

In reply to by truwrikodrorow…

Hi Vasily,

Thx for your response. I put the error message from details below.

 

 

------------------------
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"$module":"mms_vs_7641","CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB"}
Nachricht: TOL: Failed to execute the command. Backup plan 'Disk1_to_ASZ'
------------------------
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"$module":"agent_protection_addon_vs_7641","CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB"}
Nachricht: TOL: Failed to execute the command. Backup plan 'Disk1_to_ASZ'
------------------------
Fehlercode: 41
Modul: 307
Zeileninfo: 0xE6792A5EE190DE2C
Felder: {"$module":"agent_protection_addon_vs_7641"}
Nachricht: Failed to execute the command.
------------------------
Fehlercode: 53
Modul: 309
Zeileninfo: 0x2E7E9E174F1FB719
Felder: {"FailCount":"2","$module":"agent_protection_addon_vs_7641"}
Nachricht: 2 activities have not succeeded. One of them is displayed.

------------------------
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"$module":"service_process_vs_7641","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Nachricht: TOL: Failed to execute the command. Backing up
------------------------
Fehlercode: 22
Modul: 309
Zeileninfo: 0x8D165E86FB81959B
Felder: {"$module":"gtob_backup_command_addon_vs_7641","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Nachricht: TOL: Failed to execute the command. Backing up
------------------------
Fehlercode: 3
Modul: 143
Zeileninfo: 0x1CD98AAE889424F5
Felder: {"IsReturnCode":"1","$module":"disk_bundle_vs_7641"}
Nachricht: The running task has been canceled.
------------------------
Fehlercode: 1061
Modul: 1
Zeileninfo: 0xB43E776571144E10
Felder: {"$module":"disk_bundle_vs_7641"}
Nachricht:
------------------------
Fehlercode: 1060
Modul: 1
Zeileninfo: 0xB43E776571144DF0
Felder: {"$module":"disk_bundle_vs_7641"}
Nachricht: Failed to commit operations.
------------------------
Fehlercode: 34
Modul: 7
Zeileninfo: 0x2CBDD167CBCA9503
Felder: {"$module":"disk_bundle_vs_7641"}
Nachricht: Operation canceled by user.

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi,

Thank you for the full log, though I was unable to find any similar reports in our bug tracking system - the issue looks unique related to specific backup plan properties. I can suggest to try re-creating this specific backup plan for saving backups to Acronis Secure Zone (delete and create a new one) and if this doesn't help, then contact our support team for further assistance. Remember to collect Acronis system report from the affected machine before contacting.

Thank you.

Hi Vasily,

you point me to a potential source for this error! After posting the details for failed plan, I look inside the logfile (download protokoll) and there I found an interesting note:

2017-09-05T12:52:10:034+01:00 788 I000101F8: Pending operation 162 started: 'Saving partition structure (Hard disk 1)'.
2017-09-05T12:52:10:034+01:00 788 I000101F8: Pending operation 165 started: 'Creating partition image (EMERGENCY (C))'.
2017-09-05T12:52:10:034+01:00 788 I00640078: Starting the before-data-capture command: &#34;&#62;<h1/onmouseover='\u0061lert(1)'>%00.
2017-09-05T12:52:16:831+01:00 788 E000103F7: Failed to run a child process.
2017-09-05T12:52:16:847+01:00 788 E00010401: System error: '267'.
2017-09-05T12:52:16:847+01:00 788 E00640079: Failed to perform the before-data-capture command. Error code: 66,596.

So I'm wondering, what is the "before-data-capture command"? I haven't add it to the plan, so I look at the options:

image

That's it, this may be the source of troubles. Is this a new feature in build 7641? All my new created plan have checked this parameter and filled in with "&#34;&#62;<h1/onmouseover='\u0061lert(1)'>%00"

So I dissabled this optional parameters on each plan:

image

Now my plan "Disk to ASZ" run without Error!

I think, starting a manually plan with acrocmd to backup Disk to ASZ doesn't use this feature, thats the reason why manually backup to ASZ works, and each new plan (without unchecking before/after-data-capture command) will fail.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Siegfried,

The entries in pre/post commands settings seem to be somehow inserted by 3rd party factor - for example "mouseover" - looks like some automated string generated by some actions in browser, though I'm not sure here. It could also be generated during the backup plans update (after updating to latest build of Acronis Backup), but in either case it looks really weird and I see such entries for the first time. Definitely there should be no such entries in the backup options, so it's not an intended behavior. I will check with our developers what could be the potential cause, though it's unlikely that we'll be able to reproduce such problem locally which would make the investigation much more complex.

Thank you.

Hi Vasily,

I'm sorry, It's my fault, or more precisely the fault of our IT. Someone played arround on the Server and overwrote the global parameters/options, that causes the wrong parameter in some fields of each new plan.

It,s not the fault of Acronis, so I'm really sorry for the effort on your side.

 

Thank you Vasily for your support.

Sigi