|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > Scheduling a DTS Task - rights issue ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Scheduling a DTS Task - rights issue ?
|
|
| Alex Au 2002-11-29, 11:23 am |
| One of our developers ( has not got sa right ) has created
a simple DTS package ( under SQL Server 2000 sp2, WIndows
2000 SP3 ), a simple print command from Execute SQL Task.
When this DTS is executed under the users Windows logon it
works fine. But when he scheduled the DTS as a job, and
manually tried to start the job the job fails. There is no
error I could find from event log. It seems that only when
the job is owned by sa, or users with sa right then the
job runs OK. Is this normal behavior?
Could the recent installation of Windows sp3 on the server
has anything to do with this?
Thanks in advance
Alex
| |
| chris 2002-11-29, 11:23 am |
| I beleive you need to specify an account for the jobs to run in. RClick SQL
Server Agent/ props/ job system/ ucheck Only users with SA bla bla bla/
Reset Proxy Account/ specify the name and password of SA or Administrator.
Im pretty sure thats it. If not let us know.
"Alex Au" <alex.au@ace-ina.com> wrote in message
news:1f36c01c297c6$64513e80$8a
f82ecf@TK2MSFTNGXA03...
> One of our developers ( has not got sa right ) has created
> a simple DTS package ( under SQL Server 2000 sp2, WIndows
> 2000 SP3 ), a simple print command from Execute SQL Task.
> When this DTS is executed under the users Windows logon it
> works fine. But when he scheduled the DTS as a job, and
> manually tried to start the job the job fails. There is no
> error I could find from event log. It seems that only when
> the job is owned by sa, or users with sa right then the
> job runs OK. Is this normal behavior?
>
> Could the recent installation of Windows sp3 on the server
> has anything to do with this?
>
> Thanks in advance
>
> Alex
>
>
>
| |
| Alex Au 2002-11-29, 11:23 am |
| Chris
This is exactly the solution to our problem. Thank you
very much! Much appreciated.
Alex
>-----Original Message-----
>I beleive you need to specify an account for the jobs to
run in. RClick SQL
>Server Agent/ props/ job system/ ucheck Only users with
SA bla bla bla/
>Reset Proxy Account/ specify the name and password of SA
or Administrator.
>Im pretty sure thats it. If not let us know.
>
>"Alex Au" <alex.au@ace-ina.com> wrote in message
> news:1f36c01c297c6$64513e80$8a
f82ecf@TK2MSFTNGXA03...
>> One of our developers ( has not got sa right ) has
created
>> a simple DTS package ( under SQL Server 2000 sp2,
WIndows
>> 2000 SP3 ), a simple print command from Execute SQL
Task.
>> When this DTS is executed under the users Windows logon
it
>> works fine. But when he scheduled the DTS as a job, and
>> manually tried to start the job the job fails. There is
no
>> error I could find from event log. It seems that only
when
>> the job is owned by sa, or users with sa right then the
>> job runs OK. Is this normal behavior?
>>
>> Could the recent installation of Windows sp3 on the
server
>> has anything to do with this?
>>
>> Thanks in advance
>>
>> Alex
>>
>>
>>
>
>
>.
>
| |
| Allan Mitchell 2002-11-30, 2:23 am |
| Have a look at this
INF: How to Run a DTS Package as a Scheduled Job
PSS ID Number: Q269074
Article Last Modified on 06-19-2002
--
Allan Mitchell (Microsoft SQL Server MVP)
www.SQLDTS.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Alex Au" <alex.au@ace-ina.com> wrote in message
news:1f36c01c297c6$64513e80$8a
f82ecf@TK2MSFTNGXA03...
> One of our developers ( has not got sa right ) has created
> a simple DTS package ( under SQL Server 2000 sp2, WIndows
> 2000 SP3 ), a simple print command from Execute SQL Task.
> When this DTS is executed under the users Windows logon it
> works fine. But when he scheduled the DTS as a job, and
> manually tried to start the job the job fails. There is no
> error I could find from event log. It seems that only when
> the job is owned by sa, or users with sa right then the
> job runs OK. Is this normal behavior?
>
> Could the recent installation of Windows sp3 on the server
> has anything to do with this?
>
> Thanks in advance
>
> Alex
>
>
>
|
|
|
|
|