EV Indexing Service failing to start after upgrade
Hi
I've just upgraded an EV server from EV14.5 to EV15.2 and during post upgrade testing we noticed that an EV search would only return results from the elastic search indexes and nothing from the legacy indexes.
Prior to upgrading to EV14.5 the server was running EV12.5 and using the old legacy indexes only - upgrading to EV14.5 introduced the elastic search indexing engine which was working fine along with the older indexes - both were visible when looking at the properties of the EV indexing service within the VAC.
When we completed the upgrade to EV15.2, everything initially looked ok and I could again see both the elastic indexes and legacy indexes from within the properties of the EV indexing service within the VAC. I think this time there were separate tabs for the two different indexes when I opened the Index service properties.
However, during testing of random EV searches we noticed we could only see recently archived items that had been indexed to the elastic search location and items indexed to the old indexes just weren't showing up in the search results. This was accompanied by warning events in Event Viewer saying that index folders were either 'missing or empty'. I also, again, looked at the properties of the Indexing service and the only tab present now was for the elastic search location. The tab for the old indexes had vanished. The physical index files are still there on the server in the same location.
At this time the indexing service was still running. I restarted the service but it now it fails to start with the following error "The Elasticsearch Indexing Engine could not complete all the required startup routines: More that one Elasticsearch index location are configured. Either enable multiple locations support or configure a single location to resolve this issue. Service will be stopped"
So it looks like EV is not starting because it thinks it has TWO Elasticsearch locations instead of ONE Elasticsearch location and ONE legacy index location.
Has anyone had any similar issues when upgrading to EV15.2?
many thanks in advance
Hi
Thanks - we did work with Support and this turned out to be an issue with the directory database. It appeared that, following the upgrade, the IndexRootPathEntryID table had got a bit messed up and it had incorrectly set the old 64bit indexes as a second Elasticsearch index location. We compared the table information with a backup of the 14.5 directory database (from when it was working at 14.5) and saw the issues. We needed to change the index 'type' to mark the index as a 'non-elastic' search location as well as input the index folder path. So a manual update of the directory database fixed the issue. Many thanks
