Authorization failure. Cannot access centralized vaults from Management Server

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 2

This problem cropped up when I had to change the managed vault's share path. Both my storage vaults are stored on my NAS and are accessed via SMB/Windows File Sharing. Since I could not directly edit the vault's path, I had to detach the two vaults first. When I re-attached both vaults, I did so using the correct and current storage vault path. I DID NOT change any access credentials. Now I cannot access the vaults via the Management Server Console.

I've validated share permissions all along the storage vault path. I've also validated the file level permissions on the Linux NAS via a console login. All Linux directories and files are set correctly.

Here is the error details. Again, please note that I DID NOT change any credentials when attaching the vault.

Code: 262,164(0x40014)
LineInfo: 0x9A79E68F0ADD71BB;

Module: trueimg_remote_full_vs
Message: Authorization has failed. Access to 'Studio Vault' has been denied.

Code: 262,164(0x40014)
LineInfo: 0x9A79F20828BC7EE;

Module: archive_manager_plugin_vs
Message: Access is denied.

Code: 2,555,969(0x270041)
LineInfo: 0xAF0695FA9D426E1E;

Module: storage_server_vsa64
Message: Failed to obtain statistics of vault 'arl:/F552751E-1635-48FC-8B8E-2AA9F8A99C12/8990F574-3C3B-4C26-831F-37BE13DDB6C1'.

Code: 4,194,350(0x40002E)
LineInfo: 0x97675718D2B52D19;

Module: storage_server_vsa64
Message: Failed to open the backup location.

Code: 262,164(0x40014)
LineInfo: 0xF35F747B3B21FB55;

Module: storage_server_vsa64
Message: Access to the file is denied.

Code: 65,520(0xFFF0)
LineInfo: 0xBD28FDBD64EDB8E0;

Module: storage_server_vsa64
Message: Logon failure: unknown user name or bad password

Thu, 04/26/2012 - 22:08
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Dave,

Welcome to our Forum, we're glad to greet you here.

It's hard to say for sure what went wrong, we'll need additional logs to find out the exact cause. But before we proceed with the investigation, I would recommend you to try the following workaround: 

re-add the ASN to AMS, and check, whether the issue remains. If it's present, then, please, gather Acronis Info, submit a case with the information attached, and let us know its number.

If you have any additional concerns or questions - share them with us, we will be glad to help.

Thank you.

Fri, 04/27/2012 - 09:59
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 2

I did as your suggested regarding the storage node. Access now looks good in the Management Server. However, when I access the centralized vaults via the Management Console in order to run local backup plans on the Management Server, the access error is still there, albeit with different error codes.

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: 11
Module: 373
LineInfo: dfd7515541030d07
Fields: $module : staging_command_addon_vs
Message: Failed to resolve the secondary location. Location: 'arl:/F552751E-1635-48FC-8B8E-2AA9F8A99C12/5CC87707-FE6F-4E2D-9885-625A7F9ADEC8'; Archive: 'Win7'.
--------------------
Error code: 67
Module: 39
LineInfo: 19dd9920ed7240f7
Fields: IsReturnCode : 1, $module : disk_bundle_vs
Message: Cannot create archive '' in vault 'arl:/F552751E-1635-48FC-8B8E-2AA9F8A99C12/5CC87707-FE6F-4E2D-9885-625A7F9ADEC8'.
--------------------
Error code: 67
Module: 39
LineInfo: 19dd9920ed7240f7
Fields: $module : storage_server_vsa64
Message: Cannot create archive '' in vault 'arl:/F552751E-1635-48FC-8B8E-2AA9F8A99C12/5CC87707-FE6F-4E2D-9885-625A7F9ADEC8'.
--------------------
Error code: 13
Module: 39
LineInfo: 5a99bb5a00cb1b1d
Fields: $module : storage_server_vsa64
Message: Error occurred while performing operations with vault database 'C:\ProgramData\Acronis\BackupAndRecovery\ASN\VaultMetadataDatabases\5CC87707-FE6F-4E2D-9885-625A7F9ADEC8_l.fdb'.
--------------------
Error code: 1
Module: 42
LineInfo: 15c2740d0c179c33
Fields: $module : storage_server_vsa64
Message: violation of PRIMARY or UNIQUE KEY constraint "OWNER_COMPUTER_UNIQUE" on table "ARCHIVE"; (1, 335544665); (2, 'OWNER_COMPUTER_UNIQUE'); (2, 'ARCHIVE')
--------------------

I ran the AcronisInfo command to help generate a case. Alas, the program produced an AcronisInfo.zip file near 2 GB in size. Methinx that's a bit excessive. The website instructed me not to upload anything larger than 5 MB, so I must be doing something wrong in its creation. So I didn't submit the file with the case sent via email. I've yet to receive an acknowledgement or a case number.

----dave

Fri, 04/27/2012 - 21:09