More in this section
Forums / Bugs & Issues / Search indexing error - some search terms break the site

Search indexing error - some search terms break the site

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
1 posts, 0 answered
  1. Dan
    Dan avatar
    11 posts
    14 Sep 2012
    17 Dec 2010
    Link to this post

    Recently we ran into the following error while updating our search index ("Administration -> Services -> Search -> Indexes -> Index -> Start Indexing):

    Exception Type: Telerik.Framework.Search.IndexExcepton
    Message: Charset not found http://mysite.local/section/subsection/page.aspx
    Exception Type: System.ArgumentOutOfRangeException
    Message: StartIndex cannot be less than zero.
    Parameter name: startIndex
    Source: mscorlib
    Stack Trace:
    at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
    at Telerik.Framework.Utilities.HtmlPageEncodingHelper.GetEncodedDataForHtmlPage(WebClient client, Byte[] buffer, Encoding encoding, String resolvedUrl)

    What's worse was that running a search on any term that matched the offending page would bring the site down and MAX out the CPU on the server.

    We managed to eliminate the problem by locating the page that was causing the trouble and setting it to not be indexed (Page -> Properties -> More Options -> Search Options -> Index this page? -> No).  We were able to locate the problem page by using Lucene Luke to browse the index, which was very helpful:

    However, there is obviously a sitefinity / Lucene bug that still needs to be addressed.

    The page that is causing the problem is an "external page" that is being used to provide a friendly url / redirect for another page on the site.  The page that actually contains the content does not seem to cause any issues.  Strangely, we have another "external page" set up exactly the same way, that redirects to a page that uses the same template, but it does not cause the error. 

    Our workaround at least prevents the site from breaking, but we would appreciate it if you would investigate the issue further.  Please let me know if I can provide any more information.

1 posts, 0 answered