Issues between configs of RDM x86 and x64
Hi!
I've always worked on my laptop (Windows 8.1 Pro x64) with RDM 32 bit version.
Recently I bought a Workstation (Windows 8.1 Pro x64) for my office and after installing RDM I thought well to use the 64 bit version.
So from my laptop I've exported all settings into a cfg file and after importing it I restarted RDM to find that nothing was imported...
I tried to import it again but this time RDM told me that the file was corrupt... Made another one from my laptop, imported correctly, restarted, nothing, trying to import it again pops the warning that the file is corrupt...
Strange, I thought. So I started the 64 bit version on my laptop thinking to export the settings from there, but the x64 exe told me that I was under the trial period and I had 30 days left...
OMG x86 and x64 have different configs. So I registered the software and started to manually change all the settings, then I exported the cfg from the 64 bit version.
x86 cfg 54KB, x64 cfg 5KB, mmmm...
Placed the cfg into the workstation, imported, confirmed, restarted RDM, nothing changed, still in trial...
Imported again the same cfg, no warning message but again nothing imported...
As a last resort, I gone under \AppData\Local\Devolutions\RemoteDesktopManager, copied RemoteDesktopManager.cfg, .exb and .lyt from laptop to workstation, started RDM 64bit and now everything is setup and running flawlessly on my new Workstation.
I haven't told but importing the cfg made from RDM 32 bit to the new installation of RDM 32 bit worked without issues...
I've done this all with RDM 10.1.12.
Thanks, best regards.
All Comments (3)
This morning I started RDM 64 bit on my laptop and was back in trial with default config...
Copied those files from Workstation and opened normally...
However this time an error has been logged
[08/03/15 09.30.32 - 10.1.13.0 - 64-bit] Error Silent: Devolutions.RemoteDesktopManager.Business.XmlDeserializationException: Errore nel documento XML (2, 6). ---> System.InvalidOperationException: Errore nel documento XML (2, 6). ---> System.Xml.XmlException: Il carattere '`', valore esadecimale 0x60, non può essere utilizzato in un nome. Riga 2, posizione 6.
in System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
in System.Xml.XmlTextReaderImpl.ParseElement()
in System.Xml.XmlTextReaderImpl.ParseDocumentContent()
in System.Xml.XmlReader.MoveToContent()
in Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderList1.Read5_ArrayOfPasswordConfiguration()
--- Fine della traccia dello stack dell'eccezione interna ---
in System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
in System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
in Devolutions.RemoteDesktopManager.Managers.SerializationManager.LoadObjectFromString(String str, Type type, Boolean createAnInstanceIfNotExists, String nameSpace)
--- Fine della traccia dello stack dell'eccezione interna ---
in Devolutions.RemoteDesktopManager.Managers.SerializationManager.LoadObjectFromString(String str, Type type, Boolean createAnInstanceIfNotExists, String nameSpace)
in Devolutions.RemoteDesktopManager.Managers.XmlLoaderManager.c89fbb26b2875e974c83837ca8209b112(Object c5b7a41272702648f46cf77ee6b3a92cb, XElement cdc71bbd303008ff6de2ea3bc67006d8c, PropertyInfo c718f9d338cda3dfcd418b16c1bf307fa)
in Devolutions.RemoteDesktopManager.Managers.XmlLoaderManager.LoadXml(Object source, String fileName)
in Devolutions.RemoteDesktopManager.Managers.OptionManager.c428c199685fb3d03304efc3b5a48ada5(String cac93450b2ad63adc067b608718610365)
in Devolutions.RemoteDesktopManager.Managers.OptionManager.c817cf4847ff0cff890d82c9d77ada47d()
[08/03/15 09.30.32 - 10.1.13.0 - 64-bit] Error Silent: Devolutions.RemoteDesktopManager.Business.XmlDeserializationException: Errore nel documento XML (2, 6). ---> System.InvalidOperationException: Errore nel documento XML (2, 6). ---> System.Xml.XmlException: Il carattere '`', valore esadecimale 0x60, non può essere utilizzato in un nome. Riga 2, posizione 6.
in System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
in System.Xml.XmlTextReaderImpl.ParseElement()
in System.Xml.XmlTextReaderImpl.ParseDocumentContent()
in System.Xml.XmlReader.MoveToContent()
in Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderList1.Read5_ArrayOfPasswordConfiguration()
--- Fine della traccia dello stack dell'eccezione interna ---
in System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
in System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
in Devolutions.RemoteDesktopManager.Managers.SerializationManager.LoadObjectFromString(String str, Type type, Boolean createAnInstanceIfNotExists, String nameSpace)
--- Fine della traccia dello stack dell'eccezione interna ---
in Devolutions.RemoteDesktopManager.Managers.SerializationManager.LoadObjectFromString(String str, Type type, Boolean createAnInstanceIfNotExists, String nameSpace)
in Devolutions.RemoteDesktopManager.Managers.XmlLoaderManager.c89fbb26b2875e974c83837ca8209b112(Object c5b7a41272702648f46cf77ee6b3a92cb, XElement cdc71bbd303008ff6de2ea3bc67006d8c, PropertyInfo c718f9d338cda3dfcd418b16c1bf307fa)
in Devolutions.RemoteDesktopManager.Managers.XmlLoaderManager.LoadXml(Object source, String fileName)
in Devolutions.RemoteDesktopManager.Managers.OptionManager.c428c199685fb3d03304efc3b5a48ada5(String cac93450b2ad63adc067b608718610365)
in Devolutions.RemoteDesktopManager.Managers.OptionManager.cc85977e0212438c18ef7354bb67d8a4b()
Ok, I've found out what was the cause of the "Deserialization" error happened this morning...
It's caused by the "Password Generator" templates.
Yesterday I've restored some of my templates and this morning the error.
Now I've done the same and again deserialization.
I saw that custom templates are stored directly into the cfg.
This happens with any template mode (readable, pattern...)
Maybe this is also the problem that made the conflict between 32 and 64 bit versions, since with 32bit version I had many custom password templates.
Best regards.
edited by Logharn on 3/8/2015
Hi,
Could you provide me your configuration with the error (you can send it by private message).
David Hervieux