0x800423F2

Yagnavalkya Siva Prasad Manchi 1 Reputation point
2023-09-15T18:31:03.5166667+00:00

Greetings,

We are seeing the following as possible cause for Error ID 153051 in Event Details for the Replicated Item (it is an Azure VM):

VSS writer ASR Writer failed with error 0x800423f2 during After DoSnapshotSet phase on the source machine.

We restarted the VSS service responsible for ASR Writer, but the Replicated Health of the item continues to appear in Warning status.

Attached is the screenshot from "C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\Application Data\ApplicationPolicyLogs\vacp.log*".*

Request your help to sort this out.

Thanks in advance.

Regards

Screenshot_VACPLog.jpg

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
5,975 questions
Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
522 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Martin 5 Reputation points
    2023-09-28T08:04:34.81+00:00

    In our case, the service 'Azure Site Recovery VSS Provider' was set to "Manual" rather than "Automatic" by default. After a change of the behaviour, replication health returned to normal/ healthy state.

    1 person found this answer helpful.
    0 comments No comments

  2. kobulloc-MSFT 17,376 Reputation points Microsoft Employee
    2023-09-28T01:47:06.4033333+00:00

    Hello, @Yagnavalkya Siva Prasad Manchi (and @Martin)!

    Edit: Solution from @Martin:

    In our case, the service 'Azure Site Recovery VSS Provider' was set to "Manual" rather than "Automatic" by default. After a change of the behaviour, replication health returned to normal/ healthy state.

    Why am I running into the VSS writer ASR Writer failed with error 0x800423f2 during After DoSnapshotSet phase on the source machine. error on SQL Server?

    This is a question that has come up before and there are some troubleshooting steps you can take to address this:

    • What OS are you using on your VM (is this SQL Server)? There is a known issue with SQL Server 2008 R2.
    • Have you patched/updated your VMs recently? Some known issues have been addressed with older patches.
    • Was another backup taking place? If VSS was in use then it would cause a conflict that could cause this error.
    • Are you using third party software? This might cause a conflict with VSS.
    • Have these been rebooted recently? Rebooting can clear bad states on the VM that may be responsible for the error.

    Edit: Solution above from Martin.


    I hope this has been helpful! Your feedback is important so please take a moment to accept answers.

    If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

    User's image

    0 comments No comments