Database locks

[ITSyncForce]

We are running ASG RemoteDesktop 2020 patch 3 and getting errors about cleaning up the logs when starting ASG (a couple of co-workers are still on 2019 and get the same error). Further investigation tells us that there are locks on the database. Eventually most of the time ASG will open but not always, it just stays in this loop and clicking Ok will just result in a new message.

Is there a fix for this?

[Michael Scholz]

Hi,

Please check if you have limited the log count settings under "Settings -> Logs" and set a maximum of log entries or a time frame . It's possible that the log size is too big and the action takes to long. So set it to maybe 100 entries and restart ASG-RD. The Logs will be truncated on startup of ASG-RD. Does that help ?

Best regards,
Michael

[ITSyncForce]

Hi,

Please check if you have limited the log count settings under "Settings -> Logs"  and set a maximum of log entries or a time frame . It's possible that the log size is too big and the action takes to long. So set it to maybe 100 entries and restart ASG-RD. The Logs will be truncated on startup of ASG-RD. Does that help ?

Best regards,
Michael

100 entries?

We have a 16 member team using ASG and we need at least 6-12 months of security logs. At this moment we have only the logging from this year and that are 15100 rows.

[DevOma]

Do you have a detailed error message from error log or Windows Application Event log?

[ITSyncForce]

The problem seems to have been solved. When Delete log entries older than and maximum number of entries is both enabled this will cause a conflict.

[DevOma]

Ok - all the delete commands were performed inside one database transaction - perhaps that causes the locks if entries are deleted by more than one criteria - we will think about to remove the transaction on this function!