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 :

December 2012 CU for SharePoint 2010 has been released

Please Read for more Details:

Next Cumulative Update (August 2012) can only be install with SP1 installed farms/server.

If you don’t install SP1 on your SharePoint 2010 farm yet ,  Please read the fallowing post

About Sorting problem on Picture Library in Sharepoint 2010 after installing Dec 2011 CU

Hello Everyone,

We have a problem for sorting on Picture Libraries in Sharepoint 2010 . I have tested the issue SPS2010 + SP1 + Dec 2011 CU and can be easly reproducable.
The problem is when you click “Column” links or click popup window Ascending or Descending links nothing happens .Thats mean you can not able to sort items in Picture Libraries.
As far as i know it was working on SP1 level . The problem has occuring after CU upgrade.

Does any fix ? Not yet .(12/03/2012) I am expecting but not sure in June CU 2012 will fix the issue.
So until then you can use fallowing workaround to fix issue.

It is very simple wsp file created as site scope that dispatching postback events on picture libraries by using Jquery.
You can download WSP or Source project form Codeplex.

For installing solution:

1) Download “PictureLibraryFix.wsp” file to c: drive of your sharepoint server

2) Open a Sharepoint Management Shell and

3) Type fallowing for adding solution to sharepoint
Add-SPSolution -LiteralPath c:\PictureLibraryFix.wsp

4)Type fallowing for installing solution:
Install-SPSolution -identity picturelibraryfix.wsp -GACDeployment

5)Type fallowing for enable feature on specific site collection:
Enable-SPFeature -Identity 8af7cb42-0fc7-4aa6-91e8-e1d1993b34cc -url http://blog.bugrapostaci.com




Unable to complete upgrate after installing Aug 2011 Cu for Sharepoint 2010 and getting error of Exception: localStoragePath

Every upgrade attemp is one of challage for IT team. So this time we are working on a problem which is occured after Aug 2011 Cumulative Update.
the symptom is Sharepoint Configuration Wizard can not able to complete and finishing with failure.

First of all once we check the PSCDiagnostics logs we could not able to find something useful:

Configuration of SharePoint Products failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\PSCDiagnostics_10_7_2011_9_55_26_860_989474110.log, fix the problem, and run this configuration wizard again

Cool but it say nothing. So we peek that let check “upgrade” logs …
And see some error. LocalStoragePath. What is actually LocalStoragePath and why we are getting this error while upgrading. It is definitly something wrong with search db.

[OWSTIMER] [SPUpgradeSession] [ERROR] [10/7/2011 10:05:49 AM]: Exception: localStoragePath
[OWSTIMER] [SPUpgradeSession] [INFO] [10/7/2011 10:05:49 AM]: SearchAdminDatabase Name=Fast_Query_SSA_DB_3a64d349dc2249679a8be
[OWSTIMER] [SPUpgradeSession] [ERROR] [10/7/2011 10:05:49 AM]:    at Microsoft.Office.Server.Search.Administration.SearchApi.AssertParameter(String parameterName, Boolean condition)
   at Microsoft.Office.Server.Search.Administration.SearchApi.UpdateAdminComponent(String serverName, Guid serverId, String localStoragePath, Boolean standalone, Nullable`1 settingsInRegistry)
   at Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence.InitializeTopologyBasedOn2007Settings()
   at Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence.PostUpgrade()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

The problem in our scenario is some how psconfig can not update the topology, possible cause for this may be service name changes may be an old conf. backup restored or even more the server name has changed.  


1. Checked the Upgrade error log and notice following information
[OWSTIMER] [SPUpgradeSession] [INFO] [10/7/2011 10:05:49 AM]: SearchAdminDatabase Name=Fast_Query_SSA_DB_3a64d349dc2249679a8be…

2.Use Get-SPEnterpriseSearchServiceApplication cmdlet and list all search service applications. we try to delete the Search Service Application. Unable to delete the service Application through GUI hence tried successfully with following Powershell command.

$ssa = Get-SPEnterpriseSearchServiceApplication -Identity 4e6d0c5c-f47b-425e-a637-e8a44aca12ae

We had 2 search application more so we deleted all of them .

3. Run the configuration wizard

4. created a new SSA to after configuration wizard has run.