ADSM-L

Re: Communications Protocol Error

2006-07-11 14:55:28
Subject: Re: Communications Protocol Error
From: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 11 Jul 2006 14:35:17 -0400
Hi Ralph,

When we've had protocol errors, it has been when a client tried to use a
feature that
the server did not support.  In other words, a client at a higher rev than
the server, and,
using a feature of that client that the lower rev tsm server doesn't
support.


Rick





             "Levi, Ralph"
             <RLevi AT HESS DOT COM>
             Sent by: "ADSM:                                            To
             Dist Stor                 ADSM-L AT VM.MARIST DOT EDU
             Manager"                                                   cc
             <[email protected]
             .EDU>                                                 Subject
                                       Communications Protocol Error

             07/11/2006 02:11
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






Hi All,

I am running TSM 5.2.7 on AIX 5.3 and a remote client running 5.3.4 on
W2K.  I have two problems that are probably related.  Perhaps someone
has seen this and could help clue me in.

My nightly incremental backup always fails with the following message:

dsmsched.log

--- SCHEDULEREC OBJECT BEGIN DAILY_BACKUP_1900 07/10/2006 19:00:00
ANS1026E The session is rejected: There was a communications protocol
error.

dsmerror.log

cuGetPSQryResp: Out of sequence verb received; VB_PSQryResp or EndTxn
wanted
ANS1026E The session is rejected: There was a communications protocol
error.

When I start the backup gui on the client, the first start tries to
establish a session but after 10 minutes times out with a gui message:

Communications Protocol Error.

HOWEVER, while the session initialization is in the 10 minute "wait", I
can initiate another gui session from the same console without any issue
and run a backup via the gui successfully.

Also, if I have a gui session active at the time the nightly incremental
wants to start, it does establish a session and the scheduled backup
runs to a successful completion.

I have tried every backup client from 5.1 to 5.3.4 .  This has been
going on for months so I can't rightfully say what if anything has
changed.  It used to run successfully all the time but over time TSM and
network upgrades have certainly occurred.  The problem is recreateable
every run.

Anyone's insight would be greatly appreciated.

Thanks,
Ralph Levi



-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.

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