linked server: Error 17: SQL Server does not exist or access denied.

Question

I have two sql server 2000 with mixed mode authetication. 

I stand at one server and setup a linked server to the other using the same user id and password.
However when I click to the Tables icon of linked server in Enterprise manager, there is an error message:
Error 17 SQL Server does not exist or access denied.
And It does not show any table.
I register remote sql server in Enterprise manager fine.
Could any one help me ?
Thanks.

Answer 1

Hi,

What remote login did u used for linked servers.

The remote login should exists on both the server.

Regards

Mohd Sufian

Answer 2

S1 - local server
S2 - remote server

1. Ensure that the user account used has permissions to login to S2 directly and access desired table on S2.

2. Create linked server login mapping using sp_addlinkedsrvlogin on S1.
Try a simple select query on remote table using linked server name.

 

 

Answer 3

both S1 and S2 have the same user id and password.

I' ve created linked server login on S1. However when I run a select query on remote table using Query Analyzer, I get the same error message ERROR 17

Do you have any more suggesstion ?

Answer 4

Can you post the query that you executed on S1? Also, when you executed the query on S1, were you connected as the user that you set for the linked server connection?

Thanks
Laurentiu

Answer 5

Both servers 10.0.10.237 and 10.0.10.111 run Sql SERVER 2000 with mixed mode authentication user id: sa, password: vbsp

Linked server QLNSParent from 10.0.10.237 links to 10.0.10.111 with login mapping: local login: sa, remote user: sa, remote password: vbsp

At 10.0.10.237, I login Query Analyzer using user id sa, password: vbsp. Then I run the query:

select * from QLNSParent.qlns.dbo.hoso

It alway returns the error message:

Server: Msg 17, Level 16, State 1, Line 1
SQL Server does not exist or access denied.

At 10.0.10.237, I run Enterprise Manager and I can register 10.0.10.111 fine. This means thats I can connnect to 10.0.10.111 OK but not using linked server.

Do you have any suggestion ?

Thanks.

Answer 6

Can you post the output of the following commands on the 237 server?

exec sp_helpserver 'QLNSParent'
exec sp_helplinkedsrvlogin 'QLNSParent' 

Thanks
Laurentiu

Answer 7

the result of the first command:

name: QLNSParent, network_name: NULL, status: data access, use remote collation, ID: 1, connection_timeout: 0, query_timeout: 0

and the result of the second command:

Linked server: QLNSParent, local login: sa, Self mapping: 0, Remote login: sa

I think those results are ok but there is one problem of OS level security and I can't find exactly the cause.

can you help me ?

Answer 8

Dear ,

 

Do u have a named instance on sqlserver2005.

from

sufian

Answer 9

Both server run windows server 2003 enterprise edition.

In each server, we have a named instance of Sql server 2000.

 

Answer 10

Dear,

 

Connect by give the servername with instance.

ex: svt_test(server name\sql_2000(instance name)

from

sufian

Answer 11

I think the way you set up your linked server was incorrect. What was the sp_addlinkedserver command that you used?

Thanks
Laurentiu

Answer 12

sp_addlinkedserver @server = N'QLNSParent',
 @srvproduct = N' ',
 @provider = N'SQLOLEDB',
 @datasrc = N'10.0.10.111',
 @catalog = N'qlns',
 @provstr = N''
GO
sp_addlinkedsrvlogin  @rmtsrvname =  'QLNSParent',
   @useself = false,
   @locallogin = 'sa', 
   @rmtuser = 'sa',
   @rmtpassword = 'vbsp'

GO

do you have any more suggesstion ?

Answer 13

Is your SQLServer installation named QLNSParent? Can you connect to it using QA and the QLNSParent name?

If the name is ok, have you tried simply specifying:

sp_addlinkedserver N'QLNSParent', N'SQL Server'

Thanks
Laurentiu