Event error 8026 after domain password change


I have a windows server 2003 server running Exchange 2003 on a domain. After changing the domain admin password that we use to log onto servers, run backups etc...I have been receiving an event error 8026 every couple of minutes in my event log. The error is as below

LDAP Bind was unsuccessful on directory mail.hsfc.hpoolsfc.ac.uk for distinguished name 'HSFC\NT4ADMIN'. Directory returned error:[0x31] Invalid Credentials.   (Connection Agreement 'Config CA_HSFC_MAIL' #2916)

It is obviously the change of password that has caused this error but I am not sure what is trying to use it, any ideas?

Who is Participating?
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.

This is off of Microsofts site take read at this


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
There's probably an easier way...open Services on the server(s) and and see if what servers are using the Admin credentials to startup.  Look under the "Log on as" column.
brookesmAuthor Commented:
I have looked under services and the only service running as the account mentioned is Microsoft Active Directory Connector, which I have now changed to use new credentials. I am still getting the same error!!!

Any ideas??
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

brookesmAuthor Commented:
I found the solution, it wasn't a service that was using the account. For some reason the mail server did not recognise itself as a DC and so I was getting the error message stated!
thank you for the points
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

From novice to tech pro — start learning today.