MOSS 2007 Search Scope Error --> Query/Index Server Event log Error (HOW TO FIX IT)

  • Article

MOSS Error: In multi Server MOSS 2007 farm environment. You might see Search Scope Count Errors and also Event Log errors on Index/Query server

Possible Cause : Query and Index Servers are not functioning correctly

Symptoms :

View Scope page error:

Search Scope Error

 

Rule

Behavior

Item Count (approximate)

All Content

Include

(all items)

contentclass = urn:content-class:SPSPeople

Exclude

ContentSource = BDCCStarSearch

Include

ContentSource = BDCCStarSearchDelta

Include

ContentSource = BDCCStarSearchCurrent

Include

Application Event Log:

 

 

 

Description:

 

Event Type: Error

Event Source: Office SharePoint Server

Event Category: Office Server Shared Services

Event ID: 6482

Date: 9/26/2007

Time: 10:27:52 PM

User: N/A

Computer: MyServerName

Description:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (09596173-2751-4db9-a84a-920690352eba).

 

Reason: Object b605e66d-073d-4075-ad36-8565cdd48497 not found.

 

Techinal Support Details:

System.Collections.Generic.KeyNotFoundException: Object b605e66d-073d-4075-ad36-8565cdd48497 not found.

   at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()

   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

 

For more information, see Help and Support Center at https://go.microsoft.com/fwlink/events.asp.

 

 

 

Diagnosis : Steps to fix this problem

 

This problem occurs mostly when your Office SharePoint Service Search is not working (or configured correctly). When you follow steps listed here to configure your office SharePoint Service Search, you will most likely loose crawled data in content catalogs if any. You need to re-crawl data source again.

 

1. Stop Office SharePoint Service on all servers (command line option StsAdm.exe -o osearch -action stop)

2. Stop and Start MOSS timer service

3. Start office SharePoint Service Search service on index server first. (my observation is stsadm.exe command line tool works better StsAdm.exe -o osearch -action start -role index)

a. Sometimes you configure Index location on index server (use new location). Use “configure automatically” option and provide domain account which is member of local admin group on the index server (command line option StsAdm.exe -o osearch -defaultindexlocation E:\spsindexdata)

4. Start Office SharePoint Services Search Service on Query Server(s) next. (command line option StsAdm.exe -o osearch -action start -role query)

a. Sometimes you configure Index location on Query server (use new location). Use “configure automatically” option and provide domain account which is member of local admin group on the Query server. (command line option StsAdm.exe -o osearch -propogationlocation d:\spsindexdata)

5. You might want to wait couple of minutes.

6. Edit your Shared Service Provider (SSP) settings. Select Index Server in drop down list. Provide service credentials. Click OK

7. Wait about 10 minutes and check your server again. Check if Scope count Error is gone.

 

This worked for me in two diffent environments