Event ID : 6641, SSP Timer Job User Profile Change Job was not run

The following error appears in the event viewer of my share point server every minute 

/******************Error Description *****************/

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6641
Date: 5/15/2012
Time: 2:00:00 PM
User: N/A
Computer: <server name>
Description:
The SSP Timer Job User Profile Change 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.

/******************Error Description *****************/

 I googled it for the resolution and in many places I found that it has to do with the service account password change and not updated in the farm credentials. But the service account password was not locked nor it was changed. There fore the solutions I found didn't solve my issue.

After thorough search, I again found in some places where it was mentioned that, the account on which the windows share point timer services will run, has to be provided with log on as batch privileges.
Following is the process to modify the setting

Type gpedit.msc from run and under
Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment.

check for the policy "Logon as a batch Job"

check whether the service account on which the windows share point Timer services are running is present in the policy as a user. If not, add the account there.

Also make sure that, the account should also be a part of "Logon as service" policy.

Once this is added, the error stopped appearing in my event viewer.