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(243.2, 88%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
As I was getting ready to patch SP2019 updates, I ran the SP2019 Product configuration wizard.
I get the following error. Is there a setting I am missing here ? Thanks
Hi @pcaltair@MSSP ,
Which patch did you install in this article: SharePoint 2019 update history? Have you also installed MUI/language patch if there is? Have you installed patches on all APP servers and WFE servers? How about running SharePoint cofiguration wizard using the PowerShell Command: PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install If the error still persists, can you trace more clues or logs about this error?
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
The updates are kb4493162/kb4493161.
Language patches were applied too.
We have one WFE/App server. It was installed on this.
Ran the following Powershell commend for config.
Psconfig.exe -cmd upgrade -inplace b2b -wait -force
updates were done but the gui wizard is throwing an error.
Similar setup on our test server is not throwing any error.
We have one WFE/App server. It was installed on this.
You just have one server for this SharePoint 2019 farm and have installed the related updates on it, is it right?
Please check if there is a link linked to a configuration log file when you met this error like the attached image below(the sample is for SharePoint 2010, which is similar to SharePoint 2019), if yes, please check the file to find more information about this error.
Besides, please try to re-run SharePoint Product Configuration Wizard as administrator, check if this issue still exists.
Yes we have one SP2019 App and one dB server and the patches were applied on that,
I am checking for error log information in ULS logs.
I have already ran config wizard as administrator and got the same error again.
If there are any related messages in ULS logs, please share here for further assistance.