Problems to update application Server

Hi,
I made same updates to reach finally 2026.9.1.202610230010 Date 10-22 11-58

I got the message to update the applicaton server

But it failed

I tried the command line updater

It also failed.

I installed a complete fresh servoy version at a different place, but exactly the same behavior…

Any suggestions?

Thanks and greetings from Berlin
Ralf

Hi Ralf, are you running any 3rd party plugins?

Good evening Marc,
I am only using the PDF and the jasperreport-plugins.
Best
Ralf

Are these plugins updated to the latest compatible versions?
I’ve had weird error messages when updating to 2026 branch, which was due to incompatible plugin version, as 2026 is using Tomcat 11

I think the problem here is that Servoy, for whatever reason, enable the ‘Nightly Releases’ & ‘Latest Release Candidates’ by default when updating/ installing a normal new release. So what happens is someone will do the normal update, go thru the cycle of upgrade/update/restarts and then see a dialog offering a nightly or candidate release, install it and then that doesn’t have the correct repository upgrade part in it, so you get that dialog… (this happened to me on last release when I was asked to install a nightly release to test if a bug was fixed and then got stuck each time I opened IDE with the repo upgrade dialog I had to just dismiss… [@Servoy - please turn off those options!]

Hi Rafi,
exactly - that happend to me, by accident I installed an RC-Version.
And now? Any Idea what to do?
Greetings from Berlin, Ralf

Yes, latest versions - see my answer to Rafi

Thanks, Ralf

when updating from a final release to a nightly, i will try to update the nightly application_server dir also, but that is not possible because there is no update pakackage for that.
the quickest way to fix this is to: application_server\lib\version.txt
delete that file for a moment, then it will think it is already updated just fine.

For our current releases of 2026.x this doesn’t matter except that our plugins, if you need a new jar from that you need to still download the servoy_update.zip from the nighlty site.

But for the most part everything else is gotten with a normal developer update

Hi Johann,
that worked !
And after upgrading to 2026.9.1.2026110200017 there is new version.txt-file and no message any longer
Thanks once again
Ralf

Ralf, good to hear the version.txt workaround cleared the update prompt and that the fresh file came back after moving to 2026.9.1.2026110200017. Johann’s point about plugins is the part I’d keep in mind: deleting version.txt lets the update pass, but any new jar still needs the servoy_update.zip from the nightly site. For anyone on the 2026.x releases, that seems like the only piece a normal developer update won’t fetch, so worth checking before assuming everything is current.