Thursday, February 16, 2012

cannot connect to sql 2005 from isql

I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
server, I can use sqlcmd to connect to the database. However, I failed
to connect to the database from a client machine using sql7's isql. The
error was
DB-Library: Unable to connect: SQL Server is unavailable or does not
exist.
Net-Library error 1326: ConnectionOpen (CreateFile()).
Please advise, thanks.Is the server instance listening to Named Pipes?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AH" <hhhsu7a@.yahoo.com> wrote in message
news:1167102465.643393.154420@.73g2000cwn.googlegroups.com...
>I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> server, I can use sqlcmd to connect to the database. However, I failed
> to connect to the database from a client machine using sql7's isql. The
> error was
> DB-Library: Unable to connect: SQL Server is unavailable or does not
> exist.
> Net-Library error 1326: ConnectionOpen (CreateFile()).
> Please advise, thanks.
>|||Hi
If this is SQL Express then network protocols are disabled by default. Check
which network protocols are being used, if necessary you may wish to create
an alias on the client to use TCP/IP to connect to the instance. Also make
sure that the client machine has the latest service packs.
John
"AH" wrote:
> I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> server, I can use sqlcmd to connect to the database. However, I failed
> to connect to the database from a client machine using sql7's isql. The
> error was
> DB-Library: Unable to connect: SQL Server is unavailable or does not
> exist.
> Net-Library error 1326: ConnectionOpen (CreateFile()).
> Please advise, thanks.
>|||John,
I tried to open TCP on the server but still got the same error when
connecting from client machine. The client has SQL 7 SP2. Do I need to
go to SP 4?
Does Microsoft provide any tool to trace the connection?
Thanks,
Andy
John Bell wrote:
> Hi
> If this is SQL Express then network protocols are disabled by default. Check
> which network protocols are being used, if necessary you may wish to create
> an alias on the client to use TCP/IP to connect to the instance. Also make
> sure that the client machine has the latest service packs.
> John
>
> "AH" wrote:
> > I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> > server, I can use sqlcmd to connect to the database. However, I failed
> > to connect to the database from a client machine using sql7's isql. The
> > error was
> > DB-Library: Unable to connect: SQL Server is unavailable or does not
> > exist.
> > Net-Library error 1326: ConnectionOpen (CreateFile()).
> >
> > Please advise, thanks.
> >
> >

No comments:

Post a Comment