Copied to clipboard

Flag this post as spam?

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


  • Kurniawan Kurniawan 202 posts 225 karma points
    Nov 11, 2010 @ 03:15
    Kurniawan Kurniawan
    0

    Generate ExamineIndexes\Internal\Index

    Hi,

     

    I always get this error when doing internal search.

     

    no segments* file found in Lucene.Net.Store.SimpleFSDirectory@App_Data\TEMP\ExamineIndexes\Internal\Index: files:

     

    I have try to delete examineIndex folder and restart the server. It will create the new one. but still leave the /index empty.

     

    Do you know how to trigger umbraco to generate the index file ?

     

    Thanks

  • Qube 74 posts 116 karma points
    Nov 11, 2010 @ 03:22
    Qube
    0

    For me? Publish a page, wait a minute, done.

  • Kurniawan Kurniawan 202 posts 225 karma points
    Nov 11, 2010 @ 03:48
    Kurniawan Kurniawan
    0

    I have try to publish a page, but in some reason, it will not create the index file.

     

    In umbraco log, there is no error, But just don't create that index file.

  • Kurniawan Kurniawan 202 posts 225 karma points
    Nov 11, 2010 @ 03:56
    Kurniawan Kurniawan
    0

    It creates the index after I do some changes on the node and publish it.

     

    But I can't get other node to be indexed and when I search it didn't comes up.

    It only index the changes and when I publish it per node.

    When I publish in the root (content), It doesn't reindex it all.

    So it means, I have to back up my ExamineIndex as well  ? because if it is lost it's hard to create it ? Is it true ?

     

    Thanks

  • Kurniawan Kurniawan 202 posts 225 karma points
    Nov 11, 2010 @ 04:06
    Kurniawan Kurniawan
    0

    I just notice that It only index when you hit save / save and publish on the page it self.

    It doesn't reindex when you publish it on right click menu on the tree.
    And it will not reindex when you publish wiht child as well.

    So I need to go through all the pages, and hit save or publish so to get all indexed.

    Is that true ?

     

    Thanks

  • Qube 74 posts 116 karma points
    Nov 11, 2010 @ 04:35
    Qube
    0

    You don't need to publish every page. Indexing seems to be triggered by publishing (any publishing), and will spider through all content to fill in the gaps it needs. So, publish one thing and then be patient while it indexes for you.

  • Nick 19 posts 39 karma points
    Feb 11, 2011 @ 04:20
    Nick
    0

    Hey KK,

    Did you able to solve this issue? i m facing the same issue...

     

  • Kurniawan Kurniawan 202 posts 225 karma points
    Feb 11, 2011 @ 04:40
    Kurniawan Kurniawan
    0

    Hi Nick,

    It seems the spider is not fully working.

    I still have to hit Save & Publish to be appear in search result on the page it self.
    It may be because it corrupted when I use SVN on the index data.

    But still not sure, may be have to hide this search box for client.

    Please let me know if you find anything.

     

    Thanks

  • Nick 19 posts 39 karma points
    Feb 11, 2011 @ 04:45
    Nick
    0

    Hey KK,

     

    Its nilay from VJ...my problem is in Indx folder i have segments.gen and segments_1 files and Queue folder is full of file.

    Spider is not genrating any .cfs file in index folder out of those Queued file.

    Its working on local and staging.

    Any clue?

    Thanks

     

  • Kurniawan Kurniawan 202 posts 225 karma points
    Feb 11, 2011 @ 04:50
    Kurniawan Kurniawan
    0

    Hi Nilay,


    Great to hear from you.. lol

    I still hasn't get time to have a look into more detail.

    But it's weird for me, there is live project which works properly fine.

    but on my local server/ staging. it doesn't work.

    and for quick search I get this error in javascript.

    s.indexOf is not a function 

    at Jquery.AutoComplete.

    It even doesn't search for member and media as well.

    Not sure why ?

    May be there is configuration which not properly configured for this.

  • Nick 19 posts 39 karma points
    Feb 11, 2011 @ 04:53
    Nick
    0

    Hey KK,

    My problem is not working on Live and working on local and staging so cant be configuration...

     i m stuck :(

     

     

     

  • Kurniawan Kurniawan 202 posts 225 karma points
    Feb 11, 2011 @ 04:59
    Kurniawan Kurniawan
    0

    try to delete TEMP/examineIndexes

    stop the server first before delete.

    after you can clear all that file..

    then start again, as it will start reindex it again.

     

    I am trying now, but as I remember it still won't work.

    but may be it's just a matter of time. may be you can't recompile or update until it reindex for couple hours.

  • Nick 19 posts 39 karma points
    Feb 11, 2011 @ 05:13
    Nick
    0

    Hey, ,

     

    I tried that yesterday. I deleted all the folders  folders under  TEMP/examineIndexes and recycled the pool and appliled permission again on Add_data folder and publosh one node but it just created segments.gen and segments_1 files nothing else..

  • Kurniawan Kurniawan 202 posts 225 karma points
    Feb 11, 2011 @ 05:31
    Kurniawan Kurniawan
    0

    I also try still same it will generate the segments.gen until I do save and publish on the node it self.

     

    and Currently I just check the sorting on the root node (Content).

    I get this error. Have you ever face the same problem ?

     

    THanks

    No Document exists with Version '00000000-0000-0000-0000-000000000000'

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.ArgumentException: No Document exists with Version '00000000-0000-0000-0000-000000000000'

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


    Stack Trace:

    [ArgumentException: No Document exists with Version '00000000-0000-0000-0000-000000000000']
    umbraco.cms.businesslogic.web.Document.setupNode() +1469
    umbraco.cms.businesslogic.CMSNode..ctor(Guid uniqueID) +429
    umbraco.cms.businesslogic.Content..ctor(Guid id) +91
    umbraco.cms.businesslogic.web.Document..ctor(Guid id) +107
    umbraco.cms.businesslogic.web.Document.GetRootDocuments() +421
    umbraco.cms.presentation.sort.OnPreRender(EventArgs e) +1490
    System.Web.UI.Control.PreRenderRecursiveInternal() +113


    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4185
  • Nick 19 posts 39 karma points
    Feb 11, 2011 @ 05:34
    Nick
    0

    No..I thnik delete all the folders under Temp and that should fix it...

  • Kurniawan Kurniawan 202 posts 225 karma points
    Feb 11, 2011 @ 05:58
    Kurniawan Kurniawan
    0

    try to delete TEMP/examineIndexes

    stop the server first before delete.

    after you can clear all that file..

    then start again, as it will start reindex it again.

     

    I am trying now, but as I remember it still won't work.

    but may be it's just a matter of time. may be you can't recompile or update until it reindex for couple hours.

  • Kurniawan Kurniawan 202 posts 225 karma points
    Feb 11, 2011 @ 06:21
    Kurniawan Kurniawan
    0

    have you installed a umbraco plugin recently ?

     

    try to check a ghost node in your data.

    SELECT * FROM umbracoNode
    WHERE
    nodeObjectType
    = 'C66BA18E-EAF3-4CFF-8A22-41B16D66A972' -- that are of type 'Content'
    AND
    umbracoNode
    .id NOT IN (SELECT nodeId FROM cmsContent) -- but are not in the 'Content' table
  • Kurniawan Kurniawan 202 posts 225 karma points
    Feb 11, 2011 @ 06:26
    Kurniawan Kurniawan
    0

    Hi Nilay,

     

    Finally..

    I get this all working..

    -  delete the ghost node,

    -  delete the temp/examineIndexes

    - republish all sites

    - then you will see it all queued up.

     

    I think the cause of the problem is the ghost node where not belong to cmsContent..

     

     

  • Nick 19 posts 39 karma points
    Feb 11, 2011 @ 06:27
    Nick
    0

    Query return 0 result..

Please Sign in or register to post replies

Write your reply to:

Draft