A failure occurred accessing the Writer metadata

JPB · **Joined:** Thu Mar 18, 2010 12:26 pm **Posts:** 3

Dear all,

I use BackupExec 12 on a Windows 2008 server to backup other Windows 2008 Terminal Services servers. Most of them work, but some fail with this error in the log:

Quote:

V-79-57344-65225 - AOFO: Initialization failure on: "\\TSSERVER1\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE000FEC9): A failure occurred accessing the Writer metadata.

Check the Windows Event Viewer for details.

V-79-57344-65225 - AOFO: Initialization failure on: "\\TSSERVER1\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE000FEC9): A failure occurred accessing the Writer metadata.

Check the Windows Event Viewer for details.

V-79-57344-65225 - A failure occurred accessing the Writer metadata.

I followed the links to possible solutions on the Symantec web site but none of them were able to resolve it. Therefore I am looking for ideas please.

Thanks in advance

dave.webb · Posted: Sun Mar 21, 2010 12:32 pm

JPB,

Can you check that the following services are not set to disabled on the server you are trying to backup:

- Microsoft Software Shadow Copy Provider
- Volume Shadow Copy

Also, are there any VSS errors logged in the Application Event Log?

Dave

JPB · **Joined:** Thu Mar 18, 2010 12:26 pm **Posts:** 3

Both services are set to manual. I have this in the Application Eventlog:

Source: VSS
EventID: 8193

Quote:

Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid(S-1-5-21-457832296-3835485684-312220016-5639.bak). hr = 0x80070539, The security ID structure is invalid.
.

Operation:
OnIdentify event
Gathering Writer Data

Context:
Execution Context: Shadow Copy Optimization Writer
Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Name: Shadow Copy Optimization Writer
Writer Instance ID: {c1548f3e-af6c-4bbc-8a2a-b770b7c270a6}

cocker · Posted: Tue Mar 23, 2010 3:12 pm

Was this one the articles you looked at: http://seer.entsupport.symantec.com/docs/312068.htm

JPB · **Joined:** Thu Mar 18, 2010 12:26 pm **Posts:** 3

I found a post on another forum that suggested assigning a drive letter to the 100MB hidden system parition to fix this - and it worked! How strange that this problem only occurred on 2 out of 8 identical servers.

A failure occurred accessing the Writer metadata

Who is online