Patching process on SharePoint 2016 servers

Question

Patching process on SharePoint 2016 servers

sns 9,251

In Our prod form CU current Version 16.0.5368.1000

It is SharePoint 2016

Please clarify my below questions:

1.

Earlier it was done in the of April 2022, August 2022 and November 2022, this is sequence we followed.

As per your suggestion when we should plan again? ca we go head directly with Feb 2023 CU?

https://learn.microsoft.com/en-us/officeupdates/sharepoint-updates

2.

I referred above link February CU got released. so directly can we plan feb CU release?

3.

Do we need to install Language packs first and then other file, Please confirm

4.

and below 2 files need to install in all servers in farm, am i correct?

User's image

After installing then running the config wizard using below command in only in app servers? I want to run in all server, is there any harm?

PSConfig -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

Need to take both VM File back and DB server backup, both before patches upgrade am I correct?
Please clarify this cumulative update does it have any negative impact on designer workflows and Nintex workflows functionality?

Please correct if I miss any step is missing, thank you.

2 answers

Your answer

Answer 1

Hi @sns ,

As the article said, You can directly install the latest CU.

SharePoint updates are cumulative, so each update contains all of the fixes that have been released up to that point, including all previously-released security fixes. Only the most recently-released STS and WSSLOC updates need to be installed to get all of the fixes for previously-published security CVEs.

CU’s should only be installed to resolve specific issues fixed with the CUs as mentioned in each CU KB article: “Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.” Or if advised to install by Microsoft Support. Or at least every 2 years so you are eligible for Microsoft's product support.

Install the language independent update (STS) first. And then install language dependent update (WSSLOC).

Just install the 2 files in SharePoint Server.

For more information, please refer to:

https://blogit.create.pt/miguelisidoro/2019/04/08/how-to-install-sharepoint-cumulative-updates-in-a-sharepoint-farm-step-by-step/

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

For 7, as far as I know, CU is to fix some problems, in principle, it will have no effect. You can view each CU's specific targeted fixes to make a judgment. Or you can go to the Nintex forums for line-specific help.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.

sns 9,251 Reputation points

2023-02-21T17:39:41.49+00:00

Hi Yanli Jing,

Thank you for the response.

in the document you have shared not mentioned whether STS and other files need to be installed in all servers or not?

also prod config wizard should be done in all servers or not?

and do we need to resume search service applications, is it mandotary?
Yanli Jiang - MSFT 31,671 Reputation points Microsoft External Staff

2023-02-22T09:33:42.6166667+00:00

Hi sns ,

You just need to install two files on SharePoint Server and run the configuration wizard.

Wait until the backup or restore completes. After the procedure completes, it will turn on automatically, you can run the command $ssa.ForceResume(0x02) to verify.

For more information, see:

https://learn.microsoft.com/en-us/sharepoint/search/manage-a-paused-search-service-application

Restore Search service applications in SharePoint Server.
sns 9,251 Reputation points

2023-02-24T09:46:46.7466667+00:00

HI Yanli JIang,

Is it need to be installed in all servers?
sns 9,251 Reputation points

2023-02-24T09:47:01.24+00:00

test123
sns 9,251 Reputation points

2023-02-24T10:29:20.3766667+00:00

test123

Answer 2

Stefan Goßner 736 Microsoft Employee

For SharePoint Server 2016 it is sufficient to install the two fixes released with each CU.

It is recommended to install the language independent fix first (sts...) and afterwards the language dependent fix (wssloc...).

After installing the binaries on all servers you should run the config wizard on the server hosting the central administration.

After this is completed you need to run the configuration wizard on all other SharePoint servers int he farm. This can be done in parallel.

As you are talking about February 2023 CU - be aware that there is currently a known issue which affects this CU. Information about he issue and how to resolve it is in this article:

https://blog.stefan-gossner.com/2023/02/16/trending-issue-distributed-cache-problems-after-applying-january-2023-cu/

Be aware that with SharePoint Server 2016 you can also do zero-downtime-patching if your farm topology allows it:

https://blog.stefan-gossner.com/2016/04/29/sharepoint-2016-zero-downtime-patching-demystified/

To have really zero-downtime you should combine it with side-by-side patching to ensure that all servers serve the same javascript files even during patching:

https://blog.stefan-gossner.com/2017/01/10/sharepoint-server-2016-patching-using-side-by-side-functionality-explained/

Cheers,

Stefan

sns 9,251 Reputation points

2023-02-24T10:44:59.2366667+00:00

In that case I will go with Jan 2023
Stefan Goßner 736 Reputation points Microsoft Employee

2023-02-24T12:38:22.8633333+00:00

Jan CU has the same issue.
sns 9,251 Reputation points

2023-02-25T04:39:22.97+00:00

Hi Stefan,

I see 16.0.5378.100 version in SP Server from system settings and I run this command PSconfig -cmd upgrade ......

I ran above command and I was seeing some db error and I fixed those

Now if I run same command I am geting below warning , please suggest further

Could please clarify do I need to install above updates in GS0574 server? and ifit is yes , can you please share appropriate links? and also I just need to download and run, am i Correct?

Please suggest, thank you.
sns 9,251 Reputation points

2023-02-25T04:39:34.22+00:00

test123
Stefan Goßner 736 Reputation points Microsoft Employee

2023-02-25T09:50:31.35+00:00

During the installation of a sharepoint fix the information about the installed fix is added to the SharePoint configuration database. When the config wizard is run it verifies that all SharePoint servers in the farm have the same patches installed as it is required to have all machines on the same patch level.

If it identifies that a fix is missing on one of the machines it reports it as in your scenario.

There are two possible reasons: the two fixes listed above have not been installed on the reported machine (GS0574) or the during the patch installation it failed to add the information that the fixes are installed to the configuration database. e.g. if the SQL server was down when installing the fixes.

If the fixes have not been installed you need to install them.

If the fixes were installed but are incorrectly reported as missing because the info never made it into the confiuguration database you need to run the powershell command "Get-SPProduct -local" on GS0574 to update the information in the config db.

Btw: The psconfig command you were using is not the recommended one.

Please use this on going forward:

PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

See here for details:

https://blog.stefan-gossner.com/2015/08/20/why-i-prefer-psconfigui-exe-over-psconfig-exe/

Cheers,

Stefan
sns 9,251 Reputation points

2023-02-25T10:13:49.1+00:00

test123
sns 9,251 Reputation points

2023-02-25T10:18:01.68+00:00

Hi Stefhan,

I ran below commad in the GS0574

"Get-SPProduct -local" on GS0574

now do I need to run below command in GS0574 machie?

PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
Stefan Goßner 736 Reputation points Microsoft Employee

2023-02-25T12:15:43.5366667+00:00
Ok, step by step:

try to install the two fixes that were reported as missing on GS0574 (KB5002350, KB5002325).

If these fixes fail to install with the message that the fix is already installed run Get-SPProduct -local to update the info in the config db - otherwise skip this step

Go back to the machine hosting your central admin site

Run on the machine hosting the central admin site:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

The step should complete now if all fixes are installed on all servers. if the fixes are reported as missing on other servers in your farm (its not clear how many servers you have in your sharepoint farm) repeat step 1 to 3 on the other servers. Afterwards run step 4 again.

After PSConfig succeeded on the machine hosting the central admin run the same command on all other servers in the SharePoint farm to upgrade these machines as well

Thats all.
sns 9,251 Reputation points

2023-02-25T12:23:51.4933333+00:00

Test123
sns 9,251 Reputation points

2023-02-25T12:27:31.4533333+00:00

Hi Stefan ,

Thank you for the support

can you provide me link for (KB5002350, KB5002325 )
Stefan Goßner 736 Reputation points Microsoft Employee

2023-02-25T14:09:54.3466667+00:00

You will find all relevant information here:

https://blog.stefan-gossner.com/2023/02/14/february-2023-cu-for-sharepoint-server-2016-is-available-for-download/

Cheers,
Stefan
sns 9,251 Reputation points

2023-02-25T18:23:10.48+00:00

Hi Stefan,

I have done till step number 3,

I have ran step4 that is running PSCONFIG on CA server ( gs561)

I see now it is updated 16.0.5383.1000 on system settings.

It failed at last step it seems, Please refer below screenshot

and under upgrade status, Please see below screenshot

i have attached logs.

PSCDiagnostics_2_25_2023_18_19_4_366_1913680836.log

Looks like few dbs are causing with missing features.

I tried to fix the missing features, could you please suggest how to fix those missing features with clear steps for the respective databases.

In one of the script i tried but even though i gave db name , feature id and site collection url in the script, it is giving warnig " can not index to null array" not sure what mistake I am doing.

and second question:

Once these missing features issue fixed , I will run PS config in remaining servers.

Thank you
Stefan Goßner 736 Reputation points Microsoft Employee

2023-02-25T21:47:45.9066667+00:00

The error indicates that the content databases you are using reference some 3rd party solutions and features. You need to install these 3rd party solutions on this SharePoint farm.

Share via

Patching process on SharePoint 2016 servers

2 answers

Your answer