Local message search event index failed to initialise
See original GitHub issueSteps to reproduce
- My local event index got corrupted on Element Desktop
- Try to follow the options to recover
- That didn’t work, disable search altogether
- Try to re-enable it
Outcome
What did you expect?
For the event crawler to do it’s job
What happened instead?
The above will spin forever… Looking at the console I can see
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'addInitialCheckpoints')
at EventIndexPanel.tsx:129:15
Operating system
macOS
Application version
No response
How did you install the app?
No response
Homeserver
No response
Will you send logs?
No
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
"Message search initialisation failed, check your settings for ...
I see a message saying "Message search initialisation failed, ... EventIndex: Error initializing the event index {"message":"Error opening ...
Read more >Fix Failed Database Content Index for Exchange Server 2013
The content index is stored in a folder named for the GUID of the database. Delete the folder. Repeat the same steps to...
Read more >Error Message on indexer console - Splunk Community
message = Failed to send message to external search command, see search.log. severity = error. [CLUSTER] name = Event-Clustering Search ...
Read more >Event ID: 41315 A search failed with error "The search did not ...
Event ID: 41315. Task Category: Index Query Server Level: Warning Computer: EVSERVER01.ev.local. Description: A search failed with error ...
Read more >Windows Search Indexer stopped working and was closed
If the Search Indexing option or Indexer is not working or running ... error message – Windows could not start the Windows Search...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems related - I just got this:
It feels frustrating to rely on me to click the “unbreak my software” button when Element could have elected to rebuild the index upon discovering that it is (presumably irretrievably) corrupted?
Also, the only way to fix this is hidden in an “advanced” dropdown.