|
Replication Fails in Windows NT 4.0Article ID: Q157448Creation Date: 10-OCT-1996 Revision Date: 30-APR-1997
The information in this article applies to:
SYMPTOMS
Replication fails with Event 3216 - System Error 5.
CAUSE
In Windows NT 4.0, a new feature was introduced to restrict remote users
from remotely accessing a computer's Registry, unless the administrator of
that computer explicitly grants the remote user access by setting the
permission on a new registry key. This adversely affects directory
replication.
The Administrator program generates a replication account called repluser,
and grants membership for that account in the Replicator and Backup
Operators groups. These groups then configure the Directory Replicator
services on the export and import computers to use this account. When the
replication interval occurs, the import computer makes a remote procedure
call (RPC), requesting to read the registry of the export server to
determine the subdirectories that exist for replication. By default, only
the Administrators group has permission to remotely access the Registry. If
no other groups or users were specified in the Permission list, the account
used for replication is denied access and replication fails.
WORKAROUND
On the export computer, give repluser read access to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurePipeServers
\Winreg
You need to restart the computer for this registry value to be reread.
Also refer to KB Article ID: Q158994 Windows NT 4.0 Fails to Replicate to Backup Domain Controllers |
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
©1997 Microsoft Corporation. All rights reserved. Legal Notices.