We have a requirement in our project where we have to fetch the search result from a given list. Additionaly we have to display some columns from the list in serch result display.
We found a good article from Andy Burn's blog for how to do this.
This is one of the worst problem I came across. :(
I don't blame Microsoft for this, but I can say a wrong governance model is the reason for this.
Problem: My client complaint that a new item added on the site is not comes under a search result since last few days. I spent lot of a time to find out the real cause. When I have gone through the Search Crawling log an error is found saying "The parameter is incorrect in sharepoint search". When I checked for all the other sites on the farm all are working fine with search and none of the site has given such error at the time of crawling. That has increased my curiosity.
After spending a full day at last I found a reason and its a cause for small party ;), thanks to Mattias Lindberg
Solution: The reason which stops the crawling for the site is the user we have added in the site are more than 5000 in a particular group instead of adding an AD Group.
I am just copying the workaroung given by Mattias below.
Our solution was to require sites with over 1500 members to use an AD group for keeping track of membership, as recommended by the KB for SPS 2003. One disadvantage with this approach is that you must maintain membership by updating the AD group so you can no longer request membership using SharePoint standard dialogs.
Probably an article is wriiten for SPS 2003 but infect it is applied to MOSS 2007 as well.
A very good article on Twitter Search in SharePoint with screen-shots from Woody on EndUserSharePoint.Read more...
Today, at time of searching the net in my free time. I was looking at to improve some search feature in sharepoint like providing Search As-You-Type kind a functionality what Bing or Google is providing.And you know what, Jan Tielens has already did this :).Read more...
One of the things that people are not aware of is that you can customize the search results coming from the SharePoint search engine. The results, which is XML, given by the engine are styled using XSLT. If you create your own XSLT you can customize/restyle your results page.
There is a 'Visual How To' by Patrick Tisseghem explaining the steps you need to do to customize the search page.
You can do the same trick with the Best Bets meaning, you can customize them by applying your own XSLT. Before we are going to customize the Best Bets, Kevin explains what they do an how you can use them.
Best Bets are used to promote some results depending on your search keywords. If you look at the screenshot below you see that when I type SharePoint in the search box, U2U and Microsoft are pushed forward as results where you definitely can find something about SharePoint. So if you think about it, Best Bets is a way for an administrator to earn some extra money, the one who pays the most gets on top of the list.
MOSS Faceted Search is a set of web parts that provide intuitive way to refine search results by category (facet). The code is available on CodePlex.
This example shows the basic process of creating and implementing a delegate control candidate to use for the search box that is displayed on site pages. The control specifies alternate text and an alternate image file to use for the search box in Web sites where you activate the control.
One of our client is insisting us to implement Google Search on their Internet based SharePoint Site.Here I found one link which help to implement Google Search within your SharePoint site.
It is now time to put all of our resources together to build a more complex search center that can be used to search multiple team sites housed in their own site collections. You will need to have MOSS standard edition to complete all of these steps.
Since this is a project needed to accomplish within his organization, Chris Quick had documented the steps as he complete them himself!
If you have a public Sharepoint site (MOSS 2007 or WSS 3.0) that is accessible to anonymous users and you’re not using custom scopes, you probably already noticed that every time users try to search they get a user prompt. To get pass this prompt you must enter valid username, otherwise you’ll get famous “Access Denied” page. So much for anonymous access, right?
Anyway, the problem is with OSSSearchResults.aspx page, specifically with one of the inheritance reference that ASPX page. I’m talking about the part of the code that sets the inheritance of the page from the generic application page base class, which is not really required for this page to function properly.
To allow anonymous users to search your publicly available sites you need to remove that inheritance from the code, so find part of the code inside the tag that states “Inherits="Microsoft.SharePoint.WebControls.LayoutsPageBase" and remove that part of the code (not the whole line, just the part that inhertis the application page base.) OSSSearchResults.aspx page is usually stored at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS on your SharePoint server. Make sure you backup the file before making any changes!
Making those changes will not only allow anonymous users to search the SharePoint content, but also will keep the SharePoint search secure, meaning that anonymous users will only be able to search the part of the SharePoint they have permissions to view.
Lots of time I come across the requirement of how we can customize out of box search result page and I find the answer here...
