Novell client failed with RC 12

2004-07-28 Thread Timothy Hughes
Hello TSMer's

Last night 2 of our Novell clients nodes failed with a return code 12,
total number of objects failed were over 3,000 from each. (see server
Act log below)
Anyone ever seen  this type of occurrence before?


Thanks for any help/advice in advance!

TSM Novell client 5.2.2
Netware OS 5.1 SP6
TSM Server Version 5.2.1.3


07/28/04 05:50:27 ANE4952I (Session: 55283, Node: )  Total
number of
   objects inspected:  695,351
07/28/04 05:50:27 ANE4954I (Session: 55283, Node: )  Total
number of
   objects backed up:2,088
07/28/04 05:50:27 ANE4958I (Session: 55283, Node: )  Total
number of
   objects updated:  0
07/28/04 05:50:27 ANE4960I (Session: 55283, Node: )  Total
number of
   objects rebound:  0
07/28/04 05:50:27 ANE4957I (Session: 55283, Node: )  Total
number of
   objects deleted:  0
07/28/04 05:50:27 ANE4970I (Session: 55283, Node: )  Total
number of
   objects expired: 24
07/28/04 05:50:27 ANE4959I (Session: 55283, Node: x)  Total
number of
   objects failed:
3,436
07/28/04 05:50:27 ANE4961I (Session: 55283, Node:   Total
number of
   bytes transferred:  2.22 GB

07/28/04 05:50:27 ANR2579E Schedule MIDNIGHT in domain PRODUCTION
for node
   failed (return code 12).

07/28/04 06:11:03 ANE4952I (Session: 55270, Node: x)  Total
number of o
   bjects inspected:  332,794
07/28/04 06:11:03 ANE4954I (Session: 55270, Node: x)  Total
number of o
   bjects backed up:1,076
07/28/04 06:11:03 ANE4958I (Session: 55270, Node: x  Total
number of o
   bjects updated:  0
07/28/04 06:11:03 ANE4960I (Session: 55270, Node: x)  Total
number of o
   bjects rebound:  0
07/28/04 06:11:03 ANE4957I (Session: 55270, Node: x)  Total
number of o
   bjects deleted:  0
07/28/04 06:11:03 ANE4970I (Session: 55270, Node: x)  Total
number of o
   bjects expired:  5
07/28/04 06:11:03 ANE4959I (Session: 55270, Node: x  Total
number of o
   bjects failed:   3,431
07/28/04 06:11:03 ANE4961I (Session: 55270, Node: x)  Total
number of b
   ytes transferred: 280.00 MB
07/28/04 06:11:03 ANE4964I (Session: 55270, Node: x Elapsed
processing
   time:04:42:59
07/28/04 06:11:03 ANR2579E Schedule MIDNIGHT in domain PRODUCTION
for node
  x failed (return code 12).


Re: Novell client failed with RC 12

2004-07-28 Thread Richard Sims
Last night 2 of our Novell clients nodes failed with a return code 12,
total number of objects failed were over 3,000 from each. (see server
Act log below) ...

You're keeping us in suspense...  You need to examine the backup log, and
perhaps also the dsmerror.log, to ascertain the detail reason for the failures.
The session-end stats provide no info about reasons.

  Richard Sims


Re: Novell client failed with RC 12

2004-07-28 Thread Timothy Hughes
Sorry for the lack of information on my earlier post.

I took a look a the Dsmerror.log and found the
following errors leading up to the 3,000 + file failures

07/28/2004 01:51:57 A transport failure has occurred.
07/28/2004 01:51:57 ANS1870E NDS transport failure FFFDFEAF has occurred.
Please contact Novell to resolve it.
07/28/2004 01:51:57 A transport failure has occured.
07/28/2004 01:51:57 ANS1870E NDS transport failure FFFDFEAF has occurred.
Please contact Novell to resolve it.
07/28/2004 01:51:57 A transport failure has occured.
07/28/2004 01:51:57 ANS1228E Sending of object
'.[Root].O=xxx.OU=.OU=xxx
.CN=WP_AMI_GENERAL' failed
07/28/2004 01:51:57 Skip current operation
Report how you got this
07/28/2004 01:51:57 ANS1870E NDS transport failure FFFDFEAF has occurred.
Please contact Novell to resolve it.
07/28/2004 01:51:57 A transport failure has occured.
07/28/2004 01:51:57 ANS1228E Sending of object
'.[Root].O=.OU=.OU=xxx.CN=ZIP CODES' failed
07/28/2004 01:51:57 Skip current operation
Report how you got this
07/28/2004 01:51:57 ANS1870E NDS transport failure FFFDFEAF has occurred.
Please contact Novell to resolve it.
07/28/2004 01:51:57 A transport failure has occured.
07/28/2004 01:51:57 ANS1228E Sending of object
'.[Root].O=.OU=.OU=xxx
.CN=xx.CN=MTA' failed
07/28/2004 01:51:57 Skip current operation
Report how you got this
07/28/2004 01:51:57 ANS1228E Sending of object
'.[Root].O=xx.OU=xx.OU=xxx.CN=xx.CN=xxx' failed
07/28/2004 01:51:57 Skip current operation
Report how you got this
07/28/2004 01:51:57 ANS1228E Sending of object
'.[Root].O=xxx.OU=.OU=xxx.CN=xx.CN=WEBACC55' failed
07/28/2004 01:51:57 Skip current operation
Report how you got this
07/28/2004 01:51:57 ANS1228E Sending of object '.[Root].O=.OU=
.OU=xxx.CN=xx.CN=POA' failed
07/28/2004 01:51:57 Skip current operation
Report how you got this
07/28/2004 01:51:57 ANS1802E Incremental backup of '.[Root]' finished with 3426
failure


I also find the following errors some seemed to be the Internet Bookmark sites
I eluded to on my other post


07/28/2004 05:49:02 ANS1228E Sending of object
'VOL1:/PROJE/SUPPORT/Angel/neerja/Favorites/Seattle Public SchoolsÿÿDev Stg
Read.url' failed
07/28/2004 05:49:02 ANS4005E Error processing
'VOL1:/PROJE/SUPPORT/Angel/neerja/Favorites/Seattle Public SchoolsÿÿDev Stg
Read.url': file not found
07/28/2004 05:49:02 ANS1228E Sending of object
'VOL1:/PROJE/SUPPORT/Angel/Ronl/Favorites/The rÿBaseball Team.url' failed
07/28/2004 05:49:02 ANS4005E Error processing
'VOL1:/PROJE/SUPPORT/Angel/Ronl/Favorites/ Baseball Team.url': file not found
07/28/2004 05:49:02 ANS1228E Sending of object
'VOL1:/PROJE/SUPPORT/crisk/Favorites/Brick,ÿNew JerseyÿForecastÿby Intellicast.url'
failed
07/28/2004 05:50:20 (TSA500.NLM 5.5 269) No data sets can be found.
07/28/2004 05:50:23 (TSA500.NLM 5.5 269) No data sets can be found.
07/28/2004 05:50:23 (TSA500.NLM 5.5 269) No data sets can be found.

Novell Tsm client version  5.2.2
Netware OS 5.1 SP6
TSM Version 5.2.1.3


Thanks again for any help on these errors!

Richard Sims wrote:

 Last night 2 of our Novell clients nodes failed with a return code 12,
 total number of objects failed were over 3,000 from each. (see server
 Act log below) ...

 You're keeping us in suspense...  You need to examine the backup log, and
 perhaps also the dsmerror.log, to ascertain the detail reason for the failures.
 The session-end stats provide no info about reasons.

   Richard Sims


Re: Novell client failed with RC 12

2004-07-28 Thread Richard Sims
...ANS1870E NDS transport failure FFFDFEAF has occurred. ...

Novell Tsm client version  5.2.2
Netware OS 5.1 SP6

Tim - The IBM site has an indicative entry on that message number.

I'm no Novell person, but from the years of postings I've seen, Novell
environment backup problems are often due to Novell software problems
(as further suggested by the IBM site item on that message).
That may well also be the case for the ANS1228E and ANS4005E messages you also
uncovered in the dsmerror.log.  (In the past, at least, the ANS4005E message has
been caused by downlevel TSANDS and/or TSA600 NLM's.)
It looks like your best avenue is to seek some Novell patches.
Netware 5.1 is also at the low end of what the 5.2.2 TSM client supports, so
you may alternately have Netware upgrade possibilities.

   Richard Sims


Re: Novell client failed with RC 12

2004-07-28 Thread Troy Frank
If your server is NW5.1sp6 , I would also agree that sp7 is a good idea.
  I've got 20/30 of those using TSM5.2.2 just fine.


Troy Frank
Network Services
University of Wisconsin Medical Foundation
608.829.5384

 [EMAIL PROTECTED] 7/28/2004 10:44:19 AM 
...ANS1870E NDS transport failure FFFDFEAF has occurred. ...

Novell Tsm client version 5.2.2
Netware OS 5.1 SP6

Tim - The IBM site has an indicative entry on that message number.

I'm no Novell person, but from the years of postings I've seen, Novell
environment backup problems are often due to Novell software problems
(as further suggested by the IBM site item on that message).
That may well also be the case for the ANS1228E and ANS4005E messages
you also
uncovered in the dsmerror.log. (In the past, at least, the ANS4005E
message has
been caused by downlevel TSANDS and/or TSA600 NLM's.)
It looks like your best avenue is to seek some Novell patches.
Netware 5.1 is also at the low end of what the 5.2.2 TSM client
supports, so
you may alternately have Netware upgrade possibilities.

Richard Sims


Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.