November 2, 2005 at 1:37 pm
Hi all,
I have 3 servers a,b,c. On server a I am trying to create a linked server in Enterprise Manager, which will link to server b. When I click on the tables I get this error:
"Error 17:SQL server does not exist or access denied"
I can connect to server b from the other machines but not server a so it shouldn't be the login name or wrong ip address or anthing. And I know that server "a" already has a linked server to server "c" so it means that it has the ability to connect to other servers. any ideas what could be the problem? Thanks
November 2, 2005 at 2:56 pm
Probably the method of logging in while making the connection: under the security tab for the linked server, how/who you're making the connection as.
Other possibility, the name is not understood. If you're not using the network name for server B, you'd need to make a SQL alias for it on server A (under client network utility).
Or maybe the SQL Server instance on computer (A) is not using a profile with network access.
November 2, 2005 at 3:20 pm
Thanks for your reply
As I said before I did the exact same thing on another machine with the same login and it works fine.
I do have an alias on Server "A" for server "B" in my network utility. And I'm sure the login name and password are fine.
The SQL server instance on computer "A" should be using a profile with network access because it connects to server "C" with no problem.
The one possibility I just realized could be that Server "B" is rejecting the server "A" 's IP address specifically. I just called the our webhost to see if they can figure out something and they are supposed to get back to me. But if anybody has anything in mind please let me know. Thanks
November 3, 2005 at 5:13 am
Can you run Query Analyser on server A to connect to B? Does it work?
If you can't run QA, try, on server A, using xp_cmdshell to run the OSQL utility connecting to server B with a simple select statement as the statement it will execute and quit. Does this work?
November 3, 2006 at 7:33 am
Hi, I realize this is an old thread. I just found the board today while searching for help with linked servers. Microsoft's documentation on this is lacking to say the least. John, your solution just ended 2 hours of hair pulling ("If you're not using the network name for server B, you'd need to make a SQL alias for it on server A"). I had deleted an old alias but I did not know an alias was required for a linked server (I thought linking the server would take care of that!). MS documentation never mentioned that.
It worked like a charm - thanks,
carl
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply