Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-06-10 : 09:23:35
|
| paul writes "In an attempt to solve another connectivity problem I applied SQL Sp4 to our SQLserver (NT4 SP 6a)& (no prior SQL Sp's applied)(Then reapplied nt sp6a) since doing so nither remote users or our web server can connect to the server (user name password validation error connecting as sa) the remote users and web servers are at MDAC level 2.5 Is this a known problem and is there a solution" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-06-10 : 09:49:38
|
| I imagine that it might be because of reapplying NT SP 6a after applying SQL 7.0 SP4. I looked through the SP4 installation guide and couldn't find anything that stated SP 6a must be installed after SP4, and I have a feeling that some obscure DLL or component got overwritten with a older version.If you can, try applying MDAC 2.6 or higher to the SQL Server, and the client machines too, if that's possible. In all likelihood that will fix the problem.If this doesn't work, please post the EXACT error message(s) you're getting when trying to connect. |
 |
|
|
bouno
Starting Member
23 Posts |
Posted - 2002-06-18 : 18:20:48
|
| I install sp4 on sql 7.0 with no errors in installation butthe server is not updated. with select @@version shows me the sp3 and not sp4. any thoughts what is wrong?I imagine that it might be because of reapplying NT SP 6a after applying SQL 7.0 SP4. I looked through the SP4 installation guide and couldn't find anything that stated SP 6a must be installed after SP4, and I have a feeling that some obscure DLL or component got overwritten with a older version.If you can, try applying MDAC 2.6 or higher to the SQL Server, and the client machines too, if that's possible. In all likelihood that will fix the problem.If this doesn't work, please post the EXACT error message(s) you're getting when trying to connect. [/quote] |
|
|
|
MakeYourDaddyProud
184 Posts |
Posted - 2002-06-18 : 20:02:19
|
| The problem is MDAC 2.5, it is simply not compatible with SP4. I have no end of probs with it. Either reverse engineer to SP3 or upgrade MDAC to 2.6. Period.The problem lies in the semaphores used in the connection pipe net DLLs in which you have no control.Danwww.danielsmall.com IT Factoring |
|
|
|
bouno
Starting Member
23 Posts |
Posted - 2002-06-18 : 20:32:29
|
| Dan, How can i proof that the server has the MDAC 2.5and to refress my memories, what is the URL to go to upgrade to MDAC 2.6Once again, i appreciate your time.thanks,bounoThe problem is MDAC 2.5, it is simply not compatible with SP4. I have no end of probs with it. Either reverse engineer to SP3 or upgrade MDAC to 2.6. Period.The problem lies in the semaphores used in the connection pipe net DLLs in which you have no control.Danwww.danielsmall.com IT Factoring [/quote] |
|
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2002-06-18 : 20:51:50
|
| You can download all the MDAC files at http://www.microsoft.com/data/MS also has a comcheck application which will analyze your MDAC configuration. Otherwise you'll have to go off of dll versions. |
|
|
|
MakeYourDaddyProud
184 Posts |
Posted - 2002-06-19 : 05:47:34
|
| I agree, comcheck can be a useful util to report on the clients odbc config. ;-) |
|
|
|
sf
Starting Member
3 Posts |
Posted - 2002-06-20 : 20:49:27
|
| Hello danny2sweet,smccreadie,can you explain how to get the comcheckand how to use it to get the result? thanks,sf |
|
|
|
|
|
|
|
|
connection problems to SQL7 Following Sp4