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.

Similar Messages

SCCM 2012 SP1 + WSUS + Server 2012 + SQL Server 2012

Hi all;
I installed SCCM 2012 with Sp1 for my site server and everything is going well.. And than i installed the WSUS role on my Windows Server 2012 and SCCM 2012 SP1 it gave an error message which is "Fatal Error: The schema version of the database is from a newer
version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database." My database server is SQL Server 2012... Do you know any pathc for WSUS or SQL Server 2012 doesnt support WSUS yet???
Thank You...
MCT

Normally if you are going to install SCCM 2012 SP1 +Windows 2012 with SQL 2012, Then you better use the SQL 2012 sp1.
also when you are installing the WSUS version 6.2 which come with server 2012 make sure you leave the default settings as it is. it shows in the below article.
also when you are giving the path to save the WSUS contents make sure the drive you going to create the wsus folder and the place where you going to download the updates is having free disk space and its formatted with the NTFS volume. Also the service account
you are using for this configuration should have the admin rights to the location of the wsus folder you going to create,
Thanks
Hasitha

SCCM 2012 - Determine if software update requires a reboot

Using the Configuration Manager console is there a way to determine if a software update requires a reboot?

you can create a compliance item like this -
http://blog.coretech.dk/kea/dealing-with-reboot-pending-clients-in-configuration-manager-2012/ It will give you information if a reboot is requested by ConfigMgr. For all reboots, you should also look at registry.
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

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

SCCM 2012 and WSUS

I know this horse has been beat, and is probably just dust now but I am still having a problem. I am not sure what to do next. I see others have had this problem but their resolutions have not worked.
Site Config:
OS - Windows Server 2012 Datacenter
SQL - SQL Server 2012 Enterprise SP1
SCCM - SCCM 2012 SP1
WSUS : Database and WSUS Services
I have done the setup in the Server Manager window and can open the console. Below are the errors I am getting.
From SMS_WSUS_SYNC_MANAGER
WSUS Synchronization failed.
Message: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details..
From SMS_WSUS_CONFIGURATION_MANAGER
WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "SERVER".
Error in WCM.log
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
Error in wsyncmgr.log
Sync failed: WSUS update source not found on site CM1. 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=SERVER SITE=CM1 PID=1548 TID=1740 GMTDATE=Fri Sep 13 19:08:50.063 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on
site CM1. 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

Re-set the WSUS and SUP roles according to your doco, which is nice by the way, but I am still getting errors in WCM.
Assembly WSUSMSP loaded in .NET runtime v4.0.30319.17929 SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
Successfully configured WSUS Server settings and Upstream Server to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Set DBServerName property in SCF to 'VRC1SCCMPRIP01' on this site for <SERVER.DOMAIN>. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (<SERVER.DOMAIN>) is submitting SDK changes from site(CM1) SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:18e5ea77-e3d1-43b6-a0a8-fa3dbcd42e93 (Windows 8.1 Dynamic Update) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:3e5cc385-f312-4fff-bd5e-b88dcf29b476 (Windows 8 Language Interface Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:5312e4f1-6372-442d-aeb2-15f2132c9bd7 (Windows Internet Explorer 8 Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:6407468e-edc7-4ecd-8c32-521f64cee65e (Windows 8.1) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:97c4cee8-b2ae-4c43-a5ee-08367dab8796 (Windows 8 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:f4b9c883-f4db-4fb5-b204-3343c11fa021 (Windows Embedded Standard 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:37:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:38:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:39:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:22 PM 5108 (0x13F4)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
From SUPSetup.log
<09/17/13 13:36:13> ====================================================================
<09/17/13 13:36:13> SMSWSUS Setup Started....
<09/17/13 13:36:13> Parameters: I:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:<SERVER.DOMAIN> SMSWSUS 0
<09/17/13 13:36:13> Installing Pre Reqs for SMSWSUS
<09/17/13 13:36:13> ======== Installing Pre Reqs for Role SMSWSUS ========
<09/17/13 13:36:13> Found 1 Pre Reqs for Role SMSWSUS
<09/17/13 13:36:13> Pre Req SqlNativeClient found.
<09/17/13 13:36:13> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<09/17/13 13:36:13> Pre Req SqlNativeClient is already installed. Skipping it.
<09/17/13 13:36:13> ======== Completed Installation of Pre Reqs for Role SMSWSUS ========
<09/17/13 13:36:13> Installing the SMSWSUS
<09/17/13 13:36:13> Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
<09/17/13 13:36:13> Checking runtime v2.0.50727...
<09/17/13 13:36:13> Did not find supported version of assembly Microsoft.UpdateServices.Administration.
<09/17/13 13:36:13> Checking runtime v4.0.30319...
<09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
<09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
<09/17/13 13:36:13> Supported WSUS version found
<09/17/13 13:36:13> Supported WSUS Server version (6.2.9200.16384) is installed.
<09/17/13 13:36:13> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
<09/17/13 13:36:13> CTool::RegisterManagedBinary: Registered I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll successfully
<09/17/13 13:36:13> Registered DLL I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll
<09/17/13 13:36:13> Installation was successful.
<09/17/13 13:36:13> ~RoleSetup().
Second to last line shows completion.

Alert: Synchronization failure alert for software update point ( SCCM 2012 R2)

SCCM 2012 R2
Alert: Synchronization failure alert for software update point: MY.net(MY)
Alert type: Software update synchronization failure
Severity: Critical
Active time (UTC): 13-09-2014 19:37:34
Condition: Generate an alert if software updates synchronization fails for the Software Update Point role at the
MY (MY) site.
Alert Text: Software updates synchronization for the Software Update Point role at the
MY (MY)) site failed.
Please let me know what will be the cause of this Alert, how to resolve it

The reason is stated in the message: "Generate an alert if software updates synchronization fails
for the Software Update Point role at theMY (MY) site"
Examine wsyncmgr.log
Torsten Meringer | http://www.mssccmfaq.de

How to remove the parent-child software update point in sccm 2012 sp1

I have a CAS , Primary site server(1) and secondary site servers (7). I have software update point installed on CAS, Primary server and Secondary site servers as well.
I have a situation to reinstall the software update point which is in primary site server.
So, How to reinstall the software update point in primary site server since this is located in the middle between CAS and secondary site servers.
So, please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
I have referred few posts on how to remove SUP
https://social.technet.microsoft.com/Forums/en-US/c7258aad-d968-427b-8826-4829916c14c9/remove-and-re-add-software-update-point-sccm-2012?forum=configmanagersdk
and how to install SUP
http://www.windows-noob.com/forums/index.php?/topic/4467-using-sccm-2012-in-a-lab-part-6-deploying-software-updates/

Hi,
>> please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
I just tried to reinstall the SUP on the Primary site(only one SUP on Primary site and there is a SUP on Secondary site). The SUP upstream data source of the Secondary site showed empty and greyed out. But the upstream data source resumed after a while.
It seems nothing special needs to be done.
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCCM 2012: configure software update point

Hi,
I installed WSUS, installed the software update point on Windows 2012 (for SCCM 2012) with following commands:
Install-WindowsFeature -Name UpdateServices -IncludeManagementTools
cd 'C:\Program Files\Update Services\Tools\'
.\wsusutil.exe postinstall CONTENT_DIR=E:\WSUS
Add-CMSoftwareUpdatePoint -SiteCode "PRD" -SiteSystemServerName "CM01.contoso.com" -ClientConnectionType Intranet -WsusiisPort 8530 -WsusiissslPort 8531
Now I'm stuck. How do I configure the specific update (f.e. Windows 2012, forefront etc), download them to a certain folder?
Please advise.
J.
Jan Hoedt

It really isn't practical (or possible) to try to do an entire ConfigMgr implementation using PowerShell. I don't believe that you can choose your products using PoSH.
You will find a full list of cmdlets here
http://technet.microsoft.com/en-us/library/jj821831(v=sc.20).aspx
The following cmdlets are available to configure your software update infrastructure but I'm pretty sure none of them will help you with this.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Use SCCM as a standard WSUS server as well as a Software Update point?

Is it possible to use SCCM as a standard WSUS server as well as a Software Update point? I have 2 scenarios:
1) create software update packages and deploy them via software update groups in Configuration Manager
2) configure a group policy to set internal WSUS server to the SCCM server with SUP role, and allow servers to pull updates
- Is this technically possible?
- Do I need to pre-download the updates that i want delivered via method (2) above ?
I am running Systems Center Configuration Manager 2012 R2 with SUP installed.

100% agree with Jason. Sounds like a idea full of hassle and I'd imagine weirdness could creep in. I'd use ConfigMgr to patch the servers for the advanced reporting alone.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

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

SCCM 2012 R2 - Software Update Point

I have two domains, one where the site server (SCCM) will be installed home office, and then another untrusted domain Management. This server will have site roles, SUP, and some others.
I want to create a site system server with DP, MP in the untrusted domain. In order to push out updates to clients in the untrusted domain, what do I need, in the untrusted domain, to make this work.

Hi,
For the SUP in the untrusted domain the SCCM Site Server you need the proper patch level of the installed WSUS, the correct ports open on Firewall and an account from the Domain where the SCCM Site is installed which has rights on the WSUS on the primary
site. This account has to be configured during the installation of the SUP on the Site System Server.
May this post also give you some hints:
http://social.technet.microsoft.com/Forums/en-US/c3fbf3ab-ca70-48da-90b1-e7322783140c/sup-in-untrusted-forest-using-sccm-2012-sp1?forum=configmanagerdeployment
Cheers
Christoph
PS: Could somebody please move this thread to the correct Configuration Manager Forum :)

Software Update error - SCCM 2012 SP1

HI,
I have SCCM 2012 SP1 installed on Windows server 2008 R2 server. I have configured SUP role and tried sync from sccm console. I get the below error.
LOg:
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:11:42.047+00><thread=3840 (0xF00)>
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:12:42.255+00><thread=3840 (0xF00)>
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssCommunicationError: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning() $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.462+00><thread=3840
(0xF00)>
Done using DEVSWAD\SWDTR-SRV-CMPATCH credentials~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
Failed to set Subscriptions on the WSUS
. Error:(-2146233088)Unknown error 0x80131500~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=3840 GMTDATE=Thu Jan 30 14:13:12.479 2014
I have configured proper proxy account which can connect to microsoft website and the port i have configured in proxy to allow is
80 and 443. I feel the port i need to allow may be i am not sure 8530 and 8531. Or 80 and 443 is fine. Please help
Regards, Pratap

It says to check WCM.log which i posted above
wsync log:
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.118+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 14:02:14.119 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please
refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.123+00><thread=4388 (0x1124)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.132+00><thread=4388 (0x1124)>
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:14.495+00><thread=4388 (0x1124)>
Starting Sync $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.157+00><thread=4388 (0x1124)>
Performing sync on retry schedule $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.163+00><thread=4388 (0x1124)>
Read SUPs from SCF for DCMPSTPV01.devswad.net $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.577+00><thread=4388 (0x1124)>
Found 1 SUPs $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.830+00><thread=4388 (0x1124)>
Found active SUP DCMPSTPV01.devswad.net from SCF File.~ $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.833+00><thread=4388 (0x1124)>
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.876+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 15:02:15.882 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please refer
to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.892+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.912+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.915+00><thread=4388 (0x1124)>
Sync time: 0d00h00m01s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.024+00><thread=4388 (0x1124)>
Next scheduled sync is a retry sync at 31/01/2014 16:02:15 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.151+00><thread=4388 (0x1124)>
Regards, Pratap

Software Update Point doesn't show Win 2012 R2 and Windows 8.1 updates

I started deploying Windows 2012 R2 Datacenter servers and some Windows 8.1 workstations. I wanted to make sure that my Software Update Point was downloading updates available to those OS's and after going in to Administration -> Overview -> Site Configuration
-> Sites -> Configure Site Components -> Software Update Point, I notice that those OS's weren't available to select.
I then did some searches on the web and thought my problem was two fold:
1 - I was using SCCM 2012 SP1.
2 - My SCCM 2012 Software Update Point was on a Win 2008 R2 server
So the first thing I did was upgrade from SCCM 2012 SP1 to SCCM 2012 R2. I then created a Windows 2012 R2 Datacenter server and installed WSUS on it. I then added the server as a Site System Server, added the Software Update Point to it and configured it.
Unfortunately, this still didn't help me as you can see from the screen shots below:
What am I doing wrong and what needs to be done to have all the updated Operating Systems and Microsoft Software added to my Product list?
Thanks... Frank

To follow on to narcoticoo's statement, have you actually initiated a catalog sync from within the ConfigMgr console yet? If so, has it completed successfully (you can check the moniotring workspace or you can watch the wsyncmgr.log).
Jason | http://blog.configmgrftw.com
Jason...
I just ran a Synchronize Software Updates from ConfigMgr Console. I then went Monitoring -> Software Update Point Sync Status. It's showing my new WSUS server ( 2012 R2 ) but it's not showing any updates are being sync'd through it. See this screen shot:
I then went to the wsyncmgr.log file on my site server which is the OLD WSUS server ( Win 2008 R2 ) and say this:
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=PREP-SCCM12.<domain.org> SITE=STA PID=5224 TID=4028 GMTDATE=Wed Feb 26 19:00:40.236 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site STA. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.236+300><thread=4028 (0xFBC)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.279+300><thread=4028 (0xFBC)>
Setting sync alert to active state on site STA $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.313+300><thread=4028 (0xFBC)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:40.360+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win 7 Updates up to Aug 2012\0048da55-f46f-4452-b4c1-37c0f295333b\IE9-langpack-Windows7-x86-xho.exe, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.042+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win 7 Updates up to Aug 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.067+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win2k8 Updates Until Aug 2012\000f8a0a-825c-457b-a15b-57ade145a09b\windows6.0-kb2653956-x64.cab, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.119+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win2k8 Updates Until Aug 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.144+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\Win 7 Updates for Sept 2012\10f3ec1c-f096-4a82-ae41-440ba5328467\Windows6.1-RTM-Client-NEUTRAL-X86.EXE, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.173+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\Win 7 Updates for Sept 2012, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.199+300><thread=4028 (0xFBC)>
Deleting file \\?\UNC\prep-dpsccm12\WSUS Updates\XP Updates Until Sept 30\17165524-99fa-49f7-91e6-457d43d4a48e\Windows-KB890830-V4.12.exe, FAILED, Win32 Error = 5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.228+300><thread=4028 (0xFBC)>
Failed to delete orphaned content folder \\prep-dpsccm12\WSUS Updates\XP Updates Until Sept 30, error 0x5 $$<SMS_WSUS_SYNC_MANAGER><02-26-2014 14:00:41.254+300><thread=4028 (0xFBC)>
It appears to me that when doing a Sync, it's still trying to use my OLD WSUS server instead of my new one. I removed the Software Update Point from the OLD WSUS server and uninstalled WSUS from it. I'm not sure why it's still trying to sync from the old
server rather than the new one. Any ideas?
Thanks... Frank

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

SCCM 2012R2 Software Update Point (Old Programs List olny)

hi,
i have sccm 2012R2, today i add to sccm software update point role but there in Products page not showilng latest microsoft products such as Office 2013, Exchange 2013, Windows Server 2012R2,Windows 8.1,
there is only old programs,eg. office 2010, server 2012 (not R2)
i update sccm to latest cumulative update 4 but no change in there,
i need to update client computers, there are all Windows 8.1 systems.
how can i update cients from sccm?
picture link:
https://www.imageupload.co.uk/image/ZZww

This list comes from WSUS which in its default, newly installed state is out of date. The list is however updated every time that WSUS in synced and the catalog is updated in ConfigMgr. Thus, you simple need to initiate an update catalog sync from within
the ConfigMgr console by going to the Software Updates -> All Software Updates node and choosing Synchronize Software Updates from the ribbon bar or right-click context menu.
Jason | http://blog.configmgrftw.com | @jasonsandys

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

Similar Messages

Maybe you are looking for