Under review

SQL Database Breaks with 20.8 Update

Chris H 1 year ago updated by michael.obrien 1 year ago 1

We have an instance that has been running with a SQL database for many years (yes, technically unsupported), and it seems that 20.8+ has made some significant changes to its database connection code such that the database no longer functions.

Though unsupported, it does appear that the code has a number of references and provisions for SQL and Oracle databases besides SQLite, and I'd love to see some tweaks made to allow SQL to function again.

From my troubleshooting and debugging, my best guess is that the issue lies within the DbExtensions class in the ScreenConnect.Server assembly.

The error we see starting in 20.8 that we do not see in 20.7 and prior is:

System.ServiceModel.FaultException`1[ScreenConnect.SessionManagerFault]: ExecuteNonQuery requires the command to have a transaction when the connection assigned to the command is in a pending local transaction.  The Transaction property of the command has not been initialized. (Fault Detail is equal to ScreenConnect.SessionManagerFault)

Info I found about this error: https://stackoverflow.com/questions/10648718/executenonquery-requires-the-command-to-have-a-transaction-error-in-my-code/10649035

It seems there may be some minor syntax adjustments needed when executing the ExecuteNonQuery method for SQL to cooperate.

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:

Seeing the exact same issue on SQL server. Honestly, would prefer to use Postgres all things considered :)