Server crash after upgrade to 2.2.8

Hi,

After upgrading the server from 2.1.20 to 2.2.8 (both x64 via MSI installer) the server service crashes.
Windows 2016 event log:

Faulting application name: urbackup_srv.exe, version: 0.0.0.0, time stamp: 0x5a96c89c
Faulting module name: KERNELBASE.dll, version: 10.0.14393.1770, time stamp: 0x59bf2ba6
Exception code: 0x00000000
Fault offset: 0x0000000000033c58
Faulting process id: 0x988
Faulting application start time: 0x01d3b3cf97bde2ce
Faulting application path: C:\Program Files\UrBackupServer\urbackup_srv.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 9d6ebb23-f3bd-4af9-beae-b3e04b760295
Faulting package full name: 
Faulting package-relative application ID: 

And the Urbackup Server log:

2018-03-04 10:48:48: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:48:48: ERROR: Error preparing Query [SELECT id, send_to, subject, message, next_try, retry_count FROM mail_queue WHERE next_try IS NULL or next_try>=?]: no such table: mail_queue
2018-03-04 10:48:48: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:48:48: ERROR: Error preparing Query [UPDATE mail_queue SET next_try=?, retry_count=? WHERE id=?]: no such table: mail_queue
2018-03-04 10:48:48: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:48:48: ERROR: Error preparing Query [DELETE FROM mail_queue WHERE id=?]: no such table: mail_queue
2018-03-04 10:48:48: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:48:48: ERROR: Error preparing Query [UPDATE mail_queue SET next_try=NULL]: no such table: mail_queue
2018-03-04 10:48:48: WARNING: SQLite: no such column: alerts_next_check errorcode: 1
2018-03-04 10:48:48: ERROR: Error preparing Query [UPDATE clients SET alerts_next_check=NULL]: no such column: alerts_next_check
2018-03-04 10:48:48: WARNING: SQLite: no such column: file_ok errorcode: 1
2018-03-04 10:48:48: ERROR: Error preparing Query [SELECT id, name, file_ok, image_ok, alerts_state, strftime('%s', lastbackup) AS lastbackup, strftime('%s', lastseen) AS lastseen, strftime('%s', lastbackup_image) AS lastbackup_image, created, os_simple FROM clients WHERE alerts_next_check IS NULL OR alerts_next_check<=?]: no such column: file_ok
2018-03-04 10:48:48: WARNING: SQLite: no such column: file_ok errorcode: 1
2018-03-04 10:48:48: ERROR: Error preparing Query [UPDATE clients SET  file_ok=?, image_ok=?, alerts_next_check=?, alerts_state=? WHERE id=?]: no such column: file_ok
2018-03-04 10:49:20: WARNING: SQLite: table clients has no column named created errorcode: 1
2018-03-04 10:49:20: ERROR: Error preparing Query [INSERT INTO clients (name, lastseen,bytes_used_files,bytes_used_images,created) VALUES (?, CURRENT_TIMESTAMP, 0, 0, strftime('%s', 'now') )]: table clients has no column named created
2018-03-04 10:49:20: ERROR: Fatal exception code 3221225477 at address 0x00007FF8046E59AC
2018-03-04 10:49:20: ERROR: Fatal exception (APPLICATION CRASHED). Crash dump written to "C:\Windows\TEMP\UrBackup\v2.0.0-20180304-104920-8612-9376.dmp"
2018-03-04 10:49:20: ERROR: Program abort (SIGABRT)
2018-03-04 10:50:17: WARNING: SQLite: no such column: alerts_next_check errorcode: 1
2018-03-04 10:50:17: ERROR: Error preparing Query [UPDATE clients SET alerts_next_check=NULL]: no such column: alerts_next_check
2018-03-04 10:50:17: WARNING: SQLite: no such column: file_ok errorcode: 1
2018-03-04 10:50:17: ERROR: Error preparing Query [SELECT id, name, file_ok, image_ok, alerts_state, strftime('%s', lastbackup) AS lastbackup, strftime('%s', lastseen) AS lastseen, strftime('%s', lastbackup_image) AS lastbackup_image, created, os_simple FROM clients WHERE alerts_next_check IS NULL OR alerts_next_check<=?]: no such column: file_ok
2018-03-04 10:50:17: WARNING: SQLite: no such column: file_ok errorcode: 1
2018-03-04 10:50:17: ERROR: Error preparing Query [UPDATE clients SET  file_ok=?, image_ok=?, alerts_next_check=?, alerts_state=? WHERE id=?]: no such column: file_ok
2018-03-04 10:50:17: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:50:17: ERROR: Error preparing Query [SELECT id, send_to, subject, message, next_try, retry_count FROM mail_queue WHERE next_try IS NULL or next_try>=?]: no such table: mail_queue
2018-03-04 10:50:17: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:50:17: ERROR: Error preparing Query [UPDATE mail_queue SET next_try=?, retry_count=? WHERE id=?]: no such table: mail_queue
2018-03-04 10:50:17: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:50:17: ERROR: Error preparing Query [DELETE FROM mail_queue WHERE id=?]: no such table: mail_queue
2018-03-04 10:50:17: WARNING: SQLite: no such table: mail_queue errorcode: 1
2018-03-04 10:50:17: ERROR: Error preparing Query [UPDATE mail_queue SET next_try=NULL]: no such table: mail_queue
2018-03-04 10:50:48: WARNING: SQLite: table clients has no column named created errorcode: 1
2018-03-04 10:50:48: ERROR: Error preparing Query [INSERT INTO clients (name, lastseen,bytes_used_files,bytes_used_images,created) VALUES (?, CURRENT_TIMESTAMP, 0, 0, strftime('%s', 'now') )]: table clients has no column named created
2018-03-04 10:50:48: ERROR: Fatal exception code 3221225477 at address 0x00007FF803C459AC
2018-03-04 10:50:49: ERROR: Fatal exception (APPLICATION CRASHED). Crash dump written to "C:\Windows\TEMP\UrBackup\v2.0.0-20180304-105048-9864-10116.dmp"
2018-03-04 10:50:49: ERROR: Program abort (SIGABRT)

Seems the new version requires a different DB schema which wasn’t done during the upgrade. Any advice on recovering? Or at least roll back? Thanks

EDIT: uninstalled 2.2.8, reboot, and reinstalled 2.1.10 and now the server is working again.

Hi

Uroni will most likely ask you for the crash dump.
Possibly the logs at the debug level (if theses aren’t)
And the logs from the first time you started the service after the upgrade.

Other than that i think the schema update is done at each startup.
So maybe it was marked with the new version, then somehow canceled.
Or maybe there s some kind of bug and you d need to go through an intermediate version, wait for some backup to complete so the tables are filled, then update to the latest version.