Enterprise Search Summit 2012

Two years ago, I’ve conducted a workshop with Jeff Fried, Miles Kehoe and Mark Bennett at the Enterprise Search Summit 2011. This was my first time at the Search Summit and I’ve surely recognized the value and the great experience that it has provided to me personally and to all others attending the even. This year I urge you to attend it as well. Here is more information on the event, speakers and discount.

Early Bird Registration Ends April 13!
Register today to save $200 off the regular rate!
You only have until April 13 to take advantage of our early bird discount! Enterprise Search Summit is the premier event in enterprise search - we'd love for you to be there! Don't miss your chance to attend and save off the cost of your registration!

5 Reasons to Attend
You won't want to miss this spring's Enterprise Search Summit and your chance to learn from the leading minds in the industry. We've compiled a list of 5 reasons why you should attend Enterprise Search Summit to erase any doubt in your mind that this is the place you want to be May 15-16.

1. Excellent speakers
We have a full program featuring the best of the best speakers in the enterprise search industry! Learn from the experiences of leading organizations and gain expert insights from the search world. See a full list of speakers here.
2. Networking opportunities
Enterprise Search Summit brings together an unparalleled group of search experts, vendors, and practitioners. Network at breakfasts, lunches, coffee breaks, the welcome reception, and in the Enterprise Search Showcase. See the conference program for break times and showcase hours.
3. Enterprise Search Showcase
For two days only, the Showcase features the top companies in enterprise search and offers attendees the opportunity to explore new developments in product and service solutions. Admission to the Enterprise Search Showcase is also FREE with the purchase of a full-conference pass!
4. In-depth Pre-conference Workshops
Join us for a series of workshop sessions on Monday, May 14, featuring discussions about taxonomies, project management, search platforms, text analytics, and more! See the schedule of pre-conference workshops and descriptions here.
5. Learn from Real-World Implementations
Enterprise Search Summit features representatives from leading companies such as Sematext, Search Technologies, Raytion, and many more, who will share real-world examples of search implementation and their experiences. See a full list of speakers and companies here!

The Venue

Hilton New York
1335 Avenue of the Americas
New York, NY 10019
The Hilton New York is the official conference hotel for Enterprise Search Summit.  The hotel is located on Avenue of the Americas (6th Ave.) between West 53rd and West 54th Streets. 53rd street is west bound and 54th street is east bound.

Technorati Tags: Enterprise Search Summit

SharePoint 2010 Enterprise Architect’s Guidebook

I’m happy and excited to announce that the “SharePoint 2010 Enterprise Architect’s Guidebook” is available now.

I was honored to become a contributor to this great book. It was a real pleasure to work with the Authors Brian Wilson, Reza Alirezaei, Bill Baer, Apran Shah along with such contributors as Matt Rantlett, Paul Olenick, and many other great names in the industry.

This book is great for all SharePoint!!! Get your copy

Enjoy

Thesaurus in SharePoint 2010 Search (SharePoint Shop Talk Question)

I wrote this quick blog entry about last week’s discussion on SharePoint Shop Talk. The question is documented below in orange. I believe this would be a good blog entry because the situation that cause this question is fairly common and the approach to this is not necessarily the best practices approach.  Also from the response from the audience it appears that people found it insightful. 

By the way, do not hold you breath, I’m not going to answer the technical details of this question:

This is kind of a long post, but mostly because I want to make sure all of my details are in it. I mainly am looking for answer for the first two questions. The third is just a bonus!

I have a SP 2010 Standard farm (1 app server, 1 WFE, 1 SQL) with out of the box search set up.  I am trying to edit our Thesaurus file to help our employees find what they are searching for……

I followed the TechNet instructions editing the files at

\Program Files\Microsoft Office Servers\14.0\Data\Applications\GUID\Config, where GUID of the new Search service application, and nothing I try seems to work.

I noticed that the path where I am editing the files (which is the only folder under Applications) is:

D:\Program Files\Microsoft Office Servers\14.0\Data\Applications\8340232b-513b-4ed8-81f4-50a1980af0f0\Config

However, if I run the powershell command:  Get-SPEnterpriseSearchServiceApplication

The guid returned is:  9ea80497-bf69-4ead-b14e-5188c7cecf03

1. Should I have a folder in the applications patch that matches my Search Service Application guid?
2. In Central Admin, when I look at my Search Application Topology, under Index partition ... property store,  it shows Query Component 2 = my WFE and Query Component 1 = my app server.  However, the above path is only on my app server so that is where I have been changing the files.  Is this normal to have both app and WFE showing.
3. Is there a way to either exclude views or set weight on one view, to prevent same result being returned multiple times with different views.

As I mentioned above, I’m not answering the technical details here, but instead asking a question back: “Why this approach?”. Adding/editing thesaurus file to achieve the goal is not the best option here. SharePoint 2010 Search has such functionality as keyword management and best bets.

Keywords are search terms that users type into a search box when executing a query. When a user query includes a keyword that you have configured, the search results can provide a definition for the term together with links to recommended locations or documents at the top of the search results page.

You can define keywords, provide synonyms (words that closely relate to the keyword), and create Best Bets (links to featured documents or locations for the specified keyword), to provide a relevant set of search results for popular search terms. Synonyms are useful and specifically in this particular case when the requirement and the whole idea for editing the thesaurus is to use several search terms to find the results that match the same concept and content

When you create a keyword, you can also provide a definition of the keyword that appears in search results. When keywords have synonyms and associated Best Bet links, they help guide users to recommended resources. The list that is updated when a site collection administrator creates keywords and adds synonyms is called a thesaurus. The thesaurus for SharePoint Server 2010 is compatible with the thesaurus for Microsoft Office SharePoint Server 2007.

You can delegate the creation of keywords to Site collection administrators to create keywords at the site collection level. This is a better way of implementing and maintaining the required functionality then modifying thesaurus files directly.

Enjoy

Technorati Tags: SharePoint 2010 search,SharePoint Shop Talk,thesaurus

The infamous : Property doesn't exist or is used in a manner inconsistent with schema settings (SharePoint Search and FAST)

I bet we all have seen this error from time to time. This usually happens when you create new managed properties and try to expose them on the search center, but it can also happen is cases when  always. There is a check list:

1. Make sure that the managed property has been added to the managed properties and mapped to crawled properties

2. After adding managed properties start the crawl

After ensuring that the managed property has been created and populated with values, ensure that your web parts are referring to this managed property and the name is not misspelled. if you still get this error, it might be because the SharePoint Query components are not updated. Restart the IIS on the query servers, to resolve this error.

With FAST, there are also additional thing that can go wrong. In some cases you can see this error on OOTB Fast search center as well and in can be inconsistent if you have multiple query servers. This is indicative that the query servers got out of synch.

The Index Schema defined in SharePoint Central Administration at the Query SSA's FAST Search Administration section is stored in SQL Server, and deployed to FAST Search through a timer job. It's possible that not all steps of the deployment occur, leading to a newer schema in SharePoint / SQL than the FAST qrserver is using.

It is easier to restart QR components to get them back in synch than to find the one out of synch and re-synch it.

Here is what you can do to resolve it:

Open up the FAST Search for SharePoint powershell and run the following on each QR server.

(Only do the ones that exist from the list from nctrl status)

nctrl stop qrserver qrproxy search-1

nctrl start qrserver qrproxy search-1

Enjoy

Technorati Tags: SharePoint search 2010,FAST search for SharePoint 2010

The Past, Present and Future of Search: A Round Table Discussion

Happy New Year! We are excited to announce our next meeting, a Round Table Discussion. Sign up now

SUBJECT
The Past, Present and Future of Search: A Round Table Discussion

Last month, The NY Enterprise Search User Group celebrated its Two Year Anniversary. This month we would like to take a look back at past talks, hear how user group members are currently using Search, as well as the group's vision of the future of Search.
Carlos Valcarcel Technical Solutions Professional at Microsoft, Natalya Voskresenskaya SharePoint MVP & Search Engineer along with Paul Olenick SharePoint and Search Engineer at Arcovis will lead a Round Table Discussion around Search.
Take a trip down memory lane here: Past Meetups

ABOUT THE LEADERS
Carlos Valcarcel has been in software development since the mid-80's working in financial services, insurance and technology....Read More.
Natalya Voskresenskaya has been working in the field of Information Technology for over 10 years. With experience in design, architecture...Read More.
Paul Olenick is a Sr. SharePoint and Enterprise Search Consultant for Arcovis (Gold Partner and Microsoft V-TSP) where he leads projects for large enterprise customers across multiple verticals...Read More.

Leonardo Souza, Senior Technical Instructor at FAST University/Microsoft is a professional with thirteen years experience working with Microsoft...Read More.
Michael McCabe currently works as an Information Architect for Gig Werks and focuses on the SharePoint product. He has 18 years experience...Read More.

Drive with FAST search for SharePoint 2010 installation is running out of space

On one of the projects I was seeing recurring behavior where “D:\FAST Search\data\ftStorage\sequences” folder quickly fills up with files like storage_6a.data , storage_cd.meta thus causing the drive to run out of space. That location is used to store index (“fixml”) information used for fault tolerance (ft) in a backup indexing row. We have deleted these files at some point since there was an environment health issue as well, hoping that fixing the environment issue was to blame for causing this folder to fill up, but it came back again and quickly filled up the drive. In searching for the cause of the problem here is what was found.

1. It’s likely this is happening if one or more servers are configured as a “secondary” indexing row.  See this example from a FS4SP deployment.xml file:

<searchcluster>

                <row id="0" index="primary" search="true" />

                <row id="1" index="secondary" search="true" />

</searchcluster>

The options are to disable the secondary/backup indexer(s), or add more disk space to the backup row.

If the data was deleted in this folder, it’s likely the backup index data is out of sync, and will need to be resynchronized with this procedure:

“Synchronize the primary and the backup indexer servers (FAST Search Server 2010 for SharePoint)” - http://technet.microsoft.com/en-us/library/gg482028.aspx

2. In our case the box that had this issue was not configured as a secondary row, but was a primary row.

The deployment.xml has not used row 0 as the primary row (which is required, ref http://technet.microsoft.com/en-us/library/ff354931.aspx#element_searchcluster)

This caused the ftstorage files to neither be placed on the intended server, nor rotated and thus eating up the disk space.

Here is an example of the deployment

<host name="FAST01 ">

<admin/>

<crawler role="single"/>

<webanalyzer lookup-db="true" link-processing="true" max-targets="2" server="true"/> <document-processor processes="4"/> <content-distributor id="0"/> <indexing-dispatcher/>

<query/> <searchengine column="0" row="0"/> </host>

<host name="FAST02 ">

<document-processor processes="4"/>

<content-distributor id="1"/> <indexing-dispatcher/>

<query/>

<searchengine column="0" row="1"/>

</host>

<searchcluster>

<row id="1" search="true" index="primary"/> <row id="0" search="true" index="secondary"/>

</searchcluster>

Once the IDs were reconfigured and then I ran Set-FASTSearchConfiguration on the admin box as well as the non-admin. The issue went away

Enjoy

Technorati Tags: FAST Search For SharePoint 2010 reconfigure,deployment.xml

NOINDEX Handling by FAST and SharePoint Search

Just recently I had to go through troubleshooting of content being indexed by FAST and/or SharePoint Search and wanted to share experience and some collected wisdom.

Here is the case, very common: the client has branded master page that includes menu navigation items, these items were being indexed. Where in case of searching for “Vacation form” would bring every page that is using this master page with menu items, simply because link to vacation form was included into the navigation menu on this master page. After the client included ”noindex”, which works for FAST as well as for SharePoint it seemed to work. Few weeks later when I came onsite, I noticed that the Search SSAs for SharePoint as well as for FAST had their content sources misconfigured and without even knowing the client was using just SharePoint search for everything. At this point I’ve reconfigured the content sources so only “people” search is being server by SharePoint search and the rest of the content is searched by FAST. This is when we have noticed the same problem where menu items were being indexed again without respecting the NOINDEX tag. Once we purged the index and reindexed everything again, it all worked.

Here are the tags and the explanation of how they work:

1) <meta name="robots" content="noindex" /> : Supported using both crawlers, although differently. FAST crawler will drop these items. SP crawler will not drop the items, they will be dropped by the FAST pipeline. But the result is the same for both.

2) <noindex> This text will not be indexed </noindex> : Not supported regardless of crawler.

3) <div class =”noindex”> This text will not be indexed </div> : Supported. This is transparent to both crawlers, will be filtered in the FAST pipeline.

4) <span class =”noindex”> : Supported by FAST Search back-end but not SharePoint search.

5) SP crawler fix to ensure that the <meta name="xxx" content="noindex" /> was passed to the FAST pipeline (KB 2276336)

http://support.microsoft.com/kb/2276336

Part of the August 2010 CU.

Hope this helps to others.

Enjoy Holidays!!!!

Technorati Tags: sharepoint search,fast search for sharepoint,noindex tags

Technorati Tags: Fast search for sharepoint,noindex,sharepoint search