For errors encountered during installation, dedicated topics are provided, including Anti-Virus Issues, Error Messages, Network Issues, Permissions, and issues related to Services not starting.
A complete Errors List is provided to detail messages for known conditions.
This topic is dedicated to help diagnose other issues that might occur. This content is enhanced as new situations are identified.
Problem: This message results when a command is issued to a closed socket connection. For example, type EXIT or QUIT at TCL when using the browser emulator, then type X and press Enter/Send. The command X has nowhere to go.
Solution: If there is nothing to do, click the red Close Terminal button at the bottom of the emulator. If there is more to do, click the yellow Reset Connection button at the top of the emulator. Outside of the emulator ensure that a connection has been established to the server.
|
Problem: Either the hostname/IP or the socket/port are incorrect.
Solution: Telnet using a preferred terminal emulator. Note the hostname or IP and the socket port number required for a successful connection. The Profile must use the hostname to connect to the server. The port should be used in the Telnet/SSH port field in the EntryPoint definition, and/or the port field in MV Components maintenance.
|
Problem: This message is familar to object-oriented programmers. Essentially an unassigned variable has been used. This usually occurs when an operation fails to return data, and then another operation expects to use that data. The cause of the problem is usually revealed in messages prior to this message. For example, this error occurs if a connection fails due to an incorrect socket port number, and then an attempt is made to send data to that port.
Solution: Test for failure after an operation, prior to moving on to the next. If a connection failed then the next operation to use the connection should not assume the connection was successful. As Linkar is enhanced code like this is always being enhanced. Application developers should wrap code in try/catch blocks.
|
