windows 156 error

I think you should focus your attention on "'vssadmin' is not recognized as an internal or external command,
operable program or batch file."

 

Any vss errors in event viewer?

Hi Riaan,

Thanks for your response, yes the "vssadmin" command not being recongize is odd.

 I found the following error in the event viewer.

The shadow copies of volume C: were aborted because of an IO failure on volume C:.

source: volsnap

 

Riaan,

I looked up the vssadmin issue I had to run it from the>>>> C:\windows\system32 directory

C:\WINDOWS\system32>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001 Microsoft Corp.

 

Writer name: 'System Writer'

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Instance Id: {609f2821-f0a8-4b30-b862-135405b1d7ec}

   State: [1] Stable

   Last error: No error

 

Writer name: 'MSDEWriter'

   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

   Writer Instance Id: {2499f2a8-b002-4de5-b0a0-a7edb9ef661d}

   State: [1] Stable

   Last error: No error

 

Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Writer Instance Id: {94248bad-fe45-4fb6-9e28-d9ef9fe21987}

   State: [1] Stable

   Last error: No error

 

Writer name: 'COM+ REGDB Writer'

   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Writer Instance Id: {807a2a38-21f5-493b-9ce7-faae8b15d914}

   State: [1] Stable

   Last error: No error

 

Writer name: 'Event Log Writer'

   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}

   Writer Instance Id: {2d0ab3e0-f172-440f-9f1a-b31fb2d3726d}

   State: [1] Stable

   Last error: No error

 

Writer name: 'IIS Metabase Writer'

   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

   Writer Instance Id: {e5863d6a-cd7c-48aa-9012-d72524ee6f2a}

   State: [1] Stable

   Last error: No error

 

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {95e118c8-9c54-43dc-a2d9-33efa834b1d0}

   State: [1] Stable

   Last error: No error

 

 

 

I believe volsnap is from netapp? You using netapp in the env? If so try http://www.symantec.com/docs/TECH156732

 

 

Riaan,

This is a Client's server I am not sure if they are using Netapp or not. Is there a way to check the server to see if its using Netapp?

should I disregard the symantec tec doc? The backup will get the same error tonight as is.

 

Thanks

 

volsnap in this case is probably the part of the windows volume manager which vss calls

A busy volume can give this volsnap IO error, a solution can be to increase the mindiffarea so that the shadow area does not have to grow while the backup is running. Does chkdsk show any errors on this C: drive ?

Have the post below helpful when troubleshooting status 156 on windows

http://blogs.technet.com/b/askcore/archive/2010/06/18/reasons-why-the-error-enumeration-of-the-files-failed-may-occur-during-system-state-backup.aspx

 

Hi Riaan, Michael,

Thanks,  there is 1.40GB left on the C drivce also the chkdsk shows no errors.

Michael, thanks for the info.

 

 

 

 

No updates here in more than 2 weeks...

I believe that TECH156732 is applicable here. 
Please follow steps as per the TN.

Some more reading matter: 

How to verify Windows Open File Backup operation using VSSADMIN and BPFIS before contacting Symantec Technical Support
http://www.symantec.com/docs/TECH47808 

 

PS: 
C:\windows\system32 should always be in System and User PATH environment variables.

its a volsnap error in event viewer on server. check its event id share it with us and search on google it could be related to OS. sometimes there is a chance to deregister and reregister VSS dll's .

please check VSS status on client server. on cmd write

vssadmin list providers 

vssadmin list writers

----------------------------

check 2 services microsoft software shadow copy and volume shadow copy both should be in manual state.

go to my computer right click on C:\ then on configure shadow copy. then check size.

-------------------------------

go to host properties -- master server then client attributes, check what options are selected for client server.

if client server name not added, plz add it.

------------------------------

once all these basic options checked n verified. go to run and take windows server backup(it is native window server backup same as ntbackup windows 2003) of shadow copy components.

--------------------------

At last share latest bpbkar,bpfis  log files