Select the product you need help with

Error message when you continuously use the Dfsrdiag.exe utility to query DFS Replication for backlog information in Windows Server 2003 R2

Article ID: 925377 - View products that this article applies to.

SYMPTOMS

You have the Distributed File System (DFS) Replication service installed on a Windows Server 2003 R2-based computer. When you continuously use the Dfsrdiag.exe utility to query DFS Replication for backlog information, you may receive the following error message:

[ERROR] Cannot find DfsrReplicatedFolderConfig object. Possible reasons:
+ The replicated folder is not configured on the member
+ Access is denied to its configuration information

This problem occurs when the query requires replication group information.

Back to the top | Give Feedback

CAUSE

This problem occurs because of a race condition that occurs when you continuously query DFS Replication for information that requires replication group information. In this situation, the DFS Replication Windows Management Instrumentation (WMI) provider cannot provide the replication group information. Therefore, many queries that rely on replication group information will fail.

Back to the top | Give Feedback

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100

(http://support.microsoft.com/kb/889100/ )

How to obtain the latest service pack for Windows Server 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must be running Windows Server 2003 R2 to install this hotfix.

Restart requirement

To avoid restarting the computer, you must stop the DFS Replication service before you apply this hotfix. Then, start the DFS Replication service after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, x86-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Dfsr.exe	5.2.3790.2791	1,696,768	13-Sep-2006	09:57	x86	SP1

Windows Server 2003, x64-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Dfsr.exe	5.2.3790.2791	3,580,928	13-Sep-2006	18:42	x64

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

Back to the top | Give Feedback