Hi

Please run vssadmin list writers and check Writers status on the client machine. Make sure that all the writers should be in stable state and no errors.

Thanks

Panwar

I did, and all the writers are in stable state with no errors.

Hi Zridet,

I see 2 different backups running at the same time:

File System and also SQL:

Failed to back up G:\

sfatsbkp nsrsqlsv 113 Skip building named instance directory because there are no named instances installed or running on this machine

Can you please tell us what are you backing up?

Are you mixing File system and SQL backups for the same client in the same group?

Have you checked that all writers are present by running vssadmin list writers? Specially ensure that System Writer is in place.

What is the configuration of the client and what is the saveset you have configured?

Have you checked Application and System event logs on the client to see if there is any event ID 25 volsnap? If so then google it, as there are Microsoft fixes for that (you forgot to attach the fix you found, by the way)

Thank you.

Carlos.

Thank you for your answers,

Unfortunately, I cannot reboot the server because it might affect the business since it's a physical server I would need an approval from the other teams and that could take a little while..

Actually I am backing up both file system as well as SQL, yes I have checked all the writers and they are all running with no errors; however, this is what I've found on the System event log as a warning ( the recent one):

The backup operation for the cluster configuration data has been canceled. The cluster Volume Shadow Copy Service (VSS) writer received an abort request.

Sorry for the Microsoft fixe here's the link: http://support.microsoft.com/kb/976461

Thank you,

Guys,

I have the same problem as well. I've done the step provided by sekaraj and even rebooted the server but i'm still getting below error.

1 retry attempted

ERROR: Failed to initialize backup, error=0x80042301: VSS Backup or Restore is not in the correct state for the operation, or the writer is not in the correct state.

89668:save: Unable to set up VSS file system directives. Failed to back up G:\.

:  Failed with error(s)

I used the hardcoded saveset which C and E drive completed succesfully but failed on F,G and H.

This is what I get from vssadmin list writers

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

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {14642c79-7559-49f9-b0a2-bd2596ff8422}
   State: [1] Stable
   Last error: Non-retryable error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {8c2e150e-0fab-4091-bcc8-6ade0e39555a}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {89b2b0bb-8d0b-48ff-ad27-fcde7361c8b3}
   State: [1] Stable
   Last error: Non-retryable error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {f17606eb-2d62-4cb8-b90b-c0ef9d851fce}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {8bae8e6b-a0a6-4e91-bb2d-032651bc15cf}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {01fbc96f-cc3b-4444-90b4-eb9f79dc1772}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {a5533ff6-09ae-4f05-8b9a-718d94df1b6e}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {10ab8211-c917-4ff7-91bb-ab27b7e73379}
   State: [1] Stable
   Last error: No error

Any idea?

I made a troubleshooting document for myself some time ago , I paste it here since it resolves and gives info regarding all strange VSS Errors you can encounter. (Try re-register writers in the section a bit down)

1. VSS Providers

Check to see if there are any non-standard providers that are causing the problem when performing the VSS snapshot. To do this, go to the command-line and execute the following command "vssadmin list providers".

If there are any non-standard providers listed, consider uninstalling them. Note that the Microsoft default providers are generally very reliable, so uninstalling 3rd party providers may solve the problem.

If the "vssadmin list providers" command hangs, it is likely that a newly installed VSS provider is malfunctioning. We have seen this with certain imaging products. In this case, uninstall these products to resolve the issue.

1. 2. Multiple Backups

Ensure that the backup is not running at the same time as another backup as the custom provider may only allow one snap-shot at a time.

1. 3.Corrupted data on the drive to be backed up.

Run CHKDSK on each drive with the /f switch to fix any errors on the disk.
*PLEASE NOTE THIS CAN CAUSE DATALOSS*

1. 4. VSS believes the system is in setup process

Check the status of the system by following these steps:

1. a. Go to the Registry Editor and locate HKEY_LOCAL_MACHINE\SYSTEM\Setup
2. b. Ensure that the following registry values are set to 0:
   • SystemSetupInProgress
   • UpgradeInProgress

1. 5.VSS dlls are corrupted. Re-install the VSS dlls by following these steps (please note the difference between OS and platforms):

=======================

WINDOWS 2003 SERVER x86

Following are the suggested updates for vss and some basic troubleshooting for it:

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

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

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

1 ) Re-register VSS writers if missing. From cmd promt:

• net stop vss
• CD %systemroot%\system32
• regsvr32 ole32.dll
• regsvr32 vss_ps.dll
• Vssvc /Register
• regsvr32 /i swprv.dll
• regsvr32 /i eventcls.dll
• regsvr32 es.dll
• regsvr32 stdprov.dll
• regsvr32 vssui.dll
• regsvr32 msxml.dll
• regsvr32 msxml3.dll
• regsvr32 msxml4.dll

2 ) Stop the Following services:

• Volume Shadow Copy Service. It should be stopped
• MS Software Shadow Copy Provider
• "COM+ event system"
• "COM+ System Application"

3 ) Take the backup of the "Subscriptions" key

• HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions

4 ) Delete the "Subscriptions" key

5 ) Restart/Start the following services

• "COM+ event system"
• "COM+ System Application"
• "Microsoft Software Shadow Copy Provider"
• "Volume Shadow Copy"

6 ) Reboot the machine.

This will “re-build” the VSS Writers , Will fix most writers except “System Writer”

WINDOWS 2003 SERVER x64

1 ) Re-register VSS writers if missing. From admin-cmd promt:

• Net stop vss
• Net stop swprv
• Got to command prompt
• Cd %systemroot%\system32
• regsvr32 /i swprv.dll
• regsvr32 /i eventcls.dll
• regsvr32 vssui.dll
• Vssvc /Register
• regsvr32 ole32.dll
• regsvr32 vss_ps.dll
• regsvr32 es.dll
• regsvr32 stdprov.dll
• regsvr32 msxml3.dll
• Cd %systemroot%\syswow64
• regsvr32 ole32.dll
• regsvr32 vss_ps.dll
• regsvr32 es.dll
• regsvr32 stdprov.dll
• regsvr32 msxml3.dll
• regsvr32 msxml.dll
• regsvr32 msxml4.dll

2 ) Check and Stop the Following services:

• Volume Shadow Copy Service. It should be stopped
• Microsoft Software Shadow Copy Provider. It should be stopped
• COM+ event system
• COM+ System Application

3 ) Take the backup of the "Subscriptions" key

• HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions

4 ) Delete the "Subscriptions" key. Delete just the Subscriptions subkey; leave the EventClasses key.

5 ) Restart/Start the following services:

• COM+ event system
• COM+ System Application
• Microsoft Software Shadow Copy Provider
• Volume Shadow Copy
• 6. Reboot the machine.

WINDOWS 2008 SERVER

More VSS KB’s and troubleshooting for Win2008 can be found here:

http://support.microsoft.com/kb/940349Http://support.microsoft.com/kb/975928

1. Open a admin command promt

• net stop "System Event Notification Service"
• net stop "Background Intelligent Transfer Service"
• net stop "COM+ Event System"
• net stop "Microsoft Software Shadow Copy Provider "
• net stop "Volume Shadow Copy"
• cd /d %windir%\system32
• net stop vss
• net stop swprv
• regsvr32 /s ATL.DLL
• regsvr32 /s comsvcs.DLL
• regsvr32 /s credui.DLL
• regsvr32 /s CRYPTNET.DLL
• regsvr32 /s CRYPTUI.DLL
• regsvr32 /s dhcpqec.DLL
• regsvr32 /s dssenh.DLL
• regsvr32 /s eapqec.DLL
• regsvr32 /s esscli.DLL
• regsvr32 /s FastProx.DLL
• regsvr32 /s FirewallAPI.DLL
• regsvr32 /s kmsvc.DLL
• regsvr32 /s lsmproxy.DLL
• regsvr32 /s MSCTF.DLL
• regsvr32 /s msi.DLL
• regsvr32 /s msxml3.DLL
• regsvr32 /s ncprov.DLL
• regsvr32 /s ole32.DLL
• regsvr32 /s OLEACC.DLL
• regsvr32 /s OLEAUT32.DLL
• regsvr32 /s PROPSYS.DLL
• regsvr32 /s QAgent.DLL
• regsvr32 /s qagentrt.DLL
• regsvr32 /s QUtil.DLL
• regsvr32 /s raschap.DLL
• regsvr32 /s RASQEC.DLL
• regsvr32 /s rastls.DLL
• regsvr32 /s repdrvfs.DLL
• regsvr32 /s RPCRT4.DLL
• regsvr32 /s rsaenh.DLL
• regsvr32 /s SHELL32.DLL
• regsvr32 /s shsvcs.DLL
• regsvr32 /s swprv.DLL
• regsvr32 /s tschannel.DLL
• regsvr32 /s USERENV.DLL
• regsvr32 /s vss_ps.DLL
• regsvr32 /s wbemcons.DLL
• regsvr32 /s wbemcore.DLL
• regsvr32 /s wbemess.DLL
• regsvr32 /s wbemsvc.DLL
• regsvr32 /s WINHTTP.DLL
• regsvr32 /s WINTRUST.DLL
• regsvr32 /s wmiprvsd.DLL
• regsvr32 /s wmisvc.DLL
• regsvr32 /s wmiutils.DLL
• regsvr32 /s wuaueng.DLL
• net start "COM+ Event System"

6 ) COM+ needs to be re-installed. Re-install COM+ by following these steps:

• Backup and then delete HKLM\Software\Microsoft\COM3
• Boot to Recovery console and rename clbcatq.dll to ~clbcatq.dll. Be sure to use the tilde.
• Boot to normal mode and in Control Panel, open the Add or Remove Programs tool, and then open the Add/Remove Windows Components tool. Do not make any changes, just click "Next". This reinstalls COM+.

Steps 3,4,5 and 6 have been obtained from http://forums.msrportal.com/showthread.php?t=5559

7 ) Destination drive is not formatted for NTFS. Check to make sure the backup destination is compatible with the NTFS format. Please view the following article on how to convert a drive to NTFS format: http://support.microsoft.com/kb/307881

Check for disk activity during the time of backup. High disk activity at the time of the snapshot can cause the snapshot manager to determine a cutoff point easily.

Make sure that you have at least 100MB (however the more the better) free space on all drives involved within your backup.

OTHER REFERENCES 

• http://support.microsoft.com/kb/307881 

• http://forums.msrportal.com/showthread.php?t=5559 

Knowledge base articles - known Windows 2003 VSS issues:

A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003 - Last Review: July 2, 2010

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

Exchange VSS backup fails on an Exchange Server 2003 server - February 20, 2010

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

Various issues may occur on a Windows Server 2003-based computer that is running the Volume Shadow Copy Service - April 27, 2010 - April 27, 2010

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

Exchange Server 2003 data backup and Volume Shadow Copy services

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

Knowledge base articles - known Windows 2008 VSS issues:

VSS snapshot creation may fail after a LUN resynchronization on a computer that is running Windows 7 or Windows Server 2008 R2 - November 25, 2009

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

Backup fails with VSS Event ID 12292 and 11 on Windows Server 2008 and Windows Server 2008 R2 - January 20, 2010

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

No VSS writers are listed when you run the “vssadmin list writers” command in Windows Server 2008 R2

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

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

Windows 2008 R2 64-bit backup failed

General VSS articles to review:

http://solutions.emc.com/emcsolutionview.asp?id=esg108377

• The backup process may fail and a time-out error may occur in Volume Shadow Copy Service writers

http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/77862/VSS-Writer-errors-during-backup

• Event ID 9840 or 9607 is logged when a VSS backup operation fails in Exchange 2007 or in Exchange 2003

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

• Best Practices for Using Volume Shadow Copy Service with Exchange Server 2003

http://technet.microsoft.com/en-us/library/aa996004(EXCHG.65).aspx

• Error message: "Not enough server storage is available to process this command"

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

Windows 2008 R2 Action plan for VSS Trouble shooting (General)

Please apply the following resolution plan

• Check your NIC cards configurations on both server and client and make sure to set both server and client network cards to Full or half duplex (no auto negotiate)

Check first this solution to verify your NIC cards configurations :

http://solutions.emc.com/EMCSolutionView.asp?id=esg70774&usertype=C

• Check the name resolution on the server and make sure that server can resolve the client's long name (FQDN) as well as short name and IP address

Check the following solution

http://solutions.emc.com/EMCSolutionView.asp?id=esg50325&usertype=C

• Check the hosts file configuration on both server and client and make sure that the server and client hostname and ip and aliases are configured correctly

Try if you have firewall to configure TCP/IP address and name of the firewall to the client hosts file

• Make sure that server and client can ping each other with ip and hostname

My experience on Windows Server 2012, is that

1. Restarting SharePoint Search Host Controller service removed 'OSearch15 VSS Writer' from the list of writers (as seen with vssadmin list writers).
2. Starting Volume Shadow Copy Service brought 'OSearch15 VSS Writer' back in stable state.

(I still need to figure out my real problem - why 'OSearch15 VSS Writer' is waiting for completion forever.)

Do we need to restart the services on client-server from where we are taking the backup or the networker server.

VSS is a Windows specific method which runs locally. Consequently you must 'repair' the system wherever you have the trouble - the NW client.

@Showkat Bhat 

All the steps related to VSS are to be run on the problematic client machine. Also, no 2 issues might be the same even though the error on the backups are the same. Make sure you look at the event viewer and consult with your windows administrator before taking any steps.