Richard's SharePoint and Tech Blog

We were having a performance issue for our SharePoint environments.  We were also seeing a lot of errors related to the distributed cache in the ULS log Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedLogonTokenCache' - Exception 'Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode :SubStatus :There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater than or equal to the serialized object size sent from the client.) ---> System.ServiceModel.CommunicationException: The socket connection was aborted. This could be c...

I was working on a SharePoint hosted app with app part.  On my app part, it started getting this error when the page is loaded 'NotifyScriptLoadedAndExecuteWaitingJobs' is undefined After I searched online, I found the blog below from Corey.  This blog saved my day with the answer. http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2013/04/29/javascript-runtime-error-notifyscriptloadedandexecutewaitingjobs-is-undefined.aspx In case the above blog site is down for any reason, the fix is to simple add < script   type ="text/javascript"   src ="/_layouts/15/init.js"></ script > to your script reference on the app part page. My problem wasn't caused by the SP.Taxonomy.js but SP.Search.js.  The fix is the same and works for me. Hopefully, it'll help you!

From a project that I current is part of, the team realized that the user profile properties update is not picked up by the continuous crawl.  After opening a ticket with Microsoft to investigate further, it is confirmed by Microsoft that it is by design.  The recommended solution is to separate out the people information into a different content source and set a more frequent incremental crawl schedule.   It's too bad that it was designed this way.  But I guess it's not a big deal given the incremental crawl still works.