There is a thread on another forum about this: "Yes - there is a strong potential the Dll files in the registry have become corrupt or removed. Since Vss issues are Microsoft issues - have your SA re-apply SP2 from CD, then re-register the necessary Dll files associated with System state writers - also = run a Ntbackup against system state. If all works then its a TSM issue. If you execute "vssadmin list writers" from the C prompt and it returns nothing - then you have to re-registry ALL the DLLs associated with system state."
The same thread then mentions the procedure used to resolve their problem: According to Microsoft Premier Support this is the correct procedure to follow when re-registering the Volume Shadow Copy service DLL's. Open a command prompt session CD to Windows\System32 Net stop vss Net stop swprv 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 Reboot your server. After reboot, open a command prompt and run: vssadmin list writers Ensure that all your writers are displayed w/o errors. Jeff > Hi Tim > Have you check the event log in Windows and also try VSSAdmin to see if > VSS Works OK. > I'm suggesting that you look on MS Website. > This page can help you to test your MS Volume Shadow Copy Services and see > if it works OK. > > http://technet.microsoft.com/en-us/library/cc754968.aspx > > Cheers > Christian > > ________________________________ > Från: ADSM: Dist Stor Manager [EMAIL PROTECTED] för Timothy Hughes > [EMAIL PROTECTED] > Skickat: den 14 augusti 2008 16:36 > Till: ADSM-L@VM.MARIST.EDU > Ämne: Windows client failing more VSS request issues > > Hello all, > > We have a Windows 2003 client that failing with the following message in > the client error.log. Has anyone had this problem > with a 5.5.0.2 Windows Client? > > 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error > code: 4353. > 08/14/2008 00:16:43 ANS1228E Sending of object > 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed > 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS > request. For more information, see the TSM client error log. > > 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. > > 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS > request. For more information, see the TSM client error log. > > 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return > code = 12. > 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System > State\0\SystemState' Id:0-836409676 > 08/14/2008 10:06:00 ANS2054E Operating system error 13: ????????d. > 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. > TSM function name : verifyLocalBackups() > TSM function : Unable to lock local repository > TSM return code : 101 > TSM file : vssback.cpp (6353) > 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. > TSM function name : verifyLocalBackups() > TSM function : Verifying Local Backups Failed! > TSM return code : 101 > TSM file : vssback.cpp (5725) > 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: > VssRequestor::checkWriterStatus() failed with > hr=VSS_E_WRITERERROR_NONRETRYABLE > 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services > writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not > valid for the current operation or cannot be determined. The last error > reported is '800423f4'. > > Also, > > When I ran a Manual backup of the "System State" and recieved the > following > > Ans5258e - And error occured Initializing a VSS request > Ans1375E - The snapshot operation failed > > TSM Server 5.5.0.3 > Aix 5.3 > Windows 2003 sp1 Client/TSM Client 5.5.0.2 > > Thanks for any help, comments, suggestions in advance! > >
