DFS Causing stop error with Windows Server 2003 R2 Standard
Posted on 2009-04-13
I have a problem currently with a server which we have just attempted to enable DFS replication on. Everything checks out as far as diagnostics within the DFS console goes, but once replication attempts to start the server blue screen with a stop error :
Reason Code: 0x805000f
I have tried both continuous replication and scheduled replication, and this stop error occurs almost on the hour while a replication pair is configured. I have also tried creating a namespace and doing the replication though this and the same occurs.
Removing the replication pair stops the blue screen . I have uninstalled and reinstalled DFS, updated the nic drivers to the latest, turned off Antivirus and have had no luck.
I have checked communication between the 2 servers which I created the replication pair with and there are no problems. Both servers are R2 , and both have been updated to the latest patches and hotfixes.
The primary server has GC , AD, DNS, DHCP and Exchange running on it plus MSDE for an sql database which is hosted on the server. The Secondary server also has GC and AD, DNS, DHCP and MSDE for an SQL Database .
The servers are linked via a VPN, and AD replication is working fine, no unusual events are logged in the event logs. For all intents and purposes these servers are stable and running perfectly aside from this DFS problem , which happens to be of critical importance.
I have searched online for any assistance related to this but have not found anything which could explain and assist me in recitfying the issue without a full reload of the server in question.
In a process of elimination I have determined that the fault is definately with the primary server, as I have setup test replication between the secondary server and a test share on one of our R2 Terminal servers and that replicates fine.