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

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

• Imran_Akram

  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...
  

• ChasAA

  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.

  
  

• Jumperboy

  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.

  
  

• shmulik_segal

  giving the account running the ssp application pool local admin rights solved it for me... sadly this might be insecure somehow :/
  

• Sébastien Nunes

  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).
  

• thekaran

  Thanks for taking the time to write all that down, SharePoint_007, it was most helpful!
  
  

• el_Fede

  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.

  
  

• Giugio

  Thank you SharePoint_007 - you saved me!!!!
  

• r3zonance

  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.
  
  
  
  

• xRuntime

  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.

  
  

• David_navigator

  I also have this same error. Any ideas
  
  

• Neotec

  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)

  
  

• nibs

  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.

  
  
  

• Jack Hoxley

  I just got tired of fighting this problem. I backed up my sites with stsadm and reloaded the server.
  
  
• Event ID Errors: 6398, 6482, and 6641 for Share Point