Login timeout expired when updating tables from sql 2005 to sql 2000

Posted on 2009-05-20
Medium Priority
Last Modified: 2012-05-07
We moved our database from SQL 7 (32 bit) to SQL 2005 (64 bit) our latest issue is we receive a login time out expired anytime we run the VBA script that is updating the tables between two databases.  What used to happen is the SQL 7 database would update a table in a SQL 2000 (32 bit) database now we are trying to do the same except we are going from a SQL 2005 database updating the same SQL 2000 database.

Exact error message:
Run-time error '-214217900 (80040e14):

OLE DB provider "SQLNCLI" for linked server "Server_Name" returned message "Login timeout expired".
Question by:kikimayhay
  • 4
  • 4
LVL 57

Expert Comment

by:Raja Jegan R
ID: 24432700
You obtained this error because OBDC connection was attempted to sql 2000 when 2005 server is not ready to process a new local connection, possibly due to overload:  

More info below:

Author Comment

ID: 24432833
That would seem extremely unlikely. Our Sql Server 2005 database is sitting alone on a 4 processor 6 cores server with 16 gb ram (yeah it's overkill). Not to mention the updating process has not worked sonce we moved to the new server.  That would mean it is always overloaded. I am not dismissing it just seems unlikely or my understanding is way off (not impossible either).
LVL 57

Expert Comment

by:Raja Jegan R
ID: 24432877
Typed wrongly earlier, It was

You obtained this error because OBDC connection was attempted to sql 2005 when 2000 server is not ready to process a new local connection, possibly due to overload

Since you try to update SQL Server 2000, connection will be established from 2005 to 2000 server.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.


Author Comment

ID: 24432947
That also does not seem correct as this issue never popped up before we moved to sql 2005.
LVL 57

Assisted Solution

by:Raja Jegan R
Raja Jegan R earned 2000 total points
ID: 24433008

Author Comment

ID: 24433259
I tried to just perform a simple lookup from our sql 2005 database to the sql 2000 (
select * from remote_server_name.database_name.dbo.table_name)
and received the following errors

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

OLE DB provider "SQLNCLI" for linked server "server_name" 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 53, Level 16, State 1, Line 0

Named Pipes Provider: Could not open a connection to SQL Server [53].

OLE DB provider "SQLNCLI" for linked server "server_name" returned message "Invalid connection string attribute".
LVL 57

Expert Comment

by:Raja Jegan R
ID: 24433596
Check for the following:

1. In Surface Area Configuration of SQL Server 2005, check whether Remote connections using Both TCP / IP and Named Pipes are enabled.

2. In SQL Server Configuration Manager, Check whether TCP / IP Dynamic Ports are set to Blank and TCP / IP Ports are assigned to default port 1433 or something else.

3. Check whether Mixed mode Authentication are enabled in SQL Server 2005.


4. Firewall is disabled in that SQL Server 2005 machine.
5. MSDTC is configured as mentioned in


6. There was some hotfix required for SQL Server 2005 for Linked server to function properly. Hence a minimum of SP2 or SP3 will help to fix that bug in 2005.

Hope this helps.
LVL 75

Expert Comment

by:Anthony Perkins
ID: 24434468
After you moved all the data, did you update statistics?

Accepted Solution

kikimayhay earned 0 total points
ID: 24436596
We called Microsoft. To correct issue we first deleted the linked database found in SSMS --> Server Objects --> Linked Servers instead of doing it via direct hard coded sql (the method apparently preferred by sql guru's that blog). We then created a new linked server using the ssms console (right click on "linked server" from above select new)
We also had to run the sql code from article : http://support.microsoft.com/kb/906954
after that no more issues.

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article describes how to use the timestamp of existing data in a database to allow Tableau to calculate the prior work day instead of relying on case statements or if statements to calculate the days of the week.
In this article, we will see two different methods to recover deleted data. The first option will be using the transaction log to identify the operation and restore it in a specified section of the transaction log. The second option is simpler and c…
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

600 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question