Discussion:
Sql Server Job security problem
(too old to reply)
GC
2009-03-02 16:54:01 UTC
Permalink
Hi,

I have a job that run a SSIS package
When I run the SSIS package manually it works fine and I am login as the
user da on the computer and also da on Sql Server Studio Managment

da is a domaine admistrator user.
I also include this user in Sql Server 2005 as a login user with sysadmin
right
I also use this user to run SqlAgent services

I create a proxy with a credential that log as da with his password
In my job I select run as Sql Server Proxy which is the proxy account that
I create with the credential.

I also give thos Security Local Policy to the user da
Log on as a service (SeServiceLogonRight)
Log on as a batch job (SeBatchLogonRight)
Replace a process-level token (SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)

When I start the job I received this error
Unable to start execution of step 1 (reason: Error authenticating proxy
FN\da, system error: ConnGetProxyPassword). The step failed.

In the SSIS Package I have somme string connection with Integrity security,
not a user and password.

Example :
Data Source=FNTEST04;Initial
Catalog=AMC_AccPac_Import;Provider=SQLOLEDB.1;Integrated Security=SSPI;

I am working on this security issue for 3 days now and it is getting to be
frustrating
I read a lot of documentation and it seems that I miss something that I dont
understand.

Do you have any idea!

Thank in advance!
Todd C
2009-03-03 13:56:01 UTC
Permalink
Post by GC
Unable to start execution of step 1 (reason: Error authenticating proxy
FN\da, system error: ConnGetProxyPassword). The step failed.
Did the password of your FN\da account change?

Try logging in as different users to the same machine and executing via the
SSIS instance inside SSMS.
What happens when you try to set up the job to run under the Service account?

FYI: Running an SSIS package (or any process, for that matter) under the
priveledges of a Domain Administrator is NOT recommended. You are better off
creating a 'least priveledged account' for getting the job(s) done, and
granting only those security rights as are required.
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]
Continue reading on narkive:
Loading...