Skip to content

Commit c2b7456

Browse files
committed
fixes link, header
1 parent 8d3026f commit c2b7456

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/site-recovery/azure-to-azure-troubleshoot-errors.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.author: rochakm
1111

1212
# Troubleshoot Azure-to-Azure VM replication errors
1313

14-
This article describes how to troubleshoot common errors in Azure Site Recovery during replication and recovery of Azure virtual machines (VMs) from one region to another. For more information about supported configurations, see the [support matrix for replicating Azure VMs](azure-to-azure-support-matrix).
14+
This article describes how to troubleshoot common errors in Azure Site Recovery during replication and recovery of Azure virtual machines (VMs) from one region to another. For more information about supported configurations, see the [support matrix for replicating Azure VMs](azure-to-azure-support-matrix.md).
1515

1616
## Azure resource quota issues (error code 150097)
1717

@@ -372,13 +372,13 @@ You might not see the VM that you want to enable for replication if a stale Site
372372

373373
## Unable to select a virtual machine for protection
374374

375-
### Issue 1: The virtual machine has an extension installed in a failed or unresponsive state
375+
### Possible cause
376376

377-
Go to **Virtual machines** > **Settings** > **Extensions** and check for any extensions in a failed state. Uninstall any failed extension, and then try again to protect the virtual machine.
377+
The virtual machine has an extension installed in a failed or unresponsive state
378378

379-
### Issue 2: The VM's provisioning state isn't valid
379+
### Fix the problem
380380

381-
See the troubleshooting steps in [The VM's provisioning state is not valid](#the-vms-provisioning-state-is-not-valid-error-code-150019).
381+
Go to **Virtual machines** > **Settings** > **Extensions** and check for any extensions in a failed state. Uninstall any failed extension, and then try again to protect the virtual machine.
382382

383383
## The VM's provisioning state isn't valid (error code 150019)
384384

0 commit comments

Comments
 (0)