locked
SCCM 2012 SP1 - WSUS not working RRS feed

  • Question

  • Hi,

    I'm getting this in the WCM.log file:

    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608
    Checking runtime v2.0.50727...
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    Checking runtime v4.0.30319...
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    Supported WSUS version not found

    I have verified that both patches are installed on the remote WSUS server. I have also installed the WSUS console and both patches on the Primary Site, although KB2734608 isn't showing as installed. I've configured IIS to bind to port 80, 443, 8530 & 8531 and poked the necessary holes in the firewall so I'm pretty sure it's not because it can't connect to the server to check.

    Will this error be due to the missing patch on the Primary Site or is it not required due to it being a console only install? If it is required, how do I get it to install?

    Both servers are 2008R2 and the primary site runs SQL 2012.

    All help wil be greatly appreciated.

    Thanks,

    James.


    • Edited by WorkProfile Sunday, February 10, 2013 2:03 PM
    Sunday, February 10, 2013 2:00 PM

Answers

  • Just to update this thread, after 24 hours of no response from MS 24x7 support I uninstalled WSUS off the server and installed from the version I downloaded from here: http://www.microsoft.com/en-us/download/details.aspx?id=5216 (rather than using the built in 'server manager' in 2008 R2).

    I then applied updates KB2530678, KB2720211 & KB2734608 and SCCM sprung into life.

    • Proposed as answer by yoke88 Wednesday, February 20, 2013 12:38 AM
    • Marked as answer by WorkProfile Wednesday, February 20, 2013 8:49 AM
    Tuesday, February 12, 2013 7:16 PM

All replies

  • Are you using the SQL 2012 as a WSUS database? That's not supported yet.

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

    Sunday, February 10, 2013 3:06 PM
  • Thanks for the reply,

    The WSUS server uses the Windows Internal DB.

    Monday, February 11, 2013 9:45 AM
  • Further to this I've migrated the WSUS installation from the remote server to the local Primary Site System (following this guide: http://blogs.technet.com/b/sus/archive/2009/07/02/how-to-move-wsus-from-one-server-to-another.aspx) but I'm still getting the same error.

    I've re-installed the KB2734608 patch a number of times, each time it says it's completed successfully, but it never shows in the list of installed updates on the server?


    • Edited by WorkProfile Monday, February 11, 2013 4:30 PM spelling
    Monday, February 11, 2013 4:30 PM
  • Do you have an A/V that needs to be disabled in order for installation to fully work for KB2734608?
    Monday, February 11, 2013 9:09 PM
  • You might also want to try this procedure:

    • Stop SMS_EXECUTIVE service
    • stop Update Services
    • stop World Wide Web Publishing Service
    • install the hotfix
    • start all the above services

    Monday, February 11, 2013 9:30 PM
  • The Endpoint Protection client is installed on the server but realtime and scheduled scans are disabled.

    I tried stopping the services prior to installation but it's still not showing in the list of installed updates as it does on my other WSUS server.

    I've opened an support call with MS so hopefully they will resolve the issue before I'm on leave for a month.

    Thanks for the suggestions.

    Tuesday, February 12, 2013 1:57 PM
  • Just to update this thread, after 24 hours of no response from MS 24x7 support I uninstalled WSUS off the server and installed from the version I downloaded from here: http://www.microsoft.com/en-us/download/details.aspx?id=5216 (rather than using the built in 'server manager' in 2008 R2).

    I then applied updates KB2530678, KB2720211 & KB2734608 and SCCM sprung into life.

    • Proposed as answer by yoke88 Wednesday, February 20, 2013 12:38 AM
    • Marked as answer by WorkProfile Wednesday, February 20, 2013 8:49 AM
    Tuesday, February 12, 2013 7:16 PM
  • Thanks, this worked for me

    "I then applied updates KB2530678, KB2720211 & KB2734608 and SCCM sprung into life."

    Dilip


    • Edited by DCM-1 Tuesday, September 10, 2013 6:46 PM
    Tuesday, September 10, 2013 6:45 PM
  • Thanks for sharing this! Works!
    Friday, July 15, 2016 3:08 PM