Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error accessing Writer Metadata

Created: 26 Jan 2005 • Updated: 22 May 2010 | 28 comments

When backing up shadow copy componants I get the following error:

Final error: 0xa000fec9 - A failure occurred accessing the Writer metadata.

I am using windows SBS 2003


Any suggestions?

Comments 28 CommentsJump to latest comment

David Slamowitz's picture

I have tried the VSSADMIN LIST WRITERS command and all writers are stable with no errors

Also Volume Shadow Copy services are set to manual

Zerene Sangma's picture

HI,

You may try applying this patch to resolve the issue:

http://support.microsoft.com/default.aspx?scid=kb;...

Additionally, under shadow copy components select only "system state" and check the results.

David Slamowitz's picture

I have downloaded the hotfix but have not installed it yet since I will have to reboot the server. I will install it over the weekend. In the meantime I tried only backing up System state and got the same error.

One interesting point. The VSS is partially working. This is an excerpt from the job log:

Family Name: "SWC-PDC Full Backup 2/3/2005"
Backup of "Shadow?Copy?Components Shadow?Copy?Components"
Backup set #10 on storage media #1
Backup set description: "Full Backup Excluding Unscored PSG's"
Backup Type: FULL - Back Up Files - Allow incrementals and differentials using modified time

Backup started on 2/4/2005 at 2:19:19 AM.

Backup Set Detail Information
A failure occurred accessing the Writer metadata.

Backup completed on 2/4/2005 at 2:19:54 AM.

Backup Set Summary
Backed up 10 Shadow Copy Writer(s)
Backed up 9 Shadow Copy Component(s)
Processed 188,519,622 bytes in 35 seconds.
Throughput rate: 308 MB/min
Software compression ratio: 3.9:1




This is what I get from running the command 'VSSADMIN LIST WRITERS '


Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {eb4fc7ff-72fd-4009-8121-4f5d89545606}
State: Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {87aafd3e-0bb4-4760-8729-9214b4c89c4d}
State: Stable
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {0f35fa02-6c1e-4992-a769-ef8df2265562}
State: Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {d75561be-4c0b-43df-85bd-c46857370ed0}
State: Stable
Last error: No error

Writer name: 'Removable Storage Manager'
Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
Writer Instance Id: {1e2b6c8c-3ee9-470d-85a1-937da16088da}
State: Stable
Last error: No error

Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {40952594-1e19-497d-84af-d125a4ca1990}
State: Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {fc8d11e6-db64-46f4-a606-db1c51d1ef5c}
State: Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {a03a82ff-b8f1-4437-ac60-5c4106fed105}
State: Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {5fd824cd-5cf6-4fd6-9265-dd822141ed60}
State: Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {3f8358cb-603d-4af0-8ec2-754363131c93}
State: Stable
Last error: No error

Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {e34d12cc-a3fe-48df-a6c8-2cef65dbc6a6}
State: Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {88c7a606-5763-4db5-b937-dc7ff9ae6b83}
State: Stable
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {4fce7afd-b4ff-44ae-8168-7be6070be1c3}
State: Stable
Last error: No error


It seems that there are 13 writers but only 10 have been backed up . I'm not sure what the 9 componants means.

Sandor Nilsson's picture

I've got an almost identical problem. And the same report generated using VSSADMIN.

Then I tried the recommendation to download the hotfix from Microsoft. Which actually requires a phonecall.

But there's no change in performance. I still have failed backups.

Any other ideas anynone?

David Slamowitz's picture

I tried the hot fix over the weekend and still have the same problem.

David Slamowitz's picture

I'm not sure if this has any bearing,

I have also had the following error:

Event Type:Information
Event Source:Application Error
Event Category:(100)
Event ID:1004
Date:2/5/2005
Time:7:16:05 PM
User:N/A
Computer:SWC-PDC
Description:
Reporting queued error: faulting application bengine.exe, version 9.1.4691.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x00006a07.


my problem is similiar to the following forum posting: http://forums.veritas.com/discussions/thread.jspa?...

I tried the suggested fix: I have downloaded SP1 but it will not install. Everything goes well until it says 'configuring backup exec' then the installer encounters an error and the installation 'rolls back'

I have not tried MDAC should I do this next or something else.

David Slamowitz's picture

I did try renaming the catalogs folder prior to installation as suggested in one of the postings to no avail. Same rolling back problem with SP1 installation.

Mark Ellis's picture

I should like to pitch in that this same error is driving me insane also.

I have been experiencing this for months now and I cannot resolve it. I have applied all of the suggested MS hotfixes including 833167.

I back up many Windows 2003 Servers of which 3 are doing this. One is a completely new build.

I should also say that I upgraded from v9.1 to v10 to see if this would finally cure the problem, but no. HOWEVER, it may be worth noting that the error message is different.

Under v10, the same servers repeatedly produce this error, but the error message is:

Backup- \\MELCHETT\Shadow?Copy?Components \\MELCHETT\Shadow?Copy?Components

V-79-57344-65245 - A failure occurred accessing the object list.
V-79-57344-65245 - A failure occurred accessing the object list.

(Where MELCHETT is the server name in this instance.)

Any ideas very greatly received.

Mark

SANDEEP PILLAY's picture

Hi,

In order to isolate the issue, please reapply MDAC and the Jet Database from the following links:

- Microsoft Data Access Components (MDAC) 2.8

http://www.microsoft.com/downloads/details.aspx?Fa...


- How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine

http://support.microsoft.com/default.aspx?scid=kb;...

If the problem still persists then please perform a repair database. Please refer to the following technote:

- http://seer.support.veritas.com/docs/265180.htm


Also refer to the following link:

http://seer.support.veritas.com/docs/265180.htm

We hope this will help.

Mark Ellis's picture

1. MDAC 2.8 re-applied.
2. JET Database Engine re-applied.
3. Database repair performed.

No change at all.

Still the same error!

Mark

306924662's picture

Is your volume shadow copy service started in windows services? Mine was set to manual and changing to automatic fixed this problem for me.

If that doesn't help, you can read this: http://support.microsoft.com/kb/826936
There is a reg hack that goes along with the hotfix listed earlier in this thread.

Ameet Thakkar's picture

This problem may occur if the Volume Shadow Copy service on either the backup server or remote server is disabled.

Kindly refer the following steps to troubleshoot the problem.


1) Title:- "A failure occurred accessing the " (a000fec9 HEX or e000fec9 HEX) is reported during a failed backup http://seer.support.veritas.com/docs/264350.htm



2) Title:-A failure occurred accessing the Writer metadata


http://seer.support.veritas.com/docs/264350.htm

And


3)Title:- How to troubleshoot the error "A failure occurred querying the Writer status" (a000fed1 HEX or e000fed1 HEX) using VSSADMIN http://seer.support.veritas.com/docs/261993.htm

We hope this helps. Let us know if the problem still exists and revert back with the error message.

Ameet Thakkar's picture

We presume that the step mentioned above has solved your problem. Let us know if the problem still exists and revert back with the error message.

David Slamowitz's picture

Please see the second thread posting. The above suggestions were already tried and the problem continues. I have also tried to repair the installation by clicking the repair option when reinstalling Backup exec. No luck yet.

David Slamowitz's picture

Is it possible to find out which of the shadow copiers is not able to be accessed?

David Slamowitz's picture

Here is the error message:

Source Event ID Last Occurrence Total Occurrences
Backup Exec 34113 2/19/2005 7:09 AM 1
Backup Exec Alert: Job Failed (Server: "SWC-PDC") (Job: "Full Backup")
Full Backup -- The job failed with the following error: A failure
occurred accessing the Writer metadata. For more information, click the
following link:
http://eventlookup.veritas.com/eventlookup/EventLo...

David Slamowitz's picture

I am also getting the following message:

Source Event ID Last Occurrence Total Occurrences
Application Error 1000 2/19/2005 7:09 AM 1
Faulting application bengine.exe, version 9.1.4691.0, faulting module
ntdll.dll, version 5.2.3790.0, fault address 0x00008787.


I have tried loading SP1 as discussed in another post to solve this probelm. I get a 'rolling Back' message with inability to install it. I have tried renaming the 'catalog' file as discussed in a previous post and still can't install it.

Are the problems related?

Tommy Eschen Soegaard's picture

I encounter the same problems as above.

0xa000fec9 - A failure occurred accessing the Writer metadata.

I can not resolved my problem with the mentioned solutions in this thread.

I have tried to run the and update on the Veritas 9.0 to 9.1 but still i get the problem. Im running 2003 on remote desktop, and the Shadow Copy service is set to manual, still with the same result.

/Tommy
Scannet A/S

rsoftnl's picture

I too have the same problem. The problem seems to be related to me installing F-Secure for Windows Servers on the system. Does anyone know what the influence of F-Secure on VSS or Veritas could be?

I too have not found a solution yet.

glemmestad's picture

Same error here too. BExec 9.1 SP2. Windows 2003 Enterprise (Exchange 2k3 also running on same server).
Exact same error message. All suggestions in thread tested; same error still received. It appears even when I ONLY back up "System State" under "Shadow Copy Components". Backing up on local machine to Backup-2-Disk.

Thanks

Kind regards,
Even

Hugo Koren's picture

Hi,

I am having the same problem.
System configuration:
Windows 2003 with Exhange.
Veritas 9.1 SP2 with IDR and exchange plugin.

What shows up in my logfile:
Backup - Shadow?Copy?Components Shadow?Copy?ComponentsA failure occurred accessing the Writer metadata.
Witch gives me a backup failed error.

Ajit Kulkarni's picture

Hello,

Kindly update regarding the issue.

Regards.



NOTE : If we do not receive your intimation within two business days, this post would be "assumed answered" and archived.

David Slamowitz's picture

My problem has been fixed. Apparently I had a virus on my server which created a folder called WINIT in the system32 folder. The virus also created a service called 'internet explorer' the writer metadata error was related to accessing this service. Once I removed the virus and the service the error went away. Thanks.

Sandor Nilsson's picture

I have the same problem on two SBS 2003 servers and both of them are running F-Secure!

I disabled the real-time protection and made a test backup of the Shadow Volume and guess what! It worked!

Thanks for the clue mate!

608116404's picture

I have fixed it for the specific error as shown in this thread as below...It only took a month. Thx for the support VERITAS. NOT!

Team, had a niggling backup problem for the last month that came out of the blue one day. The following is the resolution should you ever get this error as was quite difficult to ascertain and repair.

1) you receive the following error:

- Backup - Shadow?Copy?Components Shadow?Copy?Components

A failure occurred accessing the Writer metadata.

2) Apply the following hotfix and reboot the server: (Note: This hotfix is only available from Microsoft through logging a call so I have put it into the following Unisys share).

- \\Aubne1-r1\Shared\TAFE QLD UNISYS\Ops SS\BackupExec\VERITAS_MS_Hotfix-833167\WindowsServer2003-KB833167-x86-ENU.EXE

3) You will then get a new error as below:

- Backup - \\SERVER1

OFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

VSS Snapshot error. Out of disk space or no NTFS volume found while creating snapshot. Add one or more NTFS drives that have at least 100 MB of free space for each volume that will be snapped.


4) Modify the backup job to only backup the system state as shown below:

5) You will also need to modify the root cause of the problem which is the fact that BE is registering that the shadow copy free space for drive C:\ is insufficient, even if it is disabled and not in use, which is quite bizarre but correct after numerous test backups, enabling and disabling etc:

- Set the size of the Shadow copy volume to > 100MB. As in the example I set it to 300MB and worked ok. Again Note: this is even though the shadow copy is set to disabled…

This should resolve the issue and you should get 100% backups from then on in. I will also be posting to the Veritas website as there is no resolution yet on a huge forum article about this problem.

608116404's picture

Sorry, O/S is 2K3 server.

Exchange / SQL/ Antivirus etc is irrelevant...

qzart's picture

I know this Thred is over 4 years old however I just got this same problem and I was able to fix it by setting my C: Shadow copy components to an alternate partition (E:)  

This happened to me shortly after I defragmented the C: Drive