SQL Server 2000 SP3 + Patches - SQL Server Forums

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.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

SQL Server 2000 SP3 + Patches

Author

Topic

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2004-03-04 : 16:32:02

Hi,
I would like to know if the following security patches came after SP3(A) or SP3??
815495 MS03-031: Cumulative Security Patch for SQL
821277 MS03-031:Security Patch for SQL Server 2000 Service Pack 3.
+
how do I know if I have already applied these or not?

This is a suggested resolution for the following error:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 53, ECID 1, UMS Context 0x04069D90
on this link [url][/url]http://support.microsoft.com/default.aspx?scid=kb;en-us;810885

Thanks,
Sarat

**To be intoxicated is to feel sophisticated, but not be able to say it.**

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-03-04 : 16:38:26

Verification
To determine what version of SQL Server you are running, use the information that is in the following Microsoft Knowledge Base article:
321185 HOW TO: Identify Your SQL Server Service Pack Version and Edition

After you apply this security patch, when you run
SELECT serverproperty('productversion')
-or-SELECT @@Version

the following should be returned:

8.00.0818

That's what Q821277 says at least.

Tara

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2004-03-04 : 16:48:32

Thank so much Tara!! We are behind! our version is 8.00.760. I am hoping it will resolve the 17883 error.

**To be intoxicated is to feel sophisticated, but not be able to say it.**

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2004-03-04 : 16:59:25

Tara,
Did you apply these after applying SP3(a)?
Thanks,
Sarat.

**To be intoxicated is to feel sophisticated, but not be able to say it.**

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-03-04 : 17:03:34

I didn't even know there was a security patch for sp3(a).

Tara

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2004-03-04 : 17:06:59

The MS03-031 patch can only be applied to SQL2K that has SP3 or SP3a already installed.

-ec

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-03-04 : 17:14:02

Right and both of us do. I usually get notified about security patches through our MS rep, I wonder how I missed this one.

Tara

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2004-03-04 : 23:31:38

quote:
Originally posted by tduggan

Right and both of us do. I usually get notified about security patches through our MS rep, I wonder how I missed this one.

Tara

you didn't!

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=27944&SearchTerms=ms03-031

-ec

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2004-03-05 : 11:13:34

But this patch still needs to go after SP3/SP3A, right? Tara, why would it be a problem?
-Sarat

**To be intoxicated is to feel sophisticated, but not be able to say it.**

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2004-03-05 : 12:31:06

the 815495 note applies to SQL2K and SQL7 including MSDE. 815495 is more of an overview, it has links to the specific patches (821277 for SQL2K and 821279 for SQL7)

-ec

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-03-05 : 15:58:05

Damn, I can't believe that I was the one to post it. Too much alcohol, not enough brain cells.

Sarat, yes it needs to be applied after sp3 or sp3a.

Tara

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2004-03-18 : 16:08:05

Tara,
I was the intoxicated one!! Anyway, did you apply this hotfix yet? I did it in Dev env and it looks okay to me. Any findings?
Thanks,
Sarat.

**To be intoxicated is to feel sophisticated, but not be able to say it.**

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-03-18 : 16:31:29

I haven't. I've been tasked with it though. I'll be doing it in our test environment first. I had to wait to see if the hotfix was certified for installation on Windows Data Center, since we have a SQL Server in production on that OS. It is certified, so I'll start working on it next week.

Tara

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2004-03-22 : 16:04:01

Hi,
It seemed like the hotfix application went well at the front end. There haven't been any issues in the database. I did go back and check the error log to see what it says when we apply the hotfix. Here is most of it. Why is the configuration option changing so many times? Do I need to worry about this? Or as long as I didn't get any error while installing, I shouldn't bother?
--
2004-03-05 15:13:34.09 spid4 SQL global counter collection task is created.
2004-03-05 15:13:41.03 spid51 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.
2004-03-05 15:13:41.34 spid52 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'xp_sqlagent_monitor'.
2004-03-05 15:13:50.89 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:13:50.89 spid52 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2004-03-05 15:13:51.28 spid52 DBCC TRACEON 1717, server process ID (SPID) 52.
2004-03-05 15:15:30.72 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:15:30.72 spid52 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2004-03-05 15:15:31.02 spid52 DBCC TRACEOFF 1717, server process ID (SPID) 52.
2004-03-05 15:15:32.19 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:15:32.19 spid52 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2004-03-05 15:15:45.24 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:15:45.24 spid52 Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install..
2004-03-05 15:16:18.92 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:16:18.92 spid52 Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install..
2004-03-05 15:17:03.03 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:17:03.03 spid52 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2004-03-05 15:17:03.85 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:17:03.85 spid52 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2004-03-05 15:17:04.03 spid52 DBCC TRACEON 1717, server process ID (SPID) 52.
2004-03-05 15:17:10.27 spid52 DBCC TRACEOFF 1717, server process ID (SPID) 52.
2004-03-05 15:17:10.52 spid52 Error: 15457, Severity: 0, State: 1
2004-03-05 15:17:10.52 spid52 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
--
Thanks,
Sarat.

**To be intoxicated is to feel sophisticated, but not be able to say it.**

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-03-22 : 16:07:08

Don't worry about those messages. You see the messages because they had to make data changes to system tables. You can't do that without allowing updates. One example of what they had to change is the value returned by @@VERSION.

Tara

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2004-03-22 : 18:27:11

Cool! Thanks.

**To be intoxicated is to feel sophisticated, but not be able to say it.**

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources