Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

2012 server - orphaned DFS share can't be deleted

Posted on 2014-04-30
10
3,061 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 36

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
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
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 36

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

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

I was asked if I could set up a fax machine so that incoming faxes were delivered to people's Exchange inboxes and so that they could send faxes from their desktops without needing to print the document first.  I knew it was possible but I had no id…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

808 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