SharePoint 2007 account causing Event ID 4625 errors

I am administering an old SharePoint 2007 Central Admin server that I have inherited.  Whenever the OWSTimer

service is running it generates 4625 errors (Unknown user name or bad password) for the designated Active Directory

account in the Security Event log.
I am able to login to the Windows Server 2008 R2 host machine with the same set of credentials.  I have manually,

and very carefully entered those same credentials into the Windows SharePoint Services Timer service in the Service

console.  So I am 100% certain those credentials are good.
I have checked the Windows Credential Manager in the Control panel and nothing is stored in there.
Based on some research that led me to Microsoft Technet, I have also run the following commands to clear the System

Context cache:

psexec -i -s -d cmd.exe
From the new DOS window run:  rundll32 keymgr.dll,KRShowKeyMgr
Remove any items that appear in the list of Stored User Names and Passwords.  Restart the computer.
There weren't any items to remove.

Does anyone know where else on this server the credentials for this designated account might be cached???  It is

driving me crazy.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


the timer service runs several jobs, so the question is, if the error comes from the timer service itself or from the job driven by it.

Changing password for MOSS is sometimes not only to directly change the passwords where you see them. Some accounts need not only access to the running service, but also on the web service and / or the database.

If no passwords are changed in the past, it is always a good idea to run the SharePoint configuration wizard because this tool makes sure, that settings and permissions are fine. Especially after updates it has to be run in most of the cases.

If you are unsure, if passwords have changed, or you know that passwords have changed, then have a look here to see, how to change these passwords for MOSS as well.

In your case possibly...
stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword

After changing passwords....
ISSReset is possibly needed....
SharePoint Configuration Wizzard may be needed.

The most imformation what is going on is coming from the ULS logs. There are two ULS Viewer on Codeplex which you can use to analyse the ULS logs. For Example:
mtkaiserAuthor Commented:
I used your instructions to reset the Sharepoint farm password.
And, its working now?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mtkaiserAuthor Commented:
Yes, thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.