Internal error when configure Azure Site Recovery appliance

Maximiliano Marín Bustos 0 Reputation points
2025-04-02T20:08:44.51+00:00

Hi All:
I am trying to register my ASR appliance for a physical server protection.
The software was correctly installed, but when I try to register with recover services vault, I get a generic error message:

The operation failed due to an internal error.

The only error message I found in event viewer is this one:

Exception Info: Microsoft.Azure.FDS.ServiceContract.AgentException: An invalid parameter AgentAuthenticationSpn:TenantId was passed.

at Microsoft.AzureMigrate.Appliance.Utils.Validate.ReturnIfNotEmptyString(String argumentValue, String argumentName) in C:__w\1\s\Core\src\Utils\Utility\Validate.cs:line 57

Any help will be appreciated.

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
791 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Srinivasa Reddy Jaggavarapu 625 Reputation points Microsoft External Staff
    2025-04-04T06:38:26.4566667+00:00

    Hi Maximiliano Marín Bustos,

    It seems you are facing issue with registering your Azure Site Recovery (ASR) appliance for protecting physical servers. Based on the error message you provided, it looks like the registration is failing due to an internal error related to incorrect parameters being passed during authentication.

    Make sure that the Tenant ID being used is correct. The error message indicates that an invalid parameter for AgentAuthenticationSpn:TenantId was passed. Double-check the Tenant ID in your configuration.

    Check the Azure user account used for registration has the necessary permissions to register the appliance with the recovery services vault.

    Look into the logs located in the %ProgramData%\\ASRLogs folder for any additional error messages that may provide more context on the failure.

    Ensure that the system clock on your appliance is synchronized and not more than 15 minutes off from the local time, as time discrepancies can lead to authentication issues.

    If the above steps do not resolve the issue, consider reinstalling the ASR appliance and ensuring that all parameters are correctly configured during the setup.

    Refer to the following Microsoft documentation link:

    https://learn.microsoft.com/en-us/azure/site-recovery/physical-azure-set-up-source#common-issues

    Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.