System Monitor Counters Generate NTFRS Errors in the System Log (294250)


The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
This article was previously published under Q294250

SYMPTOMS

The following error messages are logged in the System log of a server that is running the File Replication service (FRS):
NTFRSperf 13527

The RPC binding failed in the Open function of the FileReplicaSet Object.
The counter data for this object will not be available.
The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.
Perflib 1008

The Open Procedure for service "FileReplicaSet" in DLL "C:\WINNT\system32\NTFRSPRF.dll" failed.
Performance data for this service will not be available.
Status code returned is data DWORD 0.

CAUSE

This behavior occurs for various reasons such as data corruption which affects the performance counters.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this behavior, force the File Replication service to re-create the registry keys that point to the system monitor counters for the File Replication service:
  1. Type the net stop NTFRS command at a command prompt to stop the File Replication service.
  2. Start Registry Editor, and then delete the following registry keys:
    1. Delete the FileReplicaConn folder and all the subfolders, which are located under the HKLM\System\CurrentControlSet\Services key.
    2. Delete the FileReplicaSet folder and all the subfolders, which are located under the HKLM\System\CurrentControlSet\Services key.
  3. Restart the File Replication service to place the two keys back in the registry.
  4. Restart the server.
You may need to refresh Registry Editor to see the newly created registry keys.
Modification Type:MinorLast Reviewed:1/27/2006
Keywords:kbenv kberrmsg kbprb KB294250
©2004 Microsoft Corporation. All rights reserved.