Hi,
I've installed RDM 5.5.04 on my XP sp2 desktop running .Net 2 and 3. The install appeared to be successful and the RDM appears to start without issues but, when I try to open the option window or add a new connection I get the following error details.
ERROR[7/14/2009 9:34 AM] System.TypeInitializationException: The type initializer for 'Devolutions.RemoteDesktopManager.Managers.ConnectionTypeManager' threw an exception. ---> System.Security.SecurityException: Requested registry access is not allowed.
at System.ThrowHelper.ThrowSecurityException(ExceptionResource resource)
at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
at Microsoft.Win32.RegistryKey.OpenSubKey(String name)
at Devolutions.RemoteDesktopManager.Business.BusinessHelper.GetRegistryInstallPath(String aAppName, Boolean aCheckDisplayName, Boolean aCheckPublisher)
at Devolutions.RemoteDesktopManager.Managers.RemoteDesktopConnectionTypeDescriptor..ctor()
at Devolutions.RemoteDesktopManager.Managers.ConnectionTypeManager..cctor()
The Zone of the assembly that failed was:
MyComputer
--- End of inner exception stack trace ---
at Devolutions.RemoteDesktopManager.Managers.ConnectionTypeManager.get_Items()
at Devolutions.RemoteDesktopManager.Managers.InstallationPathManager.Find(String aName)
at Devolutions.RemoteDesktopManager.Managers.InstallationPathManager.GetPath(String aName, Boolean aFullPath)
at Devolutions.RemoteDesktopManager.Business.Connectors.RemoteDesktopConnector.get_RemoteDesktopFileName()
at Devolutions.RemoteDesktopManager.Forms.FrmMain.mnuOpenRemoteDesktop_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Also, I am a local admin on my box.
Hi,
It's weird, the log show that you are not allowed to access the registry. I will provide you a quick fix soon (in the next 12 hours).
Sorry
David Hervieux
Devolutions inc.
David Hervieux
What OS do you use ? Can you try to start the application as Administrator ?
Thank you
David Hervieux
Devolutions inc.
David Hervieux
I use XP SP2. I have tried running it with both a local admin account and a domain admin account with no luck. I find it strange as well. I have ran regmon and didn't see any failure events when the application is trying to access the registry so that may be a red herring.
Sorry for the stupid question (OS), you already wrote it on your initial post. I will continue my investigation.
David Hervieux
Devolutions inc.
David Hervieux
David,
I wanted to add an additional piece of information. My XP install is from an upgraded 2000 install so the system directory is winnt instead of windows, not that it should matter but wanted to make sure you had all the details.
I'm not sure that this is related to the problem, but thank you for the information. Have you tried the beta version
http://forum.devolutions.net/topic133-version-5505-beta.aspx
You should not get the error anymore, but RDM will not be able to search for the default path in the registry. At least, you will be able to configure your installation path manually.
Let me know if it's ok.
David Hervieux
Devolutions inc.
David Hervieux
Thanks David! Version 5.5.05 resolved this issue.
edited by trogger on 7/16/2009