Anyone has any issues with client 5.5.0.4?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Laughlin, Lisa
Sent: 2008, August, 14 12:04 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Windows client failing more VSS request issues
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 DOT EDU] On Behalf Of
Timothy Hughes
Sent: Thursday, August 14, 2008 10:31 AM
To: ADSM-L AT VM.MARIST DOT 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 DOT EDU] On Behalf
Of
>Timothy Hughes
>Sent: Thursday, August 14, 2008 9:36 AM
>To: ADSM-L AT VM.MARIST DOT 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!
>
>
_______________________________________________________________________
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations.
Any distribution, use or copying of this e-mail or the information it contains
by other than an intended recipient is unauthorized.
If you received this e-mail in error, please advise me (by return e-mail or
otherwise) immediately.
Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce
pas aux droits et obligations qui s'y rapportent.
Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il
contient par une personne autre que le (les) destinataire(s) désigné(s) est
interdite.
Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser
immédiatement, par retour de courrier électronique ou par un autre moyen.
|
