The product group released the April 2023 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 April 2023 CU should be available at the following locations in a couple of hours:
- KB 5002385 – April 2023 Update for SharePoint Server 2016 (language independent)
This is also a security update! - KB 5002370 – April 2023 Update for SharePoint Server 2016 (language dependent)
The downloads for April 2023 CU are available through the following links:
- Download April 2023 Update for SharePoint Server 2016 (language independent)
This is also a security update! - Download April 2023 Update for SharePoint Server 2016 (language dependent)
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 April 2023 CU Build Numbers:
Language independent fix: 16.0.5391.1000
Language dependent fix: 16.0.5391.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
After the installation all SharePoint Websites were unavailable. All App Pools were in stopped state. Even a iisrest nor manually starting the app pools helped.
I’ve found Events with ID 2280, IIS-W3SVC-WP: Error loading module C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\isapi\sprequestfilteringmodule.dll.
Erro Code 7E 00 00 00
File Date: 14. March 2023
Permalink
Hi Stephan,
thanks for the feedback!
If you need assistance to get this resolved I would recommend to open a ticket with Microsoft Support for this.
Cheers,
Stefan
Permalink
Hi Stephan,
we are investigating this currently. Which Windows version are your SP2016 machines running on?
Thanks,
Stefan
Permalink
Hi @all,
we get the same issue with the April CU for SP2016 after executing Configuration Wizard on all SharePoint server. All application pools get down.
Any ideas?
Regards
Christian
Permalink
Hi Christian,
I tested on two of my SP2016 farms and there no such problems occurred.
If you installed both patches (language dependent and language independent), restarted the machine and ran PSConfig and you get the same error I would recommend to open a ticket with Microsoft.
Cheers,
Stefan
Permalink
Yes, we installed both patches and finally executed psconfig on all server as recommended. We are using the Zero Downtime approach and the farm has 6 SharePoint server (2x WFEs, 2x App and 2x Search). We get the issue on all server. We patch the farm every month.
Permalink
We have the same issue on SP2016. We also patch every month. The issue started after we ran the sharepoint products configuration wizard. The SecurityTokenApplicationPool is not running on any server.
The Module DLL C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\isapi\sprequestfilteringmodule.dll failed to load. The data is the error.
A listener channel for protocol ‘http’ in worker process ‘2508’ serving application pool ‘SecurityTokenServiceApplicationPool’ reported a listener channel failure. The data field contains the error number.
Permalink
Hi Jan,
please open a ticket to get this analyzed.
Thanks,
Stefan
Permalink
Hi Jan,
we are investigating this currently. Which Windows version are your SP2016 machines running on?
Thanks,
Stefan
Permalink
Hello Stefan,
In case of this farm it is Windows Server 2012 R2 Standard, 6.3.9600
Thanks
Jan
Permalink
Windows Server 2012 R2 and the same Build as Jan Tkac
Permalink
This issue persists even with both patches installed.
As stated by Christian Dunkel, this seem to be related to “sprequestfilteringmodule.dll”. This module is referenced in:
C:\Windows\System32\inetsrv\config\appplicationHost.config (search for “sprequestfilteringmodule.dll”).
When you comment out that line pools are coming up and serving – but no clue of what else would be broken with this disabling.
Interestingly, we cannot find that DLL nor the according reference in the applicationHost.config on farms patched last month – so this seem to be introduced this month.
Permalink
Hi Malte,
this module is new in April CU and includes the AMSI integration for SharePoint Server 2016. As this is a new security feature permanently removing it is not recommended.
Of course you can do it for now to get unblocked but ensure to open a support case with Microsoft to get this analyzed as a permanent solution will be required.
Thanks,
Stefan
Permalink
Hi Malte,
we are investigating this currently. Which Windows version are your SP2016 machines running on?
Thanks,
Stefan
Permalink
Almost forgot, thank you for sharing the workaround Malte.
Permalink
no such issues in the three single server farms that I patched until now..
Permalink
Hi Stefan,
I am cooperating with Malte, we are running on Windows Server 2012 R2 Version 6.3 (Build 9600)
thanks
Vaclav
Permalink
We ran into the same error after April CUs. Commenting out the code in applicationhost.config does make the site work. We found out yesterday but I still opened up a PSS case. our servers run SharePoint 2016 and Windows Server 2012 R2 for a few more months.
Permalink
Hello, We have the same issue, on Windows 2012 R2. We worked around the issue by doing that, until an explanation is provided by Microsoft:
In IIS, go to server level and select Modules
On the right pane, click on Configure Native Modules
Select “SPRequestFilterModule” and click Remove
By the way, this DLL/Module seems to be new in SP2016, our farms with March CU do not have DLL C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\isapi\sprequestfilteringmodule on the file system.
Permalink
See here for explanation and mitigation of the issue:
https://blog.stefan-gossner.com/2023/04/14/trending-issue-503-response-on-sp2016-servers-running-on-windows-server-2012-r2-after-installing-april-2023-cu/
Permalink
I just patched our QA environment and ran Psconfig and ran into the same issue as everybody else, I applied (Malte) fix and was back online. The two IIS services that were not starting securitytoken and SharePoint Central Admin.
Permalink
Hi, after CU, we get unauthorized 401 when editing publishing pages which contain taxonomy fields.
the 401 error causes the page to repeatedly popup the login box.
on rest calls to /_vti_bin/TaxonomyInternalService.json/ValidateTerms
the same on _layouts/15/termstoremanager.aspx.
thanks
Permalink
Hi Miki,
please open a ticket with Microsoft to get this analyzed.
Cheers,
Stefan