Azure Backup internal error (ID: 130001)

Posted: May 16, 2016 |7 comments | Tags: , , , ,

Issue

When installing the Azure Backup-agent via the Register Server Wizard you need to supply your vault credentials. If doing so incorrectly you will get the following error:

Microsoft Azure Backup envountered an internal error. (ID: 130001)

Wait for a few minutes and then try the opration again. If the issue persists, please
contact Microsoft Support.

Solution

If the vault-file is located on a network share the wizard will fail.
So a pretty simple fix, move the vault-file to a local storage and try again.

7 Comments

  1. Art on 2016-06-27 at 03:02

    Thanks. Always amazes me that the community needs to work out MS's cryptic errors.

    Reply
    • ColinF on 2017-01-16 at 18:08

      I am also getting this error, but NOT when registering the server. Registration seems to have gone fine. Backups have been scheduled and running but I get this error when trying to restore files.
      If I browse I just get a generic internal error message. When I search for files to restore it gives this error code.

      Any ideas about what might be causing this? It's nice that the data is getting backed up but a bit useless if I can't actually restore files.

      Reply
      • Raymon on 2017-07-27 at 10:01

        Did you find a solution? i have the exact same problem

  3. Jeremy on 2019-07-05 at 21:39

    One thing to watch too is that if the Azure Backup Server installer fails after the MS Azure Recovery Services Agent was registered, it will try to install the MS Azure Recovery Services Agent again. This will fail to register because the server was already registered in Azure and the installer doesn't handle that situation properly even with valid vault credentials. My solution was to go into Azure and delete the server out of the Recovery Vault. Then rerun the installer again and it should register.

    Reply
  4. Jeremy on 2020-01-17 at 16:58

    THANK YOU JEREMY (cause Jeremy's ARE awesome)! This helped me with a problem I've spent hours trying to figure out. First MABs install failed at the very end. So created another vault and resource pool to try fresh. Couldn't figure out why the second attempt was failing at the agent registration. Searched everywhere and go figure, a comment saved the day. Thanks again for sharing insights!

    Jeremy

    Reply
  5. Sony on 2022-06-24 at 05:24

    I have tried this but I didn't get the result. I am trying but I couldn't resolve the issue. I am not understanding what to do further.

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *