The product group released the February 2022 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.
The KB articles for February 2022 CU should be available at the following locations in a couple of hours:
- KB 5002136 – February 2022 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002118 from January 2022 CU.
The downloads for February 2022 CU are available through the following links:
- Download February 2022 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002118 from January 2022 CU.
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2016 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
SharePoint 2016 February 2022 CU Build Numbers:
Language independent fix: 16.0.5278.1000
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2016
- Blog: SharePoint Patching Best Practices
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Hello Stefan,
we have had the following error message in the system for some time, running multiple times per second, slowing down workflows:
“Potentially excessive number of SPRequest objects (21) currently unreleased on thread 35. Ensure that this object or its parent object (e.g., an SPWeb or SPSite) is properly disposed of. This object is on a separate native heap and is not automatically disposed of. Allocation Id for this object: {3BC5145F-15ED-4147-B356-424D1BD39E65} Stack Trace of the current allocation: at Microsoft.SharePoint.SPGlobal. CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous) at Microsoft. SharePoint.SPRequestManager.GetContextRequest(SPRequestAuthenticationMode authenticationMode) at Micr… 00be1ca0-23cb-90cf-c113-caac7adbd12f”
Do you know what the chance is that it will be fixed with the February CU? Also, do you possibly know what component is causing this?
Thanks in advance.
Best regards
Marcus