Discussion:
Cannot access DFS Replication performance counters
(too old to reply)
C***@googlemail.com
2007-06-26 13:31:35 UTC
Permalink
Hi,

I have DFS-R set up between a Windows Server 2003 Enterprise Edition
R2 in German with SP2 and a Windows 2003 Storage Server R2 x64 English
with SP2.

The initial replication seems to work, the staging area is filling,
files are replicated from the primary member (the Storage Server).

But the DFS-Replication event log on the Enterprise Edition Server
(named XXXXX here) shows no activity at all in the last 24 hours,
although I set up DFS-R only 5 hours ago. The Storage server says
something like "The DFS Replication service successfully established
an inbound connection with partner XXXXX for replication group
corp.abcde.xy\software\betriebssysteme. "

The Replication Health Report shows this:

Cannot access DFS Replication performance counters.
Affected replicated folders: All replicated folders on this server.
Description: The DFS Replication service is unable to access the
performance counter DFS - replizierte Ordner(Betriebssysteme-{83D42CDA-
F17D-4025-B92C-A27D45F13C74})\Erfolgreiche Dateiinstallationsversuche
on XXXXX. Performance data is unavailable. Error ID: 0xc0000bdb.
Last occurred: Dienstag, 26. Juni 2007 at 13:48:06 (GMT1:00)
Suggested action: For information about troubleshooting this
problem, see .

Cannot access DFS Replication performance counters.
Affected replicated folders: All replicated folders on this server.
Description: The DFS Replication service is unable to access the
performance counter DFS - replizierte Ordner(Betriebssysteme-{83D42CDA-
F17D-4025-B92C-A27D45F13C74})\Größe der empfangenen Dateien on XXXXX.
Performance data is unavailable. Error ID: 0xc0000bdb.
Last occurred: Dienstag, 26. Juni 2007 at 13:48:06 (GMT1:00)
Suggested action: For information about troubleshooting this
problem, see .

I found an older KB article on this issue, but don't want to install
the hotfix, the dfsrhelper.dll version on the machines is much newer
than the one in the hotfix.

Any suggestions?

By the way: I already had to install the hotfix from KB919633 and
installed KB931685 on both servers.

Any help appreciated!

Chris
Ned Pyle [MSFT]
2007-06-27 23:45:36 UTC
Permalink
The event logs won't have much to say until initial replication is done (you
will receive 4112 upstream for initial sync, then a 4102 downstream for
initial repl start, then a 4104 downstream for initial repl finished. I
suggest running (from a CMD prompt as an admin):

wmiadap /f

(this will fix up any Perf Counter issues; it will not return anything to
the console).

Then you can use PERFMON.EXE to monitor the actual live replication
situation. Here's a long, boring read on all the perf counters and what they
mean; hopefully that will help understand what the data is saying:

DFS Replication Performance Objects:
====================================

- DFS Replicated Folders
- DFS Replication Connections
- DFS Replication Service Volumes

DFS Replicated Folders Counters:
================================

- Bandwidth Savings Using DFS Replication

Bandwidth Savings Using DFS Replication shows the percentage of bandwidth
that was
saved by the DFS Replication service for this replicated folder using a
combination of remote differential compression (RDC) and other compression
technologies that minimize network bandwidth. For example, a value of 20
indicates
that the DFS Replication service used 20% less bandwidth than it would have
used if
it had transmitted the entire files uncompressed over the network.

- Compressed Size of Files Received

Compressed Size of Files Received shows the compressed size (in bytes) of
files
received for this replicated folder.

- Conflict Bytes Cleaned up

Conflict Bytes Cleaned up shows the total size (in bytes) of the conflict
loser
files and folders that were deleted from the Conflict and Deleted folder by
the
DFS Replication service. The DFS Replication service automatically detects
and
resolves conflicts encountered in replicated folders and moves the losing
version
to the Conflict and Deleted folder. The service automatically cleans up the
Conflict and Deleted folder when it exceeds a pre-configured threshold of
the
quota.

- Conflict Bytes Generated

Conflict Bytes Generated shows the total size (in bytes) of the files and
folders
in this replicated folder that were moved to the Conflict and Deleted folder
by
the DFS Replication service. The DFS Replication service automatically
detects and
resolves conflicts encountered in replicated folders and moves the losing
version
to the Conflict and Deleted folder. The service automatically cleans up the
Conflict and Deleted folder when it exceeds a pre-configured threshold of
the
quota.

- Conflict Files Cleaned up

Conflict Files Cleaned up shows the number the conflict loser files and
folders
that were deleted from the Conflict and Deleted folder by the DFS
Replication
service. The DFS Replication service automatically detects and resolves
conflicts
encountered in replicated folders and moves the losing version to the
Conflict and
Deleted folder. The service automatically cleans up the Conflict and Deleted
folder
when it exceeds a pre-configured threshold of the quota.

- Conflict Files Generated

Conflict Files Generated shows the number of files and folders in this
replicated
folder that were moved to the Conflict and Deleted folder by the DFS
Replication
service. The DFS Replication service automatically detects and resolves
conflicts
encountered in replicated folders and moves the losing version to the
Conflict and
Deleted folder. The service automatically cleans up the Conflict and Deleted
folder
when it exceeds a pre-configured threshold of the quota.

- Conflict Folder Cleanups Completed

Conflict Folder Cleanups Completed shows the number of times conflict loser
files
and folders in the Conflict and Deleted folder were deleted by the DFS
Replication
service. The DFS Replication service automatically detects and resolves
conflicts
encountered in replicated folders and moves the losing version to the
Conflict and
Deleted folder. The service automatically cleans up the Conflict and Deleted
folder
when it exceeds a pre-configured threshold of the quota.

- Conflict Space In Use

Conflict Space in Use shows the total size (in bytes) of the conflict loser
files
and folders currently in the Conflict and Deleted folder used by the DFS
Replication service. The DFS Replication service automatically detects and
resolves
conflicts encountered in replicated folders and moves the losing version to
the
Conflict and Deleted folder. The service automatically cleans up the
Conflict and
Deleted folder when it exceeds a pre-configured threshold of the quota.

- Deleted Bytes Cleaned up

Deleted Bytes Cleaned up shows the total size (in bytes) of replicating
deleted
files and folders (in bytes) that were cleaned up from the Conflict and
Deleted
folder by the DFS Replication service. The service automatically cleans up
the
Conflict and Deleted folder when it exceeds a pre-configured threshold of
the
quota.

- Deleted Bytes Generated

Deleted Bytes Generated shows the total size (in bytes) of replicated
deleted files
and folders that were moved to the Conflict and Deleted folder after they
were
deleted from a replicated folder on a sending member. The DFS Replication
service
automatically cleans up the Conflict and Deleted folder when it exceeds a
pre-configured threshold of the quota.

- Deleted Files Cleaned up

Deleted Files Cleaned up shows the number of replicated deleted files and
folders
that were cleaned up from the Conflict and Deleted folder by the DFS
Replication
service. The service automatically cleans up the Conflict and Deleted folder
when
it exceeds a pre-configured threshold of the quota.

- Deleted Files Generated

Deleted Files Generated shows the number of replicated deleted files and
folders
that were moved to the Conflict and Deleted folder after they were deleted
from a
replicated folder on a sending member. The DFS Replication service
automatically
cleans up the Conflict and Deleted folder when it exceeds a pre-configured
threshold of the quota.

- Deleted Space In Use

Deleted Space in Use shows the total size (in bytes) of the deleted files
and
folders currently in the Conflict and Deleted folder used by the DFS
Replication
service. The DFS Replication service detects remote deletes from its sending
partner and moves the file or folder to the Conflict and Deleted folder. The
service automatically cleans up the Conflict and Deleted folder when it
exceeds a
pre-configured threshold of the quota.

- File Installs Retried

File Installs Retried shows the number of file installs that are being
retried due
to sharing violations or other errors encountered when installing the files.
The
DFS Replication service replicates staged files into the staging folder,
uncompresses them in the Installing folder, and renames them to the target
location. The second and third steps of this process are known as installing
the
file.

- File Installs Succeeded

File Installs Succeeded shows the number of files that were successfully
received
from sending members and installed locally on this server. The DFS
Replication
service replicates staged files into the staging folder, uncompresses them
in the
Installing folder, and renames them to the target location. The second and
third
steps of this process are known as installing the file.

- RDC Bytes Received

RDC Bytes Received shows the number of bytes that were received in
replicating
files using remote differential compression (RDC) for this replicated
folder. This
is the actual bytes received over the network without the networking
protocol
overhead.

- RDC Compressed Size of Files Received

RDC Compressed Size of Files Received shows the compressed size (in bytes)
of the
files received with remote differential compression (RDC) for this
replicated
folder. This is the number of bytes that would have been received had RDC
not been
used. This is not the actual bytes received over the network.

- RDC Number of Files Received

RDC Number of Files Received shows the number files that were received for
this
replicated folder.

- RDC Size of Files Received

RDC Size of Files Received shows the uncompressed size (in bytes) of the
files
received with remote differential compression (RDC) for this replicated
folder.
This is the number of bytes that would have been received had neither
compression
nor RDC been used. This is not the actual bytes received over the network.

- Size of Files Received

Size of Files Received shows the uncompressed size (in bytes) of the files
received
for this replicated folder. This is the number of bytes that would have been
received had DFS Replication compression not been used.

- Staging Bytes Cleaned up

Staging Bytes Cleaned up shows the total size (in bytes) of the files and
folders
that were cleaned up from the staging folder by the DFS Replication service.
The
DFS Replication service stages files and folders in the staging folder
before they
are replicated, and automatically cleans up the staging folder when it
exceeds a
pre-configured threshold of the quota.

- Staging Bytes Generated

Staging Bytes Generated shows the total size (in bytes) of replicated files
and
folders in the staging folder created by the DFS Replication service since
last
restart and is monotonically increasing counter. The DFS Replication service
stages
files and folders in the staging folder before they are replicated, and
automatically cleans up the staging folder when it exceeds a pre-configured
threshold of the quota.

- Staging Files Cleaned up

Staging Files Cleaned up shows the number of files and folders that were
cleaned
up from the staging folder by the DFS Replication service. The DFS
Replication
service stages files and folders in the staging folder before they are
replicated,
and automatically cleans up the staging folder when it exceeds a
pre-configured
threshold of the quota.

- Staging Files Generated

Staging Files Generated shows the number of times replicated files and
folders were
staged by the DFS Replication service. The DFS Replication service stages
files
and folders in a staging folder before they are replicated, and
automatically
cleans up the staging folder when it exceeds a pre-configured threshold of
the
quota.

- Staging Space In Use

Staging Space In Use shows the total size (in bytes) of the files and
folders
currently in the staging folder used by the DFS Replication service. This
counter
will fluctuate as staging space is reclaimed. The DFS Replication service
stages
files and folders in the staging folder before they are replicated, and
automatically cleans up the staging folder when it exceeds a pre-configured
threshold of the quota.

- Total Files Received

Total Files Received shows the number of files that were received by this
replicated folder.

- Updates Dropped

Updates Dropped shows the number of redundant file replication update
records that
were ignored by the DFS Replication service because they did not change the
replicated file or folder. For example, dropped updates can occur when
access
control lists (ACLs) are overwritten with identical ACLs on a file or
folder.

DFS Replication Connections Counters:
=====================================

- Bandwidth Savings Using DFS Replication

Bandwidth Savings Using DFS Replication shows the percentage of bandwidth
that was
saved by the DFS Replication service for this connection using a combination
of
remote differential compression (RDC) and other compression technologies
that
minimize network bandwidth use. For example, a value of 20 indicates that
the DFS
Replication service used 20% less bandwidth than it would have used if it
had
transmitted the entire files uncompressed over the network.

- Bytes Received Per Second

Bytes Received Per Second shows an estimate of the average number of bytes
that
were received each second over the past 30 seconds.

- Compressed Size of Files Received

Compressed Size of Files Received shows the compressed size of files (in
bytes)
received on the connection.

- RDC Bytes Received

RDC Bytes Received shows the bytes that were received on this connection
while
replicating files using remote differential compression (RDC). This is the
actual
bytes received over the network without the networking protocol overhead.

- RDC Compressed Size of Files Received

RDC Compressed Size of Files Received shows the compressed size (in bytes)
of files
received with remote differential compression (RDC) for this connection.
This is
the number of bytes that would have been received had RDC not been used.
This is
not the actual number of bytes received over the network.

- RDC Number of Files Received

RDC Number of Files Received shows the number files that were received on
this
connection.

- RDC Size of Files Received

RDC Size of Files Received shows the uncompressed size (in bytes) of files
received
with remote differential compression (RDC) for this connection. This is the
number
of bytes that would have been received had neither compression nor RDC been
used.
This is not the actual number of bytes received over the network.

- Size of Files Received

Size of Files Received shows the uncompressed size (in bytes) of the files
received
on this connection. This is the number of bytes that would have been
received had
DFS Replication compression not been used.

- Total Bytes Received

Total Bytes Received shows the total number of bytes received on the
connection.
The bytes received value includes file data and replication metadata.

- Total Files Received

Total Files Received shows the number of files that were received on the
connection.

DFS Replication Service Volumes Counters:
=========================================

- Database Commits

Database Commits shows the number of database commit operations performed by
the
DFS Replication service. This counter indicates how intensive the DFS
Replication
service is from a database perspective.

- Database Lookups

Database Lookups shows the number of database search operations performed by
the
DFS Replication service This counter indicates how intensive the DFS
Replication
service is from a database perspective.

- USN Journal Records Accepted

USN Journal Records Accepted shows the number of update sequence number
(USN)
journal records that were processed by the DFS Replication service. The DFS
Replication service processes all USN journal records for replicated content
on a
volume and ignores records for non-replicated files and folders on the
volume.

- USN Journal Records Read

USN Journal Records Read shows the number of update sequence number (USN)
journal
records that were read by the DFS Replication service.

- USN Journal Unread Percentage

USN Journal Unread Percentage shows the percent of the update sequence
number (USN) journal that has not yet been read and processed by the DFS
Replication service. A journal wrap will occur if this counter reaches 100.

=======

Exciting stuff! :)
--
Ned Pyle
Microsoft Enterprise Platform Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Please read http://www.microsoft.com/info/cpyright.htm for more information.


<***@googlemail.com> wrote in message news:***@k79g2000hse.googlegroups.com...
Hi,

I have DFS-R set up between a Windows Server 2003 Enterprise Edition
R2 in German with SP2 and a Windows 2003 Storage Server R2 x64 English
with SP2.

The initial replication seems to work, the staging area is filling,
files are replicated from the primary member (the Storage Server).

But the DFS-Replication event log on the Enterprise Edition Server
(named XXXXX here) shows no activity at all in the last 24 hours,
although I set up DFS-R only 5 hours ago. The Storage server says
something like "The DFS Replication service successfully established
an inbound connection with partner XXXXX for replication group
corp.abcde.xy\software\betriebssysteme. "

The Replication Health Report shows this:

Cannot access DFS Replication performance counters.
Affected replicated folders: All replicated folders on this server.
Description: The DFS Replication service is unable to access the
performance counter DFS - replizierte Ordner(Betriebssysteme-{83D42CDA-
F17D-4025-B92C-A27D45F13C74})\Erfolgreiche Dateiinstallationsversuche
on XXXXX. Performance data is unavailable. Error ID: 0xc0000bdb.
Last occurred: Dienstag, 26. Juni 2007 at 13:48:06 (GMT1:00)
Suggested action: For information about troubleshooting this
problem, see .

Cannot access DFS Replication performance counters.
Affected replicated folders: All replicated folders on this server.
Description: The DFS Replication service is unable to access the
performance counter DFS - replizierte Ordner(Betriebssysteme-{83D42CDA-
F17D-4025-B92C-A27D45F13C74})\Größe der empfangenen Dateien on XXXXX.
Performance data is unavailable. Error ID: 0xc0000bdb.
Last occurred: Dienstag, 26. Juni 2007 at 13:48:06 (GMT1:00)
Suggested action: For information about troubleshooting this
problem, see .

I found an older KB article on this issue, but don't want to install
the hotfix, the dfsrhelper.dll version on the machines is much newer
than the one in the hotfix.

Any suggestions?

By the way: I already had to install the hotfix from KB919633 and
installed KB931685 on both servers.

Any help appreciated!

Chris
C***@googlemail.com
2007-07-02 10:05:44 UTC
Permalink
Post by Ned Pyle [MSFT]
The event logs won't have much to say until initial replication is done (you
will receive 4112 upstream for initial sync, then a 4102 downstream for
initial repl start, then a 4104 downstream for initial repl finished. I
Unfortunately the DFS-Replication event log still shows NOTHING - for
6 days now. In the meantime replication works fine, initial
replication has finished and we have created new replication groups.
The other replication partner logs everything as expected.
What permissions could be wrong?

And for the replication counters: I can access all of them manually
(with Perfmon.exe), no problem. But the DFS-R report still shows the
error message with "cannot access dfs-replication performance
counters".

The server used to be a stand-alone file server in a workgroup and was
recently added to a domain and promoted as a domain controller. DFS-R
was installed afterwards. Maybe this information helps.
Post by Ned Pyle [MSFT]
wmiadap /f
(this will fix up any Perf Counter issues; it will not return anything to
the console).
Then you can use PERFMON.EXE to monitor the actual live replication
situation. Here's a long, boring read on all the perf counters and what they
...
C***@googlemail.com
2007-07-02 10:30:03 UTC
Permalink
Fixed the replication event log issue. now it is just the Perf
Counters....
Post by C***@googlemail.com
Post by Ned Pyle [MSFT]
The event logs won't have much to say until initial replication is done (you
will receive 4112 upstream for initial sync, then a 4102 downstream for
initial repl start, then a 4104 downstream for initial repl finished. I
Unfortunately the DFS-Replication event log still shows NOTHING - for
6 days now. In the meantime replication works fine, initial
replication has finished and we have created new replication groups.
The other replication partner logs everything as expected.
What permissions could be wrong?
And for the replication counters: I can access all of them manually
(with Perfmon.exe), no problem. But the DFS-R report still shows the
error message with "cannot access dfs-replication performance
counters".
The server used to be a stand-alone file server in a workgroup and was
recently added to a domain and promoted as a domain controller. DFS-R
was installed afterwards. Maybe this information helps.
Post by Ned Pyle [MSFT]
wmiadap /f
(this will fix up any Perf Counter issues; it will not return anything to
the console).
Then you can use PERFMON.EXE to monitor the actual live replication
situation. Here's a long, boring read on all the perf counters and what they
...
Ned Pyle [MSFT]
2007-07-03 21:34:57 UTC
Permalink
Verify the permissions on these two registry keys:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib

and

HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

They should be (by default):

Administrators - Full Control
Creator Owner - Special
Local Service - Read
Network Service - Read
Performance Log Users - Read
Performance Monitor Users - Read
System - Full Control
--
Ned Pyle
Microsoft Enterprise Platform Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Please read http://www.microsoft.com/info/cpyright.htm for more information.
Post by C***@googlemail.com
Fixed the replication event log issue. now it is just the Perf
Counters....
Post by C***@googlemail.com
Post by Ned Pyle [MSFT]
The event logs won't have much to say until initial replication is done (you
will receive 4112 upstream for initial sync, then a 4102 downstream for
initial repl start, then a 4104 downstream for initial repl finished. I
Unfortunately the DFS-Replication event log still shows NOTHING - for
6 days now. In the meantime replication works fine, initial
replication has finished and we have created new replication groups.
The other replication partner logs everything as expected.
What permissions could be wrong?
And for the replication counters: I can access all of them manually
(with Perfmon.exe), no problem. But the DFS-R report still shows the
error message with "cannot access dfs-replication performance
counters".
The server used to be a stand-alone file server in a workgroup and was
recently added to a domain and promoted as a domain controller. DFS-R
was installed afterwards. Maybe this information helps.
Post by Ned Pyle [MSFT]
wmiadap /f
(this will fix up any Perf Counter issues; it will not return anything to
the console).
Then you can use PERFMON.EXE to monitor the actual live replication
situation. Here's a long, boring read on all the perf counters and what they
...
C***@googlemail.com
2007-07-05 12:00:04 UTC
Permalink
Post by Ned Pyle [MSFT]
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib
and
HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
Administrators - Full Control
Creator Owner - Special
Local Service - Read
Network Service - Read
Performance Log Users - Read
Performance Monitor Users - Read
System - Full Control
--
Ned Pyle
Microsoft Enterprise Platform Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Please readhttp://www.microsoft.com/info/cpyright.htmfor more information.
Post by C***@googlemail.com
Fixed the replication event log issue. now it is just the Perf
Counters....
Post by C***@googlemail.com
Post by Ned Pyle [MSFT]
The event logs won't have much to say until initial replication is done (you
will receive 4112 upstream for initial sync, then a 4102 downstream for
initial repl start, then a 4104 downstream for initial repl finished. I
Unfortunately the DFS-Replication event log still shows NOTHING - for
6 days now. In the meantime replication works fine, initial
replication has finished and we have created new replication groups.
The other replication partner logs everything as expected.
What permissions could be wrong?
And for the replication counters: I can access all of them manually
(with Perfmon.exe), no problem. But the DFS-R report still shows the
error message with "cannot access dfs-replication performance
counters".
The server used to be a stand-alone file server in a workgroup and was
recently added to a domain and promoted as a domain controller. DFS-R
was installed afterwards. Maybe this information helps.
Post by Ned Pyle [MSFT]
wmiadap /f
(this will fix up any Perf Counter issues; it will not return anything to
the console).
Then you can use PERFMON.EXE to monitor the actual live replication
situation. Here's a long, boring read on all the perf counters and what they
...- Zitierten Text ausblenden -
- Zitierten Text anzeigen -
Excellent - that did it! Works fine now.
I have no clue why the permissions were totally different.
Ned Pyle [MSFT]
2007-07-05 23:01:06 UTC
Permalink
Me neither! :-P

Glad to hear it, have a great week.
--
Ned Pyle
Microsoft Enterprise Platform Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Please read http://www.microsoft.com/info/cpyright.htm for more information.
Post by C***@googlemail.com
Post by Ned Pyle [MSFT]
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib
and
HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
Administrators - Full Control
Creator Owner - Special
Local Service - Read
Network Service - Read
Performance Log Users - Read
Performance Monitor Users - Read
System - Full Control
--
Ned Pyle
Microsoft Enterprise Platform Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Please readhttp://www.microsoft.com/info/cpyright.htmfor more
information.
Post by C***@googlemail.com
Fixed the replication event log issue. now it is just the Perf
Counters....
Post by C***@googlemail.com
Post by Ned Pyle [MSFT]
The event logs won't have much to say until initial replication is
done
(you
will receive 4112 upstream for initial sync, then a 4102 downstream for
initial repl start, then a 4104 downstream for initial repl finished. I
Unfortunately the DFS-Replication event log still shows NOTHING - for
6 days now. In the meantime replication works fine, initial
replication has finished and we have created new replication groups.
The other replication partner logs everything as expected.
What permissions could be wrong?
And for the replication counters: I can access all of them manually
(with Perfmon.exe), no problem. But the DFS-R report still shows the
error message with "cannot access dfs-replication performance
counters".
The server used to be a stand-alone file server in a workgroup and was
recently added to a domain and promoted as a domain controller. DFS-R
was installed afterwards. Maybe this information helps.
Post by Ned Pyle [MSFT]
wmiadap /f
(this will fix up any Perf Counter issues; it will not return
anything
to
the console).
Then you can use PERFMON.EXE to monitor the actual live replication
situation. Here's a long, boring read on all the perf counters and
what
they
...- Zitierten Text ausblenden -
- Zitierten Text anzeigen -
Excellent - that did it! Works fine now.
I have no clue why the permissions were totally different.
Continue reading on narkive:
Loading...