Microsoft VSS writer failed with error code -569

Article:TECH183446  |  Created: 2012-03-09  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH183446
Article Type
Technical Solution


Environment

Issue



While freezing a passive copy database, Exchagne VSS write fails due to missing log files.


Error



Mon Feb 20 2012 17:48:22 ESE E2007 Information Store (3680) Shadow copy instance 1 aborted.
For more information, click http://www.microsoft.com/contentredirect.asp.

Mon Feb 20 2012 17:48:22 VSS W8229 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:
   Freeze Event
Context:
   Execution Context: Writer
   Writer Class Id: {xxxxxxxx-xxxxx-xxxxx-xxxx-xxxxxxxxxxxx}
   Writer Name: Microsoft Exchange Writer
   Writer Instance Name: Exchange Information Store
   Writer Instance ID: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
   Command Line: "C:\Program Files\Microsoft\Exchange Server\V14\bin\store.exe"
   Process ID: 3680

Mon Feb 20 2012 17:48:22 ESE E2002 Information Store (3680) Shadow copy instance 1 encountered error -569 on freeze.
For more information, click http://www.microsoft.com/contentredirect.asp.

Mon Feb 20 2012 17:48:22 MSExchangeIS E9611 Exchange VSS Writer (instance xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:x) failed with error code -569 when freezing the database(s).

Mon Feb 20 2012 17:48:21 ESE E459 Information Store (3680) MailboxDatabaseName: The file G:\Program Files\Microsoft\Exchange Server\V14\Mailbox\MailboxDatabaseName\E080000B192.log is missing and could not be backed-up.
For more information, click http://www.microsoft.com/contentredirect.asp.

 


Environment



Exchange 2010 DAG


Solution



Follow the same steps outlined in Microsoft kb article 935634 to properly move and regenerate new logs for the database that is failing.
 http://support.microsoft.com/kb/935634




Article URL http://www.symantec.com/docs/TECH183446


Terms of use for this information are found in Legal Notices