Hi all,
Hardly an SCCM/WSUS guru here, but I've had it running swimmingly for a few years now. Until last month... Only noticed it now, but it simply isn't working anymore. Ugh.
Started on 12/5/2016. In the Application Log I get repeated Event IDs such as:
Log Name: Application
Source: SMS Server
Date: 1/5/2017 5:25:03 PM
Event ID: 6703
Task Category: SMS_WSUS_SYNC_MANAGER
Level: Error
Keywords: Classic
User: N/A
Computer: SERVERNAME
Description:
On 1/5/2017 5:25:03 PM, component SMS_WSUS_SYNC_MANAGER on computer SERVERNAME reported: WSUS Synchronization failed.
Message: WSUS server not configured. Please refer to WCM.log for configuration error details..
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error
And...
Log Name: Application
Source: SMS Server
Date: 1/5/2017 5:20:03 PM
Event ID: 6701
Task Category: SMS_WSUS_SYNC_MANAGER
Level: Information
Keywords: Classic
User: N/A
Computer: SERVERNAME
Description:
On 1/5/2017 5:20:03 PM, component SMS_WSUS_SYNC_MANAGER on computer SERVERNAME reported: WSUS Synchronization started.
And...
Log Name: Application
Source: SMS Server
Date: 1/5/2017 4:32:02 PM
Event ID: 7000
Task Category: SMS_WSUS_CONTROL_MANAGER
Level: Error
Keywords: Classic
User: N/A
Computer: SERVERNAME
Description:
On 1/5/2017 4:32:02 PM, component SMS_WSUS_CONTROL_MANAGER on computer SERVERNAME reported: WSUS Control Manager failed to configure proxy settings on WSUS Server "SERVERNAME".
Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted.
Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified
or proxy server port is invalid.
And...
Log Name: Application
Source: SMS Server
Date: 1/5/2017 4:12:00 PM
Event ID: 7001
Task Category: SMS_WSUS_CONTROL_MANAGER
Level: Error
Keywords: Classic
User: N/A
Computer: SERVERNAME
Description:
On 1/5/2017 4:12:00 PM, component SMS_WSUS_CONTROL_MANAGER on computer SERVERNAME reported: Failures were reported on WSUS Server "SERVERNAME" for WSUS components "WSUSService,".
Solution: Verify that the failed WSUS components are installed and running.
I've Googled until I'm blue in the face, tried numerous things, and gotten nowhere. So I opened up this WCM.log file and have gone back to the general area of 12/5/2016 when this all seems to have started. My head is spinning... Not a clue what all this means. Here goes:
Attempting connection to WSUS server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:18 PM 5756 (0x167C)
Successfully connected to server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:18 PM 5756 (0x167C)
Done using TOB\sccm_svc credentials SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:20 PM 5756 (0x167C)
Using TOB\sccm_svc credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:20 PM 5756 (0x167C)
Attempting connection to WSUS server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:20 PM 5756 (0x167C)
Successfully connected to server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:20 PM 5756 (0x167C)
Done using TOB\sccm_svc credentials SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:21 PM 5756 (0x167C)
Waiting for changes for 56 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 10:25:21 PM 5756 (0x167C)
Shutting down... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:12:48 PM 5756 (0x167C)
Shutting Down... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:12:48 PM 5756 (0x167C)
SMS_EXECUTIVE started SMS_WSUS_CONFIGURATION_MANAGER as thread ID 5940 (0x1734). SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:16 PM 2224 (0x08B0)
This TOB-SCCM01.TOB.int system is the SMS Site Server. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:17 PM 5940 (0x1734)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:17 PM 5940 (0x1734)
Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:17 PM 5940 (0x1734)
Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:17 PM 5940 (0x1734)
SUP0: TOB-SCCM01.TOB.int, group = TOBSQL01, nlb = SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:17 PM 5940 (0x1734)
Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:17 PM 5940 (0x1734)
Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:17 PM 5940 (0x1734)
Wait timed out after 0 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:18 PM 5940 (0x1734)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384 SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.21848 SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Using TOB\sccm_svc credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Attempting connection to WSUS server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:29 PM 5940 (0x1734)
Successfully connected to server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:50 PM 5940 (0x1734)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:50 PM 5940 (0x1734)
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 12/5/2016 11:21:52 PM 5940 (0x1734)
Done using TOB\sccm_svc credentials SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:52 PM 5940 (0x1734)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:52 PM 5940 (0x1734)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=TOB-SCCM01.TOB.int SITE=TOB PID=3824 TID=5940 GMTDATE=Tue Dec 06 04:21:52.207 2016 ISTR0="TOB-SCCM01.TOB.int" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:52 PM 5940 (0x1734)
Setting new configuration state to 3 (WSUS_CONFIG_FAILED) SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:52 PM 5940 (0x1734)
Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:21:52 PM 5940 (0x1734)
Shutting down... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:24:20 PM 5940 (0x1734)
Shutting Down... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:24:20 PM 5940 (0x1734)
SMS_EXECUTIVE started SMS_WSUS_CONFIGURATION_MANAGER as thread ID 6052 (0x17A4). SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:51 PM 3472 (0x0D90)
This TOB-SCCM01.TOB.int system is the SMS Site Server. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:52 PM 6052 (0x17A4)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:52 PM 6052 (0x17A4)
Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:52 PM 6052 (0x17A4)
Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:52 PM 6052 (0x17A4)
SUP0: TOB-SCCM01.TOB.int, group = TOBSQL01, nlb = SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:52 PM 6052 (0x17A4)
Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:52 PM 6052 (0x17A4)
Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:52 PM 6052 (0x17A4)
Wait timed out after 0 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:29:54 PM 6052 (0x17A4)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384 SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.21848 SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Using TOB\sccm_svc credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Attempting connection to WSUS server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:04 PM 6052 (0x17A4)
Successfully connected to server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
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 12/5/2016 11:30:08 PM 6052 (0x17A4)
Done using TOB\sccm_svc credentials SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=TOB-SCCM01.TOB.int SITE=TOB PID=3776 TID=6052 GMTDATE=Tue Dec 06 04:30:08.904 2016 ISTR0="TOB-SCCM01.TOB.int" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
Setting new configuration state to 3 (WSUS_CONFIG_FAILED) SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
Waiting for changes for 60 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:08 PM 6052 (0x17A4)
SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:13 PM 6052 (0x17A4)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:13 PM 6052 (0x17A4)
Waiting for changes for 60 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/5/2016 11:30:13 PM 6052 (0x17A4)
Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:00:10 AM 6052 (0x17A4)
SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:00:15 AM 6052 (0x17A4)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:00:15 AM 6052 (0x17A4)
Waiting for changes for 30 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:00:16 AM 6052 (0x17A4)
Wait timed out after 30 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:29:52 AM 6052 (0x17A4)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.21848 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Using TOB\sccm_svc credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Attempting connection to WSUS server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Successfully connected to server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
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 12/6/2016 12:30:02 AM 6052 (0x17A4)
Done using TOB\sccm_svc credentials SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=TOB-SCCM01.TOB.int SITE=TOB PID=3776 TID=6052 GMTDATE=Tue Dec 06 05:30:02.913 2016 ISTR0="TOB-SCCM01.TOB.int" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Waiting for changes for 60 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 12:30:02 AM 6052 (0x17A4)
Wait timed out after 60 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:29:52 AM 6052 (0x17A4)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.21848 SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Using TOB\sccm_svc credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Attempting connection to WSUS server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:02 AM 6052 (0x17A4)
Successfully connected to server: TOB-SCCM01.TOB.int, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:03 AM 6052 (0x17A4)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 12/6/2016 1:30:03 AM 6052 (0x17A4)
System.IndexOutOfRangeException: Index was outside the boun
Basically, it looks like SOMETHING changed on 12/5/2016 and caused everything to go haywire. Can someone give me a hand with all this, please? Thanks!
CB