Resolution:
  There are a number of different error messages you can receive when attempting to start RTserver. The most frequently reported are, TAL-SS-50010-I and TAL-SS-00168-E

  1). TAL-SS-50010-I is the error message generated when attempting to launch an additional instance of RTserver which using the same port as an instance which is already running. The following output is an example of the error that you will see:

  $ rtserver -command rtserver.cm
  SmartSockets RTserver Version 6.4 Revision 1 [GA] 2002/11/20 23:44
  Copyright 1991-2002 TIBCO Software Inc. All Rights Reserved.
  For customer support please email support@tibco.com
  TAL-SS-50011-I Child failed.  Try running again with the -no_daemon option to find out why

  $ rtserver -command rtserver.cm -no_daemon
  SmartSockets RTserver Version 6.4 Revision 1 [GA] 2002/11/20 23:44
  Copyright 1991-2002 TIBCO Software Inc. All Rights Reserved.
  For customer support please email support@tibco.com
  bind: Address already in use
  TAL-SS-50010-I RTserver cannot be started.  There appears to be an RTserver already running.

- - - - - - - - - - - - - - - - - -

  2). TAL-SS-00168-E Is the error message generated when attempting to launch an RTserver when a process other than RTserver is using the port RTserver is trying to use. The following is an example of the error messages you would see:

  $ rtserver -command rtserver1.cm
  SmartSockets RTserver Version 6.4 Revision 2  Internal
  Copyright 1991-2003 TIBCO Software Inc. All Rights Reserved.
  For customer support please email support@tibco.com
  {CONN.client:tcp:OLIVE:5101} TAL-SS-00168-E Conn Handshake Failed: 'end of file'
  TAL-SS-50012-I Creating daemon child process.
  {CONN.client:tcp:OLIVE:5101} TAL-SS-00168-E Conn Handshake Failed: 'end of file'
  TAL-SS-50011-I Child failed.  Try running again with the -no_daemon option to find out why

  $ rtserver -command rtserver1.cm -no_daemon
  {CONN.client:tcp:OLIVE:5101} TAL-SS-00168-E Conn Handshake Failed: 'end of file'

  A common application that uses the same default port as RTserver is Yahoo Messenger which connects to the yahoo server(cs.yahoo.com) on port 5050/TCP for client-to-server communications and listens for peer-to-peer requests on port 5101/TCP . A work around to this particular problem is to launch RTserver first and Yahoo Messenger second, the latter process will seek another port to use.

RTserver fails to launch.