Software Updates missing all December 2016 patches

[lt.son]

Hello all,

 

On Tuesday afternoon I searched for the new updates and nothing showed up. I figured I might be too early so I went about my business. This morning (Thursday) I searched and it still finds no updated released in the last month. I searched the last 2 months and it found the November Rollups that have already been deployed.

 

Last month in our monthly maintenance window we updated to CU4. Could that be the problem? I have not heard of any issues regarding CU4, although it's still early in it's release.

 

I am not even sure where to look to see why it's not finding the latest updates.

 

 

[Apexes]

Check your wsync.log on your primary site server, that'll be the first step.

[Config Mangler]

Probably the same issue we are seeing. Microsoft changed the update classifications without telling anyone.

We previously used a rule to search for updates with a SEVERITY of "critical" or "Important" they have moved that value under the "update classification" so we were getting no updates.

[Rocket Man]

Probably better to use a title filter like Security Monthly Quality Rollup if it is what Config Mangler has suggested is the issue.

The update classification for the monthly quality Rollups is now Security Updates

[lt.son]

Thanks for the replies.

I've been traveling for work and have just now started looking back into this.

 

 

Check your wsync.log on your primary site server, that'll be the first step.

 

here are the pertinent errors (I think)

 

wsyncmgr.log

Wakeup for a polling cycle

Starting Sync

Performing sync on retry schedule 

Read SUPs from SCF for __server.sub.domain.com__ 

Found 1 SUPs 

Found active SUP __server.sub.domain.com__ from SCF File.~  

STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=__server.sub.domain.com__ SITE=TSM PID=3428 TID=6968 
	GMTDATE=Wed Jan 04 09:10:06.799 2017 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=__server.sub.domain.com__ SITE=TSM PID=3428 TID=6968 
	GMTDATE=Wed Jan 04 09:15:06.917 2017 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured. 
	Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Sync failed. Will retry in 60 minutes

WCM.log

Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONFIGURATION_MANAGER

Checking runtime v2.0.50727...	SMS_WSUS_CONFIGURATION_MANAGER

Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.	SMS_WSUS_CONFIGURATION_MANAGER

Checking runtime v4.0.30319...	SMS_WSUS_CONFIGURATION_MANAGER

Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONFIGURATION_MANAGER

Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.21848	SMS_WSUS_CONFIGURATION_MANAGER

Supported WSUS version found	SMS_WSUS_CONFIGURATION_MANAGER

Attempting connection to WSUS server: __server.sub.domain.com__, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER

Successfully connected to server: __server.sub.domain.com__, port: 8530, useSSL: False	SMS_WSUS_CONFIGURATION_MANAGER

Verify Upstream Server settings on the Active WSUS Server	SMS_WSUS_CONFIGURATION_MANAGER

System.IndexOutOfRangeException: Index was outside the bounds of the array.~~   
	at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)~~   
	at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetConfiguration()~~   
	at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()~~   
	at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)~~   
	at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)~~   
	at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetConfiguration()~~   
	at Microsoft.SystemsManagementServer.WSUS.WSUSServer.SetUpstreamServerSettings(Boolean SyncFromMicrosoftUpdate, Boolean ReplicaServer, 
		String UpstreamWSUSServerName, Int32 UpstreamWSUSServerPortNumber, Boolean UseSSL, Boolean HostBinariesOnMU, Int32 ReportingLevel, 
		Int32 MaximumAllowedComputers)	SMS_WSUS_CONFIGURATION_MANAGER

Remote configuration failed on WSUS Server.	SMS_WSUS_CONFIGURATION_MANAGER

STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=__server.sub.domain.com__ SITE=TSM PID=3428 TID=6936 
		GMTDATE=Tue Jan 03 15:52:23.576 2017 ISTR0="__server.sub.domain.com__" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" 
		ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_CONFIGURATION_MANAGER

Waiting for changes for 60 minutes	SMS_WSUS_CONFIGURATION_MANAGER

and WSUSmgr.log

Timed Out...~

Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ 

Checking runtime v2.0.50727...~ 

Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.~ 

Checking runtime v4.0.30319...~ 

Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384~ 

Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.21848~

Supported WSUS version found~

Attempting connection to local WSUS server 

Successfully connected to local WSUS server

System.IndexOutOfRangeException: Index was outside the bounds of the array.~~   
	at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)~~   
	at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetConfiguration()~~   
	at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()~~   
	at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)~~   
	at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)~~   
	at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetConfiguration()~~   
	at Microsoft.SystemsManagementServer.WSUS.WSUSServer.SetProxySettings(Boolean UseProxy, String ProxyName, Int32 ProxyServerPort, 
		Boolean AnonymousProxyAccess, String ProxyUserName, String ProxyUserDomain, String ProxyUserPassword, Boolean AllowProxyCredentialsOverNonSsl)

Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ 

Attempting connection to local WSUS server  

Successfully connected to local WSUS server 

Errors were reported in these WSUS Server components WSUSService, on WSUS Server __server.sub.domain.com__~ 

Failures reported during periodic health check by the WSUS Server __server.sub.domain.com__. Will retry check in 1 minutes~ 

~Waiting for changes for 1 minutes 

[lt.son]

Probably the same issue we are seeing. Microsoft changed the update classifications without telling anyone.

We previously used a rule to search for updates with a SEVERITY of "critical" or "Important" they have moved that value under the "update classification" so we were getting no updates.

 

I'm not using any filters, just searching for all updates released in the last 1 month. Nothing is found.