Group Codes Mismatch - Digital Equipment MUXserver 100 Reference Manual

Problem A protocol error occurs in a message received from a service node. A
connection attempt fails, or an existing session terminates.
Correction: Attempt to reconnect to the service. This condition indi-
cates a possible problem with the LAT software on the service node.
Report the problem to the system manager of the service node.
Local -226- Connection to 'name' not established
Invalid message or slot received
Local -266- Connection to 'name' terminated
Invalid message or slot received
Problem The service node is receiving MUXserver 100 messages that violate
the LAT protocol.
Correction: Try the CONNECT command again. If the connection to
the service fails, initialize the server again to down-line load the
server software.
If
the error messages appear again for CONNECT,
there may be a hardware problem affecting the random access mem-
ory (RAM). Refer to Section 4.6 (PROBLEMS INVOLVING THE
ETHERNET) for information about DIGITAL services to assist you
further.
4.5.3 Group Codes Mismatch
The following messages at a terminal may indicate a group codes mismatch.
Local -711- Service name not known
Local -716- Access to service name denied
Problem Service node group codes do not match the group codes for the
terminal.
Correction: Confirm the mismatch by entering the SHOW
SERVICES service-name command at the terminal.
If the service
node does not appear in the display, the group codes do not match.
Determine the group codes that are in effect for the service node.
Then adjust the group codes for the terminal as described in
Chapter 2, Section 2.7.1 (Session Control Characteristics).
38 CHAPTER 4
MUXserver 100
TROUBLESHOOTING