locked
SCCM 2012 SP1 - SUP Error RRS feed

  • Question

  • Hi guys,

    i upgraded my SCCM 2012 test Environment to SP1. I have only one Primary Site Server which holds all Roles. Everything seems to work fine except the SUP Role. If i try to synchronize the latest Updates it says that it cannot find a WSUS Server and i should check WCM.LOG.
    Within WCM.LOG i can find the following Messages:

    Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 08:56:44 3620 (0x0E24)
    Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:07:56 3620 (0x0E24)
    SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
    Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
    Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
        SUP0: CM01.TEST.LOCAL, group = , nlb = SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
    Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
    Bad Configuration, SUPs present but no default SUP SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
    Default SUP not specified SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
    Setting new configuration state to 0 (WSUS_CONFIG_NONE) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
    Waiting for changes for 47 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)

    So in General this tells me that it can find a SUP but this one is not specified as a DEFAULT SUP. How can i tell SCCM that this is my Default SUP? (I only have this one and it is configured to sync from Microsoft Update site). I have never seen this before so i guess this is related to SP1?

    PS: I also installed the 2 necessary WSUS Updates before i upgraded to SCCM SP1.

    Thanks in lot in advance.

    Stefan


    Wednesday, January 9, 2013 1:14 PM

Answers

  • http://support.microsoft.com/kb/2734608 contains the other hotfix

         Additionally, this update includes the following fixes:
    • 2530678 System Center Update Publisher does not publish customized updates to a computer if WSUS 3.0 SP2 and the .NET Framework 4 are installed
    • 2530709 "Metadata only" updates cannot be expired or revised in WSUS 3.0 SP2
    • 2720211 An update for Windows Server Update Services 3.0 Service Pack 2 is available
    Be aware of this before you proceed - http://blogs.technet.com/b/sus/archive/2012/10/31/support-tip-many-new-revisions-of-updates-may-be-downloaded-by-the-wsus-server.aspx

    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    Thursday, February 14, 2013 6:30 PM

All replies

  • Double check the port settings of the SUP role and make sure that the same ports as WSUS is using are configured.

    Torsten Meringer | http://www.mssccmfaq.de


    • Edited by TorstenMMVP Wednesday, January 9, 2013 1:25 PM
    Wednesday, January 9, 2013 1:25 PM
  • Double check the port settings of the SUP role and make sure that the same ports as WSUS is using are configured.

    Torsten Meringer | http://www.mssccmfaq.de



    I verified that already. WSUS was installed on alternative Port 8530 and SUP is configured to connect to this Port.
    Wednesday, January 9, 2013 1:43 PM
  • Have the same error over here, also SCCM 2012 SP1, fresh instalL;

    Jan Hoedt

    Wednesday, February 13, 2013 4:59 PM
  • Two KB installs were needed, you will find the KB numbers in WCM.log. This solved the problem.

    Jan Hoedt

    • Proposed as answer by janhoedt Thursday, February 14, 2013 12:36 PM
    Thursday, February 14, 2013 12:36 PM
  • http://support.microsoft.com/kb/2734608 contains the other hotfix

         Additionally, this update includes the following fixes:
    • 2530678 System Center Update Publisher does not publish customized updates to a computer if WSUS 3.0 SP2 and the .NET Framework 4 are installed
    • 2530709 "Metadata only" updates cannot be expired or revised in WSUS 3.0 SP2
    • 2720211 An update for Windows Server Update Services 3.0 Service Pack 2 is available
    Be aware of this before you proceed - http://blogs.technet.com/b/sus/archive/2012/10/31/support-tip-many-new-revisions-of-updates-may-be-downloaded-by-the-wsus-server.aspx

    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    Thursday, February 14, 2013 6:30 PM
  • None of your solutions apply to WSUS 4.0 on Server 2012

    None of the specified patches applies or will run on a Windows 2012 Std server. They either report that WSUS 3 SP 2 isn't installed OR that the patch isn't applicable to the server version installed.

    Here is a excerpt of MY WCM.LOG

    I have a fully patched Windows 2012 Standard Server, Fully updated SCCM 2012 SP1 installed, and am connected to a fully patched SQL2012 Server on another fully patched Windows 2012 Std server.

    Ports 8530 and 8531 designated on both the WSUS 4.0 Role and SCCM 2012 SP1 system (both are on same server)

    SUP0: SCCM2012.xxdomainname.ORG, group = , nlb = ~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
    Updating active SUP groups...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
    Bad Configuration, SUPs present but no default SUP  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
    Default SUP not specified  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
    Setting new configuration state to 0 (WSUS_CONFIG_NONE)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
    Waiting for changes for 11 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
    Wait timed out after 11 minutes while waiting for at least one trigger event.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
    Timed Out...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
    Default SUP not specified  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
    Waiting for changes for 60 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
    Wait timed out after 60 minutes while waiting for at least one trigger event.  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
    Timed Out...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
    Default SUP not specified  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
    Waiting for changes for 60 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>


    Randall

    Friday, March 14, 2014 7:16 PM
  • Since this is the only web result for this problem, here is what worked for me.

    I was missing two SCCM 2012 pre-requisites (though it installed fine). Install using:

    Add-WindowsFeature NET-HTTP-Activation,NET-Non-HTTP-Activ

    Then remove the Software Update Point role, reboot the server. Re-install  the Software Update Point and you should be good to go.

    Kieran.

    • Proposed as answer by Kieran Walsh Thursday, May 1, 2014 11:52 AM
    Thursday, May 1, 2014 11:28 AM