Protocol Handler RDM:// Bug: No apps are installed
Protocol Handler RDM:// Bug: No apps are installed to open this type of link (rdm)
rdm://open?... links do not work from IE, Firefox, and possibly other browsers unless a registry entry is made:
The following is observed:
In IE (11, in this case) , the error message: No apps are installed to open this type of link (rdm)
In Firefox, no error message, and the program is NOT launched.
Fix this by adding the proper registry string to HKLM\SOFTWARE\Classes\rdm (Empty string, named "URL Protocol")
;-- Start Copy --
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\rdm]
;@="URL:rdm Protocol"
;Internet explorer will give you this message: "No apps are installed to open this type of link (rdm)"
;Firefox does not produce an error message, nothing happens when clicking the link.
;You need this next line to fix IE and Firefox, but it's not there by default! Oops:
"URL Protocol"=""
;-- End Copy --
All Comments (7)
What version do you use? The installer of the latest version should create the registry key for you.
David Hervieux
I was using 9.2.3.0, I see that there is a new version released today. I'll try it.
-edit-
Interesting, nothing is mentioned regarding the url handler in the version notes for versions 9.2.4.0 or 9.2.5.0.
I deleted the registry value and then ran the latest installer.
9.2.5.0 does fix the issue for me.
- Thanks
edited by confused_pc on 4/14/2014
I had 9.2.9.0 installed on three of my machines. Two were upgraded to the latest beta. RDM file associations don't work on any of them. Checking the registry, none of them had the rdm protocol. I uninstalled and installed the latest beta. Now I see the rdm protocol and it looks correct, however putting an rdm link into IE, Firefox, Explorer, etc. just gives me "There is no program associated to perform the requested action." Thoughts?
Have you tried a reboot?
David Hervieux
Yes, I rebooted after the uninstall, then again after the install. Here's the reg key, looks fine to me, any other thoughts? At this point I'm thinking it must be system related since the reg key looks ok.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\rdm]
@="URL Protocol\"=\""
[HKEY_CLASSES_ROOT\rdm\DefaultIcon]
@="C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe"
[HKEY_CLASSES_ROOT\rdm\shell]
[HKEY_CLASSES_ROOT\rdm\shell\open]
[HKEY_CLASSES_ROOT\rdm\shell\open\command]
@="C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe \"%1\""
Ill check in a couple hours when i am at a pc i can test with.. But i remember having issues with the handler subsequent to finding a fixed version.. I think it broke later on..
In your reg file, this line does not look right:
@="URL Protocol\"=\""
Change it to:
@="URL:rdm Protocol"
Then add:
"URL Protocol"=""
Then reimport. You should not need to restart the computer , you *may* need to restart ie/firefox.
Or if you copy and paste my reg file from above. And uncomment (remove semicolon) the like with '@='. It will get you the same thing.
Two values are required in that registry key! Make sure they are both there and look like the original example.
Ah - you're totally right. I didn't look at it close enough... For some reason I had the default string with URL Protocol as the data, when URL Protocol should have been a string name and the default string should have had the other data in it.
Also I noticed some of the file paths to RDM had double \ in the path, but it isn't consistent across versions or platforms that I can see.
It's just weird that even on an uninstall, reboot, install newest beta, reboot, still had incorrect registry keys, you guys may want to check that out and also possibly blow away the previous rdm protocol association in the registry and put a correct one in with the newest release to correct prior version issues.