December 17, 2003 at 12:19 pm
I am running SQL 2K on Windows 2K with SP2. (I am going to go to SP3a this weekend.)
I am trying to add a proxy account so I can have non-sysadmins run the xp_cmdshell procedure. (I am already aware of the problems with this!)
When I run the xp_sqlagent_proxy_account procedure, with the domain, user, and password, I get the following error:
Error executing extended stored procedure: Specified user can not login
I am trying to setup the proxy account as the same account that runs the SQL Server and SQL Server Agent services. I did check to make sure the login and password were correct by logging into the server using this login and password. Everything worked fine.
I have searched the web looking for an answer but I have not found a solution that works for me.
All help is appreciated.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
December 17, 2003 at 12:33 pm
quote:
Error executing extended stored procedure: Specified user can not login
Has this user been granted to access SQL Server?
December 17, 2003 at 12:34 pm
Yes. This account is part of the sysadmin server role.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
December 17, 2003 at 12:42 pm
What local policies does it have? Can you add it into local administrators group and try again?
December 17, 2003 at 12:43 pm
It is already part of the local Administrators group and I have checked all of the rights it has on the server. Everything looks good.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
December 17, 2003 at 12:53 pm
Have you tried to set proxy account through EM?
December 17, 2003 at 12:56 pm
I get the same error there, too.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
December 17, 2003 at 1:00 pm
Ca you post SQL Server version by select @@version?
December 17, 2003 at 1:06 pm
Microsoft SQL Server 2000 - 8.00.679 (Intel X86) Aug 26 2002 15:09:48 Copyright (c) 1988-2000 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
December 17, 2003 at 1:16 pm
Ok. I can't re-produce the error you had in my SQL Server that has same version on both SQL Server and Windows. I would try to drop the login from SQL Server and re-grant it in SQL Server with 'sa' privilege as last try.
Edited by - allen_cui on 12/17/2003 1:17:08 PM
December 18, 2003 at 7:28 am
For the looks of things, it isn't SQL Giving you this error, it looks like a NT user right problem. In the local security settings control panel, validate that the NTuser or Administrators (if your user is part of Administrators) group has "Logon on As Batch" authority.
Also remember, if you want the SQL Logon to use the xp_cmdshell you will need to grant access to xp_cmdshell extended stored procedure
December 18, 2003 at 7:32 am
It's not an NT user right problem. I logged into the server with the account that I am trying to make my proxy account. Also, the message comes as a result of running the extended stored procedure. The message comes from SQL Server, not the Windows server.
I will grant the necessary permissions to the procedure once I can get the proxy account setup.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
December 18, 2003 at 8:43 am
Am I correct that you are trying to map the SQL server service account, the SQL agent service account, and the proxy account; all to the same domain login? I thought the proxy account had to be a different domain account from the service account?
December 18, 2003 at 8:50 am
Yes, I am trying to make them all the same account. I have not seen anything that says this will not work.
Also, I tried using my own login as the proxy account and I got the same error.
BTW, I just got through installing SP3a and the latest security patch on another SQL Server and I am getting the same error here also so it doesn't seem to necessarily be related to the SP level.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
December 19, 2003 at 8:03 am
epay0,
I had already reviewed that article and it applies to SQL 7.0.
Thanks anyway.
I think we may be close to solving this problem. The problem seems to be with the user rights assigned to the account. In my environment, it looks like we may have domain-level group policies that are overriding some local policies and not giving the account all of the rights it needs.
I will post again when I get a solution, whatever it turns out to be.
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply