Please be aware that the SAP SQL Anywhere Forum will be shut down on August 29th, 2024 when all it's content will be migrated to the SAP Community.

We have a Windows Server envirnoment with one Server VM running the Database and another Server VM In the network as the Client App machine.

We have no problem accessing a single Database Service from the Client to the first Databse Service. This using the 64 Bit ODBC naming the Host Name and Database Server

However when attempting a second ODBC connecion to a separate SQL Anywhere 17 service on the same Host - with all the settings the same except the the Server Name - ODBC refuses to Connect (both using the default Port)

When accessing the Database from the Server Side we have no problems connecting both.

Any idea why a second ODBC connectio to the same Host but different database Service Name will never connect?

asked 30 Mar '23, 13:36

Glenn%20Barber's gravatar image

Glenn Barber
1.1k274456
accept rate: 8%

Thanks - we were curious if SQLAnywhare could share ports - I guess not

is the -x tcpip (ServerPost=xxxx) the correct parameter to add to the Configuration Service properties?

(30 Mar '23, 16:47) Glenn Barber

Yes - when we turned off the firewall - we could connect to the second database. So it appears that when the service starts up it sees the default port being used and switches to another. So we need to designate the port for each server to avoid the first to start getting the default

permanent link

answered 30 Mar '23, 16:23

Glenn%20Barber's gravatar image

Glenn Barber
1.1k274456
accept rate: 8%

edited 30 Mar '23, 16:40

AFAIK you will have to specify the port for the second server as it cannot use the default port 2638 (which the first database server instance will occupy). Same machine connection might work by using shared memory...

So I suggest to add the different ports to the HOST connection parameter for both services.

(That being said, specifying the SERVER connection parameter should work without specifying the port...)

As usually, adding the LOG connection parameter should show connection diagnostics...

permanent link

answered 30 Mar '23, 15:49

Volker%20Barth's gravatar image

Volker Barth
40.5k365556827
accept rate: 34%

converted 31 Mar '23, 03:07

Just to add: What connection parameters do you use, as host can be specified as its own connection parameter (as "HOST=MyHost:MyPort;Server=MyServer") or in the old fashion via the LINKS parameter as part of the TCPIP options, such as "Server=MyServer;LINKS=ShMem,TCPIP(HOST=MyHost;PORT=MyPort)".

In the first case shared memory is disabled.

(31 Mar '23, 03:38) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×145

question asked: 30 Mar '23, 13:36

question was seen: 645 times

last updated: 31 Mar '23, 03:38