Tree pane entries not responding

Hello,

Which version of RDM are you using?
When the issue occur have you any logs under Help -- Application Log?

Best regards,

I'm using 14.1.3.0 x64. I'm always using the latest version.

If it occurs again next time, I'll chcek the application log and provide a copy here.

OK, it just happened. Nothing in the application log:

Hello,

As per your signature, you are using a SQLite data source, am I correct?

Is the data source saved locally under the defaut path of RDM, which is %localappdata%\Devolutions\RemoteDesktopManager, or in another folder?

Have you tried to create a new SQLite or XML data source to see if you have the same issue with this new database?

Best regards,

Yes, I'm using SQLite data source.

It is saved in the default path correct.

What does "vacuum" do here? Wonder if I should try repairing it?






I have a lot of entries in my data source, so no I haven't tried creating a new one to test, as this would require me to re-create the entries (unless there's a way to copy the entries from one data source to another?).

I never had this issue before until it started in v14 I believe.

Hello,

It's easy to export your data from one datasource to another by following the steps in this article
https://help.remotedesktopmanager.com/tipsandtricks_data_migration.htm

Don't forget to check the option Include Credentials to export your credentials inside the new data source.

Best regards,

Don't think it's an issue with the data source or database. Issue happened again and if I go into the File menu, I can't even see anything under Export:

Hello,

I remember seeing this a long time ago. If the connection with the database is lost, the export would not be possible, so this may explain why that area is empty.

Have you created a new database or not?
Could you try to move the database into another folder like C:\data as example and see if the issue is still present?

Best regards,

I have created a new database, imported all the exported entries and I'm still getting the same issue. This has happened twice on the new database now.

All I have exported and imported are the entries with the creds.


This was never an issue on v13 or older.


I think the problem is related to the Citrix Netscaler entries. If I use force 32-bit, then it seems to reproduce this issue quite consistently (not all the time):





If I don't use force 32-bit, then the Citrix Netscaler page won't load. This is a separate issue that I'd like for you to have a look at as well.


And I think in RDM v14, you guys changed the way the Citrix Netscaler entry works, so I think this is a big culprit.

Hello,

With your last post, I think that you have find the culprit of the issue.

Indeed, we have made a few changes for Citrix inside RDM 14. I have opened a ticket to our engineering department regarding this.

Thanks a lot for your feedback.

Best regards,

Hello,

I was trying to reproduce your issue, but I don't see the Force 32 bit option in my Citrix NetScaler session inside RDM 14.1.3.0.

As I can see, you are running the same version as me, so I don't understand why I am not seeing this option.
If you create a new Citrix Netscaler entry, is the Force 32bit option present in the Advanced tab?

Best regards,

Yes, it's in my screenshot in the last post. Have you updated the Citrix Netscaler addon?

Also, your colleague was the one whom recommended me using force 32 bit here:
https://forum.devolutions.net/messages.aspx?TopicID=30931#post123550

Hello,

After reinstallation of the add-on, I see the Force 32bit option.
Sorry about that.

I've been doing some tests for the last 15 minutes and I was not able to reproduce your issue.
Do you have speciic steps that I can follow to try to reproduce the issue? This would be very helpful.

Thanks again for your help regarding this thread.

Best regards,

Hi Jeff,

No specific steps, it just happens randomly. I think if you create a few Citrix Netscaler entries and try connecting to them, it might re-produce the issue.

Hi Jeff,

You can close this one. I think it was an issue with .net framework. I recently reinstalled Windows but still used the same configs / database etc (which I backed up). No issues found.