From time to time, our SharePoint Server is hit by the 6482 error related to MOSS 2007 Search.
Detailed info on this 6482 error is shown below:
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 11/6/2008
Time: 3:46:06 PM
User: N/A
Computer: xxxxxxx
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (db3c5f85-a70c-4901-98ed-a3e9a9030493).
Reason: Object bfc3dba7-666c-4968-9f4e-3c426d85c6b4 not found.
Techinal Support Details:
System.Collections.Generic.KeyNotFoundException: Object bfc3dba7-666c-4968-9f4e-3c426d85c6b4 not found.
at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()
at Microsoft.Office.Server.Search.Administration.SearchApi.SetUsersPermittedToQuery(String[] userNames, Boolean force)
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.
Complete the steps below to resolve the recurring 6482 error
1. Access the SharePoint Central Administration site.
2. Click on the “Operations” tab.
3. Click on “Services on Server” under “Topology and Services” section.
4. Stop the “Office SharePoint Server Search” and “Windows SharePoint Services Search” Services. Stopping these will uninstall the services, and once you re-start them and re-configure with the same settings, site content will start indexing properly again. You should not see the 6482 Errors anymore.
The KeyNotFoundException error reported in the Event Viewer message above was related to the following Object:
Object bfc3dba7-666c-4968-9f4e-3c426d85c6b4 not found.
This is actually a Registry key which is usually found under the following hives in the Registry on the SharePoint server:
HKLM\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\
HKLM\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\LanguageResources\Override\
You DON’T have to manually delete the “offending” Object from the above hives in the Registry. Stopping the 2 services in Central Administration site will remove the “offending” Object from the Registry.
NOTE: If you need to modify the Registry, REMEMBER TO CREATE A FULL BACKUP BEFORE MAKING ANY UPDATES.
Related Resources on the Web
http://www.eggheadcafe.com/software/aspnet/30014783/moss-2007-errors--still.aspx
http://social.technet.microsoft.com/forums/en-US/sharepointsearch/thread/81872231-0218-440f-b96f-2f5b02dd949f/
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sharepoint.windowsservices&tid=69c450d4-97a2-412c-978a-94919e41c224&cat=&lang=en&cr=US&sloc=&p=1
http://blogs.pointbridge.com/Blogs/bragdon_dwight/Pages/Post.aspx?_ID=16
Friday, December 19, 2008
HOW TO Resolve Recurring 6482 SharePoint Server 2007 Search Related Errors
Labels:
6482,
KeyNotFoundException,
MOSS 2007,
SharePoint Server 2007,
WSS 3.0
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment