I'm seeing the exact same issue... It almost always happens the first time this runs, and then pops up again randomly...
I've been going nuts over this for a few weeks now.
My Query is even simpler;
var query = searcher.CreateQuery("content").NodeTypeAlias("lmeWarehouse");
ISearchResults searchresults = query.Execute();
I've tried splitting this up as well, so that the IQuery is created first (CreateQuery("content")) and then added the boolean-operations afterwards, but the error is still persisting (Umbraco 9.5.0).
I'm going to try to use nativequery instead of the examine API next to see if I can get around this..
Sorry, this is not really an answer, but good to know that I'm not the only one going nuts about this...
Weird error - "cannot parse" - returned by examine search
I am getting a strange error from a basic examine query, it looks like:
or like:
The query is simple:
The error happens on execution:
Anyone knows what's going on and what this error means?
I had the same data in Umbraco 7 site and all worked well. I had never such or similar error returned by the searched content.
It usually happens on the first result search. I I reload the page the results are fetched with no issues.
I'm seeing the exact same issue... It almost always happens the first time this runs, and then pops up again randomly...
I've been going nuts over this for a few weeks now.
My Query is even simpler;
I've tried splitting this up as well, so that the IQuery is created first (CreateQuery("content")) and then added the boolean-operations afterwards, but the error is still persisting (Umbraco 9.5.0).
I'm going to try to use nativequery instead of the examine API next to see if I can get around this..
Sorry, this is not really an answer, but good to know that I'm not the only one going nuts about this...
Cheers, Niels
Someone found a workaround here; https://our.umbraco.com/forum/using-umbraco-and-getting-started/108739-umbraco-9-search-eof
Niels, I am glad too that it is not something I messed up!
Thanks a lot for sharing the workaround, I'll try to see if it fix my issue and report.
I can confirm I have not the problem since I added NativeQuery so your solution works.
is working on a reply...