Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection. ????????

2,490 views
Skip to first unread message

Lars-Erik Aabech

unread,
Jun 10, 2002, 6:43:03 AM6/10/02
to
Why, oh why do I get this when I try to connect to my SQL Server?? :((

Please help!

Lars-Erik


jimmers

unread,
Jun 10, 2002, 10:42:40 AM6/10/02
to
If You use named instance of MS SQL Server 2000 then try to connect via
Query Analyzer to the server specifying exactly the same
servername\instancename, login, password (or trusted connection).

Cheers

jimmers


"Lars-Erik Aabech" <lars-eri...@markedspartner.no> wrote in message
news:OJQIAuGECHA.2444@tkmsftngp05...

Lars-Erik Aabech

unread,
Jun 10, 2002, 11:16:42 AM6/10/02
to
I had to make an ODBC DSN connection where I specifically set the connection
type to be TCP/IP via 1433, not default - which is - 1433 :/ lame shitt...

Anyways.. I couldn't register it in my Enterprise Manager..

Lars-Erik

"jimmers" <jim...@yandex.ru> wrote in message
news:eSSc7zIECHA.2440@tkmsftngp05...

Hina Masud [MS]

unread,
Jun 20, 2002, 10:42:50 AM6/20/02
to
Hi,

if you are using the correct SQL server name (check by running sp_helpserver or sp_servername to check its name and network name). The following error
message can be raised when connecting to named instances of
SQL server 2000 when the SQL server machine is on a different subnet.

Connection Failed:
[Microsoft][ODBC SQL Server Driver][DBNetlib]Connection Open (Invalid
Instance()).

Connection to a named instance of SQL server 2000 should be made using the format
'VirtualServer\Instancename'. if the IP address of a machine running a named SQL server instance
(ONE)is 192.141.128.140, you can connect to the named instance using
192.141.128.140\ONE for the servername. To avoid a client app from using the above convention for a servername a client
alias can be created using the client network utility. Client network utility
can be initiated by

Start->Programs ->Microsoft SQL Server->Client Network Utility

and you can create a Named Pipes or TCP/IP alias for your server and try connecting again.

Thank you
Hina Masud
Microsoft

Disclaimer:
This posting is provided AS IS with no warranties, and confers no rights.
Get Secure! -> http://www.microsoft.com/security


--------------------
-From: "Lars-Erik Aabech" <lars-eri...@markedspartner.no>
-References: <OJQIAuGECHA.2444@tkmsftngp05> <eSSc7zIECHA.2440@tkmsftngp05>
-Subject: Re: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection. ????????
-Date: Mon, 10 Jun 2002 17:16:42 +0200
-Lines: 35
-X-Priority: 3
-X-MSMail-Priority: Normal
-X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
-X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
-Message-ID: <eIFt6GJECHA.1980@tkmsftngp04>
-Newsgroups: microsoft.public.sqlserver.security
-NNTP-Posting-Host: 195.70.185.89
-Path: cpmsftngxa08!tkmsftngp01!tkmsftngp04
-Xref: cpmsftngxa08 microsoft.public.sqlserver.security:6307
-X-Tomcat-NG: microsoft.public.sqlserver.security
-
-I had to make an ODBC DSN connection where I specifically set the connection
-type to be TCP/IP via 1433, not default - which is - 1433 :/ lame shitt...
-
-Anyways.. I couldn't register it in my Enterprise Manager..
-
-Lars-Erik
-
-"jimmers" <jim...@yandex.ru> wrote in message
-news:eSSc7zIECHA.2440@tkmsftngp05...
-> If You use named instance of MS SQL Server 2000 then try to connect via
-> Query Analyzer to the server specifying exactly the same
-> servername\instancename, login, password (or trusted connection).
->
-> Cheers
->
-> jimmers
->
->
-> "Lars-Erik Aabech" <lars-eri...@markedspartner.no> wrote in message
-> news:OJQIAuGECHA.2444@tkmsftngp05...
-> > Why, oh why do I get this when I try to connect to my SQL Server?? :((
-> >
-> > Please help!
-> >
-> > Lars-Erik
-> >
-> >
->
->
->
->
->
->
-
-
-


0 new messages