Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • kristian schneider 190 posts 351 karma points
    Jan 25, 2011 @ 10:02
    kristian schneider
    0

    Examine fails with exception while indexing

    I have a suspicion that parts of my node tree does not get indexed because of an exception that happens when the site is indexed.

    I've installed Examine Index Admin to get a bit more control over the indexing process and when I try to index my site I get the following exexption and stacktrace:

    [InvalidOperationException: Sequence contains more than one matching element]
    System.Linq.Enumerable.SingleOrDefault(IEnumerable`1 source, Func`2 predicate) +1303647
    UmbracoExamine.LinqXmlExtensions.UmbSelectDataValue(XElement xml, String alias) +704
    UmbracoExamine.LuceneExamineIndexer.GetDataToIndex(XElement node, String type) +918
    UmbracoExamine.LuceneExamineIndexer.AddNodesToIndex(String xPath, String type) +449
    UmbracoExamine.LuceneExamineIndexer.IndexAll(String type) +2314
    UmbracoExamine.LuceneExamineIndexer.RebuildIndex() +494

    This error occurs both with the standard InternalIndex and my custom index.

    Any Ideas?

  • Ismail Mayat 4511 posts 10091 karma points MVP 2x admin c-trib
    Jan 25, 2011 @ 15:25
    Ismail Mayat
    0

    kristian,

    In the directory where you have your indexes eg ExamineIndexes or Temp/ExamineIndexes delete the whole folder eg if you have folder called Internal for your internal index delete that then rebuild. It may be something with the lock file that is causing the issue but removing the folder then rebuilding "should" clear the issue.

    Regards

    Ismail

  • kristian schneider 190 posts 351 karma points
    Jan 25, 2011 @ 19:26
    kristian schneider
    0

    Hi Ismail.

    Thanks for the input put unfortunately that did not work.

    I have a suspicion that it fails at a particular node. If I could find out what node that is I might be able to figure out what is causing this.

    I've tried to subscribe to some of the events that examine fires while indexing but none seem to occur before this error happens.

    /kristian

  • kristian schneider 190 posts 351 karma points
    Jan 29, 2011 @ 19:09
    kristian schneider
    0

    By using the divide and conquer method I removed parts of my site tree and thereby found out it was caused by blog4umbraco.

    For some reason it failed when trying to do its Autoping. So I removed that handler from its eventcode and now it works:

      public class Autoping : ApplicationBase
        {
            public Autoping()
            {
              //  Document.AfterPublish += new Document.PublishEventHandler(Document_AfterPublish);
            }
Please Sign in or register to post replies

Write your reply to:

Draft