Arlecho's ScreenConnect 6 releases

[Arlecho]

Not sure what to do with this one, tried all kinds of changes to the DB Maintenance, tried rebooting the server multiple times, all without any issues.

Could you try stopping the server and using a sqlite editor to view and optimize the DB files?

[Sinauth]

Not sure what to do with this one, tried all kinds of changes to the DB Maintenance, tried rebooting the server multiple times, all without any issues.

Could you try stopping the server and using a sqlite editor to view and optimize the DB files?

How can it be this? I delete sessiondb, start SC, new sessiondb creates, 10 seconds later I stop and restart and sessiondb is already fucked.

Do you want to arrange a time to connect to one of my computers or screen share via Discord or something?

[Mr_sjappie]

I have the same problems, after upgrading to 23.4.3.8545 and patching....

Repair did not help.

What can I do to help test and find the cause ?

Now reverted back to the previous version.

[mikepool]

I finally cut my losses... I believe the database has some sort of corruption or maybe an extension altered the database which is causing the failures.

I recorded all of my settings & customization and performed a fresh install which is working just fine. It was a lot of work and I had to re-install all of my access clients but I spent far less time on the fresh install than I did troubleshooting the failed upgrades.

[Sinauth]

I finally cut my losses... I believe the database has some sort of corruption or maybe an extension altered the database which is causing the failures.

I recorded all of my settings & customization and performed a fresh install which is working just fine. It was a lot of work and I had to re-install all of my access clients but I spent far less time on the fresh install than I did troubleshooting the failed upgrades.

Yeah, I don't know in what capacity you're using it, but here's mine https://imgur.com/CjBOmgR

I need to resolve the issue. It should be something fairly simple.

[mikepool]

I need to resolve the issue. It should be something fairly simple.

Have you found a way to view the structure of the database? Maybe perform a fresh install on a temp VM and compare it's database structure to your existing database. Also look at the database structure of the existing database before and after a server reboot to see is something changed.

Mine got to the point to where it would not do anything with the old database. If I deleted it, it would not regenerate and replacing it with a backup stopped working too.

[Sinauth]

I need to resolve the issue. It should be something fairly simple.

Have you found a way to view the structure of the database? Maybe perform a fresh install on a temp VM and compare it's database structure to your existing database. Also look at the database structure of the existing database before and after a server reboot to see is something changed.

Mine got to the point to where it would not do anything with the old database. If I deleted it, it would not regenerate and replacing it with a backup stopped working too.

I've not looked into SQL lite as of yet. I will have time this Sunday to being comparing a new install to the existing installs. Do you (or Arlecho) know what generates SessionDB?

Edit: We need to get to the bottom of this and not just ignore it with fresh installs. What if this happens again next upgrade or 12 months down the line? Pain.

[mikepool]

Edit: We need to get to the bottom of this and not just ignore it with fresh installs. What if this happens again next upgrade or 12 months down the line? Pain.

Well, that's what a paid license and support are for. Without that, you take the path that makes the most sense. It's nice to get to the bottom of things but sometimes it's wiser to cut your losses and move forward if you do not have the knowledge or needed resources at your disposal. This is the first issue of this kind in how many years?

Because I don't have paid support, I've streamlined my installation with less customization and extensions (K.I.S.S.) and I'm going to script my uninstall/reinstall of Access clients so if something similar happens again, my next experience will be near "painless".

[Dolphin34]

I need to resolve the issue. It should be something fairly simple.

Have you found a way to view the structure of the database? Maybe perform a fresh install on a temp VM and compare it's database structure to your existing database. Also look at the database structure of the existing database before and after a server reboot to see is something changed.

Mine got to the point to where it would not do anything with the old database. If I deleted it, it would not regenerate and replacing it with a backup stopped working too.

I've not looked into SQL lite as of yet. I will have time this Sunday to being comparing a new install to the existing installs. Do you (or Arlecho) know what generates SessionDB?

Edit: We need to get to the bottom of this and not just ignore it with fresh installs. What if this happens again next upgrade or 12 months down the line? Pain.

While I'm sure everyone here can sympathize, keep in mind this is freely given of Arlechos time, and demanding posts like this are what cause far too many talented devs to leave the scene over time.  Not to mention if you're honestly using this software for that many machines, it's pretty certainly business related which is where there's a case to be made about the wisdom of investing in the stability & support of official channels. 

I'm not trying to be an ass here, but Arlecho does this shit for free.  And when clean installs don't have the issue there's just not really much else Arlechos needs (or can reasonably be expected to) devote his valuable time troubleshooting.

[Arlecho]

This is a hard one to debug, cannot replicate it myself and a lot of people seem to be having no issues.

If you are reliant on this product and cannot accept downtime or some time loss due to debugging, buy the product.

One can always contact their support forum and just report broken upgrades (or even just search there to start with).

As soon as someone finds a promising lead I'll most definately help debug it and maybe even help patch it if possible.
Quite simply I do not have the time to fix what is most probably a bug in their product