SCCM 2012 SP1 CAS - Unable to sync to Microsoft Updates Sites

Good Day SCCM Experts.
I would like to seek your help in resolving my issue in MY SCCM CAS, the problem is that CAS is unable to sync to microsoft update. The last good sync was on July 16, we have previously encountered an error and ended up reinstalling the WSUS/Software Update
Point.
I have followed the instruction for installing the WSUS on this link:
http://www.windows-noob.com/forums/index.php?/topic/5683-using-system-center-2012-configuration-manager-part-5-adding-wsus-adding-the-sup-role-deploying-the-configuration-manager-client-agent/
Also pls take note, CAS doesnt have any full internet access. We have only added a proxy on the internet connectivity settings.
First error we have encountered before re-installing the role:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
After re-installing the role still encountering errors: Below are the logs from wsynmgr.log, wcm.log, and wsusctrl.log
WSYNCYMGR.LOG:
Sync failed: WSUS update source not found on site C01. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 7/24/2014 7:00:01 AM
5652 (0x1614)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=5652 GMTDATE=Wed Jul 23 23:00:01.042 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source
not found on site C01. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/24/2014 7:00:01 AM
5652 (0x1614)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
7/24/2014 7:00:01 AM 5652 (0x1614)
Setting sync alert to active state on site C01
SMS_WSUS_SYNC_MANAGER 7/24/2014 7:00:01 AM
5652 (0x1614)
Sync time: 0d00h00m00s SMS_WSUS_SYNC_MANAGER
7/24/2014 7:00:01 AM 5652 (0x1614)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
7/24/2014 8:00:01 AM 5652 (0x1614)
Starting Sync SMS_WSUS_SYNC_MANAGER
7/24/2014 8:00:01 AM 5652 (0x1614)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
7/24/2014 8:00:01 AM 5652 (0x1614)
Read SUPs from SCF for MYHQKUL990707S.sdb.com
SMS_WSUS_SYNC_MANAGER 7/24/2014 8:00:01 AM
5652 (0x1614)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
7/24/2014 8:00:01 AM 5652 (0x1614)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 7/24/2014 8:00:01 AM
5652 (0x1614)
Sync failed: WSUS update source not found on site C01. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 7/24/2014 8:00:01 AM
5652 (0x1614)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=5652 GMTDATE=Thu Jul 24 00:00:01.280 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source
not found on site C01. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/24/2014 8:00:01 AM
5652 (0x1614)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
7/24/2014 8:00:01 AM 5652 (0x1614)
Setting sync alert to active state on site C01
SMS_WSUS_SYNC_MANAGER 7/24/2014 8:00:01 AM
5652 (0x1614)
Sync time: 0d00h00m00s SMS_WSUS_SYNC_MANAGER
7/24/2014 8:00:01 AM 5652 (0x1614)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
7/24/2014 9:00:01 AM 5652 (0x1614)
Starting Sync SMS_WSUS_SYNC_MANAGER
7/24/2014 9:00:01 AM 5652 (0x1614)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
7/24/2014 9:00:01 AM 5652 (0x1614)
Read SUPs from SCF for MYHQKUL990707S.sdb.com
SMS_WSUS_SYNC_MANAGER 7/24/2014 9:00:01 AM
5652 (0x1614)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
7/24/2014 9:00:01 AM 5652 (0x1614)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 7/24/2014 9:00:01 AM
5652 (0x1614)
Sync failed: WSUS update source not found on site C01. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 7/24/2014 9:00:01 AM
5652 (0x1614)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=5652 GMTDATE=Thu Jul 24 01:00:01.297 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source
not found on site C01. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/24/2014 9:00:01 AM
5652 (0x1614)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
7/24/2014 9:00:01 AM 5652 (0x1614)
Setting sync alert to active state on site C01
SMS_WSUS_SYNC_MANAGER 7/24/2014 9:00:01 AM
5652 (0x1614)
Sync time: 0d00h00m00s SMS_WSUS_SYNC_MANAGER
7/24/2014 9:00:01 AM 5652 (0x1614)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
7/24/2014 10:00:01 AM 5652 (0x1614)
Starting Sync SMS_WSUS_SYNC_MANAGER
7/24/2014 10:00:01 AM 5652 (0x1614)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
7/24/2014 10:00:01 AM 5652 (0x1614)
Read SUPs from SCF for MYHQKUL990707S.sdb.com
SMS_WSUS_SYNC_MANAGER 7/24/2014 10:00:01 AM
5652 (0x1614)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
7/24/2014 10:00:01 AM 5652 (0x1614)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 7/24/2014 10:00:01 AM
5652 (0x1614)
Sync failed: WSUS update source not found on site C01. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 7/24/2014 10:00:01 AM
5652 (0x1614)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=5652 GMTDATE=Thu Jul 24 02:00:01.529 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source
not found on site C01. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/24/2014 10:00:01 AM
5652 (0x1614)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
7/24/2014 10:00:01 AM 5652 (0x1614)
Setting sync alert to active state on site C01
SMS_WSUS_SYNC_MANAGER 7/24/2014 10:00:01 AM
5652 (0x1614)
Sync time: 0d00h00m00s SMS_WSUS_SYNC_MANAGER
7/24/2014 10:00:01 AM 5652 (0x1614)
WCM.log :
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 8:03:51 AM
8368 (0x20B0)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 8:03:51 AM
8368 (0x20B0)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=8368 GMTDATE=Thu Jul 24 00:03:51.926 2014 ISTR0="MYHQKUL990707S.sdb.com" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 8:03:51 AM
8368 (0x20B0)
Waiting for changes for 57 minutes SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 8:03:51 AM 8368 (0x20B0)
Wait timed out after 57 minutes while waiting for at least one trigger event.
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:18 AM
8368 (0x20B0)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Verify Upstream Server settings on the Active WSUS Server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:29 AM
8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:bb7bc3a7-857b-49d4-8879-b639cf5e8c3c (SQL Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:fdfe8200-9d98-44ba-a12a-772282bf60ef (Windows Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Starting WSUS category sync from upstream...
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:02:35 AM 8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:03:35 AM 8368 (0x20B0)
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:03:50 AM
8368 (0x20B0)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:03:50 AM
8368 (0x20B0)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=8368 GMTDATE=Thu Jul 24 01:03:50.438 2014 ISTR0="MYHQKUL990707S.sdb.com" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:03:50 AM
8368 (0x20B0)
Waiting for changes for 57 minutes SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:03:50 AM 8368 (0x20B0)
Wait timed out after 57 minutes while waiting for at least one trigger event.
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:18 AM
8368 (0x20B0)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Verify Upstream Server settings on the Active WSUS Server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:30 AM
8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:bb7bc3a7-857b-49d4-8879-b639cf5e8c3c (SQL Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:fdfe8200-9d98-44ba-a12a-772282bf60ef (Windows Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Starting WSUS category sync from upstream...
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:02:35 AM 8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:03:35 AM 8368 (0x20B0)
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:03:50 AM
8368 (0x20B0)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:03:50 AM
8368 (0x20B0)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=8368 GMTDATE=Thu Jul 24 02:03:50.710 2014 ISTR0="MYHQKUL990707S.sdb.com" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:03:50 AM
8368 (0x20B0)
Waiting for changes for 57 minutes SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:03:50 AM 8368 (0x20B0)
WSUSCTRL.log :
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 8:03:51 AM
8368 (0x20B0)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 8:03:51 AM
8368 (0x20B0)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=8368 GMTDATE=Thu Jul 24 00:03:51.926 2014 ISTR0="MYHQKUL990707S.sdb.com" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 8:03:51 AM
8368 (0x20B0)
Waiting for changes for 57 minutes SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 8:03:51 AM 8368 (0x20B0)
Wait timed out after 57 minutes while waiting for at least one trigger event.
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:18 AM
8368 (0x20B0)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Verify Upstream Server settings on the Active WSUS Server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:28 AM
8368 (0x20B0)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:29 AM
8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:bb7bc3a7-857b-49d4-8879-b639cf5e8c3c (SQL Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Category Product:fdfe8200-9d98-44ba-a12a-772282bf60ef (Windows Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
Starting WSUS category sync from upstream...
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:01:34 AM
8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:02:35 AM 8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:03:35 AM 8368 (0x20B0)
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:03:50 AM
8368 (0x20B0)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:03:50 AM
8368 (0x20B0)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=8368 GMTDATE=Thu Jul 24 01:03:50.438 2014 ISTR0="MYHQKUL990707S.sdb.com" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 9:03:50 AM
8368 (0x20B0)
Waiting for changes for 57 minutes SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 9:03:50 AM 8368 (0x20B0)
Wait timed out after 57 minutes while waiting for at least one trigger event.
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:18 AM
8368 (0x20B0)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Verify Upstream Server settings on the Active WSUS Server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:01:28 AM 8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:28 AM
8368 (0x20B0)
Successfully refreshed categories from WSUS server
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:30 AM
8368 (0x20B0)
Attempting connection to WSUS server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Successfully connected to server: MYHQKUL990707S.sdb.com, port: 8530, useSSL: False
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:bb7bc3a7-857b-49d4-8879-b639cf5e8c3c (SQL Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Category Product:fdfe8200-9d98-44ba-a12a-772282bf60ef (Windows Server 2008 R2) not found on WSUS
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
Starting WSUS category sync from upstream...
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:01:35 AM
8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:02:35 AM 8368 (0x20B0)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:03:35 AM 8368 (0x20B0)
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:03:50 AM
8368 (0x20B0)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:03:50 AM
8368 (0x20B0)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=9308 TID=8368 GMTDATE=Thu Jul 24 02:03:50.710 2014 ISTR0="MYHQKUL990707S.sdb.com" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 7/24/2014 10:03:50 AM
8368 (0x20B0)
Waiting for changes for 57 minutes SMS_WSUS_CONFIGURATION_MANAGER
7/24/2014 10:03:50 AM 8368 (0x20B0)
Any insights is much appreciated.
Thanks and best regards.

Hi,
According to the log, you got a HTTP 404 error, file not found.
Since it worked before, what has changed since then?
How many updates did you install after the last synchronization? Especially for update those applied to WSUS server itself.
As per the log, you are running WSUS 3.2, the update could be
KB2720211, KB2734608, KB2828185
And this thread provides good troubleshooting step though it WSUS without SCCM:
http://social.technet.microsoft.com/Forums/en-US/d0d65d6b-e1a7-4bc6-a139-b3bbaef6e78d/wsus-synchronization-failed-404-2012-server-help?forum=winserver

Similar Messages

SCCM 2012 SP1 - PowerShell command to create a software update group deployment DISABLED by default

Hello,
I create deployment jobs using new Powershell cmdlet "Start-CMSoftwareUpdateDeployment". However it looks there is no way with this cmdlet to create a job which is disabled by default.
Is it possible ? As an alternative, which cmdlet could I use to manage enable/disable job state ? I have not found anything so far.
Regards.
Sylvain

hi, i tried the solution to create a deployment using http://cm12sdk.net/?p=2014 link.
it creates deployment but it is not downloaded so a red cross sign is shown in front of software update group. can you guide me on which command to use to download software update after which we can try the script mentioned in the link.
thanks.

SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

Hi All,
Good day to all you.
I would like to seek all your help on this issue that i have encountering.
My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
Error:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
below are wsyncmgr.log:
Setting sync alert to active state on site C01 SMS_WSUS_SYNC_MANAGER (0x1690)
Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Starting Sync SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Read SUPs from SCF for MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
5776 (0x1690)
Synchronizing WSUS server MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
5776 (0x1690)
Using account sdb\SCCM-Admin to connect to WSUS Server
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Synchronizing WSUS server myhqkul990707s.sdb.com ...
SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
440 (0x01B8)
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
All response is much appreciated
Thank You

Hi,
I recommend you look at the IIS log. Maybe it can give us some clues.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Updates are not getting download after installation of SCCM 2012 SP1

I have installed SCCM 2012 SP1 step by step as per microsoft documents, Now I am getting error while downloading windows updates from microsoft site.
Error by WCM.log : System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport
connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Error By wsyncmgr: DB Server not detected for SUP XYZ.com from SCF File. skipping.
Sync failed: WSUS update source not found on site KSL. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=KSL-MUM-SCCM01.KSEC.KotakGroup.com SITE=KSL PID=3688 TID=4752 GMTDATE=Tue May 21 10:59:06.745 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS
update source not found on site KSL. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
I have reinstall my SUP on site server, i have my WSUS & site server is on same server. I have kept my sup setting as per requirment (8530 & 8531)
Kindly suggest is any other settings need to be done on server side.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
From your log snip-it, it looks like the firewall is causing your problem. Temporary turn off the firewall and see if that solves your problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 SP1 - SUP Error

Hi guys,
i upgraded my SCCM 2012 test Environment to SP1. I have only one Primary Site Server which holds all Roles. Everything seems to work fine except the SUP Role. If i try to synchronize the latest Updates it says that it cannot find a WSUS Server
and i should check WCM.LOG.
Within WCM.LOG i can find the following Messages:
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 08:56:44 3620 (0x0E24)
Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:07:56 3620 (0x0E24)
SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
SUP0: CM01.TEST.LOCAL, group = , nlb = SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Bad Configuration, SUPs present but no default SUP SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Default SUP not specified SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Setting new configuration state to 0 (WSUS_CONFIG_NONE) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Waiting for changes for 47 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
So in General this tells me that it can find a SUP but this one is not specified as a DEFAULT SUP. How can i tell SCCM that this is my Default SUP? (I only have this one and it is configured to sync from Microsoft Update site). I have never seen
this before so i guess this is related to SP1?
PS: I also installed the 2 necessary WSUS Updates before i upgraded to SCCM SP1.
Thanks in lot in advance.
Stefan

None of your solutions apply to WSUS 4.0 on Server 2012
None of the specified patches applies or will run on a Windows 2012 Std server. They either report that WSUS 3 SP 2 isn't installed OR that the patch isn't applicable to the server version installed.
Here is a excerpt of MY WCM.LOG
I have a fully patched Windows 2012 Standard Server, Fully updated SCCM 2012 SP1 installed, and am connected to a fully patched SQL2012 Server on another fully patched Windows 2012 Std server.
Ports 8530 and 8531 designated on both the WSUS 4.0 Role and SCCM 2012 SP1 system (both are on same server)
SUP0: SCCM2012.xxdomainname.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

WSUS 4.0 and SCCM 2012 SP1 Sync Errors

SCCM 2012 SP1 is installed on a Windows 2012 Std server with the WSUS 4.0 Role installed.
All other links I have found list a 2008 R2 Server with WSUS 3.0 SP2 hence all the "fixes" revolve around hot fixes and patches/settings for WSUS 3.0 or 2008 R2 systems.
WSUS is set for port 8530/8531
SCCM SUP is set for ports 8530/8531
Both are on same machine (single site SCCM 2012 SP1 System)
What does Bad Configuration, SUPs present but no default SUP
mean and how do I fix it?
Recent entry in my WCM.LOG states:
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.401+420><thread=6052 (0x17A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.454+420><thread=6052 (0x17A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.481+420><thread=6052 (0x17A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.489+420><thread=6052 (0x17A4)>
SUP0: SCCM2012.xxdomainnamexx.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

Here is my WCM Log from this mornings "re-attempt"
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:22.156+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.179+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.181+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.194+420><thread=5540 (0x15A4)>
No SUPs are present $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.199+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.220+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.224+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.226+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:37.356+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.388+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.493+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.541+420><thread=5540 (0x15A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.543+420><thread=5540 (0x15A4)>
SUP0: SCCM2012.MORTONGENERAL.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.546+420><thread=5540 (0x15A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.550+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.553+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.559+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.562+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.593+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.596+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.611+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.614+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.617+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.620+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.634+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.637+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.640+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.761+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.798+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.813+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.823+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.826+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.840+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.843+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.846+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.849+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.863+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.866+420><thread=5540 (0x15A4)>
Wait timed out after 23 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:30.913+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.917+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.920+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.923+420><thread=5540 (0x15A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:31.041+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.045+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.048+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.051+420><thread=5540 (0x15A4)>
Randall

SCCM 2012 SP1 errors when downloading updates

Currently using SCCM 2012 SP1 with CU2 and I am having some update download issue with Automatic Deployment Rules.
The Environment is:
Server 2008 R2
SCCM 2012 SP1 CU2 (Upgraded from SCCM 2012 CU2)
I created an Automatic Deployment Rule for Adobe Flash. Since I was having the same issue with Adobe Reader, when I published via SCUP to WSUS I chose not to sign the updates.
After publishing to WSUS I then sync SCCM, I see the updates and then in the ADR I had it download the updates and I see this error:
Authentication of file C:\Windows\TEMP\CABDEC5.tmp failed, error 0x800b0004 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 3712 (0x0E80)
ERROR: DownloadContentFiles() failed with hr=0x80073633 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download the update from internet. Error = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download ContentID 16845337 for UpdateID 16841530. Error code = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Now the funny thing is if I go to the update itself within update group that Flash is a member I can right click it and choose download and the error doesn't occur.
I observed that the UNC path for ADR Adobe flash, when the rule is ran, is populated with folders that have a name something like 44738297895427890.1 or 423154325378u867234789.1. I have come to realize that those are failed downloads. So for the
heck of it I then right clicked the update itself and chose download and it downloaded without issue. Now I'm guessing that when I chose to download directly from the update maybe the system is getting the update from adobe and not from wherever the rule was
trying to get it from. I then see the .1 removed from the directory name and there are updates within them.
Just for clarity here are the steps I go through from SCUP to Syncing...
Log in to WSUS server
Run SCUP as administrator
Get notified there are updates from Adobe and let SCUP download updates
Find the updates the specify the following publishing options
Full Content
Sign all software updates with a new publishing certificate .... (Is this necessary by the way?)
Then click Next
After that's done I then go to SCCM Manager Console and go to Software Updates and right click to Synchronize them.
After that's done then I run the ADR for Adobe Flash and when it goes to download the updates that's when the error occurs.
What am I missing?
Also, while I wait for help I just recently added the WSUS SCUP certificate to the SCCM server to see if by chance that fixes stuff. If it does then I'll post the results of adding the certificate to the SCCM server.
One other thing, is there a way to delete updates? When I was having this issue in the past, I went in to SCUP I marked the updates as expired and then deleted the updates. Went to SCCM and synchronized the updates and they went from not expired to expired
then I waited, maybe 30 days or so before I could add the updates back in.
Thanks for the help!

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Have you seen the note at the bottom of this page about this error?
http://technet.microsoft.com/en-us/library/bb932193.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Management Point fails after installing SCCM 2012 SP1

I'm carrying out an install of SCCM 2012 SP1 with the following hardware (fresh install not an upgrade from 2007)
1. Newly built Windows Server 2012 box
2. Site database located on a remote SQL 2012 cluster, both nodes Windows Server 2012, with CU5
The install went fine but when checking the Site Server Components the Management Point isn't installing. The following both show errors;
SMS_MP_CONTROL_MANAGER - MP.msi could not install. Checked the MP.msi log file which shows the following errors;
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_Global.mof' (Phase: 3, Object: 5, Lines: 76 - 83, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\PolicyDefaults.mof' (Phase: 3, Object: 4, Lines: 49 - 57, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\StateMsgSchema.mof' (Phase: 3, Object: 6, Lines: 89 - 94, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\DataTransferService.mof' (Phase: 3, Object: 5, Lines: 318 - 323, Error: 80041002)
[19:53:19] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_MP.mof' (Phase: 3, Object: 1, Lines: 31 - 36, Error: 80041002)
MSI (s) (0C!94) [19:53:20:862]: Product: ConfigMgr Management Point -- Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
SMS_NOTIFICATION_SERVER - bgbisapi.msi could not install. Extract from log below;
[19:53:38] IGNORE: Failed to delete extension 'C:\Program Files\SMS_CCM\bgbisapi.dll'. Return Code = 0x80020009 (The extension might not be registered)
[19:53:39] WARNING: Failed to remove PerfLib entries for performance application SmsBgb (2)
[19:53:39] WARNING: Failed to remove configuration for performance application SmsBgb (80070057)
MSI (s) (0C!80) [19:53:39:540]: Product: BGB http proxy -- Internal Error 25001. 80070057
Internal Error 25001. 80070057
CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I've tried uninstalling MP and reinstalling, triple checked all the right pre-reqs in Roles and Features are enabled, even rebuilt the server from scratch and tried again but same result.
Would really appreciate some help if anyone's fixed this issue

I'm still struggling, I've uninstalled MP
<04/16/14 08:06:59> SMSMP Setup Started....
<04/16/14 08:06:59> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /deinstall /siteserver:EICSC001 SMSMP 0
<04/16/14 08:06:59> Deinstalling the SMSMP
<04/16/14 08:06:59> No versions of SMSMP are installed. Returning Success.
<04/16/14 08:06:59> ~RoleSetup().
Ran the command, Invoke-Command {gwmi -query "SELECT * FROM __Namespace WHERE Name='CCM'" -Namespace "root" | Remove-WmiObject}
Checked Namespace Instances to ensure '= ccm' is not longer there.
Rebooted Server and re-installed MP but it still fails
<04/16/14 08:37:26> ====================================================================
<04/16/14 08:37:26> SMSMP Setup Started....
<04/16/14 08:37:26> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:EICSC001 SMSMP 0
<04/16/14 08:37:26> Installing Pre Reqs for SMSMP
<04/16/14 08:37:26> ======== Installing Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Found 2 Pre Reqs for Role SMSMP
<04/16/14 08:37:26> Pre Req MSXML60 found.
<04/16/14 08:37:26> No versions of MSXML60 are installed. Would install new MSXML60.
<04/16/14 08:37:26> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<04/16/14 08:37:26> msxml6_x64.msi exited with return code: 0
<04/16/14 08:37:26> msxml6_x64.msi Installation was successful.
<04/16/14 08:37:26> Pre Req SqlNativeClient found.
<04/16/14 08:37:26> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<04/16/14 08:37:26> Pre Req SqlNativeClient is already installed. Skipping it.
<04/16/14 08:37:26> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Installing the SMSMP
<04/16/14 08:37:26> Passed OS version check.
<04/16/14 08:37:26> IIS Service is installed.
<04/16/14 08:37:26> No versions of SMSMP are installed. Installing new SMSMP.
<04/16/14 08:37:26> Enabling MSI logging. mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE
SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<04/16/14 08:37:26> mp.msi exited with return code: 1603
<04/16/14 08:37:26> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<04/16/14 08:37:26> Fatal MSI Error - mp.msi could not be installed.
<04/16/14 08:37:26> ~RoleSetup().
On checking I don't seem to have anything in IIS, no default web site.
I've tried reinstalling IIS and reinstalling SCCM 2012 but what ever I do I still hit the same issue with the Management Point.
Any assistance would be greatly appreciated.
Thanks

SCCM 2012 SP1 - OS Deployment - hash could not be matched for the downloded content

I've got a newly deployed SCCM 2012 SP1 running on Windows Server 2012. The W2K12 runs as vm on ESX 5.1. I'm having very odd issues with OS deployment. The TS keeps failing when processing SCCM client installation - it downloads the package but then it fails
straight away with the 80091007 - hash values couldn't be matched error - some extract from smsts.log attached below. It's very consistent, it happens every time - it downloads and applies the image fine straight after that it bombs out.
What is very interesting is that it works perfectly fine when I deploy vms (on the same or different host) - the issue seems to be be only affecting physical machines (laptops desktops). This might suggest some network issues (vSwitch with Cisco switches) but
the config on the switch is very simple and this shouldn't be the case.
I had a few virtualised SCCM 2007 installations (ESX 5 and 4) and it always worked with no problems.
I tried to recreate the package (changing source directory), turn binary differential replication on and off, copy the content of the package to the dist point or not copy. Push client installation (or other package deployments) work fine
When I tried to deploy with no download - sometimes it works but most of the time I'd get the files/folder corrupt error (can't remember the No)
This is starting to drive me crazy - There are some significant changes in the way SCCM 2012 is validating package integrity (like Content Lib folder) but the consistency of this problem is just very odd.
Anyone has any clues?
thanks
- Downloaded file from http://GTKVMGMT05.GTK.LOC...m?/x64/wic_x64_enu.exe to C:\_SMSTaskSequence\Packages\GTK0000C\x64/wic_x64_enu.exe
- Download done setting progress bar to 100
VerifyContentHash: Hash algorithm is 32780
c:\_smstasksequence\packages\GTK0000c\i386 is a directory. Setting directory security
c:\_smstasksequence\packages\GTK0000c\x64 is a directory. Setting directory security
- Hash could not be matched for the downloded content. Original ContentHash = 5EF3A189C48F3469440A83026EC8ECD36EAD6EAF3B5D35663F8201BDE175413C, Downloaded ContentHash = FA4516EDD2D7907F8FA472A3E1B717DF2DD4A0976CD4CEAE11045EE62EC8C661
0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2999)
- DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3106)
- DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3331)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3221)
TS::Utility::ResolveSource(sClientPackageID, sClientPackagePath), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,1655)
- Failed to resolve package source "GTK0000C"
- Exiting ConfigureEx: 0x80091007
- BaseSetupHook::configure(sWindowsDir), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\osdsetuphook.cpp,292)
- Failed to configure OSD setup hook (0x80091007)
- Failed to configure OSD setup hook (0x80091007)

is this the only indication of a problem in your smsts.log file ? did you apply the
authenticode hotfix or have you
downloaded the SP1 media after that hotfix was applied ?
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

Reporting services keep failing on SCCM 2012 SP1

I have SCCM 2012 SP1 install with SSRS 2012 install on same server 2008 R2 server.
Reporting services keep failing with the following message when trying to START the service from the Reporting Services Configuration Manager Console
System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
Thx,
Joe
Thx, Joe

Good advice Garth, but I have opened over 5 cases to try to resolve this and several other issues with my troublesome SCOM 2012 SP1 upgrade. That is why I am also sending it to the community in hope they can provide assistance.
CSS will only work on one specific issue and in most cases these are targeted bandaid fixes that DO NOT address the underlying or related issues. I a left to opening many tickets and still floundering with a unreliable product.
It seems to only be with System Center. All other products by Microsoft seem to be reliable and predicable and are easily supported using break fix support model of the current MS teams.
It is SQL (SSRS) that controls subscriptions not CM12. CM12 only leverages the APIs provided by SQL (SSRS).
I hate to say this but Why do you think this problem has anything to do with CM12?
If CSS tell you to re-create the subscription and the problem re-occurs then I would re-open the ticket and tell them that the problem is NOT fixed and to continue working on it.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Prestaged OSD using SCCM 2012 SP1 windows Partition variable is not being set

Hello All I need some assistance with a workaround.
I am using a presaged task sequence created from a working network / PXE deployment TS for windows 7.
This TS sets a variable for the OS partition called "Windows" and the value is set in the Partition Disk task.
Problem is this value is not being read from a prestaged due to the OEMMedia condition skipping this partition and format task.
Question is how do I get it to read and or set the value for that partition?
From what I have found on Google this was an issue in beta of MDT but was fixed in RTM. I am not using MDT TS but I do have it installed. Any idea if this is a known issue with SCCM 2012 sp1 TS?
Edit: also noticed that the variable's case is different and will not let me change it.
Variable under format is "windows" variable under Apply OS is "Windows" when I change them to be the same then close and reopen they revert back to the above. Are these variables case sensitive?
Edit: for now I have changed it from variable to next available partition. I tested it twice so far it seems to be using the correct partition and it remains to be called the C drive. For now this will be my solution.

When you say "presaged task sequence created from a working network / PXE deployment TS" are you saying this is still a network boot process? Or have you done "Create Task Sequence Media"?
Dustin Estes - MCP
yes when i say prestaged that is using the create task sequence media then selecting prestaged.

SCCM 2012 SP1 to SCCM 2012 R2 - Side by Side

Hi Friends,
Currently our SCCM infrastructure is running with a CAS site, 2 Primary Sites and 8 Secondary sites with SCCM 2012 SP1. Now we want to update this infrastructure from SCCM 2012 SP1 to 2012 R2. But we want remove CAS site and to keep only single Primary Site.
Can this be done in Side by Side migration from SCCM 2012 SP1 to SCCM 2012 R2 ? If yes then please suggest how to migrate all data (Packages/Clients) from SCCM 2012 SP1 to new infra on SCCM 2012 R2.
Thanks in advance.

You don't have many (supported) options here. Detaching a site is not possible, so indeed your only option left is to migrate. Problem here is that the supported scenario is from a ConfigMgr 2012 R2 site to a ConfigMgr 2012 R2 site (see:
http://technet.microsoft.com/en-us/library/gg682006.aspx). That means you should first upgrade your old environment before you can start with your migration.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2012 SP1 - Build and Capture - ReCapture impossible

Hi all
i upgrade my SCCM 2012 RTM to SCCM 2012 SP1 yesterday. Today i started a recapture of my Windows 7 and Windows 2008 R2 Base Image.
For that i have 2 VMs located in different SCCM Collections. And a Build and Capture Task Sequence is deployed to the collections.
Before SP1 the behavior was:
- Reset Required PXE Deployment in SCCM for the VMs
- Start VM
- VM boots with PXE
- VM installs and capture the Installation
And that i could do all the time so often as i want.
Now with SP1 it is the same procedure but just for one time. After one success Build and Capture Task, the vm is unable to do the task sequence again. The VM is booting into the PXE and then i can see in the smsts log:
There are no task sequences available to this computer
But there are. The Task Sequence is set to "Always rerun".
The only "fix" is to completely recreate the computer item in sccm.
What is here wrong? Is this a known bug?
best
JBAB

Hi, your problem is that when you deploy the task over the collation you only specified "media and PXE" was available to and probably the machines that you try to capture already had the sccm client. You can try to deploy the sequence task to a collation
including the the option "configuration manager, media and PXE", or you can also deploy the task sequence to de "unknown devices" collation and delete the objects of the two virtual machines in configuration manager

CCMSETUP not updating on SCCM 2012 SP1 CU3/CU4 primary site

I have a SCCM 2012 SP1 CU3 primary site and i can't upgrade the local installed SCCM Client.
The error I get in ccmsetup.log is:
<![LOG[MSI: Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002]LOG]!><time="15:44:22.408-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:300">
<![LOG[MSI: Action 15:44:22: Rollback. Rolling back action:]LOG]!><time="15:44:22.562-60" date="02-08-2014" component="ccmsetup" context="" type="0" thread="2496" file="msiutil.cpp:314">
<![LOG[File C:\windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterHostingConfiguration.
ErrorMessages:
Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002
]LOG]!><time="15:45:00.798-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:872">
<![LOG[Client installation has failed too many times. Ccmsetup will now abort.]LOG]!><time="15:45:00.830-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7941">
<![LOG[Successfully deleted the ccmsetup service]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2496" file="ccmsetup.cpp:3320">
<![LOG[InstallFromManifest failed 0x80070643]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7086">
<![LOG[CcmSetup failed with error code 0x80070643]LOG]!><time="15:45:05.832-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2324" file="ccmsetup.cpp:10544">
I have this on my primary and secondary servers as well.
Is upgrading to R2 recommended and will that solve this issue ?
When googling to this issue i found that there is a solution for this: remove MP, upgrade Client, install MP.
But this is my primary and secondary and on secondary i am not allowed to remove the MP. It is hardcoded enabled.

Try the following steps to specify the hotfix when installing the client.
1. Open an elevated command prompt.
2. Run a command line similar to the following – if CU3 has already been installed, the MSP file below should be on the site server, in the
\\servername\SMS_SITE\Client\hotfix folder:
\ccmsetup.exe PATCH=\Configmgr2012ac-sp1-kb2882125-x64.msp
Juke Chou
TechNet Community Support

SCCM 2012 SP1 CAS - Unable to sync to Microsoft Updates Sites

Similar Messages

Maybe you are looking for