Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 705
  • Last Modified:

SharePoint 2010 Ghost Document Can't Delete

I have a document that I can't delete in a plain document library. Not Declared, Not a Permission problem. I have about 305 documents in the library and only one of them I can't check out, edit, open, or delete. I have used SP Manager and can't delete that way either (error - Unhandled exception has occurred in your application.) On the Metadata that seems to be corrupted is says FirstUniqueAncestor - Cannot complete this action. Please try again. When I try to edit them I get an Error - Property accessor 'FirstUniqueAncestor' on object 'Microsoft.SharePoint.SPListItem' threw the following excemption: 'Cannot complete this action. Any suggestion on how to delete the file would help, Powershell, STSADM anything.
0
JMayhair9195
Asked:
JMayhair9195
  • 4
  • 3
1 Solution
 
Jamie McAllister MVPSharePoint ConsultantCommented:
Create a folder in the library, move it into the folder then delete the folder.

If that fails look into downloading SharePoint Manager from Codeplex.
0
 
Jamie McAllister MVPSharePoint ConsultantCommented:
0
 
JMayhair9195Author Commented:
Jamie I have already used SP Manager (stated in question), and I can't move the file.
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
JMayhair9195Author Commented:
Thanks but this doesn't help.
0
 
Jamie McAllister MVPSharePoint ConsultantCommented:
Migrate the content to a new library and then delete the library.

Failing that option I daresay you could delete it via manipulation of the Content Database, but it's unsupported and I would never actually recommend it to anyone in production unless there was really no other way to save the day from a serious issue.

It's a technique I've had to use myself when a bug corrupted the backend information and the UI and scripts then couldn't help. I detailed my escapades here;
http://the-north.com/sharepoint/post/2008/08/29/Techniques-to-use-when-Variations-Attack!.aspx

But like I say, it's unsupported and I'm not suggesting it. It's simply the only other thing I can think of.
0
 
JMayhair9195Author Commented:
The resolution was to install SharePoint 2010 March 2012 CU.
0
 
JMayhair9195Author Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now