Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
WSUS Role (Re)Install on Server 2012 Errors at "Post-deployment Configuration" Failed

Answered WSUS Role (Re)Install on Server 2012 Errors at "Post-deployment Configuration" Failed

  • Friday, December 07, 2012 6:47 PM
     
     
    Sign In to Vote
    0

    I'm looking for some help troubleshooting WSUS Role (Re)Install on Server 2012, we are seeing the error "Post-deployment Configuration" Failed.

    The Role install process itself completes without error, but the post-deployment configuration task fails almost immediately with a generic error stating "Configuration failed.  A log file was created at ..." and the referenced log file is always present but 1K on disk and seems to be empty, so I don't really have any good clues as to what is going wrong.

    I have tried both the default WID option as well as pointing to an instance of SQL2012 running locally on the box (for SCCM 2012).  One underlying question is if WSUS does in fact support SQL 2012, but since the install fails when using WID as well I don't THINK this is the issue.

    IIS (Web role) is already installed and seems to be running properly, i.e. I can browse to the default home page.  SCCM is also installed and has some roles configured, but I'm at the point of installing WSUS so the roles that depend on that are not currently installed.

    I have tried removing the WSUS role, rebooting, and reinstalling with no change.  I have also tried to follow all of the "forced" uninstall instructions on this forum (mainly http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/f447e7d6-7007-4eb6-b38b-90f92525e09), but between not being able to find a trustworth source for the now defunct Windows Installer Cleanup Utility and also not finding the MSIZAP tool in 2012, there isn't much useful there other than some file and registry locations to check, which seem to be uninstalling cleanly when I remove the role and reboot.

    I'd appreciate any clues on what other logs to check or what else might be going wrong.  Please let me know if you need any other details of the problem.

    Thanks,

    -Scott

     

All Replies

  • Saturday, December 08, 2012 10:01 AM
     
     
    Sign In to Vote
    0

    Are you seeing this error on Server Manager?

    What happens when you start "Windows Server Update Services" from the Windows server Metro UI?

     
  • Monday, December 10, 2012 6:18 PM
     
     
    Sign In to Vote
    0

    Duran,

      Thanks for the reply.

      Yes the error about the post-deployment configuration failure is seen in the "Tasks" flag display in the Server Manager console.

      The service always fails to start, I believe because of the database not being configured.  I know that the DB is not being added correctly (due to the post-deployment script failing, and this happens regardless of if I try the WID or external SQL db, which leads me to think the script fails before any DB related tasks), but I really can't tell why.  The only log I know to look at (as referenced in the Server Manager error) is always blank, and I'm not sure where else to look.  I've combed through the Event Viewer to try and find a clue, but no luck so far.  I'm sure there is something corrupt or letf in a half-configured state, but without a log to point me to what it is I have no idea what it might be.

      Anyone else that's had a similar issue and posted about it I could find out there started from scratch and resolved their issues that way, so I'm tempted to do that.  However as this is my first foray into Server 2012 I want to try to get a good comprehension of how to troubleshoot this type of issue incase it becomes common.  The WSUS (and SC-CM 2012) would be a new service for the environment so there is no production impact here.

      Thanks,

      -Scott

     
  • Monday, December 10, 2012 7:04 PM
     
     
    Sign In to Vote
    0

    FYI, I also tried the install via PowerShell to see if I got any better results or more detailed logging, but at the completion of the install (which seems to succeed) you get the following messsage, which references a page not actually published on TechNet:

    PS C:\Windows\system32> install-windowsfeature -name UpdateServices

    Success Restart Needed Exit Code      Feature Result
    ------- -------------- ---------      --------------
    True    No             Success        {Windows Server Update Services, WSUS Serv...
    WARNING: Additional configuration may be required. Review the article Managing WSUS Using PowerShell at TechNet Library
     (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS
    installation using PowerShell.

    Doing research now to see if I can find a CLI/PowerShell means to execute the post-deployment script.

     
  • Monday, December 10, 2012 7:57 PM
     
     
    Sign In to Vote
    0

    A little progress...

    I search for how to do the WSUS install via PowerShow, found this reference:  http://blogs.technet.com/b/sus/archive/2012/03/20/installing-wsus-on-windows-server-8-beta-using-powershell.aspx

    That guide has you do the install via PowerShell, but then sends you back to ServerManger for the post-deployment script.  Thankfully, there was a post from another user having issues with the GUI install who provided a custom install script.  From the end of that, I could tell that the command being executed post install is the following:  'C:\Program Files\Update Services\Tools\WsusUtil.exe' postinstall /sm

    So from that, I realized that at least one of my issues was that the whole C:\Program Files\Update Services\Tools\ directory is missing!  Haven't figured out how or why that happened yet, but I did find WsusUtil.exe in a temp dir and copied it over to the correct location.  I them ran the script manually, and even though the command still errored out, this time I did actually have logging data at the referenced location.

    The script seems to get all the way through the DB setup and then dies trying to set up IIS as follows:

    2012-12-10 14:37:29  Configuring IIS...

    2012-12-10 14:37:29  Start: ConfigureWebsite

    2012-12-10 14:37:30  Configuring website on port 8530

    2012-12-10 14:37:32  System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified

       at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)

       at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)

       at Microsoft.UpdateServices.Administration.UseCustomWebSite.ExecuteIisCustomAction(String arguments)

       at Microsoft.UpdateServices.Administration.UseCustomWebSite.Install(Int32 portNumber)

       at Microsoft.UpdateServices.Administration.UseCustomWebSite.InstallAndConfigure(IisConfiguration& iisConfiguration, Int32 newPortNumber)

       at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)

       at Microsoft.UpdateServices.Administration.PostInstall.Run()

       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

    I'm looking into what may be causing that error next.

     
  • Friday, January 25, 2013 3:02 AM
     
     
    Sign In to Vote
    0

    Hi Scott,

    did you manage to find a resolution for this? I am having the same issue

     
  • Wednesday, January 30, 2013 4:44 PM
     
     Answered
    Sign In to Vote
    1

    It looks like the cause of this was an incompatability between SC-CM 2012 and SQL Server 2012 on Server 2012/8.  Not that I could find this documented in any of the Microsoft SC install information.

    The solution was to upgrade to SC-CM 2012 SP1 and then deploy the WSUS role.

    • Marked As Answer by Scott Berkman Wednesday, January 30, 2013 4:44 PM
    •  
     
  • Sunday, February 03, 2013 12:47 AM
    Moderator
     
     
    Sign In to Vote
    0

    It looks like the cause of this was an incompatability between SC-CM 2012 and SQL Server 2012 on Server 2012/8.  Not that I could find this documented in any of the Microsoft SC install information.

    The solution was to upgrade to SC-CM 2012 SP1 and then deploy the WSUS role.

    Couple of notes...

    WSUS is not supported on SQL Server 2012 at all.

    Since one of the core purposes of System Center SP1 is to add support for Windows 8, Windows Server 2012, and SQL Server 2012, it's a reasonable inference that System Center 2012 RTM is not supported on Windows 8, Windows Server 2012, SQL Server 2012 -- and I would venture a guess that those platforms were not listed in the System Center 2012 documentation in the system requirements at the time of release. Of course, Service Pack 1 has since been released and all of the documentation has been updated to reflect the SP1 capabilities and supported platforms.

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

     
  • Tuesday, March 19, 2013 12:49 PM
     
     
    Sign In to Vote
    0
    Hi, i am still having the same issue, and in my case it isn't connected with SCCM. I've tried to remove all the WSUS junk from system and after that i can't install it again with Post-installation error like it was described by Scott Berkman. WSUS was installed on Server 2012. Does anybody know how to resolve this?
     
  • Tuesday, March 19, 2013 4:59 PM
     
     
    Sign In to Vote
    0
    What version of SQL Server are you using?
     
  • Tuesday, March 19, 2013 5:39 PM
     
     
    Sign In to Vote
    0

    I'm using WID - it's by Default for WSUS installation. But I've tried SQL 2012 Express, it didn't work too.

    And thank you for response.