Exchange Replica Writer has rejected an event with error 0x800423f3 (Network Steve Forum)

Exchange Replica Writer has rejected an event with error 0x800423f3

Hello,

VSS backup fails if one of the Exchange 2013 database is offline. Once that DB is online the backup succeeds.

Is that any way to *skip* the offline DB, and VSS backup to succeed for the online DB's?

Here is the console output:

CheckSelectedWriterStatus: checking 12 writers
CheckSelectedWriterStatus: Writer 0:Task Scheduler Writer is VSS_WS_WAITING_FOR_BACKUP_COMPLETE
CheckSelectedWriterStatus: Writer 1:VSS Metadata Store Writer is VSS_WS_WAITING_FOR_BACKUP_COMPLETE
CheckSelectedWriterStatus: Writer 2:Performance Counters Writer is VSS_WS_WAITING_FOR_BACKUP_COMPLETE
CheckSelectedWriterStatus: Writer 3 is VSS_WS_FAILED_AT_BACKUP_COMPLETE
ERROR: Selected writer 'Microsoft Exchange Writer' is in failed state!
- Status: 12 (VSS_WS_FAILED_AT_BACKUP_COMPLETE)
- Writer Failure code: 0x800423f3 (<Unknown error code>)
- Writer ID: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
- Instance ID: {f3a6219d-4c09-4aad-9055-fea8134b04a8}
HRESULT Error catched: 0x8000ffff

Here are the events for that backup time slot:

Log Name:      Application
Source:        VSS
Date:          2/18/2015 2:37:43 AM
Event ID:      8194
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      warden.exch13ca.local
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {85e66358-a755-4c3e-a977-6eeb8773fc2d}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8194</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-18T09:37:43.000000000Z" />
    <EventRecordID>3250493</EventRecordID>
    <Channel>Application</Channel>
    <Computer>warden.exch13ca.local</Computer>
    <Security />
</System>
<EventData>
    <Data>0x80070005, Access is denied.
</Data>
    <Data>

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {85e66358-a755-4c3e-a977-6eeb8773fc2d}</Data>
    <Binary>2D20436F64653A20575254575254494330303030313239352D2043616C6C3A20575254575254494330303030313234392D205049443A202030303030303934342D205449443A202030303030313937362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>

Log Name:      Application
Source:        VSS
Date:          2/18/2015 2:37:43 AM
Event ID:      8194
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      warden.exch13ca.local
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Name: MSMQ Writer (MSMQ)
   Writer Instance Name: MSMQ Writer (MSMQ)
   Writer Instance ID: {98d1fe9e-32e4-45dc-bd67-380afb168ffa}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8194</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-18T09:37:43.000000000Z" />
    <EventRecordID>3250494</EventRecordID>
    <Channel>Application</Channel>
    <Computer>warden.exch13ca.local</Computer>
    <Security />
</System>
<EventData>
    <Data>0x80070005, Access is denied.
</Data>
    <Data>

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Name: MSMQ Writer (MSMQ)
   Writer Instance Name: MSMQ Writer (MSMQ)
   Writer Instance ID: {98d1fe9e-32e4-45dc-bd67-380afb168ffa}</Data>
    <Binary>2D20436F64653A20575254575254494330303030313239352D2043616C6C3A20575254575254494330303030313234392D205049443A202030303030313538382D205449443A202030303032303839322D20434D443A2020433A5C57696E646F77735C73797374656D33325C6D717376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>

Log Name:      Application
Source:        MSExchangeRepl
Date:          2/18/2015 2:37:44 AM
Event ID:      2140
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      warden.exch13ca.local
Description:
The Microsoft Exchange Replication service VSS Writer encountered an exception in function Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::BackupCompleteTruncateLogsComponents. HResult -3. Exception Microsoft.Mapi.MapiExceptionCallFailed: MapiExceptionCallFailed: Unable execute Truncate on snapshot. (hr=0x80004005, ec=1295)
Diagnostic context:
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 63528   StoreEc: 0x50F
    Lid: 42621   StoreEc: 0x50F
    Lid: 1750    ---- Remote Context End ----
    Lid: 59216
    Lid: 34640   StoreEc: 0x50F
    Lid: 52264
    Lid: 46120   StoreEc: 0x50F
   at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
   at Microsoft.Mapi.ExRpcAdmin.ProcessSnapshotOperation(Guid mdbGuid, SnapshotOperationCode operationCode, UInt32 flags)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass25.<SnapshotTruncateLogInstance>b__24()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at Microsoft.Exchange.Data.HA.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.SnapshotTruncateLogInstance(Guid dbGuid, UInt32 flags)
   at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.BackupCompleteTruncateLogsReplica(ReplayConfiguration replica, Guid vssIdCurrentSnapshotSetId, Boolean fTruncateLogs)
   at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.BackupCompleteTruncateLogsComponents(IVssWriterComponents* pComponents, Guid vssIdCurrentSnapshotSetId, Boolean fTruncateLogs).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="49156">2140</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-18T09:37:44.000000000Z" />
    <EventRecordID>3250496</EventRecordID>
    <Channel>Application</Channel>
    <Computer>warden.exch13ca.local</Computer>
    <Security />
</System>
<EventData>
    <Data>Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::BackupCompleteTruncateLogsComponents</Data>
    <Data>-3</Data>
    <Data>Microsoft.Mapi.MapiExceptionCallFailed: MapiExceptionCallFailed: Unable execute Truncate on snapshot. (hr=0x80004005, ec=1295)
Diagnostic context:
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 63528   StoreEc: 0x50F
    Lid: 42621   StoreEc: 0x50F
    Lid: 1750    ---- Remote Context End ----
    Lid: 59216
    Lid: 34640   StoreEc: 0x50F
    Lid: 52264
    Lid: 46120   StoreEc: 0x50F
   at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
   at Microsoft.Mapi.ExRpcAdmin.ProcessSnapshotOperation(Guid mdbGuid, SnapshotOperationCode operationCode, UInt32 flags)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass25.<SnapshotTruncateLogInstance>b__24()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at Microsoft.Exchange.Data.HA.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.SnapshotTruncateLogInstance(Guid dbGuid, UInt32 flags)
   at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.BackupCompleteTruncateLogsReplica(ReplayConfiguration replica, Guid vssIdCurrentSnapshotSetId, Boolean fTruncateLogs)
   at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.BackupCompleteTruncateLogsComponents(IVssWriterComponents* pComponents, Guid vssIdCurrentSnapshotSetId, Boolean fTruncateLogs)</Data>
</EventData>
</Event>

Log Name:      Application
Source:        MSExchangeRepl
Date:          2/18/2015 2:37:44 AM
Event ID:      2034
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      warden.exch13ca.local
Description:
The Microsoft Exchange Replication service VSS Writer (Instance ff7ec8a9-1da0-4a37-acc4-ccfd4fa3bbe9) failed with error FFFFFFFD when processing the backup completion event.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="49156">2034</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-18T09:37:44.000000000Z" />
    <EventRecordID>3250497</EventRecordID>
    <Channel>Application</Channel>
    <Computer>warden.exch13ca.local</Computer>
    <Security />
</System>
<EventData>
    <Data>ff7ec8a9-1da0-4a37-acc4-ccfd4fa3bbe9</Data>
    <Data>FFFFFFFD</Data>
</EventData>
</Event>

Log Name:      Application
Source:        VSS
Date:          2/18/2015 2:37:44 AM
Event ID:      8229
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      warden.exch13ca.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: {f3a6219d-4c09-4aad-9055-fea8134b04a8}
   Command Line: "C:\Program Files\Microsoft\Exchange Server\V15\Bin\msexchangerepl.exe"
   Process ID: 3292
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8229</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-18T09:37:44.000000000Z" />
    <EventRecordID>3250498</EventRecordID>
    <Channel>Application</Channel>
    <Computer>warden.exch13ca.local</Computer>
    <Security />
</System>
<EventData>
    <Data>0x800423f3, The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
</Data>
    <Data>

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: {f3a6219d-4c09-4aad-9055-fea8134b04a8}
   Command Line: "C:\Program Files\Microsoft\Exchange Server\V15\Bin\msexchangerepl.exe"
   Process ID: 3292</Data>
    <Binary>2D20436F64653A20575254575254494330303030353334372D2043616C6C3A20575254575254494330303030333633302D205049443A202030303030333239322D205449443A202030303031363531362D20434D443A202022433A5C50726F6772616D2046696C65735C4D6963726F736F66745C45786368616E6765205365727665725C5631355C42696E5C6D7365786368616E67657265706C2E65786522202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>

------------------------

Thanks in advance.

March 3rd, 2015 9:32am

kindly run vss list writers command and verify which component is failing.

Try to restart Microsoft information store service, Microsoft replication service.

Could be issue with connectivity between notes, verify below mentioned blogs.

http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-vss-backups-of-passive-database-copies-fail-with-error-c7ff07d7-when-preparing-snapshot.aspx

Please mark as answered, if you have got answer.

Proposed as answer by Rajkumar Nagaraj Tuesday, March 03, 2015 1:13 PM
Edited by Rajkumar Nagaraj Tuesday, March 03, 2015 1:26 PM

Free Windows Admin Tool Kit Click here and download it now

March 3rd, 2015 1:13pm

Hi Rajkumar,

Thanks for quick reply.

Well... it looks that Exchange writer gets in State: [12] Failed and Last error: Retryable error but shadows are created after all.
Could you please explain? I would expect that writer to remain in Stable state and last error No error.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\administrator.EXCH13CA>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 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: {83d064ff-acf1-4ad1-a2cb-1b23ad86e98c}
State: [1] Stable
Last error: No error

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {84b09dde-48ab-4a77-b471-6ed68c6a7b01}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {ea7ad87a-4a12-43c2-8b6a-07fed82d0368}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {1e75d7ff-bfc7-42a1-add8-7c6dd8c3b0e9}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {829b6761-56b8-411c-a540-7a24cfeea9ee}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {7bcf4d1e-f650-4ab1-8195-f6fcf065ccdc}
State: [1] Stable
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {5197d4aa-195a-4b83-99a1-044eecf1b197}
State: [1] Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {c8cb3de0-41a5-4260-97d0-462a701b11fc}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {6998e524-820e-432e-bb28-08e60bf93fc5}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {7c0780ba-85e3-44cc-98b6-8707f2707301}
State: [1] Stable
Last error: No error

Writer name: 'MSMQ Writer (MSMQ)'
Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
Writer Instance Id: {5c2480f4-e06f-49a1-8add-fea984001f7d}
State: [1] Stable
Last error: No error

C:\Users\administrator.EXCH13CA>diskshadow
Microsoft DiskShadow version 1.0
Copyright (C) 2013 Microsoft Corporation
On computer: WARDEN, 3/3/2015 7:40:16 AM

DISKSHADOW> set context persistent

DISKSHADOW> set verbose on

DISKSHADOW> begin backup

DISKSHADOW> add volume C:

DISKSHADOW> add volume E:

DISKSHADOW> add volume F:

DISKSHADOW> create
Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.
Excluding writer "BITS Writer", because all of its components have been excluded.
Component "\BCD\BCD" from writer "ASR Writer" is excluded from backup,
because it requires volume which is not in the shadow copy set.
The writer "ASR Writer" is now entirely excluded from the backup because the top-level
non selectable component "\BCD\BCD" is excluded.

* Including writer "Task Scheduler Writer":
+ Adding component: \TasksStore

* Including writer "VSS Metadata Store Writer":
+ Adding component: \WriterMetadataStore

* Including writer "Performance Counters Writer":
+ Adding component: \PerformanceCounters

* Including writer "System Writer":
+ Adding component: \System Files
+ Adding component: \Win32 Services Files

* Including writer "Microsoft Exchange Writer":
+ Adding component: \Microsoft Exchange Server\Microsoft Information Store\warden\b41b9c63-d884-40bb-a131-b3ee944658ad
+ Adding component: \Microsoft Exchange Server\Microsoft Information Store\warden\2d178b41-4032-4135-b5b9-e4a743e41ff6
+ Adding component: \Microsoft Exchange Server\Microsoft Information Store\warden\4a425763-417d-40f6-97aa-aa52c646a209
+ Adding component: \Microsoft Exchange Server\Microsoft Information Store\warden\56b73191-64fb-478c-bc73-0199494715f5
+ Adding component: \Microsoft Exchange Server\Microsoft Information Store\warden\c22490d6-09e1-4de6-a890-ad88d1383f8a
+ Adding component: \Microsoft Exchange Server\Microsoft Information Store\warden\9a58ae58-c44c-4ec5-98a8-2f3872a4676f
+ Adding component: \Microsoft Exchange Server\Microsoft Information Store\warden\e6ce0048-91f1-4044-85e5-b99a9f564491

* Including writer "COM+ REGDB Writer":
+ Adding component: \COM+ REGDB

* Including writer "IIS Config Writer":
+ Adding component: \IISCONFIG

* Including writer "IIS Metabase Writer":
+ Adding component: \IISMETABASE

* Including writer "MSMQ Writer (MSMQ)":
+ Adding component: \config
+ Adding component: \storage

* Including writer "WMI Writer":
+ Adding component: \WMI

* Including writer "Registry Writer":
+ Adding component: \Registry

Alias VSS_SHADOW_1 for shadow ID {fc1f80f2-443c-43c9-a9d1-a22a432c8faf} set as environment variable.
Alias VSS_SHADOW_2 for shadow ID {bdf977f1-5852-4abb-ba9d-317c52baf022} set as environment variable.
Alias VSS_SHADOW_3 for shadow ID {2189b4a0-dadd-498d-b8dc-863f3f083a2c} set as environment variable.
Alias VSS_SHADOW_SET for shadow set ID {7fd1bc62-e065-4c59-bf79-a1fdd99a72f7} set as environment variable.
Inserted file Manifest.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file BCDocument.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM0.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM1.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM2.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM3.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM4.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM5.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM6.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM7.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM8.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM9.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM10.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM11.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM12.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file WM13.xml into .cab file 2015-03-03_7-41-16_WARDEN.cab
Inserted file Dis2B47.tmp into .cab file 2015-03-03_7-41-16_WARDEN.cab

Querying all shadow copies with the shadow copy set ID {7fd1bc62-e065-4c59-bf79-a1fdd99a72f7}

* Shadow copy ID = {bdf977f1-5852-4abb-ba9d-317c52baf022} %VSS_SHADOW_2%
- Shadow copy set: {7fd1bc62-e065-4c59-bf79-a1fdd99a72f7} %VSS_SHADOW_SET%
- Original count of shadow copies = 3
- Original volume name: \\?\Volume{9daaf1ae-6bb8-11e4-80d1-005056af79c1}\ [E:\]
- Creation time: 3/3/2015 7:41:09 AM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
- Originating machine: warden.exch13ca.local
- Service machine: warden.exch13ca.local
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: No_Auto_Release Persistent Differential

* Shadow copy ID = {2189b4a0-dadd-498d-b8dc-863f3f083a2c} %VSS_SHADOW_3%
- Shadow copy set: {7fd1bc62-e065-4c59-bf79-a1fdd99a72f7} %VSS_SHADOW_SET%
- Original count of shadow copies = 3
- Original volume name: \\?\Volume{0446df7b-692d-11e4-80cc-005056af79c1}\ [F:\]
- Creation time: 3/3/2015 7:41:09 AM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
- Originating machine: warden.exch13ca.local
- Service machine: warden.exch13ca.local
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: No_Auto_Release Persistent Differential

* Shadow copy ID = {fc1f80f2-443c-43c9-a9d1-a22a432c8faf} %VSS_SHADOW_1%
- Shadow copy set: {7fd1bc62-e065-4c59-bf79-a1fdd99a72f7} %VSS_SHADOW_SET%
- Original count of shadow copies = 3
- Original volume name: \\?\Volume{7585ec6a-4de2-11e4-80b5-806e6f6e6963}\ [C:\]
- Creation time: 3/3/2015 7:41:09 AM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
- Originating machine: warden.exch13ca.local
- Service machine: warden.exch13ca.local
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: No_Auto_Release Persistent Differential

Number of shadow copies listed: 3

DISKSHADOW> end backup

DISKSHADOW> exit

C:\Users\administrator.EXCH13CA>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 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: {83d064ff-acf1-4ad1-a2cb-1b23ad86e98c}
State: [1] Stable
Last error: No error

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {84b09dde-48ab-4a77-b471-6ed68c6a7b01}
State: [12] Failed
Last error: Retryable error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {ea7ad87a-4a12-43c2-8b6a-07fed82d0368}
State: [1] Stable
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {5197d4aa-195a-4b83-99a1-044eecf1b197}
State: [1] Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {c8cb3de0-41a5-4260-97d0-462a701b11fc}
State: [1] Stable
Last error: No error

Writer name: 'MSMQ Writer (MSMQ)'
Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
Writer Instance Id: {5c2480f4-e06f-49a1-8add-fea984001f7d}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {7bcf4d1e-f650-4ab1-8195-f6fcf065ccdc}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {829b6761-56b8-411c-a540-7a24cfeea9ee}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {1e75d7ff-bfc7-42a1-add8-7c6dd8c3b0e9}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {7c0780ba-85e3-44cc-98b6-8707f2707301}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {6998e524-820e-432e-bb28-08e60bf93fc5}
State: [1] Stable
Last error: No error

C:\Users\administrator.EXCH13CA>

March 3rd, 2015 2:50pm

Below mentioned blog helps you to resolve Exchange Writer's issue.

http://blogs.technet.com/b/exchange/archive/2008/08/25/3406172.aspx

Please mark as answered.

Free Windows Admin Tool Kit Click here and download it now

March 3rd, 2015 3:09pm

That article applies to Exchange 2007 and Windows 2003. What exactly actions do you refer to? I have a Exchange 2013 running on Windows 2012 R2.

March 3rd, 2015 3:39pm

Exchange backup technology is same for all exchange version. Exchange is using ESE engine to generate logs, kindly try to restart the services to fix the issue.

Free Windows Admin Tool Kit Click here and download it now

March 4th, 2015 7:28am

Hi Rajkumar,

I have to add to the initial description. I develop a data protection application and I am using the VSS API. The code is similar to vshadow SDK publicly available by MS.

Excerpt from select.cpp. Please notice that diskshadow encounters VSS_WS_FAILED_AT_BACKUP_COMPLETE and it throws an exception. My question for you is:

Is it normal that shadows got created AND Exchange writer status to remain Failed, with last code Retryable error? It looks like a bug to me.

// Check the status for all selected writers
void VssClient::CheckSelectedWriterStatus()
{
FunctionTracer ft(DBG_INFO);

// Gather writer status to detect potential errors
GatherWriterStatus();

// Gets the number of writers in the gathered status info
// (WARNING: GatherWriterStatus must be called before)
unsigned cWriters = 0;
CHECK_COM(m_pVssObject->GetWriterStatusCount(&cWriters));

// Enumerate each writer
for(unsigned iWriter = 0; iWriter < cWriters; iWriter++)
{
VSS_ID idInstance = GUID_NULL;
VSS_ID idWriter= GUID_NULL;
VSS_WRITER_STATE eWriterStatus = VSS_WS_UNKNOWN;
CComBSTR bstrWriterName;
HRESULT hrWriterFailure = S_OK;

// Get writer status
CHECK_COM(m_pVssObject->GetWriterStatus(iWriter,
&idInstance,
&idWriter,
&bstrWriterName,
&eWriterStatus,
&hrWriterFailure));

// If the writer is not selected, just continue
if (!IsWriterSelected(idInstance))
continue;

// If the writer is in non-stable state, break
switch(eWriterStatus)
{
case VSS_WS_FAILED_AT_IDENTIFY:
case VSS_WS_FAILED_AT_PREPARE_BACKUP:
case VSS_WS_FAILED_AT_PREPARE_SNAPSHOT:
case VSS_WS_FAILED_AT_FREEZE:
case VSS_WS_FAILED_AT_THAW:
case VSS_WS_FAILED_AT_POST_SNAPSHOT:
case VSS_WS_FAILED_AT_BACKUP_COMPLETE:
case VSS_WS_FAILED_AT_PRE_RESTORE:
case VSS_WS_FAILED_AT_POST_RESTORE:
#ifdef VSS_SERVER
case VSS_WS_FAILED_AT_BACKUPSHUTDOWN:
#endif
break;

default:
continue;
}

// Print writer status
ft.WriteLine(L"\n"
L"ERROR: Selected writer '%s' is in failed state!\n"
L" - Status: %d (%s)\n"
L" - Writer Failure code: 0x%08lx (%s)\n"
L" - Writer ID: " WSTR_GUID_FMT L"\n"
L" - Instance ID: " WSTR_GUID_FMT L"\n",
(PWCHAR)bstrWriterName,
eWriterStatus, GetStringFromWriterStatus(eWriterStatus).c_str(),
hrWriterFailure,FunctionTracer::HResult2String(hrWriterFailure).c_str(),
GUID_PRINTF_ARG(idWriter),
GUID_PRINTF_ARG(idInstance)
);

// Stop here
throw(E_UNEXPECTED);
}
}

March 4th, 2015 9:00am

Hi there,

It looks to me that on that machine there is a standalone Exchange server that is not part of any DAG. However, there are error events from MSExchangeRepl? Can you comment on this?

Thanks.

Edited by tionescu 21 hours 59 minutes ago

Free Windows Admin Tool Kit Click here and download it now

March 11th, 2015 5:23am

Well... Just noticed that i posted this question into the DAG thread but nevertheless it's worth asking. Please clarify why there are error events from MSExchangeRepl ?

March 11th, 2015 5:57am

Well... Just noticed that i posted this question into the DAG thread but nevertheless it's worth asking. Please clarify why there are error events from MSExchangeRepl ?

Hi,

Based on my knowledge, not all Errors from MSExchangeRepl are related to DAG.

I suggest upgrade to CU1, CU1 can resolve this issue. Similar thread for your reference:

https://social.technet.microsoft.com/Forums/exchange/en-US/5bdac519-82a8-4871-b902-1cffbfd53aae/backup-exchange-2013-fails-vss-writer-problems

Thanks

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Free Windows Admin Tool Kit Click here and download it now

March 11th, 2015 10:27pm

This topic is archived. No further replies will be accepted.