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!
LVL 1
Josh PriceApplication EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Walter CurtisSharePoint AEDCommented:
One way to correct his may be to delete the search index from Central Administrator and do a full crawl to build a new index.

Hope that helps...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Josh PriceApplication EngineerAuthor Commented:
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!
Walter CurtisSharePoint AEDCommented:
Thanks, glad that helped!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.