locked
Microsoft Exchange Writer Retryable error

    Question

  • Microsoft Exchange Writer Retryable error

    Backup Application : backupExec 2012

    Exchange : exchange 2010

    No dag

    Writer name: 'Microsoft Exchange Writer'

       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

       Writer Instance Id: {8f745303-a888-4063-b36f-8c9baf40c5be}

       State: [8] Failed

       Last error: Retryable error

    Log Name:      Application

    Source:        VSS

    Date:          6/4/2013 1:53:56 PM

    Event ID:      12291

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      xxx

    Description:

    Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: BackupShutdown [0x8000ffff].

    Log Name:      Application

    Source:        VSS

    Date:          6/4/2013 1:53:56 PM

    Event ID:      8193

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      xxx

    Description:

    Volume Shadow Copy Service error: Unexpected error calling routine IMultiInterfaceEventControl::GetSubscriptions.  hr = 0x80010108.

    Tuesday, June 4, 2013 11:30 AM

Answers

All replies

  • Hi thends007,

    Please try the suggestion in this blog:
    "the Exchange writer is not in stable state (in "Retryable error" state as shown below) then we have to restart the information store service on the exchange server to get the exchange server in stable state. "
    http://blogs.technet.com/b/exchange/archive/2008/08/25/3406172.aspx

    Best Regards.

    • Marked as answer by thends007 Monday, June 10, 2013 12:54 PM
    Wednesday, June 5, 2013 2:12 AM
  • This solution does not work. We have exactly the same problem. We run Exchange 2013 CU3 on Windows Server 2012.
    Saturday, March 8, 2014 2:17 AM
  • We have the same issue. Exchange 2013 CU3 on Server 2012.

    The 'Microsoft Exchange Writer' is in a stable state, but the Last error: is Retryable Error, AND

    my MICROSOFT WINDOWS SERVER BACKUP fails with "Failure Result: 800423F3"

    I'm about to open a ticket with Microsoft, but this should not be charged because it is supposed to work!

    Tim

    Friday, April 11, 2014 4:08 PM
  • I'm trying this. I'll let you know if it works.

    If the VSS error code 0x800423f3 is reported, the reason is a corrupt state of WMI (wmiutils.dll). This may happen if a registry cleaner was used or a third-party application was uninstalled incorrectly. What you need to do is re-register wmiutils.dll and then restart the WMI service.

    In the command prompt, execute the following three lines (note that stopping the WMI service does NOT stop VMs, it only stops the management service):

    net stop winmgmt

    regsvr32 wmiutils.dll  

    net start winmgmt

    After that you should start up the Hyper-V Management Service again if needed.

    Friday, April 11, 2014 4:25 PM
  • Did it work?
    Sunday, October 12, 2014 6:21 AM
  • I seem to have the same issue. Did this get fixed?

    Sunday, October 12, 2014 7:51 PM
  • Hi,

    How about restating the IS or the server ?if still having an issue.

    lease post the latest error on it. 

    Regards

    Muthu


    Thanks Muthu

    Thursday, April 23, 2015 5:32 PM
  • Our customer with Backup Exec 2015 same problem with exchange VSS writer. I try restart server, Information store and register again VSS writers. every time same VSS error 

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {4d64939f-4732-4b34-935a-7b78ba88ebfc}
       State: [1] Stable
       Last error: Retryable error

    I try install Windows backup and take full backup with that and suprise. VSS writer works after that. 

    • Proposed as answer by Ed CrowleyMVP Saturday, October 15, 2016 7:38 PM
    Saturday, October 15, 2016 4:26 PM
  • --- Check for the below event logs

    Log Name:      Application
    Source:        VSS
    Date:          11/9/2016 7:53:56 PM
    Event ID:      8229
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      ACMA-EXCH.ACMA-INC.LOCAL
    Description:
    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 

    Operation:
       BackupComplete Event

    Context:
       Execution Context: Writer
       Writer Class Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Name: Microsoft Exchange Writer
       Writer Instance Name: Exchange Replication Service
       Writer Instance ID: {2e1494ca-6e06-47a8-af0e-f77213bfecaf}
       Command Line: "C:\Program Files\Microsoft\Exchange Server\V15\bin\msexchangerepl.exe"
       Process ID: 5176

    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          11/9/2016 7:53:56 PM
    Event ID:      2034
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ACMA-EXCH.ACMA-INC.LOCAL
    Description:
    The Microsoft Exchange Replication service VSS Writer (Instance c2f51bd6-b7b3-49e1-8e12-4ad329955268) failed with error FFFFFFFD when processing the backup completion event.

    --- Observed “Microsoft Exchange Writer” is in failed state.

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {2e1494ca-6e06-47a8-af0e-f77213bfecaf}
       State: [12] Failed
       Last error: Retryable error

    --- I have restarted the Exchange Replication Service and found the writer is in stable state.

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {12c870b7-b0b2-418c-88c0-3564025eb01c}
       State: [1] Stable
       Last error: No error

        
    • Proposed as answer by sapl_de Wednesday, April 5, 2017 9:35 AM
    Thursday, November 10, 2016 10:07 AM
  • --- Check for the below event logs

    Log Name:      Application
    Source:        VSS
    Date:          11/9/2016 7:53:56 PM
    Event ID:      8229
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      ACMA-EXCH.ACMA-INC.LOCAL
    Description:
    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 

    Operation:
       BackupComplete Event

    Context:
       Execution Context: Writer
       Writer Class Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Name: Microsoft Exchange Writer
       Writer Instance Name: Exchange Replication Service
       Writer Instance ID: {2e1494ca-6e06-47a8-af0e-f77213bfecaf}
       Command Line: "C:\Program Files\Microsoft\Exchange Server\V15\bin\msexchangerepl.exe"
       Process ID: 5176

    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          11/9/2016 7:53:56 PM
    Event ID:      2034
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ACMA-EXCH.ACMA-INC.LOCAL
    Description:
    The Microsoft Exchange Replication service VSS Writer (Instance c2f51bd6-b7b3-49e1-8e12-4ad329955268) failed with error FFFFFFFD when processing the backup completion event.

    --- Observed “Microsoft Exchange Writer” is in failed state.

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {2e1494ca-6e06-47a8-af0e-f77213bfecaf}
       State: [12] Failed
       Last error: Retryable error

    --- I have restarted the Exchange Replication Service and found the writer is in stable state.

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {12c870b7-b0b2-418c-88c0-3564025eb01c}
       State: [1] Stable
       Last error: No error

        
    This worked for us as well, thank you!
    Monday, February 13, 2017 3:42 PM