About October CU 2013 for SharePoint 2010 server build version

In official documentation (October2013 CU for SharePoint Server 2010 – KB 2825786) states that the Oct CU for SP2010 has the build number 14.0.7110.5000. However, after installing the CU and checking the Central Administration you can see the Configuration database version: 14.0.7108.5000.

The reason for this discrepancy is that mostly only the Search DLLs have the higher (14.0.7110.5000) version number: both Microsoft.SharePoint.dll and the CA portal show 14.0.7108.5000. so in case you see this in your environment

– there is nothing wrong here.

(Thanks to Piotrek)

 

SharePoint 2013 October 2013 CU

SharePoint 2013 October 2013 CU has been released;

http://blogs.msdn.com/b/joerg_sinemus/archive/2013/10/10/sharepoint-2013-october-2013-cu.aspx

 Be aware that all Updates for SharePoint 2013 require March 2013 PU for SharePoint 2013 to be installed first.

Prevent caching for specific files in SharePoint

Assume following scenario that you have a SharePoint environment and all cachings are enabled . Caching is very efficent for documents which are not change frequently . What if you have dynamically and frequently changing xml,js,txt or a css file . so how could you provide to bypass only needed files are not being cached and other leave other same type files be cached.

There is an ASP.NET trick for this purpose. Assume that we have a menu.xml and this file is updating by some Operations on server and this operation happens very frequently. But your clients could not get updated file until they completely clear their browser caches. You dont want to be prevent every xml files to be not cached .
Basically caching machanizms has deciding to cache files by checking url syntax. If you have change the url somehow you can prevent the cache. We usually provide this by adding a fake version query string like menu.xml?ver=1 at the end of the url . and increasing this parameter when ever we changed the file. For some examples you can aslo use GUIDs for this.

1)Create a test.js file and type following codes. You may also integrate this to your own page directly.

function CreateDigits() {
return (((1 + Math.random()) * 0x10000) | 0).toString(16).substring(1); }
function createGuid() {     return (CreateDigits() + CreateDigits() + “-” + CreateDigits() + “-4” + CreateDigits().substr(0, 3) + “-” + CreateDigits() + “-” + CreateDigits() + CreateDigits() + CreateDigits()).toLowerCase(); } //alert(createGuid());

$.get(‘/_layouts/menuxml/menu.xml’ + ‘?ver=’ + createGuid() , function (data) {     //do operations.     alert(‘Load was performed.’); });

2) Add test.js to your masterpage
<script type=”text/javescript” src=”/_layouts/test.js” ></script>

3) Use IE developer Panel (F12) or  Firefox Firebug plugin or Fiddler2 program on your client  check that menu2.xml is loading when you request the file.

You should see the menu.xml file request has contain ?ver=<GUID> notation.

4) Update your Javascript files where loading  XML file according to example.

5) And test the change xml file and check still browsers caching the file

What we basically do ?

Following codes has creates a GUID function CreateDigits() While we requesting the xml file we adding end of the url of the file this GUID as a parameter for every request it will creates another guid. Like http://<site>/_layouts/menuxml/menu.xml?ver=bca7f319-5627-4d22-48f6-4c3e59285199

So it will provide that every request on client is unique and force the clients update XML file for every time. This is the basic logic you can develop yours based on this.

Resources:
http://guid.us/GUID/JavaScript

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 ;
http://blogs.technet.com/b/stefan_gossner/archive/2013/02/13/feburary-2013-cu-for-sharepoint-2007-has-been-released.aspx
http://blogs.technet.com/b/stefan_gossner/archive/2013/02/13/february-2013-cu-for-sharepoint-2010-has-been-released.aspx

 

Multiple Navigation Nodes Problem and Navigation Deadlock in SharePoint 2010

Symtoms:
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()

Resolution:
 SharePoint April 2013 CU

For more details and for workarounds :
http://blogs.msdn.com/b/joerg_sinemus/archive/2013/02/12/february-2013-sharepoint-2010-hotfix.aspx