Description
After configuring and starting MOSS Search, you wish to have a clean configuration. Maybe the indexing process doesn't seem to be working correctly. Or, perhaps there are issues with the propogated index share folder. Or, maybe the crawler doesn't seem to complete its process. Or, maybe the first time around you forgot about your database naming convention and you want to rename the search database to something more relevant. Whatever the issue or reason, the solution below offers a way to gain a fresh start with MOSS search configuration. This solution creates a new search database, it clears the index and propogated index file shares and creates new ones.
Solution
From each of the search servers
* Start > Run > CMD
* net stop osearch
From each of the query servers
* Central Admin > Services on Server
* Stop/Remove MOSS Search (query) from each of the query search servers
From the index server
* Central Admin > Services on Server
* Stop/Remove MOSS search (index)
From the index server
* Central Admin > Services on server
* Note the database name
* Stop/Remove WSS search
From the index server
* Central Admin > Services on server
* Start/Add the WSS Search (this requires creating a new db)
From the index server
* Central Admin > Services on server
* Start/Add the MOSS Search (select only the index checkbox)
From each of the query servers
* Central Admin > Services on server
* Start/Add MOSS Search (select only the query checkbox)
From the SSP
* SSP Admin > User Profiles
* Verify that user profiles have been imported
From the SSP
* SSP Admin > Search Settings
* Verify all content sources, crawl rules, schedules, scopes are configured properly
* Perform a full crawl of content
Concepts: Information Architecture, Knowledge Management, Portals, Enterprise Search, Collaboration, Extranets, Intranets, Business Intelligence, Business Process Automation, ECM, Records Management, CRM, ERP, Mobile, Web
Approach: Project Management, Business Analysis, Strategy, Design, Development, Implementation
Technologies: Microsoft SharePoint, Office 365, Azure, SQL Server, Windows, HTML5, CSS, JavaScript, ASP.NET
Monday, May 21, 2007
SharePoint Error: Service Unavailable
Description:
Users receive "Service Unavailable" error when they point their browsers at the SharePoint site
Solution:
* Administrative Tools > Services > SQL Server Service > Log On Tab
Set the identity to a domain user account
Restart the service
* IIS Manager > Application Pools > Application Pool Properties > Identity Tab
Set the identity to a domain user account (e.g. use same as sql server service account)
* Start > Run > IISReset
See Also:
Microsoft Support KB973917: Description of the update that implements Extended Protection for Authentication in Internet Information Services (IIS) http://support.microsoft.com/kb/973917
Users receive "Service Unavailable" error when they point their browsers at the SharePoint site
Solution:
* Administrative Tools > Services > SQL Server Service > Log On Tab
Set the identity to a domain user account
Restart the service
* IIS Manager > Application Pools > Application Pool Properties > Identity Tab
Set the identity to a domain user account (e.g. use same as sql server service account)
* Start > Run > IISReset
See Also:
Microsoft Support KB973917: Description of the update that implements Extended Protection for Authentication in Internet Information Services (IIS) http://support.microsoft.com/kb/973917
SharePoint V3: MOSS 2007 People Search Scope, 0 Items
Description:
MOSS 2007 Search is configured but the People scope contains zero items.
Solution:
* SSP Admin > User Profiles and Properties
Verify that user profiles have been imported by looking at the number of profiles
* SSP Admin > Search Settings > Scopes > Scope Properties and Rules
Delete existing rules
Create a new rule where contentclass = urn:content-class:SPSPeople
Set the new rule behavior to "Require"
* SSP Admin > Search Settings > Scopes
Start Update Now
MOSS 2007 Search is configured but the People scope contains zero items.
Solution:
* SSP Admin > User Profiles and Properties
Verify that user profiles have been imported by looking at the number of profiles
* SSP Admin > Search Settings > Scopes > Scope Properties and Rules
Delete existing rules
Create a new rule where contentclass = urn:content-class:SPSPeople
Set the new rule behavior to "Require"
* SSP Admin > Search Settings > Scopes
Start Update Now