MS SQL Server - SQL Connection problem

Author

SQL Connection problem - Help!

JerryJustic

2006-10-24, 6:36 pm

I have an app using VB/ADO to connect to SQL databases. No problem on more
than 300 client installs... except for one.. (isn't it always the case?)

Well, this one has me pulling my hair out..

For various reasons (the most important being our app is very often
installed on small peer-to-peer networks with no domain server) we use mixed
authentication mode. When we install the database we create our own
logins/users with varying levels of access. These are embedded into our
apps, and we haven't had any problems so far.

In this one case, I was attempting to install our database into a default
instance of a standard SQl Server 2000 (as opposed to MSDE which at least
half our clients use). My login procedure fails with no administrative
access using either the sa login or NT security. The guy logging on is
using an Administrator login and defintely knows the sa password. (This is
using SQLDMO, but ADO is failing also)

I take him into Enterprise Manager opn the server and he can log in, change
the sa password.. checked that sa is the owner, that it is using mixxed
mode, etc.. still cannot connect from a worksation on their network.

I checked to make sure they have no firewall set up.. nothing. This is
Windows 2000, btw..

Anyway.. I tried installing a new instance of SQL. This new instance does
not even show up on the client workstations. Only the original default
instace shows up. Even manually constructing a connection to the new
instance returns the ADO error :

-2147467259 - [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid
connection.

Both of these were installed from a SQL Server CD version : 8.00.194 with
SP4 applied after install.

Could there be some licensing issue which prevents a client from connecting?
(Should I install an instance of MSDE and test with that?) I've googled and
looked at newsgroups til I am blue in the face, but this one really has me
stumped.. Help!

Thanks in advance,
Jerry

P.S. I posted this originally in the ADO group, but I think that group is
dead..

Warren Brunk

2006-10-24, 6:36 pm

Is the application using TCP/IP? Is TCPIP enabled as a protocol on the
database side?

Does their office have an issue with DNS? Maybe try connecting usign IP
address...

Use the SQL Server Client Network Utility by right clicking on the server in
Enterprise Manager, under the general tab, network config, Make suer TCP/IP
is enabled and on top.

thanks,
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/

"JerryJustic" <jerryj@datair.com> wrote in message
news:up%232JzI7GHA.3280@TK2MSFTNGP02.phx.gbl...
>I have an app using VB/ADO to connect to SQL databases. No problem on more
> than 300 client installs... except for one.. (isn't it always the case?)
>
> Well, this one has me pulling my hair out..
>
> For various reasons (the most important being our app is very often
> installed on small peer-to-peer networks with no domain server) we use
> mixed
> authentication mode. When we install the database we create our own
> logins/users with varying levels of access. These are embedded into our
> apps, and we haven't had any problems so far.
>
> In this one case, I was attempting to install our database into a default
> instance of a standard SQl Server 2000 (as opposed to MSDE which at least
> half our clients use). My login procedure fails with no administrative
> access using either the sa login or NT security. The guy logging on is
> using an Administrator login and defintely knows the sa password. (This is
> using SQLDMO, but ADO is failing also)
>
> I take him into Enterprise Manager opn the server and he can log in,
> change
> the sa password.. checked that sa is the owner, that it is using mixxed
> mode, etc.. still cannot connect from a worksation on their network.
>
> I checked to make sure they have no firewall set up.. nothing. This is
> Windows 2000, btw..
>
> Anyway.. I tried installing a new instance of SQL. This new instance does
> not even show up on the client workstations. Only the original default
> instace shows up. Even manually constructing a connection to the new
> instance returns the ADO error :
>
> -2147467259 - [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid
> connection.
>
> Both of these were installed from a SQL Server CD version : 8.00.194 with
> SP4 applied after install.
>
> Could there be some licensing issue which prevents a client from
> connecting?
> (Should I install an instance of MSDE and test with that?) I've googled
> and
> looked at newsgroups til I am blue in the face, but this one really has me
> stumped.. Help!
>
> Thanks in advance,
> Jerry
>
> P.S. I posted this originally in the ADO group, but I think that group is
> dead..
>
>
>

JerryJustic

2006-10-24, 6:36 pm

Sorry.. I should have mentioned that I already did that and both TCP/IP and
Named Pipes are enabled for both servers. I also checked on the client side
and the same are enabled there.

Thanks..
Jerry

"Warren Brunk" < wbrunk@techintsoluti
ons.com> wrote in message
news:O5i3wJJ7GHA.200@TK2MSFTNGP05.phx.gbl...
> Is the application using TCP/IP? Is TCPIP enabled as a protocol on the
> database side?
>
> Does their office have an issue with DNS? Maybe try connecting usign IP
> address...
>
> Use the SQL Server Client Network Utility by right clicking on the server
> in Enterprise Manager, under the general tab, network config, Make suer
> TCP/IP is enabled and on top.
>
> thanks,
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> */
>
>
> "JerryJustic" <jerryj@datair.com> wrote in message
> news:up%232JzI7GHA.3280@TK2MSFTNGP02.phx.gbl...
>
>

Sue Hoegemeier

2006-10-24, 6:37 pm

The error: [DBNETLIB][ConnectionOpen (Invalid
Instance()).]Invalid connection.
is generally due to a connection string problem. Make sure
you are using the correct server name, if it's a named
instance (and verify that no matter what they tell you) make
sure you have specified the server name with
ServerName\InstanceN
ame
Verify the port number especially if you are using this in
the connection string. Make sure you can ping the server
from the client. From the client, try doing a telnet to the
port SQL Server is listening on.

-Sue

On Wed, 11 Oct 2006 13:26:11 -0500, "JerryJustic"
<jerryj@datair.com> wrote:

>Sorry.. I should have mentioned that I already did that and both TCP/IP and
>Named Pipes are enabled for both servers. I also checked on the client side
>and the same are enabled there.
>
>Thanks..
>Jerry
>
>"Warren Brunk" < wbrunk@techintsoluti
ons.com> wrote in message
>news:O5i3wJJ7GHA.200@TK2MSFTNGP05.phx.gbl...
>

JerryJustic

2006-10-24, 6:38 pm

Ok.. I did some research on pinging and telnet and had the user try these.

Ping to the server worked fine. But telnet server port# failed.

They swear they have no software firewall (I remote connected to their
server's desktop and could not detect any). But they cannot tell me if
there is any hardware firewall. This is an internal network.. might there
still be a hardware firewall blobkiong ports? I'm an app programmer..
network setups are a bit out of my league these days.. I told them they
need their hardware guy to get involved..

appreciate the help..

thanks!

Jerry

"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
news:0qrqi2hi02eil95
bcaoj8eonr094vo3bsm@
4ax.com...
> The error: [DBNETLIB][ConnectionOpen (Invalid
> Instance()).]Invalid connection.
> is generally due to a connection string problem. Make sure
> you are using the correct server name, if it's a named
> instance (and verify that no matter what they tell you) make
> sure you have specified the server name with
> ServerName\InstanceN
ame
> Verify the port number especially if you are using this in
> the connection string. Make sure you can ping the server
> from the client. From the client, try doing a telnet to the
> port SQL Server is listening on.
>
> -Sue
>
> On Wed, 11 Oct 2006 13:26:11 -0500, "JerryJustic"
> <jerryj@datair.com> wrote:
>
>

Sponsored Links