There is no metadata for writer

[jorgene]

Hi,

Backups began to fail on 2 different servers and systems during this weekend.

Task failed Error: There is no metadata for writer '{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}'. --tr:Failed to collect Hyper-V writer document. --tr:Failed to call 'CollectWriterDoc' on server ....

Anyone else got this error message? And i can't seem to find out what's causing this issue. Other then that the
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
is NOT listed on the servers when we run the vssadmin list writers

Both servers are W2012.

[veremin]

Writer <ID> is NOT listed on the servers.

Seems to be the issue, indeed. Furthermore, what can be seen in Application event log?

Additionally, if as the result of "vssadmin list writers" command execution you get totally blank page, then, it means that something seriously wrong with the VSS service on this system and you need to dig into this way.

Thanks.

[jorgene]

I tried to compare the logs since 2013-05-10 (when the error started) but i can't find anything that seems related.
Other that the Hyper-V VSS Writer seems to have dissapered during that date.

These are left:

Code: Select all

C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {23e2e7a6-6489-4241-bd4e-1e0c8ab38532}
   State: [1] Stable
   Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {ea60fde6-d65c-4eaa-b2d2-9e29e7c7a676}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {8c4db1b0-1fb3-4848-a9fc-7eba73e8b47d}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {6d1bef49-5661-4aa9-b051-5a809b03a2d6}
   State: [1] Stable
   Last error: No error
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {7385d674-f749-471b-9577-a7d72b002977}
   State: [1] Stable
   Last error: No error

[jorgene]

Found a solution !

The Microsoft Hyper-V VSS Writer may enter an unstable state if a backup of the Hyper-V virtual machine fails. If you run the vssadmin list writers command, the Microsoft Hyper-V VSS Writer is not listed. To return the Microsoft Hyper-V VSS Writer to a stable state, the Hyper-V Virtual Machine Management service must be restarted.

[veremin]

Glad to hear that you’ve managed to find a solution and thanks for sharing the resolution with the community, much appreciated.

Thanks.

[spundae]

I have the same problem but restarting the service did not solve my issue

[Vitaliy S.]

What does "vssadmin list writers" command show you? Have you had a chance to contact our technical team on this issue?

[spundae]

Code: Select all

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {69a2144c-fd92-40d8-ad40-b2e944af7d24}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {39d31c0e-019b-4335-b592-46ca58e45889}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {dbff0d86-d3f9-4eea-ba18-de71e47d1e50}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {1964c162-88f8-4b23-aa9a-070735591388}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c6518474-e467-47ed-a3fd-ad14d02f4522}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {c4480956-b381-4013-a5c4-05879f1e66f0}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {d4c7182f-e199-4006-b49d-340936462c5f}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a56ac925-7ee7-44b8-85fc-4a57708b1805}
   State: [1] Stable
   Last error: No error

[Gostev]

Microsoft Hyper-V VSS Writer is not listed. Are you running this on Hyper-V server? Please include support case ID for this issue.

[spgsit5upport]

The whole Hyper-V solution is just one big joke.

More failures of random kind that one should accept from "enterprise" product.

Hyper-V host restart (like normally one does with any Windows OS) usually clears the problem, but is less then acceptable!

Seb

[foggy]

Seb, posting such kind of feedback, like you say, is not productive at all. Instead, we would appreciate opening cases with our technical support and providing all the required information for each reported problem, which will allow us to research and address the issues you encounter.

[Gostev]

All signs here point at issue with the Hyper-V itself. However, will be happy to work with Microsoft to research the issue, and have them produce a hot fix... just like we work with VMware in case of issues with vSphere backup. But in order to do this, we need customers with the problem reproducing reliably to open support cases with us. This really does not take much longer than posting on the forum...

[bkruczek]

Trying a backup:

22.10.2015 22:03:47 :: Task failed Error: There is no metadata for writer '{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}'.
--tr:Failed to collect Hyper-V writer document.
--tr:Failed to collect Writer Document.
There is no metadata for writer '{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}'.

Error is reproducable.
Any ideas?
B.K

[foggy]

Bernd, please include support case ID when posting about technical issues (as explained when you click New Topic), otherwise this thread will be deleted.

To clarify, are you running the backup job against Windows 10 VM?

[bkruczek]

Yes, the VMs are Windows 10 VMs. With Veeam 8.0 Update 3 Veeam runs on Windows 10 and recognizes my VM infrastructure.

[foggy]

Then please check this thread for some hints and contact support for further investigation.

[bkruczek]

Anything new?

[foggy]

What do our engineers say regarding this issue?

[lhooipg]

Hi,

I'm facing the same issue as well. My Support case number: 01099297

11/4/2015 11:37:12 AM :: Task failed Error: There is no metadata for writer '{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}'.--tr:Failed to collect Hyper-V writer document.--tr:Failed to collect Writer Document. There is no metadata for writer '{66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}'.

And yes I'm running the backup job against windows 10 VM.

Any solution for it? TQ

[foggy]

Jeffrey, have you checked VSS writers state and tried to restart Hyper-V Virtual Machine Management service, as mentioned above?

[cbruscato]

I have reproduced this issue on Windows 10 Enterprise Insider Preview Build 11082.

The Hyper-V VSS Writer is not present when running "vssadmin list writers"
Restarting the Hyper-V Management Service had no effect - the backup still failed, and the Hyper-V VSS Writer was still missing.
Machine Name: FFL-MDT01

Complete Server Logs:
http://1drv.ms/1Ps6ErK

Support Case ID: 01250222

Edit:
To clarify, the Hyper-V Host is Windows 10 Enterprise Insider Preview Build 11082, the Guest VMs to be backed up are running Windows 2012 R2 Datacenter.

[veremin]

Actually, we only support server OS as hypervisor platform. Thanks.

[mbrinkho]

Didn't see any resolution for this other than "restart the vmms" and that only worked for one day. I do have a case open, Veeam Support - Case # 01709678 - Backups Failing - No Metadata for Writer. This only started appearing for us after upgrading to v9.

[foggy]

I cannot see the resolution in the support cases provided in this thread as well, so please continue working with your engineer on this. Thanks.

[cprime@medmarc.com]

For those with this issue, do you have a vulnerability scanner running on your network? We run a Nexpose/Rapid7 solution that scans the network once per week and the timing seems to overlap with the backup failures and the Hyper-V Virtual Machine Manager service running into issues.