Resolution:
RTserver could not create a socket for binding to a particular port. The most common reason is that another process has already bound to a socket at that port. To check to see if some other process is running on the port, use the netstat command.

Under Windows or UNIX, type the following from the command console:

      netstat -a -p tcp

where:

-a Displays all connections and listening ports.
-p proto Shows connections for the protocol specified by proto.

proto may be TCP or UDP. If used with the -s option to display per-protocol statistics, proto may be TCP, UDP, or IP.

An example of why the port may already be in use is if there is a process which also listens on the port in question. If the process is launched prior to RTserver, RTserver will generate the following error message:

    "TAL-SS-50011-I Child failed.  Try running again with the -no_daemon option to find out why."


Another reason that this error may be seen is if the DNS resolution of the hostname does not map to the right IP address. To test for this, replace the hostname in the conn_names LCN with the actual IP address

Example:   setopt Conn_Names  tcp:125.28.132.22:5101

If this resolves the problem, you should check your hostname file (/etc/hosts on UNIX) to make sure that the hostname resolves to the correct IP address.

TAL-SS-10105-E Could not create conn :'socket'.