Backup Central

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!

Hate to be an old patoot, did you reboot to see if you could reproduce &
have you applied the VSS hotfix for win2k3?

I don't usually have the recurring error on our systems afterwards. On
one I did, and also applied the 5.5.1.0 client code too, and haven't had
the issue since.

thanks!
lisa


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Timothy Hughes
Sent: Thursday, August 14, 2008 9:36 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] 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!

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 [ADSM-L < at > VM.MARIST.EDU] för Timothy Hughes [Timothy.Hughes < at > OIT.STATE.NJ.US]
Skickat: den 14 augusti 2008 16:36
Till: ADSM-L < at > 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!

Lisa Thanks,

I'll have talk to the user about rebooting and applying VSS hotfixes for
win2k3 I don't which ones to apply. If those don't work I will apply
the 5.5.1.0 code.

Thanks again
Tim

Laughlin, Lisa wrote:

Hate to be an old patoot, did you reboot to see if you could reproduce &
have you applied the VSS hotfix for win2k3?

I don't usually have the recurring error on our systems afterwards. On
one I did, and also applied the 5.5.1.0 client code too, and haven't had
the issue since.

thanks!
lisa


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Timothy Hughes
Sent: Thursday, August 14, 2008 9:36 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] 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!

You'll have to request it from MS-- it's name is below- if you search
for the KB you should be able to find it. Get the one for x64 while
you're at it too, if you have any 64 bit servers

WindowsServer2003-KB934016-x86-ENU.exe

thanks!
lisa


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Timothy Hughes
Sent: Thursday, August 14, 2008 10:31 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Windows client failing more VSS request issues

Lisa Thanks,

I'll have talk to the user about rebooting and applying VSS hotfixes for
win2k3 I don't which ones to apply. If those don't work I will apply
the 5.5.1.0 code.

Thanks again
Tim

Laughlin, Lisa wrote:

Hate to be an old patoot, did you reboot to see if you could reproduce
&
have you applied the VSS hotfix for win2k3?

I don't usually have the recurring error on our systems afterwards. On
one I did, and also applied the 5.5.1.0 client code too, and haven't
had
the issue since.

thanks!
lisa


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf
Of
Timothy Hughes
Sent: Thursday, August 14, 2008 9:36 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] 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!

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 [ADSM-L < at > VM.MARIST.EDU] för Timothy Hughes
[Timothy.Hughes < at > OIT.STATE.NJ.US]
Skickat: den 14 augusti 2008 16:36
Till: ADSM-L < at > 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!

Hi Christian,

Thanks for your Reply and the link also, I did do a "vssadmin list
writers" not sure if part of the MS VSS test and it showed the
following. I am going to check with the Client about the VSS Hotfixes
that was suggested.

Thanks again!

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\>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: {12a259f2-0085-43d6-bc40-a52d4642841f}
State: [1] Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b3fe7d96-bedd-47b8-94a9-6b3df02abf9e}
State: [1] Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {847be3ca-37c6-49d1-b94d-75b685d41fd0}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {a42a078c-427f-49ee-ae88-f12054acd26c}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {f9eaec31-24e6-454f-bcee-92fc2dee87ba}
State: [1] Stable
Last error: No error

Writer name: 'Cluster Service Writer'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {6017d216-3f66-472e-a5ca-c47d20b8e67b}
State: [1] Stable
Last error: Non-retryable error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {6df2eeb9-6756-4f24-a07f-13397244fcb8}
State: [1] Stable
Last error: No error




Christian Svensson wrote:

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 [ADSM-L < at > VM.MARIST.EDU] för Timothy Hughes [Timothy.Hughes < at > OIT.STATE.NJ.US]
Skickat: den 14 augusti 2008 16:36
Till: ADSM-L < at > 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!

Thanks..Again Lisa for your help!



Laughlin, Lisa wrote:

You'll have to request it from MS-- it's name is below- if you search
for the KB you should be able to find it. Get the one for x64 while
you're at it too, if you have any 64 bit servers

WindowsServer2003-KB934016-x86-ENU.exe

thanks!
lisa


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Timothy Hughes
Sent: Thursday, August 14, 2008 10:31 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Windows client failing more VSS request issues

Lisa Thanks,

I'll have talk to the user about rebooting and applying VSS hotfixes for
win2k3 I don't which ones to apply. If those don't work I will apply
the 5.5.1.0 code.

Thanks again
Tim

Laughlin, Lisa wrote:



Hate to be an old patoot, did you reboot to see if you could reproduce


&


have you applied the VSS hotfix for win2k3?

I don't usually have the recurring error on our systems afterwards. On
one I did, and also applied the 5.5.1.0 client code too, and haven't


had


the issue since.

thanks!
lisa


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf


Of


Timothy Hughes
Sent: Thursday, August 14, 2008 9:36 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] 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!