freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
RE: [freetds] RE: [ISQL]ERROR: Could not SQLConnect
- From: "Lowden, James K" <LowdenJK AT bernstein.com>
- To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
- Subject: RE: [freetds] RE: [ISQL]ERROR: Could not SQLConnect
- Date: Mon, 7 Jun 2004 15:53:37 -0400
> From: freetds-bounces AT lists.ibiblio.org
> [mailto:freetds-bounces AT lists.ibiblio.org]On Behalf Of
> jun_chen AT bankone.com
> Sent: June 7, 2004 3:29 PM
>
> When I run isql -v visdb <username> <password>, I got the
> following error:
> [S1000][unixODBC][FreeTDS][SQL Server]Unable to connect to data source
> [28000][unixODBC][FreeTDS][SQL Server]Login incorrect.
> [08W10][unixODBC][FreeTDS][SQL Server]ASA Error -83:
> Specified database
> not found
> [ISQL]ERROR: Could not SQLConnect
>
> The same configuration works fine for MS SQL Server.
Can you log into visdb.visdb with tsql?
For ASA, the section name (dataserver name) in freetds.conf must be the same
as the the ASA database name.
--jkl
>
> I installed the sybase client into the same machine and I
> used the same
> username and password to connect to the sybase server without
> any issue.
> So I know the username and password I used are good ones.
>
> Any idea, Freddy77?
>
> Jun Chen
>
>
>
>
> freetds-request AT lists.ibiblio.org
> Sent by: freetds-bounces AT lists.ibiblio.org
> 05/19/2004 12:06 PM
> Please respond to freetds
>
>
> To: freetds AT lists.ibiblio.org
> cc:
> Subject: FreeTDS Digest, Vol 16, Issue 24
>
> 1. RE: [ISQL]ERROR: Could not SQLConnect (ZIGLIO, Frediano, VF-IT)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 19 May 2004 17:31:46 +0200
> From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
> Subject: RE: [freetds] [ISQL]ERROR: Could not SQLConnect
> To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
> Message-ID:
> <F7F148C986A2A84F930FEB8C3B169EA02504F5 AT OPDMEXO01.omnitel.it>
> Content-Type: text/plain; charset="us-ascii"
>
> >
> > Hi,
> >
> > I were trying to setup unixODBC and freetds in Redhat
> > Advanced Server 2.1
> > to access Sybase and MS SQL Server.
> > The freetds version is 0.62.3 and unixODBC's is 2.2.8.
> >
> > I used the following to configure freetds:
> > ./configure --prefix=/usr/local/freetds --disable-threadsafe
> > --with-tdsver=7.0 --with-unixodbc=/usr/local/unixODBC
> >
> > After I configured freetds.conf, I can use Perl DBI and Perl
> > DBD::Sybase
> > to access a Sybase database and
> > MS SQL Server. I can also use tsql (tsql -S views -U <username> -P
> > <password> to access those databases without any issue.
> >
> > I configured odbcinst.ini and odbc.ini by using odbcinst.
> > Here are the
> > file odbcinst.ini:
> >
> > [DB2]
> > Description = DB2 Driver
> > Driver = /usr/IBMdb2/V7.1/lib/libdb2.so
> > FileUsage = 1
> >
> > [TDS]
> > Description = v0.62
> > Driver = /usr/local/freetds/lib/libtdsodbc.so
> > FileUsage = 1
> >
> > Here is odbc.ini:
> >
> > [inv]
> > Description = Tivoli Production Inventory DB2
> > Driver = DB2
> >
> > [views]
> > Description = CSIRT MS SQL Server
> > Driver = TDS
> >
> > [peregrine]
> > Description = Peregrine MS SQL Server
> > Driver = TDS
> >
> > [visdb]
> > Driver = TDS
> > Description = SAN Point Sybase DB
> > Trace = No
> > Servername = 204.151.176.177
>
> Servername do not point do a real server (DNS or ip) but to
> freetds.conf
> servername. If you use DBD::Sybase I would suggest to specify
> Servername
> with entry in freetds.conf (or you can use Server with ip address).
>
> > Database = visdb
> > Trace = Yes
> > TraceFile = visdb.log
> > UID = DBA
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.
If you, as the intended recipient of this message, the purpose of which is to
inform and update our clients, prospects and consultants of developments
relating to our services and products, would not like to receive further
e-mail correspondence from the sender, please "reply" to the sender
indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New York,
NY 10105.
-
[freetds] RE: [ISQL]ERROR: Could not SQLConnect,
jun_chen, 06/07/2004
- <Possible follow-up(s)>
- RE: [freetds] RE: [ISQL]ERROR: Could not SQLConnect, Lowden, James K, 06/07/2004
Archive powered by MHonArc 2.6.24.