February 28, 2003 at 6:07 pm
I am running on SQL 2000 with SP2 and some hot fixes (8.00.679). I have a DTS job that logs onto another server (via NT authentication) to pull some data to my server. When I run the DTS job it works fine, but when I run the job as a scheduled task it is run as the login of the SQL Agent, which does not have access to the other server. I have the job owned by the login that has access is there anyway to force the job to run under my UserID short of having the SQLAgent run under my UserId.
March 3, 2003 at 8:00 am
This was removed by the editor as SPAM
March 3, 2003 at 3:21 pm
DTS will asume the security context of the process that is actually executing the package. Maybe you could try a CmdExec using 'Run As'.
Thanks
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
March 3, 2003 at 6:04 pm
Try to configure SQL Agent account with your NT login and should work.
SQL Agent property --> Job System --> uncheck 'Non-SysAdmin job step proxy account' --> click 'Reset Proxy Account' --> Enter your NT login/password and domain'.
March 12, 2003 at 9:30 am
I recommend you set up a user for your SQL Server to use. During the installation, you have the choice to use local administrator or an NT user of your choice during the installation. You can change this through services. This user would need domain admin rights.
I know not all system administrators are thrilled about this, but if you use a real password, there's no real security risk.
Also, if you set up the user with an email account, you can use that account to email you about the jobs.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply