Centralized Vault issue
Hello,
Please give me a hint regarding this kind of issue (for policy reasons I renamed the Machine and Vault name).
What is interesting is that we can do backups but we can't delete them.
Thanks,
Hello Ekaterina,
Thank you for your support.
I just did the tasks.
Logs attached.
Do I miss something?
Hello Ekaterina,
Meanwhile I try to create another centralized vault (I did a backup), and when I try to delete it...please take a look on the log:
Managed entity type: [None]
Managed entity: [None]
Machine: server.domain
Code: 20.250.685(0x135003D)
Module: 309
Owner:
Message:
Command 'Deleting archives' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c9510
Fields: $module : management_server_vs_43994
Message: Command 'Deleting archives' has failed.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb8195ff
Fields: TraceLevel : 1, $module : archive_manager_plugin_vs_43994
Message: TOL: Failed to execute the command. The 'Deleting archives' command deletes the specified backup archives.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb8195ff
Fields: TraceLevel : 1, $module : management_server_vs_43994
Message: TOL: Failed to execute the command. TOL isolation command.
--------------------
Error code: 11
Module: 300
LineInfo: 2a46340236902166
Fields: $module : management_server_vs_43994
Message: Failed to connect to the process.
--------------------
Error code: 12
Module: 300
LineInfo: 2a46340236902167
Fields: $module : management_server_vs_43994
Message: The operation has timed out.
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/
Event code: 0x0135003D+0x01350016+0x01350016+0x012C000B+0x012C000C
--------------------
The difference is that here I got some logs compared with the first one where I just have an "Operation Progress--Processing, please wait" window hanging forever when I try to delete a backup from the Management Console.
Thanks for your help,
Hello Remy,
This error means pretty much what it says: our product couldn't access the required service and after a set amount of time, stopped trying and failed.
The timeouts can be raised and in certain cases this is the solution. For example, when creating backups of a large number of disks, there can be timeout because it takes longer than usual to scan/snapshot them.
In your case, there is no reason I can see for a timeout. In fact, this is the first time I've ever seen this error in this context (for the AMS service when deleting archives).
This suggests to me that something is blocking access. Usually, this would be an anti-virus or something like that, but I can't really say without an investigation. It's worth a shot to try and disable it as a possible solution in any case. Also, check the Windows event logs for something suspicious.
Hello Ekaterina,
Hello Igor,
I finally managed the situation...Thanks for your support!
The issue was caused by a mismatch of the account under which the component's service run.