update from 5.9 to 6.1.3.0 errors
Hello,
I have a Windows 7 Pro with SP1 32bit PC. I have updated RDM from 5.9 to 6.1.3.0 and now I get these errors on RDM startup:
Standard Edition 6.1.3.0
InvalidOperationException - There was an error generating the XML document.
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
at System.Xml.Serialization.XmlSerializer.Serialize(Stream stream, Object o, XmlSerializerNamespaces namespaces)
at Devolutions.RemoteDesktopManager.Managers.SerializationManager.SaveObjectToString(Object value)
at Devolutions.RemoteDesktopManager.Managers.SerializationManager.SaveObjectToFile(String fileName, Object value)
at Devolutions.RemoteDesktopManager.Managers.OptionManager.DoSaveOptionsObject(String fileName, String backupFileName, Object data)
at Devolutions.RemoteDesktopManager.Managers.OptionManager.SaveOptions()
at Devolutions.RemoteDesktopManager.Managers.OptionManager.DoLoadOption()
at Devolutions.RemoteDesktopManager.Managers.OptionManager.LoadOptions()
at Devolutions.RemoteDesktopManager.Managers.ApplicationManager.InitializePhaseOne(String[] args, ApplicationDescriptor applicationDescriptor)
at Devolutions.RemoteDesktopManager.Program.Main(String[] args)
------------------------------------------
TargetInvocationException - Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, BindingFlags invokeAttr, Binder binder, Object[] index, CultureInfo culture)
at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, Object[] index)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterOption.Write114_Option(String n, String ns, Object o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterOption.Write115_Option(Object o)
------------------------------------------
TypeInitializationException - The type initializer for 'Devolutions.RemoteDesktopManager.Managers.SecurityManager' threw an exception.
at Devolutions.RemoteDesktopManager.Managers.SecurityManager.get_VersionStamp()
at Devolutions.RemoteDesktopManager.Business.Options.Option.get_EncryptedDataSources()
------------------------------------------
InvalidOperationException - This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
at Devolutions.RemoteDesktopManager.Managers.SecurityManager..cctor()
For the last error I already disabled "Use FIPS compliant algorithms for encryption, hashing, and signing" but the error came back on every startup of RDM.
(post : http://forum.devolutions.net/topic1103-remote-desktop-manager-starts-with-exception.aspx )
Thanks for help.
Kind regards
Ernie
All Comments (12)
Can you just try to upgrade to the version 6.0 before upgrading to 6.1?
http://remotedesktopmanager.com/remotedesktopmanager/Home/PreviousVersion
edited by dhervieux on 7/21/2011
David Hervieux
I reinstalled the 5.9 and then upgrade to 6.0 with these errors:
Standard Edition 6.0.0.0
TypeInitializationException - The type initializer for 'Devolutions.RemoteDesktopManager.Managers.SecurityManager' threw an exception.
at Devolutions.RemoteDesktopManager.Managers.SecurityManager.set_UseNewLockingSystem(Boolean value)
at Devolutions.RemoteDesktopManager.Program.Main(String[] args)
------------------------------------------
InvalidOperationException - This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
at Devolutions.RemoteDesktopManager.Managers.SecurityManager..cctor()
I don't understand, it's the FIPS error again, but you said the you verified this:
http://forum.devolutions.net/topic1103-remote-desktop-manager-starts-with-exception.aspx
David Hervieux
I don't understand too. But the fact is that the policy is disabled. I joined a print screen for proof. May a other policy cause this error? I have other active policies in Security Options.
edited by ernie49 on 7/22/2011
edited by ernie49 on 7/22/2011
fips.jpg
It's weird, maybe it's required a system reboot?
You can try to install the application somewhere else not in Program files? For example in c:\RDM?
David Hervieux
I installed it in c:\RDM with "Run As Administrator" and with system reboot. Always the same errors with 6.0 and 6.1.3.0.
Hi,
i really don't know what might be the problem, can you verify the registry key:
HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy
I will try to verify if I can do a version which is not using a FIPS non compliant alogorithm
David Hervieux
Hi,
I have done some tests, can you try to copy this file in the installation folder
edited by dhervieux on 7/22/2011
David Hervieux
I will try it on Monday. Big big thanks for your help.
Kind regards.
Hello,
Ichanged the reg key HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy to 0. I installed first the release 6.0 and then I update it to 6.1.3. Now it works.
Big big thanks for your help.
But I must admit that a version wich is not using FIPS would be great. I can't find the file for tests. Can you post it again please? I will try it.
Kind regards.
Hi,
Here is the file, I don't understand why it has disapeared. Just unzip it.
edited by dhervieux on 7/25/2011
David Hervieux
RemoteDesktopManager.exe.config.zip
I changed the reg key HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy back to 1 and try to start RDM for test. It makes the errors. Then I copied the config file in the installation folder and start RDM. And ..... it works. :drop:
I'm very happy that RDM works and that Fips is now disabled only for RDM.
Great great work. Lot of thanks. :)