All connections lost after upgrade to version 12.5.2.0
I use SFTP as my datasource. I received a prompt to update yesterday (17th May 2017) to version 12.5.2.0 which I accepted. When Remote Desktop Manager started up again I saw a message saying "Migrating data content to version 1.1" and it then opened up. But everything that I had configured is missing - all I see is the name of the config file in the top left hand corner.
I have tried opening it up again today and received a prompt to update to 12.5.3.0, which I accepted. But there are still no connections in my config file :-(
All Comments (6)
Hello,
If you navigate on your SFTP server and look at the XML file that is stored on your server, what is the size of that file?
If you right-click on your XML file and go in Properties, what do you see?
Best regards,
Jeff Dagenais
Hi Jeff,
It's not an .xml file, its a .cfg file and it is 699kb in size.
What specifically should I be checking in the file Properties?
Hello,
The RemoteDesktopManager.cfg file contain some information regarding the configuration of the application like the data sources or your license.
Your data (sessions) should be store in a .xml file on SFTP (like connections.xml as example).
Could you go in File -> Data Sources and post a print screen of your data source configuration please.
Best regards,
Jeff Dagenais
We just had the same thing with our data source in SFTP. There is no "connections.xml" file - only the .cfg file as specified in the SFTP settings. I setup a local VM with SFTP and copied the .cfg to that, which then allowed me to open the data source and export our entries.
Moved them to SQL server now. Something seems very wrong with the updates over the last few days (high memory/cpu, very slow to open data source, unable to open data source, etc).
I have followed Alex Heron's advice to recover to a SQL server and it is working OK now. I just needed to get back and running asap!!
@Alex Heron and @Tech Services
As I understand, you have been able to transfered your data on a SQL Server database and now you are able to work with this type of data source instead of a SFTP data source.
For your information, I have been able to reproduce your slowness issue to connect on a SFTP datasource.
A ticket has been opened to our engineering department regarding this.
Best regards,
Jeff Dagenais