April 30, 2009 at 12:37 pm
The role has the permission(s) to start and stop jobs however, it is giving the group the above message. It is a windows ad group and is in the developement enviironment with execute permissions on both sp's.
Any advice appreciated.
¤ §unshine ¤
April 30, 2009 at 2:15 pm
When Jobs are run through a .NET application the base requirement is it runs in the context of the Agent which means you need to create a proxy account with admin permissions and run the job with the Agent in the context of the proxy permissions. If this is Asp.net the runtime also needs permissions in both the server and the actual database used to run the code.
AD permissions are not relevant in Asp.net.
Kind regards,
Gift Peddie
April 30, 2009 at 2:43 pm
The proxy account is set up the same way on another server. The old server on v3257 works but new server on 4035 does not work.
¤ §unshine ¤
April 30, 2009 at 2:48 pm
I don't understand what you mean by that because I did not see admin permissions in your original post so you need to make sure you meet that base requirement and run your code again.
Kind regards,
Gift Peddie
April 30, 2009 at 2:52 pm
It is to give developers access to run a job. Our old dev server allows them to, with exact same settings. This new one. does not.
¤ §unshine ¤
April 30, 2009 at 3:07 pm
I understand your reticent but a proxy account is a system account that cannot be used for anything so you either correct your permissions limitations or do the job manually. SSIS jobs with proxy accounts runs bank deposit transfer in many web banking on the Microsoft platform so the risk is limited.
Kind regards,
Gift Peddie
May 1, 2009 at 9:32 am
I am not sure I understand what you are saying. However, I created a sql user and give it direct permissions to execute on sp_start_job and that stilli gives the permission denied error on that particular proc.
¤ §unshine ¤
May 1, 2009 at 11:47 am
Those permission denied is due to Microsoft wanting a proxy to go back to an Admin because it can also be used for SSIS data automation with other RDBMS. If you don't change the permission then you have to manually run the job for your developer.
Kind regards,
Gift Peddie
May 1, 2009 at 12:38 pm
The proxy is an admin on the box as well as sa on sql server.
¤ §unshine ¤
May 1, 2009 at 1:09 pm
That is not what your original post says which is just execute permissions because if your proxy is setup with admin permissions all you need to do is make sure your developers execute the code in the context of the Agent and not the developer.
Kind regards,
Gift Peddie
May 7, 2009 at 12:11 pm
We don't need to use a proxy, we have one server, not on a cluster on SQL SErver 2005 32bit in which it works (same settings, same rights) and one server, in which it is on a cluster 64bit and it does not work.
Are there any other suggestions?
¤ §unshine ¤
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply