Using Microsoft Search Server Features

Basic Search

NOTE: You can designate a folder outside of Ektron to be searched. For more information, see Including External Files in Your Search.

The Basic Search finds content that satisfies these criteria.

• Published. Changes checked in but not published are not accessible.

  NOTE: New and updated content is available only after the next crawl completes. See Also: Managing the Search Crawl

• Active. Also, expired content appears if the archivethe state of content upon reaching its end date. What happens next is determined by your choice at the content's Schedule tab > Action on End Date options field. Choices are * Archive and remove from site (expire) * Archive and remain on site * Add to CMS Refresh Report option is Archive and remain on Site.
• Content’s Content Searchable box is checked.
• Public. Private content is only available to those with permission to view it, such as membership users after logging in. See Also: Making Content Private

  IMPORTANT: Private content is hidden from search results if your search provider is Microsoft Search Server 2010. It is not hidden if you are using another search provider.

• Library items are searchable by title and file name. To make the content of non-image files (for example Word documents) searchable, add them as assets. See Also: Working with Assets in the Document Management System
• Language
  • Website search—Content in selected site language appears unless the developer sets the language via Advanced Query Text or API
  • Workarea search—Content in the Workarea’s current language appears (user selects Workarea language via the View > Language menu option)

• Search text is contained in title or content
• If the search text is more than one term, all terms must be found. So, multiple terms have an AND relationship.

  NOTE: A user may force an OR relationship by entering OR between search terms, or using the Advanced Search's any of these words option. Developers may create an OR-based search using the API property ImplicitAnd.

  IMPORTANT: If you have a multi-site configuration, a search conducted from any site returns results from all sites. To limit search to single site, use a syntax like this:
  AdvancedQueryText=' AND ( "parentsiteid"=0 OR "parentsiteid"=161 ) '
  

• Satisfies content type criterion selected on screen, if chosen (see below)
  —Image—

  

  NOTE: The search does not find documents inside compressed files, such as *.zip, *.cab, and so on.

The following list explains the values in the Advanced Search tab's Content Type field.

• Site
  • Content from all options listed below.
  • Any document file type defined in the Asset Server Setup screen

    NOTE: You can find these files using Site as the content type criterion, but not using Documents.

• HTML
  • HTML
  • HTML form (but not data submitted on form)
  • XML Smart Forman Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input. (field values but not field labels)
  • Blog entries (not comments)
  • Web calendar events
• Documents
  • MS Office documents (includes Powerpoint, Excel)

    NOTE: To search Visio documents, you must install the Visio IFilter. See Also: Installing the Visio IFilter

    • Document properties (categories, comments, and so on)
  • PDF file

  IMPORTANT: The search only finds text in the first 16 MB of any PDF document. So, for example, if the file is 32 MB, only the first half of the text is searchable.

  • .txt file
• Images added as assets and through the library
  • Search text in file name (including file type extension) and summary.

    NOTE: If you assign several images to an eCommerce catalog entry, and want to allow searching for that catalog entry by image file name, the search only works with the first image assigned to the catalog entry.

• Multimedia (Flash, .mp3, and so on)
  • Search text in file name (including file type extension) or summary
• Forums
  • Forum posts and replies
• Tags
  • Tags applied to content and library items See Also: Tagging Content, Library Items, Users, and Groups with Keywords
• PageBuilder Pages
  • PageBuilder page: properties (summary, metadata, and so on) and content within the page's widgets.

    IMPORTANT: If a content block is added to a PageBuilder page, the search only returns its appearance on the PageBuilder page. The search does not find such content on a non-PageBuilder page.

Advanced Search

The Advanced Search uses the same search criteria as the Basic Search. (See Basic Search). The differences are additional options and the fact that you cannot use queries.

NOTE: The advanced search screen may look like the following image, although your developer has total control over its appearance." See Also: Modifying Templated Server Controls

Formulating Search Queries

NOTE: Following text extracted from Free-Text Keyword Queries.

To search for any word or phrase on a website, enter the word into the field and click Search to begin.

The following rules apply to formulating queries:

• By default, multiple words have an "and" relationship. So, the search term calendar server returns pages that have both words.
  • To find pages with either term, use the OR operator. For example, calendar OR server returns pages that have either word.

    IMPORTANT: You must capitalize Boolean operators, such as AND.

  • To find pages with several terms in exact order with no intervening words, use quotes. For example, “calendar server” returns pages that have both terms in that order.
  • To find pages that have one term without another, use the NOT operator. For example, For example, calendar NOT server returns pages that have calendar and do not have server.
  • To find several terms close together, use NEAR. For example, treatment NEAR immunoglobulin finds pages with the word “treatment” near the word “immunoglobulin.”
    

    IMPORTANT: You cannot use the NEAR operator with Solr search provider.

    The NEAR operator is like AND because it finds pages that include both search words. However, the rank assigned by NEAR depends on the proximity of the search words. A page with search terms closer together has a higher rank than a page where they are farther apart.

    NOTE: The NEAR operator can be applied only to words or phrases.

• Search terms are case-insensitive.
• Punctuation marks, such as period (.) and comma (,), are ignored by the search.
• Operators (<, >, and &) are ignored by a search. Also, the search does not find text within angle brackets, for example <Ektron>.
• To include in a query special characters that are not operators, such as +, |, ^, #, @, $, (,), enclose the query in quotation marks (“).
• Use the wildcard character (*) to find words that start with a certain letter sequence. For example, esc* returns Web pages with “ESC,” “escape,” and so on.
• To nest expressions within a query, add parentheses. Expressions within parentheses are evaluated before the rest of the query.
• Use double quotes (“) to ignore a boolean or NEAR operator keyword. For example, “Abbott and Costello” finds pages with the entire phrase, not pages that match the Boolean expression.
• The AND operator has a higher precedence than OR. For example, the first 3 queries are equal, but the fourth is not:
  • a AND b OR c
  • c OR a AND b
  • c OR (a AND b)
  • (c OR a) AND b

Using Autosuggest

IMPORTANT: Autosuggest works with Microsoft-based search providers only. If you are using the Solr search provider, see Managing Solr AutoComplete.

Autosuggest is a search feature that suggests similar terms or common refinements that searchers have used in the past which are related to the search term. As a user enters text, possible matches appear. This immediate feedback may preclude the user from typing an entire search phrase, and instead choose a term with which to launch the search.

Terms appear on the list if they

• include the submitted letters, and
• were previously submitted by site visitors, and
• have resulted in the viewing of a search result

Autosuggest only works with the Site Search Control.

$app = Get-SPEnterpriseSearchServiceapplication "FASTQuery"

New-SPEnterpriseSearchLanguageResourcePhrase 
-SearchApplication $app 
-Language en-us 
-Type QuerySuggestionAlwaysSuggest 
-Name “ektron”

Remove-SPEnterpriseSearchLanguageResourcePhrase 
–SearchApplication $app 
-Identity ektron 
-Language en-us 
-Type QuerySuggestionBlockList

(Get-SPTimerJob –Identity “Prepare Query Suggestions”).RunNow()

$app = Get-SPEnterpriseSearchServiceApplication "FASTQuery"

New-SPEnterpriseSearchLanguageResourcePhrase 
–SearchApplication $app 
-Language en-us 
-Type QuerySuggestionBlockList 
-Name ontrek

Remove-SPEnterpriseSearchLanguageResourcePhrase 
–SearchApplication $app 
-Identity ontrek 
-Language en-us 
-Type QuerySuggestionAlwaysSuggest

(Get-SPTimerJob –Identity “Prepare Query Suggestions”).RunNow()

Get-SPEnterpriseSearchLanguageResourcePhrase 
–SearchApplication <Search Service Application> 
-Language en-US 
-Type QuerySuggestionBlockList 

The "Did you mean?" Feature

If a site visitor enters a word that is similar to a crawled term, the "Did you mean?" feature often suggests close alternatives. If you click a suggested term, a search is performed on it.

The "Did you mean?" feature works only with single word queries.

NOTE: If your search provider is Solr, the "Did you mean?" feature only works with words in the content title.

Making Content Searchable

Search only accesses data about the content if the Content Searchable field is checked.

NOTE: Despite the value of this checkbox, if an Ektron user places this content item in a Suggested Results list, it appears in the Suggested Results area of the Search Results screen. See Also: Providing Suggested Results.
Also, even if Content Searchable is unchecked, the Advanced Workarea search can find the content.

The default value of this field is determined by the ContentSearchable folder property.

Installing the Visio IFilter

The search finds text within Visio documents if the Visio IFilter is installed to the Microsoft Search Server used by the Ektron Web server. Use the following link to download and install the Visio IFilter.

Microsoft Office 2010 Filter Packs

IMPORTANT: The Visio IFilter does not work with the Solr search provider.

Searching for Metadata

The following rules apply when searching for values inside metadata.

• The search finds text within Searchable type and Content Tag metadata fields. For example, a content block has a searchable type metadata field, MapAddress, that contains 131 Amherst St. Searching for 131 returns that content.
• To find content with searchable metadata whose style is yes or no, enter true or false.

See Also: Working with Metadata

Displaying Search Results

See Also: Search Result Ranking

The following example shows the website search results screen. Your developer can customize it using the appropriate ResultsView server control. For example, to display eCommerce catalog entry results, the developer uses the Using the Search Server Controls.

Customizing the Postback Message

By default, if a search term yields no results, a message appears.

To customize this message:

1. In your site root folder, find the workarea/resources folder.
2. Open the resource file that corresponds to your site’s language. For example, if your site is in American English, open EkResource.en-US.resources. To learn how to work with a resource file, see Translating the Workarea.
3. If your site supports multiple languages, follow these steps for each corresponding resource file.
   1. Within the resource file, find the key lbl search no results.
   2. The default text (shown above) follows this key. Modify the text as needed.
   3. Save the file.

Search Result Ranking

NOTE: This topic describes search rank using Microsoft Search Server 2010. To learn about search rank using Microsoft FAST Search Server 2010, see Setting Up Microsoft Search Server 2010.

Each content item found by search is given a numerical rank. Search results are sorted by rank. Criteria used to calculate rank include the

• number of occurrences of the search term
• proximity of search term to beginning of file
• proximity of search term to other occurrences of the term
• whether the term is in the title

If you need to ensure that certain content appears at the top of search results when certain terms are entered, use suggested results. See Also: Providing Suggested Results

To learn about customizing ranking for Microsoft Search Server 2010, see

• Custom Ranking Models with SharePoint 2010: Background, Value and Administrative Overview
• Creating Custom Ranking Models
• SharePoint 2010 enterprise search developer training

Using Synonym Sets

Prerequisite

You must be a member of the Administrators Group or assigned the Search-Admin role to access Synonym Sets. See Also: Defining Roles

IMPORTANT:
*Changes to a Synonym Set reset Search Server. To minimize impact on your visitors, make such changes during off-peak hours.
* Synonym Sets apply to all Ektron sites associated with a Search Server instance. For example, if Site A, Site B, and Site C use the same Search Server instance, they share Synonym Sets. This means that a Synonym Sets created in Site A may affect Site B's search results.

You can create sets of synonyms to work with the search. If a site visitor enters into the search field any term in a synonym set, the search returns results for that term plus all other terms in the set.

For example:

• Synonym Set: Tuition
• Terms: tuition, bill, payment, pay, fee, charge, price, amount, cost, balance

If a site visitor inserts bill into the search field, Ektron uses bill or tuition or payment or pay or fee or charge, and so on., to determine search results.

The Synonym feature typically produces more “hits.” So, while visitors do no more work, their chances of finding the right information are greatly increased.

NOTE: Previous to version 8.5, you could use Synonym sets in Suggested Results. This is no longer provided in versions 8.5 and higher.

Providing Suggested Results

Prerequisite

You are a member of the Administrators Group or assigned the Search-Admin role See Also: Defining Roles

Your website may contain thousands of content items. Sometimes, depending on the search phrase, you want to focus the visitor's attention on a few topics. The Suggested Results feature lets you create a set of search terms, then specify content to appear at the top of the results when someone searches on a term.

Suggested Result links can jump to your website or an external website.

IMPORTANT:
* Prior to Ektron version 8.5, Suggested Results could be language-specific. Beginning with version 8.5, Suggested Results do not filter based on language.
* As of version 8.5, Suggested Results do not use terms from the Synonyms Set feature.

Displaying suggested results

Displaying Suggested Results

To display suggested results using templated server controls, set up a SiteSearchResultsView control whose Eval statement refers to SuggestedResults.

<ektron:SiteSearchResultsView ID="r" runat="server" ControllerID="c">
  <ItemTemplate>
    <h3>Suggested Results</h3>      
      <asp:ListView ID="suggestedResults" runat="server" 
        DataSource='<%# Eval("SuggestedResults") %>'>
        <ItemTemplate>
          <span class="highlight">
            <a href="<%# Eval("Url") %>"><%# Eval("Title") %></a>
            <%# Eval("Summary") %> 
          </span>
          </br>
        </ItemTemplate>
    </asp:ListView>
  </ItemTemplate>
</ektron:SiteSearchResultsView>

The suggested results class displays only 3 fields: title, URL, and summary.

If you want regular search results to appear below suggested results (as shown in Providing Suggested Results), your developer may want to style the suggested results to stand out. Some styling is shown above.

To display regular search results below suggested results and customize the standard result template, make the following modifications.

<ektron:SiteSearchResultsView ID="r" runat="server" ControllerID="c">
  <ItemTemplate>
    <h3>Suggested Results</h3>      
      <asp:ListView ID="suggestedResults" runat="server" 
	 DataSource='<%# Eval("SuggestedResults") %>'>
        <ItemTemplate>
	   <span class="highlight">
	   <a href="<%# Eval("Url") %>"><%# Eval("Title") %></a>
	   <%# Eval("Summary") %> 
          </span>
	   </br>
        </ItemTemplate>
      </asp:ListView>
      <asp:ListView ID="suggestedResults" runat="server" 
        DataSource='<%# Eval("Results") %>'>
        <ItemTemplate>
          . . . 
        </ItemTemplate>
      </asp:ListView>
  </ItemTemplate>
</ektron:SiteSearchResultsView>

However, if you want to display standard results and use the default template, insert a separate SiteSearchResultsView control below the suggested results control. See Also: Using the Search Server Controls

Step 1: Place Content in an External Folder

External folders must reside in the website folder so IIS has permission to access their content. Best practice is to create the external folder under the Webroot. Then, place content in the folder for the integrated search. Next, follow the steps below to set permissions and configure Search Server.

Set Permissions for the External Folder

The top-level folder that contains the external files must be accessible to the website, and the user account used by search server must have permission to read it.

The following example creates a user called IntegratedSearchUser and shares the external folder. Search Server uses the IntegratedSearchUser account to access the external folder's content.

1. On the Web Server, start Control Panel > Administrative Tools > Computer Management and create a new user called IntegratedSearchUser.
2. Using Windows Explorer, right click the external folder and choose Share.
3. Enter the IntegratedSearchUser user.
4. Click Add.

IntegratedSearchUser now has read permission for the external folder.

Step 2: Create a New Content Source for the External Folder

1. On your search server, open the SharePoint 2010 Central Administration screen.
2. Go to Manage service applications > Search Service Application > Content Sources > New Content Source.

   If you are using Microsoft FAST Search Server 2010, go to Manage service applications > FastContent Connector > Manage Content Sources > New Content Source

3. Enter the following values.
   • Enter a Name for the content source.
   • In the Content Source Type field, choose File Shares.
   • In the Start Addresses field, enter the external folder as a UNC path (\\server\directory) or full file URI (file://server/directory).
     • To make sure the search can access the external folder, you may want to use C$ in the path, like this: \\server1\c$\integratedsearch.
   • Set up Crawl Schedules for your integrated search folder contents to automatically refresh search indexes as frequently as you need to keep search results reliable. (This schedule is different than the crawl schedule for Ektron content.)
   • Begin a crawl by checking Start full crawl of this content source.
   • Click OK.

   If you successfully set this up, you see the new content source and the status shows "starting".

Step 3: Create Scope for New Content Source

NOTE: If you are using Microsoft FAST Search Server 2010, you can ignore Steps 3 and 4 proceed to Step 5.

1. On your Search Server, open the SharePoint 2010 Central Administration screen.
2. Go to Manage service applications > Search Service Application > Queries and Results > Scopes.
   —Image—

   

3. Click New Scope.
4. Give it a Name (no spaces) and Description.
5. Leave Use the Default Search Results Page checked.
6. Click Ok. The View Scopes screen reappears.
7. Use the pull-down next to the new scope name and select Edit Properties and Rules.
   —Image—

   

8. Add a New Rule.
9. In the Scope Rule Type field, select Content Source.
10. In the Content Source field, select the content source you created in Step 2: Create a New Content Source for the External Folder.
11. Set Behavior to Include.
12. Click Ok.

Step 4: Add External Folder to Ektron Website Scopes

NOTE: If you are using Microsoft FAST Search Server 2010, you can ignore Step 4 proceed to Step 5.

This step insures that the external folder content is included in Ektron search results.

1. Open the SharePoint 2010 Central Administration screen.
2. Go to Manage service applications > Search Service Application > Queries and Results > Scopes.
   —Image—

   

3. Use the pulldown next to your Ektron website's content source and select Edit Properties and Rules.
4. Click New Rule.
5. In the Scope Rule Type field, select Content Source.
6. In the Content Source field, select the external folder that you created in Step 2: Create a New Content Source for the External Folder.
7. In the Behavior field, select Include.
8. Click OK.

Step 5: Add a New Crawl Rule for the Integrated Search User

This step sets the permission for the search server to access the external folder.

1. On your Search Server, open the SharePoint 2010 Central Administration screen.
2. Go to Manage service applications > Search Service Application > Crawling > Crawl Rules.
3. Click New Crawl Rule.
4. Set the path to the external folder. (For example: \\ws10196\PressReleases\*.)
5. Set the Crawl Configuration to Include all items in this path.
6. Set Specify Authentication to Specify a different content access account.
7. Enter the Account. (For example: IntegratedSearchUser.)
8. Enter the Password and Confirm the Password.
9. Uncheck Do not allow Basic Authentication.
10. Click Ok.

Step 6: Complete the Integrated Search Mappings Screen

Prerequisite

You are a member of the Administrators Group or assigned the Search-Admin role See Also: Defining Roles

1. Choose Workarea > Settings > Configuration > Search > Integrated Search Mappings.
   —Image—

   

2. In the Start Address field, find the external folder.
3. In the Mapping field, enter the path to the external folder relative to your site root.
4. Click () to save.

Troubleshooting Integrated Search

• Problem—The protocol handler cannot be found. Check that the handler has been installed

  The protocol handler is normally installed in this folder.

  c:\windows\system32\DatabaseProtocolHandler.dll

  Solution—If the handler is in the correct place, check that all folder names and paths are correctly entered in the Content Sources, Crawl Rules and Scopes in the Search Service Application settings.

• Problem—Item was not crawled because of a password change. Update password and retry crawling.

  Solution—Verify that the Search Server user account has permission to read and write to the content database. You may have to create a unique user on the content server for this purpose.

Searching a Folder Hierarchy

1. Navigate to the folder from which you want to begin the search.

   NOTE: To search the entire site, search from the top-level (Root) folder. To limit the search to a folder (and its subfolders), select it then enter search criteria.

2. Click Action > Search. The Search Content Folder screen appears.
   —Image—

   

   • Search Published is the same as the Site Search, except your results are only retrieved from the current folder and its subfolders. If your search provider is Microsoft Search Server or Microsoft Search Server Express, you must have read-only or greater permission for the folder.
   • Advanced Search lets you expand search to include internal properties, such as last editor, date created/modified, status, and comments. See Also: Using Advanced Search in the Workarea

Using Advanced Search in the Workarea

The Workarea Advanced Search lets you find content using information that content authors and publishers would typically know. For example, you can search for content edited by a particular author within a date range.

When performing a search, enter one or more words into the text box, select search preferences, then click Search.

You can use an asterisk as a wildcard character to stand for any character. For example, the phrase CMS*00 returns topics that include CMS400, CMS300, CMS200 and CMS100.

Your system administrator can add custom search fields that only appear if a user is logged in. For more information, see Working with Metadata.

IMPORTANT: The Advanced search finds content whether or not it is marked Searchable.

The Workarea Advanced Search finds content that satisfies these criteria.

• user has read-only or greater permission for content’s folder
• matches selected language, if site is multilingual
• satisfies criteria entered on the screen
  —Image—

  

The Advanced Search screen lets you find Ektron content by specifying the following criteria. While the fields are optional, the search only returns content that satisfies all criteria.

• content type (for example, HTML content, forms, assets)
• one or more search terms. Unlike the Search Published screen, you cannot use a query.
• to search title only, enter search text into the Title field
• to search comments, enter search text into the Comments field
• a range of created or modified dates
• the editor who created or most recently updated the content
• the content’s status
• any searchable metadata assigned to the folder

Full vs. Incremental Crawls

Microsoft Search Server 2010 supports 2 types of crawls.

• Full—occurs immediately after events that significantly change data structure
• Incremental—occurs after incremental crawl intervalWhenever a crawl finishes, Ektron begins to track the time. After the number of seconds specified in the Incremental Crawl Interval expires, Ektron checks for changes to the database. If any occurred, a new incremental crawl starts. If none occurred, the timer is reset. Incremental crawls enhance your search's performance by using fewer resources. passes for less significant events that still require a crawl

Starting Crawls Manually

You should not need to start a crawl. Ektron initiates crawls as necessary. You would typically begin a manual crawl for troubleshooting purposes.

Prerequisite

You are a member of the Administrators group or assigned to the Search-Adminrole.

• To start an incremental crawl immediately, go to Workarea > Settings > Configuration > Search > Status. Click Request Incremental Crawl.
  
• To start a full crawl immediately, go to Workarea > Settings > Configuration > Search > Status. Click Request Full Crawl.
  

Improving Search Performance with Crawl Filters

When you set up the connection to Microsoft Search Server, you determine the types of content that will be crawled using the following screen.

If your crawl is taking too long, you might consider removing content types, especially those you do not use. To update the list of crawled content types, use the Search Configuration Screen's Site Registration panel > Advanced Options > Crawl Filters fields.

The following list describes the content covered by each type of crawl filter.

• HTML—Content blocks, forms, blogs, content-associated library items, completed Smart Forman Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input.s, calendar events.
• Documents—Uploaded Office documents, PDFs, images, and so on. See Working with Assets in the Document Management System
• Products—eCommerce catalog entries. See Conducting eCommerce
• Forums—Discussion topics, replies, and so on. See Working with Discussion Boards.
• Community members—Community user and groups. See Managing Community Groups. Also, Ektron users and groups.
• Community content—Community usera user with limited privileges, such as writing to a community forum, but not having the same privileges as a forum moderator, or an administrator who has access to the Workarea. (A community user is the same as a membership user.) and group photos, blogs, and so on.

• NOTE: Metadata and tags are crawled regardless of the crawl filter settings. Also, changes to other Ektron data objects result in the appropriate crawl, regardless of these settings. See Also: Full vs. Incremental Crawls

Monitoring Crawls

The Data Directory stores a log of information about each crawl. The logs are stored in the Using Microsoft Search Server Features. The Search Configuration screen's Monitoring Microsoft Search Server 2010 from the Workarea field lets you determine the amount of detail you want the log to collect.

The following errors may appear in the crawl log.

• Error—<url_path_to_asset>: The filtering was stopped because of a user action, such as stopping the crawl
• Problem—An asset is referenced in the Ektron database, but the physical file was deleted from the file system.

The following screens also let you monitor and manage crawls.

• Search Status screen in the Workarea. See Also: Setting Up Microsoft Search Server 2010
  —Image—

  

• Search Configuration Screen's Crawl Management panel
  —Image—

  

The following table compares the screens.

Table

Options	Workarea's Search Status screen	Search Configuration Screen
How to access	Workarea > Settings > Configuration > Search > Status	On server that hosts Search Server: Windows Start > All Programs > Ektron > CMS400vreleasenumber> Utilities > Search Config
View crawl information	search server content source name query credentials if there is a pending request to begin incremental search current and next scheduled search action See Also: Setting Up Microsoft Search Server 2010 most recent start and end times duration (last if no crawl currently running; current if crawl currently running) interval See Also: Setting the Incremental Crawl Interval crawl filters	On Site Registration panel Crawl IntervalSee Also: Setting the Incremental Crawl Interval Crawl Filters Crawl Tracing Level   On Crawl Management panel content source name crawl status (same as Current Action on Search Status screen) most recent start and end times duration
Start full crawl See Also: Events that Start a Full Crawl		Not available
Start incremental crawl See Also: Events that Start an Incremental Crawl		Not available
Set incremental crawl intervalWhenever a crawl finishes, Ektron begins to track the time. After the number of seconds specified in the Incremental Crawl Interval expires, Ektron checks for changes to the database. If any occurred, a new incremental crawl starts. If none occurred, the timer is reset. Incremental crawls enhance your search's performance by using fewer resources.	View only	Site Registration panel > Crawl Interval field See Also: Setting the Incremental Crawl Interval
Set the type of data that is searched	View only	Site Registration panel > Advanced Options > Crawl Filters

Troubleshooting Crawl Errors

The following information lists errors that may appears during a crawl, and how to resolve them. Errors appear in Microsoft Search Server 2010's administration portal. They do not appear in Ektron.

EktronSearchStatistics Logs

IMPORTANT: EktronSearchStatistics Logs are not available for the Solr search provider.

This log shows submission of the query statistics. It is updated only after a site visitor inserts a search term, clicks the search button, and clicks a result. To access the log, sign on to the Search Server machine > EktronSearchSite Web root > click EktronSearchStatistics folder.

PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose   Publishing Search Statistics : Begin
PID:7284 TID:7056	MTID:	2012-04-03T14:55:1
Verbose  QueryContext.Create: Creating QueryContext /
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  QueryContext.Create: Created QueryContext /
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  QueryServiceInfoProcessor.GetSearchApp for 
  QuerySSA:Search Service Application
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  QueryServiceInfoProcessor.GetSearchAppProxy 
  for QuerySSA:Search Service Application
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  MSStatsRecorderProxy.Record: Recording
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  MSSearchStatsHelper.SubmitStatistics: 
  Beginning statistics recording to SharePoint!
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  MSSearchStatsHelper.FetchClicksToRegisterValue: 
  Will be using 2 click(s) to complete 
statistics recording to SharePoint!
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  MSSearchStatsHelper.SubmitStatistics: 
  Ending statistics recording to SharePoint!
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose  MSStatsRecorderProxy.Record: Recorded!
PID:7284 TID:7056	MTID:	2012-04-03T14:55:15		
Verbose   Publishing Search Statistics : 
  Ends with Status SUCCESSFUL: 0

EktronQuerySuggestion Logs

IMPORTANT: EktronQuerySuggestion Logs are not available for the Solr search provider.

This log shows the number of entries for the query prefix. For the example below, the user entered ‘samp’ and Autosuggest found one entry (sample). To access the log, sign on to the Search Server machine > EktronSearchSite Web root > click EktronQuerySuggestion folder.

PID:7900 TID:5168	MTID:	2012-04-04T08:51:18		
Verbose  QueryContext.Create: Creating QueryContext /
PID:7900 TID:5168	MTID:	2012-04-04T08:51:18		
Verbose  QueryContext.Create: Created QueryContext /
PID:7900 TID:5168	MTID:	2012-04-04T08:51:18		
Verbose  QueryServiceInfoProcessor.GetSearchApp for 
  QuerySSA:Search Service Application
PID:7900 TID:5168	MTID:	2012-04-04T08:51:18		
Verbose  QueryServiceInfoProcessor.GetSearchAppProxy for 
  QuerySSA:Search Service Application
PID:7900 TID:5168	MTID:	2012-04-04T08:51:18		
Verbose  SPQuerySuggestionReporter.GetQuerySuggestions: 
  Q:[samp] Profile:[]
PID:7900 TID:5168	MTID:	2012-04-04T08:51:18		
Verbose  SPQuerySuggestionReporter.GetQuerySuggestions: 
  Response for Q:[samp] : [1]
PID:7900 TID:5168	MTID:	2012-04-04T08:51:18		
Verbose  SPQuerySuggestionFeed.QuerySuggestionForProfileFeed: 
  completed feed request: Q:samp Culture:en-US

Using a Search Phrase Report

The Search Phrase Report displays terms that were entered into a Search field within a selected range of dates. You can use it to discover terms being submitted to the search.

The report is gathered from the query text of keyword-based queries. The queries include those submitted through the search field of search server controls, the keyword search API, and the Workarea’s Search Published tab.

You can narrow down the search by selecting any combination of these criteria.

• language—the language of the search page (either Workarea or website search). The user performing the search can choose a language before inserting the search text. If he does not explicitly choose a language, the search uses the default one. This report shows results from all languages or one that you select.
• a minimum number of occurrences of the word or phrase to return. For example, you only want words or phrases searched for 10 times or more during the last month.
• range of dates when searches were conducted

After entering search criteria, click Get Result.

The search results show the number of times each word or phrase that satisfies the selection criteria appears. They are arranged in this order.

• words or phrases with the most occurrences appear first
• if several words or phrases have the same number of occurrences, they are arranged alphabetically

NOTE: Search terms are added to the Search Phrase Report according to rules explained in Specifying the Frequency of Writing to the Database.

Also, terms entered into the website or Workarea search are surrounded by parentheses (). Terms entered into the Advanced Workarea search have no parentheses. The Microsoft search engine uses this syntax to find content.

Solution 1: Make sure the Visio iFilter is installed. See Installing the Visio IFilter.

Solution 2: Does the content have a non-standard alias extension? Aliases that use standard extensions are not a problem. However, you can create custom alias extensions. See Also: Creating User-Friendly URLs with Aliasing. If you do, that content is searchable only if you add the custom extension to Search Server's extension list. From the Search Server Administration page, click File types > New File Type, and add the custom extension. Then, run a full crawl to index these pages.

Solution 3: Is the content stored in a Smart Forman Ektron-defined Web page that contains XML (hidden from the end user) to display content, and receive, verify, and save user input. field whose type is content? Search does not support Smart Form fields with an Advanced type of Content (instead of Attribute or Element). Smart Form fields that need to be indexed must have a type of Attribute or Element.

Solution:

1. Make sure the metaconfig.doc file exists in the siteroot/uploadedfiles directory. If it does not, ask Ektron Support to send you a new file.
2. If anyone uploaded Visio documents to your server, make sure the iFilter is installed. See Installing the Visio IFilter.