Browse by Tags

All Tags » Search (RSS)

Search Community ToolKit

Das CodePlex-Projekt Search Community Toolkit ist eine Sammlung von Tools und Beispielen die die Funktionenn von SharePoint Server 2007, SharePoint Server 2007 for Search Search Server und Search Server Express erweitern. Search ASP.NET Server Controls Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Crawling a Content Source Requiring Basic Authentication

As much as I fight basic authentication, there are still people out there who want to use it. SharePoint Enterprise Search can crawl a site requiring basic authentication through the use of Crawl Rules. Browse to the Shared Services Provider page within Central Administration. Click on Search Settings -> Content sources and crawl schedules. I recommend adding the source as a new content source. Once you have created the new content source return to the Search Settings screen. Click on Crawl Rules -> New Crawl Rule. Enter the path this rule will affect. Using wildcards is the easiest way to make sure the enter server is being crawled with the account specified. Change the crawl configuration to 'Include all items in this path'. Specify other settings if necessary. Change the authentication to 'Specify a different content access account'. DO NOT CHECK 'Do not allow Basic Authentication'. Click OK to save the settings and your new crawl rule will appear in the list. Kick off a full crawl of the content source for the rule to take effect. Simple I know. But I was hit up for this multiple times so I figured I would write a post on it. Jeff Jeff Holliday Architect, Portals and Collaboration Ensynch, Inc. Jeff Holliday's SharePoint Blog Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
Posted by SharePoint Blogs

EndUserSharePoint.com: Can I save searches as links?

The question of the day comes from Chris: Do you know of a way users can save searches as links? Chris - The basic search is a ‘get’ in the URL, so setup the search, click the search button and then copy the URL to use as the href in the link Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Search Core Results Web Part and XSL Link Property

I was customizing a search core results web part display recently and I wanted to have a sinle instance of the XSL used to translate the results since I will have multiple instances of the same search core results on many different site collections. I thought the "XSL Link" web part property of the search core results web part would allow this, but I was mistaken. The issue is you can only reference an XSL file in the XSL Link web part property only if the XSL file resides on the same site collection as the web part is displayed. I tried referencing the file from _layouts and received and error, I tried referencing the file from another site collection, received same error. I know permissions is not a problem since none of these locations are locked down. If there is anyone that knows a workaround for this I would love to hear it. Also, this was on an instance of MOSS Standard SP1. Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
Posted by SharePoint Blogs

PDF ifilter for x64

There has been a bit of an issue with a full x64 MOSS farm, mainly due to the lack of ifilters for x64, the obvious (and also, importantly, tested and supported) workaround being the use 32bit for the Index server and x64 elsewhere. The most common third party ifilter needed by clients (in my experiance) is for PDF documents, Adobe were very slow to respond and deliver an x64 ifilter (in fact they still haven't) but now have a publishing work around toi running v8.1 ifilter on x64, see this:...( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Redirecting from osssearchresults.aspx

In SharePoint MOSS 2007, when you turn on the custom scope in site collection’s “Search Settings”, most of search results will be displayed at /SearchCenter/Pages/results.aspx. The exceptions are at the contextual search (This site, This List: Documents etc) and it always displays the search result in OSSearchResults.aspx page, which you can not customize through web [...] Mirrored on SharePoint Blogs Posted on SharePoint Blogs...( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
Posted by SharePoint Blogs
Filed under:

Office SharePoint Server Search keeps results to itself

Instead of some information I'm posting a question today.. We've build an application that uses the search functionality to roll up content. Only not all content gets returned in the way you would expect it to. A description of the problem can be found here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2789944&SiteID=1&mode=1 Any suggestions as to what's happening are greatly appreciated. Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
Posted by SharePoint Blogs
Filed under: ,

How not to set up Sharepoint Search

This is going to be a quick little post where I confess to doing something stupid. I should have known better. We are currently prototyping a MOSS 2007 Enterprise solution for a government organization. This customer has a fairly large public website, and a similarly large intranet site. While demonstrating how to configure search scopes, I created a scope pointing at the external site, and changed its settings to "unlimited" without really thinking about what that meant. Well, what it means is, it's a good way to fill up your server's hard drive, and a good way to annoy other departments of the government. It turns out that in "unlimited" mode, Sharepoint crawls every link, then keeps crawling links found on destination pages, branching out until, I assume, it has indexed the entire Internet. I also learned that Sharepoint doesn't handle the ROBOTS.TXT files correctly, so sensitive information could be crawled along with everything else. I couldn't believe this, until I found a post here that confirms it: Sharepoint only looks at the root of the site for ROBOTS.TXT files, and ignores them wherever else they may be: Observations During our testing we discovered the following. 1. robots.txt file is cached for 24 Hours following it's first request by the crawler. The implication of this is that changes to robots.txt require either a restart of the Office Search Service or a delay of upto 24 hours before they are respected by the gatherer....
Posted by SharePoint Blogs
Filed under: , , ,

Joel Oleson and the Anatomy of Indexing

Ok. So the real reason that I chose today to on-ramp this blog. I wanted to add a little something to Joel Oleson's post yesterday regarding the Anatomy of Indexing . First of all, I'm sure anyone interested in my take on SharePoint is probably well aware of Joel Oleson. Most of the SharePoint community, myself included, holds Joel in the highest respect. I respect him for his wealth of SharePoint knowledge and his willingness to share it. I met him recently and in addition to being a SharePoint guru, I found him to be a very likable guy in general. Rock on Joel. So about the Anatomy of Indexing. It is a great read for anyone who's interested in that black box called SharePoint Indexing. Please make sure you've read it before continuing.... Ok, I have just one little point I'd like to add from the document repository front. During an incremental crawl, the call to the sitedata.asmx yields a result set of ALL the entries in the change log. This is particularly important to KnowledgeLake as we tend to blast a lot of content into SharePoint in a short period of time (like during migration/conversion operations). But this might also apply to standard SharePoint restore operations. If you find yourself performing some type of action that will cause a high number of document changes all at once, all crawl schedules (full and incremental) should be disabled if at all possible. If it is not possible to disable them, then the url path to the library where content is...
Posted by SharePoint Blogs
Filed under: ,

Microsoft Gets FAST!

Before I continue on with any other posts on this blog, I have to lay some very exciting groundwork. I said in my bio that SharePoint can be architected to scale from a single server installation that handles just a handful of static documents to extremely large implementations consisting of multiple farms that can handle 50 terabytes or more. Well, this is statement requires a bit of qualification. I have been part of architecture teams that have loaded 10s of terabytes into SharePoint. This is absolutely possible and I have actually developed a content load utility that can blast 50 million documents into a properly architected SharePoint system in just a couple weeks. But the problem isn't putting data into SharePoint. It's making sure you can get it back out. I've always been concerned about the 50 million document limitation for an index server in a SharePoint farm. Sure you can have multiple farms. And with the MS Search Server 2008 we can even do federated searches to aggregate results. But the problem comes with relevance. I can certainly write code that kicks off searches on multiple farms and aggregates the results but I lose relevance. Without the internal ranking engines talking to each other, all we get is a group of unranked links munged together in some sort of list. Enter FAST. With the recent acquisition offer for FAST , things may change a bit. I listened to the tele-conference call. They didn't want to come right out and talk about the implications...
Posted by SharePoint Blogs
Filed under: , ,

SharePoint and MySQL

SharePoint and MySQL Integrating SharePoint with MySQL using Business Data Catalog T his is another article of the same series that has been continuing for the last couple of weeks. Yep! SharePoint and the Business Data Catalog! Following are the recent articles that cover the SharePoint and the Business Data Catalog "Definition Editor Tool": 1. Working with Business Data Column 2. Importing BDC Data into SharePoint 3. Using Business Data Catalog Definition Editor 4. Few Issues With Microsoft...( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Build fix queries in a dynamic way

By default, we are able to display query results in our own page with the Search Core Results web part . Basically the search query can be built in two ways: UserQuery: to get a query from current user we need a Search Box or Advanced Search Box web part. After typing the query, both of these webparts give the query to the URL QueryString, and the Search Core Results webpart show the results according to these parameters. For example: http://mymoss/sites/customsearch/default.aspx?k=42 means the user...( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

How To Extend Wildcard People Search on MOSS 2007

Ramon Scott just posted on his blog on how to perform wildcard people search on MOSS 2007. His script example, shows how to search for First Name and Last Name. After reading some of the comments, many were wondering how to implement search on additional Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

MOSS Search: TotalAvailable & TotalRows not accurate

A query against MOSS search engine returns a specified number of results and a indication of the total number of results. When working with the API this is the TotalRows property of the ResultsTable, working with the WebService this is the TotalAvailable element of the ResponsePacket. If you, like me, want to base your paging on the TotalRows or TotalAvailable properties and you expect it to return the exact number of results you're in for some strange behaviour... I do not have a nice solution yet, although the API also exposes the IsTotalRowsExact property. This will tell you when you're on the save side. The webservice ResponsePacket has not got an equalivant property. The MSDN documentation of the API does not mention this number not being exact: http://msdn2.microsoft.com/en-us/library/microsoft.office.server.search.query.resulttable_members.aspx The webservice documentation actually does mention it: http://msdn2.microsoft.com/en-us/library/aa193748(office.11).aspx#RangeType_TotalAvailable "The total number available. This number may not be 100% accurate and all these results may not be accessible." The number will become more accurate once you move to the end of the resultset. Be warned... Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
Posted by SharePoint Blogs
Filed under:

SharePoint Search - Only 3 Items in the Index???

I'm trying to scope out some work for a potential project that requires a fairly robust search component. Mind you, I've done a whole lot of nothing with SharePoint Search, so I'm having to explore things as I come up with an approach. I set up a new Content Source for crawling my little test site site and ran a full crawl, the result of which was 3 items in the index. 3 items.... hmmm... No crawl errors, no errors in the event log, but no results for any of my searches. Weird. Pounding-my-head-on-the-table-after-3-hours-of-trying-to-figure-this-out kinda weird. Eventually I stumbled across the issue. I had used 'localhost' instead of my server name in the start address of my content source. Stupid me. Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
Posted by SharePoint Blogs
Filed under:
More Posts Next page »