Salta al contenuto principale

ProtectCommand: Failed to execute the command

Thread needs solution

Backup fails with the message below. It always makes it to 5%. I have this happening on several machines. I also have the exact same config on other machines that work fine.
==========================================================
ProtectCommand: Failed to execute the command.
Additional info:
--------------------
Error code: 41
Module: 307
LineInfo: e6792a5ee190dd9e
Fields: $module : agent_protection_addon_vs
Message: ProtectCommand: Failed to execute the command.
--------------------
Error code: 1
Module: 149
LineInfo: 15b308bfdeeeb9e
Fields: $module : disk_bundle_vs
Message: Invalid parameters were specified.
--------------------
==========================================================
Acronis Backup & Recovery 11 Agent Core version=11.0 build=17437
==========================================================

0 Users found this helpful

Hello William,

Thank you for your post,

I will be more than glad to help you to resolve the problem.

To begin with, can you provide more details on the way how you conduct the backups on the affected machines?

Specifically:

1. What are the settings for the backup plans? If possible provide screenshots of the settings.

2. Were the backup plans created locally on each agent or they were created on AMS (centralized backup plans)?

3. What is the history of product or build installation on the affected machines?

4. Also, please try to:

a.) If machines is added to AMS, and the backup plan is centralized, then remove machine from the AMS. If not, proceed with step "b"

b.) On the affected machine - Issue "task zap" command in Acronis Scheduler Manager, to clean the tasks from Acronis Scheduler service. More information on that here.

c.) On the affected machine - Navigate to "C:\ProgramData\Acronis\BackupAndRecovery\MMS\TasksStorage" and delete all files which are located there. These will be task scripts, which also require cleaning.

d.) If machine was added to AMS, and the backup plan was centralized, add the machine back to AMS, wait for the backup plan to be deployed and check whether the issue is resolved. If machine was not a part of AMS, and backup plan was local - recreate the backup plan, and check whether the issue is resolved.

I will be looking forward to your answers.

1) screenshots are attached
2) Locally on each agent
3) build 11.0.17437
a) not relevant
b) done
c) done
d) not relevant

After the task zap there was a file in the taskstorage directory. I removed it. I then opened the console and logged onto this machine and there was still a task there. I removed it and created a new one.

After all this same problem still happens.

Allegato Dimensione
105886-102334.zip 124.42 KB
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 7
Commenti: 166

 Hello William,

thank you for your reply and the information you provided. I will be glad to help you further with this issue.

As you have completely recreated the task and it still gives the same error, it is not likely the issue is with the scheduler, but with other backup settings. The only setting you have kept from from the old task is the personal vault you are using on the hidden share. Please check if the issue persists when you delete the vault and create it anew.

If the issue persists, please check the backups to a newly created personal vault:

  • locally on the machine
  • on a non hidden share
  • on a new hidden share

I will be happy to answer any other question you should have.

I changed the destination to a different hidden share and it worked. The only difference between the two was the name of the share. NTFS and Sharing permissions were the same. I guess for the time being I am all set. Thanks.

I recently upgraded Acronis ABR 11 to 11.5 and have the same error occuring when trying to backup my own local drive to an external USB hard drive. I found Acronis Knowledge Base Article 41292 created April 9 2013and followed the "Solution" instructions. However this did not solve the problem. I noted in the Solution notes the text . . . . "Now all freshly created backup plans will run flawlessly", such a brave and bold statement to make especially when the solution did not solve the problem! As commented by some of the previous posts here, the backup starts and runs for about 10-15 seconds and gets to about 5% completed then fails.