Skip to main content

Hi everyone,

I have updated a control room that was on v24R2 to v27 without errors.

For context, the control room, database and elasticsearch are installed on the same windows VM.

I now want to update it from v27 to v30 but I get an error “Installer has detected that there are ElasticSearch indices that are old and cannot be migrated automatically. Setup will abort”.

 

I want to follow what has been explained here

However, I fail connecting to elasticsearch while it was possible beforehand -I have tried ports 47599, 47600, 9200, 9300)

When I go to the services, the Elastic Search service is shown active. It keeps on failing even I restart process.

On the other hand, the main website can still be reached and bots be run.

 

How can I solve this problem ?

@Augustin 

Please let me know if this helps..


@Augustin

Please let me know if this helps..

Hi Goodgist and thanks for your answer.

Those GET/POST/DELETE requests is exactly what I want to do.

Unfortunately I do not have a working url:port to send those requests.

I have tried with postman and google chrome and do not get results when requesting localhost:45799 (or other posts)


This was solved by the automation anywhere support. I had to reset the elasticsearch username and password. Then I was able to go through the migation of ES.


Hi ​@Augustin Can you please share the procedure to reset the username and password . I have the exact same issue and unable to upgrade 


Hi ​@Augustin Can you please share the procedure to reset the username and password . I have the exact same issue and unable to upgrade 

I am sorry, I don’t remember how we did. 

Perhaps you should contact the support ?


Hi ​@Augustin Can you please share the procedure to reset the username and password . I have the exact same issue and unable to upgrade 

If you have direct access to the Elasticsearch server:

  • Use the built-in tool:
cd /usr/share/elasticsearch/bin
./elasticsearch-reset-password -u <username> -i

Show more lines

  • Options:
    • -u → Username (e.g., elastic)
    • -i → Interactive mode (lets you set a custom password)
    • -a → Auto-generate a strong password
  • Ensure ES_PATH_CONF points to the correct config directory before running the command