Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

New Patch Manager install failure on SQL Express

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

Find more posts tagged with

wsus

patch_manager

Accepted answers

All comments

LGarvin

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?

khiyal

Case 691850

The replica server is using the internal DB. It is an en-US server and the only thing installed is the WSUS role.

I attempted to pre-install SQL Express, but since it is not installed by PM, when the default ewdgs user is created, I ran into rights issue. All necessary SQL CLR types are also installed in addition to visual C++ redistributables and management objects.

LGarvin

I attempted to pre-install SQL Express, but since it is not installed by PM, when the default ewdgs user is created, I ran into rights issue.

Yes, there are some manual steps that must be performed when pre-installing an instance of SQL Server. I'm pretty sure they're documented.

But perhaps the most significant thing I'm getting from this is that you were able to successfully install *SQL Server* on this machine, which suggests there may be some special issue with the PM installer.

I see from the case notes that the support rep has contacted engineering for further action.

At this point you have two options:

- Complete the manual configuration of the pre-installed SQL Server x64 Express Edition instance, and then install PM using this instance (and note you'll be running on an x64 database engine in that case).

- Wait for the ticket to resolve the issue with installing the 32-bit instance.

khiyal

I went through the documentation but couldn't find any documented steps to perform for user assignment etc when using a local SQL Express instance.

Still waiting for any update on the ticket.