The product group released the March 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 March 2023 CU should be available at the following locations in a couple of hours:
- KB 5002368 – March 2023 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 5002325 from February 2023 CU.
The downloads for March 2023 CU are available through the following links:
- Download March 2023 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 5002325 from February 2023 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 March 2023 CU Build Numbers:
Language independent fix: 16.0.5387.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,
Distributed Cache issue which was reported in Jan 2023 CU is it resolved in this CU ?
Thank you
Permalink
Hi Subhash, no a fix is still in the works. Current plan is to have a fix with May CU but it might be even later as there are several changes required and intensive testing is required as well.
Permalink
Thanks for the update.
Permalink
Hello Stefan,
after applying the MArch 2023 CU for SharePoint server 2016, our customer have a problem with open drop-down menu and display the data contained within it ( is a custom web part ).
This is the error:
WebHost failed to process a request.
Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/34226248
Exception: System.ServiceModel.ServiceActivationException: The service ‘/_vti_bin/client.svc’ cannot be activated due to an exception during compilation. The exception message is: The Web application at http://“servername”/_api/Microsoft.SharePoint.Portal.SuiteNavData.GetSuiteNavData?v=2&Locale=en-US could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.. —> Microsoft.SharePoint.SPException: The Web application at http://“servername”:43210/_api/Microsoft.SharePoint.Portal.SuiteNavData.GetSuiteNavData?v=2&Locale=en-US could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.
at Microsoft.SharePoint.Utilities.SPUtility.ConfigServiceHostIfClaimsAuth(ServiceHost serviceHost)
at Microsoft.SharePoint.Client.SPClientServiceHost.OnServiceHostOpening(ServiceHost serviceHost)
at Microsoft.SharePoint.Client.Services.MultipleBaseAddressWebServiceHost.OnOpening()
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
— End of inner exception stack trace —
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result)
Process Name: w3wp
Process ID: 10788
Any idea about this ?
Thank you very much
Permalink
Hi Roberto,
I assume this is related to some customizations applied to SharePoint. Its hard to say what goes wrong here.
Did you verify that the servername is for the correct AAM zone?
If you are not the developer of the customization I would recommend to involve him to troubleshoot the issue.
If you are the developer or if the developer needs assistance to get this resolved I would recommend to open a ticket with Microsoft Support to investigate this.
Cheers,
Stefan