Hi,
I've got problem with configuring a linked server within SQL server 2005. I
am trying to connect to SQL 2000. The link from 2000 to my 2005 server has
worked fine. But not the other way. Also, the 2000 is linkable from other
2000 servers so seems to be specific to 2005 not a problem with the 200
sercer. My version is developer edition could that be the issue? didn't see
something speficic for that.
This is the error message
OLE DB provider "SQLNCLI" for linked server "svr30" returned message "Login
timeout expired".
OLE DB provider "SQLNCLI" for linked server "svr30" returned message "An
error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.".
Msg 5, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [5].
The other server is configured to allow remote connectins that's why other
2000 can see it.
I've tried different options on the link but none worked... This is what I
have at the moment...
/****** Object: LinkedServer [SVR30] Script Date: 05/30/2006 18:11:36
******/
EXEC master.dbo.sp_addlinkedserver @.server = N'SVR30', @.srvproduct=N'SVR30',
@.provider=N'SQLNCLI', @.datasrc=N'SVR30', @.catalog=N'lso'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'collation
compatible', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'data access',
@.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'dist',
@.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'pub',
@.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'rpc',
@.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'rpc out',
@.optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'sub',
@.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'connect
timeout', @.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'collation
name', @.optvalue=null
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'lazy schema
validation', @.optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'query timeout',
@.optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @.server=N'SVR30', @.optname=N'use remote
collation', @.optvalue=N'true'
Does anybody know if something is wrong? Thanks.
Panos.Maybe you want to check this link..
http://www.aspfaq.com/show.asp?id=2544|||Nah, nothing useful in the link. I've also tried to set-up the same linked
server on another sql server 2005 which I've installed on my PC. Linked
servers work fine on my local sql 2005. So there is either something
different on the network for that particular server or some setting is
different. I've checked both 2005 servers local and problematic and they see
m
to have the same settings. Any other ideas? Thanks.
Panos.
"Omnibuzz" wrote:
> Maybe you want to check this link..
> http://www.aspfaq.com/show.asp?id=2544
>|||Well...
Then it looks like a network issue.
Check this link.. A discussion on an issue very similar to what you face :)
http://forums.microsoft.com/MSDN/Sh...327775&SiteID=1
Let me know if you resolve it.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment