Corrupt session database after maintenance run

Would you share on which version are you currently?

I am now on version   24.2.10.8991   

I have setup to run the maintenance plan on saturday evening

Yesterday (sunday), i don't think the database itself was corrupt, i only needed to restart the services.   

Are there logfiles i could sent you?

I was wondering because we noticed the same issue, it started a few months ago. What issue did you have yesterday that you needed to restart services? If the database didn't corrupt this time, what made you restart the services?

Slightly off-topic but we moved to MSSQL rather than SQlite3.

When i first had this problem, i only deleted the session.db file, restarted the services and it worked, but some guests were not correctly ordered any more.

After that, i restored from a backup.

But to speed this up, i added a little script last week to make a copy from the session.db file a few hours before maintenance runs.   But i also updated to the latest version.

After maintenance, i couldn't open the web interface (error on screen), stopped the session service tried to reuse the backup of the session.db file, but this did not work.  

I then opened the original session.db with a sqlite3 viewer, and everything was ok with the database.

So i now stopped all services, put the original session.db back, and restarted the services, and voila it was working again.

Since i'm working alone here (1 license), and only have 150 a 200 guest machines active, i don't have the need for a better database, but if this continues i might concider it.

I had a maintenance plan run yesterday evening.

Fault message is :   Database disk image is malformed

Exception Details: System.ServiceModel.FaultException`1[[ScreenConnect.SecurityManagerFault, ScreenConnect.Server, Version=24.2.10.8991, Culture=neutral, PublicKeyToken=4b14c015c87c1ad8]]: database disk image is malformed
database disk image is malformed

After stopping and restarting all 4 services, all was good again.

Sorry for kinda ignoring you here. I hope the issues stopped for you. Or are they still happening? I plan to upgrade to 24.2.10 with our MSSQL setup and see how it goes. We hadn't had any crashes or issues for quite a while now, version 24.1.9 still. Moving from sqlite3db to mssql definitely made our life peaceful.

yes, still the same problem, but restarting the services solves it every time.

I am on version   24.3.1.8998   (think this is was a debug version).     I will update today to the latest version and see next week what the result is.   (maintenance runs 1 time per week on saterday night)

I see but the 24.3.3 won't help you either. You should completely disable maintenance plan / actions. Based on the size of your instance it won't be a problem.

The other option is to tweak the maintenance actions and remove actions 1 by 1 until you find the offending action which causes the issue.

Ok, i removed all actions.   

But before +/- 2 months, i never have seen this problem.   Using screenconnect for many years.

Yeah, I believe it is happening for almost everyone but people aren't bothered to post about it. You got the time right and the behavior is exactly the same. Not sure how but one of those maint. actions or perhaps multiple are causing the issue so its safer to just have it disabled.