0

The autogenerated deployment folder creates a variables.gradle file when I upgrade my application from Mendix Studo Pro version 9.x.x to 10.x.x.   When I investigated the deployment folder, I found that when the version is Mendix Studio Pro 9.24.37, the variables.gradle file looks like: excludedJars = ["commons-lang3-3.11.jar","httpclient-4.3.6.jar"]   But when I upgrade to Mendix Studio Pro version 10.0.0, the variables.gradle looks like: excludedJars = ["D:\Projects\Mendix\Intelizign\Service\MBV\AFVans-main\userlib\commons-lang3-3.11.jar","D:\Projects\Mendix\Intelizign\Service\MBV\AFVans-main\userlib\httpclient-4.3.6.jar"]   These excluded JAR files are no longer part of the project, and the path variable is not in the machine I am deploying from. NB!! I have inherited the project.  I have to upgrade to the higher versions because I want to migrate and restore my database. What could be the issue???   This is the background information:   My app was developed with Mendix Studio Pro version 9.24.22, I had to upgrade to version 10.2.0. The problem is that after I successfully copy data from the database instance that is connected to the application version that is built on Mendix Studio Pro version 9.24.22, and connect the application built in Mendix Studio Pro version 10.2.0; all the tables from all the available domains are dropped and data is deleted, and the tables are then recreated.   Upon further investigation, I found the following logs:   M2EE: An error occurred while initializing the Runtime: Unsupported pre-analysis migration version: 4.2.0. You are trying to synchronize a Mendix application database from an unsupported Mendix version.com.mendix.m2ee.api.AdminException: An error occurred while initializing the Runtime: Unsupported pre-analysis migration version: 4.2.0. You are trying to synchronize a Mendix application database from an unsupported Mendix version.at com.mendix.basis.impl.MxRuntimeImplBase.start(MxRuntimeImplBase.java:269)Caused by: com.mendix.connectionbus.ConnectionBusRuntimeException: Unsupported pre-analysis migration version: 4.2.0. You are trying to synchronize a Mendix application database from an unsupported Mendix version.DEBUG: startresponse receivedERROR: Executing start did not succeed: result: 1, message: class com.mendix.m2ee.api.AdminException occurred while executing an admin action request. See logging output for details., caused by: class com.mendix.connectionbus.ConnectionBusRuntimeException occurred while executing an admin action request. See logging output for details.   The cause of the above error is a mismatch between the database version number and the runtime version. This can happen due to changes in the project that modify system tables, triggering the database version to exceed the runtime version during deployment. When Mendix detects that the DB version is incompatible, it cannot migrate it in-place (especially if the jump skips unsupported intermediate versions). In some cases, depending on settings and environment, this can lead to Mendix deciding to recreate the schema.   The version of the database connected to the application built in Mendix Studio Pro version 9.24.22 is 4.2 with pre-analysis-migration-version-number 4.0.1, while the version of the database connected to the application built in Mendix Studio Pro version 10.2.0 is 4.2 with pre-analysis-migration-version-number 4.2.0 To workaround the problem above, I incrementally upgraded the app from Mendix Studio Pro 9.24.22 to 9.24.37 and ended up with Mendix database Runtime version 4.2 with pre-analysis Version number 4.1.0.   A new issue arrises when I upgrade the application to Mendix Studio Pro version 10.0.0, I get the following error:   FAILURE: Build failed with an exception. * Where:Script 'C:\Users\USER\Documents\GitHub\AFVans-main\AFVans-main\deployment\variables.gradle' line: 33 * What went wrong:Could not compile script 'C:\Users\USER\Documents\GitHub\AFVans-main\AFVans-main\deployment\variables.gradle'.> startup failed:script 'C:\Users\USER\Documents\GitHub\AFVans-main\AFVans-main\deployment\variables.gradle': 33: Unexpected character: '"' @ line 33, column 3."D:\Projects\Mendix\Intelizign\Service\MBV\AFVans-main\userlib\commons-lang3-3.11.jar",^ 1 error * Try:> Run with --stacktrace option to get the stack trace.> Run with --debug option to get more log output.> Run with --scan to get full insights.> Get more help at https://help.gradle.org. BUILD FAILED in 7s FAILURE: Build failed with an exception. * Where:Script 'C:\Users\USER\Documents\GitHub\AFVans-main\AFVans-main\deployment\variables.gradle' line: 33 * What went wrong:Could not compile script 'C:\Users\USER\Documents\GitHub\AFVans-main\AFVans-main\deployment\variables.gradle'.> startup failed:script 'C:\Users\USER\Documents\GitHub\AFVans-main\AFVans-main\deployment\variables.gradle': 33: Unexpected character: '"' @ line 33, column 3."D:\Projects\Mendix\Intelizign\Service\MBV\AFVans-main\userlib\commons-lang3-3.11.jar",^ 1 error * Try:> Run with --stacktrace option to get the stack trace.> Run with --debug option to get more log output.> Run with --scan to get full insights.> Get more help at https://help.gradle.org. BUILD FAILED in 7s   When I investigated the deployment folder, I found that when the version is up to Mendix Studio Pro 9.24.37, the variables.gradle file looks like:   excludedJars = ["commons-lang3-3.11.jar","httpclient-4.3.6.jar"]   But when I upgrade to Mendix Studio Pro version 10.0.0, the variables.gradle looks like:   excludedJars = ["D:\Projects\Mendix\Intelizign\Service\MBV\AFVans-main\userlib\commons-lang3-3.11.jar","D:\Projects\Mendix\Intelizign\Service\MBV\AFVans-main\userlib\httpclient-4.3.6.jar"]   I have deleted the excluded JARS, and in the app settings of the project, under the deployment tab, I do not see the excluded JARS.

asked 2025-08-20

1 answers