Re: Installing SS 2000 Breaks Connections for SS 2005 ?
- From: "George" <george_hepworth@xxxxxxxxxxx>
- Date: Mon, 5 May 2008 22:54:44 -0700
Thanks for the feedback. I'm not sure that is what is happening, but I will follow up.
I should have been more clear about the total environment.
I have two machines: a laptop and a desktop. I previously had SS 2005 installed on both of them. The SQL Native Client Driver syntax worked from both with no issues.
Yesterday, I had to add SS 2000 to the laptop to do some work for a client who required that version.
The Access FE from which I am connecting to the server is located on the laptop. The SQL Server to which I am connecting is on the desktop. It is indeed referencing the "default", and only instance, on that machine.
Another point I should have made is that I installed the SS2000 as a named instance on the laptop.
I have no problem connecting to any of the three instances from either the laptop or the desktop. From the desktop instance, the SQL Native Client Driver continues to work exactly as before in connecting to either of the two SS2005 instances.
It is ONLY the connection string from the laptop to the desktop using the SQL Native Client Driver which is no longer connecting. Actually, the error message indicates its timing out trying to connect. Moreover, using the SQLOLEDB provider does connect from the laptop to the desktop, as previously mentioned, so I know the connection is possible.
I am less confident that it has anything to do with ports being exposed or blocked, unless installing SS 2000 did so during the install, which is NOT something I would have expected, or thought to look into yet. Is that a common occurrence? If so, I'll add it to the list of lessons learned.
Finally, I appreciate the link to your blog. I'll take a look.
George
"William Vaughn [MVP]" <billvaNoSPAM@xxxxxxxxx> wrote in message news:2FF223B3-69B8-4F08-B03D-882F161B7EF1@xxxxxxxxxxxxxxxx
In your original connection string you did not specify the instance name. By not indicating the instance, the system assumes you're referencing the "default" instance. I expect the new install might have taken over the default instance. OR the new install changes how the ports are blocked/exposed so you'll need to tinker with the firewall.
See my whitepaper on connecting on my blog. www.betav.com/blog/billva
or Chapter 9 in my book.
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"George" <george_hepworth@xxxxxxxxxxx> wrote in message news:F1CB3225-6109-4010-B60B-8F068A213EBB@xxxxxxxxxxxxxxxxI recently had to install SS 2000 on a laptop which already had SS 2005 installed on it. I have a second machine, which has only SS 2005 installed on it.
The server to which I am trying to connect is located on the second machine, which has only SS2 005 installed on it.
The following connection, which worked when I had only SS 2005 on both machines, now doesn't work at all on the laptop. (It still works on the other machine as always.)
This is part of a procedure in an Access database to open an ADO recordset.
strCnxn = "Driver={SQL Native Client};" & _
"Server=NEWSERVER;" & _
"Database=TEST;" & _
"UserID=MYID;" & _
"PWD=MYPASSWORD"
I had to go back to the SQLOLEDB provider to connect :
strCnxn = "Provider=SQLOLEDB;" & _
"DATA SOURCE=NEWSERVER;" & _
"Database=TEST;" & _
"UID=MYID;" & _
"PWD=MYPASSWORD"
The specific error message returned is "(Microsoft) (SQL Native CLient) unable to complete login process due to delay in opening server connection."
Everything else seems to be working okay, and I can live with it, if I have to, but I'm wondering what, if anything, I can do here. I really would rather not have to take a step backwards, but more importantly, I'm wondering if something else is going to break.
MSDN Suggests that it is not necessary to use the Driver={SQL Native Client} unless you want access to functionality in 2005 that wasn't available earlier.
"If you do not need to use any of the new features of SQL Server 2005, there is no need to use the SQL Native Client OLE DB provider; you can continue using your current data access provider, which is typically SQLOLEDB."
Nonetheless, I would like to know if something else is going to break too.
Thanks.
George
.
- References:
- Installing SS 2000 Breaks Connections for SS 2005 ?
- From: George
- Re: Installing SS 2000 Breaks Connections for SS 2005 ?
- From: William Vaughn [MVP]
- Installing SS 2000 Breaks Connections for SS 2005 ?
- Prev by Date: Re: Installing SS 2000 Breaks Connections for SS 2005 ?
- Next by Date: Re: HELP!! SSMSE and Windows VISTA
- Previous by thread: Re: Installing SS 2000 Breaks Connections for SS 2005 ?
- Index(es):
Relevant Pages
|
