August CU 2013 has been released.

August 2013 CU for SharePoint 2013 has been released

August 2013 CU for SharePoint 2010 has been released

Note For SP2:
* It is recommended to install June 2013 CU before SP2. June 2013 CU might not correctly identify the SP2 baseline. If SP2 has already been installed and June CU does not install you need to install  August CU which will correctly identify the SP2 baseline.


June 2013 CU for SharePoint 2010 has been re-released

“The product group has now re-released the June 2013 Cumulative Update for the affected products including SharePoint.Be aware that the KB article numbers of the re-released Fixes are different from the original ones.The KB articles are not yet available but should be in the next couple of days. The fixes can already be downloaded. It is strongly recommended that customers who installed the initial June CU install the re-released updates.”

june 2013 CU for sharepoint 2007/2010/2013 has been released

June 2013 CU for SharePoint 2007/2010/2013 has been released.

SharePoint February 2013 CU updates for 2007 and 2010 product family has been released.

SharePoint February 2013 CU updates for 2007 and 2010 product family has been released.

You can find details ;


Multiple Navigation Nodes Problem and Navigation Deadlock in SharePoint 2010

Issue happens after  August 2012 CU installed for SharePoint Server 2010.

After publishing a new page the site load times start to increase dramatically or page requests don’t finish loading at all. You will see the infamous “An expected error has occurred“-error or if the callstack is enabled and custom errors are turned off in the web.config (CallStack=”true” / customErrors mode=”Off”) you will see a “Request timed out.” error-message.

System.Data.SqlClient.SqlException: Transaction (Process ID 76) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.HasMoreRows()
at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
at Microsoft.SharePoint.SPSqlClient.ExecuteQueryInternal(Boolean retryfordeadlock)
at Microsoft.SharePoint.SPSqlClient.ExecuteQuery(Boolean retryfordeadlock)

PortalSiteMapProvider was unable to fetch children for node at URL: /<site>, message: An unexpected error occurred while manipulating the navigational structure of this Web., stack trace:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.UpdateNavigationNode(String bstrUrl, Int32 lNodeId, DateTime dateParented, String bstrName, String bstrNodeUrl, Object& pvarProperties, String& pbstrDateModified)
at Microsoft.SharePoint.Navigation.SPNavigationNode.Update()

 SharePoint April 2013 CU

For more details and for workarounds :