We help IT Professionals succeed at work.

Windows 2008 R2 VSS error 12292 and 13

xpandit
xpandit asked
on
I have been receiving this errors when I try to run WSB on our Windows Server 2008 R2. The server is installed with all the latest updates

Event 11292  :
Log Name:      Application
Source:        VSS
Date:          6/14/2010 6:00:37 PM
Event ID:      12292
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:Volume Shadow Copy Service information: The COM Server with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} 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
   Obtaining provider management interface

Context:
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Class ID: {00000000-0000-0000-0000-000000000000}
   Snapshot Context: -1
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}

And Event 13:

Log Name:      Application
Source:        VSS
Date:          6/14/2010 6:00:37 PM
Event ID:      13
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} [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
   Obtaining provider management interface

Context:
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Class ID: {00000000-0000-0000-0000-000000000000}
   Snapshot Context: -1
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
Comment
Watch Question

Distinguished Expert 2018

Commented:
The first thing you should know is that VSS is simply a service that MS built into windows to assist backups. If an application needs to do something "special" for backups to work then that application can install what is called a "VSS Writer" that does those special tasks. When a backup is run, VSS just goes down the list of installed VSS writers and runs each one.
The error you are seeing mean that you have a VSS writer misbehaving. This could be an MS writer or one installed by a 3rd-party application. So the first step is to determine which writer is not working properly.
In your error messages, you'll notice that each event has a "provider ID."  In this case, the provider ID is the same for both events, so it is the same VSS writer causing both errors.
So the next step is to run this command on the server having problems from the command prompt:
vssadmin list writers
You will get a list of VSS writers installed. Each one has an ID in the list. Match the provider ID from the error with the VSS writer ID, and you've got your failing VSS writer. That'll give you a starting point to google for known error with that writer or application, and you can post that back here to see if anybody is familiar with issues or has a fix. But since each app is different, so is each fix. We need to know what is failing first.

Author

Commented:
I have attached a screen shot of the results that I got when I ran vssadmin list writers.
vss.PNG
Distinguished Expert 2018

Commented:
your screenshot barely shows two writers, and the name of a third is visible at the bottom, so this isn't a complete picture. It'd be better if you can cut and paste the output of the command window as text.
or do a
vssadmin list writers > output.txt and then you'll have a text file to cut and paste.

Author

Commented:
My humble apologies below is the text I copied, thanks for your quick response
 
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
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: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {86b3e02b-e20c-4702-90c8-04c49a665043}
   State: [5] Waiting for completion
   Last error: Unexpected error
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {2781157c-1fd5-4aa5-ba33-1f69e98906b6}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {b4dc84a5-8403-4f9b-b0ff-cc8e733a49d6}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {7aa6ab7b-59b5-4b6f-ab44-eed89292ef1e}
   State: [1] Stable
   Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {3b68d038-a0a9-41a8-9b80-c293249035ec}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {f73f08d9-058b-4f7a-b4a4-03c04089b00d}
   State: [1] Stable
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {0fe6dd9c-be86-4136-b5a9-471b41bfe609}
   State: [5] Waiting for completion
   Last error: No error
 
Distinguished Expert 2018

Commented:
Looks like your Hyper-V writer is throwing an error. Check the event viewer in the parent OS for any Hyper-V related errors with snapshots, paysing virtual macines, etc.
Commented:
we gave up with this eventually and changed our backup strategy.
I'm having the same problem that started two days ago. Backups ran great for 2 years and out of no where I get this error.
Distinguished Expert 2018

Commented:
@itconsultant: So open a new question and post as much detail as you can regarding errors, event logs, etc. This question has been closed.