locked
WS 2012 Error 80246003 downloading updates from WSUS on WS 2012 RRS feed

  • Question

  • I have a Windows Server 2012 machine that detects updates from WSUS running on another Server 2012 unit, but will not download or install them.

    Error code is 80246003. I have attached the log below.

    I have tried stopping the Windows Update service, deleting the SoftwareDistribution folder, then restarting the service, but it gives exactly the same error.

    2012-09-20	22:04:40:437	 956	e38	DnldMgr	***********  DnldMgr: Begin Downloading Updates [CallerId = AutomaticUpdatesWuApp]  ***********
    2012-09-20	22:04:40:437	 956	e38	DnldMgr	  * Call ID = {08FA26C9-3A57-4020-82FD-B71C9AEA25AC}
    2012-09-20	22:04:40:437	 956	e38	DnldMgr	  * Priority = 3, NetworkCostPolicy = 6, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 2, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2012-09-20	22:04:40:437	 956	e38	DnldMgr	  * Updates to download = 1
    2012-09-20	22:04:40:437	 956	e38	Agent	  *   Title = Security Update for Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package (KB2538242)
    2012-09-20	22:04:40:437	 956	e38	Agent	  *   UpdateId = {BB49CC19-8847-4986-AA93-5E905421E55A}.102
    2012-09-20	22:04:40:437	 956	e38	Agent	  *     Bundles 1 updates:
    2012-09-20	22:04:40:437	 956	e38	Agent	  *       {FC00F823-32D6-4DED-BC46-5FA0BEE5F85B}.102
    2012-09-20	22:04:40:437	 956	e38	DnldMgr	***********  DnldMgr: New download job [UpdateId = {FC00F823-32D6-4DED-BC46-5FA0BEE5F85B}.102]  ***********
    2012-09-20	22:04:40:437	 956	ce4	AU	  # Pending download calls = 1
    2012-09-20	22:04:40:437	 956	ce4	AU	<<## SUBMITTED ## AU: Download updates
    2012-09-20	22:04:40:453	 956	e38	DnldMgr	  * BITS job initialized, JobId = {E200E865-5E2B-46A2-B1E4-5632DCA777E0}
    2012-09-20	22:04:40:453	 956	e38	DnldMgr	BITS job {E200E865-5E2B-46A2-B1E4-5632DCA777E0} using proxy = proxy.education.netspace.net.au:8080, bypass = *.education.vic.gov.au;*.eduweb.vic.gov.au;*.edumail.vic.gov.au;*.vass.vic.edu.au;*.vcaa.vic.edu.au;*.ultranet.vic.edu.au;*.wan;*.acmi.net.au;*.museumvictoria.com.au;*.museum.vic.gov.au;*.mov.vic.gov.au;*.museumvictoria.museum;*.imaxmelbourne.com.au;*.ngv.vic.gov.au;*.slv.vic.gov.au;*.statelibrary.vic.gov.au;*.libraries.vic.gov.au;*.vicnet.net.au;*.cv.vic.gov.au;*.8hourday.org.au;*.ozcam.org;*.ozcam1.gov.au;*.padil.gov.au;*.place-hampi.museum;*.ngvartbeat.org.au;*.insideadog.com.au;*.mirroroftheworld.com.au;*.mylanguage.gov.au;*.openroad.net.au;*.victoriansatwar.net;*.ballaraths.vic.edu.au;10.128.136.*;<local>
    2012-09-20	22:04:40:453	 956	e38	DnldMgr	  * Downloading from http://7540cws01.ballaraths.vic.edu.au:8530/Content/47/B8FAB0BB7F62A24DDFE77B19CD9A1451ABD7B847.exe to C:\Windows\SoftwareDistribution\Download\df5e7d61c8b42c37a119829b904d18a6\b8fab0bb7f62a24ddfe77b19cd9a1451abd7b847 (full file).
    2012-09-20	22:04:40:453	 956	e38	DnldMgr	*********
    2012-09-20	22:04:40:453	 956	e38	DnldMgr	**  END  **  DnldMgr: Begin Downloading Updates [CallerId = AutomaticUpdatesWuApp]
    2012-09-20	22:04:40:453	 956	e38	DnldMgr	*************
    2012-09-20	22:04:40:531	 956	7b8	DnldMgr	BITS job {E200E865-5E2B-46A2-B1E4-5632DCA777E0} completed successfully
    2012-09-20	22:04:40:531	 956	7b8	DnldMgr	CUpdateDownloadJob::GetNetworkCostSwitch() Neither unrestricted or restricted network cost used, so using current cost
    2012-09-20	22:04:40:546	 956	7b8	Misc	Validating signature for C:\Windows\SoftwareDistribution\Download\df5e7d61c8b42c37a119829b904d18a6\b8fab0bb7f62a24ddfe77b19cd9a1451abd7b847:
    2012-09-20	22:04:40:562	 956	7b8	Misc	 Microsoft signed: Yes
    2012-09-20	22:04:40:562	 956	7b8	DnldMgr	  Download job bytes total = 2707352, bytes transferred = 2707352
    2012-09-20	22:04:40:578	 956	e38	DnldMgr	***********  DnldMgr: New download job [UpdateId = {FC00F823-32D6-4DED-BC46-5FA0BEE5F85B}.102]  ***********
    2012-09-20	22:04:40:578	 956	e38	DnldMgr	WARNING: Update validation failed, error 80246003.
    2012-09-20	22:04:40:578	 956	e38	DnldMgr	FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246003.
    2012-09-20	22:04:40:578	 956	e38	DnldMgr	WARNING: Got error (hr = 80246003) starting update 0 in call 3. Notifying call.
    2012-09-20	22:04:40:578	 956	e38	DnldMgr	Error 0x80246003 occurred while downloading update; notifying dependent calls.
    2012-09-20	22:04:40:578	 956	6ac	AU	>>##  RESUMED  ## AU: Download update [UpdateId = {BB49CC19-8847-4986-AA93-5E905421E55A}]
    2012-09-20	22:04:40:578	 956	6ac	AU	  # WARNING: Download failed, error = 0x80246003
    2012-09-20	22:04:40:578	 956	6ac	AU	#########
    2012-09-20	22:04:40:578	 956	6ac	AU	##  END  ##  AU: Download updates
    2012-09-20	22:04:40:578	 956	6ac	AU	#############
    

    Thursday, September 20, 2012 12:24 PM

Answers

  • The other thought I had is that working in a school, our central authority has a WSUS 2008R2 setup that we point our WSUS servers to. I'm not sure if it has been updated with the patch to support WS2012 servers, but I don't think this should have any effect?

    It could. Consider what the purpose of the update in KB2734608 is to provide WSUS v3.2 the ability to patch Win8/Win2012 systems, and why Win8/Win2012 systems that were previously registered with an unpatched WSUS v3.2 need to have their datastore blown away.

    Then consider the reality that if your Win2012 servers are synchronizing from the upstream WSUS v3.2 server, then they're also getting their metadata and content from that WSUS v3.2 server, and if KB2734608 is not applied to that server, then the metadata/content you are downloading from that server are not properly hashed for use by a Win8/Win2012 server -- Which is what the 0x80246003 error code essentially means. From the WSUS Technical Reference: Windows Update Agent Result Codes -- 0x80246003 = A download manager operation could not be completed because the file metadata requested an unrecognized hash algorithm.

    Also recall that in the text of KB2734608 we're told to synchronize all downstream servers after installing KB2734608. What would be the reason for this? To update the metadata in the downstream servers with the new hash calculations from the new hash algorithm provided by KB2734608.

    The problem here is that the error message says the file metadata requested an unrecognized hash algorithm. That means, from my take, that the update package is still using the older hash algorithm, not the newer one. The *files* are not really the issue here, but rather the *metadata* is the issue. The metadata you're getting from the unpatched upstream server.

    Ergo, it seems that the only viable resolution is to [1] install KB2734608 on the upstream server and [2] resync. And if that's not going to happen in an acceptable time frame for your needs, then your only other option is to abandon the use of that upstream server, and rebuild a WSUS v6 server that synchronizes directly from Microsoft.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    • Marked as answer by pduthie_au Saturday, September 22, 2012 2:54 AM
    Friday, September 21, 2012 6:07 PM

All replies

  • >> have a Windows Server 2012 machine that detects updates from WSUS running on another Server 2012 unit, but will not download or install them.<<

    Try to install

    http://support.microsoft.com/kb/2734608

    Thursday, September 20, 2012 2:27 PM
  • same problem here.

    KB2734608 cannot be used coz it's for WSUS3.0 not 6.2

    Report: https://connect.microsoft.com/WindowsServer/feedback/details/763790/update-from-wsus-80246003


    Eternal Snow



    • Edited by EternalSnow Thursday, September 20, 2012 5:58 PM
    Thursday, September 20, 2012 3:37 PM
  • I'm wondering if its because I originally had 2 WSUS servers - one running on 2008R2 (without patch for Win8/WS2012) for all clients up to Win7/2008R2, and a new one I built last week that only serviced WS2012/Win8 clients. This week the old WSUS server decided to die, so I decided to deploy a new server for all clients. The old clients are happily detecting and installing updates from the new server, but the 5 WS2012 clients I had on the other WSUS 6.0 server won't. I wonder if somewhere it's trying to download the updates from the old server that doesn't have these updates approved or downloaded (I only synced WS2012/Win8 updates to this server, and the updates that are failing are for other things - Visual C runtimes, etc)

    The other thought I had is that working in a school, our central authority has a WSUS 2008R2 setup that we point our WSUS servers to. I'm not sure if it has been updated with the patch to support WS2012 servers, but I don't think this should have any effect?

    Thursday, September 20, 2012 11:19 PM
  • And another thought. It looks like both WS2012 and Win8 clients can download and install updates for themselves (ie Win8/WS2012 updates) but not updates for any other product from WSUS.
    Friday, September 21, 2012 2:30 AM
  • I wonder if somewhere it's trying to download the updates from the old server

    Is this the old server or the new server:

    2012-09-20 22:04:40:453 956 e38 DnldMgr * Downloading from http://7540cws01.ballaraths.vic.edu.au:8530


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Friday, September 21, 2012 5:44 PM
  • The other thought I had is that working in a school, our central authority has a WSUS 2008R2 setup that we point our WSUS servers to. I'm not sure if it has been updated with the patch to support WS2012 servers, but I don't think this should have any effect?

    It could. Consider what the purpose of the update in KB2734608 is to provide WSUS v3.2 the ability to patch Win8/Win2012 systems, and why Win8/Win2012 systems that were previously registered with an unpatched WSUS v3.2 need to have their datastore blown away.

    Then consider the reality that if your Win2012 servers are synchronizing from the upstream WSUS v3.2 server, then they're also getting their metadata and content from that WSUS v3.2 server, and if KB2734608 is not applied to that server, then the metadata/content you are downloading from that server are not properly hashed for use by a Win8/Win2012 server -- Which is what the 0x80246003 error code essentially means. From the WSUS Technical Reference: Windows Update Agent Result Codes -- 0x80246003 = A download manager operation could not be completed because the file metadata requested an unrecognized hash algorithm.

    Also recall that in the text of KB2734608 we're told to synchronize all downstream servers after installing KB2734608. What would be the reason for this? To update the metadata in the downstream servers with the new hash calculations from the new hash algorithm provided by KB2734608.

    The problem here is that the error message says the file metadata requested an unrecognized hash algorithm. That means, from my take, that the update package is still using the older hash algorithm, not the newer one. The *files* are not really the issue here, but rather the *metadata* is the issue. The metadata you're getting from the unpatched upstream server.

    Ergo, it seems that the only viable resolution is to [1] install KB2734608 on the upstream server and [2] resync. And if that's not going to happen in an acceptable time frame for your needs, then your only other option is to abandon the use of that upstream server, and rebuild a WSUS v6 server that synchronizes directly from Microsoft.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    • Marked as answer by pduthie_au Saturday, September 22, 2012 2:54 AM
    Friday, September 21, 2012 6:07 PM
  • Looks like this is the answer - I created a second WSUS server, synced from microsoft and the updates all install happily from there.
    Saturday, September 22, 2012 2:55 AM
  • Looks like this is the answer - I created a second WSUS server, synced from microsoft and the updates all install happily from there.
    Thank you for the feedback.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Monday, September 24, 2012 10:13 PM