RE: Database Corruption after Exchange SP 2

Thanks for your suggestions.

I repaired my Exchange database successfully and I can perform backups
without any problems now.

I still get the following error:
ESENT 474 - 283 occurrences last 5:47 am
services (936) The database page read from the file
"C:\WINDOWS\Security\Database\secedit.sdb" at offset 225280
(0x0000000000037000) for 4096 (0x00001000) bytes failed verification due to a
page checksum mismatch. The expected checksum was 806199070 (0x300d9f1e) and
the actual checksum was 806166302 (0x300d1f1e). The read operation will fail
with error -1018 (0xfffffc06). If this condition persists then please restore
the database from a previous backup. This problem is likely due to faulty
hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.

This is the only error I get on the logs plus the 1202 warning mentioned
before.

I have some questions / answers for your previous suggestions:

Regarding the 1202 error Events, I recommend you try the following steps to
check the issue on the computer:

1. A conflict in Group Policy can cause these events to occur. These error
messages can occur if the "Rename Administrator Account" security policy is
enabled and then set to an account name that is already in use. Please
verify if you had set the "Rename Administrator Account" policy or not,
if it is true, please disable this policy on the computer/domain.
You can take a look at the following URL for more information:
260715 Event ID 1000 and 1202 After Configuring Policies
http://support.microsoft.com/?id=260715

Where do I check for the Rename Administrator Account? And, what should be
the value?

2. When you install the Microsoft Windows Server 2003 Administration Tools
Pack in Microsoft Windows XP and then use the Group Policy Editor in
Windows XP to configure domain policies, you may find that the policies do
not work on Microsoft Windows 2000-based computers and get the 1202 error
message.
So please make sure that you had configure the policy on the DC directly
instead of the client computers.

Also if you had imported a security template which contained specific
unique settings to Windows XP / 2003 and was attempting to apply them to
the Windows 2000
machines, this error will occur too. Make sure that you did not set the
settings like this.

I don't have any windows 2000 machines.

3. If you attempt to add users from other domains into a Restricted group
in your domain, the error message of 1202 will occur too.
Please make sure that you use only users and groups in your local domain
when you add to Restricted groups.
Also it is better for you to disable the Group Policy object (GPO) that
defines restricted groups and then check the issue again.

I onlye have one domain

4. This problem can also occur if the local Group Policy database file is
corrupt. However if the issue occurs on all the windows 2000 computer, this
may not be the root cause of this issue. I just provide this information
for your reference. You can take a look at the following URL for more
information:
278316 ESENT Event IDs 1000, 1202, 412, and 454 are logged repeatedly in the
http://support.microsoft.com/?id=278316

Regarding NTDS database corrupted, you can refer to the following article
to use the Ntdsutil tool to recover the database.

816120 How To Use Ntdsutil to Manage Active Directory Files from the Command
http://support.microsoft.com/?id=816120

I'm thinking that the secedit.sdb databse is corrupted... is there a way to
repair it? Would these articles above (4) apply to this problem?

Let me know. Thanks!

.

Relevant Pages

  • Re: Important information about XP SP2 .ADM Files
    ... The Windows 2000 fix is available here: ... >> your attention to an important issue related to Group Policy. ... >> an important issue around the use of the .ADM files we ship with XP SP2. ...
    (microsoft.public.win2000.group_policy)
  • Re: Important information about XP SP2 .ADM Files
    ... The Windows 2000 fix is available here: ... >> your attention to an important issue related to Group Policy. ... >> an important issue around the use of the .ADM files we ship with XP SP2. ...
    (microsoft.public.windows.group_policy)
  • Re: event id 1030
    ... port filtering enabled and is blocking port 389. ... Windows Platform Support Team ... > Windows cannot query for the list of Group Policy objects. ...
    (microsoft.public.windows.server.active_directory)
  • Important information about XP SP2 .ADM Files
    ... Windows XP Service Pack 2. ... your attention to an important issue related to Group Policy. ... Many of the central features in Windows XP Service Pack 2, ...
    (microsoft.public.win2000.group_policy)
  • Important information about XP SP2 .ADM Files
    ... Windows XP Service Pack 2. ... your attention to an important issue related to Group Policy. ... Many of the central features in Windows XP Service Pack 2, ...
    (microsoft.public.windows.group_policy)