Do you have any schema extensions applied? Do you know if those schemas
added any LDAP naming attributes? If the 2nd question doesn't make sense
to you, I'll figure out a way you can query this, and send it to us.
Aside, it is generally not recommended to run "restore database". In fact
this command was removed from Longhorn.
If you decide to retry that scenario again, I can suggest some
intermediate steps that would be good to know. i.e.
1. Before running auth restore, be interesting to know the results of an
esentutl /k ntds.dit (checksum the database).
2. After auth restore, it would be good to know if the database is
logically consistent from ESE's perspective (do this via "esentutl /g
ntds.dit").
3. Also after we know it is logically consistent from AD's perspective (do
this via, exact command line provided:
ntdsutil "sem data anal" "go" "q" "q"
Cheers,
BrettSh [msft]
Ex-Building 7 Garage Door Operator
On Tue, 20 Jun 2006, Joshua Coffman wrote:
> I have a few questions for you AD gurus out there! :)
>
> I just ran through a Disaster Recovery test of two of our ADs and I
> have a few questions which have come up as a result of the test.
>
> Configuration Notes:
> These boxes are Windows 2003, SP1.
> The domains were originally Windows 2000 domains.
>
> The following errors pop up on one of the domain controllers during
> the restore.
>
> "Could not display the attribute type for the object with DNT
> 831424.Error: failed to get dn of dnt 831424" This occurs many times
> throughout the restore.
>
> NOTE: This is during a complete restore, e.g. "authoritative restore:
> restore database" I also see a few of these.
>
> "There was an error parsing the GUID from the file on line: 1981" (Not
> to many of these, maybe four or five)
>
> Additionally, with SP1, LDIF files are created to restore back-links.
> The file that restores the user/group back-links imports successfully.
> The file that restores the configuration back-links fails. (sorry, I
> do not have the error handy)
>
> The authoritative restore says it completed successfully, and after I
> go through metadata cleanup and FSMO seizure, the box starts up
> without any errors, and AD throws no errors on startup.
>
> I was wondering if anyone can tell me what these errors mean? What
> are their ramifications? How can the errors be resolved.
>
> Thanks,
>
> Josh
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx
