Receving several logon failures from below account.
Account Domain: m
Failure Reason: Unknown user name or bad password
Status: 0xc000006d Sub Status: 0xc0000064 (user name does not exist)
Workstation Name: SharePoint server Source Network Address: SharePoint server
Source Port: 63247
Upon checking we see that this account is not present in AD and also had checked the Task Scheduler and services, none of the jobs are using this account.
The alert was being triggered from OWSTIMER.exe.
We performed below changes.
- Cleared config cache on the server
- Updated the service account password for SharePoint Timer service
Upon doing the above, we didn’t receive any logon failures from m\_. After a day, we got same issue reported back.
We performed below changes again.
- Cleared config cache on the server
- Ran PSConfig on the server
Upon doing the above, we didn’t receive any logon failures from m\_. After a day, we got same issue reported back.
One observation we have is that the below Timer job is failing after a day of performing the above steps. We see that once we ran PSConfig.exe, the below Timer job succeeds, but later after a day it fails again.
Job Title : **** User Profile Service - User Profile ActiveDirectory Import Job
Job Description : Imports objects from Active Directory into Profile Database
Error Message : An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=**** User Profile Service was updated by Domain\"farm account", in the OWSTIMER (5892) process, on machine “SP SERVER”. View the tracing log for more information about the conflict.
Please provide your thoughts. Thanks in advance!
Vignesh Ganesan, Microsoft SharePoint & O365 Consultant, Pune, Maharashtra. Mob : 7387783354