Unable to Connect to your Data Source (Transaction was deadlocked)
Unable to Connect to your Data Source (Transaction was deadlocked)
Dear all
We use Remote Desktop Manager 12.5.3 and sometimes we encounter an error message. It sais:
"Unable to Connect to your Data Source. Transaction (Process ID 441) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction".
In the details section:
Devolutions.RemoteDesktopManager.Business.TryGoOfflineException: Transaction (Process ID 441) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.ExecuteScalar[T](String sql, IDbDataParameter[] parameters)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.GetMaxSessionVersion()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.HasSessionChanged()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.cf14e205cdaccd081c3d8df32d968e267(BaseConnectionDataSource c01af917dca3518ff73ed69848f95f91a)
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadConnections(BaseConnectionDataSource dataSource)
This happens, when Remote Desktop Manager is idle.
Is there anything I can do or do I have to check the data source. (Though I haven't heard from any problems with our sql server.)
Thanks for your help!
Daniel
000043.png
All Comments (7)
Hi,
I've never seen this error before. I will ask our DBA to verify if something can cause that. Could you verify your automatic refresh delay in the data source configuration?
Regards
David Hervieux
Hi David
Auto refresh is 15s. Further info: We connect to an availability group, not to the SQL server directly. But according to my DBA no failover has happened while the error occured, no maintenance work, no nothing. Weird...
Looking forward to your DBA's opinion!
Daniel
How many users connected?
Regards
David Hervieux
Atm around 25
Hi Daniel,
The error you're getting is due to another transaction (explicit or implicit) locking the resources (in this case tables dbo.Connections & dbo.ConnectionHistory in read-only).
Where is this other transaction coming from? You mentioned that "no failover has happened while the error occured, no maintenance work, no nothing" on the server while the error occurred. I would like you to double-check on your end when the next error happens just to make sure. I'm checking on my end to see if there are any reasons why RDM would trip itself up with a long-running transaction.
Could it be an issue with the availability group synchronization? We have plenty of customers running with "Always On Availability Groups" and have not heard of any issues.
Best regards,
Stéfane Lavergne
Dear Stefane
It appears this issue was a combination of several things. The main problem was an "overload" of our SQL server that happened from time to time. The other problems appeared because of a cache and config access problem. As described in Thread https://forum.devolutions.net/messages.aspx?TopicID=27830 RDM seems to be very sensible if these files are on a network drive. (We have roaming profiles with folders redirected to a network drive.)
So we are now running the portable version of RDM and save the RDM config and cache to %LOCALAPPDATA%\RDM instead of the redirected roaming profile folder.
Thanks for your help!
Regards
Daniel
Daniel,
Thank you for the update.
Best regards,
Stéfane Lavergne