lsass.exe error after moving AD to a diff HW

[hal9000]

does anyone have any experience of having lsass.exe
error after moving AD to a different hardware?
the error comes up just before the login session window
asking to either reboot your server in a directory service
repair mode which as a result suffers great deal of
trouble(http://support.microsoft.com/default.aspx?
scid=kb;en-us;258007&Product=win2000)
is there any way to workaround with this matter?
the file location(ntds.dit, etc) and everything looks fine.

 

[Tim Hines [MSFT]]

There is an article on troubleshooting these errors at
http://support.microsoft.com/?id=300425 . Give that a try. Check the
Directory services event log and post the errors that that relate to the
error. That can help narrow the issue down.


--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

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

 

[a-chadl [MSFT]]

does anyone have any experience of having lsass.exe
error after moving AD to a different hardware?
the error comes up just before the login session window
asking to either reboot your server in a directory service
repair mode which as a result suffers great deal of
trouble(http://support.microsoft.com/default.aspx?
scid=kb;en-us;258007&Product=win2000)
is there any way to workaround with this matter?
the file location(ntds.dit, etc) and everything looks fine.

Hal,

First, are you talking about restoring to different hardware or did you
literally copy the NTDS.dit from one server to another? If you are
restoring, are you restoring to dissimilar hardware or is EVERYTHING
exactly the same on the new machine?

Resotring to dissimilar hardware does not work very well. This article may
be some help:
263532 How to Perform a Disaster Recovery Restoration of Active Directory on
http://support.microsoft.com/?id=263532

Also, what is the LSASS error you are getting? If you are getting Error
Status:0xc00002e1you will need to boot into AD Restore mode and run the
following commands to check/repair the integrity of the NTDS.dit file:

The command for performing the integrity check is:

esentutl /g "<Path>\ntds.dit" /!10240 /8 /v /x /o

The command to repair the database is:

esentutl /p "<Path>\ntds.dit" /!10240 /8 /v /x /o

Remember that after performing the repair, you must delete/rename/move the
log files from the
NTDS directory.

Chad A. Lacy
Windows 2000 Directory Services

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

 

[hal9000]

are you restoring to dissimilar hardware or is EVERYTHING
exactly the same on the new machine?

yes, restoring on the dissimilar hw.
or precisely, moving old ad server to a new hw. i've done
this many times and haven't had any problems.

Also, what is the LSASS error you are getting? If you are getting Error
Status:0xc00002e1

yes, this is the error.
it comes just before login window popup.

you will need to boot into AD Restore mode and run the
following commands to check/repair the integrity of the

NTDS.dit file:
thank you for the workaround.
i will give it a try.
the machine is on another bldg and takes time to get there.
though i will be sure to post a reply.

 

[hal9000]

could you tell me the correct location?
the url is no longer accessible and search does not hit
with 300425 also.

http://support.microsoft.com/?id=300425 . Give that a

try. Check the