Re: AD Repair Possible? Event ID 474's
- From: "R" <none@xxxxxxxx>
- Date: Thu, 17 Jul 2008 09:11:22 -0500
Thank you very much for the reply. I will have to schedule the downtime and
try the steps below.
thanks again.
"Miles Li [MSFT]" <v-mileli@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:EWFmG%23%235IHA.1624@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
Thank you for your post.
Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:
You receive the Active Directory database ntds.dit checksum mismatch error
(Event ID 474) on the Windows SBS 2003 server. However, everything (ADUC,
Exchange server) seems to work correctly without any problem. You have a
months old backup and have a concern if a database Check/recovery with
reboot is necessary.
If I have misunderstood your concerns please feel free to let me know.
Explanation :
==============
Typically, this issue general results from the 2 reasons (Hard disk error
and Active Directory database error). From the description, the suddenly
power off of the SBS server may stop the Active Directory write data and
make Active Directory data inconsistent. Because all check/repair Active
Directory database processes must run under the Directory Services Restore
Mode, you have to restart the SBS 2003 server to Directory Services
Restore
Mode and the SBS 2003 server will absent from service during that time.
With this error/corruption we have two options for your reference:
1. Perform an offline defragmentation of the database. The process will
return the result of the integrity check. If the error is in secondary
data
(e.g., an index page) then it will be reconstructed from primary data and
you'll be fine.
a) In the Directory Services Restore Mode, click Start, click Run, type
ntdsutil in the Open box, and then press ENTER.
b) At the Ntdsutil command prompt, type files, and then press ENTER.
c) At the file maintenance command prompt, type recover, and then press
ENTER.
d) Type quit, and then press ENTER.
e) Restart the computer.
To use Esentutl.exe to perform database recovery, follow these steps:
a) In the Directory Services Restore Mode, click Start, click Run, type
cmd
in the Open box, and then press ENTER.
b) Type esentutl /r path\ntds.dit, and then press ENTER. path refers to
the
current location of the Ntds.dit file.
c) Delete the database log files (.log) from the WINDOWS\Ntds folder.
d) Restart the computer.
Compact the directory database file (offline defragmentation)
http://technet2.microsoft.com/windowsserver/en/library/5dd6f9eb-0533-4474-ac
52-dca78c5471dd1033.mspx
If database integrity check fails, perform semantic database analysis with
fixup
http://technet2.microsoft.com/windowsserver/en/library/f531b60a-dd70-4b2f-9d
03-4ac472b44ec91033.mspx
816120 How To Use Ntdsutil to Manage Active Directory Files from
the Command Line in Windows Server 2003
http://support.microsoft.com/kb/816120
2. If all repair attempt fail, you may have to restore the Active
Directory
from the up-of-date backup.
Information needed:
==============
To have a good view of the surroundings and the error events that system
gets, could you please collect the MPS report on the SBS 2003 server and
send to me at v-mileli@xxxxxxxxxxxxx <mailto:v-mileli@xxxxxxxxxxxxx>?
Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en
Hope this helps. Also, if you have any questions or concerns, please do
not
hesitate to let me know.
Best regards,
Miles Li
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
.
- Follow-Ups:
- Re: AD Repair Possible? Event ID 474's
- From: Miles Li [MSFT]
- Re: AD Repair Possible? Event ID 474's
- References:
- AD Repair Possible? Event ID 474's
- From: R
- RE: AD Repair Possible? Event ID 474's
- From: Miles Li [MSFT]
- AD Repair Possible? Event ID 474's
- Prev by Date: Re: WSS 3.0 + Port 80?
- Next by Date: Re: ATTN Al Williams: service control mgr error
- Previous by thread: RE: AD Repair Possible? Event ID 474's
- Next by thread: Re: AD Repair Possible? Event ID 474's
- Index(es):
Relevant Pages
|
