Link to home
Start Free TrialLog in
Avatar of Josh Price
Josh PriceFlag for United States of America

asked on

SharePoint 2013 Search will not delete old site collection, does not crawl new web in its place

I removed a content database from a web application last week that contained a single site collection at the explicit managed path '/sites/site1'.

1.

I removed the database through Central Admin in Manage Content Databases.

2.

I removed the managed path from the web application.

3.

I then proceeded to create an SPWeb object at '/sites/site1' using New-SPWeb.

4.

I imported an entirely different set of content from another farm using Import-SPWeb.The content is there and it's magical and perfect.

The problem: all search crawls since this point have failed to recognize that the old site collection is gone. In fact, it continues to crawl it as though it were there, but instead of marking the pages it cannot find as deleted, it logs an error that the object is not found. Furthermore, the content in the new SPWeb is not crawled at all, but it's displayed to users properly. This acts as though it hasn't acknowledged the removal of the Managed Path and/or site collection and/or content database.

The site collection that was removed did have Site Map settings configured, so I'm wondering if that needs to be de-registered from the timer job. Otherwise, I don't really know what to look into and I need to get this site in the search index very soon.

You guys have always been helpful, so I'm hoping another win is in my future here...

Thanks!
ASKER CERTIFIED SOLUTION
Avatar of Walter Curtis
Walter Curtis
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Josh Price

ASKER

This was ultimately what I had to do. I was trying to avoid it so that I could avoid any site downtime, but it's the way to go. Thanks!
Thanks, glad that helped!