RE: active directory error

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 related error when you restart the server.
The SBS server prevents you from properly log in even when you have input
the correct Administrator username and password. However, the clients can
log onto the domain and access resources without problem. You have a
concern about what result from the error and how to fix it.
If I have misunderstood your concerns please feel free to let me know.

Explanation :
==============

Typically, this issue general results from the reasons (Hardware failure or
Active Directory database error). From the description, the error is
prompted after the hardware maintenance restart. The active directory
database may be partial corrupted for the reason of improper hardware
handling. To verify the current Active Directory database status, you can
use the Ntdsutil/esentutl tool.

Suggestion:
===============

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.

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.

2. 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

If we cannot resolve the issue after we perform the steps above, please
help me collect some information for further investigation:

Information needed:
==============
1. Can you log onto the clients using the domain Administrator account? Can
you Remote Desktop (RDP) to the SBS 2003 server with the administrator
account?

2. What is the exact message prompted when you restart the server?

3. If you can log into the SBS server with the Administrator account, could
you please collect the MPS report on the SBS 2003 server for a good view of
the surrounding and the error events that system gets 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

If you have any questions or concerns, please do not hesitate to let me
know.


Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • Re: NTDS ISAM DataBase Corruption
    ... Did you tried the recover the corrupted Active Directory process that a gave ... This is brand new IBM Server. ... using symantec livestate recovery. ... Active Directory database is unavailable because it is damaged, ...
    (microsoft.public.windows.server.active_directory)
  • RE: Move the monitoring database in Windows Small Business Server 2003
    ... I made a test on my test machine (move monitoring database from C:\Program ... Restarted the server. ... Microsoft CSS Online Newsgroup Support ... <I now cannot restart the service MSSQL$SBSMONITORING. ...
    (microsoft.public.windows.server.sbs)
  • Re: nt4.5 to w2003
    ... keep in mind that there basically is two different things you can do to move from an NT 4 (SAM Database) domain to an Active Directory Domain. ... You can choose to upgrade the domain from NT 4 to Windows 200x Active Directory. ... The thing to keep in mind here is that you have to Upgrade an NT 4 PDC to Windows 200x. ... You could download and install Virtual Server 2005 if you needed to upgrade an NT 4 machine to Windows 200x and your real hardware either does not support NT 4, or the NT 4 hardware you have does not really support Windows 200x. ...
    (microsoft.public.windows.server.migration)
  • Re: NTDS ISAM DataBase Corruption
    ... This is brand new IBM Server. ... using symantec livestate recovery. ... You may try the following steps to recover the corrupted Active Directory, ... Active Directory database is unavailable because it is damaged, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 404 Errors
    ... inherited this server from the previous IT staff here and it is riddled ... Active Directory is functioning properly and add or update this domain ... Event Source: NTDS Replication ... The replication operation encountered a database error. ...
    (microsoft.public.windows.server.active_directory)
Loading