The product group released the July 2020 Cumulative Update for the SharePoint 2013 product family.
For July 2020 CU we have full server packages (also known as Uber packages) for all products. No other CU is required to fully patch SharePoint.
As this is a common question: Yes, July 2020 CU includes all fixes from July 2020 PU.
ATTENTION:
Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first.
Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).
Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.
This CU includes all SharePoint 2013 fixes (including all SharePoint 2013 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.
The KB articles for July 2020 CU should be available at the following locations in a couple of hours:
- KB 4484444 – SharePoint Foundation 2013 July 2020 CU
- KB 4484447 – SharePoint Server 2013 July 2020 CU
- KB 4484445 – Project Server 2013 July 2020 CU
- KB 4484357 – Office Web Apps Server 2013 July 2020 CU
The Full Server Packages for July 2020 CU are available through the following links:
- Download SharePoint Foundation 2013 July 2020 CU
- Download SharePoint Server 2013 July 2020 CU
- Download Project Server 2013 July 2020 CU
- Download Office Web Apps Server 2013 July 2020 CU
After installing the fixes you need to run the SharePoint 2013 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.
Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Info:
- Technet: Updated Product Servicing Policy for SharePoint 2013
- 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
- Blog: Support for SharePoint 2013 RTM has ended
- Blog: SP1 for SharePoint 2013
- Technet: CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- Technet: Install a software update for SharePoint 2013
- Blog: How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SQL Server 2014 and SharePoint Server 2013
Permalink
The KB 4484447 – SharePoint Server 2013 July 2020 CU is not available for download.
Permalink
Hi Leonard,
I tested and I can download them. Please try again.
Thanks,
Stefan
Permalink
Recently installed June 2020 CU without issues on the same environment. Single server SP2013 … Now with July 2020 CU config wizard fails. In the Application event log I can see this:
Failed to upgrade SharePoint Products.
An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Invalid object name ‘Webs’.
System.Data.SqlClient.SqlException (0x80131904): Invalid object name ‘Webs’.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action
1 wrapCloseInAction)
1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, Boolean retryForDeadLock)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseIntegrity.CheckMissingWebTemplates(Boolean showLocation)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseIntegrity.Check(SPContentDatabaseIntegrityCheckOptions options)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.ContentDatabaseDataIntegrityCheck()
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.PreUpgrade()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Administration.SPContentDatabase.<>c__DisplayClass2.b__0()
at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)
at Microsoft.SharePoint.Administration.SPContentDatabase.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
ClientConnectionId:1863b153-a2aa-406e-88fe-cb89ec4802ec
Error Number:208,State:1,Class:16
Anyone else?! 😉
Permalink
Hi Michael,
seems some views are missing in one of your content databases or the account used to upgrade the content DB does not have rights on them.
I would recommend to open a ticket with Microsoft to analyze this in more details.
Cheers,
Stefan
Permalink
Thanks!
I already did so (MS case) and meanwhile I could identify the faulty database. Seems I don’t need this one as this is just a db for testing and demo purpose. However, I’m curious how this could happen as I’m sure nobody touch the database directly via SSMS or something …
Permalink
Dismounted the “faulty” database, restarted machine etc. Now getting other error not indicating anothing about database issues …
Still waiting for response on my case …
Failed to upgrade SharePoint Products.
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type ‘Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException’ was thrown.
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
Permalink
Hi Michael,
you should be able to get more details from the psconfig log file to see what went wrong.
Cheers,
Stefan
Permalink
We had to delete some kind of stuck one-time timer jobs and restart the wizard. Now it completed successfully. Strange things happen 😉 Almost forget about that …
Permalink
Is KB4484348 included in the KB4484447 CU for SP 2013?
Permalink
Yes
Permalink
Thanks, is there a list out there of all the KBs included in a cumulative update?
Permalink
Hi Neal,
I’m not sure what exactly you are looking for: the CU includes all the previously released fixes since SP1. So that are several hundred fixes.
About this specific one: if you open the CU kb you will see the KBs that are included from the same month.
And here you can see that KB4484447 includes KB4484348.
Cheers,
Stefan
Permalink
Hi Stefan
I have a problem on my application server with CA, I did install KB4484447 and only on this server I get the error “15.0.5259.1001 Missing/Required”.
My farm consists of a frontend, a search server, an Office WebApp server and an application server with CA.
Example:
EU1-SPAPS-02 Microsoft Search Server 2013 German Language Pack 15.0.4569.1506 Installed
EU1-SPAPS-02 Security Update for Microsoft SharePoint Enterprise Server 2013 (KB4484443) 64-bit Edition
15.0.5259.1001 Missing/Required
The wizard shows the same problem as the CA.
Can you help me?
Best
Ronny
Permalink
Hi Ronny,
I would suggest to run “get-product -local” on all servers in the farm to ensure that the info about the installed patches gets refreshed in the config database.
If the issue persists:
is it possible that you installed 4484443 on one of the servers – potentially before you installed 4484447 while on other servers only 4484447 was installed?
I would suggest to double check in control panel in the installed updates.
Cheers,
Stefan
Permalink
Hi Stefan
thanks for your answer.
Yes after my installation i got the info that (KB448444444) is missing.
I installed that too and then he still complained. Now there was nothing left for me but the CU (KB4484447) but also no improvement. After that I ran PSConfig twice, my Application- and Search Server are ok and the Databases also. But the Frontend Server can’t be fixed. Here the last two steps in PSConfig are missing.
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
I get a null Reference Exception at Frontend server:
Install-SPApplicationContent
Best,
Ronny
Permalink
My Exception message at Frontend server:
Failed to install the application content files.
This is a critical task. You have to fix the failures before you can continue.
An exception of type System.NullReferenceException was thrown. Additional exception information: Object reference not set to an instance of an object.
Permalink
Hi Ronny,
I haven’t seen this and would recommend to open a ticket with Microsoft Support to get this analyzed in more detail.
Cheers,
Stefan
Permalink
I installed version kb4484443 and from that moment part of the site in sharepoint showed me “sorry something went wrong”
Does anyone know what could be the problem?
Permalink
Hi Shay,
I would suggest to check the ULS log for a problem when loading the page.
If you need assistance I would recommend to open a support ticket with Microsoft.
Cheers,
Stefan
Permalink
Hello Stefan,
Hope you are doing well.
I would like to know if CVE-2020-1447 is included in JULY CU for SharePoint 2013 ?
And if it’s stable version ? We are in 15.0.4569
Many thanks in advance.
Best,
Rafa
Permalink
Yes, it is included.
As always test the fix in a test environment against your business critical features to ensure that it does not cause negative side effects before installing on production as it is not possible to uninstall SharePoint fixes.
Cheers,
Stefan
Permalink
Thank you very much for your feedback Stefan.
I will deploy it on our test environment before planning the production.
Cheers,
Rafa