Betsy, don't consider this a definitive answer, but it may help you
until you get more information:
I see the ANR0484W Protocol Violation errors every day from our desktop
clients.
It appears to me that ANYTHING that interrupts an ADSM WIN32 session at
the client end (shutting down the Scheduler Window on Win95, power off
the PC, etc.) can result in the ANR0484W message on the server end.
I don't know an easy way to find out what your problem is, especially on
NT.
We have had several bizarre problems with NT 4.0 machines communicating
via IP.
* There is actually a "name service" that runs on NT that
is involved in resolving IP names. We have had that get hosed on a few
NT machines, but rebooting clears it up.
* We have had some WinNT machines fail to connect
intermittently if they were also running some other IP-intensive
application, like PointCast. In that case rebooting and running with
other apps shut down should work.
* Since the GUI works but the Scheduler doesn't, there is
the possibility that your registry entries for the Scheduler service are
damaged.
* There was an earlier thread today about problems with
failing to connect if you are in Prompted mode - check that out.
Here are the things I would try:
* Make sure he has stopped and restarted the service, but still
has the problem.
* Reboot NT and start the ADSM Scheduler without starting up any
other apps like email or Netscape and see if you get the same results.
* If that doesn't work, (1) shut down the NT scheduling service
(2) go to a DOS window (3) make sure you can PING the ADSM server, (4)
cd to the baclient subdirectory, (5) type DSMC SCHED and see if that
works. If it works but the Service doesn't, must be a problem with the
service. If it doesn't, it must be a problem with IP on that machine.
* If those things don't work, try reinstalling the Scheduler
Service.
Hope this helps...
===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
301-953-6000 X8769
wanda_prather AT jhuapl DOT edu
"Intelligence has much less practical application than you'd think."
- Scott Adams/Dilbert
===============================================================
----------
From: Moir,Elizabeth[SMTP:Betsy.Moir AT abbott DOT com]
Sent: Thursday, January 29, 1998 12:18 PM
To: ADSM-L AT vm.marist DOT edu
Subject: Protocol Violation
V2 on Vm Server
V2 client on NT 4.0
Four days ago our client received the following error: ANR0484W
Protocol
violation detected. The message books reads:
ANR0484W Session session number for node node name (client
platform)
terminated - protocol violation detected.
Explanation: The server ends the specified session
because a
communications protocol error by the client has been
detected.
System Action: The server ends the client session.
User Response: Examine the client message to determine
the
problem. Correct the programming error in the client
program. If
the client program has been provided by IBM, and the
error cannot
be isolated and resolved, contact your service
representative.
Doesn't help me a whole lot. (Sorry, IBM, but your error
message
explanations for ADSM leave a whole lot to be
desired.)
His session was terminated and he hasn't been able to establish
an NT Service
session since although there is no problem communicating via the
GUI
interface. When he attempts to connect the error log shows the
following
error:
ANS4017E Session Rejected
TcpOpen TCP/IP error connecting to server.
SessOpen Failure in Communications Open Call rc: -50
Does anybody ideas on what might be happening here or what I can
try to
correct the problem. At this point his NT service just keeps
trying to log
on and failing. This is the client who's platform is showing up
as "Password
Check" that I sent the note out about earlier.
Thanks for your thoughts and
suggestions.
|
