Directory Service cannot start, Windows Server 2003 error, lsass.exe system error

Our primary domain controller is giving me the following error:

lsass.exe system error

Security Accounts Manager initalization Failed
Directory Service Cannot start

Error status:  0xc00002e1

I came into work this morning and that error was up on the screen.

This server is our:  Domain Controller, Global Catalog, DNS and DHCP server

MS Server 2003

So we are have all sorts of fun problems throughout our network right, great Monday morning.  I was able to get into Directory Services Restore Mode but have no clue what exactly I am suppose to do.  This is a major problem.  I am open to all suggestions?   We do have another machine that is another Domain Controller.  Is an easy fix just to make another server our DNS and DHP server?  Again open to all suggestions, thanks...
teamorangeAsked:
Who is Participating?
 
teamorangeConnect With a Mentor Author Commented:
Ended up having to seize DNS, Global Catalog and DHCP...  Then install DNS and DHCP on the other domain controller...  Fun stuff...
0
 
Farhan KaziSystems EngineerCommented:
Have you gone through following?
http://support.microsoft.com/kb/258062
0
 
teamorangeAuthor Commented:
Yes, I was actually going through those steps.  Ran the ntdsutil files integrity check and the following is the report:

C:\WINNT\Profiles\Administrator>ntdsutil files integrity
ntdsutil: files
file maintenance: integrity
Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet Error -501].

Error While Doing Soft Recovery
Executing Command: C:\WINNT\system32\esentutl.exe /g"C:\WINNT\NTDS\ntds.dit" /o

Initiating INTEGRITY mode...
        Database: C:\WINNT\NTDS\ntds.dit
  Temp. Database: TEMPINTEG3704.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 file or corrupted db) after 42.266 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.

Also tried the ntdsutil "sem d a" "go f"  command and received the following:

C:\WINNT\Profiles\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 -501.
Failed.

Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet Error -501].
semantic checker:

Not sure what the next logical step would be?
0
 
kibatsuCommented:
I had this exact same issue, the easiest way to fix this (and the last resort) was to restore a system state backup.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.