none
WSUS 3.0 SP2 install fails on 2008 R2 SP1

    Allgemeine Diskussion

  • Hello 

    The server is a fresh install of 2008 R2 SP1 running as a physical server and is running McAfee antivirus software. 

    I found another discussion in the forums with exact issue (http://social.technet.microsoft.com/Forums/en-US/4f70da30-8d24-42e2-9cc0-b59756925e8e/wsus-30-sp2-install-fails-2008-r2-x64).

    But the resolution in the bottom of the forum didn't solve my problem.

    Error Message that appears:

    The installation gets to the end and when it tries to run the WSUS wizard, I get a box that says,

    "An unexpected error occurred, and this wizard must be closed. You may restart the WSUS Server Configuration Wizard from the Options page in the WSUS 3.0 console."  I can launch the WSUS console, but when I try to connect to the WSUS server, it says it cannot connect. 

    I check the WSUS event logs and see the following:

    Event ID 12052 - "The DSS Authentication Web Service is not working."
    Event ID 12042 - "The SimpleAuth Web Service is not working."
    Event ID 12022 -  " The Client Web Service is not working."
    Event ID 12032 - "The Server Synchronization Web Service is not working."
    Event ID 12012 - "The API Remoting Web Service is not working."
    Event ID 12002 - "The Reporting Web Service is not working."
    Event ID 7053 - " The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\." (Note This even description isn't complete pages long)

    I also discovered that I had some IIS issues by doing a http://localhost test and got a HTTP:// error 500.24 which I resolved by changing the Application pool to classic and enabled authentication.

    Any information would be appreciated, I suspect that I have some sort of configuration issue that is causing this but I verified all requirements of WSUS are correct and installed. I have uninstalled and re-installed IIS and application server.

    thoughts?


    Donnerstag, 5. September 2013 12:23

Alle Antworten

  • Hi,

    I would start uninstalling the antivirus product and then try again. I have see odd issues when AV products block communication or newly installed services.


    Jens Ole Kragh, MCITP Server/Client, MCTS, MCT, Microsoft TechNet Influent Denmark,Blog: http://jensolekragh.wordpress.com/

    Donnerstag, 5. September 2013 13:36
  • Hello Jens,

    Thank you for the idea, I uninstalled the antivirus and the problem still exists.

    I also tried disabling the firewall....with same results of the program failed.

    Donnerstag, 5. September 2013 15:34
  • The server is a fresh install of 2008 R2 SP1 running as a physical server and is running McAfee antivirus software.

    And nothing else except the MAV and WSUS?

    I check the WSUS event logs and see the following:

    Event ID 12052 - "The DSS Authentication Web Service is not working."
    Event ID 12042 - "The SimpleAuth Web Service is not working."
    Event ID 12022 -  " The Client Web Service is not working."
    Event ID 12032 - "The Server Synchronization Web Service is not working."
    Event ID 12012 - "The API Remoting Web Service is not working."
    Event ID 12002 - "The Reporting Web Service is not working."

    I also discovered that I had some IIS issues by doing a http://localhost test and got a HTTP:// error 500.24

    Well, a dysfunctional installation of the Web Server Role would certainly interfere with healthy operation of WSUS. Which begs this question: Premised on the idea that this is a fresh install of WS2008R2 SP1, how exactly did you implement the Web Server Role, and why? Was the Web Server Role implemented in accordance with the documented guidance for WSUS, or was it implemented for some other pre-existing purpose (e.g. McAfee)?

    ...which I resolved by changing the Application pool to classic and enabled authentication.

    And why exactly did you do this?

    • WSUS provides it's own application pool, and WSUS resources should be configured to run in the WSUSPool. The Default Web Site should be running in the DefaultAppPool. These AppPools allows the use of the Integrated Pipeline in IIS7.x, which does work with WSUS. The issue with the 500.24 is not that the Managed Pipeline is misconfigured, it's that some other "extra stuff" is interfering with its proper operation for WSUS.
    • Enabling Authentication is a sure-fire way to break a WSUS server, which fundamentally is a resource accessed anonymously.

    Did you install .NET Framework v4 on this machine? If so, for what application(s)?

    You may also find this thread from this forum (May 2013) of some assistance in troubleshooting an HTTP 500.24 (and HTTP 500.21, which may also exist) on a WSUS Server, although the conclusion (but not resolution) from that thread was essentially the same:

    • Reinstall the Web Server Role with the proper configuration suitable for running WSUS.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Donnerstag, 5. September 2013 15:51
  • Hello Lawrence,

    While we do have a number of other applications on the server, we have the exact same load out on other machines and WSUS operates correctly.

    The Web Service was a requirement for another program running on the machine prior to introduction of WSUS, The installed Web service was reviewed and any needed components for WSUS were added prior to installing the software.

    That was the suggested resolution for the error, When I changed the application I found that the issue 500.24 went away, enabling the authentication was needed for the next error I received and sorry say I didn't document the error number. 

    I will review your suggested thread in your previous post and check on the version of ASP loaded on the machine

    Donnerstag, 5. September 2013 17:47
  • While we do have a number of other applications on the server, we have the exact same load out on other machines and WSUS operates correctly.

    Then it should be trivial to do a thorough comparision of the IIS configuration on the working server(s) against the IIS configuration of this not-working server and find the configuration attribute(s) that are set incorrectly.

    Fundamentally, though, failing to install the Web Server Role with the documented (and only those documented) role services almost always causes issues.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Donnerstag, 5. September 2013 22:55
  • Hello Lawrence,

    No luck, I compared the servers configuration

    • IIS Settings
    • Application Pool
    • Application Server settings
    • Port usage

    Without fail the server I am trying to fix gets the same error message at the end of the install, and when I open the WSUS console I have not options to select in the navigation tree to try and start the configuration manager.

    Thoughts?

    Dienstag, 10. September 2013 20:13
  • Thoughts?

    So, let's regroup, because you've done a lot of things, it seems, over the course of handling this issue.

    After verifying that WSUS has been fully uninstalled (See How to Uninstall WSUS), run the installation again, then find the WSUS install logs. There are two, the basic log and the detailed log. The detailed log has a name of the format WSUS_yymmdd_####.

    Post the contents of the detailed log in a reply to this message.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Mittwoch, 11. September 2013 17:50
  • Hello Lawrence,

    I have completed the uninstall steps above and re-installed.

    I found three Log Files in C:\Users\<USERNAME>\AppData\Local\Temp\2

    • WSUSCa_130912_1330.log
    • WSUSSetup.log
    • WSISSetupMSI_130912_1333.log

    I would rather not post the log information directly to the forum, I have contacted you on link to push files that way.

    Donnerstag, 12. September 2013 18:29
  • Hello Lawrence,

    Sorry for the update delay,

    I eventually resolved the issue for my servers. I updated the application pool settings from Integrated to Classic. All machines I have seen with same issue the change resolves the problem.

    Thank you for your support 

    Dienstag, 5. November 2013 15:13
  • I updated the application pool settings from Integrated to Classic. All machines I have seen with same issue the change resolves the problem.

    Hmmm. That suggests a different sort of problem. The Managed Pipeline for the WSUSPool should be "Integrated".

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Mittwoch, 6. November 2013 00:42