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

Similar Messages

  • 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

  • SCCM 2012 SP1 with remote WSUS on Server 2012 and SQL Server 2012

    I am rebuilding my SCCM 2012 lab on Server 2012 R2 x64 OS now.
    I have 1 primary site, remote SQL server 2012, and remote WSUS server.
    Is the WSUS console still required on my primary site running server 2012? If so are the below the correct steps to get this working?
    Install Console on primary server:
    Go to Server Manager à Add Roles and features, Navigate to the features section.
    Remote Server Manager tools
    >Role Administration Tools
    --Select Windows Server Update Services Tools Only
    Are there any post hotfixes to install?
    Intalling WSUS full version on remote server:
    Go to Server Manager à Add Roles and features, Server Roles section.
    Windows Server Update Services
    Do I need to select this as well on the remote wsus server? >Role Administration Tools -Select Windows Server Update Services Tools Only
    Since my SQL server is on a remote server do I select the below only?
    Are there any post hotfixes to install?

    Hi,
    One Part of the question is already answered. The second part is: If you want to use a remote SQL Server you need to select exactly what you selected in your screenshot.
    Regards,
    Thomas
    Thomas Hanrath [MCT | Regional Lead Germany] |
    http://www.hanrath.de
    Microsoft Learning Blog |
    http://blog.microsoftlearning.de

  • Sync failed: WSUS update source not found on site 786. Please refer to WCM.log for configuration error details.

    Hi,
    I have installed SC 2012 SP1 + SQL Server 2012 CU2e
    I followed the following guide:
    http://www.windows-noob.com/forums/index.php?/topic/4427-using-sccm-2012-rc-in-a-lab-part-2-add-sup-and-wds/
    And when Sync Failed, what could be went wrong?
    I have copied the logs+screenshot, and would be thankful if someone can give expert advise.
    Here is link :  http://sdrv.ms/13kmHBQ
    N.A.Malik

    Hi,
    I haven't tested myself but going to test the following:
    WSUS is bit cranky for now but here is what I did to fix it:
    1) Uninstall SUP role
    2. Uninstall WSUS
    4. Delete SUSDB from SQL Server if any
    5. Restart Server
    6. Install WSUS (Chose to install DB not WID)
    7. Configured Updates to be stored locally
    8. Run Post Deployment Configuration from Server manager
    9. Started WSUS Admin Console and ran Wizard (also chose to connect for the catalog sync) up to the Point where you select the products. Here I canceled the wizard without choosing any products
    10. Install SUP role in SCCM and configure the right Settings (WSUS on Server 2012 Defaults to its own admin Website and ports 8530 and 8531) and select the products you required.
    11. Check following log file if WSUS does not sync with SCCM.
    Path: C:\Program Files\Microsoft Configuration Manager\Logs
    File Name:
    WCM.log
    wsyncmgr.log
    12.) Starts synchronization in the sccm console
    Source:
    http://robiulislam.wordpress.com/2013/04/12/sccm-2012-installation/
    N.A.Malik

  • SCCM 2012 SP1 Install fails at splash screen: Failed to create process of setupWpf.exe

    Hello,
    I can't seem to get past the initial install screen. When I click install I receive what is shown in the screen shot. The error in question is "Failed to create process of SetupWpf.exe" This is what I get after i click install. The error above
    that one "WinHttpReceiveresponse failed 80072ee7" is what I get when I tried to download the latest updates from the splash screen. It was on like update 44 of 56 when it failed but I am not sure I need to pursue that one. I cant even get the insall
    going.
    Phil Balderos

    I am also having the same issue..
    I can start the sccm 2012 installation piror to installing SQL 2012 SP1. Once SQL installation is complete, and try to install sccm 2012 -> issue occur. Is this a sql issue, or a sccm 2012 issue.. I have download the SQL 2012 and SCCM 2012 FROM MS
    twics.. I have rebuilt my lab twice already ...
    Any help, not sure what step I am missing....
    Hello Yuyut,
    This issue is related to CM12 (not nessarly a widly known issue) perhaps something with the ISO. The copy I was using was from our MSDN subscription which kept failing. I downloaded it twice and still same issue. Since  I am setting this up as a lab
    for testing purposes I just ended up downloaded the 180 day evaluation and has worked for me so far. So again this is not related to SQL as I have noticed.
    Thorsten did mention on this thred that I should check permissons of the account I was trying to install it from. That was not my issue but you could give that a look also.
    Phil
    Phil Balderos

  • Sccm 2012 - patch sync failed

    Hi,
    Recently i updated the proxy account details and verified it is successfully connecting. But when i sync software update i get the below error. Please advice
    Sync failed: UssCommunicationError: WebException: The remote server returned an error: (407) Proxy Authentication Required.~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
    Regards, Pratap

    Hi,
    "The remote server returned an error: (407) Proxy Authentication Required."
    Have you seen this thread? This might be helpful.
    Software
    Update Point error 407 failed to authenticate?
    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.

  • SCCM 2012 - sms_notificaiton_server install fails, bgbisapi.msi could not be installed

    Hi,
    installed a SCCM 2012 R2 Primary site on a 2012 R2 server on the D: drive. Everything seemed to go well, however i am am now encountering issues with the SMS_NOTIFICATION_SERVER in that the site component manager is unable to install it. The status message
    viewer informs me that, "Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install."
    When i check the Bgbsetup.log, i see the following lines: 
    <01/19/15 14:46:27> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    <01/19/15 14:46:27> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
    Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
    <01/19/15 14:46:30> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    <01/19/15 14:46:30> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
    <01/19/15 14:46:30> Fatal MSI Error - bgbisapi.msi could not be installed.
    Having done a bit of reading, it seems a few other people have come accross this issue before:
    https://rikkoss.wordpress.com/2013/12/11/tip-do-not-change-the-default-installation-location-for-configmgr-2012/
    http://www.windows-noob.com/forums/index.php?/topic/7401-sms-notification-server-failed-critical-sccm-sp1-sql-2012-sp1/
    The solution for these folks seems to be to edit 2 files in the .Net folder,InstallUtil.exe.config and Regsvc.exe.config,
    and insert the following code:
    <runtime>
    <loadFromRemoteSources enabled=”true”/>
    </runtime>
    However, this hasn't worked for me and i'm still getting stuck with the same error messages. Since i'd really like to avoid reinstalling SCCM on the C: drive, can anyone suggest any possible solutions to this issue? 

    The MPsetup.log has this:
    <01/20/15 16:28:11>         ======== Completed Installation of Pre Reqs for Role SMSMP ========
    <01/20/15 16:28:11> Installing the SMSMP
    <01/20/15 16:28:11> Passed OS version check.
    <01/20/15 16:28:11> IIS Service is installed.
    <01/20/15 16:28:11> No versions of SMSMP are installed.  Installing new SMSMP.
    <01/20/15 16:28:11> Enabling MSI logging.  mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
    <01/20/15 16:28:11> 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
    <01/20/15 16:28:12> mp.msi exited with return code: 1603
    <01/20/15 16:28:12> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
    <01/20/15 16:28:12> Fatal MSI Error - mp.msi could not be installed.
    and the MPmsi.log has this:
    MSI (s) (B0:E0) [16:37:14:660]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI23F6.tmp, Entrypoint: CcmRegisterPerfCounters
    [16:37:14] @@ERR:25001
    Internal Error 25001. 80070057
    MSI (s) (B0!F8) [16:37:14:676]: Product: BGB http proxy -- Internal Error 25001. 80070057
    CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Had a go at removing the MP, disabled the UAC and reinstalling the MP. Same result unfortunately...The server is temporarily housed in a block GPO OU so group policy shouldn't be an issue. Thanks for all the help so far!

  • Upgraded SCCM 2012 SP1 to CU5 - Problem updating Endpoint Protection Client (to V4.5.216.0)

    We upgraded SCCM SP1 to CU5. We got one primary site, on which we had no problems with running the CU setup. After the upgrade we pushed the new administrator console and client.
    SP1 CU5 - console update -> Updated on all administrator users (50 computers)
    SP1 CU5- x64 and x86 client update -> Updated on pilot group (50 computers)
    No problems so far.
    We are having troubles updating the Endpoint Protection Client version. This was V4.1.522.0 before the upgrade. When we enroll a new computer, it receives the new V4.5.216.0, which is the last version.
    But we can't update our older clients. We try to deploy the software update (Update for Forefront Endpoint Protection 2010 Client - 4.5.216.0 (KB2952678)) but it doesn't install. After 20 minutes, if I look in the Deployment logs, it says the installation
    was successfull; but it isn't, it's still the old version.
    Strange thing is, we can upgrade to an inbetween version (Update for Forefront Endpoint Protection 2010 Client - 4.3.215.0 (KB2864366)). Which installs on a test client.
    If I look to the cache files of the new EP Client update, and use the UpdateInstall.exe manually, the update does install. Then I see in the logfile EndpointProtectionAgent.log it still refers to the version 4.1.522.0.
    EP 4.5.216.0 is installed, version is higher than expected installer version 4.1.522.0. EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
    Re-apply EP AM policy. EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
    Apply AM Policy. EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 13/01/2015 14:54:00 7808 (0x1E80)
    Applied the C:\Windows\CCM\EPAMPolicy.xml with ConfigSecurityPolicy.exe successfully. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
    Save new policy state 1 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
    State 1 and ErrorCode 0 and ErrorMsg and PolicyName Antimalware Policy and GroupResolveResultHash D277339FA77A9017801399D96266BAD42DE74F38 is NOT changed. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
    Skip sending state message due to same state message already exists. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
    Firewall provider is installed. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
    Installed firewall provider meet the requirements. EndpointProtectionAgent 13/01/2015 14:54:02 7808 (0x1E80)
    This is the WindowsUpdate.log when I try to push the new EP client.
    2015-01-14 11:24:13:651 7416 1c44 Handler :::::::::
    2015-01-14 11:24:13:651 7416 1c44 Handler : Updates to install = 1
    2015-01-14 11:24:21:716 7416 1c44 Handler : WARNING: Command line install completed. Return code = 0x8004ff25, Result = Failed, Reboot required = false
    2015-01-14 11:24:21:716 7416 1c44 Handler : WARNING: Exit code = 0x8024200B
    2015-01-14 11:24:21:716 7416 1c44 Handler :::::::::
    2015-01-14 11:24:21:716 7416 1c44 Handler :: END :: Handler: Command Line Install
    2015-01-14 11:24:21:732 7416 1c44 Handler :::::::::::::
    2015-01-14 11:24:21:794 1096 c18 Agent *********
    2015-01-14 11:24:21:794 1096 edc AU Can not perform non-interactive scan if AU is interactive-only
    2015-01-14 11:24:21:794 1096 c18 Agent ** END ** Agent: Installing updates [CallerId = CcmExec]
    2015-01-14 11:24:21:794 1096 c18 Agent *************
    2015-01-14 11:24:21:794 2296 fac COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = CcmExec]
    2015-01-14 11:24:21:794 2296 fac COMAPI - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)
    2015-01-14 11:24:21:794 2296 fac COMAPI - Reboot required = No
    2015-01-14 11:24:21:794 2296 fac COMAPI - WARNING: Exit code = 0x00000000; Call error code = 0x80240022
    2015-01-14 11:24:21:794 2296 fac COMAPI ---------
    2015-01-14 11:24:21:794 2296 fac COMAPI -- END -- COMAPI: Install [ClientId = CcmExec]
    2015-01-14 11:24:21:794 2296 fac COMAPI -------------
    2015-01-14 11:24:21:794 1096 1620 AU Can not perform non-interactive scan if AU is interactive-only
    2015-01-14 11:24:26:739 1096 1424 Report REPORT EVENT: {ED287668-4BEF-46FD-BB57-CA17680E5D3B} 2015-01-14 11:24:21:732+0100 1 182 101 {A90C3005-7B59-4268-8B11-12D9BE5C8EA0} 201 80070643 CcmExec Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Update for System Center Endpoint Protection 2012 Client - 4.5.216.0 (KB2952678).
    2015-01-14 11:24:27:207 1096 1424 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-01-14 11:24:27:207 1096 1424 Report WER Report sent: 7.5.7601.17514 0x80070643 A90C3005-7B59-4268-8B11-12D9BE5C8EA0 Install 101 Managed
    2015-01-14 11:24:27:207 1096 1424 Report CWERReporter finishing event handling. (00000000)
    Thanks in advance!

    Hello,
    According to
    kb2952678:
    To apply this update, you must have one of the following installed:
    System Center 2012 R2 Configuration Manager Cumulative Update 4 for System Center 2012
    Configuration Manager Service Pack
    Service Pack 2 for System Center Configuration Manager 2007 and Update Rollup 1 for
    Forefront Endpoint Protection 2010
    Do you have Update Rollup 1 for Forefront Endpoint Protection 2010?
    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]

  • SCOM 2012 SP1 is failing to install - SQL not compatible

    I'm getting an error when installing SCOM 2012 SP1 stating the SQL is not supported. I have seen a few posts on the forum about this error message but so far none of the resolutions resolved my issue.
    Using named instance on port 2433.  Entering SQL\instance and port 2433 yields same message as seen in another post:
    "The installed version of SQL server is not supported.  Verify that the computer and installed version of SQL Server meet the minimum requirements for installation.  Please see the Supported Configurations document for further information."
    I noticed I get this in my OpsMgrSetupWizard.log
    [15:03:28]: Error: :StackTrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementScope.InitializeGuts(Object o)
       at System.Management.ManagementScope.Initialize()
       at System.Management.ManagementObjectSearcher.Initialize()
       at System.Management.ManagementObjectSearcher.Get()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
    [15:03:28]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
    Notice the last line - IsSQLOnAValidComputer is null/empty.  The solutions I found are to open the ports between these servers but the SQL server and SCOM server are on the same network - no firewall between them.  The registry key for domain firewall
    policy to 'EnableFirewall' is 0.  The firewall service is disabled on both machines.
    I am running the installation as a domain service account - for the DAA.  It has local admin on the SQL and SCOM server.  It has sysadmin DB access to the instance.
    SCOM Server:
    Server 2008 R2 Standard SP1
    SQL Server:
    Server 2008 R2 Enterprise SP1 | SQL 2012 RM 64-bit version 11.0.2100.60
    Any help is greatly appreciated.

    Glad to hear the issue has been resolved. Thanks for the update.
    Niki Han
    TechNet Community Support

  • SCCM 2012 Matching Processor Architecture Boot Image (0) not found

    SCCM2012 SP1 ,One Site, 3DP.
    one DP can not install os with PXE boot. when start PXE F12, system crush with code 0x00000f. and Log like this
    "00:0C:29:90:D1:C0, 291241B9-AB25-4400-B746-99E018F70F1A: device is in the database. SMSPXE 2014/10/1 2:28:11 4504 (0x1198)
    Warning: Matching Processor Architecture Boot Image (0) not found SMSPXE 2014/10/1 2:28:11 4504 (0x1198)"
    The BOOT.wim file works well in ither DP.
    I have try to redeploment the PXE and reload the Boot.Wim file in this DP, but can not reslove this problem.
    I'm afried reset the Boot.wim will take other 2 DP can not work too.
    Please Help.

    Hi Pazza,
    As Torsten said,  please ensure that you have an x86 and x64 boot image configured and deployed, regardless of the architecture of the OS that
    you wish to deploy. Secondly, ensure that the boot images for both architectures have the network drivers for the respective model that you are imaging injected.
    Otherwise, please review the link below:
    ConfigMgr PXE Boot Warning: Matching Processor Architecture Boot Image (0) not found
    http://www.systemcentercentral.com/configmgr-pxe-boot-warning-matching-processor-architecture-boot-image-0-not-found/
    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.

  • 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 SP1 SUP on Windows Server 2012

    Hi sccm guys,
    I'm having Troubles to get the SUP role working on my Windows Server 2012. I'm using SCCM 2012 SP1. I installed (and did not configure) the WSUS role from the Server Manager. I Chose to install the DB on the local SQL instance (no WID instance).
    Then I added the SUP role to the Server and configured it with the seperate wsus Administration site (Ports 8530 and 8531).
    WSUS gets configured partially (Proxy Settings and "Products and Classification" Options only for Office and Windows)
    The folowing error pops up in the wcm.log
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
    Any clues?
    Cheers
    Sebastian Bammer

    Also did not fix my issue. A round of my logs:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Verify Upstream Server settings on the Active WSUS Server
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:14 a.m.
    3556 (0x0DE4)
    Successfully refreshed categories from WSUS server
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:16 a.m.
    3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Starting WSUS category sync from upstream...
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:29:26 a.m. 3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:41 a.m.
    3556 (0x0DE4)
    Successfully refreshed categories from WSUS server
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Subscription contains categories unknown to WSUS.
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCM01.domain SITE=AKL PID=1544 TID=3556 GMTDATE=Mon Jan 14 19:29:42.723 2013 ISTR0="SCCM01.domain" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
    ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
    Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
    Thanks Christoph

  • 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

  • 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

Maybe you are looking for

  • Firefox menus and text have disappeared. Also, can I map Windows key?

    I was using openbox for a while (couple of days) and then decided to switch to KDE. The switch went well and was pretty effortless. I opened Firefox and it still had that ugly "Raleigh" theme to it. Wanting it to look more like the rest of KDE, I che

  • Ask query in sap (using variable $)

    Hi.. i found this query from my sap : SELECT SUBSTRING($[$112.U_CC.1], CHARINDEX(';', $[$112.U_CC.1])+1,16) I try to create some script, but always error. i think the format like this : $[$ITEM.COLOMN.ROW] example : SELECT $[$135.2.1] I run this quer

  • Vizualizer doesn't react to music. (Windows XP)

    In both iTunes 7 and 8, none of the visualizers react to the music. This includes the "classic" visualizer, the new visualizer, and the bars in the information pane. They all display a flat wave, no bars, etc. Music plays just fine otherwise. Anyone

  • Motion Keeps Crashing @ startup

    hey, I keep trying to open motion and it crashes right after the startup screen goes away. the only new thing that I have installed on the computer are some plugins for FCP 6. this shouldn't have anything to do with motion should it? I finally got so

  • Xml import from mutlitple xml files

    Is it possible to import different xml files for different locations within the same InDesign document? For example a single page has two text boxes. Text Box 1 needs to import data from File1.xml, Text Box 2 needs to import data from File2.xml, etc.