Named Pipes Provider: Could not open a connection to SQL Server [5]. -
08-25-2009
, 04:04 PM
Hi Everybody,
I don't expect any definitive answers, but was hoping to get some
advice on what to check or try next.
From linkedserver01, the following query works fine:
select * from db1.dbo.vwAllDatabasesClients
But From linkedserver02, the following query always returns the error
"Named Pipes Provider: Could not open a connection to SQL Server [5]":
select * from linkedserver01.db1.dbo.vwAllDatabasesClients
From linkedserver02, I can query any of the following databases/tables
and get the expected results:
select * from linkedserver01.master.dbo.sysobjects
select * from linkedserver01.db1.dbo.UserTable
select * from linkedserver01.db2.dbo.TableXYZ
I am a local administrator on both linkedserver01 and linkedserver02.
"net helpmsg 5" returns "Access is denied." From linkedserver02,
within "Server Objects," I can see the linked server
"linkedserver01." Expanding it, I can see all the tables and views,
including vwAllDatabaseClients. It seems I'm only locked out of this
one object when querying through a linked server. The linked server
is using the SQL Native Client Provider, and login is to "be made
using the login's current security context."
I believe that, because of the above queries that do work correctly, I
don't need to waste time with checking network/firewall issues. I
already know I can ping linkedserver01 from linkedserver02, and I've
validated that port 1433 is open on linkedserver01 from linkedserver02
(altlhough I don't recall the command I used).
Any suggestions? I've beat the permissions to a pulp in an effort to
allow my query to succeed, but to no avail.
Thanks,
Eric |