Error Messages
The following describes startup and Client Error Messages.
Startup Messages
Section titled “Startup Messages”Unable to get host information for host name:- Explanation:
- The host name in the SERVER.MAP file is not valid.
- Action:
- Verify that the SERVER.MAP file contains valid host name entries for all of the defined servers. Try using the IP address in place of a host name to avoid name resolution issues. If an IP address was specified, try using a host name.
Unable to get host information for host address:- Explanation:
- The address in the SERVER.MAP file is not valid. Either the format is not correct or the address does not exist.
- Action:
- Verify that the SERVER.MAP file contains valid addresses for all the defined servers. Try using the IP address in place of a host name to avoid name resolution issues. If an IP address was specified, try using a host name.
Invalid SERVER.MAP entry for Server:- Explanation:
- The entry in the SERVER.MAP file is not valid.
- Action:
- Verify that the entries in the SERVER.MAP file are not missing any fields.
Unable to connect to Server:- Explanation:
- The client was unsuccessful in its attempt to connect to the server.
- Action:
- Verify that the Startup Program (tsmgr) is running on the server.
Verify that the port number in the SERVER.MAP file is 5680. If the default port is being overridden, verify that the port number in the SERVER.MAP file and the port number used by the DataServer are the same.
Verify that the firewall is set to allow the port (default 5680). If the default port is being overridden, verify that the firewall is set to allow the port defined in the SERVER.MAP file.
Verify that the network is up and functional. Try alternate methods of communicating with the Server (e.g., ping, telnet, rlogin, rcp, ftp) or notify your network administrator.
Client Error Messages
Section titled “Client Error Messages”Error 103- Explanation:
- Operating system error. When running TS Network DataServer, there might be an error from a call made to the Socket API. The cause may be a broken or lost connection to the server.
- Action:
- The client must exit Basic and restart.
From the TS Network Basic with DataServer Installation Guide, version 8.9.1. Open this page in the PDF