https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMjUzIiwiaGFzaCI6ImU5MzE4MDc2LTYxNjMtNDg4OS1iODVkLTU4NWY1MjlmZDQ2OSJ9
1-800-691-1991 | 9am - 8pm ET
EN

No VSS Writers listed in Windows 2003

Challenge

You may encounter the following error in the job log files:

Freezing guest operating system
VSSControl: -2147467259 Backup job failed.
Cannot collect writers metadata.

VSS asynchronous operation is not completed. Operation: [Gather metadata]. Code: [0x80042318].

When running the command "VSSADMIN LIST WRITERS" nothing is displayed in the list on the affected guest. The behavior is consistent even after a reboot, applying Volume Shadow Copy Service (VSS) update package for Windows Server 2003, manually starting the VSS Service, and manually re-registering the VSS Components. The server was capable of performing VSS enabled backups in the past.

Cause

The COM+ subscription information for VSS writers stored in the registry under HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key may become corrupted.

Solution

Please follow the steps outlined in the knowledge base below to resolve the issue.

http://support.microsoft.com/kb/940184/en-us

KB ID:
1253
Product:
Veeam Backup & Replication
Version:
5.x
Published:
2011-09-30
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later