Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

2012 server - orphaned DFS share can't be deleted

Posted on 2014-04-30
10
Medium Priority
?
4,828 Views
Last Modified: 2014-11-23
I need to manually delete, remove, clean up an orphaned DFS name.

I have a folder shared as \\server\data
At one time, it was also a DFS share called \\mydomain.com\data

I cannot delete/remove the share name.  I get:

“An error occurred while trying to delete the share %sharename%. The share must be removed from the Distributed File System before it can be deleted.”

The problem is - it *doesn't* exist in DFS.  
I've checked ADSIEDIT, as mentioned in countless articles.  The namespace DOES NOT EXIST in this location.

I can remove it from "display" in DFS Management, but if I go to add a namespace to display, it shows me "\\mydomain.com\data" as a valid name to add.

I can't re-add the namespace because it says it already exists.  I can't delete it because it says it doesn't exist!!

HELP!
0
Comment
Question by:snowdog_2112
  • 6
  • 2
  • 2
10 Comments
 
LVL 29

Expert Comment

by:becraig
ID: 40033625
Have you tried checking the registry to see if the namespace is persisting there :
http://cscmblog.blogspot.com/2012/06/distributed-file-system-error-share.html



This might be your issue since you indicate you cannot find the namespace in AD

Please check the registry value at:
HKLM\Software\Microsoft\Dfs\Roots\Domain
0
 
LVL 38

Expert Comment

by:Mahesh
ID: 40035445
0
 

Author Comment

by:snowdog_2112
ID: 40035744
I see an entry in the registry - waiting for after-hours window to attempt whacking it.

Will report back.  Thanks.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 29

Expert Comment

by:becraig
ID: 40066259
Did you have any luck with this ?
0
 

Author Comment

by:snowdog_2112
ID: 40067775
No luck.  The registry setting was there, and we removed it, rebooted and still can't delete the share tied to the phantom DFS namespace.

Still, if a user saves to a *SUB-FOLDER* of the drive letter mapped to the \\SERVER\share (note: not the DFS sharename \\domain\share), the file is saved to the root of the drive letter with now indication to the user - no error, no warning.  Even more strange...only Office applications exhibit this behavior, not something like Notepad.

Any other thoughts?

Meantime, I've created a new share to the same folder and have users mapped to the new share name via GPO.  File saving to the new share name via mapped drive letter works as expected.
0
 
LVL 38

Expert Comment

by:Mahesh
ID: 40067919
Are you able to view DFS object under \\domain.com\system\dfs-global-configuration folder or any other DFS folders under system container ?
If you found one just delete it
Also try to find share under below registry key
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Shares]
If  Under shares you find share pointing to your DFS root share, just delete that one.
Now restart server service on server and force AD replication

Now try to create DFS name space again
 
Mahesh
0
 

Author Comment

by:snowdog_2112
ID: 40075015
I will give that a try at the next maintenance window opportunity and report back.
0
 

Author Comment

by:snowdog_2112
ID: 40406909
I've deleted the registry key and every place I can find the name, but it still will not let me remove the share name due to a non-existent DFS name.

Are there any other options I have?  Spin up a new DC, attach the disk from this busted DC and create the shares on a new DC?  At the same time, create a "dummy" disk for the busted DC with the same folder?
0
 

Accepted Solution

by:
snowdog_2112 earned 0 total points
ID: 40450094
Abandoning this - no solutions found.

I've created a new folder and new share and migrated all mappings to the new share.

The orphaned DFS sapce will forever remain in this network apparently.
0
 

Author Closing Comment

by:snowdog_2112
ID: 40460426
No solution - had to workaround/replace the share name.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…

885 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question