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 |
|
drumm
Starting Member
14 Posts |
Posted - 2003-01-31 : 06:12:36
|
| Hi,I have two identical server setups. Both run an SQL Server 2000 with SP2 and are patched to build 679 (a roll-up patch release by Microsoft).However, I can install SP3 with no problems on one of them, but the other fails to validate the password. I can use the exact same password to login as SA in a Query Analyzer.I've checked for SQL Slammer (the 679 patches should block that exploit possibility), and I've even tried to restart the server, but without any luck.Anyone tried the same?Thanks in advance,Thomas |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-01-31 : 15:29:01
|
| Here's some info from MS on this issueSOLUTION: Validating a user error during SP3 upgradeProblem Description:Several of you have encountered problems running the Service Pack 3 setupwhere setup fails very early on while "validating a user". This problem canoccur when MDAC version 2.6 or earlier is present on the machine at the timeof upgrade. Those who received later versions of the server network librarycomponents of MDAC through a later upgrade (MDAC 2.7 as part of Windows XPPro for example) will not encounter this problem.Resolution/workaround:As Jeff Boyd noted elsewhere in the newsgroups, you can change the "DSQuery"entry in the registry as a temporary workaround. The keyHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo\DSQueryvalue to "DBNETLIB".We will get some type of official KB article out in the near future. For now, I hope this helps those of you encountering this issue.HTHJasper Smith |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-01-31 : 17:37:39
|
| Hmmm hadn't read about that one yet. Glad to know there is a workaround already. |
 |
|
|
drumm
Starting Member
14 Posts |
Posted - 2003-02-01 : 12:15:01
|
| Installed the MDAC 2.7 RTM (which, if I'm not mistaken, the SP3 actually installs as part of the update) as suggested, and suddenly, the update worked like a charm.Where did you find that Microsoft information? I've been all over the internet, but couldn't find anything.Thanks! |
 |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-02-02 : 09:23:07
|
| Actually SP3 installs MDAC 2.7 Service Pack 1 but the issue with validating user for upgrade is due to having MDAC 2.6 or earlier so 2.7 RTM will prevent this problem and be upgraded to MDAC 2.7 Service Pack 1 during the service pack install.[url]http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&selm=OtutXPyxCHA.2372%40TK2MSFTNGP12[/url]Some common problems that have solutions have been posted to the microsoft.public.sqlserver.* newsgroups. A good way to find them whilst waiting for the KB articles to be finished and posted is to search google groups[url]http://groups.google.com/groups?as_q=SP3%20SOLUTION&safe=off&ie=UTF-8&oe=UTF-8&as_ugroup=microsoft.public.sqlserver.*&lr=&num=20&hl=en[/url]HTHJasper SmithEdited by - jasper_smith on 02/02/2003 09:27:09 |
 |
|
|
JamesH
Posting Yak Master
149 Posts |
Posted - 2003-02-03 : 15:03:26
|
| Ran into the same problem on 2 of 36 Servers. Rebooted and logged in again and it took it with no problem, but I believe that was because the MDAC was installed prior to the password. On the same note, has anone seen any problems with the installation scripts failing on any servers. I noticed that on 2 out of 36 I was getting an error on some of the scripts including 'replcom.sql'. I reran all of the scripts manually and everything appeared to work except for a library call that was failing. Anyone?? The SP would fail in the same spot everytime almost like it was a versioning problem between Standard and Enterprise edition. You know, like a particular .DLL was left out becuase of the SQL Version.Thanks,JamesH. |
 |
|
|
|
|
|
|
|