Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 xp_sqlagent_proxy_account

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2001-11-16 : 09:38:48
Ion writes "Hello,

If SQL2k run under SystemAccount the following statement works well:

EXEC master.dbo.xp_sqlagent_proxy_account N'SET',
N'MyDomain, -- agent_domain_name
N'user1', -- agent_username
N'pass1'


If the SQL2K service is started under a local account on a standalone server 2k, when I try to run the same setting I receive the folowing error:

Error executing extended stored procedure: Specified user can not login

Also, if the machine is a domain controller the problem does not exist.

I tried to join the standalone server to the domain but the result is the same.

What can I do?

Thank you,

Ion"

scottpt
Posting Yak Master

186 Posts

Posted - 2002-05-06 : 10:58:42
I am having this problem also. I cannot find anything about this anywhere. Any help would be appreciated.

Go to Top of Page

scottpt
Posting Yak Master

186 Posts

Posted - 2002-05-07 : 14:17:51
BUMP

Go to Top of Page

chadmat
The Chadinator

1974 Posts

Posted - 2002-05-08 : 01:33:09
What are the permissions of the Local account that is used for the service? Is it an administrator?

-Chad

Go to Top of Page

scottpt
Posting Yak Master

186 Posts

Posted - 2002-05-08 : 10:10:32
The account is in the administrators group on the local machine. The server is stand alone.

Go to Top of Page

scottpt
Posting Yak Master

186 Posts

Posted - 2002-05-08 : 10:11:24
The account is also set up in SQLServer as NT authenticated with sysadmin rights.

Go to Top of Page

scottpt
Posting Yak Master

186 Posts

Posted - 2002-05-13 : 09:03:58
Has anybody else had this problem??

Go to Top of Page

scottpt
Posting Yak Master

186 Posts

Posted - 2002-05-15 : 11:09:02
After many painfull days I have figured it out.

The NT account needs these permissions:

Act as part of the operating system.
Increase quotas.
replace process level token.
Log on as a batch job.

Search on PRB: Error 1314 in the knowledge based.

Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2002-05-15 : 11:57:11
Uhhhhhh, didn't you say this last week:

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=14199

What happened?

Edited by - robvolk on 05/15/2002 11:57:43
Go to Top of Page

scottpt
Posting Yak Master

186 Posts

Posted - 2002-05-17 : 11:14:07
Yes, but the errors were different. The fix was the same. And just make sure when you do check permissions you differentiate between 'administrator' and 'administrators'. That is what got me.



Edited by - scottpt on 05/17/2002 11:15:32
Go to Top of Page

chadmat
The Chadinator

1974 Posts

Posted - 2002-05-19 : 15:04:33
When you change the security account for the SQL Sevice through Enterprise Manager, It automaically give the account the appropriate rights.

I know it needs:
Act as part of OS
Replace a Process Level Token
Logon as a Service
Increase Quotas

Never heard of it needing the Batch Job one.

Anyway, this is one of the reasons why it is suggested that all changes to the Service account happen through SEM.

-Chad

Go to Top of Page
   

- Advertisement -