locked
Error Message RRS feed

  • Question

  • Hello. I have DPM 2012 R2 (Update Rollup4 Installed), protecting Exchange 2013 CU6. From Friday i get the following error message:

    "

    Type: Recovery point
    Status: Failed
    Description: The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error.  If the backup process is retried,
    the error is likely to reoccur.
     (0x800423F4))"

    Recovery points are not created (short term protection) and backup to tape also fails (long term protection). 

    How can i fix this?

    Regards.

    Monday, November 17, 2014 6:09 AM

Answers

  • This issue was narrowed down to one update causing the problem on 2012 Servers.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/c78faf9a-e126-4f51-b8fe-69d547a9d365/november-2014-update-rollup-kb3000853-vss-backups-broken?forum=winserver8gen

    Removing KB3000853 did the trick, but i still have some 2012R2 servers with sql dbs that are failing to backup due to the same reason, but this update is not available in that release. 

    • Marked as answer by Gband Wednesday, November 19, 2014 7:25 AM
    Tuesday, November 18, 2014 9:33 PM
  • Hi all,

    I have communicated this issue to the Windows folks - but not sure what their plan is.  In the meantime, please reference this Windows forum thread to keep an eye on it.  Any backup application that uses VSS will be effected, so I'm sure they will need to release a fix for the issue.

    November 2014 Update Rollup - KB3000853 - VSS Backups Broken

    UPDATE 11-20-14
    ============

    Installing KB2996928 on affected servers resolves the issue without the need to uninstall KB3000853.


    Backup task fails with a time-out error in Windows Server 2012 or Windows Server 2008 R2 http://support.microsoft.com/kb/2996928/


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Wednesday, November 19, 2014 4:29 PM
    Moderator

All replies

  • Hello,

    have the same issue

    best regards

    Andreas

    Monday, November 17, 2014 3:40 PM
  • Hello,

    uninstall all updates (from Friday) on your Exchange Server and all works fine.

    Greetings

    Andreas


    • Edited by SuWAndreas Monday, November 17, 2014 4:28 PM
    Monday, November 17, 2014 4:28 PM
  • having the same issue here. Anyone have any ideas how to fix this?
    Monday, November 17, 2014 11:33 PM
  • Hello. What kind of updates do you mean? Only Windows Updates where installed before the problem started.
    Tuesday, November 18, 2014 8:29 AM
  • yes only Windows updates installed on 11/14/14
    Tuesday, November 18, 2014 9:32 AM
  • We have the same configuration with the exact same error. Does anyone know what specific update to remove or has any other solutions apart from removing all the updates please?

    Thanks

    Tuesday, November 18, 2014 9:41 AM
  • Yes please, some more detailed instructions. These are the updates installed. Should all of them be uninstalled? In which order (or it doesn't mind)?

    Is this a bug to be fixed?

    Regards.

    Tuesday, November 18, 2014 10:19 AM
  • I uninstalled all Windows Updates! Complete and no special order.

    Sorry I don't know which update (Windows or Security) the issue occur.

    I complete uninstall all last received updates on Exchange Server - when a fix is available I will install the updates again

     
    Tuesday, November 18, 2014 3:03 PM
  • Looks like i will have to remove them all. What a fun night for me! :)
    Tuesday, November 18, 2014 5:45 PM
  • This issue was narrowed down to one update causing the problem on 2012 Servers.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/c78faf9a-e126-4f51-b8fe-69d547a9d365/november-2014-update-rollup-kb3000853-vss-backups-broken?forum=winserver8gen

    Removing KB3000853 did the trick, but i still have some 2012R2 servers with sql dbs that are failing to backup due to the same reason, but this update is not available in that release. 

    • Marked as answer by Gband Wednesday, November 19, 2014 7:25 AM
    Tuesday, November 18, 2014 9:33 PM
  • Hello. Indeed, unistalling only KB3000853 and restarting the server, was able to create recovery points and tape backup. I disabled windows update service and also removed approval for KB3000853 from WSUS.

    Where should i check for final solution from Microsoft? Another update will fix this (from Windows update/Wsus)?

    Regards

    Wednesday, November 19, 2014 7:25 AM
  • Hi all,

    I have communicated this issue to the Windows folks - but not sure what their plan is.  In the meantime, please reference this Windows forum thread to keep an eye on it.  Any backup application that uses VSS will be effected, so I'm sure they will need to release a fix for the issue.

    November 2014 Update Rollup - KB3000853 - VSS Backups Broken

    UPDATE 11-20-14
    ============

    Installing KB2996928 on affected servers resolves the issue without the need to uninstall KB3000853.


    Backup task fails with a time-out error in Windows Server 2012 or Windows Server 2008 R2 http://support.microsoft.com/kb/2996928/


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Wednesday, November 19, 2014 4:29 PM
    Moderator