SCCM 2012 R2 WSUS Sync issues

hi all.
We have implemented SCCM 2012 R2 with remote SQL instance, since we don’t have internet in CM server, we have used WSUS from upstream DMZ server . When we try to Sync we are getting below error
System.Security.SecurityException: Request for principal permission failed.~~  
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~  
at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)~~The Zone of the assembly that failed was:~~MyComputer
Failed to refresh categories from WSUS server
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
Can anyone help me on this?

I spot the word "proxy" in the error message. Make sure that the servers can communicate with each other without a proxy.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

  • SCCM 2012 CU3 / WSUS - Update files are being deleted

    We have been running this configuration since April of last year and haven't had any problems. 
    The problem is a majority of the window/security updates files in the WSUSContent folder are missing.  I have ran wsusutil /reset and it takes a day or so but it will successfully download the 80GB of missing files.  But after a few days they are
    once again missing.  We do run our EPP updates through WSUS and we have no problems with those.
    I have searched endlessly through the log files, I can see where it goes through and skips them due to being superseded. 
    Do not see any database or communication issues between SCCM and WSUS, per the wsyncmgr.log it sees the thousands of that are available from our WSUS server. 
    So, any suggestions as to what might be causing the update files to be deleted from the WSUSContent folder?
    We are running this on:
    Server 2012 / SCCM 2012 CU3 / WSUS for 2012

    So, just to make sure I understand.  Is that we should be deploying updates from the SCCM Configmgr? 
    If you want to use the integrate experience, then yes.
    but the problem is that a majority of updates are showing Downloaded = No when looking under All Software Updates
    You need to either manually initiate the download of updates or set up an Automatic Deployment Rule (ADR). Either will cause ConfigMgr to download the updates placing them into an update package (which in turn gets placed on a DP where the clients can access
    and download the updates).
    wsynclog shows the sync of the update catalog, i.e., the metadata, and not the actual update binaries.
    Jason | http://blog.configmgrftw.com

  • 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.

  • Database instance for SCCM 2012 and WSUS on a single primary site server

    I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
    the road.
    During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
    Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
    Thanks and regards. 

    Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
    http://technet.microsoft.com/en-us/library/hh692394
    When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
    for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

  • GPO and SCCM 2012 Shared WSUS installation

    Hello
    At present I have a scenario where SCCM 2012 and wsus are installed on the same server and serving around 600 desktop clients.  SCCM is configured to deploy windows updates to the client machine via the sccm client, however the member servers in the
    domain do not have the sccm client installed so I have directed them to use the the WSUS installation via GPO.  The servers do appear in the wsus console but never report status and never pull down any updates.
    Should this setup be possible; to use one wsus instance for both sccm udpate distribution and direct communication from member servers?
    windowsupdate.log entries from a member server as follows:
    2014-02-04 15:10:01:172
    844 1338
    Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-02-04 15:10:01:172
    844 1338
    Agent *********
    2014-02-04 15:10:01:172
    844 1338
    Agent  * Online = No; Ignore download priority = No
    2014-02-04 15:10:01:172
    844 1338
    Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0
    and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-02-04 15:10:01:172
    844 1338
    Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-02-04 15:10:01:172
    844 1338
    Agent  * Search Scope = {Machine}
    2014-02-04 15:10:01:350
    844 14d8
    AU Getting featured update notifications.  fIncludeDismissed = true
    2014-02-04 15:10:01:351
    844 14d8
    AU No featured updates available.
    2014-02-04 15:10:01:364
    844 14d8
    AU WARNING: Returning due to error from GetDownloadProgressUx, error = 0x8024000C
    2014-02-04 15:10:01:364
    844 14d8
    AU WARNING: GetInteractiveInstallProgress failed, error = 0x8024000C
    2014-02-04 15:10:01:364
    564 678
    WUApp WARNING: Call to GetInteractiveInstallProgress failed, hr=8024000C
    2014-02-04 15:10:02:692
    844 1338
    Agent  * Found 0 updates and 74 categories in search; evaluated appl. rules of 236 out of 825 deployed entities
    2014-02-04 15:10:03:234
    844 1338
    Agent *********
    2014-02-04 15:10:03:234
    844 1338
    Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-02-04 15:10:03:234
    844 1338
    Agent *************
    2014-02-04 15:10:03:238
    844 1be4
    AU >>##  RESUMED  ## AU: Search for updates [CallId = {5C25CEFB-5315-4722-A422-790FBC7303B5}]
    2014-02-04 15:10:03:238
    844 1be4
    AU  # 0 updates detected
    2014-02-04 15:10:03:238
    844 1be4
    AU #########
    2014-02-04 15:10:03:238
    844 1be4
    AU ##  END  ##  AU: Search for updates [CallId = {5C25CEFB-5315-4722-A422-790FBC7303B5}]
    2014-02-04 15:10:03:238
    844 1be4
    AU #############
    Thanks in advance...

    Should this setup be possible; to use one wsus instance for both sccm udpate distribution and direct communication from member servers?
    No.
    Torsten Meringer | http://www.mssccmfaq.de

  • 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.

  • SCCM 2012 and WSUS Synchronization error. Message ID: 6703.

    Hi,
    I am facing issues with synchronising updates in WSUS server with SUP in SCCM 2012. I am using web proxy, which has full access to all microsoft update websites. I have configures SUP for both intranet and internet clinets. I am posting some logs below
    that may help to resolve the issue:-
    wsyncmgr.log-
    Synchronizing WSUS server SCCMSERVER.domain.com SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 3824 (0x0EF0)
    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 6368 (0x18E0)
    Sync failed: UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 11/1/2012
    11:58:04 AM 3824 (0x0EF0)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
    ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
    NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
    WCM.log-
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
    Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
    Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:21 AM 4016 (0x0FB0)
    Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>1403f223-a63f-f572-82ba-c92391218055</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>84f5f325-30d7-41c4-81d1-87a0e6535b66</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>8c3fcc84-7410-4a95-8b89-a166a0190486</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>6964aab4-c5b5-43bd-a17d-ffb4346a8e1d</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
    11:52:21 AM 4016 (0x0FB0)
    Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~ <Id>cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
    11:52:22 AM 4016 (0x0FB0)
    WSUSCtrl.log-
    WSUS registry key change notification triggered. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~  
    at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Failed to set WSUS Local Configuration. Will retry configuration. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Urgent Help Appreciated.
    Thanks,
    Deepak

    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
    ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
    ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
    System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~  
    at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
    Those errors are unrelated to ConfigMgr. The first one is a name resolution error; the second one tells that the servers is not allowed to connect to the proxy.
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 R2 WSUS wsyncact error 0x8013141A

    i have new servers with Server 2012 R2, SCCM 2012 R2, and SQL 2012 SP1 CU6. SCCM will not sync with WSUS. "Synchronize Software Updates" fails and no updates appear and the scheduled sync in "SUP Component Properties"\"Sync
    Schedule" runs, the WSUS servers do not sync with their upstream servers. There are no errors in the WCM and WSUSCtrl logs. The wsyncmgr log has these errors:
    Sync failed. Could not load file or assembly '5120 bytes loaded from wsyncact, Version 5.0.0.0, Culture=-neutral, PublicKeyToken=(alphanumeric string) or one of its dependencies. Strong name validation failed. ) Exception from HRESULT: )x8013141A). Source:
    wsyncact
    STATMSG; ID-6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=(servername) SITE=(site code) PID=2704 TID=5516 GMTDATE=(date/time) ISTR1="Could not load file or assembly 'updmgrclr, Version=5.0.7958.1000, Culture=neutral,
    PublicKeyToken=(alphanumeric string)"  or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)" ITR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
    ISTR9="" NUMATTRS=0
    Sync failed. Will retry in 60 minues.
    Moving the servers to an OU with no policies does not help. Setting registry entries to turn off strong name validation does not help.
    I did find one post that said the ports in IIS and in SCCM need to match. My do, IIS and SCCM both have 8530/8531.
    Suggestions?
    Ben JohnsonWY

    SOLVED. FINALLY!
    Do an internet search for "Keith McGuinness" and "Strong name Validation Failed (Exception from HRESULT 0x8013141A)"
    You need to create these two registry keys:
    [HKLM\Software\Microsoft\StrongName\Verification\*,123adf9123]
    [HKLM\Software\Wow6432Node\Microsoft\StrongName\Verification\*,123adf9123]
    You need to do this key pair for each 0x8013141A error you have that has a unique PublicKeyToken. Note that the "*,123adf9123" is a key, not a DWORD or anything else. Also, you have to change 123adf9123 to the PublicKeyToken(s) showing in your
    error messages within WSUS. You can then force a new sync by setting a sync time a couple minutes in the future with configure SUP under Administration\Sites.
    Note: I did this on the site server.
    Ben JohnsonWY

  • SCCM 2012 R2 WSUS db connection error 2146232060

    On a new set of two servers, I have Server 2012 R2, SCCM 2012 R2, and SQL 2012 SP1 CU6. WSUS role is on both servers with WSUS integrated into the SCCM site. Server01 would not connect Server02 with the error "failures were reported on WSUS Server02
    while trying to make WSUS db connection. Error 2146232060".
    We fixed this when we noticed that within Security\Logins "NT Authority\System" on Server01 had the securitymanager and sysadmin rights but such was not the case on Server02. When we set the system account on server02 to match the one on server01
    and rebooted, the problem was fixed.
    Just wanted to let people know in case it helps someone else.
    Ben JohnsonWY

    Hi,
    Thanks for sharing your troubleshooting information here. This could help the others that have the same issue.
    Also, since this is not a question, I will change the type to discussion.
    Juke Chou
    TechNet Community Support

  • SCCM 2012 R2 CU3 PXE issue

    Hi,
    I have a SCCM 2012 R2 CU3 lab where pxe is not working, the clients are able to connect to SCCM server but the download gets stuck on the boot image & then it fails with the following error :-
    Don't find any specific error related to this deployment in SMSPXE.log.
    Thanks,
    Pranay.

    I've had some issues various places with NICs and the TFTP process.  One fix I implemented was to add the following registry entry:
    Location:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSTFTP
    Name: MaximumBlockSize
    Type: (REG_DWORD)
    Value range: 512–1456
    Base: (Decimal)
    I set it to 1024, but you need to determine what value works for your environment.
    This is documented here:
    http://support.microsoft.com/kb/975710/en-us
    Jeff

  • SCCM 2012 - Install WSUS Off Box SQL

    Hi all,
    installed SCCM 2012 R2 CAS on a 2012 server. The SQL is off box on a server cluster. I've installed WSUS through the 'Add Roles and Features'. I configured it to have local storage for the content and a remote DB instance
    (called SQL1 on our cluster). All this worked well and the install completed as expected. I checked the SQL cluster and the "SUSDB" database was created ok.
    As a final step, i went to Tools in Server Manager and launched Windows Server Update Services. This brought up the 'Complete WSUS Installation' dialogue box. I entered the exact same DB info as i had done when completing
    the initial install of WSUS:
    Yet when i hit 'run' the following message returns:
    The relevant bit of logging is shown here:
    2015-01-14 16:58:42  Starting service W3SVC
    2015-01-14 16:58:42  Configuring IIS...
    2015-01-14 16:58:42  Start: ConfigureWebsite
    2015-01-14 16:58:42  System.Runtime.InteropServices.COMException (0x80070422): The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
    So i guess i have two question;
    1] is this Post-installation failure something i need to fix? (I presume it is)
    2] If i do need to fix this to get sccm running properly, does anyone have any suggestions as to where i should start?
    Thanks

    (for three forests which have no trust relationships).
    That's not a valid technical reason to have multiple primary sites at all. ConfigMgr does not care about, use, or rely on domain or forest boundaries or client membership in any way for client management. Using multiple primary sites and a CAS will
    significantly increase complexity and latency, will add additional points of failure, and will increase overall operational costs.
    Concur with Jason here. CAS not needed. You can add in untrusted forests to the Configmgr Console so log as you have an account with permissions in the destination forest, extend the schema, create the system management container and open up any firewall
    ports that are need for communication from site server to dc.
    Neil Peterson has a great set of blogs on how to achieve this
    http://blogs.technet.com/b/neilp/archive/2012/08/20/cross-forest-support-in-system-center-2012-configuration-manager-part-1.aspx
    and ports are listed in this TechNet article under site server -- > Domain Controller. Ensure your RPC ports match the OS of the DC.
    http://technet.microsoft.com/en-gb/library/hh427328.aspx
    Final agreement with Jason - push to get that SQL local. 
    Cheers
    Paul | sccmentor.wordpress.com

  • 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 vs WSUS for Windows Server Updates

    Hi, 
    Can anyone assist with clarifying the benefit of using SCCM 2012 for server patching over WSUS. As far as i understand SCCM can manage updates for third party applications if configured correctly. However if this is the only benefit I cannot see a clear
    reason for using it. 
    Any information on the benefits of SCCM for server patching would be much appreciated. 
    Regards, 
    Michael. 

    Hi,
    There are many reasons to use SCCM for patching instead of WSUS, I wrote a blog post a while ago listing 12 reasons why you should use it.
    http://ccmexec.com/2012/08/top-11-reasons-why-you-should-use-configmgr-2012-for-managing-software-updates/
    I hope that helps!
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Disable Automatically Deleted Updates Download on SCCM 2012 with WSUS

    Hi
    I have SCCM 2012 SP1 with WSUS integrated, both are on the same server, I created a structure where I downloaded the updates:
    D:\Wsus\HotfixWinX
    D:\Wsus = The folder where I installed the WSUS role
    HotfixWinX = The folder where I downloaded the hotfix
    When I run "Synchronize Software Updates" the updates downloaded with a time of old age are eliminated automatically, have reviewed the log wsyncmgr and I found this:
    My question is, how can I prevent updates and updates folders to be automatically deleted?
    Thank you.

    This is a fully automated process that only works for expired updates. Do keep in mind that after this specific message the updates still exist in the console. For a very good complete explanation, see:
    http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCCM 2012 R2 CU4 - WSUS Sync issues

    *EDIT/Update*
    I had incorrectly diagnosed this as an issue with CU4. The issue was in fact between Microsoft and WSUS.
    The method listed in this thread ended up working for me.
    Here is an official KB article for the issue: https://support.microsoft.com/en-us/kb/3058255?wa=wsignin1.0
    (I have a small environment - only 1 SCCM server [primary] and 200 servers managed)
    I upgraded from CU3 to CU4 last week and I cannot get my WSUS to sync all of the updates for April 2015. I also upgraded my test server and it is syncing fine.
    I did some digging yesterday and found out that even tho the site server upgraded (I only have one SCCM server), the SQL update failed because I did not have proper permissions. I've since had a DBA run the update.sql file included with the CU (found at:
    %Program Files%\Microsoft Configuration Manager\hotfix\KB3026739)
    I restarted my SCCM server again this morning and tried running multiple syncs with Microsoft and it is still pulling in nothing. 
    I am not getting any errors in WSUS, wsyncmgr.log, WCM.log, or the change.log for wsus. Everything just looks like it attempted to sync - found nothing - then ended the sync successfully.
    I had one of the networking guys look at the firewall and he says its getting thru and establishing a connection - but it looks like MS is terminating the connection? I cannot see anything that would indicate this in my logs. Here is what he sent me: http://i.imgur.com/znOvxEN.jpg
    Now, to make things even more interesting. In the many many attempts I have made over to the last two days to get SCCM/WSUS to sync April's updates, it has worked in small amounts.... it once expired 16 updates and another time pulled in 2 updates released
    on 4/15/15 (but only 2!). I have my sync settings set up exactly like my test server which, again, is working fine. 
    As always, any help is appreciated!

    sounds like there might be a bigger issue with WSUS and Microsoft?
    https://social.technet.microsoft.com/Forums/en-US/6dbe893b-39f5-4367-902d-678a2a897b9b/wsus-not-syncronizing-aprils-updates?forum=configmanagersecurity
    https://social.technet.microsoft.com/Forums/en-US/a323d2f9-a1ac-48e3-978a-054915c3f1ea/wsus-april-2015-updates-not-synced-from-microsoft?forum=winserverwsus

Maybe you are looking for