Open Bug 1226167 Opened 9 years ago Updated 9 years ago

"error occurred in sending the command to the application" on link from outlook because of ddeexec

Categories

(SeaMonkey :: OS Integration, defect)

SeaMonkey 2.39 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: alexa, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
Build ID: 20151103191810

Steps to reproduce:

Click on an URL in a MS Outloook mail (e.g.  https://bugzilla.mozilla.org/) when SeaMonkey is closed


Actual results:

A Microsoft Outlook error message is shown with the URL and "An error occurred in sending the command to the application."
SeaMonkey starts and shows the page without any problems.


Expected results:

No error message.
It helps to edit the registry. Delete any default value like:
"%1",,0,0,,,,
in:
HKEY_CURRENT_USER\Software\Classes\http\shell\open\ddeexec
HKEY_CURRENT_USER\Software\Classes\https\shell\open\ddeexec
HKEY_CURRENT_USER\Software\Classes\SeaMonkeyURL\shell\open\ddeexec

Unluckily these values are set again automatically after SM updates or when SM is set as default browser.

For this workaround see https://support.mozilla.org/en-US/questions/791994#answer-153450
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
As it seems, it is sufficient to clear:
HKEY_CURRENT_USER\Software\Classes\SeaMonkeyURL\shell\open\ddeexec
(In reply to alexa from comment #1)
> It helps to edit the registry. Delete any default value like:
> "%1",,0,0,,,,
> in:
> HKEY_CURRENT_USER\Software\Classes\http\shell\open\ddeexec
> HKEY_CURRENT_USER\Software\Classes\https\shell\open\ddeexec
> HKEY_CURRENT_USER\Software\Classes\SeaMonkeyURL\shell\open\ddeexec
> 
> Unluckily these values are set again automatically after SM updates or when
> SM is set as default browser.

So we:
1. Should *not* set this key when setting SeaMonkey as the default browser.
2. Should *not* set this key when installing or updating SeaMonkey
You need to log in before you can comment on or make changes to this bug.