Below are the security fixes for the SharePoint OnPrem versions released this month.
SharePoint Foundation security fixes also have to be applied on SharePoint Server installations.
SharePoint Server security fixes also have to be applied on Project Server installations.
SharePoint 2013 Suite:
- KB 4011600 – Visio Services for SharePoint 2013
- Microsoft Support recommends to install the complete August 2021 CU for SharePoint 2013 rather than individual security fixes
SharePoint 2016 Suite:
- KB 5002002 – SharePoint Server 2016 (language independent)
- Microsoft Support recommends to install the complete August 2021 CU for SharePoint 2016 rather than individual security fixes
SharePoint 2019 Suite:
- KB 5002000 – SharePoint Server 2019 (language independent)
- Microsoft Support recommends to install the complete August 2021 CU for SharePoint 2019 rather than individual security fixes
Office Online Server:
See the Security Update Guide below for more details about the relevant fixes:
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
will this CU address to the issues happened with previous patches?
hard to say as you did not specify the issues you are looking for a solution.
Did you have a look at the KB article for the fixes?
They include information about the issues that were fixed.
I meant for error raised regarding custom assemblies, which you already wrote another blog. Thanks.
Do you recommend running PSCONFIG on 2013, given that the 2013 update is simply for Visio services? It would be nice not to have to PSConfig if not necessary.
all SharePoint fixes require PSConfig.
First, thanks for the great resource that I’ve used for years and saved enormous amounts of time.
We’ve always followed your recommendation to install security patches as soon as possible, but only install CUs if it contains a fix for an issue we are experiencing, or, if directed to install the CU by Microsoft Support.
What can I tell my boss as to why this month is unique and it’s recommended to install the CU?
with SharePoint 2016 – we changed our recommendation to always install both fixes: language dependent and language independent and not just one of them as these components have dependencies on each other.
So in case your question is about SP2016 or SP2019 then this was always our recommendation.
Sorry, should have been more specific. I’m asking about SP2013. I see the last few months it’s been recommended to install the full CU for SP2013. Was wondering why the change in guidance from recommending installing just the security patches in the PU each month, to installing the full CU each month. And, will installing the full CU each month be the recommendation going forward in future months for SP2013?
in general Microsoft Support always recommends this as internal testing is only done on a consistent patch level as it is impossible to test all CU/security fix combinations.
With the recent security fixes we also have seen more issues caused by incompatbilities between different patch levels of the 30+ packages.
After all SharePoint components interact with each other and a change in one component which works good with components on the same patch level might have issues if the involved components are on older patch levels.
Thanks for that explanation, it totally makes sense now.
We are having PS config error for project web Content database, are they any known issues with August 2021 CU?
Failed to upgrade SharePoint Products.
This is a critical task. You have to fix the failures before you can continue. Follow this link for more information about how to troubleshoot upgrade failures: https://go.microsoft.com/fwlink/?LinkId=866803
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
FirstLine should start with ‘CREATE’: /**/ (EventID:an28z)
Upgrade [SPContentDatabase Name=ProjectWebApp] failed. (EventID:an59t)
Exception: Specified argument was out of the range of valid values.Parameter name: sLine (EventID:an59t)
there is currently no known issue similar to this.
The error you have seen usually occurs if unsupported changes have been made to the content database.
E.g. by installing a 3rd party software which adds custom stored procedures or tables to the database which is unsupported.
Please review the database for any unsupported modifications and revert them.