This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 27%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi,
I wanted to install on our first Management Server SCOM 2019 UR2.
Unfortunately it was not successful on the level of "Database Configuration".
we have 4 Management Server and our database servers for SCOM DBs are also on different servers.
I looked at the setup log. But it does not have any good information:
MSI (s) (24:E0) [13:09:19:012]: Product: System Center Operations Manager Server - Update 'System Center 2019 Operations Manager Update Rollup 2 Patch' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\myUserID\AppData\Local\Temp\2\KB4558752-AMD64-Server.msp.0.log.
MSI (s) (24:E0) [13:09:19:013]: Windows Installer installed an update. Product Name: System Center Operations Manager Server. Product Version: 10.19.10050.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: System Center 2019 Operations Manager Update Rollup 2 Patch. Installation success or error status: 1603.
MSI (s) (24:E0) [13:09:19:014]: Note: 1: 1729
MSI (s) (24:E0) [13:09:19:014]: Product: System Center Operations Manager Server -- Configuration failed.
MSI (s) (24:E0) [13:09:19:014]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager Server. Product Version: 10.19.10050.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.
Any idea?
Best regards
Birdal
Hi @Birdal ,
I think I've encountered the same issue in one of my SCOM 2019 labs, what I did to resolve was to simply restart the SCOM server before attempting to install the Update Rollup 2 patch, normally it's good to restart before to avoid any pending restarts.
It's also important that you run the Update Rollup 2 installer with Run as administrator.
----------
(If the reply was helpful please don't forget to accept as answer, thank you)
Best regards,
Leon
Hi @Leon Laude ,
I started all Management Server and tried UR2 on one MS again.
It is unfortunately failed again.
Best regards
Birdal
Which log file did you look at? Did you check the OpsMgrPatchWizard.log located under %LocalAppData%\SCOM\Logs?
Hi @Leon Laude ,
yes, I checked both OpsMgrPatchWizard.log and also KB4558752-AMD64-Server.msp.0.log.
OpsMgrPatchWizard.log is in the attachment.
Best regards
Birdal18337-opsmgrpatchwizard.txt
Not much to go with, in this case I would suggest you to perform the update of the Update Rollup 2 manually, i.e. without the simplified patching (one-click-installer), and check the results.
You'll find the installation order over at the Update Rollup 2 KB article under the Installation instructions for Operations Manager 2019 UR2 section:
https://support.microsoft.com/en-us/help/4558752/update-rollup-2-for-system-center-operations-manager-2019
Hi @Leon Laude ,
i started / tried UR2 only manually, not one-click. This error occured in this manual process.
As I checked all SCOM Servers on Concole it shows they are not monitored. Interesting is that SCOM Management Server on which I tried to update has now another version than other SCOM servers.
Best regards
Birdal
To make things clear, the error in your first post occurred when attempting to install Update Rollup 2 with the one-click-installer on a SCOM 2019 with Update Rollup 1 environment?
This is the supported installation order:
Since the update failed on the "Database Configuration" step, could you verify if there's an SQL log located here:
Good morning @Leon Laude ,
I understood what you mean with one-click now. I thought if we use the WSUS process which provided SCOM Upgrades also in this month.
Unfortunately there are no .log files under this directory. There are only two sql scripts named update_rollup_mom_db.sql (modified date: 13.07.2020), and UR_Datawarehouse.sql (modified date: 13.07.2020).
Please consider that SCOM DB roles are on different machines, not on Management Server machines.
Best regards
Birdal
To really know if an update was successful, navigate to Administration > Operations Manager Products in the SCOM console and check the ‘Version’, ‘Update Installed’ and ‘KB Number’ fields.
The one-click-installer is basically divided into three steps:
In your case you have successfully updated the management server (please double check the versions first to confirm), this means that the SQL scripts and management pack updates didn't get done successfully.
What I would do is to install the rest manually, follow the update order here:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 31%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
Hi all, Is there any solution to this. I am also facing the same issue in SCOM 2022 while applying UR2