locked
W2K8R2 server stuck checking for updates RRS feed

  • Question

  • Hi All,

    I have two servers in my environment that have randomly just stopped connecting to the WSUS about a week ago.

    I have tried different fixes found only to  try to re-mediate the issue but all seem to have failed.

    Both windowsupdate.log report the exact same thing...

    2015-11-18	12:41:42:752	 944	17b8	Misc	===========  Logging initialized (build: 7.6.7601.19046, tz: -0800)  ===========
    2015-11-18	12:41:42:752	 944	17b8	Misc	  = Process: C:\Windows\system32\svchost.exe
    2015-11-18	12:41:42:752	 944	17b8	Misc	  = Module: c:\windows\system32\wuaueng.dll
    2015-11-18	12:41:42:752	 944	17b8	Service	*************
    2015-11-18	12:41:42:767	 944	17b8	Service	** START **  Service: Service startup
    2015-11-18	12:41:42:767	 944	17b8	Service	*********
    2015-11-18	12:41:42:783	 944	17b8	Agent	  * WU client version 7.6.7601.19046
    2015-11-18	12:41:42:783	 944	17b8	Agent	  * Base directory: C:\Windows\SoftwareDistribution
    2015-11-18	12:41:42:783	 944	17b8	Agent	  * Access type: No proxy
    2015-11-18	12:41:42:783	 944	17b8	Agent	  * Network state: Connected
    2015-11-18	12:41:43:173	 944	1684	Report	CWERReporter::Init succeeded
    2015-11-18	12:41:43:173	 944	1684	Agent	***********  Agent: Initializing Windows Update Agent  ***********
    2015-11-18	12:41:43:173	 944	1684	Agent	  * Prerequisite roots succeeded.
    2015-11-18	12:41:43:173	 944	1684	Agent	***********  Agent: Initializing global settings cache  ***********
    2015-11-18	12:41:43:173	 944	1684	Agent	  * WSUS server: http://WSUS
    2015-11-18	12:41:43:173	 944	1684	Agent	  * WSUS status server: http://WSUS
    2015-11-18	12:41:43:173	 944	1684	Agent	  * Target group: (Unassigned Computers)
    2015-11-18	12:41:43:173	 944	1684	Agent	  * Windows Update access disabled: No
    2015-11-18	12:41:43:173	 944	1684	DnldMgr	Download manager restoring 0 downloads
    2015-11-18	12:41:43:469	 944	17b8	Report	***********  Report: Initializing static reporting data  ***********
    2015-11-18	12:41:43:469	 944	17b8	Report	  * OS Version = 6.1.7601.1.0.196880
    2015-11-18	12:41:43:469	 944	17b8	Report	  * OS Product Type = 0x00000007
    2015-11-18	12:41:43:485	 944	17b8	Report	  * Computer Brand = Dell Inc.
    2015-11-18	12:41:43:485	 944	17b8	Report	  * Computer Model = PowerEdge R310
    2015-11-18	12:41:43:485	 944	17b8	Report	  * Bios Revision = 1.6.4
    2015-11-18	12:41:43:485	 944	17b8	Report	  * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 1.6.4
    2015-11-18	12:41:43:485	 944	17b8	Report	  * Bios Release Date = 2011-03-03T00:00:00
    2015-11-18	12:41:43:485	 944	17b8	Report	  * Locale ID = 1033
    2015-11-18	12:42:28:163	 944	17b8	AU	###########  AU: Initializing Automatic Updates  ###########
    2015-11-18	12:42:28:163	 944	17b8	AU	AU setting next detection timeout to 2015-11-18 20:42:28
    2015-11-18	12:42:28:163	 944	17b8	AU	  # WSUS server: http://WSUS
    2015-11-18	12:42:28:163	 944	17b8	AU	  # Detection frequency: 1
    2015-11-18	12:42:28:163	 944	17b8	AU	  # Approval type: Pre-install notify (Policy)
    2015-11-18	12:42:28:163	 944	17b8	AU	  # Auto-install minor updates: Yes (Policy)
    2015-11-18	12:42:28:163	 944	17b8	AU	Successfully wrote event for AU health state:0
    2015-11-18	12:42:28:163	 944	17b8	AU	Initializing featured updates
    2015-11-18	12:42:28:163	 944	17b8	AU	Found 0 cached featured updates
    2015-11-18	12:42:28:163	 944	17b8	AU	Successfully wrote event for AU health state:0
    2015-11-18	12:42:28:163	 944	17b8	AU	Successfully wrote event for AU health state:0
    2015-11-18	12:42:28:163	 944	17b8	AU	AU finished delayed initialization
    2015-11-18	12:42:28:163	 944	17b8	AU	#############
    2015-11-18	12:42:28:163	 944	17b8	AU	## START ##  AU: Search for updates
    2015-11-18	12:42:28:163	 944	17b8	AU	#########
    2015-11-18	12:42:28:163	 944	17b8	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {44978655-49C2-44DE-9453-30CA7433E787}]
    2015-11-18	12:42:28:163	 944	14bc	Agent	*************
    2015-11-18	12:42:28:163	 944	14bc	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-11-18	12:42:28:163	 944	14bc	Agent	*********
    2015-11-18	12:42:28:163	 944	14bc	Agent	  * Online = Yes; Ignore download priority = No
    2015-11-18	12:42:28:163	 944	14bc	Agent	  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2015-11-18	12:42:28:163	 944	14bc	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2015-11-18	12:42:28:163	 944	14bc	Agent	  * Search Scope = {Machine}
    2015-11-18	12:42:28:163	 944	14bc	Setup	Checking for agent SelfUpdate
    2015-11-18	12:42:28:163	 944	14bc	Setup	Client version: Core: 7.6.7601.19046  Aux: 7.6.7601.19046
    2015-11-18	12:42:30:457	 944	14bc	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2015-11-18	12:42:30:472	 944	14bc	Misc	 Microsoft signed: NA
    2015-11-18	12:42:30:472	 944	14bc	Misc	WARNING: Cab does not contain correct inner CAB file.
    2015-11-18	12:42:30:472	 944	14bc	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2015-11-18	12:42:30:488	 944	14bc	Misc	 Microsoft signed: NA
    2015-11-18	12:42:30:488	 944	14bc	Setup	Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
    2015-11-18	12:42:30:488	 944	14bc	Setup	Skipping SelfUpdate check based on the /SKIP directive in wuident
    2015-11-18	12:42:30:488	 944	14bc	Setup	SelfUpdate check completed.  SelfUpdate is NOT required.
    2015-11-18	12:42:30:706	 944	14bc	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-11-18	12:42:30:706	 944	14bc	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUS/ClientWebService/client.asmx
    2015-11-18	12:42:53:311	 944	14bc	PT	+++++++++++  PT: Synchronizing extended update info  +++++++++++
    2015-11-18	12:42:53:311	 944	14bc	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUS/ClientWebService/client.asmx
    2015-11-18	12:47:01:585	 944	17dc	AU	Triggering AU detection through DetectNow API
    2015-11-18	12:47:01:585	 944	17dc	AU	Piggybacking on an AU detection already in progress
    

    A little background on the environtment.

    WSUS in configured on servers via GPO.

    Other servers in the environment work just fine.

    I am able to ping the WSUS server from each server having the issue.

    I am able to download http://WSUS/selfupdate/wuident.cab for each server having the issue.

    Any suggestions will be gladly appreciated.



    Wednesday, November 18, 2015 9:13 PM

Answers

  • Issue resolved.

    For those who care I tried several attempts at fixing it on the client side

    I tried resetting Windows Update Components - https://support.microsoft.com/en-us/kb/971058

    Renamed software distribution folder

    Reregistering DLLs etc...

    All with little success.

    Then I read somewhere where some updates where causing issues on some machines due to the speed of the machines, be it network speed or CPU\RAM speed, causing a similar issue to the one I was experiencing.

    Which led me to believe this could potentially be a WSUS issue. 

    Since taking over the environment I noticed server cleanup had never been done in like three years and when I tried it the WSUS went haywire.

    Needless to say after reinstalling WSUS the two problematic servers are now successfully connecting and reporting.

    • Marked as answer by Coolguycarlos Friday, November 20, 2015 6:32 PM
    Friday, November 20, 2015 6:32 PM

All replies

  • I don't see anything wrong, try this : http://windows.microsoft.com/en-au/windows7/open-the-windows-update-troubleshooter


    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, November 19, 2015 4:57 AM
  • Issue resolved.

    For those who care I tried several attempts at fixing it on the client side

    I tried resetting Windows Update Components - https://support.microsoft.com/en-us/kb/971058

    Renamed software distribution folder

    Reregistering DLLs etc...

    All with little success.

    Then I read somewhere where some updates where causing issues on some machines due to the speed of the machines, be it network speed or CPU\RAM speed, causing a similar issue to the one I was experiencing.

    Which led me to believe this could potentially be a WSUS issue. 

    Since taking over the environment I noticed server cleanup had never been done in like three years and when I tried it the WSUS went haywire.

    Needless to say after reinstalling WSUS the two problematic servers are now successfully connecting and reporting.

    • Marked as answer by Coolguycarlos Friday, November 20, 2015 6:32 PM
    Friday, November 20, 2015 6:32 PM
  • Hi,

    Glad to hear that you have found a solution and thank you for sharing with us!

    You solution is very beneficial to others who have similar issues.

    Please feel free to let us know if there are any further requirements.

    Best Regards,

    Amy


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, December 15, 2015 2:58 AM