Re: SQL Agent Proxy Account



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
>
>


.



Relevant Pages

  • Re: Running Analysis Server 2000 on seperate box
    ... changing the service account sorted things. ... with 2GB ram on Windows Server 2003. ... The server has both the database and Analysis Services ... >to use Local System which is fine for local databases, ...
    (microsoft.public.sqlserver.olap)
  • Re: SPN for SSL over common name
    ... you can't register those SPNs under the SQL Server's ... service account is the MSSQL SPN. ... That SPN should be registered under ... Lastly, since the SQL Server is not being used for delegation anywhere, ...
    (microsoft.public.inetserver.iis.security)
  • Re: In SSP Admin page Search Setting link fails with access denied
    ... First I modified the permissions of the SSP service account as you said. ... administratie and service accounts (Office SharePoint Server): ... How to change the passwords for service accounts in SharePoint Server ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Kerberos w/ SQL and WIN2000
    ... are not using Linked Servers then you don't need to set up an SPN AFAIK ... Win2000 will default to using kerberos to connect to the server anyway ... For my server called sqlnlb01 in domain domsql.com using a service account ...
    (microsoft.public.sqlserver.security)
  • SQL Agent Proxy Account
    ... Ever since a reboot of this server, jobs owned by no sa's now fail with this ... rather the sql server service account cannot log in. ...
    (microsoft.public.sqlserver.security)