Getting the dreaded "Cannot index queue items, the index is currently locked" in the LogViewer and when I go to "Settings"->"Examine Management" I get "Failed to retrieve indexer details" error. Anybody know what's up?
I have the same problem, also on Simply.com hosting. Did you find a solution? In backend I can´t get to rebuild index since the Examine Management dashboard won´t load but only show this error:
Server error: Contact administrator, see log for full details. Failed
to retrieve indexer details
I never found a solution for this. Also. nobody from the core team seemed interested in fixing this. Ended up I lost the client because they were dissatisfied with Umbraco and because I had recommended it to them. $15.000 down the drain.
It seems to me that there are multiple causes of this. Rebuilding the internal indexes worked for some people, but not for me.
I deleted the entire wwwroot folder on my azure app service and deployed from source again. The problem went away.
I have had other issues in the past that are solved by deleting the folder and deploying again. But notnsure if it's azures deployment scripts fault or umbracos fault.
Umbraco 8.3 index lock error
Getting the dreaded "Cannot index queue items, the index is currently locked" in the LogViewer and when I go to "Settings"->"Examine Management" I get "Failed to retrieve indexer details" error. Anybody know what's up?
Site is running on Unoeuro (Now Simply.com).
Do I need to delete any temp files maybe?
I should add that I'm running a site with multiple domains and I've read somewhere that Umbraco 8 might have issues with that?
Hi Tony,
I have the same problem, also on Simply.com hosting. Did you find a solution? In backend I can´t get to rebuild index since the Examine Management dashboard won´t load but only show this error:
Hi Martin,
I have the same error now too. Did you ever find a solution?
Same here: Have not found any solution, unfortunately.
I never found a solution for this. Also. nobody from the core team seemed interested in fixing this. Ended up I lost the client because they were dissatisfied with Umbraco and because I had recommended it to them. $15.000 down the drain.
Yikes. That sounds awful.
It seems to me that there are multiple causes of this. Rebuilding the internal indexes worked for some people, but not for me.
I deleted the entire wwwroot folder on my azure app service and deployed from source again. The problem went away.
I have had other issues in the past that are solved by deleting the folder and deploying again. But notnsure if it's azures deployment scripts fault or umbracos fault.
Anyone found a solution to this problem, please? I am having the same issue on a multi site website.
Same issue here!
Usually fixed by deleting all indexes and restarting app-pool.
But it keeps coming back. 🙃
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.