9 Replies Latest reply on Oct 10, 2014 8:36 AM by KMSigma

    New Patch Manager install failure on SQL Express

    khiyal

      I am installing PM 2.0 on a new server as a secondary application server. The initial setup completes successfully, but when installing SQL Express, the install process errors out. From the log:

       

      09/30/2014 16:44:06.585 Attempting to run user requested action from local setup100.exe

      09/30/2014 16:44:06.587 Attempting to launch process C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe

      09/30/2014 16:44:27.651 Process returned exit code: 0x84B40000

      09/30/2014 16:44:27.652 Local setup100.exe returned exit code: 0x84B40000

       

      I have opened a case but haven't had any response since Sep 26 so checking here if someone has had this issue and if so, how was it fixed.

       

      It is being installed on Windows Server 2012 R2 with WSUS Replica already installed.

       

      Thanks

        • Re: New Patch Manager install failure on SQL Express
          Lawrence Garvin

          09/30/2014 16:44:27.651 Process returned exit code: 0x84B40000

           

          It is being installed on Windows Server 2012 R2 with WSUS Replica already installed.

          What instance of SQL Server are you using for the WSUS Replica Server that is already installed?

          Is this an en-US server?

          Is there anything other than the WSUS Role installed on this server?


          I'll also note that the PM installer installs a 32-bit instance of SQL2008R2 Express Edition. I would suggest considering PRE-installing a 64-bit instance of Express Edition for this AppServer role.

          In addition, installing SQL Server interactively/standalone, will produce better error diagnostic messages related to the installation failure, and this specific failure code.

          There are many failures that can cause this particular code, including, but not limited to:

          • An existing installation of SQL Server on the same instance name.
          • An invalid product key (not really applicable to Express Edition).
          • Mismatched language settings (e.g. installing to a non en-US server in the case of Patch Manager)


          You may also find Microsoft KB955396 of some use in diagnosing the installation failure.


          Can you give me the Ticket # you opened on 9/26 so Support can follow-up?