MDriven Server problem with evolve
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''NEW''': | === 2022-10-28 === | ||
'''NEW''': We now look for App_Data\MissingOrMapping.xml. If ORMapping is missing in the startup of the app and the file is found, we inject the file. The included file is version 13500 of the script. You can change it if needed. | |||
Here is a short video discussing this: https://youtu.be/vwF1rjXjCak | Here is a short video discussing this: https://youtu.be/vwF1rjXjCak | ||
Versions up till 2019-03-25 had issues with admin database evolve. | Versions up till 2019-03-25 had issues with admin database evolve. This gave the effect that upon evolving the admin database of MDrivenServer (this happens when MDrivenServer has an updated internal model), the changescript needed for doing further evolves would get ERASED. | ||
This gave the effect that upon evolving the admin database of MDrivenServer ( this happens when MDrivenServer has an updated internal model), the changescript needed for doing further evolves would get ERASED. | |||
If this happens, the MDrivenServer will not be able to evolve to newer versions. | If this happens, the MDrivenServer will not be able to evolve to newer versions. | ||
| Line 11: | Line 10: | ||
To restore this missing script, follow the instructions below: | To restore this missing script, follow the instructions below: | ||
# '''Download''' this XML [[:File:Evolve.xml]] and open it in a text editor, '''NOT '''a browser - you need to preserve the encoding of < and >. | # '''Download''' this XML [[:File:Evolve.xml]] and open it in a text editor, '''NOT '''a browser - you need to preserve the encoding of < and >. | ||
# | #* Version 2022-05-13 onwards: [[:File:OR-mapping_version_20220513.xml]] | ||
# | #* Version 13500 (2021-10-12 - 2022-05-12) : [[:File:OR-mapping_version_13500.xml]] | ||
# | #* Version 10923 (2019-04-03 - 2021-10-12) forward: [[:File:OR-mapping 10923 13499.xml]] | ||
# Go to your MDrivenServer-settings-admin | # Go to your MDrivenServer-settings-admin | ||
# Check if you have the script already (Read the current Evolve script). If not, paste the correct script based on the version + then "Write Current Evolve Script" + '''Ensure you SUCCESSFULLY LOADED THE SCRIPT by ensuring that Read CURRENT EVOLVE SCRIPT RETURNS IT.''' | # Check if you have the script already (Read the current Evolve script). If not, paste the correct script based on the version + then "Write Current Evolve Script" + '''Ensure you SUCCESSFULLY LOADED THE SCRIPT by ensuring that Read CURRENT EVOLVE SCRIPT RETURNS IT.''' | ||
| Line 30: | Line 29: | ||
If issue 3: No error is seen until a future evolve when you end up at issue 1 | If issue 3: No error is seen until a future evolve when you end up at issue 1 | ||
The correct state is | The correct state is 4. Eco_Ormapping Describes the current Schema | ||
* To solve issues 1 & 2: Grab the correct script from those available above - write it with "Write current evolve script" followed by "Evolve admin DB" | |||
To solve issues 1 & 2: Grab the correct script from those available above - write it with "Write current evolve script" followed by "Evolve admin DB" | * To solve issue 3: do "Repair admin evolve script" | ||
To solve issue 3: do "Repair admin evolve script" | |||
[[Category:MDriven Server]] | [[Category:MDriven Server]] | ||
Revision as of 07:05, 28 June 2023
2022-10-28
NEW: We now look for App_Data\MissingOrMapping.xml. If ORMapping is missing in the startup of the app and the file is found, we inject the file. The included file is version 13500 of the script. You can change it if needed.
Here is a short video discussing this: https://youtu.be/vwF1rjXjCak
Versions up till 2019-03-25 had issues with admin database evolve. This gave the effect that upon evolving the admin database of MDrivenServer (this happens when MDrivenServer has an updated internal model), the changescript needed for doing further evolves would get ERASED.
If this happens, the MDrivenServer will not be able to evolve to newer versions.
To restore this missing script, follow the instructions below:
- Download this XML File:Evolve.xml and open it in a text editor, NOT a browser - you need to preserve the encoding of < and >.
- Version 2022-05-13 onwards: File:OR-mapping_version_20220513.xml
- Version 13500 (2021-10-12 - 2022-05-12) : File:OR-mapping_version_13500.xml
- Version 10923 (2019-04-03 - 2021-10-12) forward: File:OR-mapping 10923 13499.xml
- Go to your MDrivenServer-settings-admin
- Check if you have the script already (Read the current Evolve script). If not, paste the correct script based on the version + then "Write Current Evolve Script" + Ensure you SUCCESSFULLY LOADED THE SCRIPT by ensuring that Read CURRENT EVOLVE SCRIPT RETURNS IT.
- Try to make admin evolve once more.
Admin DB Issues Described
When admin DB refuses to work, it may be due to one of these issues:
- Eco_Ormapping is empty AND the DB schema is old
- Eco_Ormapping has the newest versions - but the DB schema is old
- DB schema is new but Eco_OrMapping is empty
If issue 1: Evolve cannot run - and Repair only takes us to issue 2
If issue 2: Evolve does not discover the need to update db_schema and the admin will not start due to the old schema
If issue 3: No error is seen until a future evolve when you end up at issue 1
The correct state is 4. Eco_Ormapping Describes the current Schema
- To solve issues 1 & 2: Grab the correct script from those available above - write it with "Write current evolve script" followed by "Evolve admin DB"
- To solve issue 3: do "Repair admin evolve script"
This page was edited 90 days ago on 02/10/2024. What links here