Could not initialize the applications security component: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
m (Could not initialize the browser security component moved to Could not initialize the applications security component: error message changed to "application's" in 2007 - see https://bugzilla.mozilla.org/show_bug.cgi?id=385458)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
<!--{{Right-pic|Security_component_alert.png}} hiding outdated image-->
<!--{{Right-pic|Security_component_alert.png}} hiding outdated image-->


This article deals with the causes of the message "''Could not initialize the application's security component. The most likely cause is problems with files in your Mozilla application's [[profile]] directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this application session, you might see incorrect behavior when accessing security features.''". For information on other messages received when accessing secure sites, see [[Error loading secure sites]].
This article deals with the causes of the message "''Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features.''".  


==Corrupted file==
For information on other messages received when accessing secure sites, see [[Error loading secure sites]].
The file cert8.db in your profile folder may have become corrupted. Delete this file while the application (Firefox, SeaMonkey, etc) is closed. [http://www.uni.edu/turnert/2005/02/thunderbird-error-could-not-initialize.html] To do this on Windows machines:
# Close the application by choosing File -> Exit.
# Open your [[profile folder]] in Windows Explorer.
# Click on the file named cert8.db.
# Press delete.
# Restart the application. cert8.db will be recreated when you do so.


==Hard drive capacity==
==Hard drive capacity==
Check your hard drive's remaining capacity. To do this on Windows machines:
Check your hard drive's remaining capacity. To do this on Windows machines:
# From the Start menu, click "Computer" ("My Computer" on older Windows versions)
# From the Start menu, click "Computer" (or "My Computer")
# Right click on Local Disk (C: drive)
# Right click on Local Disk (C: drive)
# Choose Properties. A dialog will come up.
# Choose Properties. A dialog will come up.
Line 28: Line 22:
# Make sure the "Read-only" checkbox is '''not''' checked.
# Make sure the "Read-only" checkbox is '''not''' checked.
# Press OK.
# Press OK.
==Corrupted file==
The file cert8.db in your profile folder may have become corrupted. Delete this file while the application (Firefox, SeaMonkey, etc) is closed. [http://www.uni.edu/turnert/2005/02/thunderbird-error-could-not-initialize.html] To do this on Windows machines:
# Close the application by choosing File -> Exit.
# Open your [[profile folder]].
# Click on the file named cert8.db.
# Press delete.
# Restart the application. cert8.db will be recreated when you do so.


==Non-Latin characters in username==
==Non-Latin characters in username==
There seems to be a [https://bugzilla.mozilla.org/show_bug.cgi?id=469856 bug] with non-Latin (For example Chinese or Russian) characters in your username. There's no fix yet but a workaround is to make another account with a Latin characters only username.
Older versions have a [https://bugzilla.mozilla.org/show_bug.cgi?id=469856 bug] with non-Latin (For example Chinese or Russian) characters in your username. (fixed 2009-10-01)


==New profile==
==New profile==

Latest revision as of 15:56, 20 March 2014


This article deals with the causes of the message "Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features.".

For information on other messages received when accessing secure sites, see Error loading secure sites.

Hard drive capacity

Check your hard drive's remaining capacity. To do this on Windows machines:

  1. From the Start menu, click "Computer" (or "My Computer")
  2. Right click on Local Disk (C: drive)
  3. Choose Properties. A dialog will come up.
  4. Go to the General tab

If it reports less than 1MB free space, you'll need to make more room.

File permissions

Check the file permissions in your profile folder. The file named cert8.db must not be read-only. To do this on Windows machines:

  1. Open your profile folder.
  2. Right click on the file named cert8.db.
  3. Choose Properties. A dialog will come up.
  4. Go to the General tab
  5. Make sure the "Read-only" checkbox is not checked.
  6. Press OK.

Corrupted file

The file cert8.db in your profile folder may have become corrupted. Delete this file while the application (Firefox, SeaMonkey, etc) is closed. [1] To do this on Windows machines:

  1. Close the application by choosing File -> Exit.
  2. Open your profile folder.
  3. Click on the file named cert8.db.
  4. Press delete.
  5. Restart the application. cert8.db will be recreated when you do so.

Non-Latin characters in username

Older versions have a bug with non-Latin (For example Chinese or Russian) characters in your username. (fixed 2009-10-01)

New profile

Create a new profile. Your current profile might be corrupted due to many reasons, such as changes in your system or lack of hard drive space at one point.