Error 62 When connecting with SSMS to a SQL Server 2000 named instance

Hello,

I get error 62 when trying to connect to a SQL Server 2000 named instance from SQL Server Management Studio. I can register and connect to other SQL Server 2000 instances

I've tried all the usual stuff, including enabling all the protocols from SQL Server configuration Manager.

Any thoughts. Your help is very appreciated.

Thanks

Kevin Lobo

Can you post the whole error msg? Is this a local or remote connection? What's the Service Pack of your SQL Server 2000? Make sure sql browser is on if you can. Also make sure sql browser and/or udp port 1434 is in exception list if you firewall is on.

Thanks,
Xinwei

So, actually error 26, not 62.

|||

Hello Xinwei,

Thanks. It is working now. The Browser was running but the firewall setting was on with 'Don't allow exceptions' checked. I unchecked it and its ok now.

many thanks.

Jut FYI, here is the entire error message:

An error has occured while establishing a connection to the server. When connecting to SQL Server
2005, the failure may be casued by the fact that under the default settings SQL Server does not
allow remote connections. (provider: SQL Network Interfaces, error 26 - Error locating Server/Instance
Specified) (Microsoft SQL Server)

error 4064 help me please

TITLE: Microsoft SQL Server Management Studio

No se puede abrir la base de datos predeterminada del usuario. Error de inicio de sesión.
Error de inicio de sesión del usuario 'HOME\jortega'. (Microsoft SQL Server, Error: 4064)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=4064&LinkId=20476

BUTTONS:

OK

Hi,

this is a english newsgroups, could you please translate the mentioned error message to an english equivalent ? That would make things easier for us (or even for me) :-)

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Have a look at the following thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=451657&SiteID=1

Thanks
Laurentiu

Error 40: could not open a connection to Mssql server

Hi,

I'm using sql server 2005 express edition. I have created a database using sql server management studio express edition. Now I'm trying to connect it in visual studio 2005. It show following error.

An error has occurred while establishing a connection to the server. When connections to SQL 5erver 2005, this failure may be caused by the fact under the server's default settings SQL Server does not allow remote connections, (provider: Named Pipes Provider, error: 40- Could not open a connection to SQL Server)

I have enables named pipes from Sql services configuration manager.

Hi,

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Is just a basic connectivity error meaning the client could not connect to the target SQL Server. So just follow the basic connectivity troubleshooting guidelines on our SQL Protocols blog, see:

SQL Server 2005 Connectivity Issue Troubleshoot - Part I

http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

and

SQL Server 2005 Connectivity Issue Troubleshoot - Part II

http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx

This should help you debug the problem.

Error 3154: The backup set holds a backup of a database other than the existing 'xx' database.

HELP!

This is happening with a restore to SS 2005 from a SS2000 backup. This article says to use the 'WITH REPLACE' clause. The SS2005 management studio does not seem to allow this via the GUI.

http://msdn2.microsoft.com/en-us/library/aa238217(sql.80).aspx

Did you use the overwrite flag in the GUI if the database already existed ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||True and you can use the Query Editior to restore the same using RESTORE DATABASE .... WITH REPLACE, as referred in BOL it is easy.|||asdaf sa gs ga sgasg asg g a

Error 3154: The backup set holds a backup of a database other than the existing 'xx' datab

HELP!

This is happening with a restore to SS 2005 from a SS2000 backup. This article says to use the 'WITH REPLACE' clause. The SS2005 management studio does not seem to allow this via the GUI.

http://msdn2.microsoft.com/en-us/library/aa238217(sql.80).aspx

Did you use the overwrite flag in the GUI if the database already existed ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||True and you can use the Query Editior to restore the same using RESTORE DATABASE .... WITH REPLACE, as referred in BOL it is easy.

Error 208 Event ID 17052

Here is a weird one:
Using EM 2000 to connect to a 7.0 SQL Server. As soon as
I click on Management, I receive an error in my SQL Log
and Event Viewer for Error 208, Event ID 17052 stating
Invalid Object Name 'msdb.dbo.log_shipping_provider'
I do not have log shipping configured on any of my
servers. Has anyone ran into this'
Thanks!Here is some more interesting info:
This only happens when using EM 2000, if I use the 7.0 EM
it does not cause the error. Anyone connecting with EM
2000 can make the error occur. Any thoughts'
>--Original Message--
>Here is a weird one:
>Using EM 2000 to connect to a 7.0 SQL Server. As soon as
>I click on Management, I receive an error in my SQL Log
>and Event Viewer for Error 208, Event ID 17052 stating
>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>I do not have log shipping configured on any of my
>servers. Has anyone ran into this'
>Thanks!
>.
>|||Hi,
This error is generally caused if the object ownership is
not properly referenced when accessing that object. You
have to use the fully qualified name i.e
dbname.ObjectOwner.ObjectName.
It seems to me that the owner of
the 'log_shipping_provider' table in the msdb is NOT dbo.
You might want to take a look the ownership of this table.
Also, it is possible that the user connecting SQL Server 7
EM is connecting with the ID that owns that table!
Suppose the above table is owned id 'test'. You could be
trying to connected with 'sa' and the connection will
fail. But if you connect with 'test', it will work fine.
Take a look. hth
DeeJay
>--Original Message--
>Here is some more interesting info:
>This only happens when using EM 2000, if I use the 7.0 EM
>it does not cause the error. Anyone connecting with EM
>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>.
>|||The log shipping tables do not exist in 7.0
So ownership wasn't the prob.
>--Original Message--
>Hi,
>This error is generally caused if the object ownership is
>not properly referenced when accessing that object. You
>have to use the fully qualified name i.e
>dbname.ObjectOwner.ObjectName.
>It seems to me that the owner of
>the 'log_shipping_provider' table in the msdb is NOT dbo.
>You might want to take a look the ownership of this table.
>Also, it is possible that the user connecting SQL Server
7
>EM is connecting with the ID that owns that table!
>Suppose the above table is owned id 'test'. You could be
>trying to connected with 'sa' and the connection will
>fail. But if you connect with 'test', it will work fine.
>Take a look. hth
>DeeJay
>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>.
>|||Silly me ... I knew that!
Are you connecting through just the client Tools (from
your workstation) or from a machine where SQL Server
2000/7 is installed?
Eventhough, log shipping is not configured, this table
could still, somehow, exist. You might want to take look
at the msdb database.
I have not found anything else for this error.
hth
DeeJay
>--Original Message--
>The log shipping tables do not exist in 7.0
>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
dbo.
>>You might want to take a look the ownership of this
table.
>>Also, it is possible that the user connecting SQL Server
>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>>as
>>I click on Management, I receive an error in my SQL
Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>.
>|||I'm just connecting through the client tools. I've
checked msdb and haven't found anything that remotely
looks like the log shipping tables.
This is weird!
>--Original Message--
>Silly me ... I knew that!
>Are you connecting through just the client Tools (from
>your workstation) or from a machine where SQL Server
>2000/7 is installed?
>Eventhough, log shipping is not configured, this table
>could still, somehow, exist. You might want to take look
>at the msdb database.
>I have not found anything else for this error.
>hth
>DeeJay
>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>dbo.
>>You might want to take a look the ownership of this
>table.
>>Also, it is possible that the user connecting SQL
Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>>EM
>>it does not cause the error. Anyone connecting with
EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
soon
>>as
>>I click on Management, I receive an error in my SQL
>Log
>>and Event Viewer for Error 208, Event ID 17052
stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>.
>|||Hum...this one got me.
The only documentation for error 208 is for what we have
already talked about
>--Original Message--
>I'm just connecting through the client tools. I've
>checked msdb and haven't found anything that remotely
>looks like the log shipping tables.
>This is weird!
>>--Original Message--
>>Silly me ... I knew that!
>>Are you connecting through just the client Tools (from
>>your workstation) or from a machine where SQL Server
>>2000/7 is installed?
>>Eventhough, log shipping is not configured, this table
>>could still, somehow, exist. You might want to take look
>>at the msdb database.
>>I have not found anything else for this error.
>>hth
>>DeeJay
>>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>>is
>>not properly referenced when accessing that object.
You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>>dbo.
>>You might want to take a look the ownership of this
>>table.
>>Also, it is possible that the user connecting SQL
>Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
>be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work
fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the
7.0
>>EM
>>it does not cause the error. Anyone connecting with
>EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
>soon
>>as
>>I click on Management, I receive an error in my SQL
>>Log
>>and Event Viewer for Error 208, Event ID 17052
>stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>>.
>.
>