Job system in sql server agent properties
Looking at sql agent properties, I wonder what is use of "Non-sysadmins job step proxy account" I saw some server in my working office have checked and unchecked these values. I notice when we unchecked the values the it require us to puyt new account, and question here can we know as well what is current account being used ?
sqljobsystems.bmp
sqljobsystems.bmp
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
well, I don't see any problem in this configuration as you are using domain user account and it has sysadmins server role, it works well.
ASKER
Hi,
Ok the reasons why I asked this such question bcoz every day, the job will failed and succeeded after several attempt of restart, when it failed the error msgs written as below in event viewer or job history, currently the box is unchecked and we set the proxy account similar with account use to start sql agent.
Will tis eliminate this such problem if I check the box ?
A problem occurred while attempting to logon as the Windows user 'SQLAgentCmdExec': Logon failure: account currently disabled. The step failed.
Ok the reasons why I asked this such question bcoz every day, the job will failed and succeeded after several attempt of restart, when it failed the error msgs written as below in event viewer or job history, currently the box is unchecked and we set the proxy account similar with account use to start sql agent.
Will tis eliminate this such problem if I check the box ?
A problem occurred while attempting to logon as the Windows user 'SQLAgentCmdExec': Logon failure: account currently disabled. The step failed.
are you sure you gave proper permission to your sqlagentcmdExec account? I guess you will be ok with the configuration you said in your post # 24154806
ASKER
Yes it is, but now instead of the check box is checked it is does not, but we do have proxy account which actually sql agent account with sysadmin roles.
well in that case, you are ok after selecting that checkbox.
ASKER
Hi,
The error is still persist regardless of checking the values or not, I just don't understands we need to restart the job few time then only it go succeed, what is actually below errors means for ?
A problem occurred while attempting to logon as the Windows user 'SQLAgentCmdExec': Logon failure: account currently disabled. The step failed.
The error is still persist regardless of checking the values or not, I just don't understands we need to restart the job few time then only it go succeed, what is actually below errors means for ?
A problem occurred while attempting to logon as the Windows user 'SQLAgentCmdExec': Logon failure: account currently disabled. The step failed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
Its confirmed that the user account use to start sql agent services has "sysadmins" in server roles, I just dont get it why first run failed and work after that???
Its confirmed that the user account use to start sql agent services has "sysadmins" in server roles, I just dont get it why first run failed and work after that???
ASKER
I have resolved the issue by creating local user, added into administrators group then assigned it onto Job system in sql agent, but I still couldnt find out why it was failed with domain user
I had strong doubt for rights as I had explained in my last post
ASKER
Hi RiteshShah
You did emphasized on the user has no sysadmins but it does and it used to start the sql services and agent, until now I still dont get it why it failed even now when I change it to use the previous account it still failed, and you did not able to help nor explained why it was always failed on first attempt but not subsequently
You did emphasized on the user has no sysadmins but it does and it used to start the sql services and agent, until now I still dont get it why it failed even now when I change it to use the previous account it still failed, and you did not able to help nor explained why it was always failed on first attempt but not subsequently
ASKER
If I check the box, and currently sql agent using domain account as service account which having sysamdins as server roles, is this the best configurations?