Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 953
  • Last Modified:

I just added a proxy to a Agent Job and got the following error.

I just added a proxy to a Agent Job and got the following error.

 Grant permission by calling sp_grant_proxy_to_subsystem or sp_grant_login_to_proxy

Does anybody know fix?

thanks
0
Mr_Shaw
Asked:
Mr_Shaw
  • 12
  • 10
1 Solution
 
subhashpuniaCommented:
In which group you created the proxy and what type of command youa re using in Agent job?
Do the credential (used for proxy) have the permission for the resource used by job?
0
 
EvilPostItCommented:
Have you granted the relevant subsystem permissions to the proxy user. Ie if you are runnning an SSIS package then you will have to grant the user access to the SSIS subsystem.
0
 
EvilPostItCommented:
The order in which you should set up a proxy is to add the user to Security > Credentials and then under "SQL Server Agent" > Proxies (Right Click) New Proxy and assign the subsystem permissions.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
Mr_ShawAuthor Commented:
Ok past that error now... the new error is

Unable to start execution of step 3 (reason: Could not get proxy data for proxy_id = 41).  The step failed.

This is tricky...
0
 
EvilPostItCommented:
Have you entered DOMAIN\USER in the credential?
0
 
Mr_ShawAuthor Commented:
No I am using a sql account.
0
 
EvilPostItCommented:
And what subsystem are you accessing? T-SQL?
0
 
Mr_ShawAuthor Commented:
i am not sure what subsystem I am using....

I am using SQL Server 2005.
0
 
EvilPostItCommented:
In the drop down in the job you have created you will see as per the screen shot. This is the subsystem. SUBSYSTEM
0
 
Mr_ShawAuthor Commented:
Oh Operation System (CmdExec)
0
 
EvilPostItCommented:
Is your SQL Service running under "Local System" or is a user specified?
0
 
Mr_ShawAuthor Commented:
I also tried it using SSIS
0
 
Mr_ShawAuthor Commented:
>>Is your SQL Service running under "Local System" or is a user specified?

Everything is under local system.

0
 
EvilPostItCommented:
What command are you running?
0
 
Mr_ShawAuthor Commented:
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTEXEC.EXE" /SQL "\BReports\Invoicing" /SERVER AD1/MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E

This command work fine if i run the Job under the SA account.

When I use the proxy it does not work.

I have included sysadmin and SQLAgentUserRole in the principals of the proxy.
0
 
EvilPostItCommented:
Sorry thinking about that is the SQL Server agent running under local system?
0
 
Mr_ShawAuthor Commented:
Yes the agent is also running under local system.
0
 
EvilPostItCommented:
Interesting that it worked with SA... I take it you dont want to use a windows account?
0
 
Mr_ShawAuthor Commented:
I don't know which windows account to use... unless I ask for a new one to be created.
0
 
EvilPostItCommented:
Probably a good idea to get a Jew one created with the specific filesystem permissions that are needed.
0
 
Mr_ShawAuthor Commented:
thank you so much for helping me through this issue.

A new domain account was created which I used in the proxy.

It all works now.
0
 
EvilPostItCommented:
No probs.
0
 
EvilPostItCommented:
Just saw the "Jew one" bit in my reply. Sorry was supposed to be "New one". Damn iPhone autocorrect.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 12
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now