none
SCCM 2012 SP1 SUP on Windows Server 2012 RRS feed

  • Question

  • 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

    Sunday, January 13, 2013 11:03 AM

Answers

  • 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

    Monday, January 14, 2013 7:32 PM

All replies

  • Can you post some of the errors from the wcm.log file.

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    Sunday, January 13, 2013 12:13 PM
  • HI Kent,

    sure, here are the last entries:

    SMS_EXECUTIVE signalled SMS_WSUS_CONFIGURATION_MANAGER to stop. SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:37 2948 (0x0B84)
    Shutting down... SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:37 6212 (0x1844)
    Shutting Down... SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:37 6212 (0x1844)
    SMS_EXECUTIVE started SMS_WSUS_CONFIGURATION_MANAGER as thread ID 2936 (0xB78). SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2948 (0x0B84)
    This MYSITESERVER.mydomain.local system is the SMS Site Server. SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2936 (0x0B78)
    Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2936 (0x0B78)
    Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2936 (0x0B78)
    Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2936 (0x0B78)
        SUP0: MYSITESERVER.mydomain.local, group = MYSITESERVER, nlb = SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2936 (0x0B78)
    Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2936 (0x0B78)
    Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:39 2936 (0x0B78)
    Wait timed out after 0 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:40 2936 (0x0B78)
    Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384 SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384 SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Attempting connection to WSUS server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Successfully connected to server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Attempting connection to WSUS server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Successfully connected to server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:50 2936 (0x0B78)
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:39:56 2936 (0x0B78)
    Attempting connection to WSUS server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:01 2936 (0x0B78)
    Successfully connected to server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:01 2936 (0x0B78)
    Category Company:3b4a8164-d87f-4a44-56ad-3641fd3451c6 (Microsoft) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:01 2936 (0x0B78)
    Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:02 2936 (0x0B78)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:07 2936 (0x0B78)
    Attempting connection to WSUS server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:07 2936 (0x0B78)
    Successfully connected to server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:07 2936 (0x0B78)
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)
    Attempting connection to WSUS server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)
    Successfully connected to server: MYSITESERVER.mydomain.local, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)
    Category Company:3b4a8164-d87f-4a44-56ad-3641fd3451c6 (Microsoft) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)
    Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=MYSITESERVER.mydomain.local SITE=XYZ PID=2836 TID=2936 GMTDATE=So Jän 13 08:40:14.539 2013 ISTR0="MYSITESERVER.mydomain.local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)
    Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 13.01.2013 09:40:14 2936 (0x0B78)

    Sebastian Bammer

    Monday, January 14, 2013 8:17 AM
  • Hi, 

    I too am having this exact error with same setup as you (only using remote SQL server).


    Thanks Christoph

    Monday, January 14, 2013 9:06 AM
  • I just had the same issue on a newly updated server 10 minutes ago. I fixed it by logging on to the WSUS Administrator console, select Option, Start the WSUS Server Configuration Wizard. I walked thru the guide until the point where it showed me the products then I cancelled the guide. My primary site server is now synchronizing again.

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    Monday, January 14, 2013 10:10 AM
  • I just tried that and it did not fix my issue, still the same error message in th ewcm log.

    I also mynually configured the WSUS server now, again, the same issue. I also tried to remove the sup role and then uninstall and reinstall WSUS and enable the role again. Still the same result.


    Sebastian Bammer

    Monday, January 14, 2013 1:12 PM
  • 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

    Monday, January 14, 2013 7:32 PM
  • Pretty strange behavior but here's what I did to fix it:

    1.) Uninstall SUP role

    2.) Uninstall WSUS

    4.) Delete SUSDB from SQL Server

    5.) Restart Server

    6.) Install WSUS (Chose to install DB nit WID)

    7.) Configured Updates to be stored locally

    8.) Ran 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 (like Kent suggested). Here I canceled the wizzard without chosing 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 I needed

    11.) Checked wcm.log where everything seemed all right now.

    12.) started synchronization in the sccm console

    At least for me this is working now.

    Cheers

     


    Sebastian Bammer


    Tuesday, January 15, 2013 9:23 PM
  • That seems to have done the trick :)

    Thanks Sebastian


    Thanks Christoph

    Wednesday, January 16, 2013 1:30 AM
  • For anyone else that stumbles on this thread, I wanted to post what worked in my case. I got this same error after moving the SUP to a different server and creating a new SUSDB. On the original server, I had integrated SCUP and was using it to publish Adobe Updates. Well, when the WCM.log says "Subscription contains categories unknown to WSUS" it was referring to the Adobe Updates. I simply had to go into the SUP settings and uncheck Adobe as a product to sync. It then allowed me to proceed with the WSUS config and sync. I assume it will all be back to normal when I integrate SCUP on the new server.
    • Edited by KevinMJohnston Saturday, February 23, 2013 12:30 AM
    • Proposed as answer by Lourh Saturday, May 25, 2013 11:16 AM
    Saturday, February 23, 2013 12:30 AM
  • This worked for us as well!


    Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

    • Proposed as answer by Lourh Saturday, May 25, 2013 11:16 AM
    Wednesday, May 22, 2013 7:35 PM
  • Thank You! Removing the Adobe and HP updates have started the Sync process!

    Hopefully it will complete!


    Regards Craig Wilson

    Monday, June 17, 2013 12:28 PM
  • We also experienced this problem:

    SCCM 2012 SP1 CU3, We do not have SCUP installed/in use

    Server 1 Site System - Server 2012 fully patched, SQL 2012 SP1

    Server 2 SUP - Server 2012 fully patched, WSUS fully patched, using internal DB


    The way I resolved this was simpler than other suggestions.  I went into the WSUS console, went to Products and Classifications and changed both (in my case only Win 7 and everything except for drivers and tools.

    Then I ran a re-sync from CCM console whcih immediately showed in the wsyncmgr log that the categories had been sync'd and they seemed to talk to each other again.

    Hope this helps

    Monday, September 30, 2013 11:32 AM
  • Had the same problem after a migration from SCCM 2012 SP1 to new hardware and SCCM 2012 R2, solved it by uncheck the SCUP updates in the "Software Update Point". After un-check it works like a charm
    Tuesday, November 5, 2013 7:49 AM

  • We also run in this problem:

    1 Server 2012 R2, WSUS installed with SQL 2012 SP1 Dbase, Primary Site, SCCM 2012 R2, SUP installed

    We followed the steps mentioned by Sebastian, started the synchronization in the wsus console.
    At this point the SUP succesful updated the configuration but then the WCM.log mentioned
    "Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS" 
    After the removal of this product in the SUP started functioning.

    Hope it helps


    Hereby a part of our WCM.log:
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SMSSRV.contoso.com SITE=MS1 PID=5492 TID=4020 GMTDATE=di nov 12 07:01:56.711 2013 ISTR0="SMSSRV.contoso.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER
    Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER
    .....
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
    Attempting connection to WSUS server: SMSSRV.contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER
    Successfully connected to server: SMSSRV.contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER
    Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER
    Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER
    WSUS sync was already in progress SMS_WSUS_CONFIGURATION_MANAGER
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
    .....
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
    Attempting connection to WSUS server: SMSSRV.contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER
    Successfully connected to server: SMSSRV.contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
    Attempting connection to WSUS server: SMSSRV.contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER
    Successfully connected to server: SMSSRV.contoso.com, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER
    Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER
    Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SMSSRV.contoso.com SITE=MS1 PID=5492 TID=4020 GMTDATE=di nov 12 09:13:01.419 2013 ISTR0="SMSSRV.contoso.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER
    Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER
    Wait timed out after 1 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER
    Timed Out... SMS_WSUS_CONFIGURATION_MANAGER

     

    • Proposed as answer by stevendes Thursday, November 28, 2013 11:27 AM
    Tuesday, November 12, 2013 10:22 AM
  • Removing "Windows 7 Language Packs" from the products did the trick for me... now syncing (finally)!
    Thursday, November 28, 2013 11:26 AM
  • I had this when I uninstalled wsus on sccm 2012 sp1 and trhen reinstalled it.

    I unchecked every classification and product on the SUP component. Did a synch. This succeeded. After this success checked every classification and component. Synched again: successful.

    Monday, March 24, 2014 2:08 PM
  • This fixed my problem too. I had done a site recovery when I migrated to Server 2012 R2 and the old Adobe category stuck around. Once I deselected it on my SUP settings, the sync works again. Now hopefully when I publish updates from SCUP, it will refresh those categories and allow me to sync again.

    Thanks!

    Thursday, March 27, 2014 5:07 PM
  • I am having the issue with Java JRE Client. Any suggestions? Thanks.
    Monday, December 26, 2016 1:30 PM
  • I found this on the internet but don't have any idea how to find it.

    Afterwards, I kept seeing an error after setting up the SUP in the WCM log:

    Category Product:e1d507be-497c-d8fd-61d7-b0d93ee399ca (Adobe Reader) not found
    on WSUS
    Subscription contains categories unknown to WSUS.
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified
    error


    Very odd error, the SUSDB was replaced and still I was having issues. I removed
    all classifications / products and the error still was seen in the WCM log.

    I searched everywhere on the web, couldn't find anything at all, looked on
    premier and old case notes, nothing.

    Finally found an individual talk about residual information left in the CM DB
    from multiple re-installs of WSUS. The location of the subscription was found
    in the v_updatecategoryinstances.  Taking the categoryinstanceID that was seen
    in the WCM, I was able to find the table "ci_updatecategorysubscription " and
    update the column "issubscribed to 0" which then allowed the sync to take place
    and update the classifications / products. I was able to now select the
    classifications and products and now have a sync running with no errors.

    Monday, December 26, 2016 3:50 PM
  • Ok, a combination worked for me.

    After uninstalling WSUS and SUP, and reinstalling them - nothing was syncing although the WSUSCTRL.log file was good. 

    the 2147467259 error showed up - to fix:

    1. open the WSUS console, next, next until you get to the "connecting" screen - then CANCEL...yes, you need to shut the wizard down, it's configured after that.

    2. Go to your SUP product selection in SCCM console, and deselect any offending products - all if you have to and turn them on one by one.  In my case, it had Adobe and Local Publisher - deselect, resync, ALL GOOD.

    Thanks for everyone's help here.!!

    Tuesday, June 27, 2017 3:08 PM
  • Thanks KevinMJohnston

    6 years later, x number of versions & CU updates & latest SCCM CB 1902 still chokes on the same!

    Is it really so difficult for MS to get things right?

    We not doing odd things, we just are trying to use they software!

    Friday, May 17, 2019 12:49 PM