Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

GP Errors

1 view
Skip to first unread message

Carl Hilton

unread,
Sep 14, 2005, 9:18:10 AM9/14/05
to
Ok, I am betting event 1202 errors referencing error 0x4b8... Reading the
associated SUPPORT help topic (Q324383) (which looks out of date because it
references using "secedit /refreshpolicy" vicd "gpupdate /force", I see
nothing in the 0x4b8 section worthwhile.. I did turn on the debugging:

Wednesday, September 14, 2005 8:58:11 AM

Error 1208: An extended error has occurred.

Error creating database.

----Configuration engine was initialized with one or more errors.----

----Un-initialize configuration engine...

this is the last GPO.

**************************

Make a local copy of
\\my-gdc\SysVol\mydomain\Policies\{F0F84F03-3EEE-4714-81FF-689512530C34}\Machine\Microsoft\Windows
NT\SecEdit\GptTmpl.inf.

GPLinkOrganizationUnit GPO_INFO_FLAG_BACKGROUND )

Process GP template gpt00000.inf.

-------------------------------------------

Wednesday, September 14, 2005 9:04:10 AM

Error 1208: An extended error has occurred.

Error creating database.

----Configuration engine was initialized with one or more errors.----

----Un-initialize configuration engine...

this is the last GPO.

Also looking at the event logs, I see some USERENV, event 1085 with a %1 of
"Security". That lends itself to reregistering the SCECLI.DLL (I believe),
which did not help.

So, now the HELP says to restore the file system and/or registry... Surely
they must be kidding?

THis is on an Tablet PC running the lastest and greatest with all upadates,
and the servers are all 2003 SP1 servers.


Carl Hilton

unread,
Sep 14, 2005, 3:36:31 PM9/14/05
to
The problem was fixed when I:

The resolution to this is simple.
perform a backup first.
In C:\windows\security directory
rename secedit.sdb, edb.chk, edb.log and res1.log and res2.log if they
exist.
reboot the server.
These files will be recreated, but will be blank.
login and perform the following commands to repopulate the database with the
out of the box defaults.

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb
/verbose
secedit /configure /cfg %windir%\repair\secDC.inf /db secDC.sdb /verbose

"Carl Hilton" <som...@microsoft.com> wrote in message
news:ulEWC7Su...@TK2MSFTNGP10.phx.gbl...

0 new messages