none
SCCM 2012 1902 Servicing Stack updates not showing RRS feed

  • Question

  • ON SCCM 2012 version 1902 and the Servicing Stack 2019-05 updates are not showing up to deploy?

    What am I missing? Where do I look?


    Systems Administrator

    Monday, July 15, 2019 3:06 PM

All replies

  • Hi David,

    I just want to notify you that the title includes two different versions of SCCM.

    I think you have SCCM 1902 and the issue is related to showing new software updates on the console, right!

    First, try to run full synchronization of software updates from the console and check the wsyncmgr.log file located on "SCCM Install directory\Microsoft Configuration Manager\Logs", are they any errors?

    Regards,

    SAAD Youssef

    _____

    Please remember to mark the replies as answer if they help, thank you!

    Monday, July 15, 2019 5:53 PM
  • Just the errors.

    Check also the WCM.log file.


    Monday, July 15, 2019 9:28 PM
  • You can also verify SUP synchronization in console under Monitoring - > Software Update Synchronization Status

    For any error check wsyncmgr.log 

      
    Tuesday, July 16, 2019 5:16 AM
  • Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse SMS_WSUS_SYNC_MANAGER 07/17/2019 9:16:58 AM 7396 (0x1CE4)

    Last Catalog Last Updated 5/6/2019?


    Systems Administrator

    Wednesday, July 17, 2019 1:42 PM
  • Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse SMS_WSUS_SYNC_MANAGER 07/17/2019 9:16:58 AM 7396 (0x1CE4)

    Last Catalog Last Updated 5/6/2019?


    Systems Administrator

    Wednesday, July 17, 2019 1:48 PM
  • No errors in this log.

    Systems Administrator

    Wednesday, July 17, 2019 1:49 PM
  • Finally got it. WCM.log shows this:

    Failed to set Subscriptions on the WSUS Server. Error:(-2146232060)Unknown error 0x80131904 SMS_WSUS_CONFIGURATION_MANAGER 07/17/2019 3:18:03 PM 8436 (0x20F4)


    Systems Administrator

    Wednesday, July 17, 2019 7:46 PM
  • Are you using any third-party update catalogs or the the third-party updates feature set in any way?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, July 17, 2019 11:53 PM
  • no.

    None. I think maybe WSUS needs uninstalled and reinstalled?


    Systems Administrator

    Thursday, July 18, 2019 3:04 PM
  • That would be a last resort IMO.

    Have you removed all classifications and product categories and initiated a sync?

    If that works, slowly add back classifications and products and initiate a sync.

    Also, what classifications and products do you have selected?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, July 18, 2019 3:11 PM
  • Mine too but.

    Removed all classifications. No joy.

    WSUS still failing to sync.


    Systems Administrator

    Thursday, July 18, 2019 3:29 PM
  • Did you remove all products as well? Specifically, I'm referring to the configuration on the SUP component properties in ConfigMgr and not directly in WSUS.

    Also, have you reviewed the WSUS log directly?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, July 18, 2019 3:50 PM
  • All changes have been made in the SUP.

    WSUS logs are not showing anything good.

    wsyncmgr showing a timeout syncing

    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 07/18/2019 1:15:16 AM 7756 (0x1E4C)
    Sync failed: Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 07/18/2019 1:17:47 AM 6464 (0x1940)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=120314VMWU1201.IMCU.LOCAL SITE=SC1 PID=5172 TID=6464 GMTDATE=Thu Jul 18 05:17:47.534 2019 ISTR0="Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow" ISTR1="Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 07/18/2019 1:17:47 AM 6464 (0x1940)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 07/18/2019 1:17:47 AM 6464 (0x1940)


    Systems Administrator

    Thursday, July 18, 2019 4:03 PM
  • Do you have any proxy on your LAN to access to the Internet? If true, try to add it in the Internet Explorer proxy settings (on the SUP) and initiate again the sync of software updates.

    Please make sure that the following sites are allowed in your firewall (Internet access):

    • http://windowsupdate.microsoft.com
    • http://*.windowsupdate.microsoft.com
    • https://*.windowsupdate.microsoft.com
    • http://*.update.microsoft.com
    • https://*.update.microsoft.com
    • http://*.windowsupdate.com
    • http://download.windowsupdate.com
    • https://download.microsoft.com
    • http://*.download.windowsupdate.com
    • http://wustat.windows.com
    • http://ntservicepack.microsoft.com
    • http://go.microsoft.com

    Regards,

    SAAD Youssef


    Thursday, July 18, 2019 9:49 PM