UmbracoExamine.UmbracoContentIndexer.ReIndexNode Exception on Publish
After adding a new custom Examine IndexSet I get this when publishing nodes of the type that the index set is indexing. I've read of similar issues on the forum but got the impression this was resolved - any pointers appreciate?
Are you using multiple document types in the <IncludeDocTypes> setting?
I've had a similar issue and it was because the custom index was indexing fields that didn't exist in all the doc types that index set was for. If that's the case the way to get around it is to manually add the field (if it's there) in the GatheringNodeData event.
Did you resolve this issue. I am also facing same issue, I have index with no user fields or exclude nodes, but still it fails to save and publish the pages.
If I remove the index completely the publish works fine.
Did some debugging (got source for Examine) and I was getting a 'no node published for id XXX' when it was trying to re-index the node. Some very unsafe code there - was actually failing writing a log funnily enough. Not sure why my node is not published however.
I'm pretty sure in my case I tracked it down through a process of elimination by adding the "IndexUserFields" proeprties in one by one until the problem occurred. I think it was down to a misspelled or missing doctype property.
Shannon Deminick's comment also worked for me, I completely emptied the Recycle Bin then 'Republished Entire Site' and then the Save and Publish option was working again for me.
UmbracoExamine.UmbracoContentIndexer.ReIndexNode Exception on Publish
After adding a new custom Examine IndexSet I get this when publishing nodes of the type that the index set is indexing. I've read of similar issues on the forum but got the impression this was resolved - any pointers appreciate?
Are you using multiple document types in the <IncludeDocTypes> setting?
I've had a similar issue and it was because the custom index was indexing fields that didn't exist in all the doc types that index set was for. If that's the case the way to get around it is to manually add the field (if it's there) in the GatheringNodeData event.
/Euan
No I am only using a single doctype, index configured as follows:
OK, not that then...
Have you tried removing the eventImage field to see if it is that issue with XML serilization?
Hi Simon/Euon,
Did you resolve this issue. I am also facing same issue, I have index with no user fields or exclude nodes, but still it fails to save and publish the pages.
If I remove the index completely the publish works fine.
Here is the index defination.
Sanjay
I don't recall exactly but it is case sensitive so can you check that things like parentID should not actually be parentId ?
Anyone get to the bottom of this one? Now I got me this issue.
Did some debugging (got source for Examine) and I was getting a 'no node published for id XXX' when it was trying to re-index the node. Some very unsafe code there - was actually failing writing a log funnily enough. Not sure why my node is not published however.
I'm pretty sure in my case I tracked it down through a process of elimination by adding the "IndexUserFields" proeprties in one by one until the problem occurred. I think it was down to a misspelled or missing doctype property.
http://issues.umbraco.org/issue/U4-1491#comment=67-4953
Shannon Deminick's comment worked for me. Deleted items in recycle bin.
Shannon Deminick's comment also worked for me, I completely emptied the Recycle Bin then 'Republished Entire Site' and then the Save and Publish option was working again for me.
:D
Just 'Republishing Entire Site' worked for me
Hi,
I had the same problem after making a copy of an EC2 Umbraco website.
I deleted all the ExamineIndexes in APP_Data\TEMP and now I can publish again :)
Cheers
Bjørn
is working on a reply...