An extended error has occurred failed to save local policy database

I got the error: ‘an extended error has occurred failed to save local policy database’ while I am trying to add an user to the Log on as a service in the Local Security Policy.

Fix error: an extended error has occurred failed to save local policy database

Fix error: An extended error has occurred failed to save local policy database

After I have googled some time, found the following solutions to fix this error.

From http://support.microsoft.com/kb/2411938 :

Consider the following scenario:

  •  You install Internet Information Services (IIS) 7.5 on a computer that is running Windows Server 2008 R2.
  • You create a user account that contains a virtual account that has a domain prefix of “IIS AppPool”.
  • You try to change the user rights of the account in Local Security Policy.

In this scenario, you receive the following error message:
An external error has occurred. Failed to save Local Policy Database

If you go back into Local Security Policy to check the user right, you find that the Classic .NET AppPool and DefaultAppPool groups disappeared from the user right.

Hotfix information: Check this article http://support.microsoft.com/kb/2411938 for further details

From http://www.winvistatips.com/extended-error-has-occurred-failed-save-local-policy-database-t548604.html:

Sounds like secedit.sdb may be corrupt. There are a couple of ways that
often will resolve that as per the links below. I would try using esentutl
first for a repair attempt. First check that permissions are correct on the
folder and file itself in windowssecuritydatabase where by default
administrators and system would have full control

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_scetroubletn.mspx
http://www.jsifaq.com/SUBH/TIP3500/rh3561.htm

Advertisement

2 thoughts on “An extended error has occurred failed to save local policy database”

  1. I've found a lot of people reporting this error but the only fixes seem to be for server 2008, apparently you're just effed if you have 2003.

    Reply

Leave a Comment