Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Sybase ODBC Driver SQLState 08001

3 posts in General Discussion Last posting was on 2011-09-09 19:14:47.0Z
Jeff Pryslak Posted on 2011-09-06 22:04:45.0Z
Sender: 2225.4e667d51.1804289383@sybase.com
From: Jeff Pryslak
Newsgroups: sybase.public.ase.general
Subject: Sybase ODBC Driver SQLState 08001
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4e6698fd.2b9a.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 6 Sep 2011 15:04:45 -0700
X-Trace: forums-1-dub 1315346685 10.22.241.41 (6 Sep 2011 15:04:45 -0700)
X-Original-Trace: 6 Sep 2011 15:04:45 -0700, 10.22.241.41
Lines: 33
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30516
Article PK: 72697

Hi All

I was working on porting apps with a customer on the phone
that had an issue. They are starting to moving their 32bit
winXP apps to 64bit Windows 7.

They are using the 32bit ODBC driver from Sybase and kept
getting
[08001] SQLSTATE: Client unable to establish a connection
(30012)

So, after messing with this development system for an hour,
we finally used 'ping host'. i know, DUH.

Guess what we got, the ipv6 address. The ODBC driver needs
the IPv4 address, so we did a
ping -4 host
this IP address was the VMWare hostnet address... and not
the inbound IP for the VM session since it is set to
bridged. So, we hard coded that in the
c:\system32\drivers\etc\hosts and are now good to go. what
a pain. This is the first time i have seen the VM not get a
proper address from dhcp. we are looking at that config,
but it looks right... anyway.

anyone have a better solution for this? did i miss
something?
i was wondering if it is a 32bit client issue, but the docs
say i can run in a dual stack mode. not a driver expert,
and just happy it is working.

thanks
jeff


Cory Sane [TeamSybase] Posted on 2011-09-09 12:40:32.0Z
From: "Cory Sane [TeamSybase]" <cory!=sane>
Newsgroups: sybase.public.ase.general
References: <4e6698fd.2b9a.1681692777@sybase.com>
In-Reply-To: <4e6698fd.2b9a.1681692777@sybase.com>
Subject: Re: Sybase ODBC Driver SQLState 08001
Lines: 45
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e6a0940$1@forums-1-dub>
Date: 9 Sep 2011 05:40:32 -0700
X-Trace: forums-1-dub 1315572032 10.22.241.152 (9 Sep 2011 05:40:32 -0700)
X-Original-Trace: 9 Sep 2011 05:40:32 -0700, vip152.sybase.com
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30525
Article PK: 72704

Jeff,
You may want to post this in the ODBC news group so that Paul Vero can help you.
He may ask you to open a case with Sybase Support (haha).

I hope to see you next week.


--
Cory Sane
[TeamSybase]
Certified Sybase Associate DBA for ASE 15.0

"Jeff Pryslak" wrote in message news:4e6698fd.2b9a.1681692777@sybase.com...
> Hi All
>
> I was working on porting apps with a customer on the phone
> that had an issue. They are starting to moving their 32bit
> winXP apps to 64bit Windows 7.
>
> They are using the 32bit ODBC driver from Sybase and kept
> getting
> [08001] SQLSTATE: Client unable to establish a connection
> (30012)
>
> So, after messing with this development system for an hour,
> we finally used 'ping host'. i know, DUH.
>
> Guess what we got, the ipv6 address. The ODBC driver needs
> the IPv4 address, so we did a
> ping -4 host
> this IP address was the VMWare hostnet address... and not
> the inbound IP for the VM session since it is set to
> bridged. So, we hard coded that in the
> c:\system32\drivers\etc\hosts and are now good to go. what
> a pain. This is the first time i have seen the VM not get a
> proper address from dhcp. we are looking at that config,
> but it looks right... anyway.
>
> anyone have a better solution for this? did i miss
> something?
> i was wondering if it is a 32bit client issue, but the docs
> say i can run in a dual stack mode. not a driver expert,
> and just happy it is working.
>
> thanks
> jeff


Paul Vero [Sybase] Posted on 2011-09-09 19:14:47.0Z
From: "Paul Vero [Sybase]" <pvero@nospam.com>
Newsgroups: sybase.public.ase.general
References: <4e6698fd.2b9a.1681692777@sybase.com>
Subject: Re: Sybase ODBC Driver SQLState 08001
Lines: 43
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e6a65a7$1@forums-1-dub>
Date: 9 Sep 2011 12:14:47 -0700
X-Trace: forums-1-dub 1315595687 10.22.241.152 (9 Sep 2011 12:14:47 -0700)
X-Original-Trace: 9 Sep 2011 12:14:47 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:30527
Article PK: 72706

Hi Jeff,

What's the exact ODBC Driver version?

Thank you,
-Paul

<Jeff Pryslak> wrote in message news:4e6698fd.2b9a.1681692777@sybase.com...
> Hi All
>
> I was working on porting apps with a customer on the phone
> that had an issue. They are starting to moving their 32bit
> winXP apps to 64bit Windows 7.
>
> They are using the 32bit ODBC driver from Sybase and kept
> getting
> [08001] SQLSTATE: Client unable to establish a connection
> (30012)
>
> So, after messing with this development system for an hour,
> we finally used 'ping host'. i know, DUH.
>
> Guess what we got, the ipv6 address. The ODBC driver needs
> the IPv4 address, so we did a
> ping -4 host
> this IP address was the VMWare hostnet address... and not
> the inbound IP for the VM session since it is set to
> bridged. So, we hard coded that in the
> c:\system32\drivers\etc\hosts and are now good to go. what
> a pain. This is the first time i have seen the VM not get a
> proper address from dhcp. we are looking at that config,
> but it looks right... anyway.
>
> anyone have a better solution for this? did i miss
> something?
> i was wondering if it is a 32bit client issue, but the docs
> say i can run in a dual stack mode. not a driver expert,
> and just happy it is working.
>
> thanks
> jeff