July 25, 2016 at 3:36 am
Hi everyone
I am encountering a strange issue on my SQL Server.
Since 2-3 weeks, my domain account gets locked frequently.
We found out that the root cause is our SQL server and in the security logs you can see
Failure Information:
Failure Reason:Unknown user name or bad password.
Status:0xC000006D
Sub Status:0xC000006A
Process Information:
Caller Process ID:0x10b8
Caller Process Name:S:\SQL2014\MSSQL12.MSSQLSERVER\MSSQL\Binn\SQLAGENT.EXE
I checked twice and twice again that my domain account is not being used for anything related to SQL server.
Can anybody help me?
July 25, 2016 at 3:44 am
SQL Server Agent could impersonate you windows users in these cases:
1) You are the owner of a job and not a sysadmin in SQL Server
2) SQL Server Agent service is started using yout account and a job is owned by a sysadmin
3) A job step explicitly requires starting as a proxy account using your credentials
4) A job step explicitly requires starting as the service account, which is your windows account
-- Gianluca Sartori
July 25, 2016 at 3:45 am
Quick question, is there an Error 18456 entry in the logs and if so, what is the ERROR STATE?
😎
July 25, 2016 at 4:04 am
spaghettidba (7/25/2016)
SQL Server Agent could impersonate you windows users in these cases:1) You are the owner of a job and not a sysadmin in SQL Server
2) SQL Server Agent service is started using yout account and a job is owned by a sysadmin
3) A job step explicitly requires starting as a proxy account using your credentials
4) A job step explicitly requires starting as the service account, which is your windows account
Hi - I am owner of 24 jobs and sysadmin - checked that.
SQL Server Agent is running with a non-expiring service account
but
I determined that my account was set up unter "Login/credentials" as UtilityAgentProxyCredentials but this was 4-5 month ago that I set this up but never used again.
Maybe I found the showstopper
July 25, 2016 at 4:30 am
pnx81 (7/25/2016)
my account was set up unter "Login/credentials" as UtilityAgentProxyCredentials but this was 4-5 month ago that I set this up but never used again.Maybe I found the showstopper
That could be it.
-- Gianluca Sartori
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply