Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 5014 Source: DFSR
The DFS Replication service is stopping communication with partner <computer> for replication group <dfs path to folder> due to an error. The service will retry the connection periodically.
Error: <error code> (<error description>)
Connection ID: <guid>
Replication Group ID: <guid2>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is DFS?
The DFS Replication service incorrectly manages the DFSR database. This behavior causes an inconsistent status. See ME943661 for a hotfix applicable to Microsoft Windows Server 2003.
This event appears because the RPC hotfix is not installed on the server. If you run the "Create Diagnostic Report" via DFS Management console, you can click on the errors it finds and see the solution. This is what mine said:
The RPC hotfix is not installed on this server.
Affected replicated folders: All replicated folders on this server.
Description: This hotfix addresses RPC issues that can cause the DFS Replication service to fail, possibly without corresponding failure events in the DFS Replication event log. If the DFS Replication service does not restart automatically, replication backlogs can occur that are not easily attributed to RPC issues. Therefore, we highly recommend that you install this hotfix on all servers participating in DFS Replication.
Now remember that DCs participate in DFS replication so you have to install the hot fix there as well. See ME908521 for the hotfix.
This is a new Event ID for Windows Server 2003 R2 SP1 found in a new DFS Replication log.
- Error: 9033 (The request was cancelled by a shutdown) - Self-explanatory.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (2) - More links...|
Send comments or solutions
- Notify me when updated