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 |
|
dhw
Constraint Violating Yak Guru
332 Posts |
 Posted - 2003-02-01 : 18:15:17
|
| Hello..We're running SQL2000 on our server and MSDE on the clients. We applied SP3 to SQL2000 and it worked perfectly. However, when I applied the latest MSDE SP3 it appears to have gone through the process...no errors or warning...but when I check the version afterwards with SELECT @@VERSION I still get the following: Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)I have tried this several times already and the version doesn't change. I looked through the Readme and can't find anything that describes this situation. Has anyone else experienced this problem? thanks,dhw |
|
|
samrat
Yak Posting Veteran
94 Posts |
Posted - 2003-02-03 : 21:57:54
|
| Greetings,I am having the same issue... any experienced gurus who can share soem insight on the problem ???Regards,Samrat |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-04 : 11:29:45
|
| Is it possible that you have multiple instances installed? If so, you need to patch all instances. |
|
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2003-02-05 : 17:36:29
|
| Yes...we do have a specific Instance Name configured...but I had been using the various command line arguments to specify the InstanceName. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-05 : 18:28:37
|
| Do both instances or all instances give the same version number? You will have to do SELECT @@VERSION on all instances. |
|
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2003-02-05 : 18:54:23
|
| Actually, they do not show the same version number. On my dev machine I have two instances...a default one (installed when I setup visual studio .net) and a named instance. This is something I noticed before...and, in fact, I tried to apply the SP to both the default and then the Named instance....and neither one's version info is changed at all. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-05 : 19:06:03
|
| Have you tried running the SSCHECK.exe utility that MS has issued to test whether or not the server is vulnerable? Maybe @@VERSION isn't correctly displaying the version number. Hopefully, SSCHECK.exe will give you the information that you need.Download the utility from:[url]http://microsoft.com/downloads/details.aspx?FamilyId=9552D43B-04EB-4AF9-9E24-6CDE4D933600&displaylang=en[/url]You will want to download SQLCheckPkg.exe.If the utility says that you are vulnerable, I would reinstall the service pack. Run the installation from the server. If it still isn't the correct version, then you are going to need to contact MS. |
|
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2003-02-06 : 11:25:12
|
| First, thanks for all of the help and advice!I ran the various sql scan/check utilities...and the msde instances were vulnerable. I ran the hotfix/critical update and then re-ran the utils and I am no longer vulnerable to worms. The version and SP levels still show the same old info.I also got some help from MS support (via one of their newsgroups) and it might be an issue with the way that msde was installed. We created a setup via Visual Studio .net and it may be that we cannot simply apply the SP to these types of msde installs. Rather, we will have to update our Setup to include the SP3..... |
|
|
|
|
|
|
|
|
SP3 not upgrading MSDE