SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I ran a stsadm -o enumsites and received 2 error messages in the output. It generates the error: The system cannot find the path specified. (Exception from HRESULT: 0x80070003). I know the URL of one of the site collections from doing some web part testing.

I cannot trace down the other site collection. enumallwebs shows nothing for the one collection I know of. The sites do not show up as orphaned.

I'm at a loss as to how to identify these sites and remove them from the configuration database I presume.

share|improve this question
I've tried everything in this MSDN post and the issue still persists, the symptoms seem identical.… – Eric Alexander Nov 23 '10 at 19:20
up vote 1 down vote accepted

Ok, I found out what the issue was. The site was a particularly large site restore that was deleted from the web ui in our test farm. I believe the delete timed out and left a bit of bad data hanging out in the SiteMap table.

This blog post lead me to finding where the particular site collection was located. Once I had that content database isolated, I deleted it from Central Administration and and added it back into the farm as described here. This cleaned up the corrupted sites.

share|improve this answer

What happens if you write a console app to iterate through the site collections? Could try identifying and removing it that way...

share|improve this answer
I don't any C# to do that, I'm not a dev by trade. – Eric Alexander Nov 9 '10 at 17:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.