Full Synchronisation failed with NT4SP5

[Andreas Bell]

I have a PDC an severals BDC set up with NT4 SP5 (english). I use the
replicator service correctly set-up. When I invoke a BDC to synchronize
with it's PDC, the event log of the BDC gets three entries:
1. ID5715 The partial synchronization replication of the SAM database... OK
2. ID5715 The partial synchronization replication of the BUILTIN
database... OK
3. ID5718 The full synchronization replication of the LSA database ...
failed with the following error:
The system cannot find the file specified.

The entries in the PDC event log are:
1. ID5711 The partial synchronization request... OK
2. ID5711 The partial synchronization request... OK
3. ID5714 The full synchronization request from ... failed with the
following error:
The system cannot find the file specified.

The dataword is c0000034.

I checked MS KBase for keywords 5714/5718/LSA and tried Q199071 and Q187327
(specially ;-)) and Q149664 and Q197985. The problem still exists (on all
BDCs).

thanks for a hint
Andy Bell
Switzerland

[Tracy]

Andy, me and a MCSE have been struggling with this same problem for
weeks now. We finally figured it out and here are the notes:

Our BDCs are now in harmony with the PDC. Quick recap: The LSA
database on the PDC would not perform a complete synchronization with
the BDCs. The Builtin and SAM databases would synchronize however.
The LSA would perform a partial synchronization with the BDCs (weird,
huh?). The problem was whenever a change was made that affected the
LSA database, the change would take a very long time to get replicated
throughout the domain. Whenever we created a new user, it would take
up to thirty minutes before the person could log on. The problem
started whenever we moved the PDC over to a new building and changed
its IP address.

We tried every Microsoft and Windows User Group suggested fix under the
sun to no avail. The latest attempt was to delete the LSA database on
BHTAS1 and see if it would recreate itself upon restart. (Warning: do
not try this at home. Bad things happen, man,... bad things.) The fix
turned out to be very easy. We basically did a brute force
synchronization of the LSA database. After bringing a temporary BDC
online and promoting it up to PDC, we synched up the domain.
Everything synched except, of course, BHTAS1. We then went into the
registry of the new PDC and copied the LSA database keys to a file. We
then went to BHTAS1 and restored the keys into the registry overwriting
the corrupt database. BHTAS1 was then able to synch up in the domain.
It was then promoted back to PDC and the temporary BDC removed. The
PDC and BDCs are now synching and replicating very fast now.

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

[mike...@my-deja.com]

What are the LSA registry keys and how to I export and Import them.

Sent via Deja.com http://www.deja.com/
Before you buy.

[Tracy]

The LSA database is not easily recognizable in the registry. It is
located at:
(from the new, fresh PDC or an existing BDC)
HKEY_LOCAL_MACHINE
SECURITY
POLICY
ACCOUNTS
and
HKEY_LOCAL_MACHINE
SECURITY
POLICY
SECRETS
Save both of these registry keys to some place which will be easily
reachable on the network. Bring the old PDC back online and immdiately
DEMOTE.
Restore the registry keys previously saved to the old PDC registry.
Sync up the servers and then PROMOTE the old PDC back to being the PDC.
The new PDC will automatically back itself down to a BDC.