Share via


Server 2008 - DFS Replication - Local Path "Not Defined"

Question

Wednesday, May 18, 2011 7:48 PM

Hello,

We are trying to setup a DFS replication on a server 2008 server and we are getting Local Path Not Defined status. When we initially added the member it gave us an error indicating target folder already exists.

History: We had a 2003 server named testfs01 which was setup with DFS replication for 5 folders. We renamed testfs01 to testfs01-old. We built a new 2008 server and named it testfs01. When we tried adding the new server as a member in the replication group for the specific folders it gave an error indicating target folder already exists. We realized that testfs01-old was still publishing shares as testfs01. We removed testfs01-old from DFS. After removing testfs01-old, we were able to add testfs01 as a new member but this time 4 folders worked and 1 folder did not work.

Current: 4 folders on testfs01 are replicating without issues. but 1 folder indicates local path as not defined. The warning icon indicates Object does not exist on domain controller possibly due to active directory domain services replication latency. We are not sure how to resolve issues with this folder. We think somewhere in AD its still getting published using the old server but not sure how to clean it up.

Any help will be greatly appreciated.

All replies (5)

Wednesday, May 25, 2011 1:54 AM ✅Answered

Hi,

Have a look at the DFSR settings in AD. Check if the old information still exists there. The picture in this thread can help show the location:

http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/a7724837-b80a-436b-89df-97bb189bcecc

If it cannot help then you may have a try to clear the replication group information and create a new one as a workaround step.

Shaon Shan |TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]


Thursday, May 19, 2011 12:14 AM

Hi milan7777,

The <Not Defined> in Local path column means that the local path of the replicated content is not well configured on the Member server. I think you may need to check to verify that the DFS share folder is well setup and configured on that member server as the DFS Management console indicates.

Meanwhile, how many domain controllers in your domain? Do they keep in sync when the issue occurs?
 
Please run "repadmin syncall" command to synchronize all the domain controller’s database to prevent the AD lantency issue. And  then open the DFS management console to see if it helps.

Hope it helps.

Thanks and Regards
Scorpio_Milo
MCTS: Windows Vista | Exchange Server 2007
MCITP: Enterprise Support Technician
MCITP: Server & Enterprise Administrator
Microsoft Infrastructure Consultant
Enterprise Service: Solution Architect
Microsoft Storage Team - File Cabinet Blog
My Blog
Contact me


Friday, May 20, 2011 9:46 PM

We are using DFS on file servers and not domain controllers. We have not experienced any replication issues. I have confirmed that the folder is shared out properly on the member server.


Sunday, May 22, 2011 3:39 AM

Hi Milan,

I understand you are using DFS on file servers, please be awared that DFS metadata information will be saved in AD database. To prevent the legacy replication issue causing not reflect in AD, Please run "repadmin syncall" command as a trial.

Thanks for co-operation.

Thanks and Regards
Scorpio_Milo
MCTS: Windows Vista | Exchange Server 2007
MCITP: Enterprise Support Technician
MCITP: Server & Enterprise Administrator
Microsoft Infrastructure Consultant
Enterprise Service: Solution Architect
Microsoft Storage Team - File Cabinet Blog
My Blog
Contact me


Monday, May 23, 2011 7:06 PM

Hello,

repadmin /syncall completed without any errors. Still getting the warning for Path Not Defined in DFS Management. 

Thank You,