Knowledge Base |

# Replicator Service Monopolizes CPU

Article ID: 111993

Article Last Modified on 10/31/2006

APPLIES TO

- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1

This article was previously published under Q111993

## SYMPTOMS

When file replication starts with a LAN Manager version 2.2 import server receiving files from a Windows NT Advanced Server export server, intermittent failures may occur. The chances for this become greater when you use multiple LAN Manager import replicator servers.
Performance Monitor running on the Windows NT Advanced Server export replicator server shows the CPU utilization at or above 90 percent due to the replicator service. Under usual conditions, the high CPU utilization only lasts briefly. However, if the LAN Manager server fails, it is possible for the high CPU utilization to persist until the Directory Replicator service is shut down at the Windows NT Advanced Server export server. The replicator shows approximately 65 percent Privileged CPU use and approximately 15 percent User CPU use, according to Performance Monitor. The files fail to replicate to one or more import servers as indicated by the presence of the following file in the REPL\IMPORT directory LAN Manager import servers:

       NOSYNCH.RPL$

## CAUSE

This problem occurs when the LAN Manager 2.2 ring 3 server fails due to a problem in NETAPI.DLL. Although the LAN Manager workstation services, HPFS386 services, and transport protocols keep a session active with the import server, the LAN Manager Server Message Block (SMB) services may fail due to the ring 3 server.

## RESOLUTION

To avoid this problem, upgrade the LAN Manager 2.2 servers to LAN Manager 2.2b, which includes the corrected OS/2 NETAPI.DLL file.

Additional query words: rpl prodnt replicator

Keywords: kbinterop KB111993