SharePoint Search Failing: Application Server job failed for service instance
/* Posted March 20th, 2008 at 11:36am *//* Filed under C#, Microsoft, Programming, SharePoint */
/* */
Was getting this error:
Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (34c9a339-ef4a-454b-a288-812fd2fd1270).
Reason: Index was outside the bounds of the array.
Techinal Support Details:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.SynchronizeDefaultContentSource(IDictionary applications)
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 http://go.microsoft.com/fwlink/events.asp.
Solution:
stsadm -o osearch -action stop
Warning: The Office SharePoint Server Search service that was enabled on this server will uninstall and all index files for all SSPs will be deleted. Are you sure you want to permanently delete all data in the index for all SSPs? [y/n]
NOTE: Only do this if you have not crawled / indexed content that cannot be re-indexed. If this is the case, then you open a support ticket with MSFT and work through it. Otherwise, hit Y
Now issue: stsadm -o osearch -action start -role index
You may receive the errror ’start’ action failed. Additional information: the handle is invalid. Wait 30-60 secs and re-issue the command. It should go through fine.
Open Central Admin – select your SSP
Application Management => Manage Search Service => Shared Services Administration
Check / validate your search service configuration.
Related Posts
Related Stories
Trend Micro stresses 'tested' patent in trade case
http://www.coderetard.com
(Tech Industry News) Barracuda Networks plans to focus on finding prior art to defend itself and the open-source ClamAV project against patent claims by rival antivirus vendor Trend Micro, which stressed Tuesday that it owns a tested and valid patent.
Dugg 1 times
Subscribe via email
on 
on 
on 
on 
on 
on 
on 
on 
on 
Hi,
I created a new virtual test environment for MOSS and was getting a similar error to yours (EventID 6482) after I had configured Search. In this environment, I haven’t been able to run a successful crawl yet. So I ran the stsadm commands. Under App Mgmt > Manage Search Service > SSP w/Search enabled, the crawling and propagation status displays Search service offline. Under Search Admin, the Active and Recently Created Crawls keep trying to load. I’m not a pro at administration. Any suggestions on what I need to do to get this back online?