Up until recently my index was fine. However i tried to rebuild my index and i am now getting error:
[UmbracoExamine] Error indexing queue items,The given key was not present in the dictionary., IndexSet: FairbairnIndexSet
the nodeid is -1 in the log.
when during reindex i look at queue folder i can see over 600 items it starts to process them and gets to 265 then doesnt go any further in my umbracolog i get this error repeating. I did make some changes recently to my home page doc type but i then republished the home page. I have tried removing xml cache and the index then republishing and still get same issue. I am using umbraco 452 and examine rtm.
It went away i think i deleted all old indexes (by this i mean the whole folder includign queue folder, lock file etc) removed xml cache restarted iis then republished that i think fixed it.
@Stephan, @Ismail, did either of you ever get to the bottom of your respective problems?
I have a similar error occurring in a production site: [UmbracoExamine] Error indexing queue items,The given
key was not present in the dictionary., IndexSet: WebsiteIndexSet.
This doesn't happen in either of the staging environments. The production server is load balanced, and the file system is replicated (though the Examine indexes are excluded from this). I'm wondering if this might be the cause.
I'm going to get on to the server admin to check on a few details - any pointers you might have however would be quite welcome.
I ended up reporting it as an issue on Codeplex (http://examine.codeplex.com/workitem/10008), and had a discussion with Shannon about it, but I'm not sure if the bug I found in the process was ever fixed, I could never find the root of it. I ended up reverting back to the RC3 of Examine, since it didn't fail. I had other issues with the RC3 that I was able to work around though :)
Stephan, thanks for your reply. I should be getting hold of a copy of the production system so I can try to replicate and debug the problem further. I'll post the result here, and update the bug you reference if it turns out to be related.
I had the same error. Turned out I was accessing the fields supplied in the GatheringNodeData event with a straight fields["bodytext"] approach, but some nodes didn't have the key I was specifying. Instead this is
fields.TryGetValue("bodytext", out bodyText) is safer.
Examine indexing error
Up until recently my index was fine. However i tried to rebuild my index and i am now getting error:
[UmbracoExamine] Error indexing queue items,The given key was not present in the dictionary., IndexSet: FairbairnIndexSet
the nodeid is -1 in the log.
when during reindex i look at queue folder i can see over 600 items it starts to process them and gets to 265 then doesnt go any further in my umbracolog i get this error repeating. I did make some changes recently to my home page doc type but i then republished the home page. I have tried removing xml cache and the index then republishing and still get same issue. I am using umbraco 452 and examine rtm.
Any ideas?
regards
Ismail
Hi Ismail,
did you ever get to the bottom of this? I get the same error.
Stephan,
It went away i think i deleted all old indexes (by this i mean the whole folder includign queue folder, lock file etc) removed xml cache restarted iis then republished that i think fixed it.
Regards
Ismail
Thanks for the quick reply!
I did that, deleted the cache xml, the indices and everything, rebuilt the site.
It indexes a few nodes, but then it starts again.
Oh well, we'll just have to wait and see what happens :)
I get a new log entry every 30 seconds, which is the interval I set for the Indexers (I have 9 Indexers, but only 1 is acting up.)
Is the index that is playing up based on pdfindexer?
Regards
Ismail
@Stephan, @Ismail, did either of you ever get to the bottom of your respective problems?
I have a similar error occurring in a production site: [UmbracoExamine] Error indexing queue items,The given key was not present in the dictionary., IndexSet: WebsiteIndexSet.
This doesn't happen in either of the staging environments. The production server is load balanced, and the file system is replicated (though the Examine indexes are excluded from this). I'm wondering if this might be the cause.
I'm going to get on to the server admin to check on a few details - any pointers you might have however would be quite welcome.
Regards,
JT
Hi James,
I ended up reporting it as an issue on Codeplex (http://examine.codeplex.com/workitem/10008), and had a discussion with Shannon about it, but I'm not sure if the bug I found in the process was ever fixed, I could never find the root of it. I ended up reverting back to the RC3 of Examine, since it didn't fail. I had other issues with the RC3 that I was able to work around though :)
Stephan, thanks for your reply. I should be getting hold of a copy of the production system so I can try to replicate and debug the problem further. I'll post the result here, and update the bug you reference if it turns out to be related.
@Stephan, I've found that it is the same error you reported. I'll continue on the codeplex issue and report back if I can find a resolution.
Thanks,
JT
@Stephan, @Ismail, did you have any protected content on the sites that the issue cropped up for you?
Yes!
I read your post on codeplex as well, great find!
I had the same error. Turned out I was accessing the fields supplied in the GatheringNodeData event with a straight
fields["bodytext"]approach, but some nodes didn't have the key I was specifying. Instead this isfields.TryGetValue("bodytext", out bodyText)is safer.is working on a reply...