Hello. I can't access a linked server from a workstation using Enterprise Manager.
I have a SQL2008 server and a SQL2000 server. I have set the SQL2000 to be a linked server on the SQL2008 box and from the server console (Logged in as domain\administrator) I can access the SQL2000 tables and query against them just fine. However, when I go to a workstation (also logged in as domain\administrator) that has the SQL2008 Enterprise Manager installed, I cannot access or query against the SQL2000 tables. The local SQL2008 Enterprise Manager can view tables on the SQL2008 server just fine.
The error message when I use the "test connection" option on the linked SQL2000 server inside the local copy of Enterprise Manager is nice and vague. It says that the login timeout has been exceeded and that perhaps the server is not configured for remote connections. I'm pretty sure the server is though.
Any thoughts?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yes, workstation is part of the domain. Workstation can ping both SQL servers by name and IP.
I ran cliconfg on the workstation and NONE of the protocols were enabled. I though "great, that must be it" and enabled both TCP/IP and Named Pipes. No luck. Took off Named Pipes - still no luck. Strangely enough, the workstation Enterprise Manager was able to see the SQL2008 databases no matter what the cliconfg settings were.
hmm.. no firewall on server or workstation. Corporate firewall is not restricting any internal LAN traffic. How do I see if its listening on a non-standard port?
Also, on the 2008 server (where I AM able to access the SQL2000 tables and query against them using Enterprise Manager) I cannot telnet to the 2000 box either.
here you go:
/****** Object: LinkedServer [SQLSERVER] Script Date: 12/17/2008 11:25:52 ******/
EXEC master.dbo.sp_addlinkedser
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrv
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
EXEC master.dbo.sp_serveroption
GO
I'm assuming this "@server=N'SQLSERVER'" has been changed to protect the guilty?
Just for grins either run the SSMS with Run As (Right-click icon --> Run As ... yada...)
or the other is to
from a command line:
X:\Program Files\Microsoft SQL Server\90\Tools\Binn
Sqlcmd -S ServerName -E -d DBName -q
and then run some simple query. You need to use GO as the separator.
Workstation SSMS =
Microsoft SQL Server Management Studio 10.0.1600.22 ((SQL_PreRelease).080709-1
Microsoft Analysis Services Client Tools 2007.0100.1600.022 ((SQL_PreRelease).080709-1
Microsoft Data Access Components (MDAC) 2000.085.1132.00 (xpsp.080413-0852)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.13
Microsoft .NET Framework 2.0.50727.3053
Operating System 5.1.2600
SQL2000 box is on SP4 OS is WindowsServer2003 SP1
I'm hesitant to relink from the workstation in case that blows up the link that is working on the server.
Can you try creating a new linked server using the Other Data Source and the Microsoft OLE DB Provider for SQL Server?
Check this out:
http://forums.microsoft.co
tried. Same error. :(
TITLE: Microsoft SQL Server Management Studio
--------------------------
The test connection to the linked server failed.
--------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Conne
--------------------------
Named Pipes Provider: Could not open a connection to SQL Server [5].
OLE DB provider "SQLNCLI10" for linked server "SQLSERVER" returned message "Login timeout expired".
OLE DB provider "SQLNCLI10" for linked server "SQLSERVER" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". (Microsoft SQL Server, Error: 5)
Interesting. Did you see that "Named Pipes Provider" message? Whenever I should find any Named Pipe enabled SQL Server, first thing I do is DISABLE PIPES. They cause a lot of trouble, are unreliable aso.
I would give that a try: Disable Named Pipes in the MSSQL2005 Server's Client network connection settings. Do the same on your client (should not be needed, but ...). And you should also do the same in the MSSQL Server network connection on both server machines.
Meanwhile I can add another strange issue: With disabled Named Pipes on server and client, the client is keen to use Named Pipes in some situations (have connect/disconnect e.g.). With disabled Named Pipes, connection issues arise! My "solution" (rather a workaround) was to re-enable Named Pipes, and make sure name resolution works, as Named Pipes do not work with IP addresses (in almost all cases).
Business Accounts
Answer for Membership
by: jimpenPosted on 2008-12-17 at 07:52:51ID: 23194411
Make sure the workstation is part of the domain.
Assuming the workstation doesn't have a firewall up:
From the workstation: Ping the SQL 2K by server name
----------------------
PING MyServer
----------------------
if that doesn't work ping by IP. If it works by IP then it is a DNS issue or a Named Pipes issue.
On the workstation disable Named Pipes
(Start > Run > Type "cliconfg" > Click "OK")
Details: http://www.sepialine.com/k
If that works then disable named pipes on the SQL 2000 server.