|
Home > Archive > MS SQL Server > October 2006 > Can't connect to new sql server instance
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Can't connect to new sql server instance
|
|
| Keithb 2006-10-24, 6:37 pm |
| 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? Pro...53&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
| |
| Linchi Shea 2006-10-24, 6:37 pm |
| 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 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? Pro...53&LinkId=20476
>
> ------------------------------
> BUTTONS:
>
> OK
> ------------------------------
>
>
>
| |
| Keithb 2006-10-24, 6:37 pm |
| That did it.
Thanks,
Keith
"Linchi Shea" < LinchiShea@discussio
ns.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06- D67A8A1005E1@microso
ft.com...[color=darkred]
> Change the forward slash to a backward slash, and try again.
>
> Linchi
>
> "Keithb" wrote:
>
|
|
|
|
|