Re: User Rights Assignment - not available

Weird. There are free tools from SysInternals called filemon and regmon that
if you start them just before you try to run something and then stop them
from logging when the action fails you may find helpful information in the
log for access denied entries that would indicate something you do not have
necessary permissions for. I use them quite a bit and find it is helpful to
add access denied to filter view to highlight as there could be thousands of
entries in the log. The link below is to regmon and filemon.

http://www.sysinternals.com/Utilities/Filemon.html
http://www.sysinternals.com/Utilities/Regmon.html

Another thing you could try is to use the secedit command to try and restore
security settings to default defined levels which may help per the link
below. You can simply copy and paste the command to run as it is. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;EN-US;313222


"Tim Munro" <Excelsior@xxxxxxxxxxx> wrote in message
news:OPXQhEiOGHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
I went through both the integrity check and did a repair anyway. Result
is the same. I'm guessing here that this may be a permissions problem.
Everything else on the "Local Policy" mmc is accessible and changeable.
It's just the "User Rights Assignment" that is bad.

When I went to rebuild (copying and renmaing as the article suggests) I
did get the access denied. Unfortunately "Import Template" was greyed out
when I used the filename secedit.sdb. Any other name and it was fine.

Is there somewhere in the registry I can check for permissions that
might be causing this behaviour?

Thanks
--
Tim

"Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8OidnU6airjcPGLenZ2dnUVZ_vudnZ2d@xxxxxxxxxxxxxx
Hmm. It sounds like you may have a corrupt secedit.sdb file. See the link
below for two possibilities of which one is to attempt a repair with
esentutl and the other is a rebuild. --- Steve

http://support.microsoft.com/?kbid=894351

To resolve this issue, first run the Esentutl.exe tool to examine the
integrity of the Secedit.sdb database. To do this, follow these steps: 1.
Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type the following command, and then press
ENTER:
esentutl /g Drive:\WinDir\security\database\secedit.sdb
Note In this command, Drive is the hard disk drive where Windows XP
Professional is installed, and WinDir is the folder where Windows XP
Professional is installed.
After the Esentutl.exe tool finishes, use one of the following methods to
resolve the issue, depending on the message that the Esentutl.exe tool
returns: . If the Esentutl.exe tool returns the following message, use
Method 1 to resolve the issue:
This operation may find that this database is corrupt
. If the Esentutl.exe tool returns information that is similar to
the following message, use Method 2 to resolve the issue:

Microsoft(R) Windows(R) Database Utilities
Version 5.2
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating INTEGRITY mode...
Database: L:\WINDOWS\security\database\secedit.sdb
Temp. Database: TEMPINTEG2680.EDB

Checking database integrity.

Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|---|---|---|---|---|---|---|---|---|---|
...................................................

Integrity check successful.

Operation completed successfully in 0.841 seconds.
Note When you run the Esentutl.exe tool, your computer is returned to the
original installation state where the Local Security Policy is not
defined. You may have to start your computer in Safe Mode to rename files
or to move files. To start your computer in Safe Mode, press the F8 key
while Windows XP Professional is starting, type 1 to choose Safe Mode
from the startup options, and then press ENTER.

"Tim Munro" <Excelsior@xxxxxxxxxxx> wrote in message
news:uOKPnsWOGHA.2124@xxxxxxxxxxxxxxxxxxxxxxx
Hello all,

On my local PC (Windows XP SP2), in "Local Security Settings>Local
Policies>User Rights Assignments" I get "Windows cannot read template
information". Any idea what happened and/or how to get this back?

--
Tim.








.

Relevant Pages

  • Re: User Rights Assignment - not available
    ... You can simply copy and paste the command to run as it ... and WinDir is the folder where Windows XP ... This operation may find that this database is corrupt ... Initiating INTEGRITY mode... ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Replacing backend database
    ... Windows copy command from within the database? ... >> to zip the backend database and copy it to a floppy. ...
    (microsoft.public.access.formscoding)
  • Re: User Rights Assignment - not available
    ... User Rights configuration was completed successfully. ... You can simply copy and paste the command to run as it is. ... and WinDir is the folder where Windows XP ... This operation may find that this database is corrupt ...
    (microsoft.public.windowsxp.security_admin)
  • Re: User Rights Assignment - not available
    ... To resolve this issue, first run the Esentutl.exe tool to examine the ... and WinDir is the folder where Windows XP ... This operation may find that this database is corrupt ... Initiating INTEGRITY mode... ...
    (microsoft.public.windowsxp.security_admin)
  • Re: User Rights Assignment - not available
    ... I went through both the integrity check and did a repair anyway. ... To resolve this issue, first run the Esentutl.exe tool to examine the ... and WinDir is the folder where Windows XP ... This operation may find that this database is corrupt ...
    (microsoft.public.windowsxp.security_admin)