none
SCCM 2012 and WSUS

    Question

  • 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

    Friday, September 13, 2013 7:50 PM

Answers

  • My recommendation would be to remove the SUP and WSUS and reinstall.

    Here's a step by step of the process

    http://www.gerryhampsoncm.blogspot.ie/2013/04/sccm-2012-sp1-step-by-step-guide-part.html



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    • Marked as answer by RCCMG Wednesday, September 18, 2013 3:54 PM
    Tuesday, September 17, 2013 5:33 PM
  • ConfigMgr does configure WSUS if everything is working as expected.
    The problem seems to be caused by "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)", but I have no idea how to fix that without sitting in front of the system in order to check various things.

    \Administration\Overview\Site Configuration\Sites -> Configure Site Components -> Software Update Point.


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

    • Marked as answer by RCCMG Wednesday, September 18, 2013 3:54 PM
    Wednesday, September 18, 2013 3:43 PM
    Moderator

All replies

  • Is WCM finding the SUP ok?  Do you have a proxy you have to go through?
    Friday, September 13, 2013 9:24 PM
  • Are all roles on the same server? Have you performed the post installation tasks of WSUS?

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

    Saturday, September 14, 2013 8:19 AM
    Moderator
  • Are you running WSUS on a separate port ie. 8350?

    Paul | sccmentor.wordpress.com

    Saturday, September 14, 2013 9:57 AM
  • Is WCM finding the SUP ok?  Do you have a proxy you have to go through?

    I think so...

    Attempting connection to WSUS server: SERVER, port: 8530, useSSL: False

    Successfully connected to server: SERVER, port: 8530, useSSL: False

    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error


    Edit: No Proxy - Forgot to answer that part.
    • Edited by RCCMG Monday, September 16, 2013 2:10 PM
    Monday, September 16, 2013 2:06 PM
  • Are all roles on the same server? Have you performed the post installation tasks of WSUS?

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

    Yep they are all on the same server. WSUS is installed on the Primary. As far as I can tell I have done the post installation tasks and can open the WSUS console.

    Monday, September 16, 2013 2:09 PM
  • Are you running WSUS on a separate port ie. 8350?

    Paul | sccmentor.wordpress.com


    8530 and 8531 according to firewall rules.
    Monday, September 16, 2013 2:11 PM
  • Anyone have any thoughts? This is realistically the last big hurdle I have for getting this up and doing OSD as we migrate from XP to 7.
    Tuesday, September 17, 2013 5:26 PM
  • My recommendation would be to remove the SUP and WSUS and reinstall.

    Here's a step by step of the process

    http://www.gerryhampsoncm.blogspot.ie/2013/04/sccm-2012-sp1-step-by-step-guide-part.html



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    • Marked as answer by RCCMG Wednesday, September 18, 2013 3:54 PM
    Tuesday, September 17, 2013 5:33 PM
  • My recommendation would be to remove the SUP and WSUS and reinstall.

    Here's a step by step of the process

    http://www.gerryhampsoncm.blogspot.ie/2013/04/sccm-2012-sp1-step-by-step-guide-part.html



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson


    Thanks. I will try that. Do I need to do anything with the SUSDB in management studio?
    Tuesday, September 17, 2013 5:37 PM
  • Yes, you can delete it after you have removed WSUS


    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Tuesday, September 17, 2013 5:38 PM
  • 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.

    Tuesday, September 17, 2013 8:04 PM
  • bah, Why cant SCCM just configure WSUS if you plan on using SUP. They configure WDS, don't understand why they don't do it here too... In anycase, I am reinstalling WSUS/SUP again to just re-trace my footsteps.

    On a side note, where do I see the categories once the SUP role is installed?

    Wednesday, September 18, 2013 3:28 PM
  • ConfigMgr does configure WSUS if everything is working as expected.
    The problem seems to be caused by "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)", but I have no idea how to fix that without sitting in front of the system in order to check various things.

    \Administration\Overview\Site Configuration\Sites -> Configure Site Components -> Software Update Point.


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

    • Marked as answer by RCCMG Wednesday, September 18, 2013 3:54 PM
    Wednesday, September 18, 2013 3:43 PM
    Moderator
  • Ok, I will see if I can do anything about that error. Thanks for the path, this new console is nice, just gotta get used to some things.

    Wednesday, September 18, 2013 3:51 PM
  • Thanks for the help guys. The Product "Windows 7 Language Packs" was my problem... After unchecking and syncing again I have progress.

    sync: WSUS synchronizing updates, processed 3727 out of 30911 items (12%), ETA in 00:22:00

    • Proposed as answer by Fred Eric S Thursday, November 07, 2013 1:45 PM
    Wednesday, September 18, 2013 3:57 PM
  • Hi,

    I've encountered the same problem today, after having to reinstall the WSUS & SUP on a Server 2008 R2 with SCCM 2012 SP1 on it, because the WSUS was saving the updates to the C:\ drive.

    After reinstalling, for some reasen, the Windows 7 Language Pack Category was not recognized anymore and lead to the error mentioned in this thread. Removing the faulty category and resyncing allowed a correct synchronization of the SUP.

    As for the faulty category, I'll have to continue next week, but I'll be sure edit this post with the results.

    Best Regards,

    Fred

    Thursday, November 07, 2013 2:45 PM
  • This was my problem as well. SCCM had the option for language packs and WSUS didnt. had to clear the option from SCCM and then it was smooth sailing.

    -Brent Blades

    Tuesday, December 31, 2013 7:44 PM
  • I am having this same issue, except the categories they are looking for are Chrome and Firefox, I used SCUP to publish them to Config Manager. I no longer have the option to deselect  them under local publisher. Updates will not sync with Microsoft. 

    I tried to re-publish through SCUP, but that is having errors as well. 

    

    

    Wednesday, February 19, 2014 7:40 PM
  • This fixed my issue also.  Figured out what I did, when installing WSUS used the config wizard and selected the Windows 7 Language Packs.  

    When the sync happens for the first time from MSSC 2012 R2 to WSUS it inserts "WSUS Enterprise Update Source objects" which must update WSUS to MSSC.

    Been going nuts the past few hours trying to figure this out, really need to read all the logs in MSSC!

    Tony


    Sunday, March 09, 2014 11:44 PM