Could not find xp_sqlagent_proxy_account

Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
> > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > account. It says successfully, but I cannot find any local account
> > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > Have you tried changing this from the Services applet?
> >
> > John
> >
> > "Min" wrote:
> >
> > > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > > account. It says successfully, but I cannot find any local account
> > > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > I don't have a SQL 7 system to check, but the if you can't find the stored
> > procedure in the master database using Enterprise Manager, then it was either
> > deleted for security or does not exist in that version.
> >
> > The local users are accessed through the Server applet in control panel. The
> > services applet in control panel will allow you to select a different user
> > for the service to be run as.
> >
> > John|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
John
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> >
> > If the machine is NT workstation you can manage local users using
> > musrmgr.exe but this is not available on NT Server.
> >
> > What account is the service running under in the services applet? Usually
> > the account would be a domain user with restricted privileges.|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via SQLMonster.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>|||Thanks. I guess my question now is really:
How can I create a proxy account correctly? Thru EM, I unchecked the box,
clicked "reset ..." and message came back saying " successfully". But I am
still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
non-admin account.
Also, there is no utility on NT server to verify the account.
"John Bell" wrote:
> Hi
> See inline:
> "Min" wrote:
> > So is it right for SQL Server 7, the only way to reset proxy account is thru
> > EM, not programatically?
> Probably but I don't have a system to check this. There may be a way to
> write your own process to do this, but whether this is a justified effort for
> a version of the product that is so old, I don't know. You may want to trace
> what happens when you use EM and see what if you can do the same.
> >
> > Does it mean for NT Server, there is no way I can check to verify if the
> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
> > the "reset proxy" account button in "Job System", it says "successfully" but
> > there is an error log entry for agent says "SQLAgentCmdExec password
> > verification failed, required client privilege not held".
> Is there anything in the Event log?
> >
> > We use a domain acount for both SQL and Agent services. It is in local
> > administrator group.
> You may also want to check:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
> John
> >
> > Thanks again!
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> > >
> > > If the machine is NT workstation you can manage local users using
> > > musrmgr.exe but this is not available on NT Server.
> > >
> > > What account is the service running under in the services applet? Usually
> > > the account would be a domain user with restricted privileges.|||Yes...use Enterprise Manager and the Reset Proxy on the Job
System tab in SQL Agent Properties. Refer to the following
for more info:
INF: Reset Proxy and the SQLAgentCmdExec Account
http://support.microsoft.com/?id=264155
But your issues are likely related to the service account,
not the proxy account. In regards to the 1314 error, that's
generally related to rights of the MSSQLServer service
account, *not* the proxy account. So it's that account that
is missing the rights of either/both Act as part of
operating system and increase quotas. You could also be
missing Replace process level token based on some of what
you posted earlier. I'm pretty sure there is a Knowledge
base article on this somewhere.
Sounds like you have some issues with the MSSQLServer
service account and that you may have changed it through the
services applet instead of Enterprise Manager. If you change
the service account through Enterprise Manager, the
permissions and rights will be set correctly.
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Okay...and right after I posted, I found the other KB
article I mentioned that has more info on error 1314:
PRB: Error 1314 Raised By xp_cmdshell When Executed as
Non-SA User
http://support.microsoft.com/?id=248391
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Thanks ... I have tried to follow both articles (actually almost every
article online that I can dig out). It is still not working even though EM
says "successfully". I decided to use another technology instead of
XP_cmdshell. My guess is that some kind of security patches blocked it.
"Sue Hoegemeier" wrote:
> Okay...and right after I posted, I found the other KB
> article I mentioned that has more info on error 1314:
> PRB: Error 1314 Raised By xp_cmdshell When Executed as
> Non-SA User
> http://support.microsoft.com/?id=248391