error saying "msnim is not a registered protocol" when clicking a link. works in IE, but not FF




Shell Integration
13 years ago
10 years ago


(Reporter: RoB, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)


(Whiteboard: Workaround comment #13, URL)


(2 attachments)



13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

It is a relatively new feature in the latest MSN Messenger program which works
in a similar way to the AOL messenger's [see example]. it seems to work in IE,
but not with FireFox. i get an alert saying "msnim is not a registered protocol".

Reproducible: Always

Steps to Reproduce:
1.create a hyperlink it to "msnim:chat?" or similar the link
Actual Results:  
get an alert saying "msnim is not a registered protocol".

Expected Results:  
in IE:
-you get an alert saying: "Are you sure you want to start a conversation with
<>? Do not share personal information with unknown
or unfamiliar contacts. [OK] [Cancel]"
-clicking "OK" opens MSN messenger and a conversation window with whoever's
email address is specified in the link.
If you run start/run in windows and enter
msnim:chat?, what Do you get ?

Comment 2

13 years ago
it works fine
It should work fine if the protocol handler is registered and calling external
protocol handlers works fine in Mozilla/Seamonkey and also Firefox. (on my
system and i didn't see any bug reports about problems in this area).

It seems that MS Messenger doesn't correctly register itself as external
protocol handler.

What is the content of the registry key under HCR\MSNIM ?
(right click in the registry editor on the msnim key and select export to get
the contents as file)

Comment 4

13 years ago
try it for yourself:

Comment 5

13 years ago
Created attachment 193721 [details]
the registry key (i think)
*** Bug 329167 has been marked as a duplicate of this bug. ***

Comment 7

12 years ago
I can confirm that this is a bug (but I can't change the status since I don't have the canconfirm permission). I just ran into this problem on this site:

On the bottom of that page is a link that says:

TechEd06 Bot for Messenger => msnim:chat?

When I click this link I get the same alert message as is reported by the bug creator. The hyperlink works in Internet Explorer and using start/run.

I use:
Firefox [Swedish]
MSN Messenger 7.5 (Build 7.5.0324)

Comment 8

12 years ago
I understand that Microsoft will be releasing information about the range of msnim: functions (msnim:chat?   msnim:add?  msnim:voice?  and  msnim:video?) in December 2006.  It would be a good idea to have this fixed before then!!

BTW, the equivalent aim:goim? function for AOL Messenger works as it should, successfully bringing up AOL after the "application being opened" warning message. 

However the equivalent ymsgr:sendim? function for Yahoo Messenger gives the same error as msnim:chat?, as described in the previous posts re this error.
Created attachment 244419 [details]

See also this message for some possible useful info:
 MSNIM handlers are useful, but It seems that these protocols are not
working in Firefox
It seems that FireFox will just check HKCU and HKCR for the handlers,
whereby MSNIM is registered as a Protocol Handler in the registry :

I really appreciate if FireFox scans through
HKLM\Software\Classes\Protocols\Handler\ too.

and here is some reference to the problem

I guess somewhere here things need to be tackled to get this working:
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 07/14
Version: unspecified → 1.0 Branch

Comment 11

11 years ago
(In reply to comment #10)
> Reporter, do you still see this problem with the latest Firefox 2? If not, can
> you please close this bug as WORKSFORME. Thanks!

the problem still exists in
I'm also seeing this on trunk.
Ever confirmed: true
Whiteboard: CLOSEME 07/14
Version: 1.0 Branch → Trunk
This appears to be special cased by the OS for Start -> Run as well as handled directly by IE, handed off to IE for the Start -> Run case, and IE then opens up MSN IM / Windows Live.

Whiteboard: Workaround comment #13

Comment 14

10 years ago
I see no evidence in this bug to suggest anything is special-cased - Firefox is not using the OS to launch the URL, it is instead checking itself and doesn't handle COM plugable protocols (where a CLSID is registered and supports an interface for handling URLs). It's just the case that Firefox is attempting to replicate OS functionality and this is one case it isn't handling.
Taking a quick look it appears that most other protocol registrations under HKCR\PROTOCOLS\Handler are also set under HKCR (e.g. under HKLM or HKCU \Software\Classes whereas msnim is not. We also use IApplicationAssociationRegistration to determine the handler on Vista and it would seem that it is not returning a handler for msnim on Vista.

Comment 16

10 years ago
Not sure of the truthfulness of this, but one of the feedback comments on the sumo page says:

This info doesn't apply to Windows Vista. Vista uses the "Default Programs" control panel applet to choose the default browser. The Firefox folks will need to start registering some Capabilities in HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications if they want Firefox to be listed as a default browser choice. See MSDN Library page for details.
Jason, I am using Vista and Firefox does register the capabilities etc. for Vista. IApplicationAssociationRegistration mentioned in comment #15 is what is used on Vista to determine the application to use for a protocol such as msnim. Regretfully, it doesn't return a handler on Vista for msnim with Windows Live installed though IE and Start Run do launch Windows Live when using an msnim URL. Interestingly, the Search in the Start Menu on Vista which will launch http, https, etc. does not launch Windows Live likely due to the same reason Firefox doesn't though Start -> Run does.
You need to log in before you can comment on or make changes to this bug.