Microsoft Exchange writer - retryable error

Question

Hi All,

We have two exchange server 2016 running in DAG with the most recent CU, the issue is with Microsoft Exchange writer automatically went to retryable error, this is happening even though the backup jobs are not triggered.

I have restarted Microsoft Exchange replication service from both the servers. Post that, i can see Microsoft Exchange writer is running with No error, but after sometime Microsoft Exchange writer is automatically changing to retryable error

I have restarted the service twice, then purged the transaction logs by enabling and disabling circular logging , but still we are facing this issue. I don't see any critical or error events for Microsoft Exchange writer

In the event logs, i can see the below information and warning event

Information - 8224 - The VSS service is shutting down due to idle timeout.

Warning - 8229 - A VSS writer has rejected an event with error 0x800423f2, The writer's timeout expired between the Freeze and Thaw events, this warning is related to the Writer Name: Cluster Shared Volume VSS Writer

Please let me know, delete the shadow copy and re enable it would help us to keep the Microsoft Exchange writer stable without error ? Does delete and re enable the shadow copy would help us to fix this issue ?

I would like to understand the cause for this automatic failure of Microsoft Exchange writer, Kindly share all your thoughts and experience.

Answer 1

Hi @Nithyanandham Singaravadivelu ,

Welcome to the Exchange Server forum.

It is recommended that you run vssadmin list writers to see if Microsoft Exchange Writer has errors? If there is retryable error, please restart the Microsoft Exchange Information Store Service and run again.
If "vssadmin list writers" still list it as not stable, restart your exchange server.

Besides, for"Warning - 8229 - A VSS writer has rejected an event with error 0x800423f2, The writer's timeout expired between the Freeze and Thaw events, this warning is related to the Writer Name: Cluster Shared Volume VSS Writer"
You also need to check Cluster Shared Volume VSS Writer for timeout errors.

For “The VSS service is shutting down due to idle timeout.”, you could check out this article: how-to-fix-vss-service-is-shutting-down-due-to-idle-timeout-error
Please Note: Since these web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.