Microsoft hyper v vss writer non retryable error

Microsoft hyper v vss writer non retryable error

Вопрос

Win2012R2, fully patched! It was all running smoothly over the last months, but suddenly: An errror in VSS making my Backup stop working

I reboot the server, all vss writers are OK

I try a single Backup (ArcServe) procedure and after the failure:

Writer name: ‘Microsoft Hyper-V VSS Writer’
Writer Id: <66841cd4-6ded-4f4b-8f17-fd23f8ddc3de>
Writer Instance Id:
State: [8] Failed Last error: Non-retryable error

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
PrepareForSnapshot Event

Context:
Execution Context: Writer
Writer Class Id: <66841cd4-6ded-4f4b-8f17-fd23f8ddc3de>
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID:
Command Line: C:Windowssystem32vmms.exe
Process ID: 2664

Volume Shadow Copy Service error: Unexpected error calling routine IMultiInterfaceEventControl::GetSubscriptions. hr = 0x80010108, The object invoked has disconnected from its clients.
.

Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: BackupShutdown [0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.

Источник

Microsoft hyper v vss writer non retryable error

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Anyone have an issue where you cannot backup the windows 2008 host with Hyper-V?

When the backup starts my VMs go to saved/running/saved/running and get stuck in that loop until the Windows backup fails after 30 minutes

All errors in event logs point to VSS and when I run the «vssadmin List writers» command I get this:

Writer name: ‘Microsoft Hyper-V VSS Writer’
Writer Id: <66841cd4-6ded-4f4b-8f17-fd23f8ddc3de>
Writer Instance Id: <849ac9f6-2996-440b-b26d-1c3c9ab49876>
State: [8] Failed
Last error: Retryable error

I have tried rebooting and that has not solved the issue.

I need to install the RTM Hyper-V update- but I would like to get a successful host server backup before I do that.

I was thinking of aside from performing flat file copies of the Guests while they are shutdown- that I maybe able to get a good backup if all the machines are shutdown- but I am not sure if the Hyper-V VSS writer is updated with the RTM version of Hyper-V or if there are some other things I could do to solve this.

I have 2 other machines configured just like this one without issue.

Answers

I am afraid this error message cannot help. Please take a look at the Event Viewer, at Windows LogsApplication, see if any errors or warnings exist relating to VSS or Backup.

If possible, please also try shutting down these VMs and then try the backing up so that we can narrow down the root cause. In addition, shutting down these VMs, then rebooting the host machine may resolve this issue.

A very possible cause is that the virtual hard disk of the VM is being written when you performed the backup, and by some unknown reasons, it cannot reach the «consistent» state. The normal procedure of backing up a running VM is saving/restoring the VM, by using the Windows Server Backup feature, even when you have IS installed. This is to ensure the disk is in a «consistent» state and, this procedure should work well in common scenarios.

If possible, would you please try the following steps to see if it can help? This is one method to ensure running VMs can be backed up via Windows Server Backup. However, we do not recommend this method at this time. If you want to back up the running VM, use the System Center Data Protection Manager (DPM, fow now it doesn’t support Hyper-V, but will come with SP1) or some other third-party backup applications that can work with Hyper-V VSS writer.

Note that you should always back up the Registry before changing it so that once you encounter any problems, you can restore it.

1. Open the Registry Editor (regedit.exe).

2. Navigate to the following registry key:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion

3. Create a new registry key, under the CurrentVersion key, and name the new key WindowsServerBackup .

4. Create a new registry key, under the WindowsServerBackup key created above, and name the new key Application Support .

5. Create a new registry key, under the Under the Application Support created above, and name the new key .

Volume Shadow Copy Error 0x800423f4 — writer error: non retry-able

Description

This error occurs when one of the VSS writers is not in a working state and causes the snapshot process to fail.

Resolutions for Hyper-V

The solutions below are for Hyper-V Server and Hyper-V guest (VM) backups. Solutions for other types of backups are in the next section.

When troubleshooting problems with Hyper-V backups, it is important to first determine which guest/s is causing the error. You can do this by checking the Hyper-V VMSS logs, as shown below. You may also be able to identify the guest from the information in the backup report. If you are not able to identify the guest, try backing up the guests one at a time until the errant guest is found.

The guest causing the error can be confirmed by running the backup again without that guest and checking that the backup runs without errors. You can also try a VSS backup on the guest itself using a trial version of BackupAssist. The success or failure of this backup will help to further narrow down what could be causing the error.

If the problem is with backing up data within a guest, will you need to open the Event Viewer inside that guest and review the VSS log entries. These may identify the exact cause of the VSS error.

Solution 1 — Re-initialize the guest’s Volume Shadow Copy Requester service

This solution applies when error 0x8004230F is mentioned in a Hyper-V-VMMS event log entry with id 10150 for a specific guest, or when this error number is shown during a failed VSS backup inside a guest.

1. Log into the Hyper-V guest (VM).
2. Delete registry key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSProviders{74600e39-7dc5-4567-a03b-f091d6c7b092}.
3. Restart the service ‘Hyper-V Volume Shadow Copy Requester’ or restart the guest.

Warning: Changes to the registry should only be performed by an experienced Systems admin. Mistakes can render the system inoperable.

Solution 2 — Change the Production checkpoints to standard

This is a known issue for pre-2016 Domain Controllers running in VMs on 2016 / Win10 Hypervisors. The problem may be related to the new Hyper-V Production Checkpoint architecture.

To resolve this problem, in the VM’s settings, change from Production checkpoints to Standard on guests that are domain controllers running pre-2016 OS, when the Hyper-V host is running Windows Server 2016.

Solution 3 — Review the VMMS logs

This error can occur if there is a VSS problem within the guest operating system preventing the Hyper-V VSS writer from successfully backing up the guest from the host level. The cause can be found by looking for errors in the Event Viewer, particularly VSS or SPP events, which will most likely be the cause of a failure within the host. To do this, open the Event Viewer on the guest machine, however instead of browsing to Hyper-V VMMS, browse to Windows Logs > Application.

Solution 4 — Run a backup with «Backup (volume checkpoint)» integration service temporarily disabled

This solution applies when error 0x80070490 is mentioned in a Hyper-V-VMMS event log entry with id 10150. This has been seen on hosts running Windows Server 2012 R2 and Windows Server 2016.

To resolve this error, temporarily disable the «Backup (volume checkpoint)» integration service and run a test backup of the guest. If this succeeds, re-enable the service and the next backup of the guest should continue to succeed.

Resolutions for other backup types

Solution 1 — If multiple backup solutions installed

Many backup solutions have their own proprietary snapshot manager which can cause conflicts with other backup solutions installed on the system.

If you have (or had) more than one backup program installed on your system, disable/uninstall all of the programs except for BackupAssist, and run the backup job again.

It is best practice to only have one backup solution installed at any one time.

You should also run a registry cleaner after the other backup solutions have been uninstalled: https://www.backupassist.com/blog/support/how-to-resolve-a-ba910-volume-shadow-copy-error-0x80004230/.

Solution 2 — If the problem is a failing VSS writer

If the reason for the error is a failing VSS writer, it’s recommended to find which one is causing the issue.

To do this, open an elevated command prompt and run the following command: vssadmin list writers

This will provide an output of all VSS writers known to Windows on that machine. Look specifically for the Last error detail and anything that does not show No Error is most likely to be the cause of the error.

Solution 3 — If there are Volume Shadow Copy errors within Event Viewer

VSS can write additional information to the event logs of your system which will provide information to help resolve the issue.

Open Event Viewer by clicking on Start > Run > Eventvwr to see if there are any specific VSS warnings or errors being generated from the system during the backup process. You will specifically want to look at the Application and System logs.

Solution 4 — If the problem is that the SQL Agent is not allowed to run

This is generated because the SQL writer has conflicts with the SharePoint VSS writer.

It is known that removing the GUID entry from the following registry key resolves this error:
HKEY_LOCAL_MACHINE/ SOFTWARE/ MICROSOFT/ MICROSOFT SQL SERVER/ SHAREPOINT/ SQLSERVERAGENT

Stopping the SQL VSS Writer Service can also resolve this error.

To do this, browse to Administrative Tools > Services and find SQL Server VSS Writer in the list. Once located, click on Stop to the left hand side of the Services screen.

Solution 5 — If the problem is that the Sqlvdi.dll file is unregistered on the system

This error is generated if there is an issue with the file Sqlvdi.dll on the system.

Microsoft outline how to resolve this for Windows Server 2003 in their KB: https://support.microsoft.com/en-us/kb/830575.

Microsoft outline how to resolve this for SBS 2011 and Windows Server 2008 in their KB: https://support.microsoft.com/en-us/kb/2615182

Are you stuck with hyper-v VSS writer failed? We can help you fix it.

This error occurs when the VSS writer service failed.

At Bobcares, we often get requests regarding Hyper-V as a part of our Server Management Services.

Today let’s discuss how our Support Engineers resolve Hyper-v VSS writer failed for our customers.

Causes for Hyper-v VSS writer failed

Volume Shadow Copy is a windows service that helps capture and creates snapshots. The VSS writer tells the backup tool how to back up the data.

Causes for the error is when VSS writers fail. There are multiple reasons for the VSS writer to fail.

One of the common reason is when two or more resources try to use the writer at the same time.

Thus, to resolve the error we restart the service or reset the VSS WMI writer.

Let’s discuss how our Support Engineers resolve this error for our customers.

How to fix Hyper-v VSS writer failed

Recently one of our customers contacted us regarding writer failure error. Let’s now discuss how our Support Engineers resolve the error for our customers.

Restarting failed writer service

First, we open the command prompt with administrative privilege.

Then we find out the failed writers using the command

vssadmin list writers

Then we find the service corresponding to the VSS writer.

After that, restart windows service corresponding to the writer. After restarting the service we check the writers.

The VSS writers were all stable.

Thus, it resolves the error.

Re-register the writers

Recently one of the customer contacted us regarding the same error. We restarted the service but still, the error was occurring. The available option is to reset the WMI Writers. Let’s discuss how our Support Engineers resolve the error for our customer.

To re-register the VSS WMI Writer we open the command prompt with administrator privileges.

We move to the directory wbem using the command

cd %windir%system32wbem

And we use the below commands to reset the WMI writer.

for /f %s in ('dir /b *.dll') do regsvr32 /s %s

wmiprvse /regserver

winmgmt /regserver

Thus, we reset the VSS WMI writer to resolve the error.

Service not running in the client-server

One of the common reasons for this error to occur is that the service might be not running. Thus, our Support Engineers start the service from the Hyper-V manager.

To restart the service from Hyper-V Manager. We Open Hyper-V Manager.

Then we click on the name of the server. In the Actions pane, we click Start Service.

Thus, it resolves the error.

[Need assistance with Hyper-V error – We can help you fix it]

Conclusion

In short, we have discussed the causes for the ‘Hyper-V VSS writer failed’ error to occur. Also, we have discussed how our Support Engineers resolve the error for our customers.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

1. When VSS fails there is usually an indication in the image or backup log file which shows in the Macrium Reflect log:

   

   

2. Alternatively, the main VSS log can be seen as an option under the log view:

   

3. If required, and you are using the Macrium Reflect email component, you can send these logs via email. Right click the log entry.
    
4. select Send backup logs via email.
    
5. A common error is Failed to Create Volume Snapshot followed by a hex result code. The result code is an error code from VSS. Googling VSS + Result Code often comes up with a solution to the VSS problems

You may also see:

Backup aborted! - Unable to open file handle for '\?GLOBALROOTDeviceHarddiskVolumeShadowCopyxxx'
The process cannot access the file because it is being used by another process.

This may be associated with a ‘VolSnap’ error in your Windows logs.

VSS uses writer components to ensure that the file system is in a stable state when creating your disk image. For example, SQL database writers ensure that all transactions to databases are complete before allowing the shadow copy service to continue. Windows includes a VSS administration program that can list the status of all VSS Writers you have on your system.

Open a command prompt and type ‘vssadmin list writers’. In Vista/7/8 and Servers 2008 and later, make sure you start the command prompt with elevated privileges. This will list all your VSS writers with their current state and last error. (Link to instructions on creating elevated command prompt at bottom of tutorial).

Typical output:

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:Windowssystem32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {4e66d2f2-136c-434b-9a67-234a3b5d38e6}
State: [1] Stable
Last error: Non-retryable error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {9c9a72d9-70f4-414d-88e2-9894fd7f13ca}
State: [1] Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {ac62d67f-bc4f-4ae0-90d1-9fc058a8880f}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {0b6a11ac-b009-44ec-a9f2-f3b94de74c7d}
State: [1] Stable
Last error: No error

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {f9626a21-0848-4fca-a7a0-287ce50ebec7}
State: [5] Waiting for completion
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {04a208b8-943b-425d-a694-6cc179ab6d46}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {6a4ffe24-b297-4602-b04b-0bf63caa5cd5}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {894ebce3-7aec-4e9b-8b38-36d3eb624145}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {dbe2fb09-898f-4b60-8539-3ca1e6cc4b67}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {06504311-56ee-4f9e-82e6-1dc08ff7eb2c}
State: [5] Waiting for completion
Last error: No error

Writers with an error state or where the last error isn’t ‘No Error’ are probably causing a problem.

Look for messages in your Windows logs.

When VSS fails you will always get a corresponding message in your Windows event log.

1. Right click on ‘My computer’
2. Select ‘Manage’
3. Expand the ‘Event Viewer’ node
4. Look in the ‘Application’ message node for error messages  relating to ‘VSS’, ‘Shadow Copy’ or ‘VolSnap’.
   
5. If you find any messages then these with give you an ‘Event ID’ and sometimes a ‘Result Code’ or ‘hr’. These two pieces of information can generally pin point the cause of your VSS failure. Try Googling the Event ID(s) and Result Code(s) for more information.

Make sure that the VSS service isn’t disabled

Changing the startup type of the VSS service and rebooting can often resolve issues.

1. Right click on ‘My Computer’.
2. Select ‘Manage’.
3. Select the ‘Services’ tree node.
4. Right click on ‘Volume Shadow Copy’
5. Select Properties
6. Change the startup type to ‘Automatic’
   
7. Reboot

Re-register the VSS components

Sometimes re-registering VSS core components can fix errors. Copy the following commands to Notepad and save the file with a ‘.bat’ extension. Run the .bat file by opening a command prompt and entering the .bat file name.

cd /d %windir%system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

Resources

http://en.wikipedia.org/wiki/Shadow_Copy
http://technet.microsoft.com/en-us/library/cc785914.aspx

VSS error articles:

It is very probable that others have had a similar problem to you, so use Google as much as you can to find potential solutions. If all else fails you should contact Microsoft support for a resolution.