Share Technology Points

Hello SharePointers ;), Here is another quick finding which I just thought should be shared to save someone precious time. If you are dealing with SharePoint 2013 search and Result sources, you must try to test the query template before saving it. If you are not able to see any results instead just a red error saying below text don't get scared I have quick solution for you. “The Search display templates are not present on this site collection. To add them, you need to activate the “Search Server Web Parts and Templates” feature on the Site Collection Features page. Display Error: The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types. Template ‘~sitecollection/_Catalogs/masterpage/DisplayTemplates/System/Control_QueryBuilderPreview.js’ not found or has sytax errors. (Load Template: ) ” You must get frustrated because your search is properly configured, its crawling the ...

Hi, Issue : The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component ‘GUID’ in search application ‘Search Service Application’ is in a good state and try again. In Farm Search Administration page when click on " Modify Topology " get error "An unhandled exception occurred in the user interface.Exception Information: Exception has been thrown by the target of an" Cause : Search is not able to connect is because of name reasons, in this article I am explaining various the solution of this issue. Solutions : Please find the below solutions, That one of it can resolve the issue. Solution 1 : In the end it turns out to be that the application pool that hosts the search service application somehow doesn’t have the correct access. You can simply change the application pool to use SharePoint Web Services System for search service applications and check. 1. Click on Start > Run > Type Ine...

Hi Guys, I was facing a very strange issue since two three days. I just wasted lot of my time while solving it. After experiencing SharePoint 2013 service architecture, I was under the impression that MS have modified SharePoint this time that one will never face any issue while configuring the service applications. But I was wrong, I am talking about the Search service application here. If you are lucky then it may be the case that you will not see this issue but I wasn't actually explored the reason behind the issue. Issue Description: “Unable to retrieve topology component health states. This may be because the admin component is not up and running.” The default content source “Local SharePoint Sites” is inconsistent. It doesn’t always appear after creation of Search, sometimes with start addresses of existing web apps listed already, other times not. Starting a full crawl results in stuck in ‘starting’.                        Tried Solutions:  Installed all hotfixes by ...

SP 2010 provides all the basic search functionalists like MOSS 2007 search was providing. Along with default features it also facilitates end user with few interesting features. With batter enhancements in search query, new search model enables end users to create and run more effective search queries. It also enables users to search the enterprise from the Windows 7 desktop. Below are few new features listed: Boolean query syntax for free-text queries and for property queries Prefix matching for search keywords and document properties Suggestions while typing search queries Suggestions after users run queries Federated search connectors for searching the enterprise from Windows 7 Search results are also restructured to use refinement panel, improved in people search area, enhanced to display and filter only relevant results. In this post, I will start explaining from scratch to create/configure search service application and later on we discuss how we can configure custom sc...