locked
Event ID Errors: 6398, 6482, and 6641 for Share Point RRS feed

  • Question

  • Hi

    I was wondering if someone can help me out with these errors I have been getting.  I look on the web and can not find anything to fix these issues.  There are a ton of these being logged.

    Event Type: Error
    Event Source: Office SharePoint Server
    Event Category: Office Server Shared Services
    Event ID: 6641
    Date:  2/8/2007
    Time:  1:20:00 PM
    User:  N/A
    Computer: CCSP
    Description:
    The SSP Timer Job Distribution List Import Job was not run.

    Reason: Logon failure: the user has not been granted the requested logon type at this computer

    Technical Support Details:
    System.ComponentModel.Win32Exception: Logon failure: the user has not been granted the requested logon type at this computer
       at Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(String userDomainName, String password, LogonType logonType)
       at Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(String userDomainName, String password)
       at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state, Boolean timedOut)

    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: 6482
    Date:  2/8/2007
    Time:  1:16:07 PM
    User:  N/A
    Computer: CCSP
    Description:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (77cdaca7-f1f3-411f-980d-82fec9ddbc92).

    Reason: Logon failure: the user has not been granted the requested logon type at this computer

    Techinal Support Details:
    System.ComponentModel.Win32Exception: Logon failure: the user has not been granted the requested logon type at this computer
       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.

    **********************************************************************************************************************

    Event Type: Error
    Event Source: Windows SharePoint Services 3
    Event Category: Timer
    Event ID: 6398
    Date:  2/8/2007
    Time:  1:20:00 PM
    User:  N/A
    Computer: CCSP
    Description:
    The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID 3a4cd737-d0c1-443b-be03-75a0f99160bb) threw an exception. More information is included below.

    Retrieving the COM class factory for component with CLSID {629DA12E-9AD5-4FEC-B886-42C5982C5109} failed due to the following error: 8007042d.

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


     

    Thursday, February 8, 2007 6:34 PM

Answers

  • I have run into this problem even when I have not changed the password.  I tried the fix to add the service account to the backup operators group and that did not completely fix the problem.  Additionally, I have notice that I have had a lot of other mysterious SharePoint Server Errors  What you need to do to correct this problem is:

     

    1.     One of Microsoft’s best practices is to make sure that the application pool account for your SSP and your service account for the SSP are the same account.

    2.     Make sure to add this account to the backup operator’s local group on all your MOSS servers.

    3.     If you are using Kerberos authentication for your web applications make sure you set your service name principle account for you ssp on you MOSS application server.  In order to complete this operation you must install Window support tools from your Windows server installation files under support>>tools>>supporttools.msi.  Once you have installed the support tools go to start>>All programs>> Windows support tools>> command prompt.

    setspn.exe –A HTTP/name_of_ssp_address domain\appication

    Assume your site address is ssp, your domain is sharePoint, and your application pool account is svc_ssp. Run these commands

    setspn.exe –A HTTP/ssp SharePoint\svc_ssp       (Run this Command)

    setspn.exe –A HTTP/ssp.sharepoint.com SharePoint\svc_ssp  (Run this command)

    If you are using Kerberos authentication on any of your web applications you must run these commands for the web applications to function properly including your central administration site.

    4.     Check your system event logs on your MOSS server for any DCOM errors.  You will notice your DCOM errors are associated with your application pool accounts.  Add these acounts to the IIS WAMREG admin service.  Make sure the accounts have local launch, remote launch, local activation, and remote activation.

    5.     Next stop your Office SharePoint Server Search through central administation>> operations>> Services on Server.

    6.     Then go to central administration>> operations>> service accounts.  Click on web application pool.  Then under web service choose Windows SharePoint Service Web application.  Next under application pool, choose your Shared Service Provider application pool account.  Under configurable you will notice that it populated your application pool account.  Now re-enter your password and click ok.

    7.     Login into all your MOSS servers and run iisreset /noforce.

    8.     Go back to central administation>> operations>> Services on Server and restart your Office Server Search.

    9.     Then go to central administation>>Application Management>> Manage this Farm's Shared Services.  click the drop down on the default SSP and click edit properties.  In the SSP service credentials enter username and password.  In the index server catagory select your index server and then click ok. Make sure you wait about 5 minutes.

    Spent a lot of time trouble shooting the sharepoint errors and I hope this information helps.

    Friday, April 13, 2007 12:12 PM
  • The error I was getting was a bit different, but I thought this information might be useful; as it seems there is still not a lot out there on this subject.

    The error:

    Event Type: Error
    Event Source: Office SharePoint Server
    Event Category: Office Server Shared Services
    Event ID: 6482
    Date:  8/6/2008
    Time:  2:56:26 PM
    User:  N/A
    Computer: SPWEB2
    Description:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (e429eb2f-8245-48a1-b66e-aa6bf6fe1005).

    Reason: Failed to resolve the site ID for 'Office Server Web Services'.

    Techinal Support Details:
    System.InvalidOperationException: Failed to resolve the site ID for 'Office Server Web Services'.
       at System.Web.Configuration.WebConfigurationHost.GetConfigPaths(IConfigMapPath configMapPath, WebLevel webLevel, VirtualPath virtualPath, String site, String locationSubPath, VirtualPath& appPath, String& appSiteName, String& appSiteID, String& configPath, String& locationConfigPath)
       at System.Web.Configuration.WebConfigurationHost.InitForConfiguration(String& locationSubPath, String& configPath, String& locationConfigPath, IInternalConfigRoot configRoot, Object[] hostInitConfigurationParams)
       at System.Configuration.Configuration..ctor(String locationSubPath, Type typeConfigHost, Object[] hostInitConfigurationParams)
       at System.Configuration.Internal.InternalConfigConfigurationFactory.System.Configuration.Internal.IInternalConfigConfigurationFactory.Create(Type typeConfigHost, Object[] hostInitConfigurationParams)
       at System.Web.Configuration.WebConfigurationHost.OpenConfiguration(WebLevel webLevel, ConfigurationFileMap fileMap, VirtualPath path, String site, String locationSubPath, String server, String userName, String password, IntPtr tokenHandle)
       at System.Web.Configuration.WebConfigurationManager.OpenWebConfigurationImpl(WebLevel webLevel, ConfigurationFileMap fileMap, String path, String site, String locationSubPath, String server, String userName, String password, IntPtr userToken)
       at System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration(String path, String site, String locationSubPath)
       at Microsoft.Office.Server.Administration.SharedWebServiceInstance.OpenWebConfiguration(String locationSubPath)
       at Microsoft.Office.Server.Administration.SharedWebServiceInstance.ProvisionRootWebConfigSettings()
       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.

    -----------------------------------------

    I have two front end web servers in my SP farm. The 2nd web server (mentioned here) was erroring out every minute. When I went into IIS I discovered my "Office Server Web Services" site had a red error symbol next to it. I could not browse the site, nor could I stop or start it.

    The first thing I did was delete the site, and attempt to recreate it identically. The site was created, but I got an error when I attempted to start the site:

    "Cannot register the URL prefix 'http://*:56737/' for site '591752002'. The necessary network binding may already be in use. The site has been deactivated. The data field contains the error number."

    I deleted the site.

    I then went to the other web server (1st), browsed IIS for the same Office Server site, right clicked on it, and selected "save configuration to file". I saved it to a location on the 2nd web server. On the 2nd web server (our problem child) I created a new website (from file). I browsed to the location selected the xml, and was prompted to create a new site, or replace existing. You want to replace existing.

    From here you should be able to start the site, and the errors should stop.

    I hope this helps someone out there!

    Wednesday, August 6, 2008 10:20 PM

All replies

  • Event Type:    Error
    Event Source:    Windows SharePoint Services 3
    Event Category:    Timer
    Event ID:    6398
    Date:        2/9/2007
    Time:        2:35:00 PM
    User:        N/A
    Computer:    SHAREPT
    Description:
    The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID 823a792a-986b-4ab6-b7cc-517197b087ea) threw an exception. More information is included below.

    Retrieving the COM class factory for component with CLSID {629DA12E-9AD5-4FEC-B886-42C5982C5109} failed due to the following error: 80070422.

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

    Friday, February 9, 2007 10:41 PM
  • I also have this same error. Any ideas?
    Monday, February 12, 2007 7:15 PM
  • I just got tired of fighting this problem. I backed up my sites with stsadm and reloaded the server.
    Monday, February 12, 2007 9:26 PM
  • giving the account running the ssp application pool local admin rights solved it for me... sadly this might be insecure somehow :/
    Tuesday, February 13, 2007 8:54 AM
  • Not sure about the Event ID 6398, however did have an issue seeing 6482 and 6641 in my Event Viewer.  I was able to fix them by adding the account used by SP (I created an SPService account) and assigning it to the Backup Operators group.  This has something to do with the need to be able to log on as a batch job.  I have also heard of people granting this through their GPO.

    Should fix it for Event ID 6482 and 6641.

    Tuesday, March 20, 2007 4:37 PM
  • I have run into this problem even when I have not changed the password.  I tried the fix to add the service account to the backup operators group and that did not completely fix the problem.  Additionally, I have notice that I have had a lot of other mysterious SharePoint Server Errors  What you need to do to correct this problem is:

     

    1.     One of Microsoft’s best practices is to make sure that the application pool account for your SSP and your service account for the SSP are the same account.

    2.     Make sure to add this account to the backup operator’s local group on all your MOSS servers.

    3.     If you are using Kerberos authentication for your web applications make sure you set your service name principle account for you ssp on you MOSS application server.  In order to complete this operation you must install Window support tools from your Windows server installation files under support>>tools>>supporttools.msi.  Once you have installed the support tools go to start>>All programs>> Windows support tools>> command prompt.

    setspn.exe –A HTTP/name_of_ssp_address domain\appication

    Assume your site address is ssp, your domain is sharePoint, and your application pool account is svc_ssp. Run these commands

    setspn.exe –A HTTP/ssp SharePoint\svc_ssp       (Run this Command)

    setspn.exe –A HTTP/ssp.sharepoint.com SharePoint\svc_ssp  (Run this command)

    If you are using Kerberos authentication on any of your web applications you must run these commands for the web applications to function properly including your central administration site.

    4.     Check your system event logs on your MOSS server for any DCOM errors.  You will notice your DCOM errors are associated with your application pool accounts.  Add these acounts to the IIS WAMREG admin service.  Make sure the accounts have local launch, remote launch, local activation, and remote activation.

    5.     Next stop your Office SharePoint Server Search through central administation>> operations>> Services on Server.

    6.     Then go to central administration>> operations>> service accounts.  Click on web application pool.  Then under web service choose Windows SharePoint Service Web application.  Next under application pool, choose your Shared Service Provider application pool account.  Under configurable you will notice that it populated your application pool account.  Now re-enter your password and click ok.

    7.     Login into all your MOSS servers and run iisreset /noforce.

    8.     Go back to central administation>> operations>> Services on Server and restart your Office Server Search.

    9.     Then go to central administation>>Application Management>> Manage this Farm's Shared Services.  click the drop down on the default SSP and click edit properties.  In the SSP service credentials enter username and password.  In the index server catagory select your index server and then click ok. Make sure you wait about 5 minutes.

    Spent a lot of time trouble shooting the sharepoint errors and I hope this information helps.

    Friday, April 13, 2007 12:12 PM
  • Thank you SharePoint_007 - you saved me!!!!
    Monday, April 23, 2007 5:48 PM
  • Thanks for taking the time to write all that down, SharePoint_007, it was most helpful!
    Wednesday, May 2, 2007 2:17 PM
  • It worked for me, but only for about an hour. After that, i got my errors back :-( I put all my sharepoint service accounts to local administrators, and stil error is: Logon failure: the user has not been granted the requested logon type at this computer. And this account is local administrator...
    Wednesday, June 20, 2007 7:35 AM
  •  

    This also might be due to an issue in Microsoft .NET framworks 2.0. There is a hotfix available.
    Look at KB 923028(http://support.microsoft.com/?id=923028).
    Friday, August 10, 2007 9:27 PM
  • Go to Central Admin/Operations/Security configuration/Service Accounts. Select Web application pool radio button. In The web service drop down list select Windows Sharepoint Services Web Application. Now, In the application pool, select one by ones and for each one type the service account and password in the configurable area at the bottom.
    This has solved the issue for me after spending decades looking for a solution (Thanks to Michael Noel assistance)

     

    Tuesday, December 4, 2007 3:45 PM
  • this error was on only one of the 3 MOSS web servers although the service account was a local admin but adding it to the "Backup Operators" group stopped this error in my event viewer. 

     

    Thanks SharePoint_007, you made my day.

    Wednesday, December 5, 2007 12:01 AM
  • Hello, I checked my services on the Web server and get this error message.  "Web Front End servers in the server farm are not consistent in the services they run."  I am confused here because I only have one server.  I an troubleshooting the same event id's written about here and am tryuing to correct them.

    Monday, December 10, 2007 9:11 PM
  •  

    For the Event ID 6398 restarting Windows SharePoint Services Timer did the trick for me.

    You can restart it via stsadm or by going to Services.

    Thursday, January 3, 2008 3:13 PM
  • Tuesday, January 29, 2008 8:26 PM
  • This error has been fixed by Microsoft finally they have patch for this and link to KB article for the patch is http://support.microsoft.com/?id=946517

     

    Hope this helps.

     

    Monday, February 4, 2008 7:35 PM
  • Thank you SharePoint_007 -   It's so helpful to me.
    Wednesday, July 2, 2008 10:20 AM
  • The problem has been resolved in Service Pack 1.

    If you can’t install SP1, create a scheduled job that restarts Windows SharePoint Services Timer every 24 hours.

     

    Wednesday, July 2, 2008 1:15 PM
  • The error I was getting was a bit different, but I thought this information might be useful; as it seems there is still not a lot out there on this subject.

    The error:

    Event Type: Error
    Event Source: Office SharePoint Server
    Event Category: Office Server Shared Services
    Event ID: 6482
    Date:  8/6/2008
    Time:  2:56:26 PM
    User:  N/A
    Computer: SPWEB2
    Description:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (e429eb2f-8245-48a1-b66e-aa6bf6fe1005).

    Reason: Failed to resolve the site ID for 'Office Server Web Services'.

    Techinal Support Details:
    System.InvalidOperationException: Failed to resolve the site ID for 'Office Server Web Services'.
       at System.Web.Configuration.WebConfigurationHost.GetConfigPaths(IConfigMapPath configMapPath, WebLevel webLevel, VirtualPath virtualPath, String site, String locationSubPath, VirtualPath& appPath, String& appSiteName, String& appSiteID, String& configPath, String& locationConfigPath)
       at System.Web.Configuration.WebConfigurationHost.InitForConfiguration(String& locationSubPath, String& configPath, String& locationConfigPath, IInternalConfigRoot configRoot, Object[] hostInitConfigurationParams)
       at System.Configuration.Configuration..ctor(String locationSubPath, Type typeConfigHost, Object[] hostInitConfigurationParams)
       at System.Configuration.Internal.InternalConfigConfigurationFactory.System.Configuration.Internal.IInternalConfigConfigurationFactory.Create(Type typeConfigHost, Object[] hostInitConfigurationParams)
       at System.Web.Configuration.WebConfigurationHost.OpenConfiguration(WebLevel webLevel, ConfigurationFileMap fileMap, VirtualPath path, String site, String locationSubPath, String server, String userName, String password, IntPtr tokenHandle)
       at System.Web.Configuration.WebConfigurationManager.OpenWebConfigurationImpl(WebLevel webLevel, ConfigurationFileMap fileMap, String path, String site, String locationSubPath, String server, String userName, String password, IntPtr userToken)
       at System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration(String path, String site, String locationSubPath)
       at Microsoft.Office.Server.Administration.SharedWebServiceInstance.OpenWebConfiguration(String locationSubPath)
       at Microsoft.Office.Server.Administration.SharedWebServiceInstance.ProvisionRootWebConfigSettings()
       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.

    -----------------------------------------

    I have two front end web servers in my SP farm. The 2nd web server (mentioned here) was erroring out every minute. When I went into IIS I discovered my "Office Server Web Services" site had a red error symbol next to it. I could not browse the site, nor could I stop or start it.

    The first thing I did was delete the site, and attempt to recreate it identically. The site was created, but I got an error when I attempted to start the site:

    "Cannot register the URL prefix 'http://*:56737/' for site '591752002'. The necessary network binding may already be in use. The site has been deactivated. The data field contains the error number."

    I deleted the site.

    I then went to the other web server (1st), browsed IIS for the same Office Server site, right clicked on it, and selected "save configuration to file". I saved it to a location on the 2nd web server. On the 2nd web server (our problem child) I created a new website (from file). I browsed to the location selected the xml, and was prompted to create a new site, or replace existing. You want to replace existing.

    From here you should be able to start the site, and the errors should stop.

    I hope this helps someone out there!

    Wednesday, August 6, 2008 10:20 PM
  • thanks for the tip working fine for me , but i still have this error coming event code is 1055

    Monday, September 8, 2008 2:47 PM
  • hi , i just got some event id with the sharepoint server. and follow the link you supply, this's  useful . thanks.
    to well live,just keeping the ardour.
    Tuesday, May 19, 2009 2:53 AM
  • Hey guys,

    for me the article http://support.microsoft.com/kb/962928/en-us works fine. Errors 6641 and 6482 are blown away by this article.
    If somebody does search the Identifier for a Website in IIS (in relation to point 3.c of the article mentioned above), because the default Identifier doesn't work, do the following:

    You have to go to the IIS Manager GUI and to the Web Sites. There you rightclick the Website you wanna figure out the ID from and click properties. On Tab Web Site, klick enable logging and then klick Properties. Down the next dialog, there is a logfilename on the bottom. Just eleminate the first five pattern
    "W3SVC" from the filename and you got the ID you're searching for!

    Hope it will help you.
    Friday, September 25, 2009 8:44 AM
  • Our issue was the event id 6641.  I followed the instructions given but now I am getting a SERVICE UNAVAILABLE page displaying on our MySites.  What did I do wrong and do you have any steps to follow to resolve the SERVICE UNAVAILABLE?  I have done an iisreset and checked all the app pools to make sure they were running.  Thanks!

    Tuesday, October 20, 2009 10:08 PM
  • I resolved the error by following the steps in this post:

     

    http://sharemypoint.wordpress.com/2007/12/18/error-event-id-6398-and-6482-about-security-rights-of-osearch-service/

     

    This worked out perfectly.  Thank you to both you and Sharepoint_007.
    • Proposed as answer by AR-Oldenburg Wednesday, December 29, 2010 10:03 AM
    • Unproposed as answer by Mike Walsh FIN Friday, April 22, 2011 11:10 AM
    Wednesday, March 10, 2010 4:16 PM
  • This solution works for me Thanks a lot!
    • Proposed as answer by AR-Oldenburg Wednesday, December 29, 2010 10:03 AM
    • Unproposed as answer by Mike Walsh FIN Friday, April 22, 2011 11:10 AM
    Wednesday, July 21, 2010 12:29 PM