Why Experts Exchange?
Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.
Jim Murphy
Programmer at Smart IT Solutions
When asked, what has been your best career decision?
Deciding to stick with EE.
Mohamed Asif
Technical Department Head
Being involved with EE helped me to grow personally and professionally.
Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question
Connect with Certified Experts to gain insight and support on specific technology challenges including:
Troubleshooting
Research
Professional Opinions
Ask a QuestionDid You Know?
We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE
I am running DFS in my environment and I have run up against a problem. I have four servers: WSCALFS, FARM1, FARM2, and FARM3.
WSCALFS is not working properly anymore: The DFS Replication service stopped replication on volume G:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume N:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume U:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The biggest problem with this is that some people have been working off WSCALFS and some people have been working off the shared replication server.
I found an article about recovering from this problem, making the crashed server the primary server, but I am not sure that that is what I want to do. https://support.microsoft.com/en-us/help/961879/how-to-recover-from-a-dfsr-database-crash-on-designated-primary-member
Any advice?
WSCALFS is not working properly anymore: The DFS Replication service stopped replication on volume G:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume N:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The DFS Replication service stopped replication on volume U:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
The biggest problem with this is that some people have been working off WSCALFS and some people have been working off the shared replication server.
I found an article about recovering from this problem, making the crashed server the primary server, but I am not sure that that is what I want to do. https://support.microsoft.com/en-us/help/961879/how-to-recover-from-a-dfsr-database-crash-on-designated-primary-member
Any advice?
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.