Cannot apply KB 932557 - receiving Error Code: 0x2C24

Question

I keep receiving an update notification for KB 932557 and when I try to apply the fix, it fails. Checking update history tells me error code 0x2c24 is the reason for failure.

 

I cannot find any help on this error code anywhere.

 

Any help most appreciated.

 

 

Answer 1

To clarify, this relates to SQL Server 2005 developer edition running on Windows XP Pro.

Answer 2

 

Thanks ever so much for your help in resolving this problem, Microsoft. NOT.

Answer 3

 

So did you ever figure this out? I'm getting this obscure error as well right now.

Answer 4

 

Sadly not Bryan.

 

I run MS One Care permanantly in amber mode and it repeatedly tells me I have important updates to apply! I don't think there is any work around other than a new install of windows and user software. Personally I would rather run One Care in Amber mode!

 

Good luck if you try to fix the problem and any information would be helpful. I wasted many many hours trying to figure this out.

 

Answer 5

Well I went and downloaded the actual hot fix via the KB's link and that didn't work either. However, it gave me more information than before. It wouldn't even let me apply the patch because it said it was for an earlier version of SQL than I ran. I found a second download for a later build (that supposedly fixes the same thing) and it said nearly the same thing. But I haven't found one for build 3161 (SP2 + the two hot fixes that came out soon after).

 

I'll keep an eye out, but as of right now I think this patch is falsely saying it is needed. Joy..

Answer 6

 

Same problem here.

 

This is the part of the log I get:

 

[...]

2007-10-03 00:52:40:359 1040 e60 Agent *************
2007-10-03 00:52:40:359 1040 e60 Agent ** START **  Agent: Finding updates [CallerId = MicrosoftUpdate]
2007-10-03 00:52:40:359 1040 e60 Agent *********
2007-10-03 00:52:40:359 1040 82c Agent   *   Title = Aggiornamento per SQL Server 2005 (KB 932557)
2007-10-03 00:52:40:359 1040 82c Agent   *   UpdateId = {8D8463BE-DAB3-446F-8077-899C8116D08A}.100
2007-10-03 00:52:40:359 1040 82c Agent   *     Bundles 1 updates:
2007-10-03 00:52:40:359 1040 82c Agent   *       {B4EB0DB6-2E8C-4BA8-9300-0E3893DC400A}.100
2007-10-03 00:52:40:359 1040 e60 Agent   * Online = Yes; Ignore download priority = No
2007-10-03 00:52:40:359 1040 e60 Agent   * Criteria = "IsInstalled=0 and IsHidden=1"
2007-10-03 00:52:40:359 1040 e60 Agent   * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D}
2007-10-03 00:52:40:359 1040 908 AU >>##  RESUMED  ## AU: Search for updates [CallId = {450C5A20-C973-447E-9943-86A2B37A50EF}]
2007-10-03 00:52:40:359 1040 908 AU   # 0 updates detected
2007-10-03 00:52:40:359 1040 908 AU #########
2007-10-03 00:52:40:359 1040 908 AU ##  END  ##  AU: Search for updates [CallId = {450C5A20-C973-447E-9943-86A2B37A50EF}]
2007-10-03 00:52:40:359 1040 908 AU #############
2007-10-03 00:52:40:718 1040 e60 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2007-10-03 00:52:40:734 1040 e60 Misc  Microsoft signed: Yes
2007-10-03 00:52:40:968 1040 e60 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2007-10-03 00:52:40:984 1040 e60 Misc  Microsoft signed: Yes
2007-10-03 00:52:41:000 1040 e60 Agent Checking for updated auth cab for service 7971f918-a847-4430-9279-4a52d1efe18d at http://www.update.microsoft.com/v7/microsoftupdate/redir/muauth.cab
2007-10-03 00:52:41:000 1040 e60 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\authcab.cab:
2007-10-03 00:52:41:015 1040 e60 Misc  Microsoft signed: Yes
2007-10-03 00:52:41:718 1040 e60 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\authcab.cab:
2007-10-03 00:52:41:734 1040 e60 Misc  Microsoft signed: Yes
2007-10-03 00:52:41:781 1040 e60 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\authcab.cab:
2007-10-03 00:52:41:953 1040 e60 Misc  Microsoft signed: Yes
2007-10-03 00:52:42:015 3564 df0 DtaStor Update service properties: service registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
2007-10-03 00:52:46:234 1040 e60 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muredir.cab:
2007-10-03 00:52:46:250 1040 e60 Misc  Microsoft signed: Yes
2007-10-03 00:52:46:296 1040 e60 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muredir.cab:
2007-10-03 00:52:46:296 1040 e60 Misc  Microsoft signed: Yes
2007-10-03 00:52:46:312 1040 e60 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
2007-10-03 00:52:46:312 1040 e60 PT   + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx
2007-10-03 00:53:39:000 1040 908 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {8D8463BE-DAB3-446F-8077-899C8116D08A}]
2007-10-03 00:53:39:000 1040 908 AU   # WARNING: Install failed, error = 0x80240017 / 0x00000000
2007-10-03 00:53:39:000 1040 82c Agent *********
2007-10-03 00:53:39:000 1040 82c Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
2007-10-03 00:53:39:000 1040 82c Agent *************
2007-10-03 00:53:39:000 1040 908 AU Install call completed.
2007-10-03 00:53:39:000 1040 908 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000

[...]

Answer 7

Hi Guys,

 

I just went through some of this on one of my servers. SQL Server had a few services disabled (cause I rarely require it). Chances are good that this is what is wrong with you, too.

 

Right click My Computer, select Manage, Services and Applications, Services. Now find everything that STARTS WITH "MSSQL" or "SQLAgent" that has a "startup type" of "Disabled" and change their startup type to "Manual".

 

You will then be able to successfully install the update.

 

It will require a reboot. After it comes back up you can re-disable the services.

 

What a waste of time.

 

-Shawn

 

Answer 8

Using Shawn's solution above worked for me when attmepting to install KB948110 and getting the error.  I found that my SBS2003 (new build) box still had the Monitoring & Reporting SQL instance disabled (because I had not run its wizard yet).  Set the instance to Manual start type, and was able to install the update successfully.

 

THANKS Shawn!

Answer 9

 

Hi guys, I had the same problem for updates

Sicherheitsupdate für SQL Server 2000 Service Pack 4 (KB948110) (error exit code 0x2C24)

and

Update für Windows Server 2003 (KB934238)  (error exit code 0x80242006)

 

And what Shawn wrotes this worked for me too! THX!

 

It was the MSSQL$SBSMONITORING service which was disabled. After setting it to manual I directly was able to install both updates!

 

Thank you Shawn!

 

 

Greetz from Luxembourg

Answer 10

Thanks a million from me too.
Just changing MSSQL$SBSMONITORING service from diabled to manual did the job.
G'day from Oz

Answer 11

 

Thank you Shawn, this is a problem I ignored for awhile.  Thanks to you, I can mark this off my list!

Answer 12

Also, I would re-download SP2 and then re-apply it -- if you installed SSIS after your initial SQL install.  SQL SP2 will recognize the newly installed SSIS and update it only.

Why re-download SP2?  MS updates it, so if you have an old copy sitting around, it likely is different from what is up on the MS website.

Answer 13

 I just used Shawn's method successfully on Server 2003 trying to apply update KB960082.  How disappointing that MS can't do more to help prevent this difficulty, and we have to go through this inconvenience of messing around with googling error codes and finding kludged-together explanations. 

jl

Answer 14

thanks shawn - it worked for me too!