ADSM-L

Re: failed (return code 12)

2006-08-08 11:05:17
Subject: Re: failed (return code 12)
From: Lyndon Benjamin <lyndonb AT MED.UMICH DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 8 Aug 2006 08:13:55 -0400
  We have around 400 windows servers and our clients get error 12's on
a regular basis. The issue is that Tivoli error 12's
are generic error that they seem to use as a catch all for a number of
errors. So I am checking our backups on a regular basis.
We have the Tivoli for windows 5.3.2 client. I have received these
errors when a server has issues doing a snapshot, couldn't access a
local drive, domain statement issues.

ben

>>> Len Boyle <Len.Boyle AT SAS DOT COM> 8/7/2006 10:50 PM >>>
Gill,

What do you find in the dsmerror.log file found on the client machine.


len

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of Gill, Geoffrey L.
Sent: Monday, August 07, 2006 7:17 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] failed (return code 12)

We see this error once in a while and I'm wondering if anyone has any
particular insight as to the cause. Here is what I found in the TSM
server
log that I'm guessing caused the report. The backup ran for 1:43
minutes
before this happened and did complete with the failure. If it is not
maybe
someone has something specific to look for.



08/06/2006 21:43:28      ANR0440W Protocol error on session 44536 for
node


                          Node12(WinNT) - invalid verb header

                          received.(SESSION: 44536)


08/06/2006 21:43:31      ANR0484W Session 44536 for node node12
(WinNT)

                          terminated - protocol violation
detected.(SESSION:
44536)



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:  <mailto:geoffrey.l.gill AT saic DOT com> geoffrey.l.gill AT saic DOT com


**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues.

<Prev in Thread] Current Thread [Next in Thread>