ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

netscape autoconfig failed

  • 5 ردود
  • 2 have this problem
  • 1 view
  • آخر ردّ كتبه cor-el

more options

I'm not sure that I am understanding the other posts related to this problem. I've created a .cfg file to disable automatic updates on a terminal server for my users. I've also creates a .js file to process the .cfg file, when I try to open Firefox i get a pop up message saying: Netscape.cfg/AutoConfig failed. Please contact your system administrator.

Error: lockPref failed: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIPrefBranch.prefIsLocked]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: prefcalls.js :: lockPref :: line 71"  data: no]

I saw a fix that involved commenting out a command in the cfg file, but I didn't find that command in my file. If i click "Ok" the pop up closes and firefox opens correctly and updating is disabled like I want. This isn't game breaking, but my users tend to "freak out" when they see a pop up message they don't understand. Any Idea on how to make this message go away?

CFG File text is: defaultPref(); // set new default value pref(); // set pref, but allow changes in current session lockPref(); // lock pref, disallow changes lockPref("app.update.enabled", false);

.js file text is: pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0); // use this to disable the byte-shift

I'm not sure that I am understanding the other posts related to this problem. I've created a .cfg file to disable automatic updates on a terminal server for my users. I've also creates a .js file to process the .cfg file, when I try to open Firefox i get a pop up message saying: Netscape.cfg/AutoConfig failed. Please contact your system administrator. Error: lockPref failed: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIPrefBranch.prefIsLocked]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: prefcalls.js :: lockPref :: line 71" data: no] I saw a fix that involved commenting out a command in the cfg file, but I didn't find that command in my file. If i click "Ok" the pop up closes and firefox opens correctly and updating is disabled like I want. This isn't game breaking, but my users tend to "freak out" when they see a pop up message they don't understand. Any Idea on how to make this message go away? CFG File text is: defaultPref(); // set new default value pref(); // set pref, but allow changes in current session lockPref(); // lock pref, disallow changes lockPref("app.update.enabled", false); .js file text is: pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0); // use this to disable the byte-shift

الحل المُختار

OMG i feel dumb... i just commented out all of the lines except the lockpref and the pop up went away... total oversight. Thanks for looking in to this for me.

Read this answer in context 👍 0

All Replies (5)

more options

Does this happen when you try it in a new profile? How are you updating the cfg file to the other profiles? http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profil...

more options

The mozilla.cfg file in in the Firefox program folder and thus works for all profiles and can't be bypassed.

Can you post the content of the mozilla.cfg file?

You can try to comment out lines with a leading // to see if you can locate an entry that isn't working.

more options

defaultPref(); // set new default value pref(); // set pref, but allow changes in current session lockPref(); // lock pref, disallow changes lockPref("app.update.enabled", false);


This is the mozilla.cfg file, I've tried commenting out the lockpref line at the bottom as that seems to be the only line that has an action in it.

more options

الحل المُختار

OMG i feel dumb... i just commented out all of the lines except the lockpref and the pop up went away... total oversight. Thanks for looking in to this for me.

more options

You do not need those three lines. Those are only meant as examples of function calls that you can use in the file and of course to make them work they would have to contain valid pref setting content.

The first line in the mozilla.cfg file is skipped and should be a comment line.

//
lockPref("app.update.enabled", false);