Staged Upgrade Approach & Version Compatibility Query - Adaxes 2025.1

Question

Hi team,

We are running version 2025.1 - 3.17.23904.0 with three servers and one SQL server. Two of the three servers are used for web access behind a load balancer.

We would like to install the new version on only one server and test it before updating the others.

Could we do the following?

• Install the new version on Server 2
• Shut down/stop the service on Servers 1 and 3
• Test and check Adaxes on Server 2
• Then either update Servers 1 and 3, or reinstall the old version on Server 2 if needed

Do you recommend any other approach? Are there any compatibility issues if we revert to the previous version (internal database/settings and SQL logging database)?

Answer 1

Hello,

The approach will not work and is highly not recommended. First of all, Adaxes 2026.1 is not compatible with 2025.1. Also, stopping Adaxes services sharing common configuration will produce a lot of errors and might lead to unpredictable results. The only recommended option to test the new version before upgrading the entire Adaxes environment is to install Adaxes 2026.1 on a separate computer. This way you can keep using Adaxes 2025.1 and test the latest version separately. Once the testing is completed, you can just uninstall Adaxes 2026.1 from the separate computer and then upgrade your Adaxes environment if suitable.