Server Port Number is Not Unique on the Machine

If a Sybase IQ server is running and you attempt to start another Sybase IQ server on the same machine using the same port number, messages appear in the server log file (*.srvlog).

These messages appear:
Trying to start TCPIP link ...
TCPIP communication link not started
Unable to initialize requested communication links
...
DBSPAWN ERROR:  -85
Communication error

Server failed to start

If you see these messages in the server log file and the server will not start, run the stop_iq command (UNIX) to display the names and port numbers of Sybase IQ servers already running on the machine. Then try to start your server, specifying either a port number that is not in use or no port number. When you start a server and do not provide a port number (and the default port number is already in use), Sybase IQ generates an available port number.

Here are the messages you see in the server log file, when you start the server and do not specify a port number:
Trying to start TCPIP link ...
Unable to start on default port; starting on port
49152 instead
TCPIP link started successfully
Now accepting requests
...
Server started successfully