RDM Enterprise 14.0 - can not delete old sessions

Hello,

Please try to reset your cache and let us know if the issue is resolved.

https://help.remotedesktopmanager.com/troubleshooting_caching.htm

Best regards,

Hello Maurice,
i followed the URL , but nothing helps. I don't believe that this is a cache issue.. because i have several times restart RDM and on other session it's working...


Bob

Hello,

Do you see any relevant errors in the Application Logs?

Thx

Hello Maurice,
another odd behavior and maybe related to current. When i modify such a session and save it, it will NOT update this session but create a new session with the same session name.
btw.
I have backleveled my RDM to 13.6.7.0 using the same datasource and can delete all the sessions which are failing under RDM 14.0.0.0. Also the modification of a session works as expected. So it seems more an bug in RDM 14.0.0.0.
PS: new created session under 14.0.0.0 can be deleted, so it's only for old sessions..



rgs Bob

Hello,

Thx for the update.


Engineering's recommendation was to backup your database, then to use our PACK datasource feature. I guess its too late if you've rolled back.

We do have 60 cases opened this morning, I will check to see if others report the same issue and post back if this is the case.


Best regards,

Many Marice, i guess you will able to recreate this inhouse and solve the problem. So looking forward for a fixed version ..

scenario:
- create under RDM 13x a JWS or a Putty session
- update to RDM 14.0

- try to modify or delete the under RDM created session..


- please try to use the "Move" function and move a session from a folder to another folder.. it doesn't works as well :(



Please note, i don't have seen this with all types of sessions, some RDP session were able to delete.

rgs Bob

Hello Maurice,
the RDM 14.0.1.0 doesn't solve this problem.
I use the 32bit version of the RDM 14.0.1.0 and the default MS Access DB as datasource.
The RemoteDesktopManager.log shows:

The system cannot find the file specified
[24/10/2018 06:46:33]ERROR SILENT System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionInformation.DeserializeData(IEnumerable`1 connections)
[24/10/2018 06:46:36]ERROR SILENT System.Threading.ThreadAbortException: Thread was being aborted.
at Devolutions.RemoteDesktopManager.Business.HttpBrowserLinker.c36e11a71b2027cacbbca5f70b6ed33df()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
[24/10/2018 06:46:54]ERROR SILENT System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionInformation.DeserializeData(IEnumerable`1 connections)
[24/10/2018 06:47:08]ERROR SILENT System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionInformation.DeserializeData(IEnumerable`1 connections)
[24/10/2018 06:47:10]ERROR SILENT System.Runtime.InteropServices.COMException (0x80040100): Trying to revoke a drop target that has not been registered (Exception from HRESULT: 0x80040100 (DRAGDROP_E_NOTREGISTERED))
at Devolutions.RemoteDesktopManager.Controls.EnhancedWebBrowser.IWebBrowser2.ExecWB(OLECMDID cmdID, OLECMDEXECOPT cmdexecopt, Object& pvaIn, IntPtr pvaOut)
at Devolutions.RemoteDesktopManager.Controls.EnhancedWebBrowser.Zoom(Int32 factor)
[24/10/2018 06:47:36]ERROR SILENT System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionInformation.DeserializeData(IEnumerable`1 connections)


I hope that help your dev team. a fix would be much appreciated as soon as possible.
Please let me know how to debug, which debug level and logs you need.


rgs Bob

Hi RDM support team,
i guess the problem is with handling the Connections.mdb under 14.0. after the upgrade.
using RDM 13x i can move and delete any session also sub sessions..

After the upgrade, i use the RDM ZIP binary always and no exe/msi bundle, i updated the v13x with the v14 zip binary bundle, then i can add new sessions.. but i can not delete or move any old session added in a previous RDM version.
So i exported all my RDM stuff and created a new Connections.mdb (MS Access type) . Now i can delete and move all the old session again.

But that's not what i expect from an update to v14 (export everything -> create a new datasource -> import everything..
So i believe and from reading the other blog entries there is a change in v14 related to the datasource and this update doesn't works as expected, for the Connections.mdb (MS Access type) too.

another annoying thing, under RDM v14 (i'm not sure if it was in previous versions as well) with the 64bit version of RDM it's not possible to create a Connections.mdb (MS Access type).. Error message, to create MS Access DS you need the 32bit version of RDM.. why ??

I don't want to use a DB server like MSSQL, MariaDB or any other ..

Please fix it...

rgs Bob

Hello,
Unfortunately RDM 64bit has never worked with Access. This is a Microsoft limitation and not an RDM issue. The difference is that now RDM install the 64bit version by default instead of 32bit version.

Regards

Many thanks David,
but what's about the orgin reported issue after upgrade from 13.6.7.0 -> 14.0.x ??

rgs Bob

Hello Bob,
We will try to reproduce it on our side with an old version. Do you still have the original database or you are now using the new one?

Regards

Hello David,
unfortunately the data in the database are confidential , so i'm not able to share them.

Bob

No problem I understand. Are you able to open your original database with Access directly and check if the ID in the table Connections is lower case or mixed case. I suspect that the Guid value is not the same with the old entries.

Regards

hello David,
many thanks about your response. i guess we found the problem and the differences.
" ...... "
As you can see the format of the ID's are the same in upper cases, but starting from V14.x the ID's are in brackets {}
v13x 16ABBC15-4FD6-4568-AE23-54153AE52DEE
v14 {E6F0785D-02D9-4301-B7F8-6140BADB1E30}
So it seems, the RDM v14 expect an ID in the {} format ... which isn't. So it can not manage (move or delete it)
now there are two questions.
- should the new behavior like this , the ID's in {} brackets
- if yes, how to modify the old Connections.mdb, i can not manually change more the 100rows ...
PS: passing remark. i use this connection.mdb since the RDM version v1, and since almost 10years ...
rgs Bob

Thank you for the confirmation. Let me take a look at this and I will get back to you.

Regards

many thanks David

rgs Bob

The issue has been resolved and will be available in v14.0.3.0

Best regards,

Hello,

Sorry to jump in, I just wanted to add another advice related to what Stefane mentioned above.
The Duplicates will need to be deleted manually. Since sharing the same ID, It will cause both entries to be deleted. To avoid loosing data, you will need to export a copy of each of these entries affected (with their credentials) Once the duplicates have been deleted, you will need to import the entries you exported previously.

Best regards,

Side note, the v14.0.3.0 will be released soon.

Warning, if you delete one of the duplicates, both will be deleted. Since in v14.0.3.0 we treat {abcd1234-...} & abcd1234-... as the same ID.

As for new session created since 14.0.0.0 you will be ok you don't need to worry and change anything.

So your duplicates will need to be cleaned up properly to avoid data loss.

You have a few options. Make sure you backup your .mdf file.
1 - Open the database with MS Access and delete the sessions with "{ }" in the ID
2 - Export your sessions, delete the duplicates, import your sessions. Since the import will "distinct" the imported sessions, you will no longer have duplicates.

Let me know if you need assistance.

Best regards,

Oops didn't see James had already replied. :-)

Hello David and Stefane,
sorry i didn't saw your update . I only have updated the RDM and the error shown in the screenshot appear. After removing the lines {} the RDM start's without problems..

many thanks...

rgs Bob

Bob,

Thank you for the update, we will investigate the issue further.

Just to be clear, manually fixing the Access table has allowed you to keep working?

Best regards,

Hello Stefane,

Just to be clear, manually fixing the Access table has allowed you to keep working?

Yes, i can work , but will still made some tests in the next days,, so far it look fine for me.

rgs Bob