I ran "vssadmin list writers" and all I got backup was:
vssadmin 1.1 - Volume Shadow Copy service administrative command-line tool
(c) cokpright 2001 Microsoft Corp.
Main Topics
Browse All TopicsI installed Backup Exec 12 and it ran fine at first. Now I am getting the error message:
Backup- \\SErVER\Microsoft Information Store\First Storage Group V-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time. Try running the job later.
VSS is running. Before this error started, I install Mozy offsite backup, however I still get this error when I stop the Mozy service so I am not sure if that is part of the problem.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Did it get back to the command prompt immediately after echo-ing those lines, or did the command just sit there after this without returning back to the prompt. If it did not return to the prompt, how long did you wait?
Try following article http://support.microsoft.c
Then I'd also apply http://support.microsoft.c
Did you get any errors when you ran all the commands to re-register the DLL's?
Event 20 again can be solved by re-registering the DLL's (http://support.microsoft.
Check if this applies: http://support.microsoft.c
You may want to consider reinstalling msxml 3.0 and 4.0.
Also check the different suggestions in http://www.eventid.net/dis
ajdratch: try the following from a command prompt. I've seen it work several times where "vssadmin list writers" produces an empty set.
1.) CD C:\Windows\System32
2.) Net stop vss
3.) Net stop swprv
4.) regsvr32 ole32.dll
5.) regsvr32 vss_ps.dll
6.) Vssvc /Register
7.) regsvr32 /i swprv.dll
8.) regsvr32 /i eventcls.dll
9.) regsvr32 es.dll
10.) regsvr32 stdprov.dll
11.) regsvr32 vssui.dll
12.) regsvr32 msxml.dll
13.) regsvr32 msxml3.dll
14.) regsvr32 msxml4.dll
Try vssadmin list writers again. If it still produces an empty list, reboot the server and try again.
My bad. I registered the DLL's in http://support.microsoft.c
Since it still did not work, I did what I should have done the first time, follow the directions EXACTLY as shown. When I did that, it work, go figure!
Business Accounts
Answer for Membership
by: honmapogPosted on 2008-02-29 at 12:17:20ID: 21017138
If you're backing up Exchange, you should probably disable AOFO.
om/kb/9403 49.
If Exchange is backed up in the same job as other resources that do need AOFO, you should probably create 2 different jobs. One with Exchange only and no AOFO. One with the other resources and AOFO enabled.
Otherwise make sure that no other applications are creating snapshots at the same time on the Exchange server.
On the Exchange server, also run "vssadmin list writers" on the command line. Make sure all writers are stable with "no error". If this is not the case, reboot the server.
Install VSS hotfix http://support.microsoft.c