Solved

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

Posted on 2009-05-20
9
692 Views
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".
0
Comment
Question by:kikimayhay
  • 4
  • 4
9 Comments
 
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:
http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx
0
 

Author Comment

by:kikimayhay
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).
0
 
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.
0
The New “Normal” in Modern Enterprise Operations

DevOps for the modern enterprise offers many benefits — increased agility, productivity, and more, but digital transformation isn’t easy, especially if you’re not addressing the right issues. Register for the webinar to dive into the “new normal” for enterprise modern ops.

 

Author Comment

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

Assisted Solution

by:Raja Jegan R
Raja Jegan R earned 500 total points
ID: 24433008
0
 

Author Comment

by:kikimayhay
ID: 24433259
Update
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".
0
 
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.

http://kbase.gfi.com/showarticle.asp?id=KBID002804

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

http://support.microsoft.com/kb/839279

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.
0
 
LVL 75

Expert Comment

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

Accepted Solution

by:
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.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
sql server concatenate fields 10 38
string fuctions 4 28
Update one table with results from another table in SQL 6 23
SSRS: Why is Visual Studio stripping these properties? 2 21
Introduction Hopefully the following mnemonic and, ultimately, the acronym it represents is common place to all those reading: Please Excuse My Dear Aunt Sally (PEMDAS). Briefly, though, PEMDAS is used to signify the order of operations (http://en.…
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

840 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