November 13, 2011 at 12:25 pm
We have a process where we have various remote SQL servers (not on our domain) accessing data on our local MSSQL 2000 server. we
have used the following query many times in the past with success....
select *
from OPENDATASOURCE(
'SQLOLEDB',
'Data Source=<ip address>;User ID=<username>;Password=<password>
).sales.dbo.stores
(obviously using correct IP and credentials)
Now if I go to a remote MSSQL 2000 or 2005 server, it
runs just fine. However, whenever we run it from MSSQL 2008 server I get the following error:
OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "Unable to complete login process
due to delay in opening server connection".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "(null)".
We know we're using the correct IP and credentials because we're able to cut and paste into 2 different
locations through RDP to test this and it works fine on the MSSQL 2005 server but not on MSSQL 2008 server.
Someone had said we need to install the MSSQL 2008 Native Client on the MSSQL 2000 server in order for the above to work. Does this sound accurate?
If so, this would be a production server so what are the risks? Are there any redflags or known issues with installing MSSQL 2008 Native Client on a MSSQL
2000 server? We are just concerned that it may take our production machine down but we wanted to research and confirm within forum first before attempting
this solution.
Any help, input or guidance would be greatly appreciated! Thanks!
November 15, 2011 at 9:09 am
Moderator - did I post this in the wrong forum? Should I have put this in the SQL Server 2008 Administration
forum? Just want to make sure it's in the right place to field responses.
November 15, 2011 at 9:29 am
SQL Server 2008 R2 Native Client supports the version of SQL Server in which it is released, and SQL Server 2000 SP4, SQL Server 2005, and SQL Server 2008.
November 15, 2011 at 9:45 am
Thanks Dev. So it *must* have SP4 installed before putting 2008 Native Client on it?
November 15, 2011 at 9:46 am
If it's an old box I'd check that version of Native Client supports the host OS.
Should be able to use an older version of NC if it is an issue.
November 15, 2011 at 9:51 am
mar311 (11/15/2011)
Thanks Dev. So it *must* have SP4 installed before putting 2008 Native Client on it?
Yes you should. And if you are planning for upgrade I would suggest for a big step (may be SS2K / SS2K8) 🙂
November 15, 2011 at 10:04 am
Thanks Gazareth. Host OS on the MSSQL 2000 server is Windows 2003 Standard Edition SP2. So I'm assuming I'm OK with the latest SQL 2008 NC install?
November 15, 2011 at 10:08 am
Yep looks like it: http://msdn.microsoft.com/en-us/library/cc280356.aspx
Got caught out by it myself a while ago by some Windows 2000 machines 🙂
November 15, 2011 at 10:30 am
Yeah basically same case as me. We need upgrade this server but in the interim need to get this up and working. Looks like I need to update SQL Server to SP4 as well since it's only on SP2 as of right now. So I'll be installing SP4 and then upon successful install of SP4 then going to install 2008 NC.
On this page: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b33d2c78-1059-4ce2-b80d-2343c099bcb4
I'll be using this file (highlighted in attached GIF) for the 2008 NC install. I am using the right file, correct?
November 16, 2011 at 2:09 pm
The install went fine without any hitches. But now we're trying to connect back to our MSSQL 2000 server with the query noted at the top of this thread and are continuing to this error msg:
OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "Unable to complete login process due to delay in opening server connection".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "(null)".
Any ideas as to what could be causing this? Any help would be appreciated!
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply