My esteemed non-linear creations colleague Amanda Holstrom is in Anaheim at the official SharePoint Conference.
She’s been blogging about the sessions she’s attended, including Microsoft’s Records Management approach, SharePoint Search, and how Telus uses social media to change their educational model.
See Ms. Holstrom’s blog at http://holstrom.blogspot.com.
I am in the process of moving a large Internet-facing website on MOSS 2007 from one hosting company to another. There are three main Web Applications (Apps A, B and C), each served by its own Shared Services Provider (SSP A, etc.). Two of the SSPs have custom search Scopes.
After the Site Collections had been configured and the web content migrated into them, I was finding that any search, in any of the three Site Collections, returned in the error message in the title above.
Web searches turned up a lot of advice on overcoming this ScopeNotFound Exception while developing custom search applications, but this was happening in the out-of-the box search pages.
I found the answer by checking the Associations under Shared Services Administration in SharePoint Central Admin: by accident, all three of the Web Applications had been associated with SSP ‘C’ (the default). I moved App ‘B’ to SSP ‘B’ and so on, and all searches immediately started working.
