John,

The errors you are experimenting with VSS have nothing to do with TSM
rather the host. Deleting the filespace won't do you any good. Try the
steps in this post:
http://www.mail-archive.com/adsm-l AT vm.marist DOT edu/msg83546.html

Good luck.

BERTAUT TCHUISE
TSM/NetApp Storage Engineer
Legg Mason Technology Services
*410-580-7032
BTchuise AT leggmason DOT com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dury, John C.
Sent: Thursday, February 11, 2010 11:08 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] VSS and system state failures on windows 2003 clients

I've been fighting this for several weeks now and I'm getting very
frustrated. I have several windows 2003 clients that consistently get
the errors listed below. I've done some research and installed the
following patches as per recommendations from several others and nothing
seems to fix the errors. I've tried multiple version of the TSM client
(v5 and v6). I've delete the file space that has the current system
state. All of the latest maintenance is installed on the Windows 2003
clients.  Sometimes I can get the "dsmc backup systemstate" to work for
one night but then the very next night, it fails again. This is on
several windows 2003 clients.  I did add the line "PRESCHEDULECMD
"ntbackup backup systemstate /F C:\temp\SystemStateBackup.bkf /L:S"" in
the dsm.opt for the offending clients so I at least have a clean backup
of the system state. I'm not sure where to turn now. Is windows 2003
support in TSM really this bad? Any ideas suggestions or hints are more
than welcome.


TSM Client version tried (all 32bit)
5.5.2.7
5.5.2.10
6.1.2.0
6.1.3.1

Errors received on several windows 2003 clients CLIENT 1 02/11/2010
09:26:25 ANS1577I The Windows console event handler received a 'Ctrl-C'
console event.
02/11/2010 09:33:29 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITER_NOT_RESPONDING 02/11/2010 09:33:29 ANS5268W The
Microsoft Volume Shadow Copy Services writer 'Removable Storage Manager'
current state (VSS_WS_STABLE) is not valid for the current operation.
02/11/2010 09:33:29 ANS5274E A Microsoft Volume Shadow Copy Services
writer is in an invalid state after backup completion.
02/11/2010 09:33:29 ANS5250E An unexpected error was encountered.
   TSM function name : CompleteVssSnapshot
   TSM function      : psVssBackupComplete() failed
   TSM return code   : 4345
   TSM file          : txncon.cpp (4324)
02/11/2010 09:33:34 ANS1999E Incremental processing of '\\client1\d$'
stopped.
02/11/2010 09:33:35 ANS4006E Error processing
'\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3': directory path not
found

CLIENT2
02/11/2010 04:10:24 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITER_NOT_RESPONDING 02/11/2010 04:10:24 ANS5268W The
Microsoft Volume Shadow Copy Services writer 'Removable Storage Manager'
current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current
operation.
02/11/2010 04:10:54 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITER_NOT_RESPONDING 02/11/2010 04:10:54 ANS5268W The
Microsoft Volume Shadow Copy Services writer 'Removable Storage Manager'
current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current
operation.
02/11/2010 04:11:24 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITER_NOT_RESPONDING 02/11/2010 04:11:24 ANS5268W The
Microsoft Volume Shadow Copy Services writer 'Removable Storage Manager'
current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current
operation.
02/11/2010 04:11:54 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITER_NOT_RESPONDING 02/11/2010 04:11:54 ANS5268W The
Microsoft Volume Shadow Copy Services writer 'Removable Storage Manager'
current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current
operation.
02/11/2010 04:11:54 ANS5271E A Microsoft Volume Shadow Copy Services
writer is in an invalid state before snapshot initialization.
02/11/2010 04:11:54 ANS5250E An unexpected error was encountered.
   TSM function name : baHandleSnapshot
   TSM function      : BaStartSnapshot() failed.
   TSM return code   : 4353
   TSM file          : backsnap.cpp (3767)
02/11/2010 04:11:54 ANS1327W The snapshot operation for
'client2\SystemState\NULL\System State\SystemState' failed with error
code: 4353.
02/11/2010 04:11:54 ANS5283E The operation was unsuccessful.

CLIENT3
02/11/2010 08:59:14 ANS1577I The Windows console event handler received
a 'Ctrl-C' console event.
02/11/2010 09:06:14 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus failed with
hr=VSS_E_WRITER_NOT_RESPONDING 02/11/2010 09:06:14 ANS5268W The
Microsoft Volume Shadow Copy Services writer 'Removable Storage Manager'
current state (VSS_WS_STABLE) is not valid for the current operation.
02/11/2010 09:06:14 ANS5274E A Microsoft Volume Shadow Copy Services
writer is in an invalid state after backup completion.
02/11/2010 09:06:14 ANS5250E An unexpected error was encountered.
   TSM function name : CompleteVssSnapshot
   TSM function      : psVssBackupComplete() failed
   TSM return code   : 4345
   TSM file          : txncon.cpp (6428)
02/11/2010 09:06:15 ANS1228E Sending of object '\\CLIENT3\e$\ABURNS\Work
Plan Analyst\2008 Files\2008 Damage Claims\WO #315451' failed 02/11/2010
09:06:15 ANS4021E Error processing '\\ CLIENT3\e$\ABURNS\Work Plan
Analyst\2008 Files\2008 Damage Claims\WO #315451': file system not ready
02/11/2010 09:06:17 ANS1228E Sending of object '\\ CLIENT3\e$\gklinsk'
failed 02/11/2010 09:06:17 ANS4005E Error processing '\\
CLIENT3\e$\gklinsk': file not found 02/11/2010 09:06:17 ANS1228E Sending
of object '\\ CLIENT3\e$\glee' failed 02/11/2010 09:06:17 ANS4005E Error
processing '\\ CLIENT3\e$\glee': file not found Lots more on CLIENT3
like the above. The filesystem is definitely there and working.

Patches installed

WindowsServer2003-KB934016-x86-ENU.exe
WindowsServer2003-KB940349-v3-x86-ENU.exe
WindowsServer2003-KB951568-x86-ENU.exe

Did this:
cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.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

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.