Linked server problem "Login timeout expired"

Hello All,

My application is dependent on two databases one is on sql 2005 machine and other is on sql 2000 machine. A linked server is establish between these two using sql account which has appropriate rights on both server's databases.

application works fine but after some time it crashes and if i see error from sql profiler i get the error

OLE DB provider "SQLNCLI" for linked server "sql2000machine" returned message "Login timeout expired".

Few days back applciation was working absolutly fine, but i was trying to make linked sever through windows account, i dnt know wat has i changed during achiveing that setup that now application (linked server) is not working even with sql account.

please help its urgent.

I am moving this thread to the Data Access forum. Hopefully someone from that forum will be able to help.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||What do you get if you do the following?
select * from sys.servers

linked server Login timeout expired error

Hello All,

My application is dependent on two databases one is on sql 2005 machine and other is on sql 2000 machine. A linked server is establish between these two using sql account which has appropriate rights on both server's databases.

application works fine but after some time it crashes and if i see error from sql profiler i get the error

OLE DB provider "SQLNCLI" for linked server "sql2000machine" returned message "Login timeout expired".

Few days back applciation was working absolutly fine, but i was trying to make linked sever through windows account, i dnt know wat has i changed during achiveing that setup that now application (linked server) is not working even with sql account.

please help its urgent.

Check network setting. Can you ping from sql2k5 to sql2k. Also, how is the linked server login setup? Is it "self" or the remote credential? Remember that domain authentication requires a domain controller. Network latency might be your enemy here.

sql

Linked Server Connectivity Error

BACKGROUND:

I have two databases that support two separate applications. Both applications are required to be in sync with one anther. One application is MSSQL 2000 based and the other is Oracle 9.i. Given the complexity of the first application (host), the best solution was to use linked servers to connect the SQL database to the Oracle database.

To prevent imbalances, the host application calls a package in Oracle to update the secondary application before it completes the transaction in SQL. This way, if anything fails at any point, the entire transaction is rolled back and neither databases are updated.

PROBLEM:

Our test system is stand alone but is performing the previously mentioned transaction in the same manner to an Oracle database on a Linux server. After passing testing, we promoted the application to the live system and are experiencing the following error when the transaction attempts to call the Oracle package:

Connectivity error: [Microsoft][ODBBC SQL Server Driver][SQL Server]MSDTC on server XXXXX is unavailable.

I have done some reading, but there really isn’t much literature on linked servers. Will someone help?

Thanks so much,

Tony

See if this link might be helpful for you:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=447602&SiteID=1

|||I checked MSDTC and it appears to be running just fine.

linked server

I have a programm that create linked server on start of application and delete it on finish.
I need to check if linked server already exist on my server.
How can i do it?system catalog: SYSSERVERS|||The easy way would be to check the return code from sp_addlinkedserver (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_adda_8gqa.asp).

-PatP|||Hi gorodd,

Assuming you have a server called "goroddServer"

if exists (select srvname from master.dbo.sysservers where srvname = goroddServer)
begin
print 'goroddServer already exists and is dropped'
exec sp_dropserver goroddServer
end

You may not want the print statement but I have it in for debugging purposes

Hope this helps

Richard