Uisng Mozilla MAPI build dated 10-03-2001 on Windows XP I tested this on 2 separate XP systems: Enabling Mozilla as the default MAPI app for mail breaks my Outlook app. I can not launch it. 1. Install WinXP 2. Install Office97 3. Run Outlook adding a mail account, use it to prove is works and set it as the default mail app and verify it works with Word, Excel, Power Point & 4. Run Outlook Express adding a mail account, use it to prove is works and set it as the default mail app and verify it works with Word, Excel, Power Point & Wordpad. 5. Install the mozilla build that has MAPI support (dated 10-03-01) 6. Select it as the default mail app via the check box that comes up when launching mail. 7. Exit Mozilla and verify it launches as the designated MAPI mail app for Word, Excel, Word Pad and Powerpoint. 8. Launch Outlook from Program menu Result: I get an error "The ordinal 36 could not be located in the dynamic link library. MAPI32.dll" and Outlook doesn't launch. I can't use Outlook at this point.

Before I let Mozilla be the default app, I saved my mapi32.dll. After Outlook broke, I compared the mapi32.dll in the system32 folder with the saved one. They don't compare, so I renamed the mapi32.dll that doesn't work with Outlook and copied the original mapi32.dll back into the system32 directory. Now Outlook works again.

sounds like a candidate for the branch.

we should discuss this one at today's PDT.

Note: If you run this same scenario using 4.78 instead of our mozilla build, I get the same error when trying to use Outlook ("The ordinal 36..."). However, I can get Outlook back to a working state by launching Outlook Express, which isn't broken, and selecting it as the default browser. This apparently replaces the working mapi32.dll in the system32 directory and allows me to use Outlook. This 4.78 behavior is very bad too, but can be corrected by switching default mail apps. This is not the case with the mozilla build. So far I found, I must replace the mapi32.dll that I had saved (which users won't think to do).

Known problem at design stage. Talked to Mitch Green about this.

Removed nsbranch.

tiantian if you don't think this is a branch candidate then you should change the keyword to nsBranch-. Removing the keyword makes it hard for us to track when a bug has been evaluated for the branch or not =).

I have some Word documents on my desktop. When I try to send them from the desktop, I run into this error since I'm trying to send from Outlook. It really isn't right to be making other products so that they don't even launch. Bad user experience.

Using today's branch build on windows XP, I don't have the problem launching Outlook when Netscape 6 is the default. This appears to be fixed. Did anyone fix this?

Mark as depedent to meta bug 103807

Sol tells me that this bug is only a problem with older versions of Outlook. Anyone associated with this bug know which versions of Outlook have this problem? Thanks.

Ok, more details on how today's build 2001-10-09 0.9.4 branch works. Now, I am back to the point where Outlook won't launch if Netcape6 is selected as the default mail app via our check box in the app. I really don't know how to explain why with Friday's and Tuesday's N6 builds cause outbook's failure to launch, but Monday's build doesn't. In any case, we're back to the original scenario. To add more to the testing of this when fixed, test this scenario: After step 8 in the original scenario, 9. Launch Netscape6, and uncheck the MAPI box in Preferences for Mail and Exit 10. If Outlook was the original default browser via Internet Explorer, it will become the default again. 11. Launch Word and do a Send To..., Outlook compose window launches, select it, add a recipient and Send. Result: Outlook hangs trying to send. Close the Outlook compose window and try to exit Word. It won't exit until the Send finishes. I had to end both of these in the Task List. Expected: Outlook to work again.

Robin, I'm using Outlook97 on a Windows XP systetm.

Ninoschka saw this with Outlook98 on Windows ME, not sure what verion Lisa has.

I tried this sceanio on Lisa's system, the only difference is she doesn't have Outlook Express, so step 4 can't be done. That means I'm changing the default from Outook to Netscape 6. I get the same results as in the original scenario, however I can get Outlook back to a working state by unchecking the MAPI box in our app. Her system is NT4 with Outlook97.

We need to make sure the workaround, of de-selecting use Netcsape Mail as the Mail client, allows Outlook to work again. If not, this is a huge issue out in the wild (for consumers).

hong or trix - can you confirm with Outlook (not Outlook Express) that the user can get back to a working state in Outlook after disabling MAPI in our product? I think this is ok now, but want official confirmation.

There could be multiple scenarios for this : 1. Outlook is currently the default mail client, now Mozilla is made the default mail client. Un-setting Mozilla as dafault from the preference will make Outlook work again. This is because we back up Outlook's mapi32.dll and when the user un-sets us to be the default we replace Outlook's mapi32.dll back and Outlook start working. 2. Outlook is currently default mail client, then N4.7 is made the default mail client and then, Mozilla is made the default mail client. Now un-setting Mozilla as default from the preference will NOT make Outlook work. This is because we back up the current default mail app's mapi32.dll (in this case N4.7) and during un-set restore the state as it was before Mozilla was made default. The work around for this case to make Outlook work is delete mapi32.dll and then run Outlook. We are making sure that both these cases are listed in the release notes, i just reviewed the release notes and have sent my comments for it. Also in the release notes we should make sure to caution the user that with the above two workarounds Mozilla will no longer be the default mail client and the user should run Mozilla and make it the default from the Edit/Preferences... before sending mails from Office apps or other apps that send mails.

Release notes update has been forwarded to Robin on Friday, and she has just updated it this morning. We'll review again her updates.

PDT-, because we are in parity with 4x

reassigning to rdayal

nominating ...

Installing the 1.0 Win32 release (done 6/18/2002) also breaks Novell's Groupwise 5.5.3.1 (running on Win NT 4 w/SP4) in a manner identical to the desciption except the error message is "The ordinal 19 could not be located in the dynamic link library MAPI32.dll". The overwritten MAPI32.DLL file is Microsoft's and is quite large. I moved Mozilla's MAPI32.DLL from C:\Winnt\System32 to the Mozilla executable directory, then restored the overwritten file from tape. Groupwise now works. I don't know if Mozilla Mail works 'cause I haven't taken the time to even determine if it can work here at work. But, Mozilla browser works, and that's what I want to test.

dupe of bug 109362 ?

Please look at: http://bugzilla.mozilla.org/show_bug.cgi?id=109362#c6 for explanation why this happens. And look at: http://bugzilla.mozilla.org/show_bug.cgi?id=109362#c9 how to make this work. Marking as duplicate of bug #109362 *** This bug has been marked as a duplicate of 109362 ***

Verified dup