1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Can't compose mail

Discussion in 'Firefox, Thunderbird & SeaMonkey' started by Westside, 2005/11/17.

  1. 2005/11/17
    Westside

    Westside Inactive Alumni Thread Starter

    Joined:
    2003/03/30
    Messages:
    4,506
    Likes Received:
    14
    A friend told me of problems with NS7.2 mail which give this error:An error occured while creating a message compose window. Please try again .
    In other words can even get the compose window. ???
     
  2. 2005/11/17
    Ramona

    Ramona Geek Member Alumni

    Joined:
    2001/12/31
    Messages:
    7,481
    Likes Received:
    2
    Westside,

    Suggest to your friend that he rename localstore.rdf (Xlocalstore.rdf). If that fixes the problem 3 cheers! If not, then rename the chrome folder (Xchrome).

    If no joy, then lemmeno...
     

  3. to hide this advert.

  4. 2005/11/18
    Westside

    Westside Inactive Alumni Thread Starter

    Joined:
    2003/03/30
    Messages:
    4,506
    Likes Received:
    14
    Ramona, I asked him to Find the word compose in localstore.rdf. I got several entries, although he said that there was none. After he renamed, he says that he lost all the names of the folders. As for the Chrome folder, it just went back from Classic to Modern theme.
    I never tried either fix. does the renaming create a new native file? And, if so would it have anything more than the basics in it?
     
  5. 2005/11/18
    Ramona

    Ramona Geek Member Alumni

    Joined:
    2001/12/31
    Messages:
    7,481
    Likes Received:
    2
    Westside,

    Once Netscape starts, a pristine file is created for those renamed files. On looking for more information on this error, I did find a bug which is for this specific error. The bug was to have been fixed some time ago, tho it appears it has reared its ugly head again: http://bugzilla.mozilla.org/show_bug.cgi?id=162640

    Your friend should replace the prefs.js file with a backup made before the error started occurring (if available) or else create a new Profile.
    http://home.att.net/~cherokee67/NS7newprofile.html
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.