Always get error starting Mozilla: "An error occurred reading the startup configuration file. Please contact your administrator. Syntax error: illegal character [then it shows 3 characters -- an up arrow, an "i", and an "a" with accent mark

VERIFIED INVALID

Status

VERIFIED INVALID
16 years ago
14 years ago

People

(Reporter: jcralston, Assigned: netscape)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126

This began after a PC-Cillin anti-virus program update downloaded and installed
itself on my machine...

Reproducible: Always

Steps to Reproduce:
1. start Mozilla
2.
3.

Actual Results:  
showed error message described above...but then seems to work.

Expected Results:  
not shown error message

Comment 1

16 years ago
Chances are that (unrelated to the PC-Cillin update) your profile's "prefs.js"
has been corrupted. Can happen during a crash.

Try open that file with Notepad while Mozilla is not running.
Search for the mentioned phrase - or simply for the accented a.
Is there a corresponding line?
(Reporter)

Comment 2

16 years ago
Thank you for the help. I opened the file with Notepad, but did not return
any matches for the exact string of characters shown in the error message.
Searching for the accented "a", I found many, many instances. Also, many
instances of "i" and then the accented "a"...

Is there anyway to ditch the prefs.js file and start again?

Comment 3

16 years ago
Is it impossible to determine where in the current prefs.js the flaw is?
Are all the "iá" findings valid occurances?

As for a new prefs.js, it's probably simpler to create a new profile, set up
mailnews again, and then copy over the mail folders from the old profile to the
corresponding new one.
(Reporter)

Comment 4

16 years ago
Okay, I just deleted the corrupted file, and now it seems to work okay...no 
error messages.

Thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Invalid.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago16 years ago
Resolution: --- → INVALID

Comment 7

16 years ago
v invalid.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.