Backup Exec 2010 VSS failure

In command line type: vssadmin list writers
What is the outcome of this command?
It could be simple conflict between VSS services.

Ran vsadmin list wirter command and if any writer fails
kinley install latest windows update and VSS update .
It can be easily downloadable.

Thanks

Please revert.

Hi Experts thanks for your response.

No errors are reported by that command.

Look forward to hearing from you again.

Show me the output of vss admin list writers command

Are you taking backup of the remote server or direct D2D. If it is remote server then, have you installed the correct version of remote agent of backup exec?
Also, Make sure that the job setup doesn't have any invalid selecton list, if any invalid selection list available the bacup job will get fail. Invalid selection list shows something like VPHOme/*..(name may be diffrent)

Please let us know your findings for further assist.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

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: {3ec87ca5-6b9d-44a5-9aa8-24a598001ed2}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {6598e1c5-1ce7-4c3a-80dc-e60ccfeb481e}
   State: [1] Stable
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
   Writer Instance Id: {0cf70467-2d71-493d-af71-8f906e874a9a}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {53a70632-4f38-4f06-9bb3-0b7df66fec18}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {84451a80-5076-4eb5-8e2b-6b971771e032}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {e580d015-0c4f-4249-84ac-78c9fe3c5c98}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {d5605928-1d35-4165-88aa-bf082ca0de39}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {8eb9a5b0-3e02-424c-9dbc-8f3b3a5ed0f2}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {16dbf9da-03f8-44f1-97df-b96af60a0e96}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {0a14a5a4-046b-4a2b-a4b6-160c5ef304a1}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {3d838b7e-bec9-4e90-8f11-9afe2001f3ff}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {38e388cf-8648-41b2-87b3-8ebd6d347d9b}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {c838c988-5481-467b-9e47-c83c712dce59}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {9ec9f423-742a-48d3-b5e7-8405eb2f4ddc}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {524ea6ae-7636-4b07-970a-6be7f8de5110}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {081ac089-eaf2-44ef-8163-c5cff0df968e}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {6bac7b61-3fc3-4041-b9e0-f5d8d8af9a41}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {2100df31-642c-4c89-bdcf-85f5b44997e9}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch4 VSS Writer'
   Writer Id: {35500004-0201-0000-0000-000000000000}
   Writer Instance Id: {6e2ae867-49c6-4a21-8a16-66200bb047a0}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {152b60da-5ddd-44eb-a4f2-ac399d7db231}
   State: [1] Stable
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {d9db3cf6-8988-479b-b249-ce0c3771af18}
   State: [1] Stable
   Last error: No error

Hi Experts,

Please see above post for the result of vssadmin list providers.

The server is not a remote server. Additionally VSS is not enabled on the secondary drives(Exchange and Data). It is enabled on the C: drive but it still does not backup correctly.

Also the correct agents are installed as we had one successful backup after the product was installed; however the SharePoint agent was not installed so it was not a full backup.

The selection list also appears to be fine.

Look forward to hearing from you.

Can you go to services and see if Microsoft VSS service is started and running?
Or just save system information file and give a link to it for me.
* select "Start"->"Programs"->"Accessories"->"System Tools"->"System Information" menu item
* select "File"->"Save"
* attach it to your reply

The solution was found from symantec forum..

Actually this was what I going to tell you. That's why I asked you for system info file where I could see which VSS service was started and used.

Hi Noxcho,

The issue has occured again over the weekend and it is still using the Acronis VSS from what I can see from the error messages in the event log.

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {79079d5c-ef20-4952-b9fc-cfd443b38641} and Name SW_PROV is [0x80040154, Class not registered
].

Operation:
   Obtain a callable interface for this provider
   List interfaces for all providers supporting this context
   Delete Shadow Copies

Context:
   Provider ID: {f782463b-33bb-4043-ad8d-60b728d26a6c}
   Class ID: {79079d5c-ef20-4952-b9fc-cfd443b38641}
   Snapshot Context: 0
   Snapshot Context: 0
   Execution Context: Coordinator


The provider ID points to Acroniss VSS. How can we stop this provider from running as default.

Also found this error in the event viewer.

An error occurred while processing a B2D command.
 Drive: InitWrite() CreateFile failed (M:\innate backup\B2D000294.bkf).  Error=32

Look forward to hearing from you.

The only solution I ever have worked for this problem is removing Acronis VSS provider. If you do not use Acronis software on this machine then remove the provider.
The issue is caused actually by both Acronis and Symantec. The first did not uninstall the components correctly and Symantec does not know how to use their own or Microsoft VSS provider by default.

But somewhere in the system must be telling it which provider to use. Additionally I turned on AOFO and pointed it to the microsoft vss and still failed.

For now I will work on removing the Acronis VSS

Look to hearing from you.

Yes, that was my understanding as well. There must be somewhere prioritizing which VSS provide should be used by default in system. But really I could not find it. Moreover I posted a question here on EE and no answer was given.
There are more software with similar problems  like Show Protect. If you have installed it for example and later install Symantec then you will use VSS provider by Shadow Protect.
The problem is that Symantec uses Microsoft VSS provider and Acronis + Storage Craft Shadow Protect have written their own VSS providers. And they do not uninstall it properly sometimes.
I investigated this problem while working with Paragon Drive Backup 10 which uses Microsoft VSS as well.
That's why I wrote - the only solution is remove Acronis provider.

Sorry, it is not Show Protect but Shadow Protect.