Link to home
Start Free TrialLog in
Avatar of srodenburg
srodenburg

asked on

PDC not replicating to BDC

The replication between my PDC (set up as en exportserver) and my BDC (set up as the import computer) does not work.
I want to replicate the logon-scripts on the PDC who reside inn the "\winnt\system32\repl\import\scripts" directory to the same directory on the BDC.

On both machines the replication-service logs on as an administrator. The "Repl$" shareperms. are set to full control to this user on both NT 4.0 SP3 servers. The directory permissions for the "\winnt\system32\repl\import" on both machines alse have full control perms.
The replication services are both running and there are no errors (or any other messages from the replicator for that matter) in their eventlogs. It's just that nothing happens at all.

On the PDC i configured the "C:\WINNT\System32\Repl\Import" directory as the export dir with the following settings: subdir=scripts, locks=no, stabilize=no, subtree=yes.

On the BDC i configured the "C:\WINNT\System32\Repl\Import" directory as the import dir with the following settings:
subdir=scripts, locks=no, status=no master (that's the problem i think), last update=empty.

I know that when you set the export dir it suggests the "C:\OS\WINNT\System32\Repl\Export" directory by default but as the scripts reside in the "import\scripts" directory i choose that dir. as the export dir. This prevents me from having to copy the scripts from the PDC's "repl\import" dir. to the PDC "repl\export" dir. in order the get them replicated to the BDC.

Also, the "From" and "To" lists on both machines are empty as they are both on the same domain and IP subnet.
The two machines connect through TCP/IP only.
There is no problem with the connection between the two because i can copy files freely between them.

Again, i get no errors anywhere but nothing happens either.

Please help,
Steven
ASKER CERTIFIED SOLUTION
Avatar of moellert
moellert

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of srodenburg
srodenburg

ASKER

The "System\CurrentControlSet\Services\Replicator" value in the key that you discribed was already there.
Also, the currently logged on user AND the user that start the replicator service are are the same (an Administrator).

Anywhere else i can look ?
What about the second part of my answer, the security settings are the WINREG key ?
??? what do you mean with "the security settings are the WINREG key". Do you mean it's possible to give permissions to individual registry keys. I've looked for this in regedit.exe (i prefer it over regedt32.exe) but did not find anything like it. Please clarify.
To modify the security setting of a special Registry key you have to use the regedt32.exe, cause the regedit.exe is just an implementation from Win95 ( OK, it is a bit nicer, easier to use, has a better search engine and so on, but what else does it give to us 8-)))  )
Serius now, open the regedt32.exe and find the key mentioned above. Then click security - permissions and you have the chance to modify all you want.
Well, i did what you said. The user (=administrator) that is used by the Replicator Service on both the PDC and the BDC has full control of the WINREG key and it's subkeys on both machines (he had not but the administrators group had by the way). I rebooted both machines.
The PDC is still quiet as a mouse (reports nothing at all about replication) but the BDC gives a new error in it's eventlog i had not seen before. The error is "The replication server could not update directory scripts from the source on CASPER due to error 32." and "System error 32 occurred." The server CASPER is the PDC and also the export-server.

What does this error mean?
Is it possible for you to implement NETBEUI just for testing ?
I solved the problem! The error "The replication server could not update directory scripts from the source on CASPER due to error 32." means that the file that the replicator wanted to copy to the BDC was in use. Possibly someone logging on at that time. The replicator has worked great ever since.
Thanks for all your help!