Question : Backup Exec VSS error

Good day Experts..

I have been getting the following error in Backup Exec when the backup job fails:

"Completed status: Failed
Final error: 0x8000ffff - Catastrophic failure
Final error category: Other Errors

For additional information regarding this error refer to link V-79-32768-65535"
 
and..
 "AOFO: Initialization failure on: "Search instance\Index files 1 (Server\4d5e14c0-813e-48f3-a06f-6de4107e5925)". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11253 - Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure". To make sure that the VSS is not disabled and can be started, click Control Panel, and then click Administrative Tools. Open the Services, and start Volume Shadow Copy. Check the Windows Event Viewer for details."

There are also two Windows Event log error s that pop up when the Backup job fails  :

"Volume Shadow Copy Service information: The COM Server with CLSID { } and name Coordinator cannot be started. [0x80070005]

Operation:
   Instantiating VSS server"

and..

"Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x80070005.

Operation:
   Instantiating VSS server"

We are running Windiws SBS server 2008 with Backup Exec 12.5 , the error pops up when backup up the Exchange Infomation Store. Also you get the folowing error when trying to select System State and Volume Shadow copies  for in the backup job:

"An error occured initializing the Volume Shapshot service."

The VSS , Microsoft Shadow Software Copy Provider and Com+ Event System service are all started and running.

Any help in finding a solution to this woruld be appriciated ,
Thanks
Quincy

Answer : Backup Exec VSS error

Open Backup Exec, Click Tools > Wizards > Advanced Open File Option Wizard.

Select your server and lets try a domain admin account as the logon credentials. If that fails can you check the permissions on your exchange information store, make sure this account has at least readd permissions over it?