SharePoint For Developers

“ Scroll to Top Search Result Page ” issue encounter while working with one of our client. Client has customized 2013 search center with branding (that includes all custom master page and layout pages) and because of this customization the scroll to top “ OOB ” functionality stop working. I have search a lot but only find one blog related to this issue, I need to must say thanks to this post help me to investigate on it. As per this blog you can enable this two ways. Web Part property to set “ScrollToTopOnRedraw” option to true. ( I checked by default it true for our ‘.webpart’ webpart. Update OOB Control template “Control_SearchResults.html” template and put “ctx.ClientControl.set_scrollToTopOnRedraw(true)” function at the top of Srch.U.shouldAnimate(ctx.DataProvider))condition. Below is the code snippets.  <div id="Control_SearchResults"> ctx.ClientControl.set_scrollToTopOnRedraw(true);  if (Srch.U.shouldAnimate(ctx.DataProvider)) { Srch.U.hideElem...

I found one most interesting issue while site collection migrated to 2010 to 2013. We have migrate SharePoint content DB 2010 to 2013 and found that the contextual search retuning the whole data for each search term no refiner working no “hit highlighting” but the result returned by the search service somehow. Every search term the service returned the same results. I have checked the same result in our search center as well in other site collection even checked contextual search all working fine as expected. So  only issue in the migrated site collection. I have mentioned the same issue on  MSND Question . To deep dive need to enable the VerboseEx log in the search farm and check what’s going behind the screen.I used the following command LETS (PowerShell) to enable the VerboseEx log. get-sploglevel | where {$_.Name -eq "Query"} | Set-SPLogLevel -TraceSeverity VerboseEx get-sploglevel | where {($_.Area -like "Search") -And ( ($_.Name -eq "Query Proc...

Today I came around this Result type issue with Multi type Managed Property. I have created one template & I wanted to show this template on particular condition. So I created the result type. The Managed property (MP) that I used, I have verified its attributes all attributes are selected and its type is Multi value. I am trying to apply the " conditions" and somehow the value not matched. I have checked MP ; it has all the values but somehow the template not called. When I removed this condition it working and when choose other MP other then Multi valued . It is working as expected. The details implementation.  Let me explain you more with example. Navigation to the schema link Under the Site Settings -> Site section click to the schema link. Verify that DisplayAuthor having all the required properties selected, the most important it must be Muti value . Next step would be crating the custom template. For that I need to map the drive and create th...

As we know Microsoft did lots of investment on improving the search architecture and did lots of changes in terms of UI prospective.  There are some of the common issue and well known, that I encounter during my development & search troubleshooting.   Below are the list of the common issues & the workaround to fix Automatic Crawl properties not created [Issue] This is known issue while creating the site column using declarative way the automatic crawled properties are not generated by the SharePoint engine.  [Solution]: The work around this either, need to create the Site columns using powershell or SharePoint object model . Display template not selected in the Content Search Webpart when we create the page using element.xml file. [Issue] The requirement where I have to create the layout pages and pre-populate the “content search web part” so I used the module feature for that & export the web part and add the same in the element. Xml f...

Week ago I had encountered the most common issue “Search has encountered a problem that prevents results from being returned”. I had searched lots of article and find diff-2 solutions. 1. Reset the Index 2. Custom Search Property not configured properly. 3. Search Index is degraded : Recreate the search service application from Central Administration In my case, I had a search page, where I had configured the content search web part and core result web part. Only my Search result web part was throwing error “Search has encountered a problem that prevents results from being returned” other webpart i.e. content search webpart was working fine. In my content search web part, I was using custom template and custom Managed Properties, so the first question comes in my mind. Was this related to the OOB MP issue? To make 100% sure about this, I need some proof, for this I had create one custom template and apply the same template in search result web part and I ...

SharePoint 2010 getting search keyword: we were writing a custom code to get the Search keyword & best bets, we used the FAST Search Proxy. The big bug found & that mentioned below. Special thanks for Mikael Svenson. He already did a lot of research on it. var ssaProxy = (SearchServiceApplicationProxy)SearchServiceApplicationProxy.GetProxy(SPServiceContext.Current); if ( ssaProxy.FASTAdminProxy != null ) Error line { var fastProxy = ssaProxy.FASTAdminProxy; KeywordContext keywordContext = fastProxy.KeywordContext; var searchGroup = (from x in keywordContext.SearchSettingGroups wherex.Name==SPContext.Current.Site.ID.ToString() select x).First();  } Above code was not working, the problem was Fast Search Service Proxy unable to connect with the search service. The FASTAdminProxy reads it’s WCF configuration from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\FASTSearchAdmin\ContentCollectionService\client.config. Se...

Search center Error message Sorry, Something went wrong.  correlation id 6661419c-0095-80c5-aec6-75e1cfadfb3f  ULS Log Error Details SharePoint Foundation         DistributedCache               ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedLogonTokenCache' - Exception 'Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0017>:SubStatus<ES0006>: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 th...