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.

Jaguar Crash

12 posts in General Discussion (old) Last posting was on 2000-03-24 00:20:05.0Z
Jeff Strike Posted on 2000-03-21 15:21:37.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Jaguar Crash
Date: Tue, 21 Mar 2000 09:21:37 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 42
NNTP-Posting-Host: wukkar-2-91.mdm.prk.execpc.com 169.207.211.219
Message-ID: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26132
Article PK: 156810

I lost a disk on an NT server that had previously been running Jaguar
with no problems. Since this was just a development server we hadn't'
been backing it up. No problem, I just re-installed NT (SP6a) and
Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
server then went up and setup the connection cache in Jaguar. I
refreshed the server and attempted to Ping the cache. I got the
following error from the Jaguar Manager:
org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
ok, get out of the manager and go look at the log and I see:

Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: Unable to allocate the connection structure.
Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
executing the method ping of the component Jaguar1/CMPing.
Mar 18 09:17:33 2000: Server is being Aborted.

The Jaguar service has been shutdown and I have to restart it. I have
this exact thing running on two other servers, one development, one
production and they're working fine.

Any suggestions?
-Jeff


Dave Wolf [Sybase] Posted on 2000-03-19 07:44:14.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Jaguar Crash
Date: Sun, 19 Mar 2000 02:44:14 -0500
Lines: 40
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: vpn-eme-010.sybase.com 130.214.8.10
Message-ID: <347_9LiuHeXk$GA.111@forums.sybase.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26124
Article PK: 156804

Thats an error from OpenClient. Can you use OpenClient at all? Like have
you tried ISQL?

Dave Wolf
Internet Applications Division

"Jeff Strike" <jstrike@wje.com> wrote in message
news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
> I lost a disk on an NT server that had previously been running Jaguar
> with no problems. Since this was just a development server we hadn't'
> been backing it up. No problem, I just re-installed NT (SP6a) and
> Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
> server then went up and setup the connection cache in Jaguar. I
> refreshed the server and attempted to Ping the cache. I got the
> following error from the Jaguar Manager:
> org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
> ok, get out of the manager and go look at the log and I see:
>
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
> executing the method ping of the component Jaguar1/CMPing.
> Mar 18 09:17:33 2000: Server is being Aborted.
>
> The Jaguar service has been shutdown and I have to restart it. I have
> this exact thing running on two other servers, one development, one
> production and they're working fine.
>
> Any suggestions?
> -Jeff


Jim O'Neil [Sybase] Posted on 2000-03-20 16:21:26.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 20 Mar 2000 11:21:26 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Jaguar Crash
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 69
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38D65006.99D85607@sybase.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26084
Article PK: 156094


"Dave Wolf [Sybase]" wrote:

> Thats an error from OpenClient. Can you use OpenClient at all? Like have
> you tried ISQL?
>
> Dave Wolf
> Internet Applications Division
>
> "Jeff Strike" <jstrike@wje.com> wrote in message
> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
> > I lost a disk on an NT server that had previously been running Jaguar
> > with no problems. Since this was just a development server we hadn't'
> > been backing it up. No problem, I just re-installed NT (SP6a) and
> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
> > server then went up and setup the connection cache in Jaguar. I
> > refreshed the server and attempted to Ping the cache. I got the
> > following error from the Jaguar Manager:
> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
> > ok, get out of the manager and go look at the log and I see:
> >
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
> > executing the method ping of the component Jaguar1/CMPing.
> > Mar 18 09:17:33 2000: Server is being Aborted.
> >
> > The Jaguar service has been shutdown and I have to restart it. I have
> > this exact thing running on two other servers, one development, one
> > production and they're working fine.
> >
> > Any suggestions?
> > -Jeff

Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
ODBC driver doesn't even talk to the db-library layer, so this problem is
pretty low level. Do you have any other ODBC enabled app to confirm the
connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
you that app have already covered the ODBC angle. If this is working on other
machines, I would take a look at the ODBC versions on the machines -
specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
could be some type of incompatibility with DLLs.
--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc


Jeff Strike Posted on 2000-03-21 14:32:34.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Jaguar Crash
Date: Tue, 21 Mar 2000 08:32:34 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 90
NNTP-Posting-Host: wukkar-2-24.mdm.prk.execpc.com 169.207.211.152
Message-ID: <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26028
Article PK: 154378

I can connect w/PB7 using ODBC w/no problems.

What ODBC versions are you talking about, the ones on the clients or
the ones on the server? The ones on the clients (2 of them) appear to
be working fine, I have other ODBC programs that can connect into the
database on the server just fine. On the server I have an ODBC
connection setup that works when I click Test connection in the setup.
It only fails from Jaguar when I attempt to do the ping. I can even
use the ODBCPing utility in SQL 7 to ping the database on the server.
(Works from both the client and the server) The ODBC version it
returns is the same on the client and the server: 03.70.0820. That
should be the latest and greatest version. Is there anything besides
the mdac patch that I need to apply?

-Jeff

On Mon, 20 Mar 2000 11:21:26 -0500, "Jim O'Neil [Sybase]"

<joneil@sybase.com> wrote:

>"Dave Wolf [Sybase]" wrote:
>
>> Thats an error from OpenClient. Can you use OpenClient at all? Like have
>> you tried ISQL?
>>
>> Dave Wolf
>> Internet Applications Division
>>
>> "Jeff Strike" <jstrike@wje.com> wrote in message
>> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
>> > I lost a disk on an NT server that had previously been running Jaguar
>> > with no problems. Since this was just a development server we hadn't'
>> > been backing it up. No problem, I just re-installed NT (SP6a) and
>> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
>> > server then went up and setup the connection cache in Jaguar. I
>> > refreshed the server and attempted to Ping the cache. I got the
>> > following error from the Jaguar Manager:
>> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
>> > ok, get out of the manager and go look at the log and I see:
>> >
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
>> > executing the method ping of the component Jaguar1/CMPing.
>> > Mar 18 09:17:33 2000: Server is being Aborted.
>> >
>> > The Jaguar service has been shutdown and I have to restart it. I have
>> > this exact thing running on two other servers, one development, one
>> > production and they're working fine.
>> >
>> > Any suggestions?
>> > -Jeff
>
>Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
>ODBC driver doesn't even talk to the db-library layer, so this problem is
>pretty low level. Do you have any other ODBC enabled app to confirm the
>connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
>you that app have already covered the ODBC angle. If this is working on other
>machines, I would take a look at the ODBC versions on the machines -
>specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
>could be some type of incompatibility with DLLs.


Jim O'Neil [Sybase] Posted on 2000-03-21 14:41:50.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 21 Mar 2000 09:41:50 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Jaguar Crash
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 112
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38D78A2E.4D3D8DE4@sybase.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com> <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26026
Article PK: 154376


Jeff Strike wrote:

> I can connect w/PB7 using ODBC w/no problems.
>
> What ODBC versions are you talking about, the ones on the clients or
> the ones on the server? The ones on the clients (2 of them) appear to
> be working fine, I have other ODBC programs that can connect into the
> database on the server just fine. On the server I have an ODBC
> connection setup that works when I click Test connection in the setup.
> It only fails from Jaguar when I attempt to do the ping. I can even
> use the ODBCPing utility in SQL 7 to ping the database on the server.
> (Works from both the client and the server) The ODBC version it
> returns is the same on the client and the server: 03.70.0820. That
> should be the latest and greatest version. Is there anything besides
> the mdac patch that I need to apply?
>
> -Jeff
>
> On Mon, 20 Mar 2000 11:21:26 -0500, "Jim O'Neil [Sybase]"
> <joneil@sybase.com> wrote:
>
> >"Dave Wolf [Sybase]" wrote:
> >
> >> Thats an error from OpenClient. Can you use OpenClient at all? Like have
> >> you tried ISQL?
> >>
> >> Dave Wolf
> >> Internet Applications Division
> >>
> >> "Jeff Strike" <jstrike@wje.com> wrote in message
> >> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
> >> > I lost a disk on an NT server that had previously been running Jaguar
> >> > with no problems. Since this was just a development server we hadn't'
> >> > been backing it up. No problem, I just re-installed NT (SP6a) and
> >> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
> >> > server then went up and setup the connection cache in Jaguar. I
> >> > refreshed the server and attempted to Ping the cache. I got the
> >> > following error from the Jaguar Manager:
> >> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
> >> > ok, get out of the manager and go look at the log and I see:
> >> >
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
> >> > executing the method ping of the component Jaguar1/CMPing.
> >> > Mar 18 09:17:33 2000: Server is being Aborted.
> >> >
> >> > The Jaguar service has been shutdown and I have to restart it. I have
> >> > this exact thing running on two other servers, one development, one
> >> > production and they're working fine.
> >> >
> >> > Any suggestions?
> >> > -Jeff
> >
> >Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
> >ODBC driver doesn't even talk to the db-library layer, so this problem is
> >pretty low level. Do you have any other ODBC enabled app to confirm the
> >connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
> >you that app have already covered the ODBC angle. If this is working on other
> >machines, I would take a look at the ODBC versions on the machines -
> >specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
> >could be some type of incompatibility with DLLs.

We'd be specifically interested in the server here, the clients aren't really
involved in the ODBC connection as you described it. When you go into the Control
Panel->ODBC and look at the About tab, are all the versions of the 8 or so DLLs
listed there the same? How do those version numbers compare with what is working
on the other machines? Can you let us know what you have filled in for the various
Cache properties - the unable to allocate connection structure does look kind of
like an Open Client message which wouldn't make sense for this type of ODBC cache,
so I'm wondering if maybe the connection library for the cache is misdefined?


--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc


Jeff Strike Posted on 2000-03-22 03:09:00.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Jaguar Crash
Date: Tue, 21 Mar 2000 21:09:00 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 137
NNTP-Posting-Host: lianna-1-23.mdm.prk.execpc.com 169.207.210.23
Message-ID: <347_rebgds8ufs4oh4dk5imgm78f367cqh53s4@4ax.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com> <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com> <347_38D78A2E.4D3D8DE4@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25959
Article PK: 155980

On Tue, 21 Mar 2000 09:41:50 -0500, "Jim O'Neil [Sybase]"

<joneil@sybase.com> wrote:

>Jeff Strike wrote:
>
>> I can connect w/PB7 using ODBC w/no problems.
>>
>> What ODBC versions are you talking about, the ones on the clients or
>> the ones on the server? The ones on the clients (2 of them) appear to
>> be working fine, I have other ODBC programs that can connect into the
>> database on the server just fine. On the server I have an ODBC
>> connection setup that works when I click Test connection in the setup.
>> It only fails from Jaguar when I attempt to do the ping. I can even
>> use the ODBCPing utility in SQL 7 to ping the database on the server.
>> (Works from both the client and the server) The ODBC version it
>> returns is the same on the client and the server: 03.70.0820. That
>> should be the latest and greatest version. Is there anything besides
>> the mdac patch that I need to apply?
>>
>> -Jeff
>>
>> On Mon, 20 Mar 2000 11:21:26 -0500, "Jim O'Neil [Sybase]"
>> <joneil@sybase.com> wrote:
>>
>> >"Dave Wolf [Sybase]" wrote:
>> >
>> >> Thats an error from OpenClient. Can you use OpenClient at all? Like have
>> >> you tried ISQL?
>> >>
>> >> Dave Wolf
>> >> Internet Applications Division
>> >>
>> >> "Jeff Strike" <jstrike@wje.com> wrote in message
>> >> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
>> >> > I lost a disk on an NT server that had previously been running Jaguar
>> >> > with no problems. Since this was just a development server we hadn't'
>> >> > been backing it up. No problem, I just re-installed NT (SP6a) and
>> >> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
>> >> > server then went up and setup the connection cache in Jaguar. I
>> >> > refreshed the server and attempted to Ping the cache. I got the
>> >> > following error from the Jaguar Manager:
>> >> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
>> >> > ok, get out of the manager and go look at the log and I see:
>> >> >
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
>> >> > executing the method ping of the component Jaguar1/CMPing.
>> >> > Mar 18 09:17:33 2000: Server is being Aborted.
>> >> >
>> >> > The Jaguar service has been shutdown and I have to restart it. I have
>> >> > this exact thing running on two other servers, one development, one
>> >> > production and they're working fine.
>> >> >
>> >> > Any suggestions?
>> >> > -Jeff
>> >
>> >Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
>> >ODBC driver doesn't even talk to the db-library layer, so this problem is
>> >pretty low level. Do you have any other ODBC enabled app to confirm the
>> >connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
>> >you that app have already covered the ODBC angle. If this is working on other
>> >machines, I would take a look at the ODBC versions on the machines -
>> >specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
>> >could be some type of incompatibility with DLLs.
>
>We'd be specifically interested in the server here, the clients aren't really
>involved in the ODBC connection as you described it. When you go into the Control
>Panel->ODBC and look at the About tab, are all the versions of the 8 or so DLLs
>listed there the same? How do those version numbers compare with what is working
>on the other machines? Can you let us know what you have filled in for the various
>Cache properties - the unable to allocate connection structure does look kind of
>like an Open Client message which wouldn't make sense for this type of ODBC cache,
>so I'm wondering if maybe the connection library for the cache is misdefined?

In the connection cache properties:
Enable cache-by-name access is checked.
Enable connection sanity check is checked.
Num of connections in cache is 10. (the other servers are set higher,
this is a development machine and I'm the only one who uses it)
Service name: Advantage - this matches the odbc connection I have
defined under the System DSN tab.
Server name is StrikeDev
User name is sa
Password is blank. (I don't have one - it worked before like this)

Under the driver tab:
DLL name is odbc32.dll. -Its the only one on the system and the
version is 3.520.4403.2.
The ODBC radio button is selected.

The verson of the SQL driver on the machines that work is 3.70.06.23,
the version on this server is 3.70.08.20. I just realized that I have
not applied the latest mdac from MS on the other servers. Should I
dig up the older mdac from MS and install that?

-Jeff


Jim O'Neil [Sybase] Posted on 2000-03-22 14:31:27.0Z
Newsgroups: sybase.public.easerver
Date: Wed, 22 Mar 2000 09:31:27 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Jaguar Crash
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 157
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38D8D93F.B5A84232@sybase.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com> <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com> <347_38D78A2E.4D3D8DE4@sybase.com> <347_rebgds8ufs4oh4dk5imgm78f367cqh53s4@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25936
Article PK: 155965


Jeff Strike wrote:

> On Tue, 21 Mar 2000 09:41:50 -0500, "Jim O'Neil [Sybase]"
> <joneil@sybase.com> wrote:
>
> >Jeff Strike wrote:
> >
> >> I can connect w/PB7 using ODBC w/no problems.
> >>
> >> What ODBC versions are you talking about, the ones on the clients or
> >> the ones on the server? The ones on the clients (2 of them) appear to
> >> be working fine, I have other ODBC programs that can connect into the
> >> database on the server just fine. On the server I have an ODBC
> >> connection setup that works when I click Test connection in the setup.
> >> It only fails from Jaguar when I attempt to do the ping. I can even
> >> use the ODBCPing utility in SQL 7 to ping the database on the server.
> >> (Works from both the client and the server) The ODBC version it
> >> returns is the same on the client and the server: 03.70.0820. That
> >> should be the latest and greatest version. Is there anything besides
> >> the mdac patch that I need to apply?
> >>
> >> -Jeff
> >>
> >> On Mon, 20 Mar 2000 11:21:26 -0500, "Jim O'Neil [Sybase]"
> >> <joneil@sybase.com> wrote:
> >>
> >> >"Dave Wolf [Sybase]" wrote:
> >> >
> >> >> Thats an error from OpenClient. Can you use OpenClient at all? Like have
> >> >> you tried ISQL?
> >> >>
> >> >> Dave Wolf
> >> >> Internet Applications Division
> >> >>
> >> >> "Jeff Strike" <jstrike@wje.com> wrote in message
> >> >> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
> >> >> > I lost a disk on an NT server that had previously been running Jaguar
> >> >> > with no problems. Since this was just a development server we hadn't'
> >> >> > been backing it up. No problem, I just re-installed NT (SP6a) and
> >> >> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
> >> >> > server then went up and setup the connection cache in Jaguar. I
> >> >> > refreshed the server and attempted to Ping the cache. I got the
> >> >> > following error from the Jaguar Manager:
> >> >> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
> >> >> > ok, get out of the manager and go look at the log and I see:
> >> >> >
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
> >> >> > executing the method ping of the component Jaguar1/CMPing.
> >> >> > Mar 18 09:17:33 2000: Server is being Aborted.
> >> >> >
> >> >> > The Jaguar service has been shutdown and I have to restart it. I have
> >> >> > this exact thing running on two other servers, one development, one
> >> >> > production and they're working fine.
> >> >> >
> >> >> > Any suggestions?
> >> >> > -Jeff
> >> >
> >> >Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
> >> >ODBC driver doesn't even talk to the db-library layer, so this problem is
> >> >pretty low level. Do you have any other ODBC enabled app to confirm the
> >> >connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
> >> >you that app have already covered the ODBC angle. If this is working on other
> >> >machines, I would take a look at the ODBC versions on the machines -
> >> >specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
> >> >could be some type of incompatibility with DLLs.
> >
> >We'd be specifically interested in the server here, the clients aren't really
> >involved in the ODBC connection as you described it. When you go into the Control
> >Panel->ODBC and look at the About tab, are all the versions of the 8 or so DLLs
> >listed there the same? How do those version numbers compare with what is working
> >on the other machines? Can you let us know what you have filled in for the various
> >Cache properties - the unable to allocate connection structure does look kind of
> >like an Open Client message which wouldn't make sense for this type of ODBC cache,
> >so I'm wondering if maybe the connection library for the cache is misdefined?
>
> In the connection cache properties:
> Enable cache-by-name access is checked.
> Enable connection sanity check is checked.
> Num of connections in cache is 10. (the other servers are set higher,
> this is a development machine and I'm the only one who uses it)
> Service name: Advantage - this matches the odbc connection I have
> defined under the System DSN tab.
> Server name is StrikeDev
> User name is sa
> Password is blank. (I don't have one - it worked before like this)
>
> Under the driver tab:
> DLL name is odbc32.dll. -Its the only one on the system and the
> version is 3.520.4403.2.
> The ODBC radio button is selected.
>
> The verson of the SQL driver on the machines that work is 3.70.06.23,
> the version on this server is 3.70.08.20. I just realized that I have
> not applied the latest mdac from MS on the other servers. Should I
> dig up the older mdac from MS and install that?
>
> -Jeff

You sure about the cache properties? For ODBC caches, it's the Server name that
corresponds to the ODBC DSN. The service name is used only in conjunction with Sybase
DirectConnect gateways. As described, I wouldn't think you'd be able to connect from
any of your machines, but I wouldn't exactly expect the error message you are getting.
As for the MDAC version, I don't know of any specific issues that would cause this
behavior just due to the slight difference in driver versions.
--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc


Jeff Strike Posted on 2000-03-23 13:37:55.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Jaguar Crash
Date: Thu, 23 Mar 2000 07:37:55 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Lines: 179
NNTP-Posting-Host: jurzan-1-93.mdm.prk.execpc.com 169.207.208.93
Message-ID: <347_fv6kdsohc6q1cmrg4honjodhkpvtc07lch@4ax.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com> <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com> <347_38D78A2E.4D3D8DE4@sybase.com> <347_rebgds8ufs4oh4dk5imgm78f367cqh53s4@4ax.com> <347_38D8D93F.B5A84232@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25841
Article PK: 155877

On Wed, 22 Mar 2000 09:31:27 -0500, "Jim O'Neil [Sybase]"

<joneil@sybase.com> wrote:

>Jeff Strike wrote:
>
>> On Tue, 21 Mar 2000 09:41:50 -0500, "Jim O'Neil [Sybase]"
>> <joneil@sybase.com> wrote:
>>
>> >Jeff Strike wrote:
>> >
>> >> I can connect w/PB7 using ODBC w/no problems.
>> >>
>> >> What ODBC versions are you talking about, the ones on the clients or
>> >> the ones on the server? The ones on the clients (2 of them) appear to
>> >> be working fine, I have other ODBC programs that can connect into the
>> >> database on the server just fine. On the server I have an ODBC
>> >> connection setup that works when I click Test connection in the setup.
>> >> It only fails from Jaguar when I attempt to do the ping. I can even
>> >> use the ODBCPing utility in SQL 7 to ping the database on the server.
>> >> (Works from both the client and the server) The ODBC version it
>> >> returns is the same on the client and the server: 03.70.0820. That
>> >> should be the latest and greatest version. Is there anything besides
>> >> the mdac patch that I need to apply?
>> >>
>> >> -Jeff
>> >>
>> >> On Mon, 20 Mar 2000 11:21:26 -0500, "Jim O'Neil [Sybase]"
>> >> <joneil@sybase.com> wrote:
>> >>
>> >> >"Dave Wolf [Sybase]" wrote:
>> >> >
>> >> >> Thats an error from OpenClient. Can you use OpenClient at all? Like have
>> >> >> you tried ISQL?
>> >> >>
>> >> >> Dave Wolf
>> >> >> Internet Applications Division
>> >> >>
>> >> >> "Jeff Strike" <jstrike@wje.com> wrote in message
>> >> >> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
>> >> >> > I lost a disk on an NT server that had previously been running Jaguar
>> >> >> > with no problems. Since this was just a development server we hadn't'
>> >> >> > been backing it up. No problem, I just re-installed NT (SP6a) and
>> >> >> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
>> >> >> > server then went up and setup the connection cache in Jaguar. I
>> >> >> > refreshed the server and attempted to Ping the cache. I got the
>> >> >> > following error from the Jaguar Manager:
>> >> >> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
>> >> >> > ok, get out of the manager and go look at the log and I see:
>> >> >> >
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
>> >> >> > executing the method ping of the component Jaguar1/CMPing.
>> >> >> > Mar 18 09:17:33 2000: Server is being Aborted.
>> >> >> >
>> >> >> > The Jaguar service has been shutdown and I have to restart it. I have
>> >> >> > this exact thing running on two other servers, one development, one
>> >> >> > production and they're working fine.
>> >> >> >
>> >> >> > Any suggestions?
>> >> >> > -Jeff
>> >> >
>> >> >Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
>> >> >ODBC driver doesn't even talk to the db-library layer, so this problem is
>> >> >pretty low level. Do you have any other ODBC enabled app to confirm the
>> >> >connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
>> >> >you that app have already covered the ODBC angle. If this is working on other
>> >> >machines, I would take a look at the ODBC versions on the machines -
>> >> >specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
>> >> >could be some type of incompatibility with DLLs.
>> >
>> >We'd be specifically interested in the server here, the clients aren't really
>> >involved in the ODBC connection as you described it. When you go into the Control
>> >Panel->ODBC and look at the About tab, are all the versions of the 8 or so DLLs
>> >listed there the same? How do those version numbers compare with what is working
>> >on the other machines? Can you let us know what you have filled in for the various
>> >Cache properties - the unable to allocate connection structure does look kind of
>> >like an Open Client message which wouldn't make sense for this type of ODBC cache,
>> >so I'm wondering if maybe the connection library for the cache is misdefined?
>>
>> In the connection cache properties:
>> Enable cache-by-name access is checked.
>> Enable connection sanity check is checked.
>> Num of connections in cache is 10. (the other servers are set higher,
>> this is a development machine and I'm the only one who uses it)
>> Service name: Advantage - this matches the odbc connection I have
>> defined under the System DSN tab.
>> Server name is StrikeDev
>> User name is sa
>> Password is blank. (I don't have one - it worked before like this)
>>
>> Under the driver tab:
>> DLL name is odbc32.dll. -Its the only one on the system and the
>> version is 3.520.4403.2.
>> The ODBC radio button is selected.
>>
>> The verson of the SQL driver on the machines that work is 3.70.06.23,
>> the version on this server is 3.70.08.20. I just realized that I have
>> not applied the latest mdac from MS on the other servers. Should I
>> dig up the older mdac from MS and install that?
>>
>> -Jeff
>
>You sure about the cache properties? For ODBC caches, it's the Server name that
>corresponds to the ODBC DSN. The service name is used only in conjunction with Sybase
>DirectConnect gateways. As described, I wouldn't think you'd be able to connect from
>any of your machines, but I wouldn't exactly expect the error message you are getting.
>As for the MDAC version, I don't know of any specific issues that would cause this
>behavior just due to the slight difference in driver versions.

Ok, I deleted the cache and the ODBC DSN for good measure, the I
recreated them both. The server name now matches the DSN. When I
ping the cache Jaguar tells me that it failed and I should check the
log, the log has pretty much the same errors as before, but the
service doen't shut down now. Here's the last few lines from the log:

Mar 22 21:25:23 2000: Unable to allocate the connection structure.
Mar 22 21:25:23 2000: Warning: DLL name is different, using previous
name
Mar 22 21:25:24 2000: cm__odbc_error: SQLError: 2012767392, SQLState:
ˆÅ, ¼døw•9
.

(The first line is repeated several times as it was before)
The ODBC connection does work, and I've tried using both named pipes
and tcp/ip sockets to connect.


Jim O'Neil [Sybase] Posted on 2000-03-23 14:59:49.0Z
Newsgroups: sybase.public.easerver
Date: Thu, 23 Mar 2000 09:59:49 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Jaguar Crash
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Lines: 197
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38DA3164.3D530594@sybase.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com> <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com> <347_38D78A2E.4D3D8DE4@sybase.com> <347_rebgds8ufs4oh4dk5imgm78f367cqh53s4@4ax.com> <347_38D8D93F.B5A84232@sybase.com> <347_fv6kdsohc6q1cmrg4honjodhkpvtc07lch@4ax.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25834
Article PK: 155870


Jeff Strike wrote:

> On Wed, 22 Mar 2000 09:31:27 -0500, "Jim O'Neil [Sybase]"
> <joneil@sybase.com> wrote:
>
> >Jeff Strike wrote:
> >
> >> On Tue, 21 Mar 2000 09:41:50 -0500, "Jim O'Neil [Sybase]"
> >> <joneil@sybase.com> wrote:
> >>
> >> >Jeff Strike wrote:
> >> >
> >> >> I can connect w/PB7 using ODBC w/no problems.
> >> >>
> >> >> What ODBC versions are you talking about, the ones on the clients or
> >> >> the ones on the server? The ones on the clients (2 of them) appear to
> >> >> be working fine, I have other ODBC programs that can connect into the
> >> >> database on the server just fine. On the server I have an ODBC
> >> >> connection setup that works when I click Test connection in the setup.
> >> >> It only fails from Jaguar when I attempt to do the ping. I can even
> >> >> use the ODBCPing utility in SQL 7 to ping the database on the server.
> >> >> (Works from both the client and the server) The ODBC version it
> >> >> returns is the same on the client and the server: 03.70.0820. That
> >> >> should be the latest and greatest version. Is there anything besides
> >> >> the mdac patch that I need to apply?
> >> >>
> >> >> -Jeff
> >> >>
> >> >> On Mon, 20 Mar 2000 11:21:26 -0500, "Jim O'Neil [Sybase]"
> >> >> <joneil@sybase.com> wrote:
> >> >>
> >> >> >"Dave Wolf [Sybase]" wrote:
> >> >> >
> >> >> >> Thats an error from OpenClient. Can you use OpenClient at all? Like have
> >> >> >> you tried ISQL?
> >> >> >>
> >> >> >> Dave Wolf
> >> >> >> Internet Applications Division
> >> >> >>
> >> >> >> "Jeff Strike" <jstrike@wje.com> wrote in message
> >> >> >> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
> >> >> >> > I lost a disk on an NT server that had previously been running Jaguar
> >> >> >> > with no problems. Since this was just a development server we hadn't'
> >> >> >> > been backing it up. No problem, I just re-installed NT (SP6a) and
> >> >> >> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
> >> >> >> > server then went up and setup the connection cache in Jaguar. I
> >> >> >> > refreshed the server and attempted to Ping the cache. I got the
> >> >> >> > following error from the Jaguar Manager:
> >> >> >> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
> >> >> >> > ok, get out of the manager and go look at the log and I see:
> >> >> >> >
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
> >> >> >> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
> >> >> >> > executing the method ping of the component Jaguar1/CMPing.
> >> >> >> > Mar 18 09:17:33 2000: Server is being Aborted.
> >> >> >> >
> >> >> >> > The Jaguar service has been shutdown and I have to restart it. I have
> >> >> >> > this exact thing running on two other servers, one development, one
> >> >> >> > production and they're working fine.
> >> >> >> >
> >> >> >> > Any suggestions?
> >> >> >> > -Jeff
> >> >> >
> >> >> >Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
> >> >> >ODBC driver doesn't even talk to the db-library layer, so this problem is
> >> >> >pretty low level. Do you have any other ODBC enabled app to confirm the
> >> >> >connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
> >> >> >you that app have already covered the ODBC angle. If this is working on other
> >> >> >machines, I would take a look at the ODBC versions on the machines -
> >> >> >specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
> >> >> >could be some type of incompatibility with DLLs.
> >> >
> >> >We'd be specifically interested in the server here, the clients aren't really
> >> >involved in the ODBC connection as you described it. When you go into the Control
> >> >Panel->ODBC and look at the About tab, are all the versions of the 8 or so DLLs
> >> >listed there the same? How do those version numbers compare with what is working
> >> >on the other machines? Can you let us know what you have filled in for the various
> >> >Cache properties - the unable to allocate connection structure does look kind of
> >> >like an Open Client message which wouldn't make sense for this type of ODBC cache,
> >> >so I'm wondering if maybe the connection library for the cache is misdefined?
> >>
> >> In the connection cache properties:
> >> Enable cache-by-name access is checked.
> >> Enable connection sanity check is checked.
> >> Num of connections in cache is 10. (the other servers are set higher,
> >> this is a development machine and I'm the only one who uses it)
> >> Service name: Advantage - this matches the odbc connection I have
> >> defined under the System DSN tab.
> >> Server name is StrikeDev
> >> User name is sa
> >> Password is blank. (I don't have one - it worked before like this)
> >>
> >> Under the driver tab:
> >> DLL name is odbc32.dll. -Its the only one on the system and the
> >> version is 3.520.4403.2.
> >> The ODBC radio button is selected.
> >>
> >> The verson of the SQL driver on the machines that work is 3.70.06.23,
> >> the version on this server is 3.70.08.20. I just realized that I have
> >> not applied the latest mdac from MS on the other servers. Should I
> >> dig up the older mdac from MS and install that?
> >>
> >> -Jeff
> >
> >You sure about the cache properties? For ODBC caches, it's the Server name that
> >corresponds to the ODBC DSN. The service name is used only in conjunction with Sybase
> >DirectConnect gateways. As described, I wouldn't think you'd be able to connect from
> >any of your machines, but I wouldn't exactly expect the error message you are getting.
> >As for the MDAC version, I don't know of any specific issues that would cause this
> >behavior just due to the slight difference in driver versions.
>
> Ok, I deleted the cache and the ODBC DSN for good measure, the I
> recreated them both. The server name now matches the DSN. When I
> ping the cache Jaguar tells me that it failed and I should check the
> log, the log has pretty much the same errors as before, but the
> service doen't shut down now. Here's the last few lines from the log:
>
> Mar 22 21:25:23 2000: Unable to allocate the connection structure.
> Mar 22 21:25:23 2000: Warning: DLL name is different, using previous
> name
> Mar 22 21:25:24 2000: cm__odbc_error: SQLError: 2012767392, SQLState:
> ˆÅ, ¼døw•9
> .
>
> (The first line is repeated several times as it was before)
> The ODBC connection does work, and I've tried using both named pipes
> and tcp/ip sockets to connect.

This is the kind of behavior I might expect on Win2000 with ODBC caches, but I'm at a loss
as to what might be causing it in your environment. Short of opening an issue with
support, the only other suggestion I have is running an ODBC trace so we can see which ODBC
API call choked - often there's a more helpful message in the trace file that will point to
a resolution.
--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc


Jeff Strike Posted on 2000-03-24 00:20:05.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Jaguar Crash
Date: Thu, 23 Mar 2000 18:20:05 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 28
NNTP-Posting-Host: wukkar-2-58.mdm.prk.execpc.com 169.207.211.186
Message-ID: <347_24cldsc9n448s0kltaqqis1g48tu9lp4ig@4ax.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com> <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com> <347_38D78A2E.4D3D8DE4@sybase.com> <347_rebgds8ufs4oh4dk5imgm78f367cqh53s4@4ax.com> <347_38D8D93F.B5A84232@sybase.com> <347_fv6kdsohc6q1cmrg4honjodhkpvtc07lch@4ax.com> <347_38DA3164.3D530594@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25778
Article PK: 154342


>This is the kind of behavior I might expect on Win2000 with ODBC caches, but I'm at a loss
>as to what might be causing it in your environment. Short of opening an issue with
>support, the only other suggestion I have is running an ODBC trace so we can see which ODBC
>API call choked - often there's a more helpful message in the trace file that will point to
>a resolution.

Issue number 41063092. She's as stumped as everyone else. She's
looking at my afconfig.dat file right now.

You mentioned Win 2000, I'm pretty sure the mdac upgrade I installed
(ver 2.5) was what they ship w/Win2K. I don't know if that'll make a
difference or not...that's why I mentioned droping back a version to
2.1.

I started the ODBC Tracing, went and did a few pings on the database
from the manager...they of course failed. I went and looked at the
log and there was nothing in it. I ran odbcping on the database to
make sure the log was working and there was in fact information in it.
I then tried to ping the database from the manager again, it failed
and there was nothing new in the log.

-Jeff


Jeff Strike Posted on 2000-03-22 17:24:26.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Jaguar Crash
Date: Wed, 22 Mar 2000 11:24:26 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 164
NNTP-Posting-Host: wjetelnet.wje.com 12.27.23.134
Message-ID: <347_f50ids8rt6f3c41djd47d6uicqdlrceh2p@4ax.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com> <347_38D65006.99D85607@sybase.com> <347_7g1fdskcha4an13ckepe07fr0q55fphoj2@4ax.com> <347_38D78A2E.4D3D8DE4@sybase.com> <347_rebgds8ufs4oh4dk5imgm78f367cqh53s4@4ax.com> <347_38D8D93F.B5A84232@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:25914
Article PK: 155942

On Wed, 22 Mar 2000 09:31:27 -0500, "Jim O'Neil [Sybase]"

<joneil@sybase.com> wrote:

>Jeff Strike wrote:
>
>> On Tue, 21 Mar 2000 09:41:50 -0500, "Jim O'Neil [Sybase]"
>> <joneil@sybase.com> wrote:
>>
>> >Jeff Strike wrote:
>> >
>> >> I can connect w/PB7 using ODBC w/no problems.
>> >>
>> >> What ODBC versions are you talking about, the ones on the clients or
>> >> the ones on the server? The ones on the clients (2 of them) appear to
>> >> be working fine, I have other ODBC programs that can connect into the
>> >> database on the server just fine. On the server I have an ODBC
>> >> connection setup that works when I click Test connection in the setup.
>> >> It only fails from Jaguar when I attempt to do the ping. I can even
>> >> use the ODBCPing utility in SQL 7 to ping the database on the server.
>> >> (Works from both the client and the server) The ODBC version it
>> >> returns is the same on the client and the server: 03.70.0820. That
>> >> should be the latest and greatest version. Is there anything besides
>> >> the mdac patch that I need to apply?
>> >>
>> >> -Jeff
>> >>
>> >> On Mon, 20 Mar 2000 11:21:26 -0500, "Jim O'Neil [Sybase]"
>> >> <joneil@sybase.com> wrote:
>> >>
>> >> >"Dave Wolf [Sybase]" wrote:
>> >> >
>> >> >> Thats an error from OpenClient. Can you use OpenClient at all? Like have
>> >> >> you tried ISQL?
>> >> >>
>> >> >> Dave Wolf
>> >> >> Internet Applications Division
>> >> >>
>> >> >> "Jeff Strike" <jstrike@wje.com> wrote in message
>> >> >> news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
>> >> >> > I lost a disk on an NT server that had previously been running Jaguar
>> >> >> > with no problems. Since this was just a development server we hadn't'
>> >> >> > been backing it up. No problem, I just re-installed NT (SP6a) and
>> >> >> > Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
>> >> >> > server then went up and setup the connection cache in Jaguar. I
>> >> >> > refreshed the server and attempted to Ping the cache. I got the
>> >> >> > following error from the Jaguar Manager:
>> >> >> > org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
>> >> >> > ok, get out of the manager and go look at the log and I see:
>> >> >> >
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> >> >> > Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
>> >> >> > executing the method ping of the component Jaguar1/CMPing.
>> >> >> > Mar 18 09:17:33 2000: Server is being Aborted.
>> >> >> >
>> >> >> > The Jaguar service has been shutdown and I have to restart it. I have
>> >> >> > this exact thing running on two other servers, one development, one
>> >> >> > production and they're working fine.
>> >> >> >
>> >> >> > Any suggestions?
>> >> >> > -Jeff
>> >> >
>> >> >Well, it's MS SQLServer, so OpenClient wouldn't be an issue here. Microsoft's
>> >> >ODBC driver doesn't even talk to the db-library layer, so this problem is
>> >> >pretty low level. Do you have any other ODBC enabled app to confirm the
>> >> >connection (like PB or Access or MSQuery) - I'm not familiar with RapidSQL, so
>> >> >you that app have already covered the ODBC angle. If this is working on other
>> >> >machines, I would take a look at the ODBC versions on the machines -
>> >> >specifically ODBC32.DLL and SQLSRV32.DLL (the SQLServer ODBC driver). This
>> >> >could be some type of incompatibility with DLLs.
>> >
>> >We'd be specifically interested in the server here, the clients aren't really
>> >involved in the ODBC connection as you described it. When you go into the Control
>> >Panel->ODBC and look at the About tab, are all the versions of the 8 or so DLLs
>> >listed there the same? How do those version numbers compare with what is working
>> >on the other machines? Can you let us know what you have filled in for the various
>> >Cache properties - the unable to allocate connection structure does look kind of
>> >like an Open Client message which wouldn't make sense for this type of ODBC cache,
>> >so I'm wondering if maybe the connection library for the cache is misdefined?
>>
>> In the connection cache properties:
>> Enable cache-by-name access is checked.
>> Enable connection sanity check is checked.
>> Num of connections in cache is 10. (the other servers are set higher,
>> this is a development machine and I'm the only one who uses it)
>> Service name: Advantage - this matches the odbc connection I have
>> defined under the System DSN tab.
>> Server name is StrikeDev
>> User name is sa
>> Password is blank. (I don't have one - it worked before like this)
>>
>> Under the driver tab:
>> DLL name is odbc32.dll. -Its the only one on the system and the
>> version is 3.520.4403.2.
>> The ODBC radio button is selected.
>>
>> The verson of the SQL driver on the machines that work is 3.70.06.23,
>> the version on this server is 3.70.08.20. I just realized that I have
>> not applied the latest mdac from MS on the other servers. Should I
>> dig up the older mdac from MS and install that?
>>
>> -Jeff
>
>You sure about the cache properties? For ODBC caches, it's the Server name that
>corresponds to the ODBC DSN. The service name is used only in conjunction with Sybase
>DirectConnect gateways. As described, I wouldn't think you'd be able to connect from
>any of your machines, but I wouldn't exactly expect the error message you are getting.
>As for the MDAC version, I don't know of any specific issues that would cause this
>behavior just due to the slight difference in driver versions.

I'm 99.99% sure this is the way I had it setup before, but I could be
wrong. I'll try changing the server name to match the DSN and see
what happens.


Jeff Strike Posted on 2000-03-23 03:28:24.0Z
Newsgroups: sybase.public.easerver
From: Jeff Strike <jstrike@wje.com>
Subject: Re: Jaguar Crash
Date: Wed, 22 Mar 2000 21:28:24 -0600
Reply-To: jstrike@wje.com
X-Newsreader: Forte Agent 1.7/32.534
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 59
NNTP-Posting-Host: jurzan-2-134.mdm.prk.execpc.com 169.207.209.72
Message-ID: <347_0k3jdsk2hf83sf2spqk1jdtdv77g3pm1k0@4ax.com>
References: <347_ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com> <347_9LiuHeXk$GA.111@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26105
Article PK: 156108

Yes, I can connect into the database and execute queries and/or stored
procedures w/no problem. I haven't tried ISQL specifically but I have
a program called Rapid SQL that I use to work on stored procs, that
works fine.

-Jeff

On Sun, 19 Mar 2000 02:44:14 -0500, "Dave Wolf [Sybase]"

<dwolf@sybase.com> wrote:

>Thats an error from OpenClient. Can you use OpenClient at all? Like have
>you tried ISQL?
>
>Dave Wolf
>Internet Applications Division
>
>"Jeff Strike" <jstrike@wje.com> wrote in message
>news:ce4fdscb16c2dl5ged9r7vasebpta4ampd@4ax.com...
>> I lost a disk on an NT server that had previously been running Jaguar
>> with no problems. Since this was just a development server we hadn't'
>> been backing it up. No problem, I just re-installed NT (SP6a) and
>> Jaguar sans the demo. I setup the connection via ODBC to our SQL 7
>> server then went up and setup the connection cache in Jaguar. I
>> refreshed the server and attempted to Ping the cache. I got the
>> following error from the Jaguar Manager:
>> org.omg.CORBA.COMM_FAILURE:localhost:9000-Connection Refused. I click
>> ok, get out of the manager and go look at the log and I see:
>>
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: Unable to allocate the connection structure.
>> Mar 18 09:17:33 2000: A Fatal NT Exception[0xc0000005] received while
>> executing the method ping of the component Jaguar1/CMPing.
>> Mar 18 09:17:33 2000: Server is being Aborted.
>>
>> The Jaguar service has been shutdown and I have to restart it. I have
>> this exact thing running on two other servers, one development, one
>> production and they're working fine.
>>
>> Any suggestions?
>> -Jeff
>