steps to reproduce: 1. Set up mail account in Mozilla test profile. 2. Launch Mozilla and select the test profile 3. In Prefs, select "Use Mozilla Mail as the default mai l application" 4. With Mozilla running, launch MSWord and attempt to send an email 5. In Mozilla Mail dialog, enter username and password or just enter username 6. Hit Enter 7. Warning shows: WINWORD.exe was generated error and will be closed by Winows. You'll need to restart the program.

Is this crash in winword happening all the time? Which version of MS Word do you have?

It's MS Word 97 SR-2. It happened to me less than a couple days ago. Probably only once today.

This occurred to me today: win32 2001-10-01-05-094 build Word 97 SR-1 version WinNT 4.0 This was the very first time I had tried to send via MS Word since I set the Netscape client as the default. Second time is ok. The problem with this bug is that you can lose your MS Word data if you try to send page prior to saving your changes in Word. cc: jaime to discuss in PDT.

for quite sometime now i've been working on trying to isolate a testcase which would duplicate this problem but have not been able to isolate it. i've tried first time installs of both Simple Mapi enabled apps and mozilla, tried various combinations of Office 97 & 2000, and have tried multiple scenarios with switching default email clients, and still haven't been able to isolate the testcase to generate the error everytime. the steps described initially do not generate the error all the time. there were many cases where i installed the test build on a new machine(no prior smapi-enabled test builds) and sent a doc through WINWORD without any problems. i'll continue to try to look for a testcase, but until we're able to isolate the problem and provide a testcase which WINWORD fails consistently, its tough to determine the severity at this point.

Hi, Lisa: Can you help to get us a reliable testcase to repro this bug? Thx.

I will try. At yesterday's PDT, it was suggested to look through the MS site to see if they have any technotes on known problems with this type of crash and mapi.

Hi, Lisa: I'll check up the MS site.

I cannot reproduce this. Will keep trying. Suggest: in release notes, to suggest to the user to save their document prior to sending.

Adding relnote keyword.

From two other people who have seen this. It sounds like this problem happens the very first time trying to set up for mapi and sending.

sheela and suzanne - can you add your scenarios to this when you saw the crash?

I had never set up mapi before on my system. I installed NS 6 with a clean profile, and when I launched mail I selected the option to "Make NS Mail my default mail".(Which I beleive set the option to turn on mapi in prefs). I had the browser up with mail at the time, then I launched Word, Wordpad and Excel one at a time, trying to "send" to our mail from each of those apps. In all cases I crashed out of those apps with a similar application error. (I'll attach the error before the crash)

PS. After I set up Outlook express,and sent mail from it successfully,I then exited Outlook express. Next, when I exited and restarted NS 6.2, Mapi send worked for me (with our mapi prefs option set on).

Commercial Branch build: 0.9.4-2001-10-11-10 win98 Running MSWord 97 on the machine. I had never set up my machine for MAPI. I was using a profile that was migrated from 4.77 to 6.2. I installed the build and launched that profile. Netscape browser and mail both were open. I then launched MSWord. Created a new test document. I did not save the document. From the file menu I clicked on sent to recipient. Result: This program has performed illegal operation and will be shut down" OK I clicked on ok and the word app closed. I also tried this not launching the application first like I did in the previous scenario. I opened word and typed a document and tried to send. But resulted in the same crash. The work around suzanne mentioned here is the same thing I did for it to start working onwards.

I think I have a consistently reproducible case for a crash..but it is in MS Frontpage 2000 (v 4.0.2.2717) Every time I send to our mail via mapi with a html file created in Frontpage, I can successfully send the file thru our mapi, but it will (within Frontpage) report in a dialog "An unmamed file was not found". When I click OK to the dialog, after a few seconds more, Frontpage will crash with the error I attached earlier. Other apps such as Word and Powerpoint don't give this crash or dialog. (I am on a Win 2k box) This happens every time for me.

I have the solution for the Front Page crash. This is happening for the similiar reason why WordPad is displaying the error message when sending unsaved document (bug # 104091). MS Office apps and WordPad creates a temp file for unsaved documents and send the path name for this temp file as well as the real file name for it to MAPISend. However, FrontPage decides to do this even for saved docuemnts !! Now all these apps try to delete the temp file they created and behave differently when they do so. MS Office apps donot display any error messages when they donot find this temp file created for the sole purpose of the messaging app, WordPad displays an error message whereas FrontPage decides that it is very severe and crashes. As I mentioned in bug # 104091 there is a simple fix, rather than us moving the temp file to our moz_mapi temp dir (which we did for performance reason in case of large files) and rename with real filename we make a copy of this temp file with real filename in our moz_mapi temp dir. Please find the fix in the patch below.

Comment on attachment 53376 [details] [diff] [review] patch for the fix for FrontPage crash and also Wordpad error msg sr=mscott I'd rather have slower performance than have us crash.

pls get the reviews, and let's see how it shakes out over the weekend ... can this be checked in on sunday, if the PDT agrees it should go into 094?

can i get a PDT+ on the patch, this solves a crash / dataloss ? If soon i can check in today or weekend so that it is in Monday's build. thanks, - rajiv.

Rajiv - do you hypothesize that this fix may also fix the crashes seen in Word as originally reported by this bug report?

i'm gonna be careful with this one, and wait until the reviews come back, but if they arev positive, we will give the PDT+ before sunday night.

No no this is a fix for the FrontPage crash and Winword error message ONLY as i mentioned on the patch too. The Word crash problem looks different since it only happens the first time, i am still trying to replicate it.

I saw error messages similar to what scalkins@netscape.com has posted. On EXCEL, Powerpoint, and MS Word. On Win NT. With the 10/12 branch build. I'll try to repro on Monday.

Comment on attachment 53376 [details] [diff] [review] patch for the fix for FrontPage crash and also Wordpad error msg R=ducarroz

JF: Thx for your stamp.

Pls move the patch into the Wordpad bug 104091 and resolve it there. This bug is for the winword issue.

The patch has been copied to bug 104091, together with QA's description about FrontPage crash, and Rajiv's explanation.

Walkaround for this bug has been documented in release note, which suggests that user save the doc before sending.

PDT-, because this has a workaround, and it can not be consistantly reproduced.

Frontpage 2k no longer crashes with todays build when sending via mapi. No error dialogs before the crash either. This was a consistent crash for me earlier. verifying Win 32 2001-10-16-05 0.9.4 Branch

Reassign to Krishna. Since Rajiv will be away from 11/10 to 11/26. Will start working on this after completion of trunk landing.

reassigning to rdayal.

nomianting because if dataloss and crash, when it happens ...

Trix, can u please try to reproduce this one.

ADT need info, does it happen, was the patch checked in?

the patch above (id=53376) has been checked in during trunk landing in Dec-Jan. This does not happen anymore. Trix, can u please verify this on trunk and 1.0 branch and close if you cannot see this anymore.

Worksforme Build ID: 2002042608 (0.9.9+) trunk Windows 98, Word 2000 SR-1.

Changing status to works for me since could not be reproduced anymore.

wfm, marking verified