SharePoint security fixes released with July 2021 PU and offered through Microsoft Update

Below are the security fixes for the SharePoint OnPrem versions released this month.

Important:
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 5001992 – SharePoint Foundation 2013 (core component)
  • KB 5001996 – SharePoint Foundation 2013
  • KB 5001984 – SharePoint Server 2013 (core component)
  • KB 5001986 – Office Web Apps Server 2013
  • Microsoft Support recommends to install the complete July 2021 CU for SharePoint 2013 rather than individual security fixes

SharePoint 2016 Suite:

  • KB 5001976 – SharePoint Server 2016 (language independent)
  • KB 5001981 – SharePoint Server 2016 (language dependent)

SharePoint 2019 Suite:

Office Online Server:

  • KB 5001973 – Office Online Server
See the Security Update Guide below for more details about the relevant fixes:

More information:

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
 

11 Comments


  1. Stefan,

    Hoping for a bit of advice here. One of our servers development Sharepoint servers had KB5001984 installed on it by an automated patching service which left the site in an broken state. We are currently unable to access any functions on the site (site settings, site contents, add a page, etc.) without getting the dreaded “Sorry, something went wrong”. When I look up the correlation ID in the ULS, the following lines are listed:

    DelegateControl: Exception thrown while adding control ‘Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource’: System.MissingMethodException: Method not found: ‘Boolean Microsoft.SharePoint.Utilities.SPUtility.SafeForDataBinding(System.Reflection.Assembly, System.Reflection.Assembly, System.String)’. at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.get_PortalProvider() at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl) 4e2ade9f-1524-f085-c49b-41770f8384cf
    07/22/2021 18:06:05.85 w3wp.exe (0x1A04) 0x3D9C SharePoint Foundation General 8sl1 High DelegateControl: Exception thrown while adding control ‘Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource’: System.MissingMethodException: Method not found: ‘Boolean Microsoft.SharePoint.Utilities.SPUtility.SafeForDataBinding(System.Reflection.Assembly, System.Reflection.Assembly, System.String)’. at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.get_PortalProvider() at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl) 4e2ade9f-1524-f085-c49b-41770f8384cf
    07/22/2021 18:06:05.85 w3wp.exe (0x1A04) 0x3D9C Web Content Management Publishing 8vzc High PortalSiteMapProvider was unable to fetch root node, request URL: /_layouts/15/settings.aspx, message: Method not found: ‘Boolean Microsoft.SharePoint.Utilities.SPUtility.SafeForDataBinding(System.Reflection.Assembly, System.Reflection.Assembly, System.String)’., stack trace: at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.get_CurrentSite() at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.get_ObjectFactory() at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.GetRootNodeCore() 4e2ade9f-1524-f085-c49b-41770f8384cf
    07/22/2021 18:06:05.85 w3wp.exe (0x1A04) 0x3D9C SharePoint Foundation General 8sl1 High DelegateControl: Exception thrown while adding control ‘Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource’: System.MissingMethodException: Method not found: ‘Boolean Microsoft.SharePoint.Utilities.SPUtility.SafeForDataBinding(System.Reflection.Assembly, System.Reflection.Assembly, System.String)’. at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.get_PortalProvider() at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl) 4e2ade9f-1524-f085-c49b-41770f8384cf
    07/22/2021 18:06:05.85 w3wp.exe (0x1A04) 0x3D9C SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/settings.aspx, Error=The DataSourceID of ‘TopNavigationMenu’ must be the ID of a control of type IHierarchicalDataSource. A control with ID ‘topSiteMap’ could not be found. at System.Web.UI.WebControls.HierarchicalDataBoundControl.GetDataSource() at System.Web.UI.WebControls.HierarchicalDataBoundControl.ConnectToHierarchicalDataSource() at System.Web.UI.WebControls.HierarchicalDataBoundControl.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System…. 4e2ade9f-1524-f085-c49b-41770f8384cf

    We have attempted to install the June 2021 Cumulative Update (KB5001961) multiple times to no avail. The errors above still persist. Do you have any recommendations on how to proceed?

    Reply

    1. Hello. I have the same problem. Can you please let me know how you resolved it?

      Thank you

      Reply

  2. Hi Eric,

    I am encountering the same issue, were you able to fix it?

    Reply

  3. If one of your servers has a July updates, it’s not a good idea to attempt to install the June updates on the other servers. Why not just install the July update on your other three servers as well?

    Reply

    1. Hi Matthew,
      the article you quoted includes the instructions from Nintex what to configure to ensure that Nintex workflows are working again with the security fix applied.
      Out of the box SharePoint workflows should work. If not you should open a support ticket with Microsoft.
      The following article includes all the details:
      https://support.microsoft.com/en-us/topic/some-scenarios-of-sharepoint-2010-workflow-are-affected-after-applying-the-july-security-update-for-sharepoint-server-kb5004862-be361cd6-9f54-48c4-b890-2c4b7cf49d13
      Cheers,
      Stefan

      Reply

    2. thank you Matthew Huggett! Your comment about Nintex saved my bacon today! I have SharePoint 2016 and 2019 farms running Nintex workflows and experienced an issue where the workflows failed to start.

      Reply

  4. You might want to update the “SharePoint 2019 Suite” in this post to list the language pack as well as you did in your other blog posthttps://blog.stefan-gossner.com/2021/07/13/july-2021-cu-for-sharepoint-server-2019-is-available-for-download/.

    I found that in this particular update, if you don’t apply it, the Modern sites have a symptom of “blank white page” when you access a modern library or the Site Contents. Once I installed the language pack KB5001974, the problem went away.

    P.S. Thanks for always keeping us up to date on the latest updates. Your blog is my go-to for updates.

    Reply

    1. Hi Dominique,
      the current post only lists the security fixes – not the non-security fixes.
      We recommend to always install both fix packages and not just a single one as there are often dependencies between language dependent and language independent packages of a CU.
      Cheers,
      Stefan

      Reply

Leave a Reply to Dominique Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.