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

Error 0008821

Created: 06 Sep 2012 | 8 comments

Hi Folks. 

Running BE 2010 R3 on 2008 R2 64. Nothing special. 

Trying to backup locally presented luns to tape using a Quantum 5 drive. 

I am receiving error 0008821. In essence jobs get stuck and freeze untill BE services restart or server is restarted. 

Error code follows: 

e0008821 - Job was recovered as a result of Backup Exec RPC service starting. No user action is required.
For additional information regarding this error refer to link V-79-57344-34849

Have tried the following:

  1. http://www.symantec.com/business/support/index?page=content&id=TECH56516 DCOM permission.
  2. http://www.symantec.com/connect/downloads/re-register-vss-windows-server-2008 Reregister vss

  3. Reboot - thats a given.

  4. The one interesting thing is when running assadmin list writers nothing shows up. 

Ideas, recommendations?

Comments 8 CommentsJump to latest comment

VJware's picture

Any errors under the event viewer ?

Additionally, pls have a look at this KB - http://www.symantec.com/business/support/index?pag...

George NZ's picture

I am receiving two VSS errors which look strangely the same:

Event ID:13

Volume Shadow Copy Service information: The COM Server with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} and name SW_PROV cannot be started. [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
 
Operation:
   Obtain a callable interface for this provider
   Add a Volume to a Shadow Copy Set
 
Event ID: 12292
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
]. 
 
Operation:
   Obtain a callable interface for this provider
   Add a Volume to a Shadow Copy Set
 

VSSADMIN LIST WRITERS now produces:

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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {15c82dee-d44e-4325-a3a3-f87ec5afb412}
   State: [1] Stable
   Last error: No error
 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {e277d4a8-df81-4a91-8b5d-9f35dd8077a0}
   State: [1] Stable
   Last error: No error
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {08ea1d7a-4d40-4bcf-9c2a-55d7038ac38c}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {c30939e8-89a4-4114-9271-93b06d067e69}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c0a93236-8c2f-484c-bb88-94003b86b14e}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {1525030f-4a83-46a4-b62a-a2058367f91f}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {bda4f5b7-cd2c-452b-b321-489b32a664c9}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {e9e5a56b-3763-4dc6-b0d2-a471e46bfe84}
   State: [1] Stable
   Last error: No error
 
Still cant make heads or tails of this. 
Backup_Exec's picture

Hi

Please check you have followed the link below

http://support.microsoft.com/kb/2009513

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

George NZ's picture

Hi Sameer, 

Thank you for your recommendation but the string seems present already so does not need changing. 

 

Any further help is welcomed. 

VJware's picture

Try re-registering this dll using this command -

regsvr32 /i%windir%system32swprv.dll

pkh's picture

What is the basis of your recommendation and does it conflict with what Colin Weaver said below?

https://www-secure.symantec.com/connect/forums/backup-completing-exception#comment-7675131

VJware's picture

On basis of this KB - TECH140909

And thanks for pointing this out, let me re-check if this KB requires further editing or not.

George NZ's picture

Thanks for the responses chaps, however before reading the response PKH I ended up reregistering the dll with an error of 0x81000203.