There is a short video discussing this here https://youtu.be/vwF1rjXjCak

Versions up until 2019-03-25 had issues with admin database evolve.

This gave the effect that upon evolving the admin database of MDrivenServer (happens when MDrivenServer has an updated internal model ) the changescript needed for doing further evolves could get ERASED

If this happen MDrivenServer will not be able to evolve to newer versions.

To restore this missing script follow the instructtions below:

1. Download this XML File:Evolve.xml and open in a text editor. NOT a browser, you need to preserve the encoding of < and >.
   1. Version 2022-05-13 onwards: File:OR-mapping_version_20220513.xml
   2. Version 13500 (2021-10-12 - onwards) : File:OR-mapping_version_13500.xml
   3. Version 10923 (2019-04-03 - 2021-10-12) forward: File:OR-mapping 10923 13499.xml THIS IS THE MOST LIKELY SCRIPT YOUR SERVER NEEDS
2. Go to your MDrivenServer -settings-admin
3. Check if you have the script already (Read current Evolve scrip) - if not paste the correct script based on version + then "Write Current Evolve Script" + ENSURE YOU SUCCESSFULLY LOADED THE SCRIPT BY ENSURING THAT Read CURRENT evolve script RETURNS IT
4. Try to make admin evolve once more

Amin db issues described

When admin db refuse to work it is one of these issues:

1. Eco_Ormapping is empty AND the db schema is old
2. Eco_Ormapping has newest versions - but db schema is old
3. DB schema is new but Eco_OrMapping is empty

If issue 1: Evolve cannot run - and Repair only takes us issue 2

If issue 2: Evolve does not discover need to update db_schema, admin will not start due to old schema

If issue 3: No error is seen until a future evolve when you end up in issue 1

The correct state is: 4. Eco_Ormapping Describes the current Schema

To solve issue 1 & 2: Grab correct script from the available above - write it with "Write current evolve script" followed by "Evolve admin DB"

To solve issue 3: do "Repair admin evolve script"