When we get that message, it's due to something being out of whack on an NT
3.1.0.5 client.  The fix for us is to put 3.1.0.6 on the offending client,
and lock it out until the time 3.1.06 can be installed on it.
The 3.1.2.1 server shows the error, but I believe it's the client causing
the problem.
Julie




"John C. Wranovics" <johnw AT FREDRICKGROUP DOT COM> on 01/19/99 03:04:10 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Julie Phinney/Green Bay/Humana)
Subject:  ADSM Server Update Problem





After updating to the latest service release I have V3, Release 1, Level
2.1
of the Server running on NT 4.0 Server with SP3.

Everyting seems to be functioning except that when I start the ADSM Server
it goes through it's startup tasks, then sits for a while then give the
following messages over and over:

ANR0406I Session 2 started for node CLIENT (WinNt)  (Tcp/IP 204.69.168.10
(3168) - ).
ANR0444W Protocol error on session s for node CLIENT (WinNT) -
out-of-sequence verb (type SignOFF) received.
ANR0484W Session 2 for node CLIENT (WinNT) terminated - protocol violation
detected.

This series of messages gets repeated over and over until I stop the
server.

Has anyone else had this problem? and if so what is the solution.

Also, what is the procedure for getting ADSM problems resolved, as I'm a
new
user.

Thanks in advance

John Wranovics
The Fredrick Group, Inc.