Directory Replication Fails with Event ID 3216

Last reviewed: November 5, 1997
Article ID: Q168464

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information on how to do this, view the "Restoring the Registry" online Help topic in Regedit.exe or the "Restoring a Registry Key" online Help topic in Regedt32.exe.

SYMPTOMS

Directory Replication fails to replicate to import servers. An export server will successfully replicate to itself, even though it may report errors.

The Windows NT Event Log on the export server records the following event:

   Event ID: 3216
   Source: REPLICATOR
   System error 5 has occurred.

The Windows NT Event Log on the import server may record one or both of the following events:

   Event ID: 3216
   Source: REPLICATOR
   System error 2116 has occurred.

   Event ID: 3208
   Source: REPLICATOR
   The replication service could not update directory <name> from source
   on <export server name> due to error <error number>.

CAUSE

In Windows NT 4.0, a new feature was introduced to restrict remote users from 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 can prevent directory replication.

When the replication interval passes, the import computer reads the registry of the export server to determine replication parameters. By default, only the Administrators group has permission to remotely access the registry. If no other groups or users were specified in the access control list, or if the registry path is not specified as an allowed path, the account used for replication is denied access and replication fails.

WORKAROUND

For Directory Replication to work properly, an explicit user account must be used. Using the System account will fail. For more information on how to create an explicit user account for Directory Replication, see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q132522
   TITLE     : Quick Directory Replication Troubleshooting Tip

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" online Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" online Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

Start the Windows NT Registry Editor (Regedt32.exe) on the export server.
Go to the following registry key:
```
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
      \SecurePipeServers\winreg\AllowedPaths
```
NOTE: The above registry key is one path; it has been wrapped for readability.
Double-click the Machine:REG_MULTI_SZ value and add the following string under that last entry:
```
      System\CurrentControlSet\Services\Replicator
```
Restart the computer.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords          : kbbug4.00 ntdomain ntgeneral NTSrvWkst kbnetwork
Version           : WinNT:4.0
Platform          : winnt
Hardware          : ALPHA PPC x86
Issue type        : kbbug

================================================================================

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.

Last reviewed: November 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.