Please have a look to see if you can assist with this problem:
Hardware: HP proliant server
Software: Windows server 2003 SBS
Problem: The system intermittently freezes for minutes and is very slow.
Error log: Reports various Active Directory errors.
Resolution: Hardware tested ok. Running Ntdsutil results in the following output:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>ntdsutil files info
ntdsutil: files
file maintenance: info
Drive Information:
C:\ NTFS (Fixed Drive ) free(282.4 Gb) total(297.8 Gb)
DS Path Information:
Database : C:\WINDOWS\NTDS\ntds.dit - 12.1 Mb
Backup dir : C:\WINDOWS\NTDS\dsadata.bak
Working dir: C:\WINDOWS\NTDS
Log dir : C:\WINDOWS\NTDS - 40.0 Mb total
res2.log - 10.0 Mb
res1.log - 10.0 Mb
edb0003C.log - 10.0 Mb
edb.log - 10.0 Mb
file maintenance: exit
Error 80070057 parsing input - illegal syntax?
file maintenance:
file maintenance:
file maintenance: q
ntdsutil: q
C:\Documents and Settings\Administrator>ntdsutil files integrity
ntdsutil: files
file maintenance: integrity
Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet
Error -255].
Error While Doing Soft Recovery
Executing Command: C:\WINDOWS\system32\esentutl.exe /g"C:\WINDOWS\NTDS\ntds.dit"
/o
Initiating INTEGRITY mode...
Database: C:\WINDOWS\NTDS\ntds.dit
Temp. Database: TEMPINTEG3580.EDB
Checking database integrity.
The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.
To ensure the database is up-to-date please use the 'Recovery' operation.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................
Integrity check completed. Database is CORRUPTED!
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi
le or corrupted db) after 0.656 seconds.
Spawned Process Exit code 0xfffffb4a(-1206)
If integrity was successful, it is recommended
you run semantic database analysis to ensure
semantic database consistency as well.
file maintenance: q
ntdsutil: q
C:\Documents and Settings\Administrator>ntdsutil "sem d a" "go f"
ntdsutil: sem d a
semantic checker: go f
Fixup mode is turned on
Opening DIT database... Could not initialize the Jet engine: Jet Error -255.
Failed.
Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet
Error -255].
semantic checker:
Where can we take it from here? Is the Active Directory reparable within reason or should the server be rebuilt?
Thanks in advance.
