Just a heads-up in case that you still have SharePoint environments running on SharePoint 2019: Mainstream support for SharePoint 2019 will end on January 9th, 2024: SharePoint Server 2019 – Microsoft Lifecycle After this date only security fixes will be provided for SharePoint 2019. Regular hotfixes can no longer be requested. If not already done […]
In May we identified an additional flavor of the distributed cache problem introduced with January 2023 CU which was not addressed with May 2023 CU: Application pools using a managed account that has been added after the farm was created might not be able to talk to the Distributed Cache server because these accounts are […]
May 2023 CU for SharePoint Server 2019 and Subscription Edition introduced an issue that affected custom solution deployment for farms where the SharePoint farm service account is a member of the local Administrators group. The symptoms are as follows: updating or retracting farm solutions takes a very long time IIS Application Pools for SharePoint web […]
Below are the security fixes for the SharePoint OnPrem versions released this month. SharePoint Server 2016: KB 5002425 – SharePoint Server 2016 (language independent) Microsoft Support recommends to install the complete July 2023 CU for SharePoint 2016 rather than individual security fixes. SharePoint Server 2019: KB 5002423 – SharePoint Server 2019 (language independent) Microsoft Support […]
The product group released the July 2023 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix. The KB article for July 2023 CU will be available at the following Location in a couple of hours: KB 5002423 – July 2023 Update for […]
In recent weeks we had a couple of discussions with customers planning to upgrade from SharePoint Server 2016 to SharePoint Server 2019. What was interesting to hear was that some customers were not aware that SharePoint Server 2016 and 2019 will both reach end of support on the same day: July 14th, 2026 As SharePoint […]
After installing June 2023 CU for SharePoint Server 2019 we received a couple of calls on a problem that creating or updating list items in modern experience not possible after June 2023 CU for SharePoint Server 2019. This affects lists and document libraries which contain hyperlink or picture columns. A fix for this issue was […]
Below are the security fixes for the SharePoint OnPrem versions released this month. SharePoint 2013: SharePoint 2013 has reached end of support. No further security fixes will be released for this product. Please update to a supported SharePoint version to ensure that your environment stays secure. SharePoint Server 2016: KB 5002404 – SharePoint Server 2016 […]
The product group released the June 2023 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix. The KB article for June 2023 CU will be available at the following Location in a couple of hours: KB 5002402 – June 2023 Update for […]
Thanks to several customer reports we identified an additional aspect of the distributed cache problem introduced with January 2023 CU which is not addressed with May 2023 CU. More details including the workaround to resolve the issue can be found in the update section of this blog post: Resolved – Trending Issue: Distributed Cache problems […]
After installing May 2023 CU for SharePoint Server 2019 and Subscription Edition we received a couple of calls around problems with custom solution deployment. A fix for this issue was released with July 2023 CU Symptoms updating or retracting farm solutions takes a very long time IIS Application Pools for SharePoint web applications remain in […]
With January 2023 CU for SharePoint Server 2016, 2019 and Subscription Edition we released a security fix which increased the transport security for communications between the SharePoint applications and the distributed cache cluster. This fix introduced a problem for some customers which so far could only be resolved using the workaround described in my blog […]
