ODBC Error in TCPIP Port Options

[Mr Smith]

Please forgive me I'm new to this so this might be a very easy one.

I'm trying to set up an ODBC connection from a WinXP SP2 box towards an
Sybase Server 8.00.03 running on a NetWare 6.5 SP7 server.

I'm pointing the Sybase ODBC 8 driver towards TCP/IP ip_address:2638 The
server does listen on this port as soon as I load the Sybase Server on
NetWare.
Despite which user account I specify I always end up with the error,

"Connection Failed: Connection Error: Error in TCPIP Port Options"

I can't even do a connection test from within the ODBC driver, I aöways
end up with this error.

For the life of me I can't figure out what's cauisng this. I can ping the
server from the WinXP and also connect over telnet on port 2638.

Any ideas anyone?

[Graeme Perrow]

Mr Smith wrote:
> Please forgive me I'm new to this so this might be a very easy one.
>
> I'm trying to set up an ODBC connection from a WinXP SP2 box towards an
> Sybase Server 8.00.03 running on a NetWare 6.5 SP7 server.
>
> I'm pointing the Sybase ODBC 8 driver towards TCP/IP ip_address:2638 The
> server does listen on this port as soon as I load the Sybase Server on
> NetWare.
> Despite which user account I specify I always end up with the error,
>
> "Connection Failed: Connection Error: Error in TCPIP Port Options"

If you can tell us *exactly* what the options are that you are using, we
will be able to tell you which one is causing the problem. If you're
creating a DSN, the easiest way is to execute "dbdsn -g <dsn name>" from
a command prompt and post the output.

--

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
iAnywhere Solutions Inc.
A Sybase company

Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
Developer Community at http://www.ianywhere.com/developer/

[Jeff Albion (Sybase iAnywhere)]

Mr Smith wrote:
> "Connection Failed: Connection Error: Error in TCPIP Port Options"

> Any ideas anyone?

What are your TCP/IP options set to?

On the "Network" tab, the "TCP/IP" protocol should be checked off and
the string beside it should look like:

host=ip_address;port=2638

Alternatively, on the "Advanced" tab in the "Additional parameters" box,
you can type:

LINKS=tcpip(HOST=ip_address;PORT=2638)

Regards,

--
Jeff Albion, Product Support Analyst
Sybase iAnywhere

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs :
http://downloads.sybase.com/swd/summary.do?baseprod=144&client=ianywhere&timeframe=0

[Mr Smith]

On Mon, 04 Feb 2008 04:57:24 -0800, Jeff Albion (Sybase iAnywhere) wrote:

> On the "Network" tab, the "TCP/IP" protocol should be checked off and
> the string beside it should look like:
>
> host=ip_address;port=2638

Thanks a million Jeff, you hit the nail right on the head.
This was my problem, I had the string set to ipaddress;port
in accordance with the instructions I'd been given it only said
to use ipaddress;port So obviously it was wrong.

Thanks again

[Mr Smith]

On Mon, 04 Feb 2008 03:43:22 -0800, Graeme Perrow wrote:

Thanks, please see my reply to Jeff.

[scien...@aol.com]

On Feb 5, 5:04 am, Mr Smith <sm...@somewhere.org> wrote:
> On Mon, 04 Feb 2008 03:43:22 -0800, Graeme Perrow wrote:
>
> Thanks, please see my reply to Jeff.

Please further assist...

How about if the standard port of 2638 is absolutely NOT the port it
is running under ( can't see with netstat -a ) yet I KNOW the engine &
database db files attached are running. How on earth do I find port
number for adaptive server engine when not on standard port ???

adaptive server icon is not showing in live icons on desktop taskbar
so can't look in there. Yet I see engine process running using
tasklist & I know database is processing live on various .db files &
logs.

[Lisa Moody]

Go to Control Panel, Administrative Tools, Services, find your Adaptive
Server Anywhere service, right click on it and select Properties. Go to the
Log On tab and check the box that says Allow Service to interact with
desktop. Click out and stop and restart the service. Now you should have
the little red SQL in your system tray and if you double click on that and
read the log, it will tell you what port it is running on.

The other option is to force the service to use the port you want it to use
(if it can't run on 2638 then you can't force that one, but you can pick
another one, I notice it usually goes to 49152 and higher) by adding the
following parameter to your service starting line:

dsn=YourDSNName -x tcpip(port=nnnn)

Lisa

<scien...@aol.com> wrote in message
news:00fbd0ae-aa77-4388...@2g2000hsn.googlegroups.com...