DFS was configured and working fine on Server 2008 STD, but now it's no longer replicating. Here are some of the errors I am seeing:

---------------------------------------------------------------------------------------
- Due to the following error, the DFS Replication reporting mechanism cannot access the WMI (Windows Management Instrumentation) namespace to retrieve certain reporting information. Error ID: 0x80041002.

- DFS Replication cannot replicate with partner <server name> for replication group <domain>\<name space>\<share>. The partner did not recognize the connection or the replication group configuration. The DFS Replication service used partner DNS name <server name>, IP address <the server ip>, and WINS address <server name> but failed with error ID: 9026 (The connection is invalid). Event ID: 5012

AND

- The DFS Replication service is stopping communication with partner <server name> for replication group Domain System Volume due to an error. The service will retry the connection periodically.

Additional Information:
Error: 1726 (The remote procedure call failed.)
Connection ID: 580D7FC3-873F-48CC-AFC1-73E96DFADCE2
Replication Group ID: ACA5FC8A-AA2E-4D40-8ECC-3A0A8F45E5F8
---------------------------------------------------------------------------------------

I also have noticed that there is a disabled sysvol in the replication area which belongs to an decommissioned server. Not sure if that would mess anything up or not since it is disabled (and not needed), but I can't get rid of it.

According to the research, the issue maybe occur because the DFS servers do not have the permission to read AD information on themselves or their partners.

1. Please open the ADSIedit.msc console to verify the "Authenticated Users" is set with the default READ permission on the following object:

a. The computer object of the DFS server

b. The DFSR-LocalSettings object under the DFS server computer object

2. After the permissions is set correct, please run "DFSRDIAG POLLAD" to pick up the changes.

Another possible reason is that FSRM is configured as some types of files are blocked from DFS replication. When the DFSR filters are not set to match FSRM screens by extension and the files exist on the server before screening, this can lead to degraded DFSR performance and the files will never replicate.

If possible, please remove file screening and reconfigure it to remove files by extension or set a comparable DFSR filter rule to prevent replication attempts.

Hope it helps.

Hi Rollinz,

Thank you for the knowledge sharing on this issue. The other community members could get benefit from it.

Thanks again.

Thanks Raymond,

Your solution worked for me!

I m still gettting the error. 

- The DFS Replication service is stopping communication with partner <server name> for replication group Domain System Volume due to an error. The service will retry the connection periodically. 
 
Additional Information: 
Error: 1726 (The remote procedure call failed.) 
Connection ID: 580D7FC3-873F-48CC-AFC1-73E96DFADCE2 
Replication Group ID: ACA5FC8A-AA2E-4D40-8ECC-3A0A8F45E5F8

This was verified and its the same on the two DFS servers. 

1. Please open the ADSIedit.msc console to verify the "Authenticated Users" is set with the default READ permission on the following object:

a. The computer object of the DFS server

b. The DFSR-LocalSettings object under the DFS server computer object

2. After the permissions is set correct, please run "DFSRDIAG POLLAD" to pick up the changes.

The below filters are not in use.

Another possible reason... the files exist on the server before screening... and the files will never replicate.

I faced similiar problems with one of my domain controllers that is in the cloud. We were having some networking difficulties with a new cloud server we spun up and contacted our cloud vendor who was attempting to troubleshoot our problem.  

Turns out that the vendor had changed our Windows firewall rules on us and then didn't notify us. So be sure to check your firewall rules as well. 

Once I fixed my firewall rules AD replication started working again.

DFS was configured and working fine on Server 2008 STD, but now it's no longer replicating.  Here are some of the errors I am seeing:

---------------------------------------------------------------------------------------
- Due to the following error, the DFS Replication reporting mechanism cannot access the WMI (Windows Management Instrumentation) namespace to retrieve certain reporting information. Error ID: 0x80041002.

- DFS Replication cannot replicate with partner <server name> for replication group <domain>\<name space>\<share>. The partner did not recognize the connection or the replication group configuration. The DFS Replication service used partner DNS name <server name>, IP address <the server ip>, and WINS address <server name> but failed with error ID: 9026 (The connection is invalid). Event ID: 5012

AND

- The DFS Replication service is stopping communication with partner <server name> for replication group Domain System Volume due to an error. The service will retry the connection periodically.
 
Additional Information:
Error: 1726 (The remote procedure call failed.)
Connection ID: 580D7FC3-873F-48CC-AFC1-73E96DFADCE2
Replication Group ID: ACA5FC8A-AA2E-4D40-8ECC-3A0A8F45E5F8
---------------------------------------------------------------------------------------

I also have noticed that there is a disabled sysvol in the replication area which belongs to an decommissioned server.  Not sure if that would mess anything up or not since it is disabled (and not needed), but I can't get rid of it.

Hi,

I have had a similar issue while setting up DFS Replication and the replication reporting issued the Error ID: 0x80041002 and also Error: 9026 (The connection is invalid).

In my case I was able to resolve it by registering the MicrosoftDFS WMI namespace (I don't know if or why it has been de-registered or somehow stepped on).

Anyway maybe this helps you if you have the same issue

Open a CMD prompt in %windir%\system32\wbem

type mofcomp dfsrprovs.mof

net stop winmgmt
net start winmgmt
net start iphlpsvc
net stop dfsr
net start dfsr

Now it works (for me) and I hope for you !

Raymond

This worked for me. A new installation of 2012R2 running AD DS and DFS was not replicating at all (dfsrdiag replicationstate was coming up empty with 0 active connections) even though everything was showing green status in DFS Management. Later I ran the health report and saw errors on both ends (both DFS partners), finally I realized the dfsrdiag pollad was returning Error ID: 0x80041002 on this new server (was good on partner).

Above procedure fixed it! Thanks!

Thanks Raymond...

It works for me.