Hello,
Environment: We use two dfs servers which replicate all namespaces and dfs folders between each other. There are two namespaces: Data and Users. First server (DC12) has referrals enabled the second server (DC07) has referrals disabled. This is globally configured across all namespaces and dfs folders. Both servers are Server 2008 R2 Standard x64 OS. Other roles on these servers include AD DS, DNS, and DHCP.
Issue: Within the Data namespace windows explorer location on DC12 (D:\Data\) the folder structure was mysteriously changed for all (9) dfs folders. Dfs folders had “DFS.<DFS SID>” prepended to their folder names and are now no longer accessible. For example: folder previously named “Accounts Receivable” were renamed to “DFS.8c654b7d-0246-4389-ab00-2b1b7027626fAccounts Receivable” within explorer, but are named "Accounts Receivable" within DFS Management. Additionally, there was another, empty dfs folder created in D:\Data\ called “Accounts Receivable”, but when we try to access it from either D:\Data\ or through \\namespace\data we get an error “Location is not available: The network location cannot be reached.”
Background: Our server switch died and replication between DC12 and DC07 was interrupted for about 90 minutes. We replaced the switch and the environment came back online. When testing to confirm network, resource, and LOB functionality, we discovered this issue and have been thus far unsuccessful in resolving.
Associated Event Log Found:
Log Name: DFS Replication
Source: DFSR
Date: 5/14/2014 5:33:16 PM
Event ID: 4004
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DC12
Description:
The DFS Replication service stopped replication on the replicated folder at local path D:\Data\Lab Tech.
Additional Information:
Error: 87 (The parameter is incorrect.)
Additional context of the error:
Replicated Folder Name: Lab Tech
Replicated Folder ID: C6475450-CA1B-4AE2-929A-2C67F5EC79BF
Replication Group Name: schaeffer.com\data\lab tech
Replication Group ID: 478B691D-415F-4788-8D64-41DEBDDB76FD
Member ID: 66B7D8A8-6A93-43B7-844D-DF77AB3EF31F
Troubleshooting Steps Done So Far:
- Restarted DFS Namespace (Dfs), DFS Replication (DFSR), and Netlogon services on both DC12 and DC07
- Renaming folders - folders don't exist error
- Restarted DC12 and DC07
This issue is ONLY isolated to DC12 and ONLY the Data namespace. DC07 and Users namespace works just fine.We ended up having to disable DC12 as a referral target and in replication so that clients were pointing to DC07. I’m hoping that I won’t have to rebuild the Data namespace because it’s massive. Hoping for some guidance on troubleshooting. Thanks for your time.