Troubleshooting
5. When the MAXserver 1600 chooses a load server, a message similar to this one appears:
Terminal Server, Type 74, Rev x.xx.x
Ethernet address 08-00-87-xx-xx-xx, port x
Loading over Link L1 from server xx-xx-xx-xx-xx-xx, message 0
Link L1 refers to the Ethernet transceiver cable or ThinWire network cable; that is, the unit is loading
via the LAN. If the message count remains at zero while you type <RETURN>s are continuously, the
load server was configured to load the MAXserver 1600, but encountered a problem with the load file
or directory. Check the file name and directory at the load server.
Additionally, in some newer VAX /VMS installations, the logical name "MOM$LOAD" might not be
defined properly. (Refer to the Software Installation Guide for VMS load hosts for more information.)
6. After the MAXserver 1600 loads a file, it checks the contents of the file for proper identification and
size. One of the following messages can appear if the MAXserver 1600 encounters a file problem:
Server xx-xx-xx-xx-xx-xx; File error: not a load file.
This message type appears if the load server attempted to load a file image that is incompatible with
the MAXserver 1600. (The load file did not have a Xyplex ASCII identification string header.) This
can happen if, for example, the file is a DECserver 200 load file.
Server xx-xx-xx-xx-xx-xx; File error: corrupted data.
This message type indicates that the load server attempted to load a file that is compatible with the
MAXserver 1600, but the file has been corrupted. Correct this problem by installing a new file in
the load server. Refer to the Software Installation Guide for instructions.
Server xx-xx-xx-xx-xx-xx; File error: not executable.
No 680xx CPU identifier appears in the file header. This is a Xyplex file, but it cannot be executed
by the server. Resolve this problem by installing the proper file in the load server. Refer to the
Software Installation Guide for instructions.
Server xx-xx-xx-xx-xx-xx; Timed out, will retry.
This message type indicates that the MAXserver 1600 gave up waiting for the load server to send a
load file image. When this happens, the server restarts the load request process. If the message count
was not zero, and the "timed out" message was displayed, it is possible that your network experienced
communication problems. Note that if there is no progress of the message count number beyond zero,
a load server problem exists. A network problem probably exists if the message count remains stuck
at a number other than zero.
28
0590
