Closed Bug 217869 Opened 21 years ago Closed 21 years ago

Using two user Profiles one user is able to open "Compose new mail/message window" the other gets reported an error

Categories

(MailNews Core :: Composition, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 162640

People

(Reporter: wjs, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

We (my friend and me) are using Win 2 K with 2 user-profiles for mozilla. He can
edit and write new messages and mails. If I try to open the compose window I get
a small window reporting the following: "An error occured while creating a
message compose window. Please try again." But it doesn't matter how often I
try, it's always the same. The error occured after upgrading from mozilla 1.3
final to 1.4 final. And also when we tried to use 1.5 alpha it didn't work. I
searched all possible data files matching user relevant differences but couln't
find any relevant entry.

Reproducible: Always

Steps to Reproduce:
1. Open the messenger.
2. Press the "Compose"-button or "Reply"-button.
3. Get failure-notice


Actual Results:  
failure-notice saying: "An error occured while creating a message compose
window. Please try again."

Expected Results:  
Opening a message compose window
It might be that your profile is corrupt. Try creating a new one and seeing if
it works.
dupe of "an error occurred while creating a message compose window. Please try
again."

the bug is caused by invalid account settings in your preferences (accounts
referencing non-existent servers in your prefs.js).  you can clean up your
prefs.js file, grab 1.5b or wait for 1.4.1.

*** This bug has been marked as a duplicate of 162640 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.