none
0x800423F4

    Question

  • I can't make any backup to my exchange server. I got this error: "The volume shadow copy operation failed with error 0x800423f4."

    PS C:\Users\Administrator> vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.


    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error


    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error


    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error


    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {724d8a9f-33e8-4c99-b84e-6cda52f1214c}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {b981f959-43df-4c5a-b09c-27c841e85929}
       State: [1] Stable
       Last error: No error


    Writer name: 'DFS Replication service writer'
       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
       Writer Instance Id: {e09cbc5e-4c28-4dde-bab9-c43b175176c1}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {7b9510d1-2e92-4eea-a4e4-ace0bdbaf1e4}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {fa1ba3a8-4215-49e9-bfb5-d60fda6b7521}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {44714267-a69a-4b4c-a7c5-decd398e506d}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {44af8b02-3c08-4de8-b363-7d8683f4814a}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {37d62c08-b672-4183-adc4-d3a636b161f0}
       State: [1] Stable
       Last error: No error


    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {0fb4255f-e0e8-4b38-b358-d9b8d650ee6d}
       State: [1] Stable
       Last error: No error


    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {edd02309-8c8e-47dc-ba20-1498b6a39f49}
       State: [1] Stable
       Last error: No error


    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {d6d084f9-4629-4e59-b1c8-fd5892e1bb2d}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {ddcec708-1726-48a1-a409-a786907147a1}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {62ea555d-4afb-47e0-8116-9777f3ab5b1e}
       State: [1] Stable
       Last error: No error

    What to do in this case ... ?

    Wednesday, February 15, 2012 8:26 AM

All replies

  • It worked before movig the old server to the new one, with new hardware configuration. Can anyone help me?
    Wednesday, February 15, 2012 7:48 PM
  • It worked before movig the old server to the new one, with new hardware configuration. Can anyone help me?

       

    Hi,

    From your description, it seems that there are many errors in VSS writers, you may try to re-register the VSS Writers and retry the backup operation.

    How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003

    http://www.symantec.com/business/support/index?page=content&id=TECH70486

    By the way, please confirm that if you had install the windows server backup.


    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.


    Thursday, February 16, 2012 2:21 AM
    Moderator
  • Yes I have WinServerBackup installed.

    I tried what they wrote in your link ... but i'm getting this:

    C:\Windows\System32>Wbadmin start systemstatebackup -backuptarget:E:
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.


    Starting to back up the system state [16.02.2012 10:07]...
    Retrieving volume information...
    This will back up the system state from volume(s) System Reserved (100.00 MB),W
    ndows Server 2008 R2(C:) to E:.
    Do you want to start the backup operation?
    [Y] Yes [N] No y


    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Summary of the backup operation:
    ------------------


    The backup of the system state failed [16.02.2012 10:07].
    Log of files successfully backed up:
    C:\Windows\Logs\WindowsServerBackup\Backup-16-02-2012_10-07-28.log


    Log of files for which backup failed:
    C:\Windows\Logs\WindowsServerBackup\Backup_Error-16-02-2012_10-07-28.log


    The operation ended before completion.
    The system writer is not found in the backup.


    C:\Windows\System32>


    • Edited by xD90europe Thursday, February 16, 2012 8:12 AM
    Thursday, February 16, 2012 8:11 AM
  • Now if I type this in WPoerShell ... I'm not receiving any errors after running that batch.

    Windows PowerShell
    Copyright (C) 2009 Microsoft Corporation. All rights reserved.


    PS C:\Users\Administrator> vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.


    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error


    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error


    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error


    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {417ad5c6-b70f-465c-baa7-b88db6fa7839}
       State: [1] Stable
       Last error: No error


    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {43ea8695-37f4-48a2-86a5-8c8c7db9ecfb}
       State: [1] Stable
       Last error: No error


    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {506ec564-2b8f-43d3-ab52-5549139e2c55}
       State: [1] Stable
       Last error: No error


    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {527f4512-eec6-4056-a752-e3c4bbc44975}
       State: [1] Stable
       Last error: No error


    PS C:\Users\Administrator>

    Why it shows me less writer objects?

    Thursday, February 16, 2012 8:16 AM
  •  ... No solution for my problem?
    Saturday, February 18, 2012 9:49 AM
  • I need help as soon as possible!
    Saturday, February 18, 2012 6:23 PM
  • when you are encountering the error "The system writer is not found in the backup.", please refer to the following article.
    http://support.microsoft.com/kb/2009272

    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.

    Monday, February 20, 2012 2:12 AM
    Moderator
  • I did what wrote there and than I typed vssadmin list writers and I got what I wrote in Thursday, February 16, 2012 8:16 AM ... but the Backup didn't worked.  If I type  vssadmin list writers after 2-3 minutes I'm receiving this (in cmd):

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error


    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error


    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error


    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {4e603331-0f5b-4b45-b4d1-42487011f7b3}
       State: [7] Failed
       Last error: Non-retryable error


    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {cbb365e8-3ccb-4153-a62c-1260c5083e27}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {0c7fc531-e8df-4182-a8aa-7cd7d972499d}
       State: [7] Failed
       Last error: Timed out


    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {3b2b57ac-aaa0-4248-8bd7-450ccdac32d1}
       State: [7] Failed
       Last error: Timed out

     I did the restore of server via Todo Backup ... from a server to a different hardware server ... I think is because of this ... because it worked before!

    Monday, February 20, 2012 7:14 AM
  • This is the Event Viewer Log Error:

    ---------------------------------------------------------------------[VSS]

    IVssAsrWriterBackup::GetDiskComponents
    0x80070057, The parameter is incorrect.
    Operation: OnIdentify event Gathering Writer Data Context: Execution Context: ASR Writer Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Name: ASR Writer Writer Instance ID: {4e603331-0f5b-4b45-b4d1-42487011f7b3}
    2D20436F64653A20575254415352574330303030303234332D2043616C6C3A20575254415352574330303030303138332D205049443A202030303030313536302D205449443A202030303031323130302D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820

    Binary data:

    In Words

    0000: 6F43202D 203A6564 41545257 43575253
    0008: 30303030 33343230 6143202D 203A6C6C
    0010: 41545257 43575253 30303030 33383130
    0018: 4950202D 20203A44 30303030 30363531
    0020: 4954202D 20203A44 31303030 30303132
    0028: 4D43202D 20203A44 575C3A43 6F646E69
    0030: 735C7377 65747379 5C32336D 76737376
    0038: 78652E63 20202065 7355202D 203A7265
    0040: 656D614E 544E203A 54554120 49524F48
    0048: 535C5954 45545359 53202C4D 533A4449
    0050: 352D312D 2038312D

    In Bytes

    0000: 2D 20 43 6F 64 65 3A 20 - Code:
    0008: 57 52 54 41 53 52 57 43 WRTASRWC
    0010: 30 30 30 30 30 32 34 33 00000243
    0018: 2D 20 43 61 6C 6C 3A 20 - Call:
    0020: 57 52 54 41 53 52 57 43 WRTASRWC
    0028: 30 30 30 30 30 31 38 33 00000183
    0030: 2D 20 50 49 44 3A 20 20 - PID:
    0038: 30 30 30 30 31 35 36 30 00001560
    0040: 2D 20 54 49 44 3A 20 20 - TID:
    0048: 30 30 30 31 32 31 30 30 00012100
    0050: 2D 20 43 4D 44 3A 20 20 - CMD:
    0058: 43 3A 5C 57 69 6E 64 6F C:\Windo
    0060: 77 73 5C 73 79 73 74 65 ws\syste
    0068: 6D 33 32 5C 76 73 73 76 m32\vssv
    0070: 63 2E 65 78 65 20 20 20 c.exe
    0078: 2D 20 55 73 65 72 3A 20 - User:
    0080: 4E 61 6D 65 3A 20 4E 54 Name: NT
    0088: 20 41 55 54 48 4F 52 49 AUTHORI
    0090: 54 59 5C 53 59 53 54 45 TY\SYSTE
    0098: 4D 2C 20 53 49 44 3A 53 M, SID:S
    00a0: 2D 31 2D 35 2D 31 38 20 -1-5-18 

    -------------------------------------------------------------[SPP]

    ASR Writer
    The parameter is incorrect. (0x80070057)
    01000000C70F0000B60F00000000000042BEB7C511CAC619E59C92030000000000000000

    Binary data:

    In Words

    0000: 00000001 00000FC7 00000FB6 00000000
    0008: C5B7BE42 19C6CA11 03929CE5 00000000
    0010: 00000000

    In Bytes

    0000: 01 00 00 00 C7 0F 00 00 ....Ç...
    0008: B6 0F 00 00 00 00 00 00 ¶.......
    0010: 42 BE B7 C5 11 CA C6 19 B¾·Å.ÊÆ.
    0018: E5 9C 92 03 00 00 00 00 園.....
    0020: 00 00 00 00 ....

    -----------------------------------------------------------------[Backup]

    The backup operation that started at '‎2012‎-‎02‎-‎20T07:04:09.133000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Monday, February 20, 2012 7:29 AM
  • Isn't any hotfix for ws 2008 R2 (I found one, but it was for ws 2003)
    Thursday, February 23, 2012 7:04 AM
  • Other backup software [uninstalled] can cause this problem with WindowsServerBackup&Restore???
    How can I fix it?

    Friday, February 24, 2012 8:06 AM