A past post said:

"as long as they have different server names,
2 instances of dbsrv50 can run on the same machine"

I have not been able to get that to work:

SERVER 1
-x tcpip
-c 4M
-m
-gd all
-gk all
-p 1472
-ti 0
-tq 00:00
-n Enroll_Server
c:\Enroll\Data\Enroll.db


SERVER 2
-x tcpip
-c 4M
-m
-gd all
-gk all
-p 1472
-ti 0
-tq 00:00
-n Enroll_Test
c:\Enroll\DataTest\Enrolltest.db


ERROR Message when starting SERVER 2
WARNING
Unable to start -- Unable to initialize requested communication links

Why?


TIA
Mike

Mike,

if you want to run two servers on the same box, they have to use different
TCP/IP ports - and you will have to specify a particular port for the 2nd
server.

Look at the example from the SA 5.5 help below.

HTH
Volker



Network Guide
CHAPTER 5. SQL Anywhere Components
Network communications parameters
ServerPORT parameter

Example for the ServerPORT parameter:


1. Start a SQL Anywhere network server:
dbsrv50 -x tcpip c:\sqlany50\sademo.db
->Port number 1498 is now taken.

2. Attempt to start another database server:
dbsrv50 -x tcpip c:\sqlany50\sademo2.db
-> This fails with an error "Unable to initialize communication links",
as the port is currently allocated.

3. Start another database server, assigning a different port number to it:
dbsrv50 -x tcpip{ServerPort=1499} c:\sqlany50\sademo2.db
-> This should succeed as long as 1499 is not a reserved port and no other
application has allocated it.

4. The following command line allows a client to communicate with servers on
both ports:
dbclient -x tcpip{ServerPort=1499;ServerPort=1498} sademo


"Mike" <mike777iii (AT) NOSPAM_yahoo_ (DOT) com> wrote in
news:472037ae$2 (AT) forums-1-dub (DOT) ..

Volker,

This worked great: {ServerPort=1499}

Thank you for providing the example. Now I understand it.


Mike


Volker Barth wrote: