Diana,

Off-hand, I do not know what this problem is.

Are there any other messages in the activity log that could signal a
problem  around the time this problem occurs?

Is there anything in the dsmerror.log file that coincides with the time
this problem occurs?

What else is in the dsmsched.log file around the time the problem occurs?
If you are running with the QUIET option, comment it out, then retry the
backup and see what other detailed messages you get.

What is the history of this problem in your shop? Does it occur on just
one machine, some machines, or all machines? On the machines where the
problem occurs, does it occur every time, intermittently, or just once? On
the machines where the problem occurs, did the backups ever run without
trouble? If so, then what (if anything) changed in your environment that
might coincide with when the trouble started to occur?

I would also recommend gathering the following documentation and
contacting IBM support:

1) A client SERVICE trace that shows the problem. Add the following to
your client options file (dsm.opt):

   TRACEMAX 20
   TRACEFILE C:\TRACE.TXT
   TRACEFLAGS SERVICE

If the problem happens within a few minutes after the the backup starts,
you can eliminate the TRACEMAX line. Also, from your original description,
it sounds like the backup stops altogether when the error occurs. If this
is not the case, and the backup keeps going, then eliminate the TRACEMAX
line.

Also, if you have QUIET in your client options file, remove it. If you
have a client options set with the QUIET option in it, remove that, too
(at least temporarily) so that you can see detailed output from the
console and/or dsmsched.log.

If you can quickly reproduce the problem by running "dsmc incremental",
then try it that way. Otherwise stop and restart the scheduler, so you'll
get the trace the next time the backup runs.

2) dsm.opt

3) dsmsched.log

4) dsmerror.log

5) TSM server activity log from one hour before the error occurs to one
hour after the error occurs.

6) Client options set information (output from QUERY CLOPTSET) if your
node has a client options set associated with it.

That should be good for starters.

Feel free to keep me posted on your progress.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Diana Noble <djk AT UMICH DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/04/2002 07:01
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        ANR0444W Protocol Error - Type GroupHandler



Hi Everyone -

We have a Windows 2000 Active Directory client running TSM 5.1 which has
started receiving the following message in the activity log:

ANR0444W Protocol error on session 11716 for node DCITCS (WinNT) -
out-of-sequence verb (type GroupHandler) received.
ANR0484W Session 11716 for node DCITCS (WinNT) terminated - protocol
violation detected.

The client scheduler log specifies an unknown system error.  I haven't
been
able to find anything on "type GroupHandler".  The server is TSM 4.2.2.5
running on AIX 4.3.3.  We receive this error on both scheduled backups and
selective incremental backups.  Does anyone have any information on what
may be causing this or what "type GroupHandler" means?

Thank you,

Diana Noble