Wednesday, March 7, 2012

Connecting to a second instance of SQL

When I try to connect to an external SQL Server via enterprise manager I
cannot seem to connect to a named instance. In the past this has worked with
no problem when I do ip\instance. However when I now try I am getting invali
d
instance name. The name I am using is correct. I am connecting from
Enterprise manager to a SQL2000 instance. Any ideas why it doesn`t connect ?
SiPlease paste in the exact error message
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:356739A9-573E-4D7D-AF9B-2B0DA95CEE2E@.microsoft.com...
> When I try to connect to an external SQL Server via enterprise manager I
> cannot seem to connect to a named instance. In the past this has worked
> with
> no problem when I do ip\instance. However when I now try I am getting
> invalid
> instance name. The name I am using is correct. I am connecting from
> Enterprise manager to a SQL2000 instance. Any ideas why it doesn`t connect
> ?
>
> Si|||Invalid connection.Connectioopen (Invalid Instance())
Cheers
"Kevin3NF" wrote:

> Please paste in the exact error message
>
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> http://kevin3nf.blogspot.com
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:356739A9-573E-4D7D-AF9B-2B0DA95CEE2E@.microsoft.com...
>
>|||Does the Instance Name contain any invalid character, such as '-'?
Try enclosing the instance name in square brackets, e.g.,
[MyServer\MyInstance].
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:A5D1AFBD-54F6-4600-A7EA-215AEFD7A1C6@.microsoft.com...[vbcol=seagreen]
> Invalid connection.Connectioopen (Invalid Instance())
> Cheers
> "Kevin3NF" wrote:
>|||There are no invalid characters. Even so I tried enclosing in square bracket
s
and still no joy.
Its a puzzle !
Si
"Arnie Rowland" wrote:

> Does the Instance Name contain any invalid character, such as '-'?
> Try enclosing the instance name in square brackets, e.g.,
> [MyServer\MyInstance].
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to th
e
> top yourself.
> - H. Norman Schwarzkopf
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:A5D1AFBD-54F6-4600-A7EA-215AEFD7A1C6@.microsoft.com...
>
>|||Is UDP 1434 open between the SQL Server you are registering
on and the named instance you are trying to register? That
could be what's causing your problems.
You could try an alias and see if that works -
On the SQL Server box where you are trying to register the
named instance, use the Client Network Utility to create an
alias to the named instance and specify the port number
(check the listening port on the named instance).
In that scenario with the alias, you are specifying the port
so you would bypass the SQL Server Resolution Service and
going through UDP 1434.
-Sue
On Mon, 30 Oct 2006 01:20:02 -0800, Simon
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>There are no invalid characters. Even so I tried enclosing in square bracke
ts
>and still no joy.
>Its a puzzle !
>Si
>"Arnie Rowland" wrote:
>

No comments:

Post a Comment