Re: SQL Agent Proxy Account
- From: "michelle" <michelle@xxxxxxxxxx>
- Date: Fri, 6 Jan 2006 15:33:38 -0600
I found this - and in BOL :)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_2gmm.asp
I forwarded to Server Admin. Not sure if it's relevant. There are different
settings with this service account/other sql server service accounts and
with this computer account/other sql server computer accounts.
"michelle" <michelle@xxxxxxxxxx> wrote in message
news:OpdugavEGHA.1312@xxxxxxxxxxxxxxxxxxxxxxx
> Ever since a reboot of this server, jobs owned by no sa's now fail with
this
> error:
>
> "A problem occurred while attempting to logon as the Windows user
> 'SQLAgentCmdExec': A required privilege is not held by the client. The
step
> failed."
>
> I verified that the proxy account was still set (that the 'only sa' check
> box was not checked). I tried to re-set the proxy account using both
> xp_sqlagent_proxy_account and the gui but get the following error:
>
> Error executing extended stored procedure: Specified user can not login
>
> I understand that this is not that I cannot login to make this change but
> rather the sql server service account cannot log in. I used the MS KB
> article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;890775
>
> to verify that the sql server service account still has the correct
> permissions and it does. I've seen other posts from people with this issue
> that did the same thing AND use Enterprise Manager to re-set the sql
server
> service account but this did not resolve their issue (and obviously would
> require downtime of the server to perform). So, before trying to get this
> down time which may or may not resolve the issue - what could be causing
> this?
>
> Something with Kerberos/spn? I thought that I saw that somewhere but now
> can't seem to find that again.
>
> We can set the jobs to run as some in the sa role for now if necessary but
> that it not desirable.
>
> The reboot was unplanned (automatic install of OS patches/hot fixes,
> automatic reboot, not sure that Server Admin intended this). I looked up
all
> of the patches/hot fixes that were applied and none seem to be related to
> this so I'm just thinking that something else got goofed up and didn't
take
> affect until after the reboot.
>
> Frustrated,
>
> Michelle
>
>
.
- References:
- SQL Agent Proxy Account
- From: michelle
- SQL Agent Proxy Account
- Prev by Date: ISAPI Application and Integrated Security
- Next by Date: Re: SSPI handshake failed - SQL Server 2005
- Previous by thread: SQL Agent Proxy Account
- Next by thread: ISAPI Application and Integrated Security
- Index(es):
Relevant Pages
|