Connection to the storage node x.x.x.x through port '{{ASNPort}}' failed
Hello,
After updating to the latest Cyber Protect Build we started getting the following error in some of the agent systems.
Error code: 48562277
Fields: {"$module":"asyncipc_vsa64_29486","Code":336134278}
Message: SocketError: error: 14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed
Kindly help me to resolve this issue.
Fichier attaché | Taille |
---|---|
MicrosoftTeams-image (1).png | 300.45 Ko |
MicrosoftTeams-image.png | 318.79 Ko |

- Se connecter pour poster des commentaires

Hello Packy Zhang!
I have the same problem and th kb that you recommended unfortunately didnt work. I removed a location and now cant readd, this is the error message: "There are more than one location metadata files. Keep only one location metadata file and retry the operation."
do you or anyone else have any ideas? None of our plans dont work after update...:-(
- Se connecter pour poster des commentaires

Lorinc Laboncz wrote:Hello Packy Zhang!
I have the same problem and th kb that you recommended unfortunately didnt work. I removed a location and now cant readd, this is the error message: "There are more than one location metadata files. Keep only one location metadata file and retry the operation."
do you or anyone else have any ideas? None of our plans dont work after update...:-(
Hi Lorinc,
The files in the .meta directory need attention. For error message - "There are more than one location metadata files. Keep only one location metadata file and retry the operation." It means that there are conflicting meta files of backup archive under .meta folder. You can try moving all meta files under the .meta folder to a different location, then refresh the location from the Acronis Cyber Protection Management Console --> Backup Location --> The specified ASN location, which will regenerate new metafiles of location.
In addition, If the first solution in https://kb.acronis.com/content/68671 didn't help, the stored certificate hash needs to be removed manually by Workaround 2. It should be executed on the client side, not on the management server or storage node.
In any case, You can open a ticket to Acronis Support Center for assistance if you still have active license maintenance.
- Se connecter pour poster des commentaires