Commercial branch build: 2001-10-11-10 win98 I was not able to send the message from MSExcel-97. Got this error in the excel application. " General mail failure, Quit microsoft excel, restart the mail system and try again" So according to the dlg I did so and the second attempted failed too. I tried to send this document after saving and before saving the new document. Both resulted in the same error. It failed to open the compose window to be able to send the mail from Excel. But Excel did not crash and the netscape also did not crash.

Esther helped me with this problem. I had not turned on this feature using another mail application. After enabling MAPI from outlook express I was able to send from excel 97. marking worksforme.

verified worksforme.

I am reopening this bug after speaking with Esther. Because according to bug 102389 I still should have been able to send with out enabling MAPI from another application. I am not sure if this is the same problem as the bug 102389. But I can say that except word97 none of the other applications worked before using the work around of enabling MAPI using another app. Here is more information on how the system was before the work around was used. System info: OS: Windows 98 Word,Excel,wordpad,powerpoint-97. Internet explorer and outlook express -version 5 -I have different profiles in 4.77 and the profile that I was using in 6.x was a migrated profile -The MAPI pref in 6.x was checked because this is enabled in 4.77 on this profile -I am using SSL for both sending and receiving messages for this account. -The first time I tried with MSWord-97 without the application was opened I was able to send from MSWord. I then exit word app. -Launched MSExcel-97 and tried to send but got an error message " General mail failure, quit MSExcel, restart the mail system and try again" -So I launched Excel and then tried to send keeping 6.x open and still failed -This was the same on Powerpoint too. I did not get any error but failed to bring the compose window. So the work around suggested by Esther and here is what we did: -Disabled MAPI from 4.77 in preference. -Then we opened outlook express and made this as the default application to be used for mail. Then exit outlook express -Launced each application (word, excel, PowerPoint, wordpad) and sent mail using Outlook Express. Exit all the applications. -Launch Netscape 6.x and then enable the preference to use MAPI -Exit application -Launch each of the applications mentioned above. -Was able to send mail without 6.x open from all the apps. -Was able to send mail with 6.x open from all the apps. But on my machine I had to use this workaround for MAPI to be able to work. So I will leave this open for now. Later if this happens to be the same problem as bug 102389 it can be marked as dup. But I will keep it open till someone takes a look at it.

I saw the same behaviour, got the same error message with EXCEL on my winNT4.0, with yesterday's branch build. I deselected the pref to select NS as default email client, exit, close the app. Then launch again, select the pref. Then it works. Reassign to Krishna.

Reassign to Sean.

Krishna will work with Sean on this.

The problem is due to COM interfaces are modified from 10/10 build to 10/11 build. When the interfaces are changed we will have to re-register the Proxy dll. (regsvr32 MapiProxy.dll) which is there in the /bin directory. The failure is happened b'cos after installing 10/11 build you did not reset-set the preference again, which will not only enable mozill MAPI to be the default, but registers the Proxy dll. The solution is to register the Proxy Dll again. So, the following code needs to be added to the installation script. regsvr32 /s MapiProxy.dll (The MapiProxy.dll is in /bin directory). Note that regsvr32 may fail if it doesn't find the dll. In that case the code should ignore the error and proceed with the installation.

nsbranch+ per Simple MAPI team. tentative PDT+, pending positive reviews.

This kind of a thing will not happen in a normal case. It may however happen in case of upgrade. Normal install need not change. We will need to do this only in the case if the Proxy changes. The Pref code looks at the registry key setting to decide if the pref is enabled or not. In case of upgrade it may however happen that this registry key is not touched or changed to reflect the new mapi32.dll. However the new mapiProxy dll will not be registered and send may fail. So we will have to do this registration thing in case of an upgrade.

We should also try and replicate the test case that Sheela mentioned above. If N4.7 is set as default the pref for Mozilla to be default mail client should NOT be enabled ! Even if u use migrated profile it does not matter since the profile migration does not set the registry keys for enabling Mozilla to be default mail client.

Sean: Thanks for taking this up. Please try to get your r, sr, and check in tonight. Many thanks. This is important for our testers who do not do an uninstall, and get the fresh daily build everyday.

Installing on top *is* a normal case, unless you expect our customers will keep 6.2 forever. It's just not a case that's normally going to come up for months, but when it does it'll happen in spades. Why isn't mapiproxy.dll registered once and for all in the installer, instead of doing it conditionally? Why do we ever unregister it? What's the harm in leaving us simply registered, which should have no effect unless something else actually points at our CLSID?

Comment on attachment 53390 [details] [diff] [review] patch #2 (ns tree) sr=dveditz for patch #2

Comment on attachment 53391 [details] [diff] [review] patch #2 (moz tree) sr=dveditz for patch #2

patch #2 checked into the branch only.

patched also checked in to trunk. closing bug.

verified on 2001-10-15-05-0.9.4