2007 Error 6482

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Sharepoint 2007 Event ID 6482 SharePoint > SharePoint Legacy Versions - Search Question 0 Sign in to vote Our two server SharePoint 2007 SP2 farm has an issue. Event ID 6482 appears in the Application log of the Web front end many times a day. Often many time a minute.  The service account has not been changed.  IIS has a GoDaddy certificate that is valid and can be viewed in the IIS snap-in.  Servers are Windows 2003 x64 and SQL 2005 The full error is from Office SharePoint Server Event Type: Error Event Source: Office SharePoint Server Event Category: Office Server Shared Services Event ID: 6482 Date: 11/12/2009 Time: 3:05:22 PM User: N/A Computer: XXXXXX Description: Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (36a9b7ef-59aa-4f94-8887-8bf7b56f2f91). Reason: Error during encryption or decryption. System error code 0. Techinal Support Details: System.ArgumentException: Error during encryption or decryption. System error code 0. 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. The SharePoint site appears to be functioning normally and Search returns expected results. Any suggestions would be appreciatedDave Thursday, November 12, 2009 8:58 PM Reply | Quote All replies 0 Sign in to vote Hi Dave,Please see the following KB article which explains how to update SharePoint passwords. It looks like the SSP account's cache credentials are corrupt.http://support.microsoft.com/kb/934838You want to focus on step 6a from that article as that command updates the SSP account credentials, but it would not hurt

is hit by the 6482 error related to MOSS 2007 Search.Detailed info on this 6482 error is shown below:Event Type: ErrorEvent Source: Office SharePoint ServerEvent Category: Office Server Shared ServicesEvent ID: 6482Date: 11/6/2008Time: 3:46:06 PMUser: N/AComputer: xxxxxxxDescription:Application Server Administration job https://social.technet.microsoft.com/Forums/sharepoint/en-US/dd26fbef-5edb-4201-bb10-dcda1dcdf295/sharepoint-2007-event-id-6482?forum=sharepointsearchlegacy 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 http://kiran-kakanur.blogspot.com/2008/12/how-to-resolve-recurring-6482.html recurring 6482 error1. 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 "

events after every minute. http://alstechtips.blogspot.com/2011/03/how-to-resolve-office-sharepoint-error.html   Event Type:        Error Event Source:     Office SharePoint Server Event Category:  Office Server Shared Services Event ID:   6482 Date:        XXXXXXXX Time:        XXXXXXXX User:         N/A Computer:  Server Name Description: Application Server Administration 2007 error job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (a30c0eb5-8dac-4654-be59-5c9f950ed3b4).   Reason: The specified account name is invalid. Parameter name: account   Techinal Support Details: System.ArgumentException: The specified account name is invalid. Parameter name: account --> System.Security.Principal.IdentityNotMappedException: Some or all 2007 error 6482 identity references could not be translated.    at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)    at System.Security.Principal.NTAccount.Translate(Type targetType)    at Microsoft.Office.Server.Utilities.WindowsSecurity.ValidateAccount(NTAccount account, Boolean throwIfInvalid)    -- End of inner exception stack trace --    at Microsoft.Office.Server.Utilities.WindowsSecurity.ValidateAccount(NTAccount account, Boolean throwIfInvalid)    at Microsoft.Office.Server.Administration.SharedAccessRule.Validate()    at Microsoft.Office.Server.Administration.SharedComponentSecurity.SetAccessRule(SharedAccessRule accessRule)    at Microsoft.Office.Server.Administration.SharedResourceProvider.GetApplicationSecurity()    at Microsoft.Office.Server.Administration.SharedWebServiceInstance.ProvisionSharedResourceProviderWebConfigSettings(SharedResourceProvider srp)    at Microsoft.Office.Server.Administration.SharedWebServiceInstance.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.   Event Type:        Error Event Source:     Office SharePoint Server Event Category:  Office Server Shared Services Event ID:   6481 Date:        XXXXXXXX Time:        XXXXXXXX User:         N/A Computer:  Server Name Description: Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (d245dafa-360e-4267-993d-501d04d03025).   Rea

some practical steps to take in order to resolve the following error: Event Type: Error Event Source: Office SharePoint Server Event Category: Office Server Shared Services Event ID: 6482 Date: [date] Time: [time] User: N/A Computer: [yourservername] Description: Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance... This error was experienced with regard to a SharePoint Server 2007 Enterprise instance hosted on Windows Server 2003 Enterprise Edition. Procedure Go to Services, and then reset SharePoint search server accounts (stop/start) Reset the crawl index (clears the index) Stop and then start the Office Search Server - two options: command line: ststadm -o osearch -action stop Central Administration: stop and then restart the service Reset default content access account One or more of these steps together will usually resolve any instance of this error. Good luck! References EventID.NET Notes SharePoint 2007 hosted on Windows Server 2003 with SQL Server 2005 Standard backend. Posted by Al at Thursday, March 10, 2011 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: SharePoint 2007 No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Blog Archive ► 2016 (37) ► September (4) ► August (4) ► July (8) ► June (3) ► May (5) ► April (3) ► March (3) ► February (4) ► January (3) ► 2015 (98) ► December (6) ► November (5) ► October (8) ► September (9) ► August (5) ► July (6) ► June (10) ► May (5) ► April (12) ► March (12) ► February (7) ► January (13) ► 2014 (122) ► December (12) ► November (3) ► October (5) ► September (9) ► August (5) ► July (10) ► June (17) ► May (15) ► April (13) ► March (8) ► February (11) ► January (14) ► 2013 (88) ► December (12) ► November (4) ► October (23) ► September (24) ► August (1) ► June (11) &#