SharePoint 2013 March 2016 CU

Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint 2013? Read more in the post from my colleague Stefan.

New since April 2015:

  • You need to have SP1 installed!
  • In case you have installed a SP1 slipstream version, please read the article from my colleague Stefan!!!
  • Search enabled Farm, please check as well this article.

The format how we are providing the Cumulative Update packages has changed in 2015, means you can find all packages on our Download Center.

When you reached the download website, it is independent which language you chose, the packages are the same.

Plan to upgrade carefully, you may need more time in case the current patch level for your Farm is June 2015 or earlier! Reason is in regards to Search and psconfig. Please check the post from my colleague Stefan!


SharePoint Foundation 2013
3114822 The full server package for SharePoint Foundation 2013

Download link:

SharePoint Server 2013
3114827 The full server package for SharePoint Server 2013 and contains also the SharePoint Foundation 2013 fixes so you need only this package.

Download link:


Office Web Apps Server 2013
3114821 Microsoft Office Web Apps Server 2013 hotfix package

This package contains also a security fix for OWAS.

Download link:


Project Server 2013
3114823 The full server package for Project Server 2013 and contains also the SharePoint Server and Foundation 2013 fixes so you need only this package.

Download link:


Important for all Server Applications listed above:
After any binary update you need to run psconfig or psconfigui. Please refer to the following article to find out what is the best for you: why-i-prefer-psconfigui-exe-over-psconfig-exe.aspx

You might have you own strategy to run psconfig, because it depends on the farm structure and what makes sense to reduce the downtime.

As soon as possible (in case patch level of your Farm is June 2015 or earlier) after you installed the binaries, run the psconfig! Reasons are here.

Related Info:

Update Center for Microsoft Office, Office Servers, and Related Products

October 2015 Office Update Release by sustain engineering team
Common Question: What is the difference between a PU, a CU and a COD?

How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled

CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging

SQL Server 2014 and SharePoint Server 2013

Comments (2)

  1. Marcus says:

    Since applying the March 2016 CU for SharePoint 2013 we have encountered a problem with the contribute permission level and being unable to add documents to SharePoint where the require check in and out is turned on.

    The error(s) we receive:

    System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.

    at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex)

    at Microsoft.SharePoint.SPSecurableObject.CheckPermissions(SPBasePermissions permissionMask)

    at Microsoft.SharePoint.SPList.CheckPermissions(SPBasePermissions permissionMask)

    at Microsoft.SharePoint.SPSecurity.ValidateSecurityOnOperation(SPOperationCode code, SPSecurableObject obj)

    at Microsoft.SharePoint.SPSecurityOnOperationScope..ctor(SPOperationCode code, SPSecurableObject obj)

    at Microsoft.SharePoint.SPDocumentLibrary.get_CheckedOutFiles()

    at MAPILab.SharePoint.Statistics.EventReceivers.MLSiteScopeItemEventReceiver.c__DisplayClass7.b__0()

    at Microsoft.SharePoint.SPSecurity.c__DisplayClass5.b__3()

    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)

    at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)

    at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)

    at MAPILab.SharePoint.Statistics.EventReceivers.MLSiteScopeItemEventReceiver.ProcessItemEvent(SPItemEventProperties properties)

    at MAPILab.SharePoint.Statistics.EventReceivers.MLSiteScopeItemEventReceiver.OnItemEvent(SPItemEventProperties properties)

    Followed by:
    System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

    at Microsoft.SharePoint.Library.SPRequestInternalClass.GetFileAndFolderProperties(String bstrUrl, String bstrStartUrl, ListDocsFlags ListDocsFlags, Boolean bThrowException, Int32& phrStatus, Object& pvarFiles, Object& pvarDirs, UInt32& pdwNumberOfFiles, UInt32& pdwNumberOfDirs)

    at Microsoft.SharePoint.Library.SPRequest.GetFileAndFolderProperties(String bstrUrl, String bstrStartUrl, ListDocsFlags ListDocsFlags, Boolean bThrowException, Int32& phrStatus, Object& pvarFiles, Object& pvarDirs, UInt32& pdwNumberOfFiles, UInt32& pdwNumberOfDirs)

    at Microsoft.SharePoint.SPWeb.GetFileOrFolderProperties(String strUrl, ListDocsFlags listDocsFlags, Boolean throwException, SPBasePermissions& permMask)

    at Microsoft.SharePoint.SPFile.PropertiesCore(Boolean throwException)

    at Microsoft.SharePoint.SPFile.get_Length()

    at Microsoft.SharePoint.ApplicationPages.UploadPage.OnSubmit(Object o, EventArgs e)

    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    How do I go about reporting a bug on this CU ?

    I’ve noticed by changing the contribute permission level to include the additional option:

    Override List Behaviors – Discard or check in a document which is checked out to another user, and change or override settings which allow users to read/edit only their own items. This issue goes away, however this is not a fix

    has anyone else experienced this, can anyone else confirm it is a bug

    1. Reading MAPILab.SharePoint.Statistics.EventReceivers in a CallStack sounds always suspicious and would need to investigate at that point. What happens when this event receiver is not visible in the CallStack? In case you would need a support case, please add to that also the source for this particular event receiver, so that everyone can reproduce the issue.

Skip to main content