Active Directory Lightweight Directory Services could not be initialized. 1811 JET_errFileNotFound, File not found

Question

HI ,

ADAM instance cannot be restarted after windows reboot and below error is observed in Logs

Active Directory Lightweight Directory Services could not be initialized.

The directory service cannot recover from this error.

User Action
Restore the local directory service from backup media.

Additional Data
Error value:
-1811 JET_errFileNotFound, File not found

Thanks for any help

Answer 1

Hi @Fan Fan ,

To restore - will copy adamntds.dit file from backup folder and paste it in c:/programfiles/microsoftADAM/data/ location
We have migrated A&B old servers to C&D

Created replica instance in C & D . then seized FSMO roles to C from A.

backup was taken before the seizure.

now server C & D are rebooted then we noticed that adamntds.dit is missing in both new servers

we are trying to recover the lost files but as a plan B we are also thinking of restoring the backup which was taken before seizure.

So to do that , do i need server A & B instances to be in active state as in the backup A is the schema master
steps am thinking for restore is

1. Make server A & B AD LDS instance service started
2. copy adamntds.dit from backup to data folder in new server
3. try to seize schema master to server C again if at all its possible
4. once its successful , disable the AD LDS instance in server A & B

But am not sure if the above steps will work.
Thanks in advance.

Answer 2

Hi ,

Noticed that adamntds.dit file is missing after 2016 server reboot !

I have a backup of 3 days old but that was taken before seizing the schema master to new servers.

Now if i restore this backup , should i have old servers running because schema master is old server on that backup

Thanks

Answer 3

Hi,
Would you please tell more information about the restore operation?
Did the backup a system backup or full server backup?
How may DCs do you have? Were all of them failed?
If you still have good DCs in your domain, it is not suggested to restore the DC from backup.
You can consider demote the problematic one from domain, and then promote again (with a different name and IP address ).
If you can't demote it successfully, you can perform a metadata cleanup:
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup

Best Regards,

Answer 4

Hi ,

I have followed above steps mentioned in my previous comment and able to resolve it.

Thanks