Jump to content


BrokenMasonJar

Scan failed with error = 0x8024000f

Recommended Posts

I'm having an issue with a few servers checking in with Config Manager 2007 for compliance on Software Updates. When I checked the WUAHandler.log file I see the following section repeat:

 

<![LOG[Async searching of updates using WUAgent started.]LOG]!><time="11:50:04.431+300" date="02-13-2014" component="WUAHandler" context="" type="1" thread="8576" file="cwuahandler.cpp:587">
<![LOG[Async searching completed.]LOG]!><time="11:50:05.478+300" date="02-13-2014" component="WUAHandler" context="" type="1" thread="11256" file="cwuahandler.cpp:2099">
<![LOG[OnSearchComplete - Failed to end search job. Error = 0x8024000f.]LOG]!><time="11:50:05.478+300" date="02-13-2014" component="WUAHandler" context="" type="3" thread="1368" file="cwuahandler.cpp:2966">
<![LOG[scan failed with error = 0x8024000f.]LOG]!><time="11:50:05.478+300" date="02-13-2014" component="WUAHandler" context="" type="3" thread="1368" file="cwuahandler.cpp:3223">

 

I see similar errors in the CAS.log and the Windowsupdate.log.

 

This is most noticable when I initiate a Machine Policy Retrieval and Evaluation Cycle

 

Another issue is the system also can't get updates from the SUP. However some parts of the agent are still working normal.

 

I've tried the following to remedy the situation:

 

  • stopped the winmgmt and renamed the repository folder under windows/system32/wbem directory thinking it was a corrupt wmi.
  • ran a repair on the config manager agent.
  • uninstalled and re-installed the agent

Windows firewall is disabled. And I verified the time zones and time is the same as the time servers which all systems sync to.

 

Any thoughts on what the issue could be?

Share this post


Link to post
Share on other sites

Alright, so after 2 weeks working on this I finally figured out the issue. It was a corrupt windows update store. I stumbled upon the following site in search of my original issue. http://support.microsoft.com/kb/958048/en-us

The fix worked. Basically create a batch file with the following:

 

net stop wuauserv
cd %systemroot%
ren SoftwareDistribution SoftwareDistribution.old
net start wuauserv

 

Run the batch with admin priviliages.

 

The sync now completes with no errors in the WUAhandler.log after doing a Machine Policy Retrieval and Evaluation Cycle on the ConfigManager client.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.