The app registration was disabled. after enabling it. getting below error. Health of 'Re-protection server' on ASR replication appliance is critical as latest heartbeat is missing. 'Re-protection server' is unable to communicate with Site Recovery services in Azure. One or more required service principal (SPN) in Azure Active directory is no longer available. How to fix it?

Health of 'Re-protection server' on ASR replication appliance is critical as latest heartbeat is missing.

Kale, Ashish 0

The app registration was disabled. after enabling it. getting below error.

Health of 'Re-protection server' on ASR replication appliance is critical as latest heartbeat is missing.

'Re-protection server' is unable to communicate with Site Recovery services in Azure.
One or more required service principal (SPN) in Azure Active directory is no longer available.

How to fix it?

SadiqhAhmed-MSFT 45,671 Reputation points Microsoft Employee

2024-06-21T11:19:05.67+00:00
@Kale, Ashish Thank you for posting your query on the Microsoft Q&A platform. Happy to assist you!

From the description I understand that you noticed health critical alerts for re-protection server. It looks like you are experiencing an issue with the "Re-protection server" on your Azure Site Recovery (ASR) replication appliance. The error message indicates that the server is unable to communicate with Site Recovery services in Azure, and that one or more required service principal (SPN) in Azure Active Directory is no longer available.

Here are some steps you can take to troubleshoot this issue:

Check the status of the "Re-protection server" in the ASR portal. If the server is shown as "Critical", this indicates that there is a problem with the server or the connection to the server.

Check the network connectivity between the ASR replication appliance and the "Re-protection server". Make sure that the server is accessible from the replication appliance and that there are no network issues that could be causing the problem.

Check the Azure Active Directory (AAD) to ensure that the required service principal (SPN) is available. If the SPN is missing, you can create a new one by following the steps in the Microsoft documentation on Create an Azure AD application and service principal that can access resources.

Check the permissions of the SPN in Azure. Make sure that the SPN has the necessary permissions to access the Site Recovery services in Azure.

Restart the "Re-protection server" and see if this resolves the issue. If the server is a virtual machine, you can try restarting the VM. If the server is a physical machine, you can try restarting the server or the services that are responsible for the heartbeat.

If the issue persists, you may need to contact Azure support for assistance. You can submit a support case through the Azure portal and provide the error message and any other relevant information.

Hope this helps! Let me know if you have any other questions or if there is anything else I can assist you with.
Kale, Ashish 0 Reputation points

2024-06-21T12:14:01.7666667+00:00

Tried all steps, still no luck.
SadiqhAhmed-MSFT 45,671 Reputation points Microsoft Employee

2024-06-25T09:59:42.4566667+00:00

@Kale, Ashish Please contact Azure technical support team by raising a support ticket. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.

Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.

Share via

Health of 'Re-protection server' on ASR replication appliance is critical as latest heartbeat is missing.

Your answer