Tuesday, February 14, 2012

Can't connect to new sql server instance

I installed sql server 2000 on a box that already has sql server 2005
installed. I used an instance name of "{machine name}/mssql2k" and I'm
trying to connect using {machine name}/mssql2k. When I open SQL Server
Management Studio and try to connect to the new instance, I get the message
shown below. Please let me know what I need to do to connect.
Thanks,
Keith
TITLE: Connect to Server
--
Cannot connect to LT-E48643/mssql2k.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
For help, click:
http://go.microsoft.com/fwlink?Prod...53&LinkId=20476
BUTTONS:
OK
--Change the forward slash to a backward slash, and try again.
Linchi
"Keithb" wrote:

> I installed sql server 2000 on a box that already has sql server 2005
> installed. I used an instance name of "{machine name}/mssql2k" and I'
m
> trying to connect using {machine name}/mssql2k. When I open SQL Serve
r
> Management Studio and try to connect to the new instance, I get the messag
e
> shown below. Please let me know what I need to do to connect.
> Thanks,
> Keith
> TITLE: Connect to Server
> --
> Cannot connect to LT-E48643/mssql2k.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (Microsoft SQL Server, Error: 53)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...53&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>|||That did it.
Thanks,
Keith
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06-D67A8A1005E1@.microsoft.com...[vbcol=seagreen]
> Change the forward slash to a backward slash, and try again.
> Linchi
> "Keithb" wrote:
>

No comments:

Post a Comment